Patent Application
20240146441
The disclosure relates to a wireless communication system and, more particularly, to a method and apparatus for smoothly providing a service in a communication system. More specifically, the disclosure relates to a method and apparatus for transmitting or receiving control information by a terminal in a communication system.
To meet the demand for wireless data traffic having increased since deployment of 4G communication systems, efforts have been made to develop an improved 5G or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called a “Beyond 4G Network” or a “Post LTE System”.
The 5G communication system is considered to be implemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higher data rates. To decrease propagation loss of the radio waves and increase the transmission distance, the beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, an analog beam forming, large scale antenna techniques are discussed in 5G communication systems.
In addition, in 5G communication systems, development for system network improvement is under way based on advanced small cells, cloud radio access networks (RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), reception-end interference cancellation and the like.
In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access(NOMA), and sparse code multiple access (SCMA) as an advanced access technology have also been developed.
The Internet, which is a human centered connectivity network where humans generate and consume information, is now evolving to the Internet of things (IoT) where distributed entities, such as things, exchange and process information without human intervention. The Internet of everything (IoE), which is a combination of the IoT technology and the big data processing technology through connection with a cloud server, has emerged. As technology elements, such as “sensing technology”, “wired/wireless communication and network infrastructure”, “service interface technology”, and “security technology” have been demanded for IoT implementation, a sensor network, a machine-to-machine (M2M) communication, machine type communication (MTC), and so forth have been recently researched. Such an IoT environment may provide intelligent Internet technology services that create a new value to human life by collecting and analyzing data generated among connected things. IoT may be applied to a variety of fields including smart home, smart building, smart city, smart car or connected cars, smart grid, health care, smart appliances and advanced medical services through convergence and combination between existing information technology (IT) and various industrial applications.
In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as a sensor network, machine type communication (MTC), and machine-to-machine (M2M) communication may be implemented by beamforming, MIMO, and array antennas. Application of a cloud radio access network (RAN) as the above-described big data processing technology may also be considered an example of convergence of the 5G technology with the IoT technology.
As described above, a plurality of services can be provided to a user in a communication system, and in order to provide the plurality of services to the user, a method capable of providing respective services according to characteristics in the same time section and an apparatus using the same are required. Various services provided in the 5G communication system are being studied, and one criterion for such services is a service that satisfies a low-latency requirement. Another one is that the services satisfy a high-reliability requirement. Consideration of both of these requirements is described in the disclosure as ultra-reliability and low latency communication (URLLC). In order to dynamically support a service that satisfies various URLLC requirements, a base station needs a method of dynamically supporting various methods of performing transmission to a terminal.
An embodiment of the specification has been proposed in order to solve the above-mentioned problems, and aims to provide a method and an apparatus for simultaneously providing different types (or the same type) of services.
In addition, an embodiment of the specification is to provide various methods and apparatuses for determining a modulation and coding scheme (MCS) by a terminal. In addition, an embodiment of the specification is to provide a method and apparatus for supporting multiple modulation and coding schemes (MCS) by a base station. Specifically, an embodiment is to provide a method for indicating or configuring, by a base station, a specific MCS table for a terminal in a situation where the terminal receives support according to two or more MCS tables.
In order to solve the above problems, a method performed by a terminal in a wireless communication system includes transmitting, to a base station, capability information including information on whether the terminal supports a capability associated with a specific target BLER, receiving DCI from the base station, wherein a CRC of the DCI is scrambled by an RNTI associated with a URLLC service, receiving, from the base station, a PDSCH based on the DCI, and identifying a modulation order and a target code rate for the PDSCH based on an MCS table, wherein the MCS table is determined based on the RNTI scrambled to the CRC of the DCI.
In order to solve the above problems, a method performed by a base station in a wireless communication system includes receiving, from a terminal, capability information including information on whether the terminal supports a capability associated with a specific target BLER, transmitting DCI to the terminal, wherein a CRC of the DCI is scrambled by an RNTI associated with a URLLC service, generating a PDSCH based on a modulation order and a target code rate for the PDSCH, and transmitting, to the terminal, the PDSCH based on the DCI, wherein the modulation order and the target code rate for the PDSCH is based on an MCS table, and wherein the MCS table is associated with the RNTI scrambled to the CRC of the DCI.
In order to solve the above problems, a terminal in a wireless communication system includes a transceiver configured to transmit and receive a signal, and a controller configured to transmit, to a base station, capability information including information on whether the terminal supports a capability associated with a specific target BLER, receive DCI from the base station, wherein a CRC of the DCI is scrambled by an RNTI associated with a URLLC service, receive, from the base station, a PDSCH based on the DCI, and identify a modulation order and a target code rate for the PDSCH based on an MCS table, wherein the MCS table is determined based on the RNTI scrambled to the CRC of the DCI.
In order to solve the above problems, a base station in a wireless communication system includes a transceiver configured to transmit and receive a signal, and a controller configured to receive, from a terminal, capability information including information on whether the terminal supports a capability associated with a specific target BLER, transmit DCI to the terminal, wherein a CRC of the DCI is scrambled by an RNTI associated with a URLLC service, generate a PDSCH based on a modulation order and a target code rate for the PDSCH, and transmit, to the terminal, the PDSCH based on the DCI, wherein the modulation order and the target code rate for the PDSCH are based on an MCS table, and wherein the MCS table is associated with the RNTI scrambled to the CRC of the DCI.
The above and other aspects, features, and advantages of certain embodiments of the present disclosure will be more apparent from the following detailed description, when taken in conjunction with the accompanying drawings, in which:
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.
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.
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.
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.
Here, 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.
Further, each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
As used herein, the “unit” refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the “unit” does not always have a meaning limited to software or hardware. The “unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the “unit” includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the “unit” may be either combined into a smaller number of elements, or a “unit”, or divided into a larger number of elements, or a “unit”. Moreover, the elements and “units” or may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Further, the “unit” in the embodiments may include one or more processors.
Wireless communication systems, which provided voice-oriented services in early stages, have evolved into broadband wireless communication systems that provide high-speed and high-quality packet data services according to communication standards such as high-speed packet access (HSPA) of 3GPP, long-term evolution (LTE), evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-A), high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), and IEEE 802.16e. In addition, a communication standard of 5G or new radio or next radio (NR) is being produced as a 5th-generation wireless communication system.
As described above, in a wireless communication system including a 5th-generation wireless communication system, at least one service among enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC) may be provided to a terminal. The services may be provided to the same terminal during the same time period. In an embodiment, eMBB may be a service aiming at high-speed transmission of high-capacity data, mMTC may be a service aiming at minimization of terminal power consumption and access by multiple terminals, and URLLC may be a service aiming at high reliability and low latency, but the disclosure is not intended to be limited thereto. The three services may be a main scenario in an LTE system or a system such as 5G and/or NR after the LTE system. According to an embodiment of the disclosure, a method for coexistence between eMBB and URLLC or coexistence between mMTC and URLLC, and an apparatus using the same are described.
If a base station has scheduled, for any terminal, data corresponding to an eMBB service during a particular transmission time interval (TTI), if there occurs the situation where URLLC data must be transmitted during the TTI, a part of the eMBB data may not be transmitted in a frequency band in which the eMBB data is already scheduled and transmitted, but the generated URLLC data may be transmitted in the frequency band. The terminal for which the eMBB data has been scheduled and the terminal for which the URLLC data has been scheduled may be the same terminal or different terminals. In the example, since there occurs the situation where a part of the eMBB data that has already been scheduled for transmission is not actually transmitted, the possibility that the eMBB data will be damaged becomes higher. Accordingly, in the above case, it is necessary to determine a method for processing a received signal by the terminal for which the eMBB data has been scheduled or by the terminal for which the URLLC data has been scheduled, or a signal reception method thereof.
Therefore, according to an embodiment of the disclosure, a description is provided of a method for coexistence of heterogeneous services for enabling transmission of information according to each service when part or all of a frequency band is shared so as to schedule pieces of information (which may include data and control information) according to eMBB and URLLC, simultaneously schedule pieces of information according to mMTC and URLLC, simultaneously schedule pieces of information according to mMTC and eMBB, or simultaneously schedule pieces of information according to eMBB, URLLC, and mMTC.
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. In addition, in describing the disclosure, if it is determined that a detailed description of related functions or configurations may unnecessarily obscure the subject matter of the disclosure, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the disclosure, and may vary according to a user's or operator's intention or practice. Therefore, the definition should be made based on the contents throughout this specification.
Hereinafter, a base station is the entity that performs resource allocation for a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a terminal, a cellular phone, a smart phone, a computer, or a multimedia system capable of performing communication functions. In the disclosure, a downlink (DL) indicates a radio transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) indicates a radio transmission path of a signal transmitted by the terminal to the base station. In addition, although an embodiment of the disclosure is described below as an example of an LTE or LTE-A system, the embodiment of the disclosure may be applied to other communication systems having a similar technical background or channel form. For example, 5G mobile communication technology, developed after LTE-A, may be included in other communication systems. In addition, the embodiments of the disclosure may be applied to other communication systems through some modifications within a range that does not significantly depart from the scope of the disclosure, according to the determination of those skilled in the art.
As a representative example of broadband wireless communication systems, an LTE system (hereinafter, examples of the LTE system may include LTE and LTE-A systems) adopts an orthogonal frequency division multiplexing (OFDM) scheme in a downlink, and adopts a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink. The term “uplink” refers to a radio link through which a terminal transmits data or a control signal to a base station, and the term “downlink” refers to a radio link through which a base station transmits data or a control signal to a terminal. The above-described multiple access scheme normally allocates and operates time-frequency resources, which carry data or control information to be transmitted according to users, so as to prevent the time-frequency resources from overlapping each other, that is, establish orthogonality, thus making it possible to distinguish the data or control information of one user from another.
If a decoding failure occurs upon initial transmission, the LTE system adopts a hybrid automatic repeat request (HARQ) scheme for retransmitting the relevant data in a physical layer. If a receiver fails to accurately decode data, the HARQ scheme enables the receiver to transmit, to a transmitter, information (negative acknowledgement (NACK)) providing notification of the decoding failure and thus the transmitter can retransmit the corresponding data in the physical layer. The receiver combines the data retransmitted by the transmitter with the data for which decoding failed, thereby increasing the data reception performance. In addition, if the receiver accurately decodes the data, information (acknowledgement (ACK)) providing notification of decoding success is transmitted to the transmitter, and thus the transmitter may transmit new data.
Referring to
The basic unit of resources in the time-frequency domain is a resource element (RE) 112, and may be represented by an OFDM symbol index and a subcarrier index. A resource block (RB) (or a physical resource block (PRB)) 108 may be defined by Nsymb consecutive OFDM symbols 102 in the time domain and N RB consecutive subcarriers 110 in the frequency domain. Accordingly, in one slot, one RB 108 may include Nsymb×NRBREs 122. Generally, the minimum allocation unit of data in the frequency domain is the RB unit. In the LTE system, generally, Nsymb=7 and NRB=12, and NBW may be proportional to the bandwidth of the system transmission band. The data rate is increased in proportion to the number of RBs scheduled for the terminal. The LTE system may define and operate six transmission bandwidths. In an FDD system, which operates the downlink and the uplink separated in the frequency domain, a downlink transmission bandwidth and an uplink transmission bandwidth may be different from each other. The channel bandwidth represents a radio frequency (RF) bandwidth, which corresponds to the system transmission bandwidth. <Table 1> below shows the correspondence relationship between the system transmission bandwidth and channel bandwidth defined in the LTE system. For example, in an LTE system having a channel bandwidth of 10 MHz, a transmission bandwidth may include 50 RBs.
Downlink control information may be transmitted within the first N OFDM symbols within the subframe. In an embodiment, generally, N={1, 2, 3}. Accordingly, the value of N may be variably applied to each subframe depending on the amount of control information that needs to be transmitted in the current subframe. The control information to be transmitted may include a control channel transmission section indicator, indicating the number of OFDM symbols in which the control information is transmitted, scheduling information for downlink data or uplink data, and information for HARQ ACK/NACK.
In the LTE system, scheduling information of downlink data or uplink data is delivered from a base station to a terminal through downlink control information (DCI). The DCI may be defined depending on various formats. According to each format, the DCI may indicate whether the DCI is scheduling information (UL grant) of the uplink data or scheduling information (DL grant) of the downlink data, whether the DCI is compact DCI having small-sized control information, whether to apply spatial multiplexing using multiple antennas, whether the DCI is DCI for power control, and the like. For example, DCI format 1, which is the scheduling control information (DL grant) of the downlink data, may include at least one piece of information among the following pieces of control information.
The DCI may be subjected to a channel coding and modulation process, and may then be transmitted through a physical downlink control channel (PDCCH) (or downlink control information transmitted through a PDCCH, the terms “PDCCH” and “downlink control information” being interchangeably used hereinafter) or an enhanced PDCCH (EPDCCH) (or downlink control information transmitted through an EPDCCH, “EPDCCH” and “downlink control information” being interchangeably used hereinafter).
Generally, the DCI is independently scrambled by a particular radio network temporary identifier (RNTI) (which may be understood as a terminal identifier or a terminal ID) for each terminal so as to have a cyclic redundant check (CRC) bit added thereto, is channel-coded, and is then configured as independent PDCCH and then transmitted. In the time domain, the PDCCH is mapped and then transmitted during the control channel transmission section. The mapping location in the frequency domain of the PDCCH may be determined based on an identifier of each terminal and transmitted over the entire system transmission bandwidth.
The downlink data may be transmitted through a physical downlink shared channel (PDSCH), which is a physical channel for downlink data transmission. The PDSCH may be transmitted after the control channel transmission section in the time axis, and scheduling information of a detailed mapping location in the frequency domain of the PDSCH, a modulation scheme, or the like may be determined based on the DCI transmitted through the PDCCH.
Through MCS, among the pieces of control information configuring the DCI, a base station provides notification of the modulation scheme applied to a PDSCH to be transmitted to a terminal and the size of data (transport block size (TBS)) to be transmitted. In an embodiment, the MCS may include 5 bits or a number of bits greater than or less than 5 bits. The TBS corresponds to a size before channel coding for error correction is applied to a data transport block (TB) to be transmitted by the base station.
Modulation schemes supported by the LTE system include quadrature phase shift keying (QPSK), 16 quadrature amplitude modulation (QAM), and 64 QAM, of which modulation orders Qms correspond to 2, 4, and 6, respectively. That is, in the case of QPSK modulation, 2 bits per symbol may be transmitted, in the case of 16 QAM modulation, 4 bits per symbol may be transmitted, and in the case of 64 QAM modulation, 6 bits per symbol may be transmitted. In addition, modulation schemes above 256 QAM may be used depending on system modification.
Referring to
The basic unit of resources in the time-frequency domain is a resource element (RE) 212, and may be defined by an SC-FDMA symbol index and a subcarrier index. A resource block (RB) 208 may be defined by Nsymb consecutive SC-FDMA symbols in the time domain and NRB consecutive subcarriers 210 in the frequency domain. Accordingly, one RB includes Nsymb×NRB REs. In general, a minimum transmission unit of data or control information is an RB unit. A PUCCH is mapped to a frequency domain corresponding to one RB and transmitted in one subframe.
In the LTE system, it is possible to define a timing relationship of a PUCCH or a PUSCH, that is, an uplink physical channel, through which a HARQ ACK/NACK corresponding to a PDSCH as a physical channel for downlink data transmission or a PDCCH or EPDDCH including a semi-persistent scheduling release (SPS release) is transmitted. For example, in an LTE system operating according to frequency division duplex (FDD), HARQ ACK/NACK, corresponding to the PDSCH transmitted in an (n−4)th subframe, or PDCCH or EPDCCH including the SPS release may be transmitted through the PUCCH or the PUSCH in an n-th subframe.
In the LTE system, a downlink HARQ adopts an asynchronous HARQ scheme in which a data retransmission time point is not fixed. That is, if, for initial transmission data transmitted by the base station, the HARQ NACK is fed back from the terminal, the base station freely determines the transmission time point of data to be retransmitted based on a scheduling operation. The terminal may perform buffering of data, which is determined as an error as a result of decoding the received data for a HARQ operation, and may then combine the same with data to be retransmitted next.
If the terminal receives a PDSCH including downlink data transmitted from the base station in subframe n, the terminal transmits uplink control information including a HARQ ACK or a NACK of the downlink data to the base station through a PUCCH or PUSCH in subframe (n+k). For example, k may be defined differently depending on whether the LTE system adopts FDD or time division duplex (TDD), and the UL/DL subframe configuration thereof. For example, in the case of an FDD LTE system, k is fixed to 4. In the case of a TDD LTE system, k may be determined according to a subframe configuration and a subframe number. In addition, if data is transmitted through multiple carriers, the value of k may be applied differently depending on the TDD configuration of each carrier.
In the LTE system, unlike a downlink HARQ, an uplink HARQ adopts a synchronous HARQ scheme in which a data transmission time point is fixed. That is, an uplink/downlink timing relationship between a physical uplink shared channel (PUSCH), which is a physical channel for uplink data transmission, a PDCCH, which is a downlink control channel preceding the PUSCH, and a physical hybrid indicator channel (PHICH), which is a physical channel through which a downlink HARQ ACK/NACK corresponding to the PUSCH is transmitted, may be determined by the following rules.
If, in the subframe n, the terminal receives a PDCCH including uplink scheduling control information transmitted from the base station or a PHICH through which a downlink HARQ ACK/NACK is transmitted, the terminal transmits uplink data corresponding to the control information through a PUSCH in a subframe (n+k). In this case, k may be defined differently depending on whether the LTE system adopts FDD or TDD, and on the subframe configuration thereof. For example, in the case of a FDD LTE system, k may be fixed to 4. In the case of a TDD LTE system, k may be determined according to a subframe configuration and a subframe number. In addition, if data is transmitted through multiple carriers, the value of k may be applied differently depending on the TDD configuration of each carrier.
In addition, if, in subframe i, the terminal receives a PHICH including information related to the downlink HARQ ACK/NACK from the base station, the PHICH corresponds to a PUSCH that the terminal transmits in subframe (i−k). For example, k may be defined differently depending on whether FDD or TDD is implemented in the LTE system and on the subframe configuration thereof. For example, in the case of the FDD LTE system, k is fixed to 4. In the case of the TDD LTE system, k may be determined according to the subframe configuration and the subframe number. In addition, if data is transmitted through multiple carriers, the value of k may be applied differently depending on the TDD configuration of each carrier.
<Table 2> above describes supportable DCI format types according to each transmission mode in conditions configured by C-RNTI included in 3GPP TS 36.213. A terminal performs search and decoding under the assumption that the corresponding DCI format exists in a control space section according to a pre-configured transmission mode. For example, if the terminal receives transmission mode 8 as an indication, the terminal searches for a DCI format 1A in a common search space and a UE-specific search space, and searches for a DCI format 2B only in the UE-specific search space.
The wireless communication system has been described with reference to the LTE system, but the disclosure is not limited to the LTE system, and may be applied to various wireless communication systems, including NR, 5G, and the like. In addition, in an embodiment, in the case of being applied to another wireless communication system, the value of k described above may be changed and applied even to a system using a modulation scheme corresponding to FDD.
A base station may select one of MCS tables, which are designed to have different target block length error rate (BLER) values, and provide the selected MCS table to a terminal (operation 310). For example, one of the MCS tables may be an MCS table that is configured with MCS values satisfying a target BLER of 10−1 (or a data transmission success rate of 90%). This is referred to as a first MCS table in the disclosure. According to another example, one of the MCS tables may be an MCS table configured with MCS values satisfying a target BLER of 10−5 (or a data transmission success rate of 99.999%). This is referred to as a second MCS table in the disclosure.
According to an example, the configuration of the first MCS table may be as shown in <Table 3> below. According to an example, the configuration of the second MCS table may be as shown in <Table 4> below. Referring to <Table 3> and <Table 4>, some MCS indexes may have the same modulation order, the same target code rate, or the same spectral efficiency values. <Table 3> shows the first MCS table based on the target BLER of 10−1, and <Table 4> shows the second MCS table based on the target BLER of 10−5. In the blank of Table 4, arbitrary values for satisfying the target BLER of 10−5 can be configured. In order to determine a modulation order, a target code rate, and a transport block size (TBS) of a downlink data channel, a terminal identifies MCS index values among MCS fields, configured as <Table 3> or <Table 4> in downlink control information.
According to the first embodiment, the terminal may determine whether an MCS index indicator in downlink control information (DCI) is based on the first MCS table or the second MCS table based on one bit in the DCI. In the disclosure, the one bit is described as an MCS table indicator. The MCS index indicator can be configured by five bits in the downlink control information. For example, if the 1-bit MCS table indicator indicates “0” (operation 320), the terminal determines a modulation order and a target code rate of downlink data or uplink data using the first MCS table and the index value of the corresponding table (operations 330, 350, and 360). According to another example, if the 1-bit MCS table indicator indicates “1” (operation 320), the terminal determines a modulation order and a target code rate of downlink data or uplink data using the second MCS table and the index values of the corresponding table (operations 340, 350, and 360). The 1-bit MCS table indicator information is included in the downlink control information existing together with CRC scrambled by C-RNTI.
For reference, the first MCS table (Table 3) and the second MCS table (Table 4) described in the first embodiment are sufficiently applicable to other embodiments.
According to the (1-1)th embodiment, for a terminal having reported, to a base station, UE capability supporting both a target BLER of 10−1 and a target BLER of 10−5, one bit, which is used as an MCS table indicator in the downlink control information having the CRC scrambled by C-RNTI, may always exist. The MCS table indicator is used to indicate whether an index value indicated by the MCS index indicator included in the downlink control information is based on the first MCS table or the second MCS table. In the case where the index value is based on the first MCS table, the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value based on the first MCS table. In the case where the index value is based on the second MCS table, the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value based on the second MCS table.
According to the (1-2)th embodiment, for a terminal having reported, to a base station, UE capability supporting only the target BLER of 10−1, the MCS index indicator in the downlink control information existing together with CRC scrambled by C-RNTI indicates an index based on the first MCS table, and the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value based on the first MCS table.
According to the (1-3)th embodiment, for a terminal having reported, to a base station, UE capability supporting only the target BLER of 10−5, the MCS index indicator in the downlink control information having the CRC scrambled by C-RNTI indicates an index based on the second MCS table, and the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value based on the second MCS table.
According to the second embodiment, the terminal may determine whether an MCS index indicator in downlink control information is based on a first MCS table or a second MCS table according to a value indicated by one of the fields existing in the downlink control information (operation 410).
For example, if a new data indicator (NDI) in the downlink control information is toggled, the terminal determines a modulation order and a target code rate of downlink data or uplink data using an index value indicated by the MCS index indicator based on the first MCS table. This may occur since, in the initial transmission, it is possible to use an MCS table having a high target BLER in order to improve transmission efficiency.
According to another example, if the NDI in the downlink control information is not toggled, the terminal determines a modulation order and a target code rate of downlink data or uplink data using an index value indicated by the MCS index indicator based on the second MCS table. This may occur since, in the initial transmission, it is possible to use an MCS table having a high target BLER in order to increase transmission efficiency, but in retransmission, the base station may perform transmission using an MCS table having a lower target BLER value in order to satisfy the required latency.
For example, if a PDSCH (or PUSCH) mapping type indicates type A in a time resource allocation field in the downlink control information (operation 420), the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 430, 450, and 460). The PDSCH (or PUSCH) mapping type A refers to a PDSCH in which the position of a demodulation reference signal (DMRS) for data decoding is fixed at a specific symbol position with reference to a slot boundary regardless of a data transmission start symbol position and a data transmission interval size. This is because PDSCH (or PUSCH) mapping A is more suitable for eMBB transmissions requiring a higher target BLER value than URLLC.
According to another example, if the PDSCH (or PUSCH) mapping type indicates type B in the time resource allocation field in the downlink control information (operation 420), the terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 430, 450, and 460). In PDSCH (or PUSCH) mapping type B, a DMRS symbol position is changed according to a data transmission start symbol position and a data transmission interval size, and the corresponding DMRS is located at the symbol at which the data transmission starts. This is because PDSCH (or PUSCH) mapping type B is more suitable for URLLC transmission requiring a lower target BLER value than that required by eMBB.
In addition to the NDI or the PDSCH mapping type illustrated in the above example, it is sufficiently possible to determine, by the terminal, whether the MCS index indicator is based on the first MCS table or the second MCS table, by replacing the NDI or PDSCH mapping type with a time resource allocation field, a frequency resource allocation field, a redundancy version (RV) field, a downlink assignment index (DAI) field, a HARQ process number field, a PDSCH-HARQ feedback timing indicator field, and the like.
According to the third embodiment, the terminal may determine whether an MCS index indicator in downlink control information is based on a first MCS table or a second MCS table, depending on the RNTI type scrambled with the CRC for the downlink control information (operation 510).
For example, the terminal determines that an MCS index indicator field in the downlink control information existing together with the CRC scrambled by RNTI type, such as cell RNTI (C-RNTI), configured scheduling RNTI (CS-RNTI), system information RNTI (SI-RNTI), paging RNTI (P-RNTI), or random access RNTI (RA-RNTI), is configured based on the first MCS table (operations 520 and 530). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 530, 550, and 560). The C-RNTI and CS-RNTI are RNTIs used for transmission of information such as eMBB. SI-RNTI is an RNTI used for transmission of system information. P-RNTI is an RNTI used for transmission of paging information. RA-RNTI is an RNTI used for transmission of random access-related information. The terminal determines that the MCS index indicator field in the downlink control information, which exists together with the CRC scrambled by the RNTI type, such as C-RNTI, CS-RNTI, SI-RNTI, P-RNTI, or RA-RNTI, is configured based on the first MCS table because uplink data or downlink data associated with the RNTIs described above are services that do not require a target BLER of 10−5.
According to another example, the terminal determines that the MCS index indicator field in the downlink control information, which exists together with the CRC scrambled by the RNTI type, such as URLLC C-RNTI (U-C-RNTI) or URLLC CS-RNTI (U-CS-RNTI), is configured based on the second MCS table (operations 520 and 540). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 540, 550, and 560). The U-C-RNTI and U-CS-RNTI are RNTIs used for transmission of information such as URLLC. The terminal determines that the MCS index indicator field in the downlink control information having the CRC scrambled by the U-C-RNTI and the U-CS-RNTI is configured based on the second MCS table because uplink data or downlink data associated with the RNTIs are services requiring a target BLER of 10−5.
According to the fourth embodiment, a terminal may determine whether the MCS index indicator in the downlink control information is based on the first MCS table or the second MCS table according to a search space type of a physical downlink control channel (PDCCH) searched for by the terminal. A set of PDCCH candidates searched for by the terminal is called a search space, and a set of PDCCH candidates searched for by all terminals in common is called a common search space (CSS) and a set of PDCCH candidates individually searched for by a specific terminal is called a UE-specific search space (USS).
For example, the terminal determines that the MCS index indicator field in the downlink control information found in the common search space is configured based on the first MCS table (operations 620 and 630), and the terminal determines a modulation order and a target code rate of downlink data or uplink data using an index value indicated by the MCS index indicator based on the first MCS table (operations 630, 640, and 650). The terminal determines that the MCS index indicator field in the downlink control information found in the common search space is configured based on the first MCS table because the common search space is a control information search area used for transmission of data such as system information, paging information, and random access information, which are not related to a specific data service such as eMBB or URLL, and thus do not require a target BLER of 10−5.
According to another example, the terminal determines that the MCS index indicator field in the downlink control information found in the UE-specific search space is configured based on the second MCS table (operations 620 and 640), and the terminal determines a modulation order and a target code rate of downlink or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 640, 650, and 660). The terminal determines that the MCS index indicator field in the downlink control information found in the UE-specific search space is configured based on the second MCS table because the UE-specific search space is a control information search area in which data related to a specific data service such as eMBB or URLLC can be transmitted, and a target BLER of 10−5 is required to support data transmission requiring high reliability, such as URLLC. If the terminal determines that the MCS index indicator field in the downlink control information found in the UE-specific search space is configured based on the second MCS table, the terminal that made the determination does not correspond to one of terminals supporting only eMBB. Instead, the terminal may be one of terminals supporting URLLC. Otherwise, the terminal may not correspond to one of terminals having reported the capability of URLLC non-supporting to the base station. Instead, the terminal may be one of terminals having reported the UE capability of URLLC supporting to the base station.
According to the fifth embodiment, when the terminal receives, from a base station, configuration of a control resource set (CORESET), which is a resource area in which downlink control information is searched for, the base station may configure whether the MCS index indicator field in downlink control information transmitted from the corresponding CORESET is based on the first MCS table or the second MCS table via higher-layer signaling.
For example, in the case where the base station is configured such that the MCS index indicator in the downlink control information transmitted in the first CORESET is based on the first MCS table (operation 720), the terminal determines that the MCS index indicator field found in the first CORESET is configured based on the first MCS table (operation 730). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 750 and 760).
According to another example, in the case where the base station is configured such that the MCS index indicator in the downlink control information transmitted in the second CORESET is based on the second MCS table (operation 720), the terminal determines that the MCS index indicator field found in the second CORESET is configured based on the second MCS table (operation 740). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 750 and 760).
According to the sixth embodiment, the terminal may determine whether an MCS index indicator in downlink control information is based on the first MCS table or the second MCS table according to the downlink control information format found by the terminal.
For example, the terminal determines that an MCS index indicator field in a fallback downlink information format that can be transmitted in both a common search space and a UE-specific search space is configured based on the second MCS table (operations 820 and 840). The terminal determines a modulation order and a target code rate of downlink data or uplink data using an index value indicated by the MCS index indicator based on the second MCS table (operations 840, 850, and 860). The fallback downlink control information format may correspond to DCI format 0_0 for PUSCH scheduling of 5G (NR) and DCI format 1_0 for PDSCH scheduling. The terminal determines that the MCS index indicator field in the fallback downlink information format is configured based on the second MCS table because the number of fallback downlink information format bits is generally smaller than the number of non-fallback downlink information format bits, and thus it is suitable for satisfying a condition (for example, reliability).
According to another example, the terminal determines that the MCS index indicator field in the non-fallback downlink control information format that can be transmitted in the UE-specific search space is configured based on the first MCS table (operations 820 and 830). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 830, 850, and 860). The non-fallback downlink control information format may correspond to DCI format 0_1 for PUSCH scheduling of 5G (NR) and DCI format 1_1 for PDSCH scheduling. The terminal determines that the MCS index indicator field in the non-fallback downlink information format is configured based on the first MCS table because the number of non-fallback downlink information format bits is generally larger than the number of fallback downlink information format bits, and thus it is not suitable for satisfying the URLLC requirement (e.g., reliability).
According to the seventh embodiment, a terminal may determine whether an MCS index indicator in downlink control information is based on a first MCS table or a second MCS table according to downlink control information format found by the terminal. In addition, an MCS table indicator field indicating whether the MCS index indicator is based on the first MCS table or the second MCS table is separately included in a specific downlink control information format.
For example, a fallback downlink control information format that can be transmitted in both a common search space and ae UE-specific search space includes a 1-bit MCS table indicator field (operation 920). The MCS table indicator field indicates whether the MCS index indicator is based on the first MCS table or the second MCS table (operation 940). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on a specific MCS table indicated by the MCS table indicator field (operations 942, 944, 960, and 960). The fallback downlink control information format may correspond to DCI format 0_0 for PUSCH scheduling of 5G (NR) and DCI format 1_0 for PDSCH scheduling. The MCS table indicator field is added to the fallback downlink control information format because eMBB and URLLC data can be dynamically supported in the fallback downlink control information format at the same time. In addition, other pieces of information (e.g., system information, paging information, and random access information) other than eMBB and URLLC data are also supported in the fallback downlink control information format.
According to another example, the terminal determines that an MCS index indicator field in a non-fallback downlink control information format that can be transmitted in the UE-specific search space is configured based on the first MCS table (operations 920 and 930). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 930, 950, and 960). The non-fallback downlink control information format may correspond to DCI format 0_1 for PUSCH scheduling of 5G (NR) and DCI format 1_1 for PDSCH scheduling. The terminal determines that the MCS index indicator field in the non-fallback downlink information format is configured based on the first MCS table because the number of non-fallback downlink information format bits is generally larger than the number of fallback downlink information format bits, and thus it is not suitable for satisfying the URLLC requirement (e.g., reliability, 10−5 target BLER).
According to the eighth embodiment, a terminal may determine whether an MCS index indicator in downlink control information is based on a first MCS table or a second MCS table according to a target BLER value related to channel quality indicator (CQI) configuration for measurement of channel state information (CSI).
A CQI table used for CQI index reporting may include a first CQI table based on a target BLER of 10−1 and a second CQI table based on a target BLER of 10−5. The base station may configure, via higher-layer signaling, whether the terminal uses the first CQI table or the second CQI table for CQI index reporting according to the result of channel measurement. In addition, CQI index reporting based on a specific CQI table, configured through the higher-layer signaling, can be performed based on the first CQI table and the second CQI table, which can be independently configured for a terminal. In other words, the terminal may receive configuration, as the CQI table used for CQI index reporting, of the first CQI table, the second CQI table, or both of them. The CQI index reporting is transmitted from the terminal to the base station through an uplink control channel or a data channel.
For example, if the terminal does not receive configuration of the CQI index reporting based on the second CQI table (operation 1020), the terminal determines that an MCS index indicator field in a downlink control information format found in a downlink control channel is configured based on the first MCS table (operation 1030). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 1030, 1050, and 1060).
When the terminal has received the configuration of the CQI index reporting based on the second CQI table (operation 1020), the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the second MCS table (operation 1040). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 1040, 1050, and 1060).
According to the (8-1)th embodiment, if the terminal has received the configuration of the CQI index reporting based on the first CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is based on the first MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table.
If the terminal has received the configuration of the CQI index reporting based on the second CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the second MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table.
If the terminal has received the configuration of all the CQI index reporting based on both the first CQI table and the second CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the second MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table.
According to the (8-2)th embodiment, if the terminal has received the configuration of the CQI index reporting based on the first CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the first MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table.
If the terminal has received the configuration of the CQI index reporting based on the second CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the second MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table.
If the terminal has received the configuration of all the CQI index reporting based on both the first CQI table and the second CQI table, the downlink control information format found in the downlink control channel includes a 1-bit MCS table indicator field. The MCS table indicator field indicates whether the MCS index indicator is based on the first MCS table or the second MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on a specific MCS table indicated by the MCS table indicator field.
According to the (8-3)th embodiment, if the terminal does not receive configuration of the CQI index reporting based on the second CQI table, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the first MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table.
If the terminal receives the configuration of the CQI index reporting based on the second CQI table, the 1-bit MCS table indicator is included in the downlink control information, in a situation in which specific conditions are satisfied, and the MCS table indicator indicates whether the MCS index indicator is based on the first MCS table or the second MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on a specific MCS table indicated by the MCS table indicator field. The specific conditions are as follows.
If at least one of the above conditions is not satisfied, the 1-bit MCS table indicator is not included in the downlink control information, and the terminal determines whether the MCS index indicator is based on the first MCS table or the second MCS table according to the MCS table-related configuration information received via higher-layer signaling. The terminal determines a modulation order and a target code rate of downlink data or uplink data using an index value indicated by the MCS index indicator based on a specific MCS table configured through the higher-layer signaling.
According to the ninth embodiment, the terminal determines whether the MCS index indicator in the downlink control information is based on the first MCS table or the second MCS table according to a CQI reporting time point and a valid time (operation 1110).
For example, if there is no resource configured for CQI index reporting based on the second CQI table, the terminal determines that an MCS index indicator field in a downlink control information format found in a downlink control channel is configured based on the first MCS table (operations 1120 and 1130). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table (operations 1130, 1150, and 1160).
According to another example, if there is a resource configured for CQI index reporting based on the second CQI table, the terminal determines that the MCS index indicator field in the downlink control information format, which is searched for in the downlink control channel only for a specific time period, is configured based on the second MCS table (operations 1120 and 1140). The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the second MCS table (operations 1140, 1150, and 1160). Except for the specific time period, the terminal determines that the MCS index indicator field in the downlink control information format found in the downlink control channel is configured based on the first MCS table. The terminal determines a modulation order and a target code rate of downlink data or uplink data using the index value indicated by the MCS index indicator based on the first MCS table. The specific time period includes a time period k starting from the time point (N) at which the CQI index reporting is performed based on the second CQI table, for example. In other words, the specific time period may be a period from N to (N+k). The units of N and k may be slots, symbols, or absolute times.
Referring to
Referring to
The embodiments described in the disclosure may not be applicable to UEs having reported the UE capability of URLLC non-supporting (or 10−5 target BLER non-supporting) to a base station. Alternatively, different embodiments described in the disclosure may be applicable to UEs having reported the UE capability of URLLC supporting (or 10−5 target BLER supporting) to the base station.
Meanwhile, the embodiments of the disclosure disclosed in the specification and drawings are merely to provide specific examples in order to easily explain the technical matters of the disclosure and to 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 modified examples based on the technical idea of the disclosure may be implemented. In addition, the above embodiments can be combined with each other and used, as necessary. For example, parts of the first embodiment to the ninth embodiment of the disclosure may be combined with each other to implement the base station and the terminal. In addition, although the above embodiments have been proposed based on the NR system, other modified examples based on the technical idea of the above embodiment may be implemented in other systems, such as an FDD or TDD LTE system.
In addition, the different embodiments described in the disclosure may be combined with each other. In addition, the scope of the disclosure is not limited to the examples described in the disclosure, and the examples are sufficiently applicable to a sufficiently opposing situation.
Further, although exemplary embodiments of the disclosure have been described and shown in the specification and the drawings by using particular terms, they have been used in a general sense merely 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. It will be apparent to those skilled in the art that, in addition to the embodiments disclosed herein, other variants may be achieved on the basis of the technical idea of the disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2018-0054223 | May 2018 | KR | national |
This application is a Continuation Application of U.S. patent application Ser. No. 17/825,688, which was filed in the U.S. Patent and Trademark Office on May 26, 2022, which is a Continuation Application of U.S. application Ser. No. 16/980,689, which was filed in the U.S. Patent and Trademark Office on Sep. 14, 2020, now U.S. Pat. No. 11,349,593, issued May 31, 2022, as a National Phase Entry of PCT International Application No. PCT/KR2019/005175, which was filed on Apr. 30, 2019, and claims priority to Korean Patent Application No. 10-2018-0054223, which was filed on May 11, 2018, the entire content of each of which is incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17825688 | May 2022 | US |
| Child | 18404313 | US | |
| Parent | 16980689 | Sep 2020 | US |
| Child | 17825688 | US |
