KR20230139643A - Method and apparatus for transmitting and receiving data for low latency service in wireless communication system - Google Patents

Abstract

A method and device for transmitting and receiving data for a low-latency service in a wireless communication system are disclosed. A method of transmitting and receiving data for a low-latency service in a wireless communication system is a method of operating a terminal in a communication system, comprising: receiving a message including terminal-specific identifier information and public identifier information from a base station; generating terminal-specific CRC bits for data to be transmitted to the base station using the terminal-specific identifier; generating a data block containing the data and the terminal-specific CRC bits; performing channel coding on the data block; performing scrambling on the data block on which the channel coding was performed using the common identifier; and transmitting a signal generated by modulating the scrambling data block to the base station.

Description

Method and device for transmitting and receiving data for low-latency service in wireless communication system {METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING DATA FOR LOW LATENCY SERVICE IN WIRELESS COMMUNICATION SYSTEM}

The present invention relates to data transmission and reception technology, and more specifically, to a data transmission and reception method and device for low-latency services in a wireless communication system.

With the advancement of information and communication technology, various wireless communication technologies are being developed. Representative wireless communication technologies include long term evolution (LTE) and new radio (NR), which are defined in the 3rd generation partnership project (3GPP) standard. LTE may be a wireless communication technology among 4G (4th Generation) wireless communication technologies, and NR may be a wireless communication technology among 5G (5th Generation) wireless communication technologies.

In order to handle the rapid increase in wireless data after the commercialization of the 4G communication system (e.g., a communication system supporting LTE), the frequency band of the 4G communication system (e.g., a frequency band below 6 GHz) as well as the 4G communication system A 5G communication system (e.g., a communication system supporting NR) that uses a frequency band higher than the frequency band (e.g., a frequency band of 6 GHz or higher) may be considered. The 5G communication system can support enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC).

To reduce time delay in 5G NR URLLC, in addition to dynamic grant-based transmission, configured grant (CG) configuration transmission technology can be used. The CG configuration transmission method may use a k-repeated transmission method and a method of allocating multiple CG configurations to reduce the probability of collision while allocating UE common wireless resources rather than UE (User Equipment)-specific wireless resources. . Meanwhile, since the base station cannot know when and to which terminal data was generated, the base station may have to blindly receive multiple radio resources allocated in the CG configuration. Therefore, there is a problem in that the base station must repeatedly perform reception equal to the number of terminals to which CG configuration resources are allocated and the number of multiple CG configurations.

The purpose of the present invention to solve the above problems is to provide a method and device for transmitting and receiving data for low-latency services in a wireless communication system.

A method of transmitting and receiving data for a low-latency service in a wireless communication system according to an embodiment of the present application to achieve the above object is a method of operating a terminal in a communication system, and is provided from a base station to a terminal-specific (UE (User Equipment)-specific) ) Receiving a message containing identifier information and common identifier information; Generating terminal-specific CRC (Cyclic Redundancy Check) bits for data to be transmitted to the base station using the terminal-specific identifier; generating a data block containing the data and the terminal-specific CRC bits; performing channel coding on the data block; performing scrambling on the data block on which the channel coding was performed using the common identifier; And it may include transmitting a signal generated by modulating the scrambling data block to the base station.

Here, generating the terminal-specific CRC bits includes performing a CRC operation on the data to obtain CRC bits including first CRC bits and second CRC bits; and generating third CRC bits by performing an operation on the second CRC bits using the terminal-specific identifier, wherein generating the data block comprises: the data, the first CRC bit, and generating a data block including the third CRC bits.

Here, generating the third CRC bits by performing an operation on the second CRC bits includes generating the third CRC bits by performing an exclusive OR (XOR) operation between the second CRC bits and the terminal-specific identifier. It may be characterized by generating bits.

Here, the terminal-specific identifier information includes CRC generation polynomial information set differently for each terminal, and the step of generating the terminal-specific CRC bits includes generating the terminal-specific CRC bits using the CRC generation polynomial. It can be characterized.

Here, it further includes receiving a retransmission request from the base station, wherein the retransmission request is DCI (Downlink Control Information) transmitted through a PDCCH (Physical Downlink Control Channel), and the terminal uses the public identifier to transmit the DCI. It may be characterized by receiving.

Here, receiving retransmission reservation resource information, which is a resource for transmitting retransmission data, from the base station through RRC (Radio Resource Control) signaling, and transmitting the retransmission data to the base station based on the retransmission reservation resource information. may further include.

Here, the retransmission reservation resource information may include a frequency interval between the PDCCH resource and the retransmission resource and a time interval between the PDCCH resource and the retransmission resource.

A method of transmitting and receiving data for a low-latency service in a wireless communication system according to another embodiment of the present application for achieving the above object includes transmitting a message including terminal-specific identifier information and public identifier information to a terminal, the terminal Transmitting Downlink Control Information (DCI) through a Physical Downlink Control Channel (PDCCH), obtaining a data block from the terminal from a resource scheduled by the DCI, and transmitting a data block to the data block. performing descrambling using the public identifier, performing channel decoding on the data block on which the descrambling was performed, and performing channel decoding on the data block on which the channel decoding was performed, and the terminal -May include performing a CRC (Cyclic Redundancy Check) check using a specific identifier.

Here, the terminal-specific identifier may be a terminal-specific Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) associated with the base station, and the public identifier may be a public CS-RNTI commonly assigned to the terminals.

Here, the message may further include CRC generation polynomial information set differently for each terminal.

Here, the step of performing a CRC (Cyclic Redundancy Check) check on the data block on which the channel decoding has been performed may be characterized by performing a CRC check using the CRC generation polynomial.

Here, when the received signal power of the Dedicated deModulation Reference Signal (DMRS) for the data block is greater than or equal to a predetermined value, the step of requesting retransmission of data from the terminal may be further included.

Here, when the received signal power of the DMRS for the data block is more than a predetermined value, the step of requesting retransmission of the data to the base station involves scrambling (using the common identifier through PDCCH (Physical Downlink Control Channel)) It may be characterized by transmitting scrambled Downlink Control Information (DCI) to request retransmission of the data from the base station.

In order to achieve the above object, a data transmitting and receiving device for a low-latency service in a wireless communication system according to another embodiment of the present application adds a CRC (Cyclic Redundancy Check) generated using a terminal-specific identifier to the data. A CRC addition unit for generating a data block, a channel coding unit for performing channel coding on the data block, and scrambling using a common identifier for the data block on which the channel coding was performed. It may include a scrambling unit that performs scrambling and a modulation unit that modulates the scrambling data block.

Here, the terminal-specific identifier may be a terminal-specific Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) associated with the terminal, and the public identifier may be a public CS-RNTI commonly assigned to the terminal.

Here, the CRC generated using the terminal-specific identifier may be a CRC generated by performing an exclusive OR (XOR) operation between the CRC bits of data to be transmitted to the base station and the terminal-specific identifier.

Here, the CRC (Cyclic Redundancy Check) generated using the terminal-specific identifier may be characterized as being generated using CRC bits of data to be transmitted to the base station and a CRC generation polynomial that is different for each terminal.

According to the present application, the base station can reduce the amount of calculation to perform descrambling and/or decoding only once using a shared identifier for PUSCH (Physical Uplink Shared Channel) data received from the terminal, The time delay of the communication system can be reduced.

In addition, according to the present application, when a collision occurs between terminals in CG configuration PUSCH transmission, at least one terminal can receive a retransmission request from the base station, and at least one terminal can transmit uplink data to the base station using different resources. It can be retransmitted to .

1 is a conceptual diagram showing a first embodiment of a communication system.
Figure 2 is a block diagram showing a first embodiment of components of a communication node included in a communication system.
Figure 3 is a flowchart showing a first embodiment of an uplink communication method according to a CG type 1 configuration (configuredGrant type 1 configuration) in a communication system.
FIG. 4 is a flowchart illustrating a first embodiment of an uplink communication method according to a configuredGrant type 2 configuration in a communication system.
Figure 5 is a conceptual diagram showing a first embodiment of multiple CG configurations.
Figure 6 is a conceptual diagram showing a first embodiment of CG configuration transmission of multiple terminals.
Figure 7 is a block diagram showing a first embodiment of a CG configuration PUSCH transmission device that uses CS-RNTI in a scrambling procedure of PUSCH data.
Figure 8 is a block diagram showing a first embodiment of a CG configuration PUSCH receiving device that uses CS-RNTI in the descrambling procedure of PUSCH data.
Figure 9 is a block diagram showing a first embodiment of a data transmission and reception device for low-delay service in a wireless communication system.
Figure 10 is a block diagram showing a second embodiment of a data transmission and reception device for low-delay service in a wireless communication system.
Figure 11 is a block diagram showing a third embodiment of a data transmission and reception device for low-delay service in a wireless communication system.
Figure 12 is a block diagram showing a fourth embodiment of a data transmission and reception device for low-delay service in a wireless communication system.
Figure 13 is a flowchart showing a first embodiment of a data transmission and reception method for low-delay service in a wireless communication system.
Figure 14 is a flowchart showing a second embodiment of a data transmission and reception method for low-delay service in a wireless communication system.
Figure 15 is a conceptual diagram showing a first embodiment of a method for adding a CRC using a terminal-specific identifier.
Figure 16 is a flowchart showing a first embodiment of the uplink data transmission procedure of the terminal.
FIG. 17 is a conceptual diagram illustrating a first embodiment of a method in which a base station transmits a DCI requesting retransmission of a terminal to at least one terminal.
Figure 18 is a conceptual diagram showing a first embodiment of a retransmission reservation resource used for retransmission of uplink data of a terminal.

A communication system to which embodiments according to the present application are applied will be described. The communication system to which the embodiments according to the present application are applied is not limited to the content described below, and the embodiments according to the present application can be applied to various communication systems. Here, communication system may be used in the same sense as communication network.

Since this application can make various changes and have various embodiments, specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the present application to specific embodiments, and should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present application.

Terms such as first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be named a second component without departing from the scope of the present application, and similarly, the second component may also be named a first component. The term “and/or” may include any of a plurality of related stated items or a combination of a plurality of related stated items.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this application are merely used to describe specific embodiments and are not intended to limit the present application. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Throughout the specification, network refers to, for example, wireless Internet such as WIFI, mobile Internet such as WiBro (wireless broadband internet) or WiMax (world interoperability for microwave access), GSM (global system for mobile communication), or CDMA (code Division multiple access) or 3G mobile communication network such as CDMA2000, 3.5G (3.5th generation) mobile communication network such as HSDPA (high speed downlink packet access) or HSUPA (high speed uplink packet access), LTE (long term evolution) network or LTE -May include 4G (4th generation) mobile communication networks such as Advanced, and 5G (5th generation) mobile communication networks.

Throughout the specification, terminal refers to a mobile station, mobile terminal, subscriber station, portable subscriber station, user equipment, and access terminal. etc., and may include all or part of the functions of a terminal, a mobile station, a mobile terminal, a subscriber station, a portable subscriber station, a user device, an access terminal, etc.

The above-mentioned terminals are desktop computers, laptop computers, tablet PCs, wireless phones, mobile phones, smart phones, and smart watches capable of communication. (smart watch), smart glass, VR glasses (virtual reality glass), e-book reader, PMP (portable multimedia player), portable game console, navigation device, digital camera, DMB (digital) multimedia broadcasting player, digital audio recorder, digital audio player, digital picture recorder, digital picture player, digital video player, etc. It can refer to various devices that users of mobile communication services can use.

Throughout the specification, base station refers to an access point, radio access station, node B, evolved node B, base transceiver station, and MMR. -Can refer to BS (Mobile Multi-hop Relay - Base Station), etc., and can include all or part of the functions of base station, access point, wireless access station, NodeB, eNodeB, transmitting and receiving base station, MMR-BS, etc. there is.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which this application pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an idealized or excessively formal sense. No.

Below, the 3GPP NR system as well as the 3GPP LTE/LTE-A system can be described as an example of a wireless access system in which embodiments of the present application can be used. Hereinafter, in order to clarify the description of the present application, the description is based on the 3GPP communication system (LTE, NR, etc.), but the technical idea of the present application is not limited thereto.

The following technologies are CDMA (code division multiple access). It can be used in various access communication systems such as frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

A communication system or a memory system to which embodiments according to the present invention are applied will be described. The communication system or memory system to which the embodiments according to the present invention are applied is not limited to the content described below, and the embodiments according to the present invention can be applied to various communication systems. Here, communication system may be used in the same sense as communication network.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the attached drawings. In order to facilitate overall understanding when describing the present invention, the same reference numerals are used for the same components in the drawings, and duplicate descriptions for the same components are omitted.

1 is a conceptual diagram showing a first embodiment of a communication system.

Referring to FIG. 1, the communication system 100 includes a plurality of communication nodes 110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). A plurality of communication nodes are 4G communication (e.g., long term evolution (LTE), LTE-A (advanced)), 5G communication (e.g., new radio (NR)) specified in the 3rd generation partnership project (3GPP) standard. ), etc. can be supported. 4G communications can be performed in frequency bands below 6 GHz, and 5G communications can be performed in frequency bands above 6 GHz as well as below 6 GHz. Additionally, 6G communication may be performed at a frequency in the terahertz (THz) band.

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

Meanwhile, a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-) constituting the communication system 100 4, 130-5, 130-6) Each can have the following structure.

Figure 2 is a block diagram showing a first embodiment of components of a communication node included in a communication system.

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

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

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

Referring again to FIG. 1, the communication system 100 includes a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) and a plurality of terminals (130- 1, 130-2, 130-3, 130-4, 130-5, 130-6). Base stations (110-1, 110-2, 110-3, 120-1, 120-2) and terminals (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) The communication system 100 that includes may be referred to as an “access network.” Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell. Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the cell coverage of the first base station 110-1. The second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the cell coverage of the second base station 110-2. The fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong to the cell coverage of the third base station 110-3. there is. The first terminal 130-1 may belong to the cell coverage of the fourth base station 120-1. The sixth terminal 130-6 may belong to the cell coverage of the fifth base station 120-2.

Here, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 includes a NodeB, an evolved NodeB, a base transceiver station (BTS), Radio base station, radio transceiver, access point, access node, road side unit (RSU), radio remote head (RRH), transmission point (TP), TRP ( transmission and reception point), eNB, gNB, small base station, small cell base station, femto cell base station, micro cell base station, picocell base station It may be referred to as, etc.

A plurality of terminals (130-1, 130-2, 130-3, 130-4, 130-5, and 130-6) each include a user equipment (UE), a terminal, an access terminal, and a mobile device. Terminal, station, subscriber station, mobile station, portable subscriber station, node, device, IoT (Internet of Thing) It may be referred to as a device, a mounted device (mounted module/device/terminal or on board device/terminal, etc.), etc.

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

In addition, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 performs multi-input & multi-output (MIMO) transmission (e.g., single user (Single User; SU)-MIMO, Multi-User (MU)-MIMO, multi-cell MIMO, massive MIMO, etc.), Adaptive MIMO Switching (AMS) , Coordinated Multi-Point transmission and reception (CoMP), Carrier Aggregation (CA) transmission, transmission in unlicensed band, Device-to-Device communication (D2D communication) ) (or ProSe (Proximity Services)), etc. may be supported. Here, each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, and 130-6 is connected to a base station 110-1, 110-2, 110-3, and 120-1. , 120-2) and operations corresponding to those supported by the base stations 110-1, 110-2, 110-3, 120-1, and 120-2. For example, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO method, and the fourth terminal 130-4 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO method. A signal can be received from the second base station 110-2. Alternatively, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 and the fifth terminal 130-5 based on the MU-MIMO method, and the fourth terminal 130-4 and the fifth terminal 130-5 can each receive a signal from the second base station 110-2 by the MU-MIMO method.

Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP method, and the fourth terminal 130-4 may transmit a signal to the fourth terminal 130-4. The terminal 130-4 can receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 using the CoMP method. Each of a plurality of base stations (110-1, 110-2, 110-3, 120-1, 120-2) has a terminal (130-1, 130-2, 130-3, 130-4) within its cell coverage. , 130-5, 130-6), and signals can be transmitted and received based on the CA method. The first base station 110-1, the second base station 110-2, and the third base station 110-3 each control D2D between the fourth terminal 130-4 and the fifth terminal 130-5. and each of the fourth terminal 130-4 and the fifth terminal 130-5 can perform D2D under the control of each of the second base station 110-2 and the third base station 110-3. .

Meanwhile, in the communication system, at least one base station (110-1, 110-2, 110-3) performs all functions of the communication protocol (e.g., remote wireless transmission and reception function, baseband processing function) can do. Alternatively, among all the functions of the communication protocol, the remote wireless transmission and reception function may be performed by a transmission reception point (TRP) (e.g., f(flexible)-TRP), and the baseband processing function among all the functions of the communication protocol Can be performed by a BBU (baseband unit) block. The TRP may be a remote radio head (RRH), radio unit (RU), transmission point (TP), etc. A BBU block may include at least one BBU or at least one digital unit (DU). A BBU block may be referred to as a “BBU pool,” “centralized BBU,” etc. The TRP can be connected to the BBU block via a wired fronthaul link or a wireless fronthaul link. A communication system consisting of a backhaul link and a fronthaul link may be as follows. When the function split method of the communication protocol is applied, the TRP can selectively perform some functions of the BBU or some functions of medium access control (MAC)/radio link control (RLC).

Next, grant free (or CG (Configured Grant)) uplink communication methods in a communication system will be described. Even when a method (e.g., transmission or reception of a signal) performed in a first communication node among communication nodes is described, the corresponding second communication node is described as a method (e.g., transmitting or receiving a signal) corresponding to the method performed in the first communication node. For example, reception or transmission of a signal) can be performed. That is, when the operation of the terminal is described, the corresponding base station can perform the operation corresponding to the operation of the terminal. Conversely, when the operation of the base station is described, the corresponding terminal can perform the operation corresponding to the operation of the base station.

With the advancement of information and communication technology, various wireless communication technologies are being developed. Representative wireless communication technologies include long term evolution (LTE) and new radio (NR), which are defined in the 3rd generation partnership project (3GPP) standard. LTE may be a wireless communication technology among 4G (4th Generation) wireless communication technologies, and NR may be a wireless communication technology among 5G (5th Generation) wireless communication technologies.

In order to handle the rapid increase in wireless data after the commercialization of the 4G communication system (e.g., a communication system supporting LTE), the frequency band of the 4G communication system (e.g., a frequency band below 6 GHz) as well as the 4G communication system A 5G communication system (e.g., a communication system supporting NR) that uses a higher frequency band (e.g., a frequency band of 6 GHz or higher) is being considered. The 5G communication system can support enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC).

In the 3GPP 5G NR (New Radio) system, eMBB is used to meet the requirements of new use cases such as intelligent transportation, augmented/virtual reality, and industrial automation. Standardization is underway in three scenarios: (enhanced Mobile BroadBand), mMTC (massive Machine Type communication), and URLLC (Ultra-Reliable Low Latency Communication).

In particular, in 3GPP 5G NR Rel-15, URLLC aims to support use cases such as augmented and virtual reality in the entertainment industry, remote driving in the transportation industry, and power distribution, and can define performance requirements as follows: For Rel-15 URLLC uplink/downlink data size of 32 bytes, the latency is in the 1 ms (millisecond) range and the block error rate (BLER) is in the range. It was set to . Additionally, in Rel-16 URLLC, the block error rate is , the requirements were further tightened by setting the time delay to 0.5 to 1 ms.

To improve the reliability of the block error rate of 5G NR URLLC, in addition to the Modulation and Coding Scheme (MCS) table for eMBB with a conventional block error rate of 10 ^-1 , the URLLC requirements are A new MCS table was added to the standard to support PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel) transmission. Through the new MCS table added, it is transmitted at a code speed and modulation method suitable for URLLC transmission. In addition, reliability was improved through repeated transmission on the PDCCH (Physical Downlink Control Channel) channel, which transmits downlink control information (DCI).

Meanwhile, in the 3GPP 4G LTE system, the uplink in which the terminal transmits data to the base station may be based on the base station's dynamic grant method. The dynamic approval-based method means that the moment the terminal generates data to transmit to the base station, the terminal performs a scheduling request to the base station, and then the base station allocates radio resources for time and frequency in response to the scheduling request for the uplink. This is a procedure to grant data transmission. The terminal can transmit data using allocated wireless resources. At this time, the characteristic is that radio resources are allocated separately to each terminal so that collisions do not occur.

In 3GPP 5G NR URLLC, in addition to dynamic grant-based transmission, CG (configured grant) configuration and transmission can be used as a standard technology to reduce time delay. When the CG method is used for uplink communication in a communication system, the terminal can transmit uplink data using preset uplink resources (eg, CG configuration resources) without a resource allocation procedure by the base station.

CG configuration transmission allows the terminal to transmit the data to the base station (gNB) the moment data to be transmitted to the base station occurs without the terminal's scheduling request and/or the base station's approval procedure. The base station may inform the terminal in advance of resources and related parameters for performing CG configuration transmission to enable the above-described CG configuration transmission. CG configuration transmission methods can be classified into CG Type 1 configuration and CG Type 2 configuration. Hereinafter, the physical channel through which the terminal transmits URLLC data may be referred to as PUSCH (Physical Uplink Shared channel).

CG Type 1 configuration is where the base station uses Radio Resource Control (RRC) signaling to configure the time and frequency domains, including the periodicity of the CG configuration resources, offset, start symbol and length of PUSCH, MCS, number of repetitions, redundant base station version, and power level. Information such as resource allocation can be provided to the terminal. When CG type 1 configuration is used, CG configuration resources can be set and activated by radio resource control (RRC) signaling procedures. In the CG type 2 configuration, the base station provides only the periodicity and repetition number to the terminal through RRC signaling, and provides other parameters through downlink control information (DCI) and can activate and deactivate the service. If CG type 2 configuration is used, CG configuration resources may be established by an RRC signaling procedure and activated by a physical (PHY) signaling procedure (e.g., downlink control information (DCI)).

Figure 3 is a flowchart showing a first embodiment of an uplink communication method according to CG type 1 configuration in a communication system.

Referring to FIG. 3, a communication system may include a base station and a terminal. The base station may be the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 shown in FIG. 1, and the terminal may be the terminals 130-1, 130-2, and It may be 130-3, 130-4, 130-5, 130-6). Each of the base station and the terminal may be configured the same or similar to the communication node 200 shown in FIG. 2.

The base station may transmit an RRC reconfiguration message including CG configuration setting information to the terminal (S301). The terminal can receive an RRC reset message from the base station and check the CG configuration setting information included in the RRC reset message. CG configuration setting information may mean “CG configuration information element (IE),” “CG configuration setting parameter,” or “CG configuration parameter.” In step S302, the terminal can set the CG based on the CG configuration setting information and activate the set CG. In embodiments, CG may mean CG configuration resources, parameters for CG, and/or operations for CG. CG configuration resources can be set periodically.

When uplink data to be transmitted through the CG configuration resource occurs, the terminal may transmit the uplink data to the base station using the CG configuration resource set by the base station (S303). Additionally, the terminal may start the CG configuration timer at the time of transmission of uplink data. From the start of the CG configuration timer to the end of the CG configuration timer, the UE monitors the PDCCH using a configured scheduling-radio network temporary identifier (CS-RNTI) in the UE (User Equipment)-specific search space. The action can be performed.

If a DCI requesting retransmission of uplink data (for example, a DCI including a new data indicator (NDI) set to 1) is received from the base station before the expiration of the CG configuration timer, the terminal performs a retransmission procedure for uplink data. It can be done. That is, when the NDI included in the DCI is set to 1, the terminal can determine that the resource allocated by the DCI is a retransmission resource. The retransmission procedure of uplink data can be performed using resources indicated by DCI. If a DCI requesting retransmission of uplink data is not received from the base station before the end of the CG configuration timer, the terminal may determine that the uplink data has been successfully received from the base station.

The base station can perform a reception operation of uplink data by performing a monitoring operation on the CG configuration resources (S304). Monitoring operations may be performed periodically. For example, the base station may perform a detection operation of a dedicated demodulation reference signal (DMRS) in CG configuration resources (S304-1). The DMRS detection operation may be an autocorrelation operation for the DMRS sequence set between the base station and the terminal. If the energy level as a result of the detection operation of the DMRS is above the threshold, the base station may determine that uplink data has been transmitted in the CG configuration resource. If the energy level resulting from the detection operation of the DMRS is less than the threshold, the base station may determine that uplink data has not been transmitted in the CG configuration resource.

If it is determined that uplink data has been transmitted from the CG resource, the base station may perform a cyclic redundancy check (CRC) operation on the uplink data obtained from the CG resource (S304-2). If the result of the CRC operation is successful, the base station can perform a decoding operation of uplink data (S304-3). If the result of the CRC operation is failure, the base station can perform a resource allocation procedure for retransmission of uplink data.

In step S301 described above, an RRC reset message may be transmitted to set up a data radio bearer (DRB) of the terminal. The RRC reset message may include an index of the DRB, a logical channel identifier (LCID) mapped to the corresponding DRB, etc. For example, the RRC reset message is It may include (Information Element), May include parameters defined in Table 1 below (e.g., parameters below related to logical channels). The parameters defined in Table 1 can be used for logical channel prioritization (LCP) operation and buffer status report (BSR) operation in the medium access control (MAC) layer of the terminal. In embodiments, the radio link control (RLC) layer may be an entity that performs the functions of the RLC layer, the MAC layer may be an entity that performs the functions of the MAC layer, and the physical (PHY) layer may be a PHY layer. It may be an entity that performs a function.

The terminal can check the parameters defined in Table 1 by receiving an RRC reset message in step S301. set to true may indicate that CG type 1 configuration is used for the logical channel mapped to the corresponding DRB. To apply multiple CGs, may include indices of CG configuration parameters applied in the corresponding logical channel. The index of the CG configuration parameter is included in It can be set by .

The upper layer (e.g., RLC layer) of the terminal may transmit information (e.g., buffer information) indicating the existence of data to be transmitted according to the CG type 1 configuration to the MAC layer of the terminal. The MAC layer of the terminal may receive buffer information from a higher layer and update buffer information for the logical channel based on the received buffer information. When CG configuration resources according to CG type 1 configuration exist, the MAC layer of the terminal can generate a MAC PDU (protocol data unit) using data existing in the RLC buffer, and send the MAC PDU to the lower layer of the terminal (e.g. For example, it can be passed to the PHY layer).

Additionally, the RRC reset message transmitted in step S301 is It may further include, may include the parameters defined in Table 2 below. may include transmission period information, frequency resource information, time resource information, transport block size (TBS) information, etc. for CG type 1 configuration.

The terminal can check the parameters defined in Table 2 by receiving an RRC reset message in step S301. If a CG Type 1 configuration is used, the parameters are sent in the RRC reset message (e.g. ) can be transmitted by.

[Cycle setting of CG configuration resources]

The period (e.g., transmission period) of CG configuration resources according to CG type 1 configuration can be determined based on Equation 1 below.

may be the number of slots per radio frame, may be the number of symbols per slot. , , and Is It may be a parameter included in . may be the starting symbol within the slot. is the RRC parameter It can be set by . The value (m) is , PUSCH (physical uplink shared channel) mapping type, and PUSCH- consisting of SLIV (start and length indicator) The index (m+1) of can be indicated. may mean the interval between DCI and PUSCH in the time domain. SLIV may indicate a combination of the index of the first symbol of the PUSCH resource and the length of the PUSCH resource. The index of the first symbol of the PUSCH resource and the length of the PUSCH resource can be determined based on Equation 2 below.

Based on Equation 1, N with the closest value to the current SFN (system frame number), slot, and symbol can be determined, and the CG configuration resource is "determined N It can be set to “periodicity”. Here, the determined N can be increased by 1.

[Setting of frequency and time resources]

Frequency and time resources for CG Type 1 configuration can be set by RRC parameters. The time resource (e.g., the length L of the time resource) for CG Type 1 configuration is the RRC parameter: It can be set by . Frequency resources for CG type 1 configuration are "parameters that set the allocation method of frequency resources (e.g., bitmap or RIV (resource indication value)). " and "Set the resource allocation area (e.g., starting physical resource block (PRB) and number of PRBs) according to the allocation method. "It can be set by:

