KR102589485B1 - Method and apparatus for transmission of uplink phase tracking reference signal in wireless communication system - Google Patents

Abstract

This disclosure relates to a communication technique and system that integrates a 5G communication system with IoT technology to support higher data transmission rates after the 4G system. This disclosure provides intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied.

Description

Method and apparatus for transmitting an uplink phase estimation reference signal in a wireless communication system {METHOD AND APPARATUS FOR TRANSMISSION OF UPLINK PHASE TRACKING REFERENCE SIGNAL IN WIRELESS COMMUNICATION SYSTEM}

The present invention relates to a wireless communication system, and more specifically, to a method and device for transmitting an uplink phase estimation reference signal.

In order to meet the increasing demand for wireless data traffic following the commercialization of the 4G communication system, efforts are being made to develop an improved 5G communication system or pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is called a Beyond 4G Network communication system or a Post LTE system. To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (such as the 60 gigabit (80GHz) band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, to improve the network of the system, the 5G communication system uses advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), and ultra-dense networks. , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation. Technology development is underway. In addition, the 5G system uses FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), which are advanced coding modulation (ACM) methods, and advanced access technologies such as FBMC (Filter Bank Multi Carrier) and NOMA. (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

Meanwhile, the Internet is evolving from a human-centered network where humans create and consume information to an IoT (Internet of Things) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection to cloud servers, etc., is also emerging. In order to implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. Recently, sensor networks for connection between things, and machine to machine communication (Machine to Machine) are required to implement IoT. , M2M), and MTC (Machine Type Communication) technologies are being researched. In an IoT environment, intelligent IT (Internet Technology) services that create new value in human life can be provided by collecting and analyzing data generated from connected objects. IoT is used in fields such as smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliances, and advanced medical services through the convergence and combination of existing IT (information technology) technology and various industries. It can be applied to .

Accordingly, various attempts are being made to apply the 5G communication system (5th generation communication system, or New Radio (NR)) to the IoT network. For example, technologies such as sensor network, Machine to Machine (M2M), and MTC (Machine Type Communication) are being implemented by 5G communication technologies such as beam forming, MIMO, and array antenna. . The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of the convergence of 3eG technology and IoT technology.

As various services can be provided as described above and with the development of wireless communication systems, there is a need for a method to provide these services smoothly.

The disclosed embodiment can provide a method and apparatus for transmitting an uplink phase estimation reference signal in a wireless communication system.

The present invention to solve the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

The technical problems to be achieved by this disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by those skilled in the art from the description below. You will be able to.

According to the present disclosure, the uplink transmission performance of the terminal can be improved by determining whether an uplink phase estimation reference signal is transmitted and setting a transmission method in a wireless communication system.

Figure 1 is a diagram showing the time-frequency domain transmission structure of LTE, LTE-A, NR, or similar wireless communication systems.
Figure 2 shows an expanded frame structure according to some one embodiment.
3 shows an expanded frame structure according to some other embodiments.
Figure 4 shows an expanded frame structure according to some further embodiments.
FIG. 5 is a diagram illustrating an example of settings for a bandwidth portion in a 5G communication system according to some embodiments.
FIG. 6 is a diagram illustrating a method for indicating and changing a bandwidth portion according to some embodiments.
Figure 7 is a diagram illustrating an example of PDSCH or PUSCH frequency axis resource allocation according to some embodiments.
FIG. 8 is a diagram illustrating an example of PDSCH or PUSCH time axis resource allocation according to some embodiments.
FIG. 9 is a diagram for explaining the structure of a downlink control channel of a next-generation mobile communication system according to an embodiment of the present disclosure.
FIG. 10 is a diagram illustrating a base station and terminal wireless protocol structure when performing single cell, carrier aggregation, and dual connectivity according to an embodiment of the present disclosure.
FIG. 11 is a block diagram illustrating the presence or absence of uplink PT-RS transmission for scheduled or activated PUSCH transmission in DCI format 0_0 according to some embodiments.
FIG. 12 is a block diagram illustrating the presence or absence of uplink PT-RS transmission for PUSCH transmission scheduled or activated in DCI format 0_1 or based on the configured grant method according to some embodiments.
Figure 13 is a block diagram showing a terminal structure according to some embodiments.
Figure 14 is a block diagram illustrating a base station structure according to some embodiments.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

In describing the embodiments, description of technical content that is well known in the technical field to which this disclosure belongs and that is not directly related to this disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanation.

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically shown. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the embodiments of the present disclosure are merely intended to ensure that the present disclosure is complete and are within the scope of common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory The instructions stored in may also be capable of producing manufactured items containing instruction means to perform the functions described in the flow diagram block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it may be possible for the blocks to be performed in reverse order depending on the corresponding function.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' performs certain roles. do. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, according to some embodiments, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and processes. Includes scissors, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, according to some embodiments, '˜unit' may include one or more processors.

Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the attached drawings. In the following description of the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification. Hereinafter, the base station is the entity that performs resource allocation for the terminal and may be at least one of gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or node on the network. A terminal may include a UE (User Equipment), MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above examples.

Hereinafter, this disclosure describes technology for a terminal to receive broadcast information from a base station in a wireless communication system. This disclosure relates to a communication technique and system that integrates a 5G communication system with IoT technology to support higher data transmission rates after the 4G system. This disclosure provides intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. ) can be applied.

Terms used in the following description include terms referring to broadcast information, terms referring to control information, terms related to communication coverage, terms referring to state changes (e.g., events), and network entities. Terms referring to messages, terms referring to messages, and terms referring to components of a device are provided as examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

For convenience of explanation below, some terms and names defined in the 3GPP (3rd generation partnership project) LTE (long term evolution) or 3GPP NR (new radio) specifications may be used. However, the present disclosure is not limited by the above terms and names, and can be equally applied to systems complying with other standards.

Wireless communication systems have moved away from providing early voice-oriented services to, for example, 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), and LTE-Advanced. Broadband wireless that provides high-speed, high-quality packet data services such as communication standards such as (LTE-A), LTE-Pro, 3GPP2's High Rate Packet Data (HRPD), UMB (Ultra Mobile Broadband), and IEEE's 802.16e. It is evolving into a communication system.

As a representative example of a broadband wireless communication system, the LTE system uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (DL), and SC-FDMA (Single Carrier Frequency Division Multiple Access) in the uplink (UL). ) method is adopted. Uplink refers to a wireless link in which a terminal (UE (User Equipment) or MS (Mobile Station)) transmits data or control signals to a base station (eNode B, or base station (BS)), and downlink refers to a wireless link in which the base station transmits data or control signals to the base station (eNode B, or base station (BS)). It refers to a wireless link that transmits data or control signals. The multiple access method described above distinguishes each user's data or control information by allocating and operating the time-frequency resources to carry data or control information for each user so that they do not overlap, that is, orthogonality is established. .

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect the various requirements of users and service providers, so services that satisfy various requirements must be supported. Services considered for the 5G communication system include Enhanced Mobile BroadBand (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC). etc.

According to some embodiments, eMBB aims to provide more improved data transmission rates than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink from the perspective of one base station. At the same time, an increased user perceived data rate of the terminal must be provided. In order to meet these requirements, improvements in transmission and reception technology are required, including more advanced Multi Input Multi Output (MIMO) transmission technology. Additionally, the data transmission speed required by the 5G communication system can be satisfied by using a frequency bandwidth wider than 20MHz in the 3~6GHz or above 6GHz frequency band instead of the 2GHz band used by the current LTE.

At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. In order to efficiently provide the Internet of Things, mMTC may require support for access to a large number of terminals within a cell, improved coverage of terminals, improved battery time, and reduced terminal costs. Since the Internet of Things provides communication functions by attaching various sensors and various devices, it must be able to support a large number of terminals (for example, 1,000,000 terminals/km ² ) within a cell. Additionally, due to the nature of the service, terminals that support mMTC are likely to be located in shadow areas that cannot be covered by cells, such as the basement of a building, so they may require wider coverage than other services provided by the 5G communication system. A terminal that supports mMTC must be configured as a low-cost terminal, and since it is difficult to frequently replace the terminal's battery, a very long battery life time may be required.

Lastly, in the case of URLLC, it is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, As a service used for unmanned aerial vehicles, remote health care, emergency alerts, etc., it must provide communications that provide ultra-low latency and ultra-reliability. For example, services that support URLLC must satisfy air interface latency of less than 0.5 milliseconds and have a packet error rate of less than 10-5. Therefore, for services supporting URLLC, the 5G system must provide a smaller Transmit Time Interval (TTI) than other services, and at the same time, design requirements are required to allocate wide resources in the frequency band. However, the above-described mMTC, URLLC, and eMBB are only examples of different service types, and the service types to which this disclosure is applied are not limited to the above-described examples.

The services considered in the 5G communication system described above must be integrated and provided based on one framework. In other words, for efficient resource management and control, it is desirable for each service to be integrated, controlled, and transmitted as a single system rather than operating independently.

In addition, hereinafter, embodiments of the present disclosure will be described using the LTE, LTE-A, LTE Pro or NR system as an example, but the embodiments of the present disclosure can also be applied to other communication systems with similar technical background or channel type. Additionally, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge. Hereinafter, the frame structures of LTE, LTE-A, and 5G systems will be described with reference to the drawings, and the design direction of the 5G system will be explained.

Figure 1 is a diagram showing the time-frequency domain transmission structure of LTE, LTE-A, NR, or similar wireless communication systems.

Figure 1 shows the LTE, LTE-A, and NR systems based on Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (CP-OFDM) or Single Carrier-Frequency Division Multiple Access (SC-FDMA) waveform. It represents the basic structure of the time-frequency resource area, which is a radio resource area where data or control channels are transmitted.

In Figure 1, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. Uplink (UL: uplink) may refer to a wireless link through which a terminal transmits data or control signals to a base station, and downlink (DL: downlink) refers to a wireless link through which a base station transmits data or control signals to a terminal. can do.

The minimum transmission unit in the time domain of LTE, LTE-A and NR systems is an OFDM symbol or SC-FDMA symbol, and N _symb (1-05) symbols can be gathered to form one slot (1-15). . In the case of LTE and LTE-A, two slots consisting of N _symb =7 symbols can be gathered to form one subframe (1-40). Additionally, according to some embodiments, 5G may support two types of slot structures: slot and mini-slot (mini-slot or non-slot). For 5G slots, N _symb can have a value of either 7 or 14, and for 5G minislots, N _symb can be set to one of the values of 1, 2, 3, 4, 5, 6, or 7. In LTE and LTE-A, the length of the slot is 0.5ms and the length of the subframe is fixed at 1.0ms, but in the NR system, the length of the slot or minislot can be flexibly changed depending on the subcarrier spacing. In LTE and LTE-A, a radio frame (1-35) is a time domain unit consisting of 10 subframes. In LTE and LTE-A, the minimum transmission unit in the frequency domain is a subcarrier of 15kHz (subcarrier spacing = 15kHz), and the overall system transmission bandwidth is a total of N _BW (1-10) subcarriers. It is composed. The flexible expandable frame structure of the NR system will be described later.

The basic unit of resources in the time-frequency domain is a resource element (1-30, Resource Element; RE), which can be expressed as an OFDM symbol or SC-FDMA symbol index and subcarrier index. Resource Block (1-20, Resource Block; RB or Physical Resource Block; PRB) consists of N _symb (1-05) consecutive OFDM symbols or SC-FDMA symbols in the time domain and N _RB (1-25) in the frequency domain. It can be defined as two consecutive subcarriers. Therefore, one RB (1-20) is composed of N _symb x N _RB REs (1-30). In LTE and LTE-A systems, data is mapped in units of RB, and the base station performs scheduling in units of RB-pairs constituting one subframe for a given terminal. The number of SC-FDMA symbols or the number of OFDM symbols, N _symb , is determined according to the length of the Cyclic Prefix (CP) added to each symbol to prevent interference between symbols. For example, when a general CP is applied, N _symb = 7, When extended CP is applied, N _symb = 6. Extended CP can be applied to systems where the radio wave transmission distance is relatively larger than that of regular CP, thereby maintaining orthogonality between symbols.

According to some embodiments, subcarrier spacing, CP length, etc. are essential information for OFDM transmission and reception, and smooth transmission and reception can be possible only when the base station and the terminal recognize each other as a common value.

The frame structure of the LTE and LTE-A systems as described above is designed in consideration of typical voice/data communications, and is subject to limitations in scalability to satisfy various services and requirements, such as the NR system. Therefore, in the NR system, it is necessary to define and operate the frame structure flexibly, taking into account various services and requirements.

2 to 4 are diagrams illustrating an expandable frame structure according to some embodiments.

The examples shown in FIGS. 2 to 4 may include subcarrier spacing, CP length, slot length, etc. as a set of essential parameters defining an extended frame structure.

In the early stages of introduction of the 5G system in the future, at least coexistence or dual mode operation with the existing LTE/LTE-A system is expected. Through this, the existing LTE/LTE-A can provide stable system operation, and the 5G system can provide improved services. Therefore, the extended frame structure of the 5G system needs to include at least the frame structure or essential parameter set of LTE/LTE-A. Referring to FIG. 2, it shows a 5G frame structure or essential parameter set, such as the frame structure of LTE/LTE-A. The frame structure type A shown in FIG. 2 shows that the subcarrier interval is 15kHz, 14 symbols constitute a 1ms slot, and 12 subcarriers (=180kHz = 12 x 15kHz) constitute a PRB (Physical Resource Block).

Referring to FIG. 3, the frame structure type B shown in FIG. 3 shows that the subcarrier interval is 30kHz, 14 symbols constitute a 0.5ms slot, and 12 subcarriers (=360kHz = 12x30kHz) constitute a PRB. In other words, compared to frame structure type A, the subcarrier interval and PRB size are doubled, and the slot length and symbol length are doubled.

Referring to FIG. 4, the frame structure type C shown in FIG. 4 shows that the subcarrier interval is 60kHz, 14 symbols constitute a 0.25ms subframe, and 12 subcarriers (=720kHz = 12x60kHz) constitute a PRB. . In other words, compared to frame structure type A, the subcarrier spacing and PRB size are 4 times larger, and the slot length and symbol length are 4 times smaller.

That is, if the frame structure type is generalized, essential parameter sets such as subcarrier interval, CP length, slot length, etc. have an integer multiple relationship with each other for each frame structure type, thereby providing high scalability. Additionally, a subframe with a fixed length of 1 ms can be defined to represent a reference time unit that is unrelated to the frame structure type. Therefore, in frame structure type A, one subframe consists of one slot, in frame structure type B, one subframe consists of two slots, and in frame structure type C, one subframe consists of four slots. It is composed. Of course, the expandable frame structure is not limited to the frame structure types A, B, or C described above, and can also be applied to other subcarrier spacings such as 120kHz and 240kHz and may have different structures.

According to some embodiments, the frame structure type described above can be applied in response to various scenarios. In terms of cell size, the longer the CP length, the larger cells can be supported, so frame structure type A can support relatively larger cells than frame structure types B and C. From the operating frequency band perspective, the larger the subcarrier spacing, the more advantageous it is for phase noise recovery in the high frequency band, so frame structure type C can support a relatively higher operating frequency than frame structure types A and B. From a service perspective, a shorter subframe length is more advantageous to support ultra-low-latency services such as URLLC, so frame structure type C is relatively more suitable for URLLC service than frame structure types A and B.

Additionally, multiple frame structure types can be multiplexed and integrated within one system.

In NR, one component carrier (CC) or serving cell can consist of up to 250 or more RBs. Therefore, if the terminal always receives the entire serving cell bandwidth, such as in LTE, the power consumption of the terminal may be extreme. To solve this, the base station sets one or more bandwidth parts (BWP) to the terminal so that the terminal can operate within the cell. It is possible to support changing the receiving area. In NR, the base station can set 'initial BWP', which is the bandwidth of CORESET #0 (or common search space, CSS), to the terminal through MIB. Afterwards, the base station sets the initial BWP (first BWP) of the terminal through RRC (radio resource control) signaling and provides at least one BWP configuration information that can be indicated through DCI (downlink control information) in the future. You can notify. Afterwards, the base station can indicate which band the terminal will use by announcing the BWP ID through DCI. If the terminal cannot receive DCI from the currently assigned BWP for a certain period of time or more, the terminal returns to 'default BWP' and attempts to receive DCI.

FIG. 5 is a diagram illustrating an example of settings for a bandwidth portion in an NR communication system according to some embodiments.

Referring to Figure 5, the terminal bandwidth (5-00) can be set to two bandwidth parts, that is, bandwidth part #1 (5-05) and bandwidth part #2 (5-10). The base station can set one or multiple bandwidth parts to the terminal, and can set the following information for each bandwidth part.

[Table 1]

In addition to the setting information in [Table 1], various parameters related to the bandwidth can be set to the terminal. Configuration information can be delivered from the base station to the terminal through upper layer signaling, for example, RRC signaling. Among one or multiple bandwidth portions set, at least one bandwidth portion may be activated. Whether to activate the set bandwidth portion can be semi-statically transmitted from the base station to the terminal through RRC signaling, or dynamically transmitted through MAC (medium access control) CE (control element) or DCI.

Setting the bandwidth supported by the 5G communication system can be used for various purposes.

For example, if the bandwidth supported by the terminal is smaller than the system bandwidth, this can be supported through partial bandwidth settings. For example, in [Table 1], by setting the frequency location (setting information 1) of the bandwidth portion to the terminal, the terminal can transmit and receive data at a specific frequency location within the system bandwidth.

As another example, for the purpose of supporting different numerologies, the base station may set multiple bandwidth portions for the terminal. For example, in order to support both data transmission and reception using a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz for a certain terminal, the two bandwidth portions can be set to use subcarrier spacings of 15kHz and 30kHz, respectively. Different bandwidth portions can be frequency division multiplexed (FDM), and when data is to be transmitted and received at a specific subcarrier interval, the bandwidth portion set at the corresponding subcarrier interval can be activated.

As another example, for the purpose of reducing power consumption of the terminal, the base station may set bandwidth portions with different sizes of bandwidth to the terminal. For example, if the terminal supports a very large bandwidth, for example, 100 MHz, and always transmits and receives data through that bandwidth, it may cause very large power consumption. In particular, in a situation where there is no traffic, it is very inefficient in terms of power consumption for the terminal to monitor unnecessary downlink control channels for a large bandwidth of 100 MHz. Therefore, for the purpose of reducing the power consumption of the terminal, the base station can set a relatively small bandwidth portion, for example, a bandwidth portion of 20 MHz, to the terminal. In a situation where there is no traffic, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, data can be transmitted and received using the 100 MHz bandwidth portion according to the instructions of the base station.

FIG. 6 is a diagram illustrating a dynamic setting instruction and change method for a bandwidth portion according to some embodiments.

As described in [Table 1] above, the base station can set one or multiple bandwidth parts to the terminal, and the settings for each bandwidth part include the bandwidth of the bandwidth part, the frequency location of the bandwidth part, and the numeric role of the bandwidth part. It can provide information about the area, etc. Referring to FIG. 6, one terminal has two bandwidth portions within the terminal bandwidth (6-00), bandwidth portion #1 (BPW#1, 6-05) and bandwidth portion #2 (BWP#2, 6-10). can be set. Among the set bandwidths, one or multiple bandwidth portions may be activated, and FIG. 6 shows an example in which one bandwidth portion is activated. In Figure 6, among the bandwidth parts set in slot #0 (6-25), bandwidth part #1 (6-02) is activated, and the terminal is in the control area # set in bandwidth part #1 (6-05). The physical downlink control channel (PDCCH) can be monitored in 1 (6-45), and data (6-55) can be transmitted and received in bandwidth part #1 (6-05). The control area in which the terminal receives the PDCCH may be different depending on which bandwidth portion is activated among the set bandwidth portions, and the bandwidth through which the terminal monitors the PDCCH may vary accordingly.

The base station may additionally transmit an indicator to change the bandwidth settings to the terminal. Here, changing the settings for the bandwidth portion may be considered the same as an operation to activate a specific bandwidth portion (for example, changing activation from bandwidth portion A to bandwidth portion B). The base station can transmit a configuration switching indicator to the terminal at a specific slot, and after receiving the configuration switching indicator from the base station, the terminal determines the portion of bandwidth to be activated by applying the changed settings according to the configuration change indicator from a specific point in time. and monitoring of the PDCCH can be performed in the control area set in the activated bandwidth portion.

In Figure 6, the base station sends a configuration switching indicator (6-15) that instructs the terminal to change the activated bandwidth portion from existing bandwidth portion #1 (6-05) to bandwidth portion #2 (6-10). It can be transmitted from slot #1 (6-30). After receiving the corresponding indicator, the terminal can activate bandwidth part #2 (6-10) according to the contents of the indicator. At this time, a transition time (6-20) may be required to change the bandwidth portion, and accordingly, the time to change and apply the activated bandwidth portion can be determined. FIG. 6 shows a case where a transition time of 1 slot (6-20) is required after receiving a setting change indicator (6-15). Data transmission and reception may not be performed during the corresponding transition time (6-20) (6-60). Accordingly, bandwidth part #2 (6-10) is activated in slot #2 (6-35), so that control channel and data transmission and reception operations can be performed through the corresponding bandwidth part.

The base station can preset one or multiple bandwidth portions to the terminal using upper layer signaling (e.g., RRC signaling), and the configuration change indicator (6-15) is mapped to one of the bandwidth portion settings preset by the base station. Activation can be indicated with . For example, a log ₂ N-bit indicator can select and indicate one of N preset bandwidth portions. [Table 2] below shows an example of indicating setting information for the bandwidth portion using a 2-bit indicator.

[Table 2]

The configuration change indicator (6-15) for the aforementioned bandwidth portion is in the form of MAC (Medium Access Control) CE (Control Element) signaling or L1 signaling (e.g., common DCI, group-common DCI, terminal-specific DCI). It can be transmitted from the base station to the terminal.

) 슬롯 뒤부터 적용)에 따르거나, 또는 기지국이 단말에게 상위레이어 시그날링(예컨대 RRC 시그날링)으로 설정하거나, 또는 설정 변경 지시자(6-15)의 내용에 일부 포함되어 전송될 수 있다. 또는 상기 방법의 조합으로 결정될 수 있다. 단말은 대역폭 부분에 대한 설정 변경 지시자(6-15)를 수신한 후 상기 방법으로 획득한 시점에서부터 변경된 설정을 적용할 수 있다.Depending on the setting change indicator (6-15) for the above-described bandwidth portion, the timing of applying the bandwidth portion activation depends on the following. At what point the setting change will be applied is determined by a predefined value (e.g., after receiving the setting change indicator, N (

) applied after the slot), or the base station may set the terminal to higher layer signaling (e.g., RRC signaling), or it may be transmitted as part of the contents of the configuration change indicator (6-15). Alternatively, it may be determined by a combination of the above methods. After receiving the configuration change indicator (6-15) for the bandwidth portion, the terminal can apply the changed settings from the time obtained by the above method.

In addition to frequency domain resource candidate allocation through BWP indication, NR provides the following detailed frequency domain resource allocation (FD-RA) methods.

FIG. 7 is a diagram illustrating an example of physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) frequency axis resource allocation according to some embodiments. Referring to FIG. 7, three frequency axis resource allocation methods are shown: type 0 (7-00), type 1 (7-05), and dynamic switch (7-10) that can be set through the upper layer in NR.

If the terminal is set to use only resource type 0 through upper layer signaling (7-00), some DCIs that allocate PDSCH or PUSCH to the terminal have a bitmap consisting of N _RBG bits. The conditions for this will be explained later. At this time, N _RBG means the number of RBG (resource block group) determined as shown in [Table 3] below according to the BWP size assigned by the BWP indicator and the upper layer parameter rbg-Size, and is indicated as 1 by the bitmap. Data is transmitted to RBG.

[Table 3]

개의 비트들로 구성되는 주파수 축 자원 할당 정보를 가진다. 이를 위한 조건은 추후 다시 설명하도록 한다. 기지국은 이를 통하여 starting VRB(7-20)와 이로부터 연속적으로 할당되는 주파수 축 자원의 길이(7-25)를 설정하는 것이 가능하다.If the terminal is set to use only resource type 1 through upper layer signaling (7-05), some DCI (downlink control information) that allocates PDSCH or PUSCH to the terminal may be

It has frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (7-20) and the length (7-25) of the frequency axis resources continuously allocated from it.

If the terminal is set to use both resource type 0 and resource type 1 through upper layer signaling (7-10), some DCI (downlink control information) that allocates PDSCH or PUSCH to the terminal is Frequency axis resource allocation information consisting of bits of the larger value (7-35) of payload (7-15) to set resource type 0 and payload (7-20, 7-25) to set resource type 1. has The conditions for this will be explained later. At this time, one bit is added to the first part (MSB) of the frequency axis resource allocation information within the DCI. If the bit is 0, it indicates that resource type 0 is used, and if the bit is 1, it indicates that resource type 1 is used. can do.

또는

)값 그리고 DCI를 통하여 동적으로 지시되는 한 slot 내 OFDM symbol 시작 위치(8-00)와 길이(8-05)에 따라 PDSCH 자원의 시간 축 위치를 지시하는 것이 가능하다.FIG. 8 is a diagram illustrating an example of PDSCH or PUSCH time axis resource allocation according to some embodiments. Referring to Figure 8, the base station determines the subcarrier interval and scheduling offset (scheduling offset) of the data channel and control channel set through upper layer signaling.

or

) value and it is possible to indicate the time axis position of the PDSCH resource according to the OFDM symbol start position (8-00) and length (8-05) within one slot that are dynamically indicated through DCI.

In NR, the terminal performs blind decoding in a specific time and frequency domain to receive PDCCH including DCI (downlink control information). The base station can set the control resource space (Control Resource SET, CORESET) and search space for the terminal through upper layer signaling to provide the time, frequency domain, and mapping method for the terminal to perform blind decoding. . The base station can set up to 3 CORESETs and up to 10 search spaces for each BWP set in the terminal. For example, the base station and the terminal can exchange signaling information as shown in [Table 4] to deliver information about CORESET.

[Table 4]

The signaling information ControlResourceSet in [Table 4] contains information about each CORESET. Information included in the signaling information ControlResourceSet may have the following meaning.

- controlResourceSetId: Indicates the CORESET index.

- frequencyDomainResources: Indicates frequency resource information of CORESET. For all PRBs included in the BWP, 6 RBs are grouped, and 1 bit indicates whether or not CORESET frequency resources are included for each RB bundle. (1: Included in CORESET, 0: Not included in CORESET)

- duration: Symbol level time resource information of CORESET. It has a value of 1, 2, or 3.

- cce-REG-MappingType: Indicates whether control channel elements (CCE) mapped to CORESET are interleaved. If the CCE is interleaving, additional information about interleaving (reg-BundleSize, interleaverSize, shiftIndex) is provided.

- precoderGranularity: Indicates information about frequency resource precoding of CORESET. The size of the precoder may be the same as the REG (resource element group) bundle size or the size of the entire frequency resource of CORESET.

- tci-StatePDCCH-ToAddList, tci-StatePDCCH-ToReleaseList: Represents a set of TCI (Transmission Configuration Indication) states that can be activated in CORESET. One of CORESET's set of TCI states that can be activated can be activated through higher layer signaling (e.g., MAC CE). If CORESET is a CORESET set during the initial connection process, the TCI state set may not be set. An explanation of the TCI state will be provided later.

- tci-PresentInDCI: Indicates whether the DCI transmitted in the PDCCH included in CORESET includes an indicator indicating the TCI state of the PDSCH.

- Pdcch-DMRS-ScramblingID: Sequence scrambling index of DMRS transmitted on PDCCH included in CORESET

The terminal can perform blind decoding to receive the PDCCH by referring to the information about the aforementioned CORESET.

In NR, the base station provides an antenna port (e.g., a DMRS port of a PDSCH or a PDSCH DMRS port or Information about the QCL (quasi co-location) relationship between CSI-RS ports) can be transmitted. The QCL relationship between antenna ports may have one of a total of four QCL types.

- 'QCL-typeA': {Doppler shift, Doppler spread, average delay, delay spread}

- 'QCL-typeB': {Doppler shift, Doppler spread}

- 'QCL-typeC': {Doppler shift, average delay}

- 'QCL-typeD': {Spatial RX parameter}

If some of the above-mentioned QCL types are shared between two different antenna ports, or one antenna port refers to some of the QCL types of another antenna port, the terminal may use the parameters supported by the QCL types shared or referenced by the two antenna ports. It can be assumed that they have the same value by sharing .

The base station can set the TCI state to deliver information about the QCL relationship between antenna ports to the terminal. The TCI state includes information about one or two downlink RSs and the supported QCL type. For example, the base station and the terminal can exchange signaling information as shown in [Table 5] to convey information about the TCI state.

[Table 5]

The signaling information TCI-state in [Table 5] includes information about each TCI state. According to the signaling information, each TCI state includes a TCI state index and one or two types of QCL-Info (qcl-Type1, qcl-Type2) information. qcl-Type1 or qcl-Type2 is a cell index where RS is set, a BWP index containing RS, an RS that provides information on parameters supported by the QCL type according to the QCL type, and information about one of a total of four QCL types. provides. For qcl-Type1, you can have one QCL type out of a total of four QCL types: 'QCL-typeA', 'QCL-typeB', or 'QCL-typeC', and for qcl-Type2, you can have 'QCL-typeD' You can have The terminal may refer to the TCI state activated in the antenna port transmitting the downlink channel and perform reception and decoding of the downlink channel based on the RS referenced in the activated TCI state and the supported QCL type.

FIG. 9 is a diagram for explaining the structure of a downlink control channel of a next-generation mobile communication system according to an embodiment of the present disclosure. That is, FIG. 9 is a diagram illustrating an example of basic units of time and frequency resources constituting a downlink control channel that can be used in 5G according to an embodiment of the present disclosure.

Referring to FIG. 9, the basic unit of time and frequency resources constituting the control channel can be defined as REG (Resource Element Group, 9-03). REG (9-03) can be defined as 1 OFDM symbol (9-01) on the time axis and 1 PRB (Physical Resource Block, 9-02) on the frequency axis, that is, 12 subcarriers. The base station can configure a downlink control channel allocation unit by concatenating REG (9-03).

As shown in FIG. 9, if the basic unit to which a downlink control channel is allocated in 5G is called CCE (Control Channel Element, 9-04), 1 CCE (9-04) is equivalent to a plurality of REGs (9-03). It can be composed of: For example, REG (9-03) shown in Figure 9 may be composed of 12 REs, and if 1 CCE (9-04) is composed of 6 REGs (9-03), 1 CCE (9-04) ) can be composed of 72 REs. When a downlink control area is set, the area can be composed of multiple CCEs (9-04), and a specific downlink control channel can be configured with one or multiple CCEs (9-04) depending on the aggregation level (AL) within the control area. -04) and can be transmitted. CCEs (9-04) in the control area are classified by numbers, and at this time, the numbers of CCEs (9-04) can be assigned according to a logical mapping method.

The basic unit of the downlink control channel shown in FIG. 9, that is, REG (9-03), may include both REs to which DCI is mapped and an area to which DMRS (9-05), a reference signal for decoding this, is mapped. there is. As shown in Figure 9, three DMRS (9-05) can be transmitted within 1 REG (9-03). The number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and the different numbers of CCEs allow link adaptation of the downlink control channel. It can be used to implement. For example, when AL=L, one downlink control channel can be transmitted through L CCEs.

The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs can be defined for blind decoding. The search space is a set of downlink control channel candidates consisting of CCEs that the terminal must attempt to decode on a given aggregation level. Since there are various aggregation levels that create a bundle of 1, 2, 4, 8, and 16 CCEs, the terminal can have multiple search spaces. A search space set can be defined as a set of search spaces at all set aggregation levels.

Search space can be classified into common search space and UE-specific search space. According to an embodiment of the present disclosure, a certain group of terminals or all terminals may search the common search space of the PDCCH to receive cell common control information such as dynamic scheduling or paging messages for system information.

For example, the UE can receive PDSCH scheduling allocation information for SIB transmission, including cell operator information, etc., by examining the common search space of the PDCCH. In the case of a common search space, since a certain group of UEs or all UEs must receive the PDCCH, the common search space can be defined as a set of pre-arranged CCEs. Meanwhile, the UE can receive scheduling allocation information for the UE-specific PDSCH or PUSCH by examining the UE-specific search space of the PDCCH. The terminal-specific search space can be terminal-specifically defined as a function of the terminal's identity and various system parameters.

In 5G, parameters for the search space for PDCCH can be set from the base station to the terminal through higher layer signaling (eg, SIB, MIB, RRC signaling). For example, the base station monitors the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or UE-specific search space), The combination of the DCI format and RNTI to be monitored in the search space, the control area index to be monitored in the search space, etc. can be set to the terminal. For example, the above-described settings may include information as shown in [Table 6] below.

[Table 6]

Based on the configuration information, the base station can configure one or more search space sets for the terminal. According to an embodiment of the present disclosure, the base station can configure search space set 1 and search space set 2 for the terminal, and can configure DCI format A scrambled with X-RNTI in search space set 1 to be monitored in the common search space. In addition, DCI format B scrambled with Y-RNTI in search space set 2 can be set to be monitored in a terminal-specific search space.

According to the configuration information, one or multiple search space sets may exist in the common search space or the terminal-specific search space. For example, search space set #1 and search space set #2 may be set as common search spaces, and search space set #3 and search space set #4 may be set as terminal-specific search spaces.

In the common search space, the combination of DCI format and RNTI below can be monitored. Of course, this is not limited to the examples below.

- DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

- DCI format 2_0 with CRC scrambled by SFI-RNTI

- DCI format 2_1 with CRC scrambled by INT-RNTI

- DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

- DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

In the terminal-specific search space, the combination of the DCI format and RNTI below can be monitored. Of course, this is not limited to the examples below.

- DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

- DCI format 1_0/1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

The specified RNTIs may follow the definitions and uses below.

- C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

- CS-RNTI (Configured Scheduling RNTI): Semi-statically configured UE-specific PDSCH scheduling purpose

- INT-RNTI (Interruption RNTI): Used to inform whether or not there is puncturing for PDSCH.

- MCS-C-RNTI: Used to provide MCS table information that can be replaced for PDSCH or PUSCH

- P-RNTI (Paging RNTI): Used for PDSCH scheduling where paging is transmitted

- SI-RNTI (System Information RNTI): PDSCH scheduling purpose where system information is transmitted

- SP-CSI-RNTI: Used to semi-statically set up CSI reporting through PUSCH

- SFI-RNTI: Used to inform slot format

- TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands to PUSCH

- TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands to PUCCH

- TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands to SRS

- RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access stage

- TC-RNTI (Temporary Cell RNTI): For UE-specific PDSCH scheduling

NR provides various types of DCI formats as shown in [Table 7] below depending on the purpose for efficient control channel reception by the terminal.

[Table 7]

For example, the base station can use DCI format 1_0 or DCI format 1_1 to assign (scheduling) a PDSCH to one cell.

DCI format 1_0 contains at least the following information when transmitted with C-RNTI (Cell Radio Network Temporary Identifier) or CS-RNTI (Configured Scheduling RNTI) or CRC scrambled by MCS-C-RNTI:

- Identifier for DCI formats (1 bits): DCI format indicator, always set to 1

bits): 주파수 축 자원 할당을 지시하며, DCI format 1_0이 UE specific search space에서 모니터 되는 경우

는 active DL BWP의 크기이며, 이외의 경우

는 initial DL BWP의 크기이다. 상세 방법은 상기 주파수 축 자원 할당을 참조한다.- Frequency domain resource assignment (

bits): Indicates frequency axis resource allocation, when DCI format 1_0 is monitored in UE specific search space

is the size of the active DL BWP, otherwise

is the size of the initial DL BWP. For detailed methods, refer to the frequency axis resource allocation above.

- Time domain resource assignment (4 bits): Indicates time domain resource allocation according to the above description.

- VRB-to-PRB mapping (1 bit): If 0, it indicates non-interleaved, and if 1, it indicates interleaved VRP-to-PRB mapping.

- Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

- New data indicator (1 bit): Indicates whether the PDSCH is initial transmission or retransmission depending on whether toggle.

- Redundancy version (2 bits): Indicates the redundancy version used for PDSCH transmission.

- HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

- Downlink assignment index (2 bits): DAI indicator

- TPC command for scheduled PUCCH (2 bits): PUCCH power control indicator

- PUCCH resource indicator (3 bits): PUCCH resource indicator, indicating one of eight resources set as the upper layer.

- PDSCH-to-HARQ_feedback timing indicator (3 bits): HARQ feedback timing indicator, indicating one of eight feedback timing offsets set in the upper layer.

DCI format 1_1 contains at least the following information when transmitted with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

- Identifier for DCI formats (1 bit): DCI format indicator, always set to 1

- Carrier indicator (0 or 3 bits): Indicates the CC (or cell) through which the PDSCH allocated by the relevant DCI is transmitted.

- Bandwidth part indicator (0 or 1 or 2 bits): Indicates the BWP through which the PDSCH allocated by the relevant DCI is transmitted.

는 active DL BWP의 크기이다. 상세 방법은 상기 주파수 축 자원 할당을 참조한다.- Frequency domain resource assignment (payload determined according to the frequency axis resource allocation): Instructs frequency axis resource allocation,

is the size of the active DL BWP. For detailed methods, refer to the frequency axis resource allocation above.

- Time domain resource assignment (4 bits): Indicates time domain resource allocation according to the above description.

- VRB-to-PRB mapping (0 or 1 bit): If 0, it indicates non-interleaved, and if 1, it indicates interleaved VRP-to-PRB mapping. If the frequency axis resource allocation is set to resource type 0, the bit is 0.

- PRB bundling size indicator (0 or 1 bit): If the upper layer parameter prb-BundlingType is not set or set to 'static', it is 0 bit, and if it is set to 'dynamic', it is 1 bit.

- Rate matching indicator (0 or 1 or 2 bits): Indicates the rate matching pattern.

- ZP CSI-RS trigger (0 or 1 or 2 bits): Indicator that triggers aperiodic ZP CSI-RS.

-For transport block 1:

- Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

- New data indicator (1 bit): Indicates whether the PDSCH is initial transmission or retransmission depending on whether toggle.

- Redundancy version (2 bits): Indicates the redundancy version used for PDSCH transmission.

-For transport block 2:

- Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PDSCH transmission.

- New data indicator (1 bit): Indicates whether the PDSCH is initial transmission or retransmission depending on whether toggle.

- Redundancy version (2 bits): Indicates the redundancy version used for PDSCH transmission.

- HARQ process number (4 bits): Indicates the HARQ process number used for PDSCH transmission.

- Downlink assignment index (0 or 2 or 4 bits): DAI indicator

- TPC command for scheduled PUCCH (2 bits): PUCCH power control indicator

- PUCCH resource indicator (3 bits): PUCCH resource indicator, indicating one of eight resources set as the upper layer.

- PDSCH-to-HARQ_feedback timing indicator (3 bits): HARQ feedback timing indicator, indicating one of eight feedback timing offsets set in the upper layer.

- Antenna port (4 or 5 or 6 bits): Indicates DMRS port and CDM group without data.

- Transmission configuration indication (TCI) (0 or 3 bits): TCI indicator.

- SRS request (2 or 3 bits): SRS transmission request indicator

- CBG transmission information (0 or 2 or 4 or 6 or 8 bits): An indicator indicating whether to transmit code block groups within the allocated PDSCH. 0 means that the corresponding CBG is not transmitted, and 1 means that it is transmitted.

- CBG flushing out information (0 or 1 bit): An indicator that indicates whether previous CBGs are contaminated. 0 means they may be contaminated, and 1 means they can be used when receiving retransmissions (combinable).

- DMRS sequence initialization (0 or 1 bit): DMRS scrambling ID selection indicator

For example, the base station can use DCI format 0_0 or DCI format 0_1 to allocate PUSCH to one cell.

DCI format 0_0 includes at least the following information when transmitted with a CRC scrambled by at least one of C-RNTI, CS-RNTI, or MCS-C-RNTI:

- Identifier for DCI formats (1 bit): DCI format indicator, always set to 0

는 active DL BWP의 크기이다. 상세한 방법은 상술한 주파수 축 자원 할당 방법을 참조하여 설명될 수 있다.- Frequency domain resource assignment (payload determined according to frequency axis resource allocation): Instructs frequency axis resource allocation,

is the size of the active DL BWP. The detailed method can be described with reference to the frequency axis resource allocation method described above.

- Time domain resource assignment (4 bits): Instructs time domain resource allocation according to the above description.

- Frequency hopping flag (0 or 1 bit): Indicates whether the PUSCH allocated by the corresponding DCI is hopping on the frequency axis.

- Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PUSCH transmission.

- New data indicator (1 bit): Indicates whether PUSCH is initial transmission or retransmission depending on whether toggle.

- Redundancy version (2 bits): Indicates the redundancy version used for PUSCH transmission.

- HARQ process number (4 bits): Indicates the HARQ process number used for PUSCH transmission.

- TPC command for scheduled PUSCH (2 bits): This is an indicator for controlling the transmission intensity of the PUSCH allocated by the relevant DCI.

- UL-SCH indicator (1 bit): Indicates whether the PUSCH allocated by the corresponding DCI includes the UL-SCH.

DCI format 0_1 is scrambled by at least one of C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), SP-CSI-RNTI (Semi Persistent Channel State Information RNTI), or MCS-C-RNTI When transmitted with a CRC, it contains at least the following information:

- Identifier for DCI formats (1 bit): DCI format indicator, always set to 0

- Carrier indicator (0 or 3 bits): Indicates the CC (or cell) through which the PUSCH allocated by the corresponding DCI is transmitted.

- UL/SUL indicator (0 or 1 bit): Indicates whether to transmit supplementary uplink (SUL) of the PUSCH allocated by the corresponding DCI.

- Bandwidth part indicator (0 or 1 or 2 bits): Indicates the BWP through which the PUSCH allocated by the relevant DCI is transmitted.

는 active DL BWP의 크기이다. 상세한 방법은 상술한 주파수 축 자원 할당 방법을 참조하여 설명될 수 있다.- Frequency domain resource assignment (payload determined according to frequency axis resource allocation): Instructs frequency axis resource allocation,

is the size of the active DL BWP. The detailed method can be described with reference to the frequency axis resource allocation method described above.

- Time domain resource assignment (4 bits): Instructs time domain resource allocation according to the description.

- Frequency hopping flag (0 or 1 bit): Indicates whether the PUSCH allocated by the corresponding DCI is hopping on the frequency axis.

- Modulation and coding scheme (5 bits): Indicates the modulation order and coding rate used for PUSCH transmission.

- New data indicator (1 bit): Indicates whether PUSCH is initial transmission or retransmission depending on whether toggle.

- Redundancy version (2 bits): Indicates the redundancy version used for PUSCH transmission.

- HARQ process number (4 bits): Indicates the HARQ process number used for PUSCH transmission.

- 1 ^st downlink assignment index (1 or 2 bits): Indicates DAI for HARQ-ACK codebook generation.

- 2 ^nd downlink assignment index (0 or 2 bits): Indicates DAI for generating the HARQ-ACK codebook.

- TPC command for scheduled PUSCH (2 bits): This is an indicator for controlling the transmission intensity of the PUSCH allocated by the relevant DCI.

- SRS resource indicator (depending on the SRS usage setting): Indicates the transmission precoding setting of the PUSCH allocated by the corresponding DCI through the SRS resource.

- Precoding information and number of layers (0 or 1 or 2 or 3 or 4 or 5 or 6 bits): Indicates the transmission precoding information and number of transmission layers of the PUSCH allocated by the corresponding DCI.

- Antenna port (2 or 3 or 4 or 5 bits): Indicates the transmission DMRS port and CDM group without data of the PUSCH allocated by the relevant DCI.

- SRS request (2 or 3 bits): Indicates the SRS resource requesting transmission through the relevant DCI.

- CSI request (0 or 1 or 2 or 3 or 4 or 5 or 6 bits): Indicates the CSI report trigger state requesting transmission through the corresponding DCI.

- CBG transmission information (0 or 2 or 4 or 6 or 8 bits): This is an indicator that indicates whether to transmit code block groups in the PUSCH allocated through the corresponding DCI.

- PTRS-DMRS association (0 or 2 bits): Indicates the port connection relationship between the uplink PT-RS of the PUSCH allocated by the corresponding DCI and the uplink DM-RS.

- Upper layer signaling PTRS-UplinkConfig is not set and when CP-OFDM transmission (e.g., transform precoding is not applied), or when DFTS-OFDM transmission (e.g., transform precoding is not applied) When precoding (transform precoding) is applied), or when the value of upper layer signaling maxRank is 1, the field is 0 bit.

- Except for the above cases, the field has a length of 2 bits. Tables 8 and 9 below indicate the connection between the uplink PT-RS port and the uplink DM-RS port for transmission of one and two uplink PT-RS ports, respectively.

[Table 8]

[Table 9]

- Beta_offset indicator (0 or 2 bits): Indicates the offset value used when multiplexing HARQ-ACK or CSI reporting on PUSCH.

- DMRS sequence initialization (0 or 1 bit): DMRS scrambling ID selection indicator.

- UL-SCH indicator (1 bit): Indicates whether the PUSCH allocated by the corresponding DCI includes the UL-SCH.

The maximum number of DCIs of different sizes that the terminal can receive per slot in the corresponding cell is 4. The maximum number of DCIs of different sizes scrambled with C-RNTI that the UE can receive per slot in the corresponding cell is 3.

In NR, the base station can schedule the terminal to transmit PUSCH using DCI format 0_0 or DCI format 0_1. The time axis and frequency axis resource mapping information of the PUSCH transmitted by the UE is obtained by referring to the values of the DCI's Time domain resource assignment and Frequency domain resource assignment fields. The detailed mapping method is described in the time axis resource allocation method and frequency axis resource allocation method as described above. Follow. In addition, the transmission precoding information, rank, and number of transmission layers of the PUSCH transmitted by the terminal refer to the configuration information of the SRS resource indicated through the SRS resource indicator (SRI) field of the DCI or the precoding information and number of DCI. Follow the information indicated in the layers field. Specifically, when the base station schedules the terminal to transmit PUSCH using DCI format 0_0, the terminal can transmit the PUSCH in a single layer without applying precoding. When the base station schedules the terminal to transmit a codebook-based PUSCH using DCI format 0_1, the terminal transmits the configuration information of the SRS resource indicated through the SRI field of the DCI and the precoding information and number of layers field of the DCI. PUSCH can be transmitted by determining the transmission precoding and number of transmission layers according to the indicated information. When the base station schedules the terminal to transmit a non-codebook-based PUSCH using DCI format 0_1, the terminal transmits the transmission precoding applied when transmitting the SRS resource(s) indicated through the SRI field of the DCI. The PUSCH can be transmitted by determining the transmission precoding to be applied to the PUSCH and the number of transmission layers according to the number of transmission layers.

The UE's spatial domain transmission filter applied to the PUSCH transmitted by the UE may follow the value set in the SRS resource indicated through the SRI field of DCI, or a predetermined spatial domain transmission filter may be applied. Specifically, when the base station schedules the terminal to transmit PUSCH using DCI format 0_0, the terminal follows the activated spatial relation info of the PUCCH resource with the lowest index in the activated uplink BWP of the serving cell. If spatial relation info refers to the index of a CSI-RS resource or SSB, the terminal can use a spatial domain transmission filter, such as the spatial domain receive filter used when receiving the referenced CSI-RS resource or SSB. Alternatively, if spatial relation info refers to an SRS resource index, the terminal can use the spatial domain transmission filter used when transmitting the referenced SRS resource. When the base station schedules the terminal to transmit PUSCH using DCI format 0_1, the terminal follows spatial relation info or associated CSI-RS information set by upper layer signaling in the SRS resource indicated through the SRI field of DCI. If spatial relation info is set in the SRS resource, the terminal can use a spatial domain transmission filter according to the spatial relation info reference method described above. If spatial relation info is not set in the SRS resource and the SRS resource set including the SRS resource includes csi-RS or associatedCSI-RS configuration information, the terminal transmits transmission precoding information calculated according to the associated CSI-RS information. You can determine the spatial domain transmission filter by referring to .

When the base station schedules the terminal to transmit PUSCH using DCI format 0_0 or DCI format 0_1, the terminal uses the transmission method indicated through DCI (transmission precoding method in SRS resource, number of transmission layers, spatial domain transmission filter). When applied, a PUSCH preparation procedure time may be required to transmit PUSCH. NR took this into consideration and defined the PUSCH preparation procedure time. The PUSCH preparation procedure time of the terminal can follow [Equation 1] below.

[Equation 1]

에서 각 변수는 하기와 같은 의미를 가질 수 있다.aforesaid

Each variable may have the following meaning.

: 단말의 capability에 따른 단말 처리 능력 (UE processing capability) 1 또는 2와 뉴머롤로지 에 따라 정해지는 심볼 수. 단말의 capability 보고에 따라 단말 처리 능력 1로 보고된 경우 표 10의 값을 가지고, 단말 처리 능력 2로 보고되고 단말 처리 능력 2를 사용할 수 있다는 것이 상위레이어 시그날링을 통해 설정된 경우 표 11의 값을 가질 수 있다.-

: UE processing capability 1 or 2 and numerology depending on the capability of the terminal The number of symbols determined according to . According to the capability report of the terminal, if terminal processing capability 1 is reported, it has the value of Table 10. If it is reported as terminal processing capability 2 and it is set through upper layer signaling that terminal processing capability 2 can be used, it has the value of Table 11. You can have it.

[Table 10]

[Table 11]

: PUSCH의 첫 번째 심볼이 DM-RS만으로 이루어지도록 설정된 경우 0, 아닌 경우 1로 정해지는 심볼 수.-

: Symbol number set to 0 if the first symbol of PUSCH is set to consist of DM-RS only, otherwise 1.

: 64-

: 64

:

또는

중,

이 더 크게 되는 값을 따른다.

은 PUSCH를 스케줄링 하는 DCI가 포함된 PDCCH가 전송되는 하향링크의 뉴머롤로지를 뜻하고,

은 PUSCH가 전송되는 상향링크의 뉴머롤로지를 뜻한다.-

:

or

middle,

This follows the larger value.

refers to the numerology of the downlink where PDCCH including DCI for scheduling PUSCH is transmitted,

refers to the numerology of the uplink where PUSCH is transmitted.

를 가진다.-

has

: PUSCH를 스케줄링하는 DCI가 BWP 스위칭을 지시하는 경우 BWP 스위칭 시간을 따르고, 그렇지 않은 경우 0을 가진다.-

: If the DCI scheduling PUSCH indicates BWP switching, the BWP switching time is followed. Otherwise, it has 0.

이후에 CP가 시작하는 첫 상향링크 심볼보다 PUSCH의 첫 심볼이 먼저 시작하는 경우 PUSCH preparation procedure time이 충분하지 않다고 판단한다. 만일 그렇지 않은 경우 기지국과 단말은 PUSCH preparation procedure time이 충분하다고 판단한다. 단말은 PUSCH preparation procedure time이 충분한 경우에 한해 PUSCH를 전송하고, PUSCH preparation procedure time이 충분하지 않은 경우 PUSCH를 스케줄링 하는 DCI를 무시할 수 있다.Considering the time axis resource mapping information of the PUSCH scheduled through DCI and the influence of TA (timing advance) between uplink and downlink, the base station and the terminal start from the last symbol of the PDCCH including the DCI that scheduled the PUSCH.

Afterwards, if the first symbol of the PUSCH starts before the first uplink symbol started by the CP, it is determined that the PUSCH preparation procedure time is not sufficient. If not, the base station and terminal determine that the PUSCH preparation procedure time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation procedure time is sufficient, and if the PUSCH preparation procedure time is not sufficient, the UE may ignore the DCI that schedules the PUSCH.

FIG. 10 is a diagram illustrating a base station and terminal wireless protocol structure when performing single cell, carrier aggregation, and dual connectivity according to an embodiment of the present disclosure.

Referring to FIG. 10, the wireless protocols of the NR system include NR SDAP (Service Data Adaptation Protocol 10-25, 10-70), NR PDCP (Packet Data Convergence Protocol 10-30, 10-65) at the terminal and NR base station, respectively. It may include NR RLC (Radio Link Control 10-35, 10-60) and NR MAC (Medium Access Control 10-40, 10-55).

The main functions of NR SDAP (10-25, 10-70) may include at least some of the following functions.

- Transfer of user plane data

- Mapping function of QoS flow and data bearer for uplink and downlink (mapping between a QoS flow and a DRB for both DL and UL)

- Marking QoS flow ID in both DL and UL packets for uplink and downlink

- A function of mapping the relective QoS flow to the data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

For SDAP layer devices, the terminal can use an RRC message to configure whether to use the header of the SDAP layer device or use the functions of the SDAP layer device for each PDCP layer device, each bearer, or each logical channel. When the SDAP header is set, the base station sets the NAS QoS reflection setting in the SDAP header. 1-bit indicator (NAS reflective QoS) and the AS QoS reflection setting 1-bit indicator (AS reflective QoS) enable the terminal to set uplink and downlink QoS flow and data. You can instruct to update or reset the mapping information for the bearer. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

The main functions of NR PDCP (10-30, 10-65) may include at least some of the following functions.

- Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

The reordering function of the NR PDCP device refers to the function of rearranging PDCP PDUs received from the lower layer in order based on PDCP sequence number (SN). The reordering function may include a function of transmitting data to a higher layer in the rearranged order, or may include a function of directly transmitting data without considering the order, and may include a function of reordering and recording lost PDCP PDUs. It may include a function to report the status of lost PDCP PDUs to the transmitting side, and may include a function to request retransmission of lost PDCP PDUs.

The main functions of NR RLC (10-35, 10-60) may include at least some of the following functions.

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection function

- Protocol error detection

- RLC SDU deletion function (RLC SDU discard)

- RLC re-establishment function

The in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in order. The sequential delivery function may include the function of reassembling and delivering when one RLC SDU is originally received by being divided into several RLC SDUs, and assigns the received RLC PDUs to an RLC SN (sequence number) or PDCP SN. It may include a function to reorder based on (sequence number), it may include a function to rearrange the order and record lost RLC PDUs, and it may include a function to report the status of the lost RLC PDUs to the transmitter. It may include a function to request retransmission of lost RLC PDUs, and if there is a lost RLC SDU, a function to transmit only the RLC SDUs up to the lost RLC SDU in order to the upper layer. It may include a function of delivering all RLC SDUs received before the timer starts to the upper layer in order if a predetermined timer has expired even if there is a lost RLC SDU, or the lost RLC SDU may include a function. However, if a predetermined timer has expired, it may include a function of delivering all RLC SDUs received to date to the upper layer in order. In addition, the sequential delivery function can process RLC PDUs in the order in which they are received (regardless of the order of serial numbers and sequence numbers, in the order of arrival) and deliver them to the PDCP device regardless of sequence order (out-of sequence delivery). . When a segment is received, the sequential delivery function can receive a segment stored in a buffer or a segment at a later time, reconstruct it into one complete RLC PDU, and then deliver it to the PDCP device. The NR RLC layer may not include a concatenation function and the above-described function may be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

The out-of-sequence delivery function of the NR RLC device refers to the function of directly delivering RLC SDUs received from a lower layer to the upper layer regardless of their order. Originally, one RLC SDU is divided into several RLC SDUs. If it is received in fragments, it may include a function to reassemble and transmit it, and it may include a function to store the RLC SN or PDCP SN of the received RLC PDUs, sort the order, and record lost RLC PDUs. .

The NR MAC (10-40, 10-55) can be connected to several NR RLC layer devices configured in one terminal, and the main functions of the NR MAC may include at least some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing and demultiplexing function (Multiplexing/demultiplexing of MAC SDUs)

- Scheduling information reporting

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification function

- Transport format selection function

- Padding function

The NR PHY layer (10-45, 10-50) channel-codes and modulates the upper layer data, creates OFDM symbols and transmits them to the wireless channel, or demodulates and channel decodes the OFDM symbols received through the wireless channel and transmits them to the upper layer. The transfer operation can be performed.

The detailed structure of the wireless protocol structure described above may change in various ways depending on the carrier (or cell) operation method. For example, when the base station transmits data to the terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure with a single structure for each layer, such as Single cell LTE/NR (10-00). On the other hand, when the base station transmits data to the terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal have a single structure up to RLC as in (10-10), but PHY through the MAC layer. A protocol structure that multiplexes layers is used. As another example, when the base station transmits data to the terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal have a single structure up to RLC as in (10-20), but the MAC layer A protocol structure that multiplexes the PHY layer is used.

In LTE and NR, the terminal can perform a procedure to report the capabilities supported by the terminal to the corresponding base station while connected to the serving base station. In the description below, this is referred to as UE capability (reporting).

The base station can deliver a UE capability inquiry message requesting capability reporting to the connected UE. The message may include a terminal capability request for each RAT type of the base station. The request for each RAT type may include requested frequency band information. Additionally, in the case of the UE capability enquiry message, one RRC message container may request UE capabilities for multiple RAT types, or the base station may include a UE capability enquiry message including a UE capability request for each RAT type multiple times to request the UE capability for each RAT type. It can be delivered to. That is, the UE capability inquiry is repeated multiple times and the UE can configure the corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, terminal capability requests can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). In addition, the UE capability inquiry message is generally transmitted initially after the terminal is connected to the base station, but the base station can request it under any conditions when necessary.

In the above step, the terminal that has received a UE capability report request from the base station configures the terminal capability according to the RAT type and band information requested from the base station. Below is a summary of how the terminal configures UE capabilities in the NR system.

1. If the terminal receives a list of LTE and/or NR bands through a UE capability request from the base station, the terminal configures a band combination (BC) for EN-DC and NR stand alone (SA). In other words, a BC candidate list for EN-DC and NR SA is constructed based on the bands requested from the base station through FreqBandList. Additionally, the bands are prioritized in the order listed in FreqBandList.

2. If the base station requests UE capability reporting by setting the “eutra-nr-only” flag or “eutra” flag, the UE completely removes NR SA BCs from the candidate list of configured BCs. This operation can only occur if the LTE base station (eNB) requests “eutra” capability.

3. Afterwards, the terminal removes fallback BCs from the candidate list of BCs constructed in the above step. Here, fallback BC means BC that can be obtained by removing the band corresponding to at least one SCell from any BC, because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. It can be omitted. This step also applies to MR-DC, i.e. LTE bands as well. The BCs remaining after this step are the final “candidate BC list”.

4. The terminal selects BCs to report by selecting BCs that fit the requested RAT type from the final “candidate BC list” above. In this step, the terminal configures the supportedBandCombinationList in a given order. In other words, the terminal configures the BC and UE capabilities to be reported in accordance with the order of the preset rat-Type. (nr -> eutra-nr -> eutra). Additionally, a featureSetCombination is constructed for the configured supportedBandCombinationList, and a list of "candidate feature set combinations" is constructed from the candidate BC list from which the list of fallback BCs (containing capabilities of the same or lower level) is removed. The above “candidate feature set combination” includes both feature set combinations for NR and EUTRA-NR BC, and can be obtained from the feature set combination of the UE-NR-Capabilities and UE-MRDC-Capabilities containers.

5. Also, if the requested rat Type is eutra-nr and it affects, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, NR's feature set includes only UE-NR-Capabilities.

After the UE capability is configured, the UE transmits a UE capability information message containing the UE capability to the base station. The base station then performs appropriate scheduling and transmission/reception management for the terminal based on the UE capability received from the terminal.

The present disclosure provides a method for determining whether or not to transmit an uplink phase estimation reference signal (hereinafter abbreviated as PT-RS (Phase Tracking Reference Signal)) according to various PUSCH transmission methods of the terminal. In NR, when the communication system operates at high frequencies, phase noise can cause inaccurate demodulation and decoding of the received signal, so uplink PT-RS is transmitted and received to perform phase estimation and demodulation. and decoding. For example, when the terminal receives a PUSCH scheduled with a random access response uplink grant (random access response UL grant) before RRC connection, the terminal does not transmit an uplink PT-RS for the corresponding PUSCH transmission. Additionally, when the UE is instructed to retransmit the Msg3 PUSCH in the random access process after RRC connection, the UE does not transmit an uplink PT-RS for the corresponding PUSCH transmission. Additionally, the UE can determine whether to transmit PT-RS when performing PUSCH transmission scheduled through DCI after RRC connection. Additionally, the UE can determine whether to transmit PT-RS when performing PUSCH transmission through a configured grant after RRC connection. In this disclosure, we will specifically describe a method for determining whether or not to transmit an uplink PT-RS of a terminal for various PUSCH transmission situations through various embodiments below.

Hereinafter, embodiments of the present disclosure will be described in detail with the accompanying drawings. Additionally, when describing the present invention, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. The terms described below are defined in consideration of the functions in the present invention, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Hereinafter, in the present disclosure, the above examples will be described through a number of embodiments, but these are not independent examples, and it is possible for one or more embodiments to be applied simultaneously or in combination.

<First embodiment: When the terminal's uplink PT-RS is not transmitted>

As an example of a method of determining whether the UE transmits an uplink PT-RS, if the UE does not set phaseTrackingRS, a parameter in DMRS-UplinkConfig, which is upper layer signaling, the UE does not transmit the uplink PT-RS. Additionally, the UE's uplink PT-RS transmits a scheduled PUSCH or configured grant through PDCCH including a CRC scrambled with MCS-C-RNTI, C-RNTI, CS-RNTI, and SP-CSI-RNTI. It can exist only for PUSCH transmission that follows the scheme.

As another example of a method of determining whether the UE transmits an uplink PT-RS, the UE performs CP-OFDM transmission (for example, when transform precoding is not applied) and higher layer signaling If phaseTrackingRS, a parameter in DMRS-UplinkConfig, is set, the following operations can be expected.

- The timeDensity and frequencyDensity parameters in PTRS-UplinkConfig, which is upper layer signaling, refer to the values of ptrs-MCS _i and N _RB,i shown in the left column of Tables 12 and 13 below.

- If any of the parameters timeDensity and frequencyDensity in PTRS-UplinkConfig, which is upper layer signaling, is set, the UE determines whether there is an uplink PT-RS and the transmission pattern of the uplink PT-RS is scheduled within the MCS and bandwidth portion. It can be assumed that it is determined as a function of bandwidth.

- If timeDensity, a parameter in PTRS-UplinkConfig, which is upper layer signaling, is not set, the terminal may assume the value of timeDensity to be 1.

- If frequencyDensity, a parameter in PTRS-UplinkConfig, which is upper layer signaling, is not set, the terminal may assume the value of frequencyDensity is 2.

- If both timeDensity and frequencyDensity, which are parameters in PTRS-UplinkConfig, which is upper layer signaling, are not set, the UE may assume the value of timeDensity is 1 and the value of frequencyDensity is 2.

[Table 12]

[Table 13]

Upper layer signaling PTRS-UplinkConfig provides the parameter ptrs-MCS _i (i=1,2,3), and ptrs-MCS _i can have a value between 0 and 29 if the UE uses MCS Table No. 1. If MCS Table No. 2 is used, it can have a value between 0 and 28. ptrs-MCS ₄ is not explicitly set as upper layer signaling, but can have a value of 29 if MCS Table No. 1 is used, and can have a value of 28 if MCS Table No. 2 is used. Upper layer signaling PTRS-UplinkConfig provides the parameter N _RB,i (i=0,1), and N _RB,i can have a value between 1 and 276. If the parameter ptrs-MCS _i in the upper layer signaling PTRS-UplinkConfig has the same value as ptrs-MCS _i+1 , the rows in table x where ptrs-MCS _i and ptrs-MCS _i+1 exist are invalidated. If the parameter N _RB,i in the upper layer signaling PTRS-UplinkConfig has the same value as N _RB,i+1 , the row in table y where N _RB,i exists and N _RB,i+1 is invalid. If either ptrs-MCS _i (i=1,2,3) or N _RB,i (i=0,1), or both have a value corresponding to 'PT-RS not present', the terminal transmits the uplink PT -It can be assumed that RS does not exist. If the UE is allocated 2 or less OFDM symbols for PUSCH transmission and the time density of the uplink PT-RS is set to 2 or 4, the UE does not transmit the uplink PT-RS. If the UE is allocated 4 or fewer OFDM symbols for PUSCH transmission and the time density of the uplink PT-RS is set to 4, the UE does not transmit the uplink PT-RS. When the UE is scheduled for PUSCH retransmission, if the scheduled MCS value is greater than 28 if the UE uses MCS table 1, or if the scheduled MCS value is greater than 27 if the UE uses MCS table 2, uplink PT- The MCS value that determines the time density of RS uses the value shown in the DCI for the initial transmission of the transport block currently being retransmitted, and the corresponding MCS value is 28 or smaller when using MCS table 1, or MCS table 2. When used, it is 27 or smaller. The maximum number of configured uplink PT-RS ports is given through the parameter maxNrofPorts in the upper layer signaling PTRS-UplinkConfig.

The terminal does not expect more uplink PT-RS ports to be configured than the number reported by the terminal. If the UE reports a UE capability that supports full-coherent uplink transmission, the UE can expect the number of uplink PT-RS ports to be 1 when uplink PT-RS is configured. In the case of PUSCH transmission based on codebook or non-codebook, the connection between the uplink PT-RS and DM-RS ports can be transmitted through the PTRS-DMRS association field in DCI format 0_1. In the case of non-codebook-based PUSCH transmission, the actual number of uplink PT-RS ports can be determined through SRI (SRS resource indicator). If the UE has been configured with phaseTrackingRS, a parameter in DMRS-UplinkConfig, which is upper layer signaling, the UE sets the uplink PT-RS index for each configured SRS resource through ptrs-PortIndex, a parameter within SRS-Config, which is upper layer signaling. can be set. If the indices of PT-RS ports corresponding to different SRIs are the same, the corresponding uplink DM-RS ports are connected to one uplink PT-RS port. If the UE reports UE capability supporting partial-coherent or non-coherent uplink transmission in codebook-based PUSCH transmission, the actual number of uplink PT-RS ports can be determined through TPMI and TRI in DCI format 0_1. If the terminal has set maxNrofPorts, a parameter in PTRS-UplinkConfig, which is upper layer signaling, to n2, the actual uplink PT-RS port and the connected transport layer can follow the indicated TPMI. PUSCH antenna ports 1000 and 1002 within the indicated TPMI share PT-RS port number 0, and PUSCH antenna ports 1001 and 1003 within the indicated TPMI share PT-RS port number 1. Uplink PT-RS port number 0 is connected to the uplink layer [x] transmitted to PUSCH antenna ports 1000 and 1002 through the indicated TPMI, and uplink PT-RS port number 1 is connected to the PUSCH antenna port 1001 through the indicated TPMI. It is connected to the uplink layer [y] transmitted to 1003. The aforementioned [x], [y] are given through the PTRS-DMRS association field in DCI format 0_1.

개의 상향링크 전송 레이어를 스케줄링 받았다면, 하기의 동작이 가능하다.If the terminal has Q _p = {1,2} uplink PT-RS ports and

If uplink transport layers have been scheduled, the following operations are possible.

과 같이 주어질 수 있고,

는 상위 레이어 시그널링인 ptrs-Power의 값을 따르고, 하기의 표 14를 통해 확인할 수 있다. 상향링크 PT-RS 스케일링 인자는

와 같이 주어질 수 있고, DCI 내의 precoding information and number of layers 필드에도 존재할 수 있다.- If the UE has been configured with ptrs-Power, which is upper layer signaling, the power ratio between PUSCH and uplink PT-RS for each layer and each RE is

It can be given as,

follows the value of ptrs-Power, which is upper layer signaling, and can be confirmed through Table 14 below. The uplink PT-RS scaling factor is

It can be given as , and can also exist in the precoding information and number of layers field within DCI.

- The terminal assumes that ptrs-Power, a parameter in PTRS-UplinkConfig, which is upper layer signaling, is not set or that the value of ptrs-Power is "00" in Table 14 below in case of non-codebook-based PUSCH transmission.

[Table 14]

As another example of a method of determining whether the UE transmits uplink PT-RS or not, the UE performs DFTS-OFDM transmission in the uplink (for example, when transform precoding is applied) and the upper layer If transformPrecoderEnabled, a parameter in the signaling PTRS-UplinkConfig, is set, the following operations can be expected.

- The terminal can receive sampleDensity, which is upper layer signaling, and the terminal can determine the presence of uplink PT-RS and the uplink PT-RS group pattern as a function of the scheduled bandwidth in the bandwidth portion as shown in Table 15 below. It can be assumed. If N _RB0 >1, the UE can assume that it has been scheduled for fewer RBs than N _RB0 or that uplink PT-RS is not transmitted if the RNTI is TC-RNTI.

- If timeDensityTransformPrecoding, which is upper layer signaling, is set, the terminal can expect the time density of the uplink PT-RS to be set to 2, and if timeDensityTransformPrecoding is not set, the terminal can expect the time density of the PT-RS to be set to 1. .

- If sampleDensity, which is upper layer signaling, is N _RB,i = N _RB,i+1 , rows containing N _RB,i and N _RB,i+1 in Table 15 are invalid.

[Table 15]

는 하기의 표 16에서 확인할 수 있듯이, 스케줄링된 변조 방식에 따라 결정될 수 있다.If the UE transmits DFTS-OFDM in the uplink (for example, when transform precoding is applied) and the UE receives transformPrecoderEnabled, a parameter in PTRS-UplinkConfig, which is upper layer signaling, uplink PT- RS scaling factor

As can be seen in Table 16 below, can be determined according to the scheduled modulation method.

[Table 16]

As another example of a method of determining whether the UE transmits an uplink PT-RS, when the UE receives scheduling Msg3 PUSCH as a random access response uplink grant (random access response UL grant) before RRC connection, the UE transmits the corresponding PUSCH Uplink PT-RS is not transmitted for transmission. In addition, if the UE schedules retransmission for the Msg3 PUSCH in DCI format 0_0 before or after the RRC connection, and the DCI format 0_0 includes a CRC scrambled with TC-RNTI, the UE performs an uplink PT for the corresponding PUSCH transmission. -Do not transmit RS. Additionally, when the UE transmits a PUSCH scheduled in DCI format 0_0 including a CRC scrambled with TC-RNTI, the UE does not transmit an uplink PT-RS.

<Second embodiment: When the terminal's PUSCH transmission is scheduled by DCI and the terminal's uplink PT-RS is transmitted>

As an example of a method of determining whether the terminal transmits an uplink PT-RS, the terminal is scheduled with a DCI that includes a CRC scrambled with MCS-C-RNTI, C-RNTI, CS-RNTI, and SP-CSI-RNTI. Uplink PT-RS can be transmitted. As another example of a method for determining whether the terminal transmits uplink PT-RS, the terminal uses DCI format 0_1 including a CRC scrambled with MCS-C-RNTI, C-RNTI, CS-RNTI, and SP-CSI-RNTI. When PUSCH transmission based on codebook or non-codebook is scheduled through , the connection between the uplink PT-RS and DM-RS port can be transmitted through the PTRS-DMRS association field in DCI format 0_1. In addition, when the UE is scheduled to transmit PUSCH through DCI format 0_0 including a CRC scrambled with MCS-C-RNTI, C-RNTI, and CS-RNTI, the uplink PT-RS port is connected to DM-RS port number 0. connected. Additionally, as described above in Embodiment 1, when the UE is scheduled to transmit PUSCH through DCI format 0_0 including a CRC scrambled with TC-RNTI, the uplink PT-RS is not transmitted.

<Third embodiment: When the terminal's PUSCH transmission is performed based on a configured grant and the terminal's uplink PT-RS is transmitted>

When performing PUSCH transmission based on a configured grant, the UE can determine whether to transmit an uplink PT-RS. If the UE performs PUSCH transmission based on configured grant Type 1, cg-DMRS-Configuration, which is a parameter in ConfiguredGrantConfig, which is upper layer signaling (e.g., the same information as DMRS-UplinkConfig in Example 1 above) Uplink PT-RS transmission can be determined according to the settings of PTRS-UplinkConfig, a parameter within the parameter (can be set). The settings of PTRS-UplinkConfig and cg-DMRS-Configuration, which are upper layer signaling, follow the contents of Embodiment 1 described above. When the UE transmits PUSCH based on configured grant Type 2, the UE transmits PUSCH based on configured grant Type 2 through DCI format 0_0 or 0_1 including a CRC scrambled with CS-RNTI. You may be instructed to activate. At this time, when activation of PUSCH transmission based on configured grant Type 2 is instructed through DCI format 0_0 including CRC scrambled with CS-RNTI, the uplink PT-RS port is DM-RS port 0. It is connected to the number. In addition, when activation of PUSCH transmission based on configured grant Type 2 is instructed through DCI format 0_1 including CRC scrambled with CS-RNTI, the connection between the uplink PT-RS port and DM-RS port Can be transmitted through the PTRS-DMRS association field in DCI format 0_1.

FIG. 11 is a block diagram illustrating the presence or absence of uplink PT-RS transmission for scheduled or activated PUSCH transmission in DCI format 0_0 according to some embodiments.

Referring to FIG. 11, the terminal may be instructed to schedule or activate PUSCH transmission through DCI format 0_0 (11-05). If the terminal is before the RRC connection (11-10), the terminal does not transmit uplink PT-RS for the corresponding PUSCH transmission (11-15). If the terminal is after RRC connection (11-10), the terminal performs different operations depending on which RNTI the corresponding DCI is scrambled with (11-20). If the UE receives DCI format 0_0 including a CRC scrambled with TC-RNTI (11-20), the UE does not transmit an uplink PT-RS for the corresponding PUSCH transmission (11-25). If the terminal receives DCI format 0_0 (11-20) including a CRC scrambled with an RNTI (e.g., C-RNTI, CS-RNTI, MCS-C-RNTI) other than TC-RNTI, the terminal For link PT-RS transmission, assume that the uplink PT-RS port is connected to DM-RS port number 0.

FIG. 12 is a block diagram illustrating the presence or absence of uplink PT-RS transmission for PUSCH transmission scheduled or activated in DCI format 0_1 or based on the configured grant method according to some embodiments.

Referring to FIG. 12, the UE is scheduled for PUSCH transmission through DCI format 0_1, is instructed to activate for PUSCH transmission based on configuration grant Type 2 through DCI format 0_1, or performs upper layer signaling for PUSCH transmission based on configuration grant Type 1. You can be instructed to activate (12-05). If the UE has not set the parameter phaseTrackingRS in DMRS-UplinkConfig, which is upper layer signaling (12-10), the UE does not transmit the uplink PT-RS (12-15). If the UE sets the parameter phaseTrackingRS in DMRS-UplinkConfig, which is upper layer signaling (12-10), and performs DFTS-OFDM transmission (for example, if transform precoding is applied) (12-20) , If transformPrecoderEnabled, a parameter in PTRS-UplinkConfig, which is upper layer signaling, is set, the UE transmits an uplink PT-RS through settings and instructions as described above in Embodiment 1 (12-25). If the UE performs CP-OFDM transmission (e.g., does not apply transform precoding) (12-20), one or both of ptrs-MCS _i or N _RB,i If the value is 'PT-RS not present' (12-30), the terminal does not transmit uplink PT-RS (12-35). If neither ptrs-MCS _i nor N _RB,i variables have the value 'PT-RS not present' (12-30), and the symbol length of the scheduled PUSCH is less than or equal to the time density of the uplink PT-RS ( 12-40), the terminal does not transmit uplink PT-RS (12-45). If the symbol length of the scheduled PUSCH is greater than the time density of the uplink PT-RS (12-40), the terminal transmits the uplink PT-RS through settings and instructions as described above in Example 1 (12 -50).

Figure 13 is a block diagram showing the structure of a terminal according to some embodiments.

Referring to FIG. 13, the terminal may be comprised of a transmitter/receiver (13-00, 13-10), a processing unit (13-05) including a memory, and a processor. Depending on the communication method of the terminal described above, the transmitting and receiving units 13-00 and 13-10 and the processing unit 13-05 of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the aforementioned components. In addition, the transmitting and receiving units 13-00 and 13-10 and the processing unit 13-05 may be implemented in the form of a single chip.

The transmitting and receiving units 13-00 and 13-10 can transmit and receive signals with the base station. Here, the signal may include control information and data. For this purpose, the transceiver units 13-00 and 13-10 may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. there is. However, this is only an example of the transceiver units 13-00 and 13-10, and the components of the transceiver units 13-00 and 13-10 are not limited to the RF transmitter and RF receiver.

In addition, the transmitting and receiving units 13-00 and 13-10 may receive signals through a wireless channel and output them to the processing unit 13-05, and transmit the signal output from the processing unit 13-05 through a wireless channel. .

The processing unit 13-05 can store programs and data necessary for operation of the terminal. Additionally, the processing unit 13-05 may store control information or data included in signals obtained from the terminal. The processing unit 13-05 may include a memory consisting of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

Additionally, the processing unit 13-05 can control a series of processes so that the terminal can operate according to the above-described embodiment. According to some embodiments, the processing unit 13-05 may receive a DCI composed of two layers and control the components of the terminal to receive multiple PDSCHs at the same time.

Figure 14 is a block diagram showing the structure of a base station according to some embodiments.

Referring to FIG. 14, the base station may be composed of a transmitting and receiving unit (14-00, 14-10) and a processing unit (14-05) including a memory and a processor. Depending on the communication method of the base station described above, the transmitting and receiving units 14-00 and 14-10 and the processing unit 14-05 of the base station may operate. However, the components of the base station are not limited to the above examples. For example, a base station may include more or fewer components than those described above. In addition, the transmitting and receiving units 14-00 and 14-10 and the processing unit 14-05 may be implemented in the form of a single chip.

The transmitting and receiving units (14-00, 14-10) can transmit and receive signals to and from the terminal. Here, the signal may include control information and data. To this end, the transceiver units 14-00 and 14-10 may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. there is. However, this is only an example of the transceiver units 14-00 and 14-10, and the components of the transceiver units 14-00 and 14-10 are not limited to the RF transmitter and RF receiver.

In addition, the transmitting and receiving units 14-00 and 14-10 may receive signals through a wireless channel and output them to the processing unit 14-05, and transmit the signal output from the processing unit 14-05 through a wireless channel. .

The processing unit 14-05 can store programs and data necessary for the operation of the base station. Additionally, the processing unit 14-05 may store control information or data included in the signal obtained from the base station. The processing unit 14-05 may include a memory consisting of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

The processing unit 14-05 can control a series of processes so that the base station can operate according to the embodiment of the present invention described above. According to some embodiments, the processing unit 14-05 may control each component of the base station to configure DCI including allocation information for the PDSCH and transmit it.

Meanwhile, the embodiments of the present invention disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. In other words, it is obvious to those skilled in the art that other modifications based on the technical idea of the present invention can be implemented. Additionally, each of the above embodiments can be operated in combination with each other as needed. For example, parts of Embodiments 1 and 2 of the present invention may be combined to operate the base station and the terminal.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the patent claims described later, but also by the scope of this patent claim and equivalents.

Claims (20)

In a method performed by a terminal in a communication system,
Identifying scheduling information scheduling a physical uplink shared channel (PUSCH); and
Transmitting the PUSCH based on the scheduling information; Including,
Whether to transmit a PT-RS (phase tracking reference signal) related to the PUSCH is determined based on one or more predefined conditions related to whether to transmit the PT-RS,
The one or more predefined conditions are:
If the terminal is not connected to radio resource control (RRC), the scheduling information is identified based on a random access response uplink grant, and the PUSCH is a message 3 PUSCH, the PT -RS includes conditions related to determining not to be transmitted. According to claim 1,
The one or more predefined conditions are:
The scheduling information is identified based on downlink control information (DCI) format 0_0, the PUSCH is the message 3 PUSCH, and the DCI format 0_0 is scrambled with a temporary cell-radio network temporary identifier (TC-RNTI). A method according to claim 1, comprising a condition relating to the PT-RS being determined not to be transmitted if it has a cyclic redundance check (CRC). According to claim 1,
The one or more predefined conditions are:
wherein the scheduling information is identified based on DCI format 0_0, and if the DCI format 0_0 has a CRC scrambled with TC-RNTI, the PT-RS is determined not to be transmitted. According to claim 1,
The one or more predefined conditions are:
The scheduling information is identified based on configured grant type 1: If the upper layer parameter configuring the PT-RS is included in the upper layer parameter configuring the configured grant type 1, the PT-RS is transmitted. and a condition related to determining that the PT-RS is not transmitted if the upper layer parameter configuring the PT-RS is not included in the upper layer parameter configuring the configuration grant type 1. According to claim 1,
The one or more predefined conditions are:
If the scheduling information is identified based on configuration grant type 2, the PT-RS is determined to be transmitted. According to claim 5,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_0 with a CRC scrambled with CS-RNTI (configured scheduling-RNTI), the PT-RS port of the PT-RS is connected to the DM-RS (demodulation) of the PUSCH. associated with DM-RS port 0 of the reference signal,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_1 with a CRC scrambled with the CS-RNTI, the association between the PT-RS port and the DM-RS port is the PTRS included in the DCI format 0_1. -Method, identified based on the DMRS association field. In a terminal operating in a communication system,
Transmitter and receiver; and
Including a control unit connected to the transceiver unit,
The control unit:
Identify scheduling information for scheduling a physical uplink shared channel (PUSCH); and
Transmit the PUSCH based on the scheduling information; is set to,
Whether to transmit a PT-RS (phase tracking reference signal) related to the PUSCH is determined based on one or more predefined conditions related to whether to transmit the PT-RS,
The one or more predefined conditions are:
If the terminal is not connected to radio resource control (RRC), the scheduling information is identified based on a random access response uplink grant, and the PUSCH is a message 3 PUSCH, the PT -RS includes conditions related to determining not to transmit, terminal. According to claim 7,
The one or more predefined conditions are:
The scheduling information is identified based on downlink control information (DCI) format 0_0, the PUSCH is the message 3 PUSCH, and the DCI format 0_0 is scrambled with a temporary cell-radio network temporary identifier (TC-RNTI). A terminal, having a cyclic redundance check (CRC), comprising a condition related to the PT-RS being determined not to be transmitted. According to claim 7,
The one or more predefined conditions are:
If the scheduling information is identified based on DCI format 0_0, and the DCI format 0_0 has a CRC scrambled with TC-RNTI, the PT-RS is determined not to be transmitted. According to claim 7,
The one or more predefined conditions are:
The scheduling information is identified based on configured grant type 1: If the upper layer parameter configuring the PT-RS is included in the upper layer parameter configuring the configured grant type 1, the PT-RS is transmitted. and a condition related to determining that the PT-RS is not transmitted if the upper layer parameter configuring the PT-RS is not included in the upper layer parameter configuring the configuration grant type 1. According to claim 7,
The one or more predefined conditions are:
If the scheduling information is identified based on configuration grant type 2, the PT-RS includes conditions related to being determined to be transmitted. According to claim 11,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_0 with a CRC scrambled with CS-RNTI (configured scheduling-RNTI), the PT-RS port of the PT-RS is connected to the DM-RS (demodulation) of the PUSCH. associated with DM-RS port 0 of the reference signal,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_1 with a CRC scrambled with the CS-RNTI, the association between the PT-RS port and the DM-RS port is the PTRS included in the DCI format 0_1. - A terminal identified based on the DMRS association field. In a method performed by a base station in a communication system,
Transmitting scheduling information scheduling a physical uplink shared channel (PUSCH); and
Receiving the PUSCH; Including,
One or more predefined conditions related to reception of a PT-RS (phase tracking reference signal) related to the PUSCH are predefined,
The one or more predefined conditions are:
If the terminal is not connected to RRC (radio resource control), the scheduling information is based on a random access response uplink grant, and the PUSCH is message 3 PUSCH, the PT-RS Method, including conditions relating to non-receipt. According to claim 13,
The one or more predefined conditions are:
The scheduling information is based on downlink control information (DCI) format 0_0, the PUSCH is the message 3 PUSCH, and the DCI format 0_0 is a CRC scrambled with a temporary cell-radio network temporary identifier (TC-RNTI) ( cyclic redundance check), wherein the PT-RS includes a condition related to not being received. According to claim 13,
The one or more predefined conditions are:
If the scheduling information is based on DCI format 0_0, and the DCI format 0_0 has a CRC scrambled with TC-RNTI, the PT-RS is not received. According to claim 13,
The one or more predefined conditions are:
If the scheduling information is based on configured grant type 1: and the upper layer parameter configuring the PT-RS is included in the upper layer parameter configuring the configured grant type 1, the PT-RS is received, and A method comprising a condition related to the PT-RS not being received if the upper layer parameter configuring the PT-RS is not included in the upper layer parameter configuring configuration grant type 1. According to claim 13,
The one or more predefined conditions are:
If the scheduling information is identified based on configuration grant type 2, the PT-RS includes conditions related to being received. According to claim 17,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_0 with a CRC scrambled with CS-RNTI (configured scheduling-RNTI), the PT-RS port of the PT-RS is DM-RS (demodulation) of the PUSCH. associated with DM-RS port 0 of the reference signal,
If the DCI indicating activation of the configuration grant type 2 is DCI format 0_1 with a CRC scrambled with the CS-RNTI, the association between the PT-RS port and the DM-RS port is the PTRS included in the DCI format 0_1. -Method, identified based on the DMRS association field. In a base station operating in a communication system,
Transmitter and receiver; and
Including a control unit connected to the transceiver unit,
The control unit:
Transmit scheduling information for scheduling PUSCH (physical uplink shared channel); and
Receiving the PUSCH; is set to,
One or more predefined conditions related to reception of a PT-RS (phase tracking reference signal) related to the PUSCH are predefined,
The one or more predefined conditions are:
If the terminal is not connected to RRC (radio resource control), the scheduling information is based on a random access response uplink grant, and the PUSCH is message 3 PUSCH, the PT-RS Base station, including conditions related to non-reception. According to claim 19,
The one or more predefined conditions are:
The scheduling information is based on downlink control information (DCI) format 0_0, the PUSCH is the message 3 PUSCH, and the DCI format 0_0 is a CRC scrambled with a temporary cell-radio network temporary identifier (TC-RNTI) ( The base station has a cyclic redundance check, which includes a condition related to the PT-RS not being received.