Patent Application
20240098714
The present disclosure relates to a method and a device for transmitting signals through a plurality of slots in a wireless 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” communication system or a “post LTE” system. The 5G communication system defined by 3GPP is called a “new radio (NR) system”. The 5G communication system is considered to be implemented in ultrahigh 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 in the ultrahigh frequency bands, beamforming, massive multiple-input multiple-output (massive MIMO), full dimensional
Multiple-input and multiple-output (MIMO), full dimensional multiple-input and multiple-output (FD-MIMO), array antenna, analog beam forming, and 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 networks, 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 (IT) 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 (cloud 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.
With the recent development of 5G communication systems, the need for a method of repeatedly transmitting an uplink to expand cell coverage in an ultra-high frequency (mmWave) band has emerged.
The disclosure proposes methods and devices for an effective signal processing method when the number of transport blocks and the number of slots or physical channels are not the same (hereinafter referred to as asymmetric transmission) in a communication system.
In various embodiments, methods and devices for transmitting a transport block through a plurality of slots or physical channels are proposed.
In various embodiments, a downlink control information (DCI) design for asymmetric transmission is proposed.
In various embodiments, a transport block size determination for asymmetric transmission is proposed.
In various embodiments, a code block segmentation design for asymmetric transmission is proposed.
In various embodiments, a code block cyclic redundancy check (CRC) design for asymmetric transmission is proposed.
In various embodiments, a transmission rate matching design for asymmetric transmission is proposed.
In various embodiments, an interleaving design for asymmetric transmission is proposed.
In various embodiments, a code block concatenation design for asymmetric transmission is proposed.
In various embodiments, a multiplexing design of data and control information is proposed.
In various embodiments, a scrambling design for asymmetric transmission is proposed.
In various embodiments, a method for combining some or all of the above tasks is proposed.
A method of a UE in a wireless communication system according to an embodiment of the disclosure for solving the above problems may include receiving transport block over multi-slot (TBoMS) configuration information including one transport block from a base station; receiving downlink control information for scheduling transmission of a physical uplink shared channel (PUSCH) from the base station; performing a physical layer signal processing procedure based on the TBoMS configuration information and downlink control information; and transmitting the PUSCH to the base station in a plurality of slots.
According to an embodiment, the downlink control information may include DCI format 0_0.
According to an embodiment, the TBoMS configuration information may include information on the number of slots for transmitting the one transport block, and the transport block size (TBS) related to the transport block may be determined based on the number of slots.
According to an embodiment, code block segmentation for the transport block may be performed in the physical layer signal processing procedure.
A method of a base station in a wireless communication system according to an embodiment of the disclosure may include transmitting transport block over multi-slot (TBoMS) configuration information including one transport block to a UE; transmitting downlink control information for scheduling transmission of a physical uplink shared channel (PUSCH) to the UE; and receiving the PUSCH transmitted based on a physical layer signal processing procedure performed based on the TBoMS configuration information and downlink control information from the UE in a plurality of slots.
A UE in a wireless communication system according to an embodiment of the disclosure may include a transceiver; and a controller configured to receive transport block over multi-slot (TBoMS) configuration information including one transport block from a base station, receive downlink control information for scheduling transmission of a physical uplink shared channel (PUSCH) from the base station, perform a physical layer signal processing procedure based on the TBoMS configuration information and downlink control information, and transmit the PUSCH to the base station in a plurality of slots.
A base station in a wireless communication system according to an embodiment of the disclosure may include a transceiver; and a controller configured to transmit transport block over multi-slot (TBoMS) configuration information including one transport block to a UE, transmit downlink control information for scheduling transmission of a physical uplink shared channel (PUSCH) to the UE, and receive the PUSCH transmitted based on a physical layer signal processing procedure performed based on the TBoMS configuration information and downlink control information from the UE in a plurality of slots.
The disclosure proposes a method and device for an effective signal processing method for asymmetric transmission.
Through the method of the disclosure, additional channel coding gain may be obtained, and coverage of an uplink channel may be improved.
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.
The contents of the disclosure may be applied to near field communication systems including WiFi employing asymmetrical transmission and mobile communication systems including LTE, NR, and 6 systems. Furthermore, based on determinations by those skilled in the art, the disclosure may also be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure. In describing embodiments of the disclosure below, 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. Furthermore, in describing the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.
In the following description, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In the disclosure, a “downlink (DL)” refers to a radio link via which a base station transmits a signal to a terminal, an “uplink (UL)” refers to a radio link via which a terminal transmits a signal to a base station, and a “sidelink (SL)” refers to a radio transmission link between a terminal and a terminal. Furthermore, in the following description, an NR system may be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types.
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.
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 in the embodiments of the disclosure, the term “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, “unit” does not always have a meaning limited to software or hardware. A “unit” may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, a “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” may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Furthermore, a “unit” in the embodiments may include one or more processors.
It should be appreciated that an embodiment of the disclosure and the terms used therein are not intended to limit the technological features set forth herein to a particular embodiment and include various changes, equivalents, or replacements for an embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, each of such phrases as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C,” may include any one of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.
Hereinafter, embodiments of the disclosure will be described in detail with accompanying drawings. Hereinafter, the method and device proposed in the embodiments of the disclosure will describe the embodiments of the disclosure as an example the PUSCH design, but may be applied to UL, DL, and SL channels of various systems applying asymmetric transmission, such as physical downlink shared channel (PDSCH) and physical sidelink shared channel (PSSCH). That is, the disclosure is not limited to each embodiment, and may be applied to a method for configuring frequency resources corresponding to other channels by using all or a combination of one or more embodiments proposed in the disclosure. Accordingly, the embodiments of the disclosure may be applied through some modifications within a range that does not significantly deviate from the scope of the disclosure by the judgment of a skilled person with technical knowledge.
Furthermore, in describing the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it is determined that the description may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.
A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE {long-term evolution or evolved universal terrestrial radio access (E-UTRA)}, LTE-Advanced (LTE-A), LTE-Pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), IEEE 802.17e, and the like, as well as typical voice-based services.
As a typical example of the broadband wireless communication system, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL) and employs a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). 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) (eNode 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.
Since a 5G communication system, which is a post-LTE communication system, must freely reflect various requirements of users, service providers, and the like, services satisfying various requirements must be supported. The services considered in the 5G communication system include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), ultra-reliability low-latency communication (URLLC), and the like.
eMBB aims at providing a data rate higher than that supported by existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink for a single base station. Furthermore, the 5G communication system must provide an increased user-perceived data rate to the UE, as well as the maximum data rate. In order to satisfy such requirements, transmission/reception technologies including a further enhanced multi-input multi-output (MIMO) transmission technique are required to be improved. In addition, the data rate required for the 5G communication system may be obtained using a frequency bandwidth more than 20 MHz in a frequency band of 3 to 6 GHz or 6 GHz or more, instead of transmitting signals using a transmission bandwidth up to 20 MHz in a band of 2 GHz used in LTE.
In addition, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. mMTC has requirements, such as support of connection of a large number of UEs in a cell, enhancement coverage of UEs, improved battery time, a reduction in the cost of a UE, and the like, in order to effectively provide the Internet of Things. Since the Internet of Things provides communication functions while being provided to various sensors and various devices, it must support a large number of UEs (e.g., 1,000,000 UEs/km2) in a cell. In addition, the UEs supporting mMTC may require wider coverage than those of other services provided by the 5G communication system because the UEs are likely to be located in a shadow area, such as a basement of a building, which is not covered by the cell due to the nature of the service. The UE supporting mMTC should be configured to be inexpensive, and requires a very long battery life-time such as 10 to 15 years because it is difficult to frequently replace the battery of the UE.
Lastly, URLLC, which is a cellular-based mission-critical wireless communication service, may be used for remote control for, for example, robots or machines, industrial automation, unmanned aerial vehicles, remote health care, emergency alert, and the like. Thus, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 ms, and also requires a packet error rate of 10-5 or less. Therefore, for the services supporting URLLC, a 5G system must provide a transmit time interval (TTI) shorter than those of other services, and also must assign a large number of resources in a frequency band in order to secure reliability of a communication link.
The above-described three services in the 5G communication system (hereinafter, may be interchangeably used with “5G system”), that is, eMBB, URLLC, and mMTC, may be multiplexed and transmitted in a single system. In order to satisfy different requirements of the respective services, different transmission/reception techniques and transmission/reception parameters may be used between the services.
Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the drawings.
In
In an example of
Next, a demodulation reference signal (DMRS), which is one of the reference signals in the 5G system, will be described in detail.
The DMRS may consist of a plurality of DMRS ports, and each port maintains orthogonality so as not to interfere with each other by using code division multiplexing (CDM) or frequency division multiplexing (FDM). However, the terms for the DMRS may be expressed in other terms depending on the user's intention and the purpose of using the reference signal. More specifically, the term DMRS is only presented as a specific example to easily explain the technical content of the disclosure and help understanding of the disclosure, and is not intended to limit the scope of the disclosure. That is, it is obvious to those of ordinary skill in the art that the technical idea of the disclosure may be implemented in reference signals as well.
In a 5G system, two DMRS patterns may be supported. Two DMRS patterns are specifically illustrated in
In the one-symbol pattern of 301 of
DMRS type 2 of 303 and 304 in
In the one-symbol pattern of 303 of
As described above, in the NR system, two different DMRS patterns (301, 302 or 303, 304 of
More specifically, the downlink DMRS configuration described above may be configured through RRC signaling as illustrated in Table 2 below.
In addition, the above-described uplink DMRS configuration may be configured through RRC signaling as illustrated in Table 3 below.
In performing a channel estimation for data decoding by using the above-described DMRS, the channel estimation may be performed within a corresponding bundling unit, precoding resource block group (PRG), by using PRB bundling linked to a system band in a frequency band. In addition, in a time unit, the channel estimation may be performed by assuming that only a DMRS received from one PUSCH has the same precoding.
Hereinafter, a method of time domain resource allocation for a data channel in a 5G communication system will be described. The base station may configure a table for time domain resource allocation information for a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH) to the UE through higher signaling (e.g., RRC signaling).
The base station may configure a table including maxNrofDL-Allocations=17 entries for the PDSCH, and may configure a table including maxNrofUL-Allocations=17 entries for the PUSCH. The time domain resource allocation information may include, for example, PDCCH-to-PDSCH slot timing (corresponds to the time interval in units of slots between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted as KO) or PDCCH-to-PUSCH slot timing (corresponds to the time interval in units of slots between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the location and length of a start symbol in which PDSCH or PUSCH is scheduled within a slot, PDSCH or PUSCH mapping type, and the like. For example, time domain resource allocation information for PDSCH may be configured to the UE through an RRC signal as illustrated in Table 4 below.
In addition, for example, time domain resource allocation information for PUSCH may be configured to the UE through an RRC signal as illustrated in Table 5 below.
The base station may transmit one of the table entries for the time domain resource allocation information to the UE through L1 signaling (e.g., downlink control information (DCI)) (for example, it may be indicated by the ‘time domain resource allocation’ field in DCI). The UE may obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.
In the following, transmission of an uplink data channel (physical uplink shared channel (PUSCH)) in a 5G system will be described in detail. The PUSCH transmission may be dynamically scheduled by a UL grant in DCI or may be operated by configured grant Type 1 or Type 2. The dynamic scheduling for PUSCH transmission, for example, may be indicated by DCI format 0_0 or 0_1.
The grant Type 1 PUSCH transmission may be configured semi-statically through reception of configuredGrantConfig including the rrc-ConfiguredUplinkGrant of Table 6 through higher signaling without receiving UL grant in DCI. The configured grant Type 2 PUSCH transmission may be scheduled semi-continuously by UL grant in DCI after reception of configuredGrantConfig that does not include the rrc-ConfiguredUplinkGrant of Table 6 through higher signaling. When the PUSCH transmission is operated by a configured grant, parameters applied to the PUSCH transmission may be applied through configuredGrantConfig that is the higher signaling of Table 6 except for specific parameters (e.g., dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, scaling of UCI-OnPUSCH, and the like) provided by pusch-Config, which is the higher signaling, of [Table 7]. For example, if the UE is provided with the transformPrecoder in configuredGrantConfig, which is the higher signaling of Table 6, the UE may apply tp-pi2BPSK in pusch-Config of Table 7 to PUSCH transmission operated by the configured grant.
Next, a PUSCH transmission method will be described. The DMRS antenna port for PUSCH transmission may be the same as the antenna port for SRS transmission. The PUSCH transmission may follow a codebook-based transmission method and a non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of Table 7, which is higher signaling, is ‘codebook’ or ‘nonCodebook’. As described above, the PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1 and may be semi-statically configured by the configured grant.
If the UE has received an instruction of scheduling for the PUSCH transmission through DCI format 0_0, the UE may perform beam configuration for PUSCH transmission by using a pucch-spatialRelationInfoID corresponding to the UE-specific (dedicated) PUCCH resource having the lowest ID within the uplink bandwidth part (BWP) activated in the serving cell. In this case, the PUSCH transmission may be performed based on a single antenna port. The UE may not expect scheduling for PUSCH transmission through DCI format 0_0 within the BWP in which the PUCCH resource including the pucch-spatialRelationInfo is not configured. If the UE has not received configured txConfig in pusch-Config of Table 7, the UE may not expect to be scheduled with DCI format 0_1.
Next, codebook-based PUSCH transmission will be described. The codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, and may operate semi-statically by a configured grant. When the codebook-based PUSCH is dynamically scheduled by DCI format 0_1 or is configured semi-statically by the configured grant, the UE may determine a precoder for PUSCH transmission based on SRS resource indicator (SRI), the transmission precoding matrix indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).
In this case, the SRI may be given through a field SRS resource indicator in the DCI or may be configured through srs-ResourceIndicator which is higher signaling. When transmitting the codebook-based PUSCH, the UE may receive at least one configured SRS resource and, as an example, up to two configured SRS resources. When the UE is provided with an SRI through DCI, the SRS resource indicated by the corresponding SRI may refer to an SRS resource corresponding to the SRI among SRS resources transmitted before the PDCCH including the corresponding SRI. In addition, TPMI and transmission rank may be given through field precoding information and number of layers in DCI, or may be configured through precodingAndNumberOfLayers, which is a higher signaling. TPMI may be used to indicate the precoder applied to PUSCH transmission.
The precoder to be used for PUSCH transmission may be selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in SRS-Config, which is a higher signaling. In codebook-based PUSCH transmission, the UE may determine the codebook subset based on the TPMI and the codebookSubset within the push-Config, which is the higher signaling. In this case, the codebookSubset in push-Config, which is the higher signaling, may be configured to one of ‘fullyAndPartialAndNonCoherent’, ‘partialAndNonCoherent’, or ‘nonCoherent’ based on UE capability reported by the UE to the base station.
If the UE reports ‘partialAndNonCoherent’ with UE capability, the UE may not expect the value of the higher signaling codebookSubset to be configured to ‘fullyAndPartialAndNonCoherent’. In addition, if the UE reports ‘nonCoherent’ with UE capability, the UE may not expect the value of the higher signaling codebookSubset to be configured to ‘fullyAndPartialAndNonCoherent’ or ‘partialAndNonCoherent’. When nrofSRS-Ports in SRS-ResourceSet, which is the higher signaling, indicates two SRS antenna ports, the UE may not expect the value of codebookSubset, which is the higher signaling, to be configured to ‘partialAndNonCoherent’.
The UE may receive one SRS resource set configured in which the value of the usage in the SRS-resource set, which is the higher signaling, is configured to ‘codebook’, and one SRS resource within the SRS resource set may be indicated through the SRI. If multiple SRS resources are configured within the SRS resource set in which the usage value in the SRS-resource set, which is the higher signaling, is configured to ‘codebook’, the UE may expect that the value of nrofSRS-Ports in the SRS-resource, which is the higher signaling, is configured to be the same for all SRS resources.
The UE may transmit one or a plurality of SRS resources included in the SRS resource set in which the value of usage is configured to ‘codebook’ to the base station according to upper level signaling, and the base station may select one of the SRS resources transmitted by the UE and instruct the UE to perform PUSCH transmission by using the transmission beam information of the corresponding SRS resource. In this case, in the codebook-based PUSCH transmission, the SRI is used as information on selecting an index of one SRS resource and may be included in the DCI. In addition, the base station may include information indicating the TPMI and rank to be used by the UE for PUSCH transmission in the DCI for transmission. The UE may perform PUSCH transmission by applying the TPMI indicated based on the transmission beam of the corresponding SRS resource and the precoder indicated by the rank by using the SRS resource indicated by the SRI.
Next, non-codebook-based PUSCH transmission will be described. The non-codebook-based PUSCH transmission may be dynamically scheduled through DCI format 0_0 or 0_1, or may operate semi-statically by a configured grant. When at least one SRS resource is configured in the SRS resource set in which the value of usage in the SRS-ResourceSet, which is the higher signaling, is configured to ‘nonCodebook’, the UE may receive the non-codebook-based PUSCH transmission scheduled through DCI format 0_1.
For the SRS resource set in which the value of usage in the SRS-ResourceSet, which is the higher signaling, is configured to ‘nonCodebook’, the UE may receive a configured non-zero power (NZP) CSI-RS resource related to one SRS resource set. The UE may perform calculation on the precoder for SRS transmission through measurement of the configured NZP CSI-RS resource related to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource related to the SRS resource set and the first symbol of the aperiodic SRS transmission in the UE is less than specific symbols (e.g., 42 symbols), the UE may not expect information on the precoder for SRS transmission to be updated.
When the value of resourceType in the SRS-ResourceSet, which is the higher signaling, is configured to ‘aperiodic’, the NZP CSI-RS related to the SRS-ResourceSet may be indicated by the SRS request, which is a field in DCI format 0_1 or 1_1. In this case, when the NZP CSI-RS related to the SRS-ResourceSet is an aperiodic NZP CSI-RS resource, and when the value of the field SRS request in DCI format 0_1 or 1_1 is not ‘00’, it may indicate that the NZP CSI-RS related to the SRS-ResourceSet exists. In this case, the corresponding DCI should not indicate cross carrier or cross BWP scheduling. In addition, when the value of the SRS request indicates the presence of the NZP CSI-RS, the corresponding NZP CSI-RS may be located in the slot in which the PDCCH including the SRS request field is transmitted. In this case, the TCI states configured in the scheduled subcarrier may not be configured to QCL-TypeD.
If a periodic or semi-persistent SRS resource set is configured, the NZP CSI-RS related to the SRS resource set may be indicated through the associatedCSI-RS in the SRS-ResourceSet, which is the higher signaling. For non-codebook-based transmission, the UE may not expect that spatialRelationInfo, which is the higher signaling for SRS resource, and associatedCSI-RS in SRS-ResourceSet, which is the higher signaling, are configured together.
When a plurality of SRS resources are configured, the UE may determine the precoder to be applied to PUSCH transmission and the transmission rank based on the SRI indicated by the base station. In this case, the SRI may be indicated through a field SRS resource indicator in the DCI or may be configured through srs-ResourceIndicator, which is the higher signaling. Like the above-described codebook-based PUSCH transmission, when the UE receives SRI through DCI, the SRS resource indicated by the corresponding SRI may refer to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the corresponding SRI. The UE may use one or a plurality of SRS resources for SRS transmission, and the maximum number of SRS resources capable of simultaneous transmission in the same symbol in one SRS resource set may be determined by the UE capability reported by the UE to the base station. In this case, the SRS resources simultaneously transmitted by the UE may occupy the same RB. The UE may configure one SRS port for each SRS resource. Only one SRS resource set in which the value of usage in the SRS-ResourceSet, which is the higher signaling, may be configured to ‘nonCodebook’, and up to four SRS resources for non-codebook-based PUSCH transmission may be configured.
The base station may transmit one NZP-CSI-RS related to the SRS resource set to the UE, and the UE may calculate a precoder to be used when transmitting one or a plurality of SRS resources in the corresponding SRS resource set based on the result measured when receiving the corresponding NZP-CSI-RS. The UE may apply the calculated precoder when transmitting one or a plurality of SRS resources in the SRS resource set in which usage is configured to ‘nonCodebook’ to the base station, and the base station may select one or a plurality of SRS resources among received one or a plurality of SRS resources. In this case, in non-codebook-based PUSCH transmission, the SRI indicates an index capable of representing one or a combination of a plurality of SRS resources, and the SRI may be included in the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station may be the number of transmission layers of the PUSCH, and the UE may transmit the PUSCH by applying the precoder applied to the SRS resource transmission to each layer.
Next, repeated PUSCH transmissions will be described. When the UE has received scheduling for PUSCH transmission with DCI format 0_1 in the PDCCH including the CRC scrambled with cell radio-network temporary identifier (C-RNTI), modulation coding scheme (MCS)-C-RNTI or configured scheduling radio-network temporary identifier (CS-RNTI), if the UE is configured with higher layer signaling push-AggregationFactor, the same symbol allocation is applied in consecutive slots equal to the push-AggregationFactor, and PUSCH transmission may be limited to single-rank transmission. For example, the UE must repeat the same transport block (TB) in consecutive slots equal to the pushch-AggregationFactor and apply the same symbol allocation for each slot. Table 8 illustrates a redundancy version applied to repeated PUSCH transmissions for each slot. If the UE has received scheduling for repeated PUSCH transmission in a plurality of slots with DCI format 0_1, and at least one symbol among slots in which repeated PUSCH transmissions are performed is indicated as a downlink symbol according to information of higher layer signaling tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE may not perform PUSCH transmission in the slot where the corresponding symbol is located.
Hereinafter, repetitive transmission of an uplink data channel (PUSCH) in a 5G system will be described in detail. The 5G system supports two types, PUSCH repeated transmission type A and PUSCH repeated transmission type B, as repeated transmission methods of an uplink data channel. The UE may be configured with either PUSCH repetitive transmission type A or B through higher layer signaling.
Regarding PUSCH repetitive transmission type A:
and the symbol where nominal repetition starts in the start slot may be given by mod (S+n·L,Nsymbslot). The slot where the nth nominal repetition ends may be given by
and the symbol where nominal repetition ends in the last slot may be given by mod(S+(n+1)·L,Nsymbslot). Here, n=0, . . . numberofrepetitions-1, S may represent the start symbol of the configured uplink data channel, and L may represent the symbol length of the configured uplink data channel. Ks may indicate a slot in which PUSCH transmission starts and Nsymbslot may indicate the number of symbols per slot.
Accordingly, a total of repK_actual=4 PUSCHs may be actually transmitted. In this case, when the repK-RV is configured to 0-2-3-1, the RV of the PUSCH of the first resource 504 actually transmitted is 0, the RV of the PUSCH of the second resource 505 actually transmitted is 2, the RV of the PUSCH of the third resource 506 actually transmitted is 3, and the RV of the PUSCH of the fourth resource 507 actually transmitted is 1. In this case, only PUSCHs with RV 0 and RV 3 may be decoded by themselves, and in the case of the first resource 504 and the third resource 506, because the PUSCH is transmitted only in 3 symbols much less than actually configured symbol length (14 symbols), the bit lengths 508 and 510 to be rate-matched are less than the bit lengths 509 and 511 calculated by the configuration.
In the following, a method of calculating a transport block size (TBS) in a 5G system will be described in detail.
N′RE, which is the number of REs allocated to PUSCH mapping in one PRB in the allocated resource is calculated. N′RE may be calculated as NscRB×Nsymbsh−NohPRB. Here, NscRB may be 12, and Nsymbsh may indicate the number of OFDM symbols allocated to the PUSCH. NDMRSPRB is the number of REs in one PRB occupied by DMRSs of the same CDM group. NohPRB is the number of REs occupied by overhead in one PRB configured by higher signaling, and may be configured to one of 0, 6, 12, and 18. Then, the total number of REs NRE allocated to the PUSCH may be calculated. NRE is calculated as min(166,N′RE)×nPRB, and nPRB represents the number of PRB s allocated to the UE. The number of temporary information bits Ninfo may be calculated as NRE×R×Qm×v. Here, R is a code rate and Qm is a modulation order, and information on this value may be transmitted by using the MCS bit field of DCI and a prearranged table. In addition, v is the number of assigned layers. If Ninfo ≤3824, TBS may be calculated through the following process. Otherwise, TBS may be calculated through step 4. N′info may be calculated through the formula of
and n=max(3, └log2(Ninfo)┘−6). TBS may be determined to be the closest value to N′info among the values not less than N′info in Table 9 below.
If Ninfo>3824, Ninfo may be calculated through the formulas of
and n=└log2(Ninfo−24)┘−5. TBS may be determined through the N′info value and the following pseudo-code 1. Below, C corresponds to the number of code blocks (CB) included in one TB.
Pseudo-code 1 start
In order to improve the coverage of a transport channel in a wireless communication system, a transmission technology based on transport block processing over multi-slot (TBoMS), in which one transport block (TB) is mapped to a plurality of slots or a plurality of physical channels (e.g., PUSCH) and transmitted, is being discussed.
Referring to
In the past, because one TB was mapped to one slot or one physical channel and transmitted, when the number of TBs and the number of transport slots (or the number of physical channels) to which the TBs are mapped differ, such as in TBoMS, a signal processing procedure in the physical layer needs to be newly designed. Hereinafter, in the disclosure, the signal processing technology for the case where the number of TBs and the number of slots (or the number of physical channels) for transmitting the corresponding TB is different is referred to as ‘asymmetric signal processing’, but the name is for illustrative purposes only and does not limit the scope of the disclosure. The disclosure proposes procedures in the overall physical layer including DCI format design, TBS determination, code block (CB) division, rate matching, interleaving, CB concatenation, multiplexing, and scrambling for such asymmetric signal processing. Hereinafter, some embodiments will be described based on a signal processing procedure in the physical layer for data transmission for description, but the corresponding physical layer signal processing procedure may also be applied for data reception.
Hereinafter, the disclosure will be described based on the PUSCH of the NR system, but TBoMS in which one TB is transmitted through a plurality of slots will be described as an example. However, this is for illustrative purposes only and does not limit the scope of the disclosure and may be applied for any asymmetric signal processing. In addition, in some descriptions of the disclosure below, TBoMS-based PUSCH transmission is described as an example, but this is only for example and does not limit the scope of the disclosure, and it may be applied for any physical channel transmission including PUSCH/PDSCH/PSSCH transmission through predefined/configured or signaling between a base station and a UE. In addition, in some descriptions of the disclosure below, slots and PUSCHs will be used interchangeably, but it may be understood that a slot is replaced with a PUSCH or a PUSCH is replaced with a slot on the premise that one PUSCH is transmitted in one slot. However, the disclosure may be equally applied even when a plurality of PUSCHs are transmitted in one slot or one PUSCH is transmitted over a plurality of slots. In this case, one slot should naturally be understood as one PUSCH. In some examples below, although the operation of a UE or a base station has been described based on the operation of the UE or base station, the base station (or other UE) or the UE may also perform a corresponding operation to support the operation of the corresponding UE or base station. Hereinafter, each embodiment and signal processing procedure of the disclosure may be applied independently or in combination with one or more of them.
A physical layer signal processing for TBoMS described in the disclosure may be performed when TBoMS is configured to the UE through TBoMS configuration information. The TBoMS configuration information may be configured through any signaling including RRC signaling, system information, MAC or DCI, and may include any information used to perform the physical layer signal processing for TBoMS described below. For example, TBoMS configuration information may include information on the number of slots to which one TB is mapped in TBoMS.
For example, the TBoMS configuration may be a detailed item of PUSCH configuration, and each PUSCH configuration may be a detailed item of BWP configuration. Accordingly, when one cell operates a plurality of BWPs, the TBoMS method may operate only in some BWPs of the cell.
In addition, within one BWP, if TBoMS configuration is transmitted based on system information, the TBoMS configuration may be applied to PUSCH in the initial access process, and if transmitted based on dedicated RRC signaling thereafter, the TBoMS configuration may be applied to PUSCH transmission in RRC connected state. If there is no transmission based on system information and transmission is performed based on dedicated RRC signaling, the TBoMS configuration may be applied only to PUSCH transmission in an RRC connected state.
In addition, the number of REs appearing in the following description is a value corresponding to the number of RBs and the number of time resources (number of OFDM symbols) used for PUSCH transmission, and the number of REs may be replaced with the number of RB s and time resources (number of OFDM symbols) used for PUSCH transmission in the following operation based on the number of Res.
A DCI format design method for TBoMS according to an embodiment of the disclosure is disclosed.
According to an embodiment, an arbitrary DCI format may be used for TBoMS. However, because it is not desirable to transmit a lot of data together to obtain a coding gain, the UE and the base station may assume that the remaining TBs except for the first TB are always deactivated for a DCI format (e.g., DCI format 0_1 or 1_1, etc.) supporting a plurality of TBs when TBoMS is configured. For a DCI format supporting multiple TBs, the UE may not expect DCI reception indicating activation of the remaining TB s except for the first TB, or if DCI indicating activation of the remaining TB s is received, the UE may not perform PDSCH/PUSCH transmission scheduled by the corresponding DCI or may not perform PDSCH/PUSCH transmissions corresponding to the remaining TBs except for the first one.
On the other hand, when an arbitrary DCI format is allowed, the number of bits to be received by the UE increases for the DCI format supporting a plurality of TBs, and physical channel resources may be wasted and the burden of signal processing of the UE may increase. Accordingly, in order to further improve performance in asymmetric signal processing such as TBoMS, only a DCI format (e.g., DCI format 0_0 or 1_0) supporting a maximum of one TB may be used.
Referring to
In an embodiment, when the TBoMS is configured, the UE may monitor a search space for monitoring a DCI format (e.g., DCI format 0_0 or 1_0) supporting only one TB of the configured search space, and may not monitor a search space for monitoring a DCI format (e.g., DCI format 0_1 or 1_1) supporting a plurality of TBs. Accordingly, the UE may monitor only DCI format 0_0 or 1_0 and perform TBoMS-based PDSCH/PUSCH/PSSCH transmission and reception based on this.
In an embodiment, when TBoMS is configured, the base station and the UE may assume that only a search space for monitoring DCI format 0_0 or 1_0 is configured. That is, when TBoMS is configured, the base station and the UE may not expect that a search space for monitoring other DCI formats other than DCI format 0_0 or 1_0 is configured. Accordingly, the UE may monitor only DCI format 0_0 or 1_0 based on the configured search space and perform TBoMS-based PDSCH/PUSCH/PSSCH transmission/reception based on this. On the other hand, according to another embodiment, a DCI format for TBoMS or a search space for monitoring the DCI format for TBoMS may be configured in the UE through TBoMS configuration information. When the TBoMS configuration information indicates a specific DCI format, the UE may monitor only the search space for the DCI format indicated through the TBoMS configuration information among the search spaces configured for the UE. Alternatively, when the TBoMS configuration information includes information on the search space for the specific DCI format, the UE may monitor the search space included in the TBoMS configuration information. In this embodiment, the information included in the TBoMS configuration information may include DCI format 0_0 or 1_0, but is not necessarily limited thereto.
A UE identifier for DCI format for TBoMS according to an embodiment of the disclosure is disclosed.
In an embodiment, the DCI format for TBoMS may include a CRC scrambled with a specific radio network temporary identifier (RNTI). For example, in the case of a DCI format (e.g., DCI format 0_0) for scheduling a PUSCH, a CRC scrambled with C-RNTI (cell RNTI) or TC-RNTI (temporary C-RNTI) may be included. In addition, in the case of a DCI format (e.g., DCI format 1_0) for scheduling a PDSCH, a CRC scrambled with C-RNTI, TC-RNTI, paging RNTI (P-RNTI), random access RNTI (RA-RNTI), or system information RNTI (SI-RNTI) may be included.
Here, the TC-RNTI may be used for DCI scheduling Msg3 PUSCH transmission used in the random access procedure. In this case, the UE and the base station may operate as follows, depending on whether the random access procedure related to the TC-RNTI is an initial access procedure or not.
In the case of initial connection, TBoMS operation according to DCI reception including a CRC scrambled with TC-RNTI may be performed based on TBoMS configuration information included in RACH-config common included in SIB 1. In cases other than initial access, TBoMS operation according to DCI reception including a CRC scrambled with TC-RNTI may be performed based on TBoMS configuration information configured through Dedicated RRC. In this case, TBoMS configuration information configured through Dedicated RRC may be included, for example, in PUSCH-config or RACH-config dedicated. According to an embodiment, when Msg 3 is transmitted in a plurality of slots, a transmission operation of a corresponding preamble (Msg 1) may also be performed through a plurality of slots or RACH Occasion. Depending on the configuration, when information on the number of transmissions of the preamble (Msg 1) is separately defined or when the corresponding Msg 3 is transmitted in a plurality of slots, a plurality of preambles (Msg 1) may also be implicitly transmitted.
Referring to
In the following description, it is assumed that one DCI is related to transmission of a plurality of PUSCHs. However, even when a plurality of DCIs schedule one TB for a plurality of PUSCH transmissions, the following content may be equally applied. On the other hand, in a system for obtaining coding gain and channel coverage improvement, it is advantageous to increase transmission power through a small band and a large number of time resources without requiring a high MCS. Accordingly, in the case of TBoMS, the bit size of a modulation and coding scheme (MCS) for indicating an MCS and a frequency domain resource allocation (FDRA) for indicating a frequency resource among information indicated through DCI may be reduced. For example, when using only the lower N MCSs among all MCSs indicated by the existing 5-bit MCS field for the MCS field, only ┌log2N┐-sized bits may be used instead of the existing 5 bits. N may be determined based on TBoMS configuration information, the TBoMS configuration information may include information directly indicating the number N of MCSs to be used as information for determining N, or information indicating an MCS index, and it may be assumed that the base station and the UE use the MCS corresponding to the index below the indicated index. In addition, for example, for the FDRA field, when the maximum number of PRBs for TBoMS is configured through TBoMS configuration information, because the RIV value for indicating the number of PRBs exceeding the maximum number of PRB s is not required, the number of bits for FDRA may be reduced accordingly.
Regarding hybrid automatic repeat request acknowledgement (HARQ-ACK) operation, in the case of PUSCH, when even one of the plurality of PUSCHs is acknowledgement (ACK), it may be determined as ACK (retransmission DCIs for the plurality of PUSCHs corresponding to the DCI are not transmitted), and when all PUSCHs are negative acknowledgement (NACK), NACK may be transmitted (retransmission DCIs for the plurality of PUSCHs corresponding to the DCI are transmitted). In contrast, when even one of the plurality of PUSCHs is NACK, NACK may be transmitted (retransmission DCIs for the plurality of PUSCHs corresponding to the DCI are transmitted), and when all PUSCHs are ACKs, ACKs may be determined (retransmission DCIs for a plurality of PUSCHs corresponding to DCIs are not transmitted). The former is suitable when ACK/NACK of the entire TB may be determined through one PUSCH, and the latter is suitable when ACK/NACK for the entire TB may be determined only after receiving all PUSCHs. A detailed description of this may be understood through the following technical description (procedures such as code block division and transmission rate matching).
When applied to PDSCH for HARQ-ACK operation, if the UE receives configuration of the dynamic HARQ-ACK codebook, the UE may determine the HARQ-ACK feedback bit or HARQ-ACK codebook size to be transmitted by the UE based on downlink assignment indicator (DAI) information included in the DCI in a slot in which HARQ-ACK information determined according to K0, which is the slot information to which the PDSCH is mapped, and the HARQ-ACK feedback timing information K1 value for the PDSCH are transmitted. If a plurality of PDSCHs are scheduled through one DCI indicating DAI according to an embodiment of the disclosure, a method of determining the DAI value or a method of determining the HARQ-ACK feedback bit or HARQ-ACK codebook size based on the DAI value may be required.
In an embodiment, the DAI may be sequentially increased for each DCI in consideration of the cell as before, and the UE may perform one HARQ-ACK feedback for a plurality of PDSCHs. The one HARQ-ACK feedback is based on the decoding result of all
PDSCHs, and for example, if any one of a plurality of PDSCHs is ACK, ACK may be transmitted, and if all PDSCHs are NACK, NACK may be transmitted. Alternatively, if even one of the plurality of PDSCHs is NACK, NACK may be transmitted, and if all PDSCHs are ACK, ACK may be transmitted. HARQ-ACK transmission timing may be determined based on the reception time of the last PDSCH (e.g., the last symbol of the last PDSCH). When code block group (CBG)-based PDSCH transmission is configured, HARQ-ACK feedback may be performed for each CBG.
In an embodiment, the DAI may be sequentially increased for each DCI in consideration of the cell as before, and the UE may perform HARQ-ACK feedback for each of a plurality of PDSCHs. In this case, the same HARQ-ACK may be fed back for a plurality of PDSCHs scheduled by DCI indicating one DAI, and the same HARQ-ACK feedback may be fed back as much as the number of PDSCHs (or slots) scheduled through the corresponding DCI. This may be effective when TB s transmitted on a plurality of PDSCHs are the same, but multiplexed control information is different for each PDSCH or is included only in some PDSCHs.
In an embodiment, the DAI may be configured to sequentially increase in consideration of the number of PDSCHs related to each DCI together with the cell, and based on the corresponding DAI value, the UE may perform HARQ-ACK feedback for each of a plurality of PDSCHs.
DCI format 0_0 according to the above description may be described as follows.
If DCI format 0_0 is applied to scheduling of a plurality of PUSCHs, each field below will be used for each PUSCH transmission.
In particular, in the case of the redundancy version, the interpretation method will be explained in detail in the transmission rate matching part. In addition, it is configured that one same HARQ process number is applied to all PUSCHs. The transmit power control (TPC) command configures that the same value is applied to all PUSCHs. However, if joint channel estimation is not applied and there is a TPC command transmitted at an applicable point after the corresponding TPC command (TPC command transmitted through DCI format 2_2, etc.), this will be applied. Finally, in the case of TDRA, the existing 4 bits are used as they are, but based on the TDRA list stored in the UE or base station, Dedicated RRC or SIB configuration, etc., information on the number of PUSCHs may be additionally included in addition to the information of the existing TDRA.
The following description relates to bit size determination, and a specific interpretation method will follow the above-mentioned.
A method for determining a transport block size (TBS) for TBoMS according to an embodiment of the disclosure is disclosed.
In an embodiment, TBS may be determined based on the total number of resource elements (REs) allocated to PUSCHs transmitted in a plurality of slots.
In an embodiment, if the same number of REs are allocated to PUSCHs transmitted in all slots related to one TB transmission, TBS may be determined based on the same number of REs. That is, TBS may be determined based on the number of REs allocated to the PUSCH transmitted in one slot.
In an embodiment, if REs are independently allocated to PUSCHs transmitted in each slot associated with one TB transmission (i.e., allowing different numbers of REs to be allocated), TBS may be determined based on any one of the following methods.
1. TBS may be determined based on the number of REs allocated to the PUSCH of a specific predefined slot among a plurality of slots. For example, TBS may be determined based on the number of REs allocated to the PUSCH of the first or last slot among a plurality of slots.
2. A slot to be used for TBS calculation may be directly configured through RRC or MAC, or a condition for determining a slot to be used for TBS calculation may be configured. TBS may be determined based on the configured slot or a slot determined according to conditions.
3. TBS may be determined based on the largest or smallest number of REs allocated to the PUSCH of each slot.
4. TBS may be determined based on the average of the number of REs allocated to the PUSCH of all slots.
The TBS determination method based on the above embodiments may be predefined/configured or configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
According to an embodiment, the TBS determined according to the above embodiments may be determined to be equal to or less than the maximum TBS for TBoMS transmission. For example, when designing DCI, the base station may adjust or limit parameters used in the TBS calculation process so that the TBS calculated according to the above embodiments is equal to or less than the maximum TBS for TBoMS. As such, a UE receiving the DCI designed such that the TBS is calculated to be equal to or less than the maximum TBS may calculate the TBS based on the received DCI. As another example, the maximum TBS may be configured through signaling between the base station and the UE. For example, the maximum TBS may be included in TBoMS configuration information and configured to the UE. If the TBS calculated by the UE is greater than the configured maximum TBS, the UE may not perform PUSCH transmission for the corresponding TB, or may perform PUSCH transmission by using the configured maximum TBS instead of the calculated TBS. Of course, the above two examples may be implemented independently of each other or in combination. The maximum TBS for the TBoMS may be configured to one value independent of a modulation order, or the maximum TBS corresponding to each modulation order may be configured. When the maximum TBS corresponding to each modulation order is configured, the base station and the UE may perform the above-described operation in consideration of the modulation order determined through the MCS field. When the TBS is determined as described above, a CRC bit may be attached to the TB having the determined TBS. The CRC bit attached to the TB may be 24 bits.
A code block (CB) division method for TBoMS according to an embodiment of the disclosure is disclosed.
In an embodiment, CB segmentation may not be supported in case of TBoMS-based transmission. That is, considering high coding gain in TBoMS, it is preferable to transmit a small-sized TB, and in this case, CB splitting may not occur.
When the CB segmentation is not supported, the base station may design and transmit the DCI to the UE so that the TBS is calculated to be equal to or less than the size required for the CB segmentation. When TBoMS is configured (i.e., when TBoMS configuration information is received), the UE may not expect DCI reception that causes TBS to exceed the size required for the CB segmentation. If received, the UE may not perform transmission of the physical channel scheduled by the corresponding DCI.
Alternatively, the base station or the UE may configure the maximum TBS size for the TBoMS described in the TBS determination method above to be equal to or less than the TBS required for the CB segmentation.
Alternatively, if the calculated TBS exceeds the TBS for which CB segmentation is required, the base station or the UE may scale the calculated TBS to be equal to or less than the TBS for which CB segmentation is required.
Alternatively, the base station or the UE may not perform the CB segmentation when TBoMS is configured, regardless of the calculated TBS and the TBS for which CB segmentation is required.
In one embodiment, the CB segmentation may be supported for TBoMS-based transmission.
When the segmentation is supported, the base station and the UE may determine the number of CBs and the size of each CB with reference to TS 38.212 Section 5.2 of Release 15 according to the size of the TBS, and for example, the number of CBs and the size of each CB may be determined based on Table 10 below.
Alternatively, the number of divided CBs may be equal to the number of slots (or physical channels) for TBoMS or may be determined to be a multiple of the number of slots (or PUSCHs). Here, the number of slots for TBoMS may be configured through TBoMS configuration information.
If the number of CBs determined based on the conventional method described above is equal to or a multiple of the number of slots for TBoMS, the same number of CBs may be mapped to and transmitted to each physical channel (e.g., PUSCH). For example, when the number of slots for TBoMS is configured to 4 in PUSCH transmission and the determined number of CBs is 4, one CB may be mapped to each PUSCH of each slot and transmitted.
In contrast, when the number of CB s determined based on the conventional method is not the same as or is not multiple of the number of slots for TboMS, the CB may be re-divided into the same number or multiple.
If the determined number of CBs is smaller than the number of slots for TBoMS, the CB may be re-divided into smaller CBs to match the number of corresponding slots. For example, when the number of slots for TBoMS in PUSCH transmission is configured to 4 and the determined number of CBs is 2, the TB may be re-divided into 4 CBs having smaller sizes. The four re-segmented CBs may be transmitted after being mapped one by one to the PUSCH of each slot.
If the number of CBs is greater than the number of slots for TBoMS, the CB may be re-divided into smaller or larger CBs to match the number of slots or to be a multiple of the number of slots. For example, when the number of slots for TBoMS in PUSCH transmission is configured to 4 and the determined number of CBs is 6, the TB may be re-divided into 4 CB s having a larger size. The four re-segmented CBs may be transmitted after being mapped one by one to the PUSCH of each slot. As another example, the TB may be re-divided into 8 CBs having a smaller size. The eight re-segmented CBs may be transmitted after being mapped to two PUSCHs of each slot.
Whether CB segmentation is supported for TBoMS-based transport or when supported or not supported, which methods are used respectively may be predefined/configured or configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
A CB CRC attachment method for TBoMS according to an embodiment of the disclosure is disclosed.
If the CB segmentation is not supported, a separate CB CRC attachment operation may not be required because the CRC is attached to the TB.
If CB segmentation is supported, the CRC attachment operation for the divided CB may be performed according to the method below.
In an embodiment, a 24-bit CRC may be attached to each CB as in the prior art.
In another embodiment, a smaller size CRC bit may be used in the case of TBoMS instead of the conventional 24 bits to minimize redundancy for high coding gain. For example, a 16-bit CRC may be attached to each CB, or a CRC of an arbitrary size newly defined in relation to TBoMS may be attached to each CB. This embodiment may also include a case in which a 0-bit CRC is used, that is, a separate CRC is not attached even if the CB segmentation is supported.
In the case of supporting transmission based on a code block group (CBG), the CRC may be attached in units of CBGs instead of each CB.
In the disclosure, whether the CB segmentation is supported, or the CB CRC attachment method for the case where it is supported, may be predefined/configured or configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
As described above, the channel coding may be performed on a CB to which a CRC is attached (or, if CB segmentation is not supported, a TB to which a CRC is attached). The Channel coding may be performed based on at least one of LDPC codes, polar codes, and simplex codes.
A rate matching or bit selection method for TBoMS according to an embodiment of the disclosure is disclosed. An embodiment described below may be applied to a rate matching operation for channel coding based on an LDPC code, a polar code, or a simplex code.
In an embodiment, one rate matching may be performed over the entire number of slots configuration for TBoMS. That is, for bits output through channel coding, rate matching or bit selection may be performed based on the number of REs of all PUSCHs transmitted in slots for TBoMS and the RV indicated by DCI. In this case, bits corresponding to the number of REs of each PUSCH will be sequentially allocated to each PUSCH. This has the same effect as sequentially applying RV to each PUSCH. However, as a method for determining the starting time point of bits allocated to each PUSCH, a method in which the next bit of the bit allocated to the previous PUSCH among all selected bits becomes the starting time point of the bit allocated to the current PUSCH may be applied, rather than the method described in the existing standard.
In an embodiment, rate matching or bit selection may be performed for each slot according to the number configured for TBoMS.
In this case, if the PDSCH/PUSCH transmitted in all slots has the same number of REs and the same RV, rate matching or bit selection may be substantially performed only once, and the result of the one-time execution may be equally used for PDSCH/PUSCH transmission in each slot. In this case, for all PDSCHs/PUSCHs, bits according to the same RV may be determined to have the same bit size in the channel coding result.
Alternatively, when PDSCH/PUSCH transmitted in all slots have the same number of REs but have respective RVs, rate matching or bit selection may be performed for each RV. In this case, for each PDSCH/PUSCH, bits corresponding to each RV in the channel coding result may be determined to have the same bit size. In this case, assuming that DCI indicates only one RV value, the RV value of the PDSCH/PUSCH of each slot may be determined sequentially (e.g., 0→2→3→1, 2→3→1→0 . . . ) through a modulo formula similar to the PUSCH repetition operation. The order may be determined through RRC signaling.
Alternatively, when PDSCH/PUSCH transmitted in all slots have the same RV but have respective number of REs, rate matching or bit selection may be performed for each number of REs. In this case, for each PDSCH/PUSCH, the number of bits corresponding to each bit size determined according to the number of REs in the channel coding result may be determined based on the same RV.
Alternatively, when PDSCH/PUSCH transmitted in each slot has each RE number and RV, rate matching or bit selection may be performed for each RE number and RV. In this case, for each PDSCH/PUSCH, bits corresponding to each bit size determined according to the number of REs in the channel coding result may be determined through a part corresponding to each RV.
In the present disclosure, whether to perform rate matching over all slots or whether to perform rate matching for each slot may be predefined/configured or may be configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE. In addition, when rate matching is performed for each slot, whether to use one of the methods described above may be predefined/configured, configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE, or may be switched as needed.
If CB segmentation is supported, rate matching may be performed for each CB. When the CB segmentation is performed according to the above-described embodiment and a different CB is mapped for each PDSCH/PUSCH of each slot, the RV to be applied for the rate matching for each CB may be determined sequentially (e.g., 0→2→3→1, 2→3→1→0 . . . ) through a modulo formula similarly to the PUSCH repetition operation, or the same RV value may be used for all CBs.
In one embodiment, the number of bits determined through bit selection in the rate matching step may be determined by considering the number of bits multiplexed in the PUSCH of each slot, which will be described later, and the number of bits of each PUSCH determined through bit selection may be different according to the multiplexing method. For example, when the number of bits determined based on the number of REs allocated to the PUSCH of a specific slot is 120, if there is no uplink control information (UCI) multiplexing in the corresponding slot, 120 bits may be output through bit selection. On the other hand, when 16-bit UCI multiplexing is required in the corresponding slot, 104 bits may be output through bit selection by considering bits to be added for the multiplexing.
An interleaving method for TBoMS according to an embodiment of the disclosure is disclosed.
In an embodiment, when TBoMS is configured, the interleaving may be performed on all bits output through rate matching.
In an embodiment, when TBoMS is configured, the interleaving may be performed between bits mapped to the same slot (or PUSCH) among bits output through rate matching. In this case, if different CB s are mapped for each PUSCH, the interleaving may be performed only between selected bits corresponding to each CB. Alternatively, if selected bits transmitted on each PUSCH are different even if different CB s are not mapped for each PUSCH, the interleaving may be performed between corresponding selected bits of each PUSCH.
In the disclosure, whether the interleaving for all bits or the slot-based interleaving is performed may be predefined/configured or configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
A CB concatenation method for TBoMS according to an embodiment of the disclosure is disclosed. In this paragraph, it is described as CB coupling, but when considering the rate matching or interleaving, it may also be referred to as rate matching block coupling or interleaving block coupling.
If the CB segmentation is not supported, or if one rate matching is performed over all slots of the number configured for TBoMS, or if TBoMS is configured, a separate CB concatenation operation is not required when the interleaving is performed on all bits output through rate matching.
In a case other than the above case, the CB concatenation may be performed according to the method below.
In an embodiment, all bits corresponding to all rate-matched and interleaved CBs are combined, and a signal processing procedure after the CB concatenation may be performed based on the combination of all bits of all the CBs.
In an embodiment, a slot-based CB concatenation may be performed. For example, when two CBs are mapped to each slot, two CBs mapped to the same slot may be combined. If CBs are different for each slot (PUSCH) and the number of CBs mapped per PUSCH is multiple, CB concatenation may be performed between selected bits of CBs corresponding to each PUSCH.
In an embodiment, when selected bits mapped per PUSCH are obtained for each slot (PUSCH), CB concatenation may be performed between selected bits corresponding to each PUSCH.
Multiplexing
A multiplexing method of a data channel and a control channel for TBoMS according to an embodiment of the disclosure is disclosed. In a slot configured for TBoMS-based PUSCH transmission, when transmitting uplink control information (UCI) including HARQ-ACK or CSI, the UCI may be multiplexed together with a PUSCH for data transmission and transmitted. As another example, when sidelink control information (SCI) is transmitted in a slot configured for TBoMS-based PSSCH transmission, the SCI may be multiplexed together with PSSCH for data transmission and transmitted.
As an example, the entirety of UCI information may be multiplexed based on the same number of bits in all slots, or multiplexed based on an individual number of bits for each slot. As another example, a part constituting the entire UCI information may be multiplexed based on the same number of bits in all slots, or based on an individual number of bits for each slot. As another example, all or part of UCI information may be multiplexed and transmitted in part or one rather than all of a plurality of slots. If UCI is multiplexed in one or more partial slots among a plurality of slots, the method according to the previous two examples may be used. The same method may be applied to multiplexing of SCI and PSSCH. Specifically, data and control information may be multiplexed and transmitted according to the following method.
According to the disclosure, UCI may be multiplexed with PUSCH and transmitted in a slot configured for TBoMS-based PUSCH transmission based on at least one of the following methods.
In one embodiment, entire channel-coded modulation symbols of UCI may be multiplexed and transmitted in each of the PUSCHs of a plurality of slots. In this case, the same number of coded modulation symbols may be multiplexed and transmitted in the PUSCH of all slots. Accordingly, in this case, the calculation of the number of coded modulation symbols for UCI may be performed only once for a plurality of slots. In this case, the calculation of the number of coded modulation symbols for UCI may utilize information on the number of CBs applied to a specific PUSCH, the number of bits per CB, the number of RB s, and the number of time resources. This is inferred from the information included in the DCI. Here, a method of selecting a specific slot is the same as a method described later. Alternatively, the information may be an average value for each slot.
In an embodiment, the calculation of the number of coded modulation symbols for UCI is the same as above in that the calculation of the number of coded modulation symbols is performed only once for a plurality of slots, but the information on the number of CBs, the number of bits per CB, the number of RBs, and the number of time resources is information considering the entire PUSCH, and the calculated coded modulation symbols may be equally divided and multiplexed in each slot or differentially divided and multiplexed based on the number of REs for each slot.
In an embodiment, according to the number of REs (or OFDM symbols) allocated to the PUSCH of each slot, the number of coded modulation symbols individually determined for each PUSCH of each slot may be multiplexed and transmitted. In this case, the calculation of the number of coded modulation symbols for UCI may be individually performed for each slot, and the number of coded modulation symbols multiplexed in each slot may be the same or different. In this case, the calculation of the number of coded modulation symbols for UCI may utilize information on the number of CBs applied to each PUSCH, the number of bits per CB, the number of RBs, and the number of time resources.
In an embodiment, all of the channel-coded modulation symbols of the UCI may be multiplexed and transmitted in some (or one) of a plurality of slots. For example, UCI may be multiplexed and transmitted only in the PUSCH of the first slot, and only UL-SCH may be transmitted in the remaining slots. Alternatively, the PUSCH having the largest number of REs may be selected. The PUSCH or its selection condition may be configured by signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
According to the present disclosure, when SCI is multiplexed with PSSCH, the same method as when UCI is multiplexed with PUSCH may be applied.
On the other hand, as described above, if control information (UCI, SCI, . . . ) multiplexed in TBoMS-based data channel transmission exists, bit selection in the rate matching step may be performed considering the number of bits inserted for the multiplexing. If modulation symbols corresponding to different numbers of bits are multiplexed for each slot, accordingly, the number of bits determined through the bit selection may also vary for each slot.
The method for performing multiplexing described in the disclosure may be predefined/configured or configured through signaling (RRC, system information, MAC, DCI, . . . ) between the base station and the UE.
A scrambling method for TBoMS according to an embodiment of the disclosure is disclosed. Here, it is assumed that the processing of the placeholder bit in the existing standard is the same as in the prior art.
In an embodiment, only one scrambling code (or scrambling sequence) for the scrambling operation may be generated to be applied over all of a plurality of slots, and the scrambling operation may be performed over all slots. In this case, the scrambling operation may be performed by sequentially mapping bits for data channels (PDSCH/PUSCH/PSSCH) of a plurality of slots from the start of the scrambling code. Alternatively, considering the REs not used for the data channel within the slot, as many bits as corresponding to the bits for the corresponding REs among the scrambling code bits are not used, and a scrambling operation may be performed by mapping from the next bit to the bits for the data channel of the next slot.
In an embodiment, a scrambling code (or scrambling sequence) for a scrambling operation may be generated for each of a plurality of slots, and the scrambling operation may be performed for each slot.
Specifically, data and control information may be multiplexed and transmitted according to the following method.
1. One scrambling code (or scrambling sequence) is generated for all of the plurality of slots, and scrambling may be performed based on this.
1-1. A starting point of the scrambling code for each slot of the entire scrambling sequence may be determined based on the number of coded modulation symbols (i.e., the number of REs for actual PDSCH/PUSCH/PSSCH) in the previous slot. The starting point of the scrambling code for the first slot may be 0.
1-2. A start point of the scrambling code for each slot in the entire scrambling sequence may be determined based on the number of REs between the start RE of the PDSCH/PUSCH/PSSCH of the previous slot and the start RE of the PDSCH/PUSCH/PSSCH of the current slot. In this case, OFDM symbols not allocated to PDSCH/PUSCH/PSSCH and REs for DMRS may also be included. The starting point of the scrambling code for the first slot may be 0.
1-3. A starting point of the scrambling code for each slot of the entire scrambling sequence may be determined based on the slot length and the number of allocated PRB s. The starting point of the scrambling code for the first slot may be 0.
2. A scrambling code is generated for each slot, and scrambling may be performed based on this.
Referring to
TBS may be determined based on TBoMS configuration information and information included in the DCI (1002). For example, if the number of PUSCH transmission slots configured through TBoMS configuration information is 4, the same RE is allocated to PUSCHs in all slots, and the TBS determined based on the number of REs allocated to PUSCHs in one slot is 40 bit, the TBS may be determined as 40*4=160 bits for PUSCH of a total of 4 slots.
A CRC may be attached to the TB corresponding to the determined TBS (1003). The CRC attached to the TB may have, for example, 24 bit size.
On the other hand, as described above, when considering high coding gain in TBoMS, it is preferable to transmit a small TB, and accordingly, in this example, it may be assumed that CB segmentation is not performed (1004). When the CB segmentation is not performed, a separate CB CRC attaching step may also not be performed (1005). However, it should be noted that the omission of 1004 and 1005 is only for this example, and the corresponding operation may be performed according to the above-described embodiments.
Channel coding may be performed on the entire 184 bits to which the CRC is attached to the TB (1006). For example, the channel coding may be performed based on LDPC code.
Rate matching (or bit selection) may be performed on the channel-coded bits (1007). In this example, one rate matching operation is performed over the PUSCH of all slots, and in this case, bit selection may be performed based on channel coded bits according to the RV value indicated through DCI format 0_0. As another example, if the rate matching operation is performed for each slot or CB, RV may be equally applied as a value indicated by DCI for each slot, or may be sequentially determined through a modulo equation. In addition, in this step, the UE may perform bit selection considering UCI bits multiplexed in the PUSCH of a plurality of slots. In this case, if the rate matching operation is performed for each slot or CB in another example, bit selection of different sizes may be performed considering UCI bits multiplexed in each slot.
Interleaving may be performed on the rate-matched bits (1008). In this example, it is assumed that interleaving is performed once for all rate-matched bits, that is, over the PUSCH of all slots. As another example, interleaving may be performed in units of slots or CBs, and a detailed method refers to the above-described embodiment.
In this example, because it is assumed that CB segmentation is not performed previously, CB concatenation may also not be performed (1009). In contrast, if the CB segmentation is performed, the CB concatenation may also be performed, and for a detailed method, refer to the above-described embodiment.
Thereafter, bits for control information (UCI in case of PUSCH transmission) may be multiplexed in PUSCH transmission (1010). In this example, all UCI bits are multiplexed in each PUSCH in all slots, but UCI bits may be multiplexed in PUSCHs in a plurality of slots in various ways according to the above-described embodiment.
After the UCI bit is inserted for multiplexing, scrambling may be performed based on a scrambling code (or scrambling sequence) (1011). In this example, although the scrambling is performed by applying one scrambling code to the PUSCH of all slots as an example, a separate scrambling code may be applied to each slot. When one scrambling code is applied to the PUSCH of all slots, bits corresponding to the PUSCH of each slot may be sequentially mapped to the determined scrambling code. On the other hand, although not separately illustrated, according to an example, scrambling codes corresponding to multiplexed control information (e.g., UCI) bits may be generated based on placeholder bits so that scrambling operations are not performed.
After scrambling, the PUSCH may be transmitted in a plurality of slots through modulation, layer mapping and precoding, resource mapping, and the like.
Referring to
TBS may be determined based on TBoMS configuration information and information included in the DCI (1052). For example, if the number of PUSCH transmission slots configured through TBoMS configuration information is 4, the same RE is allocated to PUSCHs in all slots, and the TBS determined based on the number of REs allocated to PUSCHs in one slot is 40 bit, the TBS may be determined as 40*4=160 bits for PUSCH of a total of 4 slots.
A CRC may be attached to the TB corresponding to the determined TBS (1053). The CRC attached to the TB may have, for example, 24 bit size.
On the other hand, as described above, when considering high coding gain in TBoMS, it is preferable to transmit a small TB, and accordingly, in this example, it may be assumed that CB segmentation is not performed (1054). When the CB segmentation is not performed, a separate CB CRC attaching step may also not be performed (1055). However, it should be noted that the omission of 1054 and 1055 is only for this example, and the corresponding operation may be performed according to the above-described embodiments.
Channel coding may be performed on the entire 184 bits to which the CRC is attached to the TB (1056). For example, the channel coding may be performed based on LDPC code.
Rate matching (or bit selection) may be performed on the channel-coded bits (1057). In this example, it is exemplified that the rate matching is performed for each PUSCH of each slot, and in this case, it is configured that the RV value indicated through DCI format 0_0 is equally applied to all PUSCH rate matching. In an example, RV may be determined sequentially through a modulo equation. When the rate matching is performed for each PUSCH of a slot, the result of bit selection for each slot may vary according to the number of REs or RV value of each PUSCH. In addition, in this step, the UE may perform bit selection by considering UCI bits multiplexed in the PUSCH of each slot. When the rate matching is performed for each slot or CB, bit selection of different sizes may be performed considering the UCI bits multiplexed in each slot.
Interleaving may be performed on the rate-matched bits (1058). In this example, interleaving is performed in units of slots or CBs. A detailed method refers to the above-described embodiment.
In this example, because it is assumed that CB segmentation is not performed previously, CB concatenation may also not be performed (1059). In contrast, if the CB segmentation is performed, the CB concatenation may also be performed, and for a detailed method, refer to the above-described embodiment.
Thereafter, bits for control information (UCI in case of PUSCH transmission) may be multiplexed in PUSCH transmission (1060). In this example, all UCI bits are multiplexed in one selected PUSCH, but UCI bits may be multiplexed in PUSCHs in a plurality of slots in various ways according to the above-described embodiment.
After the UCI bit is inserted for multiplexing, scrambling may be performed based on a scrambling code (or scrambling sequence) (1061). In this example, a separate scrambling code may be applied for each slot. In this case, if PN code initialization is performed by using the same identifier and parameters (slot index, subframe index, etc.) for time units are not used for PN code generation when generating scrambling codes for each PUSCH, the scrambling codes applied to each slot are substantially the same. However, the length of the scrambling code may be different according to the number of bits allocated to each PUSCH.
After scrambling, the PUSCH may be transmitted in a plurality of slots through modulation, layer mapping and precoding, resource mapping, and the like.
Referring to
Referring to
Referring to
Referring to
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, parts of embodiments of the disclosure may be combined with each other to operate a base station and a terminal.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2021-0060322 | May 2021 | KR | national |
This application is a continuation application of International Application No. PCT/KR2022/005725 filed on Apr. 21, 2022, which claims priority from and derives the benefit of Korean Patent Application No. 10-2021-0060322 filed on May 10, 2021, the entire contents of each of these applications is hereby incorporated in their entirety, by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2022/005725 | Apr 2022 | US |
| Child | 18506082 | US |