this If set, frequency resources for CG type 1 configuration can be indicated by a bitmap. The total bandwidth can be divided into RBG (resource block group) units and bitmaps (e.g., ) can indicate whether one RBG is configured for CG type 1 configuration. That is, one bit included in the bitmap can be mapped one-to-one with one RBG.

The size of the RBG is determined by the RRC parameter. and bandwidth size. In CG configuration parameters: The field is Since it is set, the size of the RBG can be determined based on Table 3 according to the bandwidth of the communication system (eg, the size of the bandwidth part (BWP)).

this When set to , the frequency resources for CG type 1 configuration are RIV (e.g. ) can be indicated by. As shown in Equation 3 below, RIV is the starting RB (e.g., ) and number of RBs (e.g. ) can be indicated. may indicate the bandwidth size (e.g., number of BWPs).

[TBS settings]

When CG Type 1 configuration is used, PHY parameters for PUSCH transmission may be transmitted through an RRC message (eg, RRC reset message). Therefore, the main parameters for calculating TBS are may be included in TBS can be determined based on Equation 4 below.

" "It can be defined as: may be the number of allocated RBs. R may be the code rate. may be a modulation order. v may be the number of layers. The main parameters for determining TBS are , MCS level, and number of layers. Can be set in the resource setting procedure described above. MCS level is and r included in It can be set by . may mean an MCS table consisting of a list of modulation orders and coding rates. may refer to an index in an MCS table. The number of layers is included in It can be set by .

When CG type 1 configuration is used, parameters required for uplink communication (e.g., period of CG configuration resources, frequency resources, time resources, TBS, etc.) may be set by an RRC reset message. When the setup operation according to the RRC reset message is completed, the terminal may activate the CG (eg, CG configuration resource). “If data to be transmitted according to CG type 1 configuration occurs and CG configuration resources exist,” the terminal can determine the HARQ process ID for transmitting the data based on Equation 5 below. and Is may be included in

FIG. 4 is a flowchart illustrating a first embodiment of an uplink communication method according to a CG type 2 configuration in a communication system.

Referring to FIG. 4, a communication system may include a base station and a terminal. The base station may be the base stations 110-1, 110-2, 110-3, 120-1, and 120-2 shown in FIG. 1, and the terminal may be the terminals 130-1, 130-2, and It may be 130-3, 130-4, 130-5, 130-6). Each of the base station and the terminal may be configured the same or similar to the communication node 200 shown in FIG. 2.

The base station may transmit an RRC reset message including CG configuration setting information (e.g., basic parameters for CG) to the terminal (S401). The terminal can receive an RRC reset message from the base station and check the CG configuration setting information included in the RRC reset message. The terminal may set parameters, resources, and/or operations for uplink communication based on CG configuration setting information (S402). That is, CG may be set in step S402.

The base station may transmit a DCI for CG activation (hereinafter referred to as “activation DCI”) to the terminal (S403). The activated DCI may include period information of CG configuration resources, frequency resource information, time resource information, TBS information, etc. The terminal can receive the activation DCI from the base station and check the information included in the activation DCI. If the information included in the activated DCI is confirmed, the terminal may transmit a MAC CE (control element) for CG confirmation to the base station (S404). When the MAC CE for CG confirmation is received from the terminal, the base station may determine that the activation DCI has been successfully received from the terminal. Step S404 may be an optional operation.

When the activation DCI is received, the terminal may activate the CG (eg, CG configuration resource) (S405). CG configuration resources can be set periodically. When uplink data to be transmitted through the CG configuration resource occurs, the terminal may transmit the uplink data to the base station using the CG configuration resource set by the base station (S406). Additionally, the terminal may start the CG configuration timer at the time of transmission of uplink data. From the start of the CG configuration timer until the end of the CG configuration timer, the UE may perform a monitoring operation of the PDCCH using CS-RNTI in the UE-specific search space.

If a DCI requesting retransmission of uplink data (e.g., DCI including NDI set to 1) is received from the base station before the end of the CG configuration timer, the terminal may perform a retransmission procedure for uplink data. That is, when the NDI included in the DCI is set to 1, the terminal can determine that the resource allocated by the DCI is a retransmission resource. The retransmission procedure of uplink data can be performed using resources indicated by DCI. If a DCI requesting retransmission of uplink data is not received from the base station before the end of the CG configuration timer, the terminal may determine that the uplink data has been successfully received from the base station.

The base station can perform a reception operation of uplink data by performing a monitoring operation on the CG configuration resources (S407). Monitoring operations may be performed periodically. For example, the base station may perform a DMRS detection operation in CG configuration resources (S407-1). The DMRS detection operation may be an autocorrelation operation for the DMRS sequence established between the base station and the terminal.

If the energy level as a result of the detection operation of the DMRS is above the threshold, the base station may determine that uplink data has been transmitted in the CG configuration resource. If the energy level resulting from the detection operation of the DMRS is less than the threshold, the base station may determine that uplink data has not been transmitted in the CG configuration resource. If it is determined that uplink data has been transmitted in the CG resource, the base station may perform a CRC operation on the uplink data obtained from the CG resource (S407-2). If the result of the CRC operation is successful, the base station can perform a decoding operation of uplink data (S407-3). If the result of the CRC operation is failure, the base station can perform a resource allocation procedure for retransmission of uplink data.

Meanwhile, when CG type 2 configuration is used, the basic parameters for CG can be set by an RRC reset message, and the period, frequency resource, time resource, and TBS of the CG configuration resource are DCI for CG activation (i.e. It can be set by activating DCI). The RRC reset message transmitted in step S401 can be used to set the DRB and logical channel of the terminal. The RRC reset message may include the index of the DRB, the LCID mapped to the corresponding DRB, etc. Additionally, the RRC reset message may include parameters (e.g., parameters defined in Table 1) related to a logical channel for performing an LCP operation and a BSR operation in the MAC layer of the terminal.

To indicate that CG Type 2 configuration is applied on the logical channel that is mapped to the DRB, may not be set, and the indices of parameters for CG type 2 configuration applied to the corresponding logical channel are may be included in In this case, the upper layer (e.g., RLC layer) of the terminal may transmit information (e.g., buffer information) indicating that data to be transmitted according to the CG type 2 configuration exists to the MAC layer of the terminal, The MAC layer of the terminal may update buffer information for the logical channel based on the received buffer information. When uplink resources according to the CG Type 2 configuration are generated, the MAC layer of the terminal can generate a MAC PDU using the data stored in the RLC buffer, and send the MAC PDU to the lower layer of the terminal (e.g., PHY layer). can be transmitted to.

RRC reset messages are defined in Table 4 below. may include, May include basic parameters for CG type 2 configuration.

[Cycle setting of CG configuration resources]

The period (e.g., transmission period) of CG configuration resources according to the CG type 2 configuration can be determined based on Equation 6 below. In Equation 6, the parameters may be set by an RRC message (eg, RRC reset message) and DCI (eg, activation DCI).

may be the number of slots per radio frame, may be the number of symbols per slot. , , and may mean the time resource of PUSCH allocated by the activated DCI. is described above It may be a parameter included in . CG configuration resources are "based on the time of the first PUSCH indicated by the activated DCI. "Can be set for each.

[Setting of frequency and time resources]

Frequency and time resources for CG Type 2 configuration can be set by parameters included in the activation DCI. The time resources for CG Type 2 configuration are included in the activating DCI. It can be set by . The value (m) is , PUSCH mapping type, and SLIV. The index (m+1) of can be indicated. K ₂ may mean the interval between the activated DCI and PUSCH in the time domain. SLIV may indicate a combination of the index of the first symbol of the PUSCH resource and the length of the PUSCH resource.

Frequency resources for CG Type 2 configuration are "setting the allocation method of frequency resources (e.g., bitmap or RIV)" "and "setting the resource allocation area (e.g. starting PRB and number of PRBs) according to the allocation method. "It can be set by: may be included in an RRC message (e.g., an RRC reset message), may be included in DCI.

this If set, frequency resources for CG type 2 configuration can be indicated by a bitmap. The total bandwidth can be divided into RBG units and bitmaps (e.g. ) can indicate whether one RBG is configured for CG type 2 configuration. That is, one bit included in the bitmap can be mapped one-to-one with one RBG. The size of the RBG can be determined based on Table 3 described above.

this When set to , the frequency resources for CG type 2 configuration are RIV (e.g. ) can be indicated by. The terminal is included in the activated DCI The starting RB and number of RBs can be derived using the value of (i.e., RIV).

[TBS settings]

If CG type 2 configuration is used, PHY parameters for PUSCH transmission may be transmitted through the active DCI. TBS can be determined based on Equation 4 described above. The main parameters for determining TBS are (i.e., the number of allocated RBs), MCS level, and number of layers. Can be set in the resource setting procedure described above. The MCS level is included in the RRC message. and enable DCI included It can be set by . The number of layers is included in the active DCI. It can be set by .

The base station is configured through Settings-Grant Setting Information ( C ) can be generated and the generated RRC message can be transmitted. Configuration-grant configuration information is information indicating time-frequency resources (hereinafter referred to as “configured-grant (CG) resources”) allocated for uplink communication (e.g., physical uplink shared channel (PUSCH) transmission). It may contain elements (e.g., timeDomainOffset, timeDomainAllocation, frequencyDomainAllocation).

The terminal can receive an RRC message from the base station, check the configuration-grant configuration information included in the received RRC message, and check the CG configuration resources based on the configuration-grant configuration information. CG configuration resources can be set periodically and can always be allocated regardless of whether uplink data is generated.

When uplink data to be transmitted to the base station is generated, the terminal can transmit the uplink data using the CG configuration resources set by the RRC message. Uplink data may be URLLC data (eg, data transmitted to satisfy URLLC requirements).

Meanwhile, when downlink data to be transmitted to the terminal is generated, the base station can generate downlink control information (DCI) including resource allocation information of the PDSCH, and transmit the generated DCI through a physical downlink control channel (PDCCH). there is. The base station can transmit downlink data to the terminal through PDSCH scheduled by DCI.

In addition, the DCI may further include CG configuration resource allocation information, and the CG configuration resource allocation information may indicate one index within the temporal table established by the RRC message (e.g., the temporal table listed in Table 1). there is. The size of the field in which CG configuration resource allocation information is recorded within the DCI may be determined depending on the number of indexes included in the temporal table. If the configuration-grant configuration information does not include a temporal table, the temporal table may be included in the DCI. In this case, the DCI may further include a time table as well as CG configuration resource allocation information.

The base station may transmit DCI including “PDSCH resource allocation information + CG configuration resource allocation information” or “PDSCH resource allocation information + time table + CG configuration resource allocation information” through the PDCCH. The base station can transmit downlink data to the terminal through the PDSCH scheduled by DCI. Here, DCI may be DCI format 1_0 or DCI format 1_1. DCI (e.g., DCI's cyclic redundancy check (CRC) value) may be scrambled by a cell-radio network temporary identifier (C-RNTI) or MCS-C-RNTI.

The terminal can receive DCI from the base station through the PDCCH and can check the PDSCH by checking the information elements included in the received DCI. The terminal can receive downlink data from the base station through PDSCH. Additionally, the UE may obtain CG configuration resource allocation information from the DCI and check the offset, start symbol, and length mapped to CG configuration resource allocation information (e.g., index) within the time table obtained from the RRC message. You can. The terminal can check the CG time resource based on the offset, start symbol, and length. In other words, the terminal uses time-frequency resources (i.e., CG configuration resources) for PUSCH transmission based on the CG frequency resources indicated by the configuration-grant configuration information and the CG time resources indicated by “configuration-grant configuration information and DCI” )can confirm.

When uplink data (eg, URLLC data) is generated in the terminal, the terminal may transmit the uplink data using the CG configuration resources indicated by the RRC message and DCI.

If the UE does not generate a lot of data in the CG configuration transmission, unused radio resources may increase, so the 3GPP standard allows multiple terminals to commonly use the radio resources allocated to the CG configuration transmission. In other words, in rare cases where data from terminals occurs, data collisions rarely occur and the size of radio resources allocated to CG configuration transmission is reduced.

For CG configuration transmission, the time delay and probability of data collision decrease as more wireless resources are allocated, but the size of unused wireless resources may increase. In order to reduce the occurrence of data collisions, the data of the terminals can be repeated k times and the CG configuration transmission can be set to multiple.

Figure 5 is a conceptual diagram showing a first embodiment of multiple CG configurations.

Referring to FIG. 5, in PUSCH k repetitive transmission when k = 4, a plurality of CG configurations may be configured to transmit repeatedly four times during the first PUSCH data transmission region, the second PUSCH data transmission region and/or It can also be configured to transmit repeatedly four times in the 3rd PUSCH data transmission area. Additionally, when the terminal transmits PUSCH data using only one configuration (CG configuration 1), the terminal may have to wait for a certain period of time for repeated PUSCH transmission after the terminal's data is generated. Accordingly, the communication system can set multiple CG configurations so that the waiting time of the terminal is minimized. Additionally, the communication system may be set so that the first transmission time of PUSCH data is different in at least one of CG configuration 1, CG configuration 2, CG configuration 3, and/or CG configuration 4. The terminal can transmit PUSCH data using the CG configuration with the lowest latency from the time the data is generated.

Figure 6 is a conceptual diagram showing a first embodiment of CG configuration transmission of multiple terminals.

Referring to FIG. 6, when terminal A and/or terminal B repeatedly transmit data in PUSCH k repetitive transmission when k=4, terminal A and terminal B select different CG configurations to transmit data to terminal A and/or terminal B. In the CG configuration area where UE B's data transmission does not collide, data from UE A and/or Terminal B can be successfully transmitted to the base station. That is, if terminal A transmits PUSCH data using CG configuration 1 and terminal B transmits PUSCH data using CG configuration 2, the data of terminal A and terminal B are transmitted in some CG configuration areas (512, 513, 514). , 521, 522, and 523), but there is no collision in some of the remaining CG configuration areas (511, 524), so terminal A's PUSCH data 511 and terminal B's PUSCH data 524 are successfully transmitted to the base station. It can be. A communication system using the CG configuration transmission method can allocate terminal common wireless resources rather than terminal-specific wireless resources, and the communication system can also use a k-repeated transmission method or set multiple CG configurations to lower the probability of collision. there is.

Meanwhile, since the base station that received data in the terminal common radio resource area cannot know when and to which terminal the data was generated, the base station may have to blindly receive a number of radio resources allocated in the CG configuration. There may be complexity in that the base station must repeatedly perform reception as many CG configurations as the number of terminals to which it has allocated CG configuration resources. Therefore, there is a need for a data transmission and reception method and device for low-latency services that reduce transmission and reception complexity in CG configuration transmission of multiple terminals in a wireless communication system.

In a communication system using the CG configuration transmission method, the base station can provide CG configuration PUSCH parameters to the terminal, and the terminal can transmit data using the above-described CG configuration PUSCH parameters. At this time, UEs that have received parameters for CG type 1 configuration or CG configuration PUSCH parameters for CG type 2 configuration from the base station may be assigned each UE's CS-RNTI (Configured Scheduling - Radio Network Temporary Identifier) from the base station. When PUSCH data to be transmitted to the base station is generated, the terminal can perform CRC addition, LDPC (low density parity check) channel coding, rate matching, scrambling, and/or modulation on the data. . Here, when the terminal performs scrambling on PUSCH data, the CS-RNTI of each terminal may be input and calculated as the initial scrambling value of the PUSCH data for each different terminal.

Figure 7 is a block diagram showing a first embodiment of a CG configuration PUSCH transmission device that uses CS-RNTI in a scrambling procedure of PUSCH data.

Referring to FIG. 7, the terminal 700 may include a CRC addition unit 710, a channel coding and/or rate matching unit 720, a scrambling unit 730, and/or a modulation unit 740. The CRC adding unit 710 of the terminal 700 may add a CRC to the PUSCH data to be transmitted to the base station (710), and the channel coding and/or rate matching unit 720 of the terminal 700 may add the CRC. Channel coding and/or rate matching can be performed on the PUSCH data. Additionally, the scrambling unit 730 of the terminal 700 may perform scrambling on channel-coded and/or rate-matched PUSCH data using the CS-RNTI allocated from the base station. The modulator 740 of the terminal 700 can modulate the scrambled PUSCH data. The terminal 700 may transmit the modulated signal to the base station.

Figure 8 is a block diagram showing a first embodiment of a CG configuration PUSCH receiving device that uses CS-RNTI in the descrambling procedure of PUSCH data.

Referring to FIG. 8, the base station 800 may include a demodulation unit 810, a descrambling unit 820, a channel decoding and/or de-rate matching unit 830, and/or a CRC check unit 840. . The demodulator 810 of the base station 800 can demodulate the signal received from the terminal, and the descrambling unit 820 of the base station 800 uses CS-RNTI to determine the radio resource area set by the CG configuration parameter. Descrambling is possible. The channel decoding and/or de-rate matching unit 830 of the base station 800 may perform channel decoding and/or de-rate matching on the descrambled PUSCH data. The CRC check unit 840 of the base station 800 can perform a CRC check on the channel decoded and/or de-rate matched PUSCH data, and the base station 1000 can successfully receive the PUSCH data transmitted by the terminal. . Additionally, if no error occurs in the CRC check, the base station 800 can identify the terminal that transmitted PUSCH data using CS-RNTI.

At this time, the base station 800 may need to repeatedly perform descrambling and/or decoding as many times as the number of terminals assigned CS-RNTI and the number of CG configurations. That is, when the base station 800 allocates CS-RNTIs to M terminals, the base station may need to perform a descrambling procedure using the M CS-RNTIs for signals received from the terminals. Additionally, the base station 800 may need to perform decoding M times for each of the M signals obtained using M CS-RNTIs. Additionally, the base station 800 may need to perform descrambling and/or decoding by repeating the resource area set by the CG configuration parameter as many times as the number of CG configurations. Accordingly, the base station may have to perform many operations by repeatedly performing descrambling and/or decoding as many times as the number of terminals and the number of CG configurations, and thus the time delay of the wireless communication system may increase.

Hereinafter, a method of reducing time delay by reducing the complexity of repetitive operations of descrambling and/or channel decoding of PUSCH data performed at the base station 800 may be proposed. To this end, in the PUSCH data scrambling procedure of the terminal 700, instead of performing scrambling using the CS-RNTI assigned to each terminal 700 from the base station 800, the terminal 700 performs scrambling in the CRC addition procedure. A specific identifier (e.g., UE specific CS-RNTI (UE specific CS-RNTI) or a different CRC generation polynomial for each terminal) may be used. Here, the UE-specific CS-RNTI may refer to the CS-RNTI assigned to each UE from the base station. Hereinafter, CRC bits generated using a terminal-specific identifier (terminal-specific CS-RNTI or a CRC generation polynomial different for each terminal) may be referred to as terminal-specific CRC bits. Additionally, the terminal 700 may use a terminal common identifier (eg, common CS-RNTI) commonly used by terminals in the scrambling procedure.

As an example, when the communication system uses the CG configuration transmission method, the base station may allocate a public CS-RNTI and a UE-specific CS-RNTI to the UE. When the UE transmits a CG configuration PUSCH to the base station, the UE may add a CRC to the PUSCH data using the UE-specific CS-RNTI in the CRC addition procedure, and the UE may perform scrambling using the common CS-RNTI in the scrambling procedure. can be performed. Below, a data transmission and reception device for low-latency service in a wireless communication system using public CS-RNTI and/or terminal-specific CS-RNTI is disclosed.

Figure 9 is a block diagram showing a first embodiment of a data transmission and reception device for low-delay service in a wireless communication system.

Referring to FIG. 9, the terminal 900 may include a CRC addition unit 910, a channel coding and/or rate matching unit 920, a scrambling unit 930, and/or a modulation unit 940. The CRC addition unit 910 of the terminal 900 can calculate CRC bits for the PUSCH data using the PUSCH data to be transmitted to the base station, and a data block containing “PUSCH data + CRC bits”. can be created. In addition, the CRC addition unit 910 of the terminal 900 may calculate terminal-specific CRC bits for PUSCH data using the CRC bits and/or the above-described terminal-specific CS-RNTI, and may calculate “PUSCH data + CRC A data block containing “bits + terminal-specific CRC bits” may be generated. The data block may be a transport block (TB) or a code block group (CBG). The channel coding and/or rate matching unit 920 of the terminal 900 may perform channel coding and/or rate matching on a data block containing “PUSCH data + CRC bits + terminal-specific CRC bits”. there is. Additionally, the scrambling unit 930 of the terminal 900 may perform scrambling on channel-coded and/or rate-matched data blocks using the common CS-RNTI described above. The modulator 940 of the terminal 900 can modulate the scrambled data block. The terminal 900 may transmit the modulated signal to the base station. That is, when transmitting a CG configuration PUSCH to the base station, the terminal 900 can use the terminal-specific CS-RNTI for CRC addition and perform scrambling using the common CS-RNTI to transmit data.

Figure 10 is a block diagram showing a second embodiment of a data transmission and reception device for low-delay service in a wireless communication system.

Referring to FIG. 10, the base station 1000 may include a demodulation unit 1010, a descrambling unit 1020, a channel decoding and/or de-rate matching unit 1030, and/or a CRC check unit 1040. . The demodulator 1010 of the base station 1000 can generate a data block by demodulating the signal received from the terminal, and the descrambling unit 1020 of the base station 1000 can generate the resource area set by the CG configuration parameter as described above. Data blocks can be descrambled using the common CS-RNTI. The channel decoding and/or de-rate matching unit 1030 of the base station 1000 may perform channel decoding and/or de-rate matching on the descrambled data block. The CRC check unit 1040 of the base station 1000 may perform a CRC check using the above-described UE-specific CS-RNTI on the channel decoded and/or de-rate matched data block, and the base station 1000 The transmitted PUSCH data can be successfully received. Additionally, if no error occurs in the CRC check, the base station 1000 can identify the terminal that transmitted PUSCH data using the terminal-specific CS-RNTI.

Here, the descrambling unit 1020 of the base station 1000 descrambles the resource area set by the CG configuration parameter using the above-described common CS-RNTI, so that the descrambling unit 1020 of the base station 1000 receives data from the terminal. Desrambling can be performed only once for one data block. Additionally, the channel decoding unit 1030 of the base station can perform decoding on a descrambled data block only once.

As another embodiment, when the communication system uses the CG configuration transmission method, the base station may allocate a common CS-RNTI, a UE-specific CS-RNTI, and/or a different CRC generation polynomial for each UE to the UE. When the terminal transmits a CG configuration PUSCH to the base station, the terminal may generate CRC bits using a different CRC generation polynomial for each terminal in the CRC addition procedure. In the CRC addition procedure, the terminal may generate a data block containing “PUSCH data + CRC bits” using a different CRC generation polynomial for each terminal. The data block may be a transport block (TB) or a code block group (CBG). Additionally, the terminal can perform scrambling on a data block using the common CS-RNTI in the scrambling procedure. Below, a data transmission and reception device for low-delay service in a wireless communication system using a common CS-RNTI, a terminal-specific CS-RNTI, and/or a CRC generation polynomial different for each terminal is disclosed.

Figure 11 is a block diagram showing a third embodiment of a data transmission and reception device for low-delay service in a wireless communication system.

Referring to FIG. 11, the terminal 1100 may include a CRC addition unit 1110, a channel coding and/or rate matching unit 1120, a scrambling unit 1130, and/or a modulation unit 1140. The CRC addition unit 1110 of the terminal 1100 may generate a data block including “PUSCH data + CRC bits” using PUSCH data to be transmitted to the base station and/or a CRC generation polynomial that is different for each terminal. The data block may be a transport block (TB) or a code block group (CBG). Additionally, the channel coding and/or rate matching unit 1120 of the terminal 1100 may perform channel coding and/or rate matching on a data block including “PUSCH data + CRC bits.” Additionally, scrambling 1130 of the terminal 1100 may perform scrambling on channel-coded and/or rate-matched data blocks using the common CS-RNTI described above. The modulator 1140 of the terminal 1100 can modulate the scrambled data block. The terminal 1100 can transmit the modulated signal to the base station. That is, when transmitting a CG configuration PUSCH to the base station, the terminal 1100 can use a different CRC generation polynomial for each terminal for CRC addition and can perform scrambling using the common CS-RNTI to transmit data.

Figure 12 is a block diagram showing a fourth embodiment of a data transmission and reception device for low-delay service in a wireless communication system.

Referring to FIG. 12, the base station 1200 may include a demodulation unit 1210, a descrambling unit 1220, a channel decoding and/or de-rate matching unit 1230, and/or a CRC check unit 1240. . The demodulator 1210 of the base station 1200 can demodulate the signal received from the terminal, and the descrambling unit 1220 of the base station 1200 uses the common CS-RNTI that describes the resource area set by the CG configuration parameter. You can use descrambling. The channel decoding and/or de-rate matching unit 1230 of the base station 1200 may perform channel decoding and/or de-rate matching on the descrambled PUSCH data. The CRC check unit 1040 of the base station 1200 may perform a CRC check on the channel decoded and/or de-rate matched PUSCH data using the above-described UE-specific CS-RNTI, and the base station 1200 may perform a CRC check on the channel decoded and/or de-rate matched PUSCH data. The transmitted PUSCH data can be successfully received. Additionally, if no error occurs in the CRC check, the base station 1200 can identify the terminal that transmitted PUSCH data using a CRC generation polynomial that is different for each terminal.

Here, the descrambling unit 1220 of the base station 1200 descrambles the resource area set by the CG configuration parameter using the above-described common CS-RNTI, so that the descrambling unit 1220 of the base station 1200 receives data from the terminal. Desrambling can be performed only once for one data block. Additionally, the channel decoding unit 1230 of the base station can perform decoding on a descrambled data block only once.

Figure 13 is a flowchart showing a first embodiment of a data transmission and reception method for low-delay service in a wireless communication system.

Referring to FIG. 13, the base station may allocate a public CS-RNTI and/or a terminal-specific CS-RNTI to the terminal, and the terminal may be assigned a public CS-RNTI and/or a terminal-specific CS-RNTI from the base station. There is (S1301). The base station can transmit DCI to the terminal through PDCCH. The terminal can generate a data block including “PUSCH data + CRC value” by adding a CRC to the data to be transmitted to the base station using the terminal-specific CS-RNTI allocated from the base station (S1302). The data block may be a transport block (TB) or a code block group (CBG). After the UE adds the CRC using the UE-specific CS-RNTI, the UE may perform channel coding and/or rate matching on the data block containing “PUSCH data + CRC value” (S1303). After the terminal performs channel coding and/or rate matching on the data block, the terminal may scramble the channel-coded and/or rate-matched data block using the common CS-RNTI (S1304). After the terminal scrambles the channel-coded and/or rate-matched data block, the terminal may transmit a signal generated by modulating the scrambled data block to the base station (S1304).

The base station can receive a signal from the terminal (S1305), and the base station can obtain a data block from the resource scheduled by DCI from the terminal. After receiving a signal from the terminal, the base station can descramble the data block using the common CS-RNTI (S1306). After the base station descrambles the data block using the common CS-RNTI, the base station may perform channel decoding and/or derating matching on the descrambled data block (S1307). After the base station performs channel decoding and/or de-rate matching on the data block, the base station may perform a CRC check on the channel-decoded and/or de-rate matched data block using a UE-specific CS-RNTI. (S1308). A base station that performs a CRC check using the UE-specific CS-RNTI can successfully receive PUSCH data from the UE. Accordingly, the base station can perform descrambling and/or decoding only once using the common CS-RNTI commonly assigned to all terminals.

Figure 14 is a flowchart showing a second embodiment of a data transmission and reception method for low-delay service in a wireless communication system.

Referring to FIG. 14, the base station may allocate a common CS-RNTI, a terminal-specific CS-RNTI, and/or a different CRC generation polynomial for each terminal to the terminal, and the terminal may receive the common CS-RNTI and the terminal-specific CS-RNTI from the base station. A different CRC generation polynomial may be received for each RNTI and/or terminal (S1401). The terminal may generate CRC bits in the PUSCH data to be transmitted to the base station using a different CRC generation polynomial for each terminal received from the base station. The terminal may generate a data block containing “PUSCH data + terminal-specific CRC bits” using a CRC generation polynomial that is different for each terminal (S1402). After the terminal adds a CRC using a CRC generation polynomial that is different for each terminal, the terminal may perform channel coding and/or rate matching on the data block containing “PUSCH data + terminal-specific CRC bits” ( S1403). After the terminal performs channel coding and/or rate matching on a data block containing “PUSCH data + terminal-specific CRC bits,” the terminal performs channel coding and/or rate matching on the data block using the common CS-RNTI. After scrambling the data block using the common CS-RNTI, the terminal can transmit a signal generated by modulating the scrambled data block to the base station (S1405).

The base station can receive a signal from the terminal (S1405), and the base station can obtain a data block from the resource scheduled by DCI from the terminal. After receiving a signal from the terminal, the base station can descramble the data block using the common CS-RNTI (S1406). After the base station descrambles the data block using the common CS-RNTI, the base station may perform channel decoding and/or derating matching on the descrambled data block (S407). After the base station performs channel decoding and/or derating matching on the descrambled data block, the base station performs a CRC check using a CRC generation polynomial that is different for each terminal for the channel decoding and/or derate matched data block. It can be performed (S1408). A base station that performs a CRC check using a CRC generation polynomial that is different for each terminal can successfully receive PUSCH data. Accordingly, the base station can perform descrambling and/or decoding only once using the common CS-RNTI commonly assigned to all terminals.

Meanwhile, the computational amount of LDPC decoding in PUSCH reception may be very large, and accordingly, LDPC decoding may greatly affect the PUSCH reception processing time delay. On the other hand, the computational amount of the CRC check in PUSCH reception may be very small, and the PUSCH reception processing time delay due to the CRC check may be negligible. Below, an example of a method for adding a CRC using a terminal-specific CS-RNTI is described.

Figure 15 is a conceptual diagram showing a first embodiment of a method for adding a CRC using a terminal-specific identifier.

Referring to FIG. 15, the terminal can input PUSCH data 1510 to be transmitted into the CRC addition unit. The CRC adder may calculate the CRC value of the PUSCH data and obtain CRC bits. The above-described CRC bits may be composed of Y bits may be referred to as second CRC bits 1522. The CRC addition unit may generate third CRC bits 1524 (or terminal-specific CRC bits) using the above-described second CRC bits 1522 and/or the terminal-specific CS-RNTI (1523). there is. Here, the CRC addition unit may generate the third CRC bits 1524 by performing an XOR operation on the above-described second CRC bits 1522 and/or the terminal-specific CS-RNTI 1523. The CRC adder may generate the CRC 1520 by combining the first CRC bits 1521 and the third CRC bits 1524. The CRC adding unit may generate a data block by adding the CRC 1520, which is a combination of the above-described first CRC bits 1521 and third CRC bits 1524, to the PUSCH data 1510. The CRC addition unit may input the generated data block to the channel coding unit.

In other words, the CRC addition unit may not perform an XOR operation with the UE-specific CS-RNTI for (X-Y) bits among the A UE-specific CS-RNTI and XOR operation can be performed on Y bits among the X bits of CRC bits obtained by calculation.

The terminal can transmit a signal to the base station using the method of adding a CRC using the terminal-specific identifier described above. The base station that receives the above-described signal from the terminal can perform decoding and then perform a CRC check with the terminal-specific CS-RNTI to identify which terminal transmitted the data. That is, if the base station assigns CS-RNTI A, CS-RNTI B, and CS-RNTI C to terminal A, terminal B, and terminal C, respectively, the base station performs decoding and then assigns CS-RNTI A, CS-RNTI B, and /Or, a CRC check can be performed on each CS-RNTI C to identify which terminal transmitted the data.

As another example of a method of adding a CRC using a terminal-specific identifier, the terminal may generate a terminal-specific CRC using a 24-bit CRC generator polynomial allocated differently for each terminal. For this purpose, the base station provides terminal A with the first CRC generation polynomial (or, ) can be assigned, and the base station provides terminal B with a second CRC generation polynomial (or, ) can be assigned, and the third CRC generation polynomial (or, ) can be assigned. The first to third CRC generation polynomials described above may mean different CRC polynomials. Also here: , , It can mean.

The terminal can transmit a signal to the base station using the method of adding a CRC using the terminal-specific identifier described above. After receiving the above-described signal from the terminal, the base station performs decoding and then assigns CRC generation polynomials differently for each terminal (terminal A, terminal B, terminal C) ( , , ) can be used to perform a CRC check to identify whether the terminal transmitting data is terminal A, terminal B, or terminal C. That is, the base station sends terminal A the first CRC generation polynomial (or, ) is assigned, and the base station provides terminal B with the second CRC generation polynomial (or, ) is assigned, and the third CRC generation polynomial (or, ), the base station performs decoding and then , and/or You can perform a CRC check using to identify whether the terminal transmitting data is terminal A, terminal B, or terminal C. Meanwhile, the base station can determine whether the terminal transmitted data in the CG configuration area based on the size of the Dedicated deModulation Reference Signal (DMRS) signal in the CG configuration PUSCH.

If an error occurs in the data transmitted by the terminal, or if the terminals transmit using the same CG configuration resource, the probability that the base station successfully receives data through the CRC check may be low. When a plurality of terminals perform scrambling using each terminal's CS-RNTI and transmit signals to the base station using the same CG configuration resources, the base station performs descrambling using each terminal's CS-RNTI to DMRS signals can be received. However, when multiple terminals perform scrambling using a common CS-RNTI and transmit signals to the base station using the same CG configuration resources, the base station may have a high probability of receiving an amplified DMRS signal.

Therefore, when a plurality of terminals perform scrambling using a common CS-RNTI and transmit signals to the base station using the same CG configuration resources, the base station can receive the amplified DMRS signal. When the base station receives the amplified DMRS signal, the base station may determine that multiple terminals have transmitted the PUSCH using the same CG configuration resource. Additionally, when the base station receives the amplified DMRS signal, the base station may request retransmission of uplink data from at least one terminal.

Figure 16 is a flowchart showing a first embodiment of the uplink data transmission procedure of the terminal.

Referring to FIG. 16, terminal A can transmit a CG configuration PUSCH to the base station using the CG configuration (S1601), and terminal B can transmit a CG configuration PUSCH to the base station using the CG configuration. At this time, when terminal A and terminal B transmit the CG configuration PUSCH using the same CG configuration, the base station can detect a collision of the CG configuration PUSCH (S1603). After detecting a collision of the CG configuration PUSCH, the base station may request retransmission from terminal A and/or terminal B (S1604, S1605). Terminal A, which has received a retransmission request, can retransmit uplink data to the base station (S1606). Terminal B, which has received a retransmission request from the base station, can retransmit uplink data to the base station (S1607).

In the step of detecting a collision of the CG configuration PUSCH (S1603), the base station detects a collision of a plurality of terminals when the power of the DMRS received signal is greater than a predetermined first value (for example, the average power value of the DMRS received signal). It can be determined that PUSCH is transmitted using the same CG configuration resource. In addition, when the power of the DMRS received signal is greater than a predetermined first value (e.g., the average power value of the DMRS received signal), the base station sends a DCI requesting retransmission of the terminal to at least one terminal through the PDCCH. can be transmitted. Additionally, the above-described first predetermined value may be determined according to the wireless channel environment.

Additionally, in the step where the base station requests retransmission from terminal A and/or terminal B (S1604, S1605), the base station transmits a DCI requesting retransmission of the terminal to terminal A and/or terminal B through the PDCCH and uplinks the terminal to the terminal. You can request retransmission of link data. Here, since the base station may not be able to identify the terminal where a data collision occurred, the base station can scramble the DCI requesting retransmission of the terminal using the common CS-RNTI. For example, the base station can scramble the CRC value of the DCI requesting retransmission by the terminal using the common CS-RNTI. That is, the base station can transmit a scrambled DCI to at least one terminal using the common CS-RNTI and request retransmission from the terminal. Additionally, the base station can transmit a scrambled DCI to at least one terminal using the above-described common CS-RNTI, allowing the terminal to perform retransmission in a pre-reserved resource region. The base station may receive uplink data from the terminal based on at least one piece of information included in the DCI requesting retransmission from the terminal.

FIG. 17 is a conceptual diagram illustrating a first embodiment of a method in which a base station transmits a DCI requesting retransmission of a terminal to at least one terminal.

Referring to FIG. 17, terminal A and terminal B can use the same CG configuration in CG configuration PUSCH transmission, and terminal A and terminal B can use the same CG configuration resource to transmit CG configuration PUSCH data to the base station. When terminal A and terminal B transmit signals to the base station using the same CG configuration resources, the base station uses the common CS-RNTI described above in the descrambling procedure of the PUSCH data associated with the signal received from at least one terminal. You can. After the base station performs descrambling of the PUSCH data associated with the signal received from at least one terminal, the base station transmits the PUSCH to the same CG configuration resource by multiple terminals at the power size of the DMRS received signal included in the CG configuration PUSCH. It can be judged that it was done.

If the power level of the above-described DMRS received signal is greater than or equal to the first predetermined value, the base station may determine that a plurality of terminals have transmitted the PUSCH using the same CG configuration resource. That is, the base station can detect a CG configuration PUSCH transmission collision between multiple terminals based on the power size of the DMRS received signal included in the CG configuration PUSCH. Additionally, when the power level of the above-described DMRS received signal is greater than the predetermined first value, the base station may request retransmission of uplink data from at least one terminal. At this time, the base station transmits a predetermined time (e.g., ) can transmit a DCI requesting retransmission to at least one terminal described above.

At least one terminal may receive a DCI requesting retransmission from the base station by monitoring and/or blind decoding the PDCCH channel. Additionally, at least one terminal can receive the above-described DCI using the common CS-RNTI. At least one terminal can obtain retransmission request information from the base station by receiving a DCI requesting retransmission from the base station. At least one terminal may receive a DCI requesting retransmission from the base station and obtain information necessary for retransmission of the terminal.

Among the terminals that have received a DCI requesting retransmission from the base station, at least one terminal in which a data collision occurred during PUSCH transmission can retransmit uplink data to the base station. In addition, at least one terminal in which a data collision occurred during PUSCH transmission may retransmit uplink data to the base station based on information necessary for the terminal's retransmission included in the DCI requesting retransmission of the terminal. Among the terminals that have received a DCI requesting retransmission from the base station, at least one terminal in which a data collision occurred during PUSCH transmission can retransmit uplink data using different retransmission reservation resources. Here, the above-mentioned retransmission reservation resource can be reserved by the base station through RRC signaling, and the base station reserves a predetermined time interval and/or a predetermined frequency interval from the resource of the PDCCH requesting retransmission to each terminal as a retransmission reservation resource. can do.

Figure 18 is a conceptual diagram showing a first embodiment of a retransmission reservation resource used for retransmission of uplink data of a terminal.

Referring to FIG. 18, the base station may inform each terminal of the frequency interval between PDCCH resources and retransmission resources and/or the time interval between PDCCH resources and retransmission resources through RRC signaling. Terminal A has a frequency interval between the PDCCH resources received through RRC signaling from the base station and the retransmission resources ( ) and/or the time interval between the PDCCH resource and the retransmission resource ( ) Based on this, uplink data can be retransmitted to the base station. Terminal B has a frequency interval between the PDCCH resources received through RRC signaling from the base station and the retransmission resources ( ) and/or the time interval between the PDCCH resource and the retransmission resource ( ) Based on this, uplink data can be retransmitted to the base station. Terminal A and Terminal B may retransmit uplink data to the base station using different resources based on the frequency interval between the PDCCH resource and the retransmission resource and/or the time interval between the PDCCH resource and the retransmission resource, respectively, received through RRC signaling. You can.

As an embodiment, terminal A determines the frequency resource location of the PDCCH carrying a DCI requesting retransmission of the terminal from the base station and the frequency interval between the resource of the PDCCH received through RRC signaling from the base station and the retransmission resource ( ) Based on this, the frequency resource for retransmitting uplink data to the base station can be determined. In addition, terminal A determines the time resource location of the PDCCH carrying the DCI requesting retransmission of the terminal from the base station and the time interval between the resource of the PDCCH received through RRC signaling from the base station and the retransmission resource ( ) Based on this, time resources for retransmitting uplink data to the base station can be determined.

Terminal B determines the frequency resource location of the PDCCH carrying the DCI requesting retransmission of the terminal from the base station and the frequency interval between the retransmission resource and the PDCCH resource received through RRC signaling from the base station ( ) Based on this, the frequency resource for retransmitting uplink data to the base station can be determined. In addition, terminal B determines the time resource location of the PDCCH carrying the DCI requesting retransmission of the terminal from the base station and the time interval between the resource of the PDCCH received through RRC signaling from the base station and the retransmission resource ( ) Based on this, time resources for retransmitting uplink data to the base station can be determined.

Each terminal can transmit uplink data retransmitted to the base station without repetition, and each terminal may not receive a retransmission request from the base station even after a predetermined time has passed from the time of transmitting and/or retransmitting uplink data to the base station. , the terminal can determine that the data has been successfully transmitted to the base station.

The operation of the method according to the embodiment of the present invention can be implemented as a computer-readable program or code on a computer-readable recording medium. Computer-readable recording media may include all types of recording devices that store information that can be read by a computer system. Additionally, computer-readable recording media can be distributed across networked computer systems so that computer-readable programs or codes can be stored and executed in a distributed manner.

Additionally, computer-readable recording media may include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Program instructions may include not only machine language code such as that created by a compiler, but also high-level language code that can be executed by a computer using an interpreter, etc.

Although some aspects of the invention have been described in the context of an apparatus, it may also refer to a corresponding method description, where a block or device may correspond to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be represented by corresponding blocks or items or features of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as a microprocessor, programmable computer, or electronic circuit, for example. In some embodiments, at least one or more of the most important method steps may be performed by such an apparatus.

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

Although the present invention has been described with reference to preferred embodiments of the present invention, those skilled in the art may make various modifications and changes to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. You will understand that it is possible.

Claims (18)

As a method of operating a terminal in a communication system,
Receiving a message including UE (User Equipment)-specific identifier information and common identifier information from a base station;
Generating terminal-specific CRC (Cyclic Redundancy Check) bits for data to be transmitted to the base station using the terminal-specific identifier;
generating a data block containing the data and the terminal-specific CRC bits;
performing channel coding on the data block;
performing scrambling on the data block on which the channel coding was performed using the common identifier; and
A method of operating a terminal, comprising transmitting a signal generated by modulating the scrambling data block to the base station. In claim 1,
The step of generating the terminal-specific CRC bits is,
performing a CRC operation on the data to obtain CRC bits including first CRC bits and second CRC bits; and
Generating third CRC bits by performing an operation on the second CRC bits using the terminal-specific identifier,
The step of generating the data block is,
A method of operating a terminal, comprising generating a data block including the data, the first CRC bits, and the third CRC bits. In claim 1,
The terminal-specific identifier is a terminal-specific Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) associated with the terminal, and the public identifier is a public CS-RNTI commonly assigned to the terminal. . In claim 2,
The step of generating third CRC bits by performing an operation on the second CRC bits is:
A method of operating a terminal, characterized in that generating the third CRC bits by performing an exclusive OR (XOR) operation between the second CRC bits and the terminal-specific identifier. In claim 1,
The terminal-specific identifier information includes CRC generation polynomial information set differently for each terminal,
The step of generating the terminal-specific CRC bits is,
A method of operating the terminal, characterized in that generating the terminal-specific CRC bits using the CRC generation polynomial. In claim 1,
Further comprising receiving a retransmission request from the base station,
The retransmission request is Downlink Control Information (DCI) transmitted through a Physical Downlink Control Channel (PDCCH), and the terminal receives the DCI using the public identifier. In claim 6,
Receiving retransmission reservation resource information, which is a resource for transmitting retransmission data, from the base station through RRC (Radio Resource Control) signaling; and
A method of operating a terminal further comprising transmitting the retransmission data to the base station based on the retransmission reservation resource information. In claim 7,
The retransmission reservation resource information includes a frequency interval between the PDCCH resource and the retransmission resource and a time interval between the PDCCH resource and the retransmission resource. As a method of operating a base station in a communication system,
Transmitting a message including UE (User Equipment)-specific identifier information and common identifier information to a terminal;
Transmitting Downlink Control Information (DCI) to the terminal through a Physical Downlink Control Channel (PDCCH);
Obtaining a data block from a resource scheduled by the DCI from the terminal;
performing descrambling on the data block using the public identifier;
performing channel decoding on the descrambling data block; and
A method of operating a base station, comprising performing a CRC (Cyclic Redundancy Check) check on the data block on which the channel decoding has been performed using the terminal-specific identifier. In claim 9,
The terminal-specific identifier is a terminal-specific Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) associated with the base station, and the public identifier is a public CS-RNTI commonly assigned to the terminal. . In claim 9,
The terminal-specific identifier further includes CRC generation polynomial information set differently for each terminal. In claim 11,
The step of performing a CRC (Cyclic Redundancy Check) check on the data block on which the channel decoding has been performed is:
A method of operating a base station, characterized in that performing a CRC check using the CRC generation polynomial. In claim 9,
A method of operating a base station further comprising requesting the terminal to retransmit data when the received signal power of the Dedicated deModulation Reference Signal (DMRS) for the data block is greater than or equal to a predetermined value. In claim 13,
When the received signal power of the DMRS for the data block is greater than a predetermined value, requesting retransmission of data to the base station includes,
A method of operating a base station, characterized in that by transmitting scrambled Downlink Control Information (DCI) using the public identifier through a Physical Downlink Control Channel (PDCCH) to request retransmission of data from the terminal. As a terminal in a communication system,
A CRC adding unit that generates a data block by adding a CRC (Cyclic Redundancy Check) generated using a terminal-specific identifier to data;
a channel coding unit that performs channel coding on the data block;
a scrambling unit that performs scrambling on the channel-coded data block using a common identifier; and
A terminal comprising a modulator that modulates the scrambling data block. In claim 15,
The terminal, characterized in that the terminal-specific identifier is a terminal-specific Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) associated with the terminal, and the public identifier is a public CS-RNTI commonly assigned to the terminal. In claim 15,
The CRC generated using the terminal-specific identifier is a CRC generated by performing an exclusive OR (XOR) operation between CRC bits of data to be transmitted to the base station and the terminal-specific identifier. In claim 15,
The CRC is characterized in that it is generated using a CRC generation polynomial set differently for each terminal.