Method and apparatus for transmitting / receiving paging information in a satellite communication system

Abstract

The disclosure relates to a fifth generation (5G) or sixth generation (6G) communication system for supporting a higher data transmission rate. A method and device for efficiently transmitting / receiving paging information in a satellite communication system. According to an embodiment, a method for: receiving, from a network, first configuration information related to repeated transmission of paging information; receiving, from the network, DL control information (DCI) indicating the repeated transmission of the paging information and a number of repeated transmissions based on the first configuration information; and receiving, from the network, the paging information repeatedly transmitted for the number of repeated transmissions based on the DCI.

Description

Technical Field

[0001] This disclosure generally relates to the operation of user equipment (UE) and base station (BS) in a satellite communication system, and more specifically, to a method for transmitting / receiving paging information in a satellite communication system and a device capable of performing the method. Background Technology

[0002] Fifth-generation (5G) mobile communication technology defines wide bandwidth, enabling high transmission rates and new services. It can be implemented not only in sub-6 GHz bands such as 3.5 GHz, but also in higher bands above 6 GHz, including the 28 GHz and 39 GHz bands known as millimeter-wave (mmWave) bands. Furthermore, sixth-generation (6G) mobile communication technology, known as Super 5G, is being considered in terahertz (THz) bands (e.g., the 95 GHz to 3 THz band), aiming to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] Since the development of 5G mobile communication technology began, in order to support services and meet the performance requirements associated with enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), there has been ongoing standardization work on the following aspects: beamforming and massive multiple-input multiple-output (MIMO) in mmWave to mitigate radio wave path loss and increase radio wave transmission distance; dynamic operation to support parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats for efficient utilization of mmWave resources; initial access technologies to support multi-beam transmission and broadband; definition and operation of bandwidth portions (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; layer 2 (L2) preprocessing; and network slicing for providing dedicated networks tailored to specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, there are ongoing discussions regarding improvements and performance enhancements to the initial 5G mobile communication technology, and there is already physical layer standardization for technologies such as: Vehicle-to-Everything (V2X) for assisting autonomous vehicle driving decisions based on information about the vehicle's location and status transmitted by the vehicle and for enhancing user convenience; New Radio Unlicensed (NR-U) for system operation designed to comply with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTN) for providing coverage in areas where communication with terrestrial networks is not possible, as well as positioning.

[0005] Furthermore, in the wireless interface architecture / protocol domain, there is ongoing standardization regarding technologies such as: Industrial Internet of Things (IIoT) supporting new services through interconnection and convergence with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover; and Two-Step Random Access for NR (Two-Step RACH) for simplifying the random access process. In the system architecture / service domain, standardization is also underway regarding: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for UE location-based reception services.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices will increase exponentially, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research is planned related to: Extended Reality (XR) for effectively supporting Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance improvements and complexity reduction through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.

[0007] This development of 5G mobile communication systems will serve as the foundation for the development of: new waveforms for providing terahertz band coverage for 6G mobile communication technologies; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving terahertz band signal coverage; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS); as well as the foundation for the development of: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technologies and improving system networks; AI-based communication technologies for leveraging satellites and AI from the design phase to achieve system optimization and internalize end-to-end AI support functions; and next-generation distributed computing technologies for achieving services with complexity levels exceeding the operational limits of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] Despite advancements in wireless communication, there remains a need in the art for a method and apparatus for efficiently sending / receiving paging information in satellite communication systems. Summary of the Invention

[0009] Technical solutions

[0010] This disclosure has been made to address at least the aforementioned problems and / or disadvantages, and to provide at least the following advantages.

[0011] Therefore, one aspect of this disclosure is to provide a method and apparatus for effectively transmitting / receiving paging information in a satellite communication system.

[0012] According to one aspect of this disclosure, a method for a UE in a satellite communication system includes receiving first configuration information related to repeated transmission of paging information from a network, receiving downlink control information (DCI) from the network based on the first configuration information, including information related to repeated transmission indicating repeated transmission of paging information and the number of repeated transmissions, and receiving paging information repeatedly transmitted by the number of repeated transmissions from the network based on the DCI.

[0013] According to one aspect of this disclosure, a UE in a satellite communication system includes a transceiver and at least one processor configured to receive first configuration information related to repeated transmissions of paging information from a network, and based on the first configuration information, receive downlink control information (DCI) from the network including information related to repeated transmissions indicating repeated transmissions of paging information and the number of repeated transmissions, and based on the DCI, receive paging information from the network that is repeatedly transmitted in the number of repeated transmissions.

[0014] According to one aspect of this disclosure, a method of a BS in a satellite communication system includes: sending first configuration information related to repeated transmission of paging information to a UE; sending a DCI (Distributed Information Containment Code) including information related to repeated transmission and the number of repeated transmissions of paging information to the UE based on the first configuration information; and repeatedly transmitting paging information to the UE based on the DCI and the number of repeated transmissions.

[0015] According to one aspect of this disclosure, a BS in a satellite communication system includes a transceiver and at least one processor configured to: send first configuration information to a UE relating to repeated transmissions of paging information; based on the first configuration information, send a DCI indicating repeated transmissions of paging information and the number of repeated transmissions to the UE; and based on the DCI, repeatedly transmit paging information to the UE at the number of repeated transmissions. Attached Figure Description

[0016] The above and other aspects, features, and advantages of certain embodiments of this disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings, wherein:

[0017] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment is shown;

[0018] Figure 2The structure of frames, subframes, and time slots in a wireless communication system according to an embodiment is shown;

[0019] Figure 3 An example of BWP configuration in a wireless communication system according to an embodiment is shown;

[0020] Figure 4 An example configuration of the control region of a DL control channel in a wireless communication system according to an embodiment is shown;

[0021] Figure 5 The structure of a DL control channel in a wireless communication system according to an embodiment is shown;

[0022] Figure 6 This illustrates an embodiment where a UE in a wireless communication system can have multiple physical downlink control channel (PDCCH) monitoring locations in a time slot, via a span.

[0023] Figure 7 An example of BS beam allocation configured according to Transmission Configuration Indication (TCI) status in a wireless communication system according to an embodiment is shown;

[0024] Figure 8 An example of a TCI state allocation method for a PDCCH in a wireless communication system according to an embodiment is shown;

[0025] Figure 9 The TCI-indicating Media Access Control (MAC) control element (CE) signaling structure for PDCCH demodulation reference signal (DMRS) in a wireless communication system is shown according to an embodiment.

[0026] Figure 10 An example of beam configuration for the search space and control resource set (CORESET) in a wireless communication system according to an embodiment is shown;

[0027] Figure 11 A method for transmitting / receiving data by a BS and UE in a wireless communication system, taking into account DL data channels and rate matching resources, is illustrated according to an embodiment.

[0028] Figure 12 This paper illustrates a method for selecting an acceptable CORESET by considering priority when a UE receives a DL control channel in a wireless communication system, according to an embodiment.

[0029] Figure 13 An example of an aperiodic channel state information (CSI) reporting method according to an embodiment is shown;

[0030] Figure 14An example of Physical UL Shared Channel (PUSCH) repetitive transmission type B in a wireless communication system according to an embodiment is shown;

[0031] Figure 15 The radio protocol structures of the BS and UE in single-cell, carrier aggregation (CA) and dual connectivity scenarios in a wireless communication system according to an embodiment are shown.

[0032] Figure 16 An example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system according to an embodiment is shown;

[0033] Figure 17 An example of a DCI configuration for cooperative communication in a wireless communication system according to an embodiment is shown;

[0034] Figure 18 This illustrates the process by which the BS controls the UE's transmit power in a cellular system;

[0035] Figure 19 The process of generating a type 1 (semi-static) HARQ-ACK codebook from a UE according to an embodiment is illustrated.

[0036] Figure 20 The process of generating a type 2 (dynamic) HARQ-ACK codebook from a UE according to an embodiment is shown;

[0037] Figure 21 The Earth orbit period of a communication satellite, depending on the satellite's altitude or elevation, is shown according to an embodiment.

[0038] Figure 22 A method for repeatedly transmitting UE paging information according to an embodiment is shown;

[0039] Figure 23 This is a flowchart illustrating the process of receiving a PUSCH retransmission including paging information according to an embodiment;

[0040] Figure 24 The structure of a UE in a wireless / satellite communication system according to an embodiment is shown; and

[0041] Figure 25 The structure of a BS in a wireless / satellite communication system according to an embodiment is shown. Detailed Implementation

[0042] In the following, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same or similar elements are preferably represented by the same or similar reference numerals. For clarity and brevity, detailed descriptions of known functions or configurations that might obscure the subject matter of this disclosure will be omitted.

[0043] The terms described below are defined with reference to the functionality of this disclosure and may vary depending on the intent or practice of the user and provider. Therefore, they should be defined based on the entire contents of this specification.

[0044] In the accompanying drawings, some components are exaggerated, omitted, or shown schematically. The sizes of the components do not perfectly reflect their actual sizes. Identical or equivalent components are labeled with the same reference numerals in all drawings.

[0045] The embodiments of this disclosure complete the disclosure, and these embodiments are provided to fully inform those skilled in the art to which this disclosure pertains of the scope of the disclosure.

[0046] Throughout the specification, the same reference numerals refer to the same components.

[0047] For ease of description, terms are provided to indicate network entities or network functions and entities of an edge computing system, as well as terms to indicate messages and identification information used in this disclosure. Therefore, this disclosure is not limited to the terms described below, and other terms indicating objects with equivalent technical meanings may be used.

[0048] In the following, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. In this disclosure, a BS can be an entity that allocates resources to a UE, and can be at least one of a satellite, gateway, ground station, gNode B, gNB, eNode B, Node B, BS, radio access unit, BS controller, and nodes on a network. Furthermore, in this disclosure, a BS can be a BS included in a satellite or a BS on the ground. Terminals can include UEs, MS (mobile station), cellular phones, smartphones, computers, or multimedia systems capable of performing communication functions. Although 5G or next-generation systems are described herein, this disclosure can also be applied to other communication systems with similar technical backgrounds or channel configurations. For example, LTE or LTE-A mobile communication and post-5G mobile communication technologies can be included therein. Embodiments of this disclosure can be modified without significantly departing from the scope of this disclosure, as determined by those skilled in the art, and such modifications can be applied to other communication systems. The content of this disclosure applies to FDD and TDD systems.

[0049] Detailed descriptions of known techniques or functions may be omitted when it is determined that such descriptions would obscure the subject matter of this disclosure. The terminology used herein is defined with reference to the functions described in this disclosure and may be replaced with other terms depending on the intent or practice of the user or operator. Therefore, the terminology should be defined on a holistic basis as the disclosure is made.

[0050] In this disclosure, higher-level signaling may correspond to at least one or a combination of one or more of the following signaling types.

[0051] Master Information Block (MIB)

[0052] System Information Block (SIB) or SIB X (X=1,2,…)

[0053] Radio Resource Control (RRC)

[0054] MAC CE

[0055] L1 signaling can correspond to at least one or a combination of one or more of the following physical layer channels or signaling methods that use signaling.

[0056] PDCCH

[0057] DCI

[0058] UE-specific DCI

[0059] Group Public DCI

[0060] Public DCI

[0061] DCI (Dispatch Control Center) is used to schedule downlink (DL) or uplink (UL) data.

[0062] Non-scheduling DCI (e.g., DCI not used for scheduling DL or UL data)

[0063] Physical UL Control Channel (PUCCH)

[0064] UL Control Information (UCI)

[0065] In this document, the term UE can refer to any component, such as a mobile station, subscriber station, remote terminal, wireless terminal, receiving point, or user equipment. For convenience, the term UE is used to refer to a device accessing the BS, regardless of whether it needs to be considered a mobile device (such as a mobile phone or smartphone) or a fixed device (such as a desktop computer or vending machine). For the convenience of the following description, the terminal is referred to as UE.

[0066] In this article, the term "timing advance" (TA) can be used interchangeably with TA information, TA value, or TA index.

[0067] Data or control information sent from the BS to the UE can be referred to as a first signal, and UL signals associated with the first signal can be referred to as second signals. For example, the first signal may include DCI, UL authorization, PDCCH, Physical DL Shared Channel (PDSCH), Random Access Response (RAR), etc., and the second signal associated with the first signal may include PUCCH, PUSCH, msg 3 (message 3), etc.

[0068] A correlation may exist between the first signal and the second signal. For example, when the first signal is a PDCCH that includes UL authorization for UL data scheduling, the corresponding second signal may be a PUSCH that includes UL data. Meanwhile, the gap between the transmission / reception times of the first and second signals may be a predetermined value between the UE and the BS. Alternatively, the difference between the transmission / reception times of the first and second signals may be indicated and determined by the BS, or it may be determined by a value transmitted via higher-layer signaling. Hereinafter, higher-layer signaling may be simply referred to as higher-layer signaling.

[0069] In the following text, BS can be an entity that allocates resources to terminals and can be at least one of gNode B, eNode B, Node B, Radio Access Unit, BS controller, and nodes on the network. UE can include UE, MS (Mobile Station), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. DL refers to the radio transmission path of a signal from the BS to the terminal, and UL refers to the radio transmission path of a signal from the terminal to the BS. Although LTE or LTE-A systems are described below as examples, embodiments can be applied to other communication systems with similar technical backgrounds or channel modes. For example, 5G mobile communication technologies (5G, New Radio, NR) developed after LTE-A can be included therein, and 5G below can be a concept including legacy LTE, LTE-A, and other similar services. It will be determined by those skilled in the art that embodiments can be modified without significantly departing from the scope of this disclosure, and such modifications can be applied to other communication systems.

[0070] It should be understood that the boxes and combinations of flowcharts in each flowchart can be executed by computer program instructions. Since computer program instructions can be located in the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment generate means for performing the functions associated with the boxes in each flowchart. Since computer program instructions can be stored in a computer-usable or computer-readable storage device that can be oriented towards the computer or other programmable data processing equipment to implement its functions in a specified manner, the instructions stored in the computer-usable or computer-readable storage device can produce a product including instruction means for performing the functions associated with the boxes in each flowchart. Since computer program instructions can be located in a computer or other programmable data processing equipment, the instructions executed on the computer or other programmable data processing equipment generate the process to be performed by the computer as a series of operational steps, and operating the computer or other programmable data processing equipment can provide steps for performing the functions associated with the boxes in each flowchart.

[0071] Each box may represent a module, segment, or portion of code comprising one or more executable instructions for performing a specified logical function. Furthermore, it should be noted that in some alternative embodiments, the functions mentioned in the boxes may occur in different orders. For example, depending on the corresponding function, two consecutively shown boxes may be executed substantially simultaneously or in reverse order.

[0072] As used herein, the term "unit" means a software element or hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A unit plays a specific role. However, a "unit" is not limited to software or hardware. A "unit" can be configured in a storage medium that can be addressed or configured to execute one or more processors. Thus, by way of example, a "unit" includes elements (such as software elements, object-oriented software elements, class elements, and task elements), processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data schemas, tables, arrays, and variables. The functionality provided within components and "units" can be combined into a smaller number of components and "units," or further divided into additional components and "units." Components and "units" can be implemented as one or more CPUs in an execution device or secure multimedia card. According to embodiments, "...unit" may include one or more processors.

[0073] As used herein, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B or C” can include all possible combinations of the items listed together in the corresponding one of the phrases. As used herein, terms such as “first” and “second” or “first” and “second” can be used simply to distinguish corresponding components from one other component and do not restrict the components in any other way (e.g., in terms of importance or order).

[0074] Wireless communication systems have evolved from voice-centric services to broadband wireless communication systems that provide high data rates and high-quality packet data services, such as the 3rd Generation Partnership Project (3GPP) High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-pro, 3GPP2 High-Speed ​​Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the Institute of Electrical and Electronics Engineers (IEEE) 802.16e communication standard.

[0075] As a representative example of such a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for Downlink and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for Downlink. Downlink is the radio link through which the UE or MS transmits data or control signals to the BS or eNode B, and downlink refers to the radio link through which the BS transmits data or control signals to the UE. This multiple access scheme can typically allocate and operate time-frequency resources carrying each user's data or control information in a non-overlapping manner, i.e., maintaining orthogonality, thereby distinguishing the data or control information of each user.

[0076] Post-LTE communication systems (e.g., 5G communication systems) need to be flexible enough to reflect the diverse needs of users and service providers, thereby supporting services that simultaneously meet various requirements. Services considered for use in 5G communication systems include, for example, eMBB, mMTC, and URLLC.

[0077] Compared to LTE, LTE-A, or LTE-pro, eMBB aims to provide further enhanced data transmission rates. For example, for a single base station (BS), eMBB for a 5G communication system needs to provide a peak data rate of 20Gbps in the downlink and 10Gbps in the ultra-low frequency (UL). 5G communication systems also need to provide increased user-aware data rates while delivering such peak data rates. To meet these requirements, various transmit (TX) / receive (RX) technologies and MIMO should be further enhanced. While LTE uses a maximum TX bandwidth of 20MHz in the 2GHz band to transmit signals, 5G communication systems employ wider frequency bandwidths ranging from 3GHz to 6GHz or above to meet the data rates required by 5G communication systems.

[0078] mMTC is also considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To effectively deliver IoT, mMTC is needed to support a large number of UEs in a cell, enhance UE coverage and battery life, and reduce UE costs. IoT terminals are attached to various sensors or devices to provide communication capabilities, and therefore, it needs to support multiple UEs per cell (e.g., 1,000,000 UEs / km). 2 Depending on the nature of the service, a UE supporting mMTC is likely to be located in shadow areas not covered by cell coverage (such as underground in buildings), and therefore may require wider coverage compared to other services provided by 5G communication systems. Due to the need for low cost and the difficulty in frequently replacing batteries, UEs supporting mMTC may need to have very long battery life, for example, 10 to 15 years.

[0079] URLLC is a mission-critical, cellular-based wireless communication service. For example, URLLC can be considered for remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote healthcare, or emergency alerts. This requires URLLC to provide very low latency and very high reliability communication. For example, services supporting URLLC need to meet an air interface latency of less than 0.5 milliseconds while having 10... -5 Or even a lower packet error rate. Therefore, for services that support URLLC, 5G communication systems may need to provide shorter Transmission Time Intervals (TTIs) than other services, while ensuring reliable communication links by allocating wide resources in the frequency band.

[0080] Three 5G services (eMBB, URLLC, and mMTC) can be multiplexed and transmitted within a single system. In this case, the services can employ different TX / RX schemes and TX / RX parameters to meet their different requirements. Of course, 5G is not limited to these three services.

[0081] [NR Time and Frequency Resources]

[0082] The frame structure of the 5G system is described in more detail below with reference to the accompanying drawings.

[0083] Figure 1 The basic structure of the time-frequency domain is shown, which is the radio resource region where data or control channels are transmitted in a 5G system.

[0084] exist Figure 1 In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in both the time and frequency domains is a resource element (RE) 101, which can be defined by an OFDM symbol 102 on the time axis and a subcarrier 103 on the frequency axis. In the frequency domain... (For example, 12 consecutive REs can form a resource block (RB) 104.

[0085] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to an embodiment is shown.

[0086] Figure 2 An example structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, and therefore, a frame 200 can consist of a total of 10 subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (i.e., the number of symbols per time slot (...)). =14). A subframe 201 may consist of one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on μ (204 or 205), which is a set value for the subcarrier spacing. Figure 2 Examples of subcarrier spacing settings μ=0 (204) and μ=1 (205) are shown. When μ=0 (204), a subframe 201 can consist of one time slot 202, and when μ=1 (205), a subframe 201 can consist of two time slots (203). In other words, the number of time slots in each subframe depends on the set subcarrier spacing value μ. The number of time slots per frame can vary, and therefore, the number of time slots per frame ( The values ​​can differ depending on the subcarrier spacing μ. as well as It can be defined in Table 1 below.

[0087] [Table 1]

[0088]

[0089] BWP

[0090] Figure 3 An example of BWP configuration in a wireless communication system according to an embodiment is shown.

[0091] Figure 3 An example is shown where UE bandwidth 300 is divided into two BWPs (e.g., BWP#1 301 and BWP#2 302). A BS can configure one or more BWPs in the UE, and can configure the following information shown in Table 2 for each BWP.

[0092] [Table 2]

[0093]

[0094] However, this is not the only limitation; various other BWP-related parameters besides the configuration information described above can be configured in the UE. The BS can transmit information to the UE via higher-layer signaling (e.g., RRC signaling). At least one of the one or more configured BWPs can be activated. Whether a configured BWP is activated can be semi-statically transmitted from the BS to the UE via RRC signaling or dynamically via DCI.

[0095] Prior to RRC connection, the UE can be configured with an initial BWP for initial access via the MIB through the BS. More specifically, during the initial access phase, the UE can receive configuration information for the search space and CORESET via the MIB, where the PDCCH can be sent to receive system information required for initial access (e.g., Residual System Information (RMSI) or SIB1, which may correspond to SIB1). Each of the control area and search space configured with the MIB can be considered as identifier (ID) 0. The BS can provide the UE with configuration information via the MIB, such as frequency allocation information, time allocation information, and parameter sets for control area #0. The BS can also provide the UE with configuration information for the timing and monitoring period of control area #0, i.e., configuration information for search space #0, via the MIB. The UE can consider the frequency range of control area #0 obtained from the MIB as the initial BWP for initial access. In this case, the ID of the initial BWP can be considered as 0.

[0096] The BWP configurations supported in the aforementioned 5G can be used for various purposes.

[0097] According to the embodiment, when the bandwidth supported by the UE is less than the system bandwidth, this can be supported through BWP configuration. For example, when the BS configures the UE with the frequency position of the BWP (configuration information 2), the UE can send / receive data at a specific frequency position in the system bandwidth.

[0098] According to an embodiment, to support different parameter sets, the BS can configure multiple BWPs for the UE. For example, to support some UEs using a 15kHz subcarrier spacing and a 30kHz subcarrier spacing for data transmission / reception, the BS can configure two bandwidths for the UE as 15kHz and 30kHz subcarrier spacings. Different BWPs can be frequency-division multiplexed, and when data is transmitted / received at a specific subcarrier spacing, the BWP configured for the corresponding subcarrier spacing can be activated.

[0099] According to an embodiment, to reduce UE power consumption, the BS can configure the UE with a BWP of different bandwidth sizes. For example, significant power consumption may occur when the UE supports a bandwidth exceeding a very large bandwidth (e.g., 100 MHz) and always uses that bandwidth to send / receive data. In particular, using a large bandwidth of 100 MHz to monitor unnecessary DL control channels in the absence of service is very inefficient in terms of power consumption. To reduce UE power consumption, the BS can configure the UE with a relatively small bandwidth BWP, for example, a 20 MHz BWP. In the absence of service, the UE can perform monitoring in a 20 MHz bandwidth, and if data occurs, the UE can send / receive data in a 100 MHz bandwidth according to instructions from the BS.

[0100] In the method for configuring the BWP, the UE prior to RRC connection can receive initial bandwidth configuration information via the MIB during the initial access phase. More specifically, the UE can be configured with a control area (e.g., CORESET) for the DL control channel, in which the DCI for scheduling SIBs can be transmitted from the MIB on the Physical Broadcast Channel (PBCH). The bandwidth configured by the MIB can be considered as the initial BWP, and the UE can receive the PDSCH for transmitting SIBs via the configured initial BWP. The initial BWP can be used for other SIs (OSI), paging and RA, and for receiving SIBs.

[0101] BWP changes

[0102] If the UE is configured with one or more BWPs, the BS can use the BWP indicator in the DCI to indicate a change (or switch or transition) of the BWP to the UE. As an example, when the UE's currently active BWP is... Figure 3 When BWP#1 301 is in the DCI, the BS can use the BWP indicator in the DCI to indicate BWP#2 302 to the UE, and the UE can change the BWP to BWP#2 302 indicated by the BWP indicator in the received DCI.

[0103] As described above, since DCI-based BWP changes can be indicated via DCI scheduling of PDSCH or PUSCH, the UE should be able to receive or transmit the DCI-scheduled PDSCH or PUSCH without difficulty in the changed BWP if a BWP change request is received. To this end, the standard specifies the delay time T required for changing the BWP. BWP The requirements can be defined in Table 3 as follows.

[0104] [Table 3]

[0105]

[0106] Depending on the UE's capabilities, the delay requirement for BWP changes must support either Type 1 or Type 2. The UE can report the supported BWP delay time types to the BS.

[0107] If the UE receives the DCI including the BWP change indicator in time slot n according to the above requirements for the BWP change delay time, the UE can proceed no later than time slot n+T. BWP The time required for the change to the new BWP indicated by the BWP change indicator is completed, and transmission / reception can be performed on the data channel scheduled by the DCI within the changed new BWP. When scheduling the data channel in the new BWP, the BS can consider the UE's BWP change delay time T. BWPThis is used to determine the time-domain resource allocation of the data channel. In other words, when scheduling a data channel using a new BWP, in the method for determining the time-domain resource allocation of the data channel, the BS can schedule the corresponding data channel after the BWP change delay time. Therefore, the UE may not expect the DCI indication indicating the BWP change to be less than the BWP change delay time (T). BWP The time slot offset (K0 or K2).

[0108] If the UE has already received a DCI indicating a BWP change (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving for the period from the third symbol of the slot in which the PDCCH including the DCI was received to the start of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the UE receives a DCI indicating a BWP change in slot n, and the slot offset value indicated by the DCI is K, the UE may refrain from transmitting or receiving from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0109] SS / PBCH block

[0110] The Synchronization Signal (SS) / PBCH block indicates a physical layer channel block consisting of the Primary SS (PSS), Secondary SS (SSS), and PBCH. Details are as follows.

[0111] PSS: A signal used as a reference for DL ​​time / frequency synchronization and providing partial information about the cell ID.

[0112] SSS: Used as a reference for DL ​​time / frequency synchronization and provides additional information about the cell ID not provided by PSS. Additionally, it can be used as a reference signal for demodulation in PBCH.

[0113] PBCH: Provides the necessary SIs required for the UE to transmit and receive data and control channels. Necessary SIs may include search space-related control information indicating radio resource mapping information for control channels and scheduling control information for separate data channels used to transmit SIs.

[0114] SS / PBCH Blocks: An SS / PBCH block consists of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within 5 ms, and each sent SS / PBCH block can be distinguished by an index.

[0115] The UE can detect the PSS and SSS during the initial access phase and can decode the PBCH. The UE can obtain the MIB from the PBCH and can be configured with a control area (e.g., CORESET) #0 based on the MIB (which may correspond to a control area with control area index 0). The UE can perform monitoring on control area #0, assuming the selected SS / PBCH block and the DMRS transmitted in control area #0 are quasi-co-located (QCL). The UE can receive the SI as a DCI transmitted in control area #0. The UE can obtain configuration information related to the RA channel (RACH) required for initial access from the received SI. The UE can transmit the physical RACH (PRACH) to the BS considering the selected SS / PBCH index, and the BS receiving the PRACH can obtain information about the SS / PBCH block index selected by the UE. The BS can know which block the UE has selected from the SS / PBCH blocks and monitor the associated control area #0.

[0116] PDCCH: DCI related

[0117] In a 5G system, scheduling information for PUSCH or PDSCH is transmitted from the BS to the UE via DCI. The UE can monitor the DCI format used for fallback and the DCI format used for non-fallback for PUSCH or PDSCH. The fallback DCI format can consist of fixed fields predetermined between the BS and the UE, while the non-fallback DCI format can include configurable fields.

[0118] DCI messages can be transmitted via PDCCH through channel coding and modulation. Cyclic Redundancy Check (CRC) is added to the DCI message payload, and the CRC is scrambled with a Radio Network Temporary Identifier (RNTI) that serves as the UE's identity. Different RNTIs can be used for the purpose of the DCI message, such as UE-specific data transmission, power control commands, or RA responses (RARs). In other words, the RNTI is not explicitly transmitted; rather, it is included in the CRC calculation process and transmitted accordingly. Upon receiving a DCI message transmitted on the PDCCH, the UE uses the assigned RNTI to identify the CRC, and when the CRC is correct, the UE knows that the message has been sent.

[0119] For example, the DCI for scheduling PDSCH for SI can be scrambled with SI-RNTI. The DCI for scheduling PDSCH for RAR messages can be scrambled with RA-RNTI. The DCI for scheduling PDSCH for paging messages can be scrambled with P-RNTI. The DCI providing the Slot Format Indicator (SFI) can be scrambled with SFI-RNTI. The DCI providing Transmit (or Transport) Power Control (TPC) can be scrambled with TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled with the Cell RNTI (C-RNTI).

[0120] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. The DCI format 0_0 with CRC scrambled with C-RNTI can include the information in Table 4 below.

[0121] [Table 4]

[0122]

[0123] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled with C-RNTI. The DCI format 0_1 ​​with CRC scrambled with C-RNTI can include the information in Table 5 below.

[0124] [Table 5]

[0125]

[0126]

[0127] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. The DCI format 1_0 with CRC scrambled with C-RNTI can include the information in Table 6 below.

[0128] [Table 6]

[0129]

[0130] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled with C-RNTI. The DCI format 1_1 with CRC scrambled with C-RNTI can include the information in Table 7 below.

[0131] [Table 7]

[0132]

[0133]

[0134] [PDCCH: CORESET, REG, CCE, Search Space]

[0135] An example of a CORESET transmitting a DL control channel in a 5G wireless communication system. Figure 4 An example is shown where two control regions (Control Region #1 401 and Control Region #2 402) are configured in a single time slot 420 on the time axis, and the UE BWP 410 is configured on the frequency axis. Control regions 401 and 402 can be configured as specific frequency resources 403 within the entire system BWP 410 on the frequency axis. One or more OFDM symbols can be configured on the time axis, which can be defined as a CORESET duration 404. Figure 5 In the example, control region #1 401 is configured to a control region length of two symbols, and control region #4 402 is configured to a control region length of one symbol.

[0136] The control region in 5G described above can be configured in the UE by the BS via higher-layer signaling (e.g., SIB, MIB, or RRC signaling). Configuring a control region for the UE means providing the UE with information such as the control region ID, the frequency location of the control region, and the symbol length of the control region. For example, this may include the information in Table 8 below.

[0137] [Table 8]

[0138]

[0139]

[0140] In Table 8 above, the tci-statesPDCCH (which can be abbreviated as TCI state) configuration information may include information about one or more SS / PBCH block indices or channel state information reference signals (CSI-RS) indices that are co-located with the DMRS quasi-co-located in the corresponding control area.

[0141] Figure 5 An example of the basic units constituting the time and frequency resources available in 5G's DL control channels is shown. (Refer to...) Figure 5 The basic unit constituting the time and frequency resources of the DL control channel can be called a resource element group (REG) 503, and the REG 503 can be defined on the time axis by an OFDM symbol 501 and on the frequency axis by a physical RB (PRB) 502 (i.e., 12 subcarriers). The BS can configure the DL control channel allocation unit by cascading REG 503.

[0142] like Figure 5 As shown, if the basic unit for allocating DL control channels in 5G is a Control Channel Element (CCE) 504, then one CCE 504 can be composed of multiple REG 503s. Figure 5 In the example of REG 503 shown, REG 503 can consist of 12 REs, and if a CCE 504 consists of six REG 503s, then a CCE 504 can consist of 72 REs. When a downlink control area is set up, the area can consist of multiple CCE 504s, and a specific downlink control channel can be mapped to one or more CCE 504s and transmitted according to the aggregation level (AL) in the control area. CCE 504s in the control area are distinguished by numbers, and in this case, the numbers of CCE 504s can be assigned according to a logical mapping scheme.

[0143] Figure 5 The basic unit of the downlink control channel shown (i.e., REG 503) can contain the region to which the DCI is mapped and the region to which the DMRS 505 (a reference signal for decoding the RE) is mapped. Figure 5 As shown, three DMRS 505s can be transmitted within a single REG 503. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be, for example, 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the DL control channel. For example, if AL=L, a DL control channel can be transmitted via L CCEs. The UE needs to detect the signal without knowing the information about the DL control channel, and for blind decoding, a search space is defined to indicate the set of CCEs. The search space is the set of candidate control channels consisting of CCEs that the UE needs to attempt to decode at a given aggregation level, and because there are several aggregation levels that bundle 1, 2, 4, 8, or 16 CCEs, the UE has multiple search spaces. The search space set (set) can be defined as the set of search spaces for all configured aggregation levels.

[0144] The search space can be categorized into a shared search space and a UE-specific search space. A pre-defined group of UEs or all UEs can search the PDCCH shared search space to receive cell common control information, such as paging messages or dynamic scheduling of SIs. For example, the PDSCH scheduling allocation information for sending SIBs containing, for example, cell service provider information can be received by investigating the PDCCH shared search space. In the case of the shared search space, since a group of UEs or all UEs need to receive the PDCCH, it can be defined as a previously agreed set of CCEs. Scheduling allocation information for UE-specific PDSCHs or PUSCHs can be received by inspecting the PDCCH UE-specific search space. The UE-specific search space can be defined UE-specific using various system parameters and UE identifiers.

[0145] In 5G, parameters for the search space used for PDCCH can be configured in the UE by the BS via higher-layer signaling (e.g., SIB, MIB, or RRC signaling). For example, the BS can configure the UE with parameters such as the number of PDCCH candidates at each aggregation level L, the monitoring period of the search space, the monitoring timing of symbol cells in the time slots of the search space, the search space type (public search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the search space, and the control area index to be monitored in the search space. For example, information from Table 9 below may be included.

[0146] [Table 9]

[0147]

[0148]

[0149] Based on the configuration information, the BS can configure one or more search space sets for the terminal. According to an embodiment, the BS can configure search space set 1 and search space set 2 for the UE, and configure them to monitor DCI format A scrambled with X-RNTI in search space set 1 in the common search space, and monitor DCI format B scrambled with Y-RNTI in search space set 2 in the UE-specific search space.

[0150] Based on the above configuration information, one or more search space sets can exist in the public search space or the UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a public search space, and search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0151] In the public search space, combinations of DCI formats and RNTI can be monitored. Of course, this is not limited to the examples described below.

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

[0153] DCI format 2_0 with CRC scrambled by SFI-RNTI

[0154] DCI format 2_1 with CRC scrambled by INT-RNTI

[0155] DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI

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

[0157] Within a specific UE search space, combinations of DCI formats and RNTI can be monitored. However, this is not limited to the examples described below.

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

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

[0160] The specified RNTI can be defined and used as follows.

[0161] Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH

[0162] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH

[0163] Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

[0164] RA-RNTI: Used for scheduling PDSCH during the RA phase.

[0165] Paging RNTI (P-RNTI): Used to schedule the PDSCH sent in the paging process.

[0166] SI RNTI (SI-RNTI): Used to schedule the PDSCH sent in SI.

[0167] Interrupt RNTI (INT-RNTI): Used to indicate whether to puncture the PDSCH.

[0168] TPC for PUSCH RNTI (TPC-PUSCH-RNTI): Used to indicate power control commands for PUSCH.

[0169] TPC for PUCCH RNTI (TPC-PUCCH-RNTI): Used to indicate power control commands for PUCCH.

[0170] TPC for SRS RNTI (TPC-SRS-RNTI): Used to indicate power control commands for SRS.

[0171] The DCI format described above can follow the definitions in Table 10 below.

[0172] [Table 10]

[0173]

[0174] In 5G, the search space of the control region p and the aggregation level L in the search space set s can be represented by the following equation (1).

[0175] [Equation 1]

[0176]

[0177] - L: Aggregation Level

[0178] - Carrier index

[0179] - The total number of CCEs existing in control region p.

[0180] - Time slot index

[0181] - Number of PDCCH candidate groups at aggregation level L

[0182] - =0, …, -1: Aggregate-level PDCCH candidate group index

[0183] - = 0, …, -1

[0184] - , , , , ,

[0185] - UE identifier

[0186] In the context of public search spaces, It can be 0.

[0187] In the case of a specific search space for the UE It can be a value that changes depending on the UE's identifier (C-RNTI or ID configured in the UE by the BS) and the time index.

[0188] In 5G, multiple search space sets can be configured with different parameters, as shown in Table 10 below. Therefore, the set of search space sets monitored by the UE at each time point can be different. For example, when search space set #1 is configured for time slot X and search space set #2 is configured for time slot Y, and X is different from Y, the UE can monitor both search space set #1 and search space set #2 in a specific time slot, and can monitor either search space set #1 or search space set #2 in a specific time slot.

[0189] PDCCH: Span

[0190] The UE can perform UE capability reporting at each subcarrier interval for cases where multiple PDCCH monitoring locations exist within a time slot, and in this case, the concept of a "span" can be used. A span refers to the consecutive symbols of the PDCCH that the UE can monitor within a time slot, with each PDCCH monitoring location within a span. A span can be represented as (X, Y). Here, X indicates the minimum number of symbols in which the first symbols of two consecutive spans should be separated from each other, and Y indicates the number of symbols of the PDCCH that can be monitored within a span. In this case, the UE can monitor the PDCCH for a period of Y symbols starting from the first symbol of the span.

[0191] Figure 6 The diagram illustrates the situation where a UE in a wireless communication system can have multiple PDCCH monitoring locations in a time slot, via spans. Spans can be (X,Y) = (7,3)610, (4,3)620, and (2,2)630. Specifically, (610) represents the case where there are two spans in a time slot, which can be represented as (7,3). The interval between the first symbols of the two spans is represented as X=7, and the PDCCH monitoring locations can exist within a total of Y=3 symbols from the first symbol of each span, with search spaces 1 and 2 existing within Y=3 symbols. In (620), when there are a total of three spans, it can be represented as (4,3). The interval between the second and third spans is X'=5 symbols, which is greater than X=4.

[0192] PDCCH: UE Capability Report

[0193] The locations of the time slots containing the aforementioned public search space and UE-specific search space are indicated by the monitoringSlotPeriodicityAndOffset parameter in Table 9, and the symbol positions within the time slots are indicated by a bitmap using the monitoringSymbolsWithinSlot parameter in Table 9. Additionally, the UE can report the symbol positions within the time slots that it can monitor for search space to the BS via the following UE capabilities.

[0194] UE Capability 1 (hereinafter referred to as FG 3-1). When an MO exists in a time slot for a UE-specific search space or a common search space of Type 1 and Type 3, the UE capability indicates the ability to monitor the corresponding monitoring opportunity (MO) when the MO is in the first three symbols of the time slot, as shown in Table 11 below. UE capabilities are mandatory capabilities that all UEs supporting NR should support, and whether or not they support the capability is not explicitly reported to the BS.

[0195] [Table 11]

[0196]

[0197]

[0198] -UE Capability 2 (hereinafter referred to as FG 3-2). As shown in Table 12 below, a UE capability refers to the ability to monitor an MO (Multiple Object) for a common search space or a UE-specific search space when such MO exists in a time slot, regardless of the location of the starting symbol of the corresponding MO. This UE capability is optionally supported by the UE, and whether or not the UE supports this capability is explicitly reported to the BS.

[0199] [Table 12]

[0200]

[0201] -UE Capability 3 (hereinafter referred to as FG 3-5, 3-5a, or 3-5b). This UE capability indicates the patterns of MOs that the UE can monitor when multiple MOs exist in the time slot for the common search space or the UE-specific search space, as shown in Table 13 below. The above patterns consist of the starting symbol interval X between different MOs and the maximum symbol length of one MO. The (X,Y) combinations supported by the UE can be one or more of {(2,2), (4,3), (7,3)}. The UE may optionally support this UE capability, and whether it supports this capability and the above (X,Y) combinations are explicitly reported to the BS.

[0202] [Table 13]

[0203]

[0204]

[0205]

[0206] The UE can report to the BS whether it supports UE capability 2 and / or UE capability 3, along with related parameters. The BS can perform time-axis resource allocation in the common search space and the UE-specific search space based on the UE capabilities. During resource allocation, the BS can prevent the MO from being located in a position where UE surveillance is impossible.

[0207] QCL, TCI status

[0208] In wireless communication systems, one or more different antenna ports (which may be replaced by one or more channels, signals, or combinations thereof, but for ease of description, are collectively referred to as different antenna ports in the following description of this disclosure) can be associated with each other through QCL configuration, as shown in Table 14 below. The TCI state is used to announce the QCL relationship between the PDCCH (or PDCCH DMRS) and another RS ​​or between channels. When some reference antenna ports A (reference RS#A) and another target antenna port B (target RS#B) are quasi-co-located with each other, this means that the UE is allowed to apply all or some of the large-scale channel parameters estimated in antenna port A to channel measurements based on antenna port B. QCL may need to associate different parameters depending on the context, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by Doppler shift and Doppler spread, 3) radio resource management (RRM) affected by average gain, and 4) beam management (BM) affected by spatial parameters. Therefore, NR supports four types of QCL relationships, as shown in Table 14 below.

[0209] [Table 14]

[0210]

[0211] Spatial RX parameters can be collectively referred to as all or some of various parameters, such as angle of arrival (AoA), power angular spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit / receive channel correlation, transmit / receive beamforming, and spatial channel correlation.

[0212] QCL relationships can be configured for the UE via the RRC parameters TCI-State and QCL-Info, as shown in Table 15 below. The BS can configure one or more TCI states for the UE, indicating up to two QCL relationships (qcl-Type1 and qcl-Type2) for the RS (i.e., the target RS) whose ID is used to reference the TCI state. In this case, the QCL information (QCL-Info) included in each TCI state includes the serving cell index and BWP index of the reference RS indicated by the QCL information, the type and ID of the reference RS, and the QCL type, as shown in Table 14 above.

[0213] [Table 15]

[0214]

[0215]

[0216] Figure 7 An example of BS beam allocation configured according to TCI status is shown. (Refer to...) Figure 7 The BS can transmit information about N different beams to the UE through N different TCI states. For example, when... Figure 7 When N=3, the BS can announce / indicate that the qcl-Type2 parameters included in the three TCI states #0 700, TCI state #1 705 and TCI state #2 710 are associated with the CSI-RS or SSB corresponding to different beams, and are presented as set in QCL type D such that the antenna ports referencing different TCI states 700, 705 and 710 are associated with different spatial RX parameters (i.e. different beams).

[0217] Tables 16 to 20 below show the valid TCI state configurations based on the target antenna port type.

[0218] Table 16 below shows the effective TCI state configurations when the target antenna port is a CSI-RS for tracking, or in other words, when the target antenna port is a Tracking Reference Signal (TRS). A TRS refers to a CSI-RS in which the repetition parameter is not set and trs-Info is set to true non-zero power (NZP). The third configuration in Table 16 can be used for aperiodic TRS.

[0219] Table 16 below shows an example of an effective TCI state configuration when the target antenna port is TRS.

[0220] [Table 16]

[0221]

[0222] Table 17 below shows the valid TCI state configuration when the target antenna port is a CSI-RS for CSI. A CSI-RS for CSI refers to an NZP CSI-RS in which no parameter indicating repetition is set (e.g., repetition parameter) and trs-Info is not set to true.

[0223] Table 17 below shows an example of an effective TCI state configuration when the target antenna port is a CSI-RS for CSI.

[0224] [Table 17]

[0225]

[0226] Table 18 below shows the valid TCI status configuration when the target antenna port is a CSI-RS for beam management (BM), which can have the same meaning as a CSI-RS for L1 RSRP reporting. A CSI-RS for BM refers to an NZP CSI-RS in which the repeating parameter is set and has an On or Off value, and trs-Info is not set to True.

[0227] Table 18 below shows an example of an effective TCI state configuration when the target antenna port is a CSI-RS for BM (for L1 RSRP reporting).

[0228] [Table 18]

[0229]

[0230] Table 19 below shows the effective TCI state configuration when the target antenna port is PDCCH DMRS.

[0231] [Table 19]

[0232]

[0233] Table 20 below shows the effective TCI state configuration when the target antenna port is PDSCH DMRS.

[0234] [Table 20]

[0235]

[0236] According to the representative QCL configuration methods in Tables 16 to 20 above, the target antenna port and reference antenna port for each step are set and operated as "SSB" -> "TRS" -> "CSI-RS for CSI, or CSI-RS for BM, or PDCCHDMRS, or PDSCHDMRS". This can help the UE's reception operation, where statistical characteristics can be measured based on the SSB and TRS associated with the antenna port.

[0237] PDCCH: TCI state related

[0238] Specifically, the combinations of TCI states applicable to the PDCCH DMRS antenna port are shown in Table 21 below. In Table 21, the fourth row represents the combinations assumed by the UE before RRC configuration, and which are not possible after RRC configuration.

[0239] [Table 21]

[0240]

[0241] NR supports, for example Figure 8 The layered signaling method for dynamic allocation of PDCCH beams is shown. (Refer to...) Figure 8 The BS can configure N TCI states 805, 810, 815, and 820 for the UE via RRC signaling 800, and set some of them as the TCI state for CORESET (825). Subsequently, the BS can indicate one of the TCI states 830, 835, and 840 (845) for CORESET to the UE via MAC CE signaling. Afterwards, the UE receives the PDCCH based on the beam information included in the TCI state indicated by the MAC CE signaling.

[0242] Figure 9 The TCI indication MAC CE signaling structure for PDCCH DMRS is shown. (See reference...) Figure 9 The MAC CE consists of eight bytes, and Oct 1 (900) and Oct 2 (905) may contain different information depending on the fields of the respective MAC CE. The TCI indication MAC CE signaling used for PDCCH DMRS consists of, for example, 2 bytes (16 bits) and includes a five-bit serving cell ID 915, a three-bit CORESET ID 920, and a seven-bit TCI status ID 925.

[0243] Figure 10 An example of the beam configuration based on the search space and CORESET described above is shown. (Refer to...) Figure 10The BS can indicate one of the TCI state lists (1005) included in the CORESET (1000) configuration via MAC CE signaling. Thereafter, until another TCI state is indicated to the corresponding CORESET via other MAC CE signaling, the UE considers the same QCL information (beams #1, 1005) for one or more search spaces #1 1010, search space #2 1015, and search space #3 1020 associated with the CORESET. The above PDCCH beam assignment method is difficult to indicate beam changes that are delayed faster than MAC CE signaling, and applies the same beam to all CORESETs regardless of search space characteristics. Therefore, flexible PDCCH beam operation can be difficult. The following embodiments of this disclosure provide a method for configuring and operating PDCCH beams more flexibly. In describing embodiments of this disclosure, several individual examples are provided for ease of description; however, these examples are not mutually exclusive, but rather two or more can be combined and applied depending on the context.

[0244] The BS can configure one or more TCI states for a specific control area to the UE, and activate one of the configured TCI states via a MAC CE activation command. For example, {TCI state #0, TCI state #1, TCI state #2} is set as TCI states in control area #1. The BS can send an activation command to the UE via MAC CE to assume TCI state #0 as the TCI state of control area #1. Based on the TCI state activation command received via MAC CE, the UE can correctly receive the DMRS of the corresponding control area based on the QCL information of the activated TCI state.

[0245] For a control area where the index is set to 0 (control area #0), if the UE does not receive a MAC CE activation command for the TCI state of control area #0, the UE may assume that the DMRS transmitted in control area #0 is quasi-co-located with the SS / PBCH block identified in the initial access procedure or in a non-contention-based RA procedure not triggered by a PDCCH command.

[0246] For a control area (control area #X) where the index is set to a non-zero value, if no TCI state for control area #X is configured for the UE, or if one or more TCI states are configured but no MAC CE activation command is received to activate one of them, the UE may assume that the DMRS sent in control area #X is quasi-co-addressed with the SS / PBCH block identified during the initial access procedure.

[0247] [PDCCH: Related to QCL priority sorting rules]

[0248] The operation for determining the QCL priority used for PDCCH is described in detail below.

[0249] When a UE operates in CA mode within a frequency band or a single cell, and multiple cores in a BWP active in a single or multiple cells are equal to each other during a specific PDCCH monitoring period, or overlap over time with the same or different QCL-TypeD characteristics, the UE can select a specific core based on QCL priority sorting and monitor cores with the same QCL-TypeD characteristics as the corresponding core. In other words, when multiple cores overlap over time, only one QCL-TypeD characteristic can be received. In this case, the criteria for determining QCL priority can be as follows.

[0250] Standard 1. In the cell corresponding to the lowest index among the cells that include the common search space, connect to the CORESET with the lowest index in the common search space.

[0251] Standard 2. In the cell corresponding to the lowest index among the cells that include the UE-specific search space, connect to the CORESET that has the lowest index for the UE-specific search space.

[0252] As mentioned above, when the above criteria are not met, the following criteria apply. For example, when CORESETs overlap over time during a specific PDCCH monitoring period, if all CORESETs are not connected to the common search space but to the UE-specific search space, i.e., if criterion 1 is not met, then the UE can apply criterion 2 and omit criterion 1.

[0253] When the UE selects a CORESET based on the above criteria, the UE may consider the following two matters regarding the QCL information set in the CORESET. First, when the UE has CSI-RS 1 as the reference signal in which CORESET 1 has a QCL-TypeD relationship, where the reference signal in CSI-RS 1 with a QCL-TypeD relationship is SSB1, and the reference signal in another CORESET 2 with a QCL-TypeD relationship is SSB1, the UE may consider that the two CORESETs 1 and CORESET 2 have different QCL-TypeD characteristics. Second, when a UE has a CSI-RS 1 configured in cell 1 as a reference signal in which CORESET 1 has a QCL-TypeD relationship, where the reference signal in CSI-RS 1 with a QCL-TypeD relationship is SSB1, and it has a CSI-RS 2 configured in cell 2 as a reference signal in which CORESET 2 has a QCL-TypeD relationship, where the reference signal in CSI-RS 2 with a QCL-TypeD relationship is SSB1, the UE can consider that the two CORESETs have the same QCL-TypeD characteristics.

[0254] Figure 12A method for selecting receivable cores by considering priorities when a UE receives a DL control channel in a wireless communication system, according to an embodiment, is illustrated. For example, the UE may be configured to receive multiple overlapping cores over a specific PDCCH monitoring period (segment) 1210, and the multiple cores may be associated with a common search space for multiple cells or a UE-specific search space. In the corresponding PDCCH monitoring period, core 1 1215 associated with common search space 1 may exist in BWP 1 1200 of cell 1, and core 1 1220 associated with common search space 1 and core 2 1225 associated with UE-specific search space 2 may exist in BWP 11205 of cell 2. CORESETs 1215 and 1220 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in BWP 1 of cell 1, and CORESET 1225 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in BWP 1 of cell 2. Therefore, if Standard 1 is applied to the corresponding PDCCH monitoring period 1210, all other CORESETs with the same QCL-TypeD reference signal as CORESET 1215 can be received. Thus, the UE can receive CORESETs 1215 and 1220 in the corresponding PDCCH monitoring period 1210. As another example, the UE can be configured to receive multiple CORESETs that overlap over time in a specific PDCCH monitoring period 1240, and these multiple CORESETs can be associated with a shared search space for multiple cells or a UE-specific search space. During the corresponding PDCCH monitoring period, CORESET 1 1245 associated with UE-specific search space 1 and CORESET 2 1250 associated with UE-specific search space 2 can exist in BWP 1 1230 of cell 1, and CORESET 1 1255 associated with UE-specific search space 1 and CORESET 2 1260 associated with UE-specific search space 3 can exist in BWP 1 1235 of cell 2. CORESET 1245 and CORESET 1250 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in BWP 1 of cell 1, CORESET 1255 can have a QCL-TypeD relationship with CSI-RS resource 1 configured in BWP 1 of cell 2, and CORESET 1260 can have a QCL-TypeD relationship with CSI-RS resource 2 configured in BWP 1 of cell 2.However, when Standard 1 is applied to the corresponding PDCCH monitoring period 1240, since there is no common search space, Standard 2 can be applied as the next standard. If Standard 2 is applied to the corresponding PDCCH monitoring period 1240, all other CORESETs with the same QCL-TypeD reference signal as CORESET 1245 can be received. Therefore, the UE can receive CORESETs 1245 and 1250 in the corresponding PDCCH monitoring period 1240.

[0255] Rate matching / punching

[0256] When arbitrary time and frequency resources A used to transmit arbitrary symbol sequences A overlap with time and frequency resources B, rate matching or puncturing can be considered as the transmission / reception of channel A taking into account resource C in the overlapping region between resources A and B. The specific operation can follow the following steps.

[0257] Rate matching operation

[0258] The BS can map channel A to only the remaining resource area of ​​the entire resource A, excluding resource C which corresponds to the area of ​​overlapping resource B, to send the symbol sequence A to the UE and transmit it. For example, when the symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the BS can sequentially map the symbol sequence A to {resource #1, resource #2, resource #4}, which is the remaining resource in resource A excluding {resource #3} corresponding to resource C, and transmit it. Therefore, the BS can map the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4} respectively and transmit it.

[0259] The UE can determine resources A and B based on the scheduling information for symbol sequence A from the BS, and thus determine resource C as the overlapping area between resources A and B. The UE can receive symbol sequence A assuming that it has already been mapped and transmitted in the remaining area of ​​resource A except for resource C. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE can assume that symbol sequence A has been sequentially mapped to {resource #1, resource #2, resource #4} to receive it, where {resource #1, resource #2, resource #4} are the remaining resources in resource A besides {resource #3} corresponding to resource C. Therefore, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4} to perform a subsequent series of reception operations.

[0260] Drilling operation

[0261] When there is a resource C corresponding to the area of ​​the entire resource A that overlaps with the resource B to send symbol sequence A to the UE, the BS maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C. Instead, it can only perform transmission in the remaining resource areas of resource A other than resource C. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the BS can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4} respectively. Transmission can be performed only in the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to resource A's {resource #1, resource #2, resource #4}, which are the remaining resources besides {resource #3} corresponding to resource C. However, the {symbol #3} mapped to {resource #3} corresponding to resource C can be omitted. Therefore, the BS can map symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4} respectively and transmit the symbol sequence.

[0262] The UE can determine resources A and B based on the scheduling information for symbol sequence A from the BS, and thus determine resource C as the overlapping area between resources A and resource B. The UE can receive symbol sequence A, assuming that symbol sequence A has been mapped to the entire resource A, but only performs transmission in the remaining area of ​​resource region A excluding resource C. For example, when symbol sequence A consists of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE can receive them. Assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but does not send {symbol #3} mapped to {resource #3} corresponding to resource C. Furthermore, the symbol sequence {symbol #1, symbol #2, symbol #4} mapped to {resource #1, resource #2, resource #4} is the remaining resource of resource A besides {resource #3} corresponding to resource C. Therefore, the UE can assume that symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4} to perform a subsequent series of reception operations.

[0263] The following describes a method for configuring rate matching resources for 5G communication systems. Rate matching refers to adjusting the signal size by taking into account the amount of resources available for signal transmission. For example, rate matching of a data channel may mean adjusting the data size by avoiding mapping and transmitting data channels for specific time and frequency resource areas.

[0264] Figure 11 A method for transmitting / receiving data by the BS and UE considering DL data channel and rate matching resources is shown.

[0265] Reference Figure 11The diagram illustrates PDSCH 1101 and rate matching resource 1102. The BS can configure one or more rate matching resources 1102 to the UE via higher-layer signaling (e.g., RRC signaling). The rate matching resource (1102) configuration information may include time axis resource allocation information 1103, frequency axis resource allocation information 1104, and periodicity information 1105. In the following description, the bitmap corresponding to the frequency axis resource allocation information 1104 is referred to as the "first bitmap", the bitmap corresponding to the time axis resource allocation information 1103 is referred to as the "second bitmap", and the bitmap corresponding to the periodicity information 1105 is referred to as the "third bitmap". When all or part of the time and frequency resources of the scheduled data channel 1101 overlap with the configured rate matching resource 1102, the BS can rate match the data channel 1101 in the rate matching resource (1102) portion and transmit it, and the UE can assume that the data channel 1101 has been rate matched in the rate matching resource (1102) portion and then perform reception and decoding.

[0266] The BS can dynamically notify the UE via DCI whether rate matching of the data channel is performed in the configured rate matching resource section through additional configuration (which corresponds to the "rate matching indicator" in the DCI format described above). Specifically, the BS can select some of the configured rate matching resources, group them into rate matching resource groups, and use a bitmap scheme to notify the UE via DCI whether rate matching of the data channel is performed for each rate matching resource group. For example, when four rate matching resources RMR#1, RMR#2, RMR#3, and RMR#4 are configured, the BS can configure rate matching groups RMG#1={RMR#1, RMR#2} and RMG#2={RMR#3, RMR#4}, and can notify the UE whether rate matching has been completed in RMG#1 and RMG#2 in two bits of the DCI field. For example, if rate matching is required, it can be indicated as "1", and if rate matching is not required, it can be indicated as "0".

[0267] 5G supports "RB symbol level" and "RE level" granularity as a method for configuring the aforementioned rate-matching resources to the UE. More specifically, the following configuration method can be followed.

[0268] RB symbol level

[0269] The UE can receive configurations for up to four RateMatchPatterns per BWP via higher-layer signaling, and a RateMatchPattern can include the following.

[0270] - As a reserved resource in BWP, it can include resources where the corresponding time and frequency resource regions are configured as a combination of symbol-level bitmaps and RB-level bitmaps on the frequency axis. Reserved resources can span one or two time slots. A time-domain pattern (periodicityAndPattern) can be additionally configured where the time and frequency regions configured in each RB-level and symbol-level bitmap pair are repeated.

[0271] This may include time-domain and frequency-domain resource regions configured as CORESET in BWP, as well as resource regions corresponding to time-domain modes configured with search space where the corresponding resource regions are repeated.

[0272] RE Level

[0273] The UE can receive the following configuration via higher-layer signaling.

[0274] The configuration information (lte-CRS-ToMatchAround) of the RE corresponding to the LTE CRS (e.g., cell-specific reference signal or common reference signal) mode may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift value (v-shift), the LTE carrier center subcarrier location information (carrierFreqDL) from the reference frequency point (e.g., reference point A), the LTE carrier bandwidth information (carrierBandwidthDL), and the subframe configuration information (mbsfn-SubframeConfigList) corresponding to the Multicast Broadcast Single Frequency Network (MBSFN). The UE can determine the location of the CRS in the NR slot corresponding to the LTE subframe based on the above information.

[0275] Configuration information regarding resource sets corresponding to one or more Zero Power (ZP) CSI-RS in the BWP can be included in higher-level signaling.

[0276] LTE CRS rate matching related

[0277] For the coexistence of LTE and the new RAT (NR) (LTE-NR coexistence), NR provides the NR UE with the ability to configure a cell-specific reference signal (CRS) mode for LTE. More specifically, the CRS mode can be provided via RRC signaling that includes at least one parameter in either the ServingCellConfig IE (Information Element) or the ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, and crs-RateMatch-PerCORESETPoolIndex-r16.

[0278] Rel-15 NR provides the capability to configure one CRS pattern per serving cell via the lte-CRS-ToMatchAround parameter. In Rel-16 NR, this capability has been extended to allow multiple CRS patterns per serving cell. More specifically, one CRS pattern can be configured for one LTE carrier in a single transmit and receive point (TRP) configured UE, and two CRS patterns can be configured for one LTE carrier in a multi-TRP configured UE. For example, in a single-TRP configured UE, up to three CRS patterns can be configured per serving cell via the lte-CRS-PatternList1-r16 parameter. As another example, CRS can be configured for each TRP in a multi-TRP configured UE. In other words, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. However, if two TRPs are configured as described above, the crs-RateMatch-PerCORESETPoolIndex-r16 parameter determines whether the CRS modes of both TRP1 and TRP2 are applied to a specific PDSCH or only the CRS mode for one TRP is applied. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is enabled, only the CRS mode of one TRP is applied; otherwise, the CRS modes of both TRPs are applied.

[0279] Table 22 shows the ServingCellConfig IE including CRS mode, and Table 23 shows the RateMatchPatternLTE-CRS IE including at least one parameter for CRS mode.

[0280] [Table 22]

[0281]

[0282]

[0283] [Table 23]

[0284]

[0285] [PDSCH: Processing Time]

[0286] Next, the PDSCH processing time is described. When the BS schedules the UE to transmit PDSCH using DCI format 1_0, 1_1, or 1_2, the UE may require PDSCH processing time to receive the PDSCH by applying the transmission method indicated by the DCI (Modulation / Demodulation and Coding Indicator Index (MCS), DMRS-related information, time and frequency resource allocation information, etc.). In NR, the PDSCH processing time is defined by taking this into account. The UE's PDSCH processing time can be expressed in equation (2) below.

[0287] [Equation 2]

[0288]

[0289] The T described in equation (2) above proc,1 In this context, each variable can have the following meanings.

[0290] N1: The number of symbols determined based on UE processing capability 1 or 2 and the parameter set μ based on the UE's capabilities. When UE processing capability 1 is reported according to the UE capability report, it can have the values ​​in Table 24a below. When UE processing capability 2 is reported and configured to be usable via higher-layer signaling, it can have the values ​​in Table 24b. The parameter set μ can correspond to μ PDCCH μ PDSCH and μ UL The minimum value of T proc,1 Maximize, and μ PDCCH μ PDSCH and μ UL These can refer to the parameter set of the PDCCH that has already been scheduled for PDSCH, the parameter set of the scheduled PDSCH, and the parameter set of the UL channel in which HARQ-ACK is to be sent.

[0291] Table 24a below shows an example of PDSCH processing time under the condition of PDSCH processing capacity 1.

[0292] [Table 24a]

[0293]

[0294] Table 24b below shows an example of PDSCH processing time with a PDSCH processing capacity of 2.

[0295] [Table 24b]

[0296]

[0297] κ 64

[0298] T ext When the UE uses a shared spectrum channel access scheme, the UE can calculate T. ext And apply it to the PDSCH processing time. Otherwise, T ext It is assumed to be 0.

[0299] If l1, representing the PDSCH DMRS position value, is 12, then N in Table 24a 1,0 It has a value of 14, otherwise it has a value of 13.

[0300] For PDSCH mapping type A, if the last symbol of the PDSCH is the i-th symbol in the slot in which the PDSCH is transmitted, and i < 7, then d 1,1 It is 7-i, otherwise d 1,1 It is 0.

[0301] d2: When a PUCCH with a high priority index overlaps with a PUCCH or PUSCH with a low priority index over time, d2 of the PUCCH with the high priority index can be set to the value reported from the UE. Otherwise, d2 is 0.

[0302] When PDSCH mapping type B is used for UE processing capability 1, d 1,1 The value can be determined based on the number of symbols L of the scheduled PDSCH and the number of overlapping symbols d between the PDCCH that schedules the PDSCH and the scheduled PDSCH.

[0303] If L≥7, then d 1,1 =0.

[0304] If L≥4 and L≤6, then d 1,1 =7-L.

[0305] If L=3, then d 1,1 =min(d,1).

[0306] If L=2, then d 1,1 =3+d.

[0307] When PDSCH mapping type B is used for UE processing capability 2, d 1,1The value can be determined based on the number of symbols L of the scheduled PDSCH and the number of overlapping symbols d between the PDCCH that schedules the PDSCH and the scheduled PDSCH.

[0308] If L≥7, then d 1,1 =0.

[0309] If L≥4 and L≤6, then d 1,1 =7-L.

[0310] When L=2

[0311] When the scheduled PDCCH exists within a CORESET consisting of three symbols, and the CORESET and the scheduled PDSCH have the same start symbol, d 1,1 =3.

[0312] Otherwise, d 1,1 =d.

[0313] When the UE supports capability 2 in a given serving cell, and the UE sets higher-layer signaling processingType2Enabled to enabled for the cell, the PDSCH processing time based on the UE's processing capability 2 can be applied.

[0314] If the position of the first UL transmission symbol of the PUCCH containing HARQ-ACK information (the corresponding position can be considered in terms of K1- defined at the HARQ-ACK transmission time, the PUCCH resources used for HARQ-ACK transmission, and the TA effect) does not have a T after the last symbol of the PDSCH in the first UL transmission symbol. proc,1 If the PDSCH processing time is sufficient, the UE should send a valid HARQ-ACK message. In other words, the UE should only send a PUCCH including a HARQ-ACK if sufficient time has been allocated for PDSCH processing. Otherwise, the UE may not provide the BS with a valid HARQ-ACK message corresponding to the scheduled PDSCH. proc,1 It can be used for both normal and extended CP scenarios. For a PDSCH consisting of two PDSCH transmission positions within a time slot, d is calculated relative to the first PDSCH transmission position within the corresponding time slot. 1,1 .

[0315] [PDSCH: Receive preparation time during cross-carrier scheduling]

[0316] Next, in μ, which serves as the parameter set for the next scheduled PDCCH. PDCCH μ is sent and used as the parameter set of the PDSCH scheduled via the corresponding PDCCH. PDSCHIn the case of cross-carrier scheduling, N- describes the UE's PDSCH reception preparation time as defined by the time interval between the PDCCH and PDSCH. pdsch .

[0317] If μ PDCCH < μ PDSCH Then, in slot N after the last symbol of the PDCCH that has already been scheduled for PDSCH... pdsch The scheduled PDSCH may not be sent before the first symbol of a symbol. The transmission symbol of the corresponding PDSCH may include DM-RS.

[0318] If μ PDCCH > μ PDSCH Then, N is the last symbol of the PDCCH that has already been scheduled for PDSCH. pdsch At each symbol, a scheduled PDSCH can be transmitted. The transmission symbol of the corresponding PDSCH may include DM-RS.

[0319] Table 25 below shows N based on the scheduled PDCCH subcarrier spacing. pdsch Examples.

[0320] [Table 25]

[0321]

[0322] Detection Reference Signal (SRS)

[0323] The BS can configure at least one SRS configuration for each UL BWP to transmit configuration information for SRS transmission, and can configure at least one SRS resource set for each SRS configuration for the UE. As an example, the BS and UE can exchange the following higher-level signaling information to transmit information about the SRS resource set.

[0324] -srs-ResourceSetId: SRS resource set index

[0325] -srs-ResourceIdList: A collection of SRS resource indexes referenced by the SRS resource collection.

[0326] -resourceType: The timeline transmission configuration of the SRS resources referenced by the SRS resource set. This can be set to one of "Periodic," "Semi-Persistent," and "Aperiodic." When set to "Periodic" or "Semi-Persistent," the associated CSI-RS information may be provided depending on the usage of the SRS resource set. If set to "Aperiodic," an aperiodic SRS resource trigger list and slot offset information can be provided, and the associated CSI-RS information may be provided depending on the usage of the SRS resource set.

[0327] - Usage: The usage configuration of SRS resources referenced by the SRS resource set, and can be set to one of "beamManagement", "codebook", "nonCodebook", and "antennaSwitching".

[0328] alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: This provides parameter configuration for adjusting the transmit power of SRS resources referenced by the SRS resource set.

[0329] The UE can understand that the SRS resources included in the SRS resource index set referenced by the SRS resource set follow the information configured in the SRS resource set.

[0330] The BS and UE can send / receive higher-layer signaling information to transmit separate configuration information for SRS resources. As an example, separate configuration information for SRS resources may include time-frequency axis mapping information in the time slots of the SRS resource, which may include information for frequency hopping within or between time slots of the SRS resource. Separate configuration information for SRS resources may include the time axis transmission configuration of the SRS resource and may be set to one of "periodic," "semi-persistent," and "aperiodic." This may impose limitations on having the same time axis transmission configuration as the set of SRS resources that includes the SRS resource. If the time axis transmission configuration of the SRS resource is set to "periodic" or "semi-persistent," the SRS resource transmission period and time slot offset (e.g., periodicityAndOffset) may be additionally included in the time axis transmission configuration.

[0331] The BS can trigger the activation or deactivation of SRS transmissions to the UE via RRC signaling or higher-layer signaling including MAC CE signaling or L1 signaling (e.g., DCI). For example, the BS can activate or deactivate periodic SRS transmissions via higher-layer signaling to the UE. The BS can indicate activation of a set of SRS resources where resourceType is set to periodicity via higher-layer signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The time-frequency axis resource mapping in the time slots of the transmitted SRS resources follows the resource mapping information configured in the SRS resources, and the time slot mapping, including transmission period and time slot offset, follows periodicityAndOffset configured in the SRS resources. The spatial domain transmission filter applied to the transmitted SRS resources can refer to spatial relation information configured in the SRS resources, or it can refer to associated CSI-RS information configured in the SRS resource set including the SRS resources. The UE can transmit SRS resources within a UL BWP activated for periodic SRS resources activated via higher-layer signaling.

[0332] For example, the BS can activate or deactivate semi-persistent SRS transmission via higher-layer signaling to the UE. The BS can instruct the activation of an SRS resource set via MAC CE signaling, and the UE can transmit SRS resources referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to SRS resource sets where resourceType is set to semi-persistent. The time-frequency axis resource mapping in the timeslots of the transmitted SRS resources follows the resource mapping information configured in the SRS resources, and the timeslot mapping, including transmission period and timeslot offset, follows periodicityAndOffset configured in the SRS resources. The spatial domain transmission filter applied to the transmitted SRS resources can refer to spatial relation information configured in the SRS resources, or it can refer to associated CSI-RS information configured in the SRS resource set that includes the SRS resources. If the spatial relation information is configured in the SRS resources but not followed, the spatial domain transmission filter can be determined by referring to the configuration information of the spatial relation information transmitted via MAC CE signaling that activates semi-persistent SRS transmission. The UE can transmit SRS resources within a UL BWP activated for semi-persistent SRS resources activated via higher-layer signaling.

[0333] For example, the BS can trigger aperiodic SRS transmissions via the DCI to the UE. The BS can indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) via the SRS request field of the DCI. The UE understands that the SRS resource set indicated by the DCI in the aperiodic SRS resource trigger list, which includes the configuration information of the SRS resource set, has been triggered. The UE can transmit SRS resources referenced by the triggered SRS resource set. The time-frequency axis resource mapping in the time slots of the transmitted SRS resources follows the resource mapping information configured in the SRS resources. The time slot mapping of the transmitted SRS resources can be determined by the time slot offset between the PDCCH including the DCI and the SRS resources, and it can refer to the values ​​included in the time slot offset set configured in the SRS resource set. Specifically, as the time slot offset between the PDCCH including the DCI and the SRS resources, the value indicated by the time domain resource assignment field of the DCI can be applied from the offset values ​​included in the time slot offset set configured in the SRS resource set. The spatial domain transmission filter applied to the transmitted SRS resources can refer to spatial relationship information configured in the SRS resources, or it can refer to associated CSI-RS information configured in the SRS resource set that includes the SRS resources. The UE can transmit SRS resources within a ULBWP activated for aperiodic SRS resources triggered by DCI.

[0334] When the BS triggers an aperiodic SRS transmission to the UE via DCI, the UE may need a minimum time interval between the SRS being transmitted and the PDCCH containing the DCI that triggered the aperiodic SRS transmission in order to apply configuration information for the SRS resources and transmit the SRS. The time interval for the UE's SRS transmission can be defined as the number of symbols between the last symbol of the PDCCH containing the DCI that triggered the aperiodic SRS transmission and the first symbol of the first SRS resource mapped to be transmitted. The minimum time interval can be determined with reference to the PUSCH preparation time required for the UE to prepare for PUSCH transmission. Depending on the set of SRS resources used, including the SRS resources to be transmitted, the minimum time interval can have different values. For example, by referring to the UE's PUSCH preparation time, the minimum time interval can be determined as N² symbols, taking into account the UE's processing capabilities. When considering the use of the SRS resource set, including the SRS resources to be transmitted, and the use of the SRS resource set is set to "codebook" or "antennaSwitching", the minimum time interval can be determined to be N². When the use of the SRS resource set is set to "nonCodebook" or "beamManagement", the minimum time interval can be determined to be N² + 14 symbols. The UE can transmit aperiodic SRS when the time interval used for aperiodic SRS transmission is greater than or equal to the minimum time interval, and the UE can ignore the DCI that triggers aperiodic SRS when the time interval used for aperiodic SRS transmission is less than the minimum time interval.

[0335] The spatialRelationInfo configuration information in Table 26 below is applied to the beam for SRS transmission corresponding to the beam information about the corresponding reference signal by referring to a reference signal.

[0336] [Table 26]

[0337]

[0338]

[0339] For example, the configuration of spatialRelationInfo can include information such as that shown in Table 27 below.

[0340] [Table 27]

[0341]

[0342] Referring to the `spatialRelationInfo` configuration, the SS / PBCH block index, CSI-RS index, or SRS index can be set to the reference signal index to be referenced for use with beam information about a specific reference signal. The higher-layer signaling `referenceSignal` is configuration information indicating which reference signal will be referenced for the corresponding SRS transmission, and `ssb-Index`, `csi-RS-Index`, and `srs` refer to the indexes of the SS / PBCH block, CSI-RS, and SRS, respectively. If the value of the higher-layer signaling `referenceSignal` is set to "ssb-Index", the UE can apply the receive beam already used to receive the SS / PBCH block corresponding to `ssb-Index` as the transmission beam for the corresponding SRS transmission. If the value of the higher-layer signaling `referenceSignal` is set to "csi-RS-Index", the UE can apply the receive beam already used to receive the CSI-RS corresponding to `csi-RS-Index` as the transmission beam for the corresponding SRS transmission. If the value of the higher-layer signaling referenceSignal is set to "SRS", the UE can apply the transmission beam that has already been used to transmit the SRS corresponding to the SRS as the transmission beam for the corresponding SRS transmission.

[0343] [PUSCH: Transmission Scheme Related]

[0344] Next, the scheduling method for PUSCH transfers is described. PUSCH transfers can be dynamically scheduled by a UL license in the DCI, or operated by a configured license type 1 or type 2. Dynamic scheduling instructions for PUSCH transfers are available in DCI format 0_0 or 0_1.

[0345] Configuration type 1 PUSCH transports can be semi-statically configured via receiving configuredGrantConfig, which includes rrc-ConfiguredDuplinkGrant (Table 28), through higher-layer signaling, without receiving UL authorization in the DCI. Configuration type 2 PUSCH transports can be semi-persistently scheduled by UL authorization in the DCI after receiving configuredGrantConfig, which does not include rrc-ConfiguredDuplinkGrant (Table 28), through higher-layer signaling. When operating a PUSCH transport with a configured authorization, the parameters applied to the PUSCH transport are applied via configuredGrantConfig, which is also a higher-layer signaling parameter in Table 28, in addition to scaling dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and UCI-OnPUSCH provided by pusch-Config (Table 29). If the UE receives the transformPrecoder via the configuredGrantConfig, which is a higher-layer signaling in Table 28, the UE applies the tp-pi2BPSK from the push-Config in Table 29 to the PUSCH transport that is configured to be permitted.

[0346] [Table 28]

[0347]

[0348]

[0349]

[0350] Next, the PUSCH transmission method is described. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. PUSCH transmission may follow a codebook-based transmission method or a non-codebook-based transmission method depending on whether the value of txConfig in push-Config in Table 29 (which is a higher-layer signaling) is "codebook" or "nonCodebook".

[0351] As described above, PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, or semi-statically configured via configured permissions. If the UE receives a command to schedule a PUSCH transmission via DCI format 0_0, the UE performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the smallest ID in the active UL BWP in the serving cell, and in this case, the PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmissions via DCI format 0_0 in a BWP that does not have a PUCCH resource configured with pucch-spatialRelationInfo. If the UE has not yet been configured with txConfig in push-Config in Table 29, the UE does not expect to be scheduled via DCI format 0_1.

[0352] [Table 29]

[0353]

[0354]

[0355] Next, codebook-based PUSCH transmission is described. Codebook-based PUSCH transmission can be operated dynamically via DCI format 0_0 or 0_1, or semi-statically configured with configured permissions. If dynamically scheduled via codebook-based PUSCH DCI format 0_1 ​​or semi-statically configured with configured permissions, the UE determines the precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), Transport Precoding Matrix Indicator (TPMI), and transport rank (number of PUSCH transport layers).

[0356] In this scenario, the SRI can be provided via the SRI field in the DCI, or configured via srs-ResourceIndicator as higher-layer signaling. During codebook-based PUSCH transmission, the UE can have at least one, and at most two, SRS resources configured for it. When the UE receives an SRI via the DCI, the SRS resource indicated by the corresponding SRI is the SRS resource among those transmitted before the PDCCH including the SRI. TPMI and transport rank can be provided via the precoding information and layer number fields in the DCI, or configured via precodingAndNumberOfLayers as higher-layer signaling. TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, TPMI indicates the precoder to be applied to the configured SRS resource. If the UE is configured with multiple SRS resources, TPMI indicates the precoder to be applied to the SRS resource indicated by the SRI.

[0357] The precoder to be used for PUSCH transmission is selected from a UL codebook with the same number of antenna ports as the nrofSRS-Ports value in the SRS-Config, which serves as higher-layer signaling. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the push-Config, which serves as higher-layer signaling. The codebookSubset in the push-Config, which serves as higher-layer signaling, can be set to one of "fullyAndPartialAndNonCoherent," "partialAndNonCoherent," or "nonCoherent" based on the UE capability reported by the UE to the BS. If the UE reports "partialAndNonCoherent" as a UE capability, the UE does not expect the codebookSubset value, which serves as higher-layer signaling, to be set to "fullyAndPartialAndNonCoherent." Furthermore, if the UE reports "nonCoherent" as a UE capability, the UE does not expect the codebookSubset value, which serves as higher-layer signaling, to be set to either "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent." If nrofSRS-Ports in the SRS-ResourceSet used as higher-layer signaling indicates two SRS antenna ports, the UE does not expect the value of codebookSubset used as higher-layer signaling to be set to "partialAndNonCoherent".

[0358] A UE can be configured with an SRS resource set, where the usage value in the SRS-ResourceSet (for higher-layer signaling) is set to "codebook," and an SRS resource within the corresponding SRS resource set can be indicated via SRI. If several SRS resources are configured in the SRS resource set, and the usage value in the SRS-ResourceSet (for higher-layer signaling) is set to "codebook," the UE expects the same value to be set for all SRS resources in the nrofSRS-Ports value within the SRS-Resource (for higher-layer signaling).

[0359] The UE can send one or more SRS resources from a set of SRS resources whose values ​​are set to "codebook" to the BS based on higher-layer signaling. The BS selects one of the SRS resources sent by the UE and instructs the UE to perform PUSCH transmission using the transmission beam information for the corresponding SRS resource. In this case, in codebook-based PUSCH transmission, the SRI is used as an index for selecting an SRS resource and is included in the DCI. Additionally, the BS includes in the DCI information indicating the TPMI and rank to be used by the UE for PUSCH transmission. The UE performs PUSCH transmission using the SRS resource indicated by the SRI by applying a precoder indicated by the rank and a TPMI indicated by the transmission beam of the SRS resource.

[0360] Next, non-codebook-based PUSCH transmission is described. Non-codebook-based PUSCH transmission can be operated dynamically via DCI format 0_0 or 0_1, or semi-statically configured by configured permissions. When at least one SRS resource is configured in an SRS resource set whose value used in the SRS-ResourceSet as higher-layer signaling is set to "nonCodebook", the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0361] For an SRS resource set whose value is set to "nonCodebook" in the SRS-ResourceSet used for higher-layer signaling, the UE can be configured with an NZP CSI-RS. The UE can perform calculations on the precoder used for SRS transmission by measuring the NZP CSI-RS resources connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the information about the precoder used for SRS transmission to be updated.

[0362] If the value of resourceType in the SRS-ResourceSet, used as higher-layer signaling, is set to "Aperiodic," then a connected NZP CSI-RS can be indicated by an SRS request as a field in DCI format 0_1 ​​or 1_1. In this case, if the connected NZP CSI-RS resource is an aperiodic NZP CSI resource, it indicates the existence of a connected NZP CSI-RS for cases where the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not "00." In this case, DCI should not indicate cross-carrier or cross-BWP scheduling. Furthermore, if the value of the SRS request indicates the presence of an NZP CSI-RS, then the NZP CSI-RS is located in the time slot in which the PDCCH including the SRS request field is transmitted. In this case, the TCI state configured for the scheduled subcarrier is not set to QCL-typeD.

[0363] If a periodic or semi-persistent SRS resource set is configured, the associated CSI-RS in the SRS-ResourceSet as higher-layer signaling can be used to indicate the connected NZP CSI-RS. For non-codebook-based transmissions, the UE does not expect spatialRelationInfo as higher-layer signaling for SRS resources and associated CSI-RS in the SRS-ResourceSet as higher-layer signaling to be configured together.

[0364] When multiple SRS resources are configured for a UE, the UE can determine the precoder and transmission rank to be applied to PUSCH transmissions based on the SRI indicated by the BS. In this case, the SRI can be indicated by the SRI field in the DCI or configured as srs-ResourceIndicator as higher-layer signaling. Similar to the codebook-based PUSCH transmission described above, when the UE receives an SRI via the DCI, the SRS resource indicated by the corresponding SRI indicates the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmissions. The maximum number of SRS resources and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol within an SRS resource set are determined by the UE capabilities reported by the UE to the BS. In this case, the SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set whose value is set to "nonCodebook" can be configured for use as a higher-level signaling SRS-ResourceSet, and up to four SRS resources can be configured for non-codebook-based PUSCH transport.

[0365] The BS sends an NZP CSI-RS connected to the SRS resource set to the UE, and the UE calculates a precoder to be used for transmission of one or more SRS resources in the SRS resource set based on the measurements received at the time of NZP CSI-RS reception. The UE may apply the calculated precoder when sending to the BS one or more SRS resources in the SRS resource set that are set to "nonCodebook", and the BS selects one or more SRS resources from the received SRS resources. In this case, in nonCodebook-based PUSCH transmission, the SRI indication may represent an index of a combination of one or more SRS resources, and the SRI is included in the DCI. In this case, the number of SRS resources indicated by the SRI sent by the BS may be the number of transport layers of the PUSCH. The UE applies the precoder to each layer for SRS resource transmission and transmits the PUSCH.

[0366] PUSCH: Preparation time

[0367] When the BS schedules the UE to send PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require PUSCH preparation time to apply the transmission precoding method, transmission layer number, and spatial domain transmission filter to the transmission method (SRS resource) indicated by the DCI and send the PUSCH. Therefore, the NR defines the PUSCH preparation time. The UE's PUSCH preparation time can be expressed in equation (3) below.

[0368] [Equation 3]

[0369] T proc,2 = max(( N2+ d 2,1 + d2)( 2048 + 144 ) κ2 -μ T c + T ext + T switch , d 2,2 )

[0370] T described in equation (3) above proc,2 In this context, each variable can have the following meanings.

[0371] N2: The number of symbols determined based on UE processing capability 1 or 2 and the parameter set μ of the UE's capabilities. When UE processing capability 1 is reported based on the UE capability report, it can have the value in Table 30 below. When UE processing capability 2 is reported and configured to be usable via higher-layer signaling, it can have the value in Table 31 below.

[0372] [Table 30]

[0373]

[0374] [Table 31]

[0375]

[0376] d 2,1 If all resource elements of the first OFDM symbol transmitted by PUSCH are configured to consist only of DM-RS, the symbol number is set to 0; otherwise, it is set to 1.

[0377] κ: 64

[0378] μ: or This follows T proc,2 Larger values. The instruction includes the set of parameters of the DL that the DCI's PDCCH is sent to schedule the PUSCH, and The set of parameters that indicates the UL to which PUSCH is sent.

[0379] T c This has , , .

[0380] d 2,2 This follows the BWP handover time when the DCI of the PUSCH scheduling is instructing a BWP handover; otherwise, it is 0.

[0381] d2: When a PUCCH overlaps with both a PUSCH with a higher priority index and a PUCCH with a lower priority index in an OFDM symbol on the time axis, the d2 value of the PUSCH with the higher priority index is used. Otherwise, d2 is 0.

[0382] T ext When the UE uses a shared spectrum channel access scheme, the UE can calculate T. ext And apply it to the PUSCH preparation process time. Otherwise, assume T ext It is 0.

[0383] T switch When the UL switching interval is triggered, T switch It is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0384] Considering the timeline resource mapping information of PUSCH scheduled via DCI and the impact of TA between UL and DL, if T starts after the last symbol of the PDCCH that includes the DCI scheduling PUSCH... proc,2If the first symbol of the PUSCH begins before the first UL symbol of the CP, then the BS and UE determine that the PUSCH preparation time is insufficient. Otherwise, the BS and UE determine that the PUSCH preparation time is sufficient. The UE can send the PUSCH only if the PUSCH preparation time is sufficient, and can ignore the DCI that schedules the PUSCH if the PUSCH preparation time is insufficient.

[0385] PUSCH: Related to repeated transmissions

[0386] The following describes in detail the retransmission of the UL data channel in a 5G system. The 5G system supports two types, PUSCH retransmission type A and PUSCH retransmission type B, as the retransmission method for the UL data channel. The UE can have either PUSCH retransmission type A or B configured for it via higher-layer signaling.

[0387] PUSCH Repeat Transfer Type A

[0388] As described above, the symbol length and starting symbol position of the UL data channel can be sent through a time-domain resource allocation method in a time slot, and the BS can notify the UE of the number of repeated transmissions through higher-layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0389] - The UE can repeatedly transmit UL data channels with the same length and start symbol as the configured UL data channels in consecutive time slots based on the number of repeated transmissions received from the BS. In this case, when at least one symbol of the UL data channel configured by the BS to the UE via DL or the time slot configured to the UE is configured via DL, the UE omits UL data channel transmission, but counts the number of repeated UL data channel transmissions.

[0390] PUSCH Repeat Transfer Type B

[0391] As described above, as a time-domain resource allocation method in a time slot, the start symbol and length of the UL data channel can be sent, and the BS can notify the UE of the number of repetitions via higher-layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).

[0392] First, based on the start symbol and length of the UL data channel configured above, the nominal repetition of the UL data channel is determined as follows. The time slot at the start of the nth nominal repetition is determined by... The symbol given, and the one that begins in that time slot, is... Given. The time slot at which the nth nominal repetition begins is determined by... The symbol given, and which ends in the time slot, is... Given: Here, n=0,..., numberofrepetitions-1, S indicates the start symbol of the configured UL data channel, and L indicates the symbol length of the configured UL data channel. The time slot indicating the start of PUSCH transmission, and Indicates the number of symbols in each time slot.

[0393] The UE determines invalid symbols for PUSCH repetitive transmission type B. Symbols configured via DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are determined as invalid symbols for PUSCH repetitive transmission type B. Alternatively, invalid symbols can be configured in higher-level parameters (e.g., InvalidSymbolPattern). Since higher-level parameters (e.g., InvalidSymbolPattern) provide symbol-level bitmaps in one or two slots, invalid symbols can be configured. A 1 in the bitmap indicates an invalid symbol. Additionally, the periodicity and pattern of the bitmap can be configured via higher-level parameters (e.g., periodicityAndPattern). If a higher-level parameter (e.g., InvalidSymbolPattern) is configured, and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter indicates 1, the UE applies the invalid symbol pattern; if it indicates 0, the UE does not apply the invalid symbol pattern. If a higher-level parameter (e.g., InvalidSymbolPattern) is configured, and the InvalidSymbolPatternIndicator-ForDCIFormat0_1 or InvalidSymbolPatternIndicator-ForDCIFormat0_2 parameter is not configured, the UE applies the invalid symbol mode.

[0394] After identifying invalid symbols, for each nominal repeat, the UE may treat all symbols except the invalid symbols as valid symbols. If each nominal repeat includes one or more valid symbols, then the nominal repeat may include one or more actual repeats. Here, each actual repeat includes a consecutive set of valid symbols that can be used for PUSCH repeat transmission type B in a time slot.

[0395] Figure 14An example of PUSCH repetition transmission type B in a wireless communication system according to an embodiment is shown. The UE can set the start symbol to 0 and the UL data channel length L to 14, and can set the number of repetitions to 16. In this case, nominal repetition is indicated in 16 consecutive time slots (1401). Thereafter, the UE can determine that symbols set to DL symbols in each nominal repetition 1401 are invalid symbols. The UE determines that symbols set to 1 in invalid symbol mode 1402 are invalid symbols. In each nominal repetition, when valid symbols rather than invalid symbols consist of one or more consecutive symbols in a time slot, they are set as actual repetitions and transmitted (1403).

[0396] For repeated PUSCH transfers, NR version 16 can define the following additional methods for UL-licensed PUSCH transfers and configuration-licensed PUSCH transfers across time slot boundaries.

[0397] Method 1 (Micro-slot-level Repetition): Two or more PUSCH repetitions are scheduled within a single slot or across the boundaries of consecutive slots, with a UL license. For Method 1, the time-domain resource allocation information in the DCI indicates the resources for the first repetition. The time-domain resource information for the remaining repetitions can be determined based on the UL or DL ​​direction determined for each symbol in each slot and the time-domain resource information of the first repetition. Each repetition occupies consecutive symbols.

[0398] Method 2 (Multi-segment Transmission): Two or more repeated PUSCH transmissions are scheduled in consecutive time slots via a single UL license. In this case, one transmission is assigned to each time slot, and the start point or repetition length can be different for each transmission. Furthermore, in Method 2, the time-domain resource allocation information in the DCI indicates the start point and repetition length for all repeated transmissions. When repeated transmissions are performed within a single time slot via Method 2, if several consecutive symbol bundles exist in the corresponding time slot, each repeated transmission is performed for each UL symbol bundle. If a unique bundle of consecutive UL symbols exists in the corresponding time slot, a single PUSCH repeated transmission is performed according to the method of NR Release 15.

[0399] Method 3: Schedule two or more repeated PUSCH transmissions in consecutive time slots using two or more UL licenses. In this case, one transmission is assigned to each time slot, and the nth UL license can be received before the PUSCH transmission scheduled by the (n-1)th UL license ends.

[0400] Method 4: One or more PUSCH repetitions within a single time slot or two or more PUSCH repetitions at the boundaries of consecutive time slots can be supported via a UL license or a configured license. The number of repetitions indicated by the BS to the UE is only a nominal value, and the number of repetitions actually performed by the UE can be greater than the nominal number of repetitions. The time-domain resource allocation information in the DCI or configured license indicates the resources for the first repetition indicated by the BS. Time-domain resource information for the remaining repetitions can be determined by the UL or DL ​​direction of the reference symbol and the resource information for at least the first repetition. If the time-domain resource information for the repetitions indicated by the BS exceeds the time slot boundary or includes a UL / DL switching point, the corresponding repetition can be divided into multiple repetitions. In this case, one repetition can be included for each UL period within a time slot.

[0401] PUSCH: Frequency hopping process

[0402] The frequency hopping of the UL data channel (Physical UL Shared Channel (PUSCH)) in the 5G system is described in detail below.

[0403] 5G supports two methods for frequency hopping for each PUSCH repetition transmission type as frequency hopping methods for UL data channels. First, PUSCH repetition transmission type A supports intra-slot frequency hopping and inter-slot frequency hopping, while PUSCH repetition transmission type B supports inter-repetition frequency hopping and inter-slot frequency hopping.

[0404] The intra-slot frequency hopping method supported by PUSCH repetitive transmission type A is a method in which the UE changes and transmits frequency domain allocation resources by setting a frequency offset in two hops within a time slot. In intra-slot frequency hopping, the starting RB of each hop can be represented in the following equation (4).

[0405] [Equation 4]

[0406]

[0407] In equation (4), i=0 and i=1 represent the first jump and the second jump, respectively, and This represents the starting RB in the UL BWP and is calculated according to the frequency resource allocation method. This represents the frequency shift between two hops through higher-level parameters. The number of symbols in the first hop can be expressed as... And the number of symbols in the second jump can be represented as . It is the length of the PUSCH transmission within a time slot and is expressed as the number of OFDM symbols.

[0408] Next, the inter-slot frequency hopping method supported by PUSCH repetitive transmission types A and B is a method in which the UE changes and transmits allocated resources in the frequency domain in each time slot by a set frequency offset. In inter-slot frequency hopping, The starting RB for each time slot period can be represented in equation (5) below.

[0409] [Equation 5]

[0410]

[0411] In equation (5), Indicates the current timeslot number in a multi-slot PUSCH transmission. This represents the starting RB in the UL BWP and is calculated according to the frequency resource allocation method. This represents the frequency offset between two hops through higher-level parameters.

[0412] Next, the inter-repetition frequency hopping method supported by PUSCH repetition transmission type B moves and transmits resources allocated in the frequency domain for one or more actual repetitions within each nominal repetition by a set frequency offset. The RB serves as the index of the starting RB in the frequency domain for one or more actual repetitions within the nth nominal repetition. start (n) can be represented in equation (6) below.

[0413] [Equation 6]

[0414]

[0415] In equation (6), n represents the nominally repeating index, and The RB offset between two hops is represented by high-level parameters.

[0416] PUSCH: Reuse rules for AP / SP CSI reports

[0417] The following describes in detail a method for measuring and reporting channel states in a 5G communication system. CSI may include Channel Quality Information (CQI), Precoding Matrix Indicator (PMI), CSI-RS Resource Indicator (CRI), SS / PBCH Block Resource Indicator (SSBRI), Layer Indicator (LI), Rank Indicator (RI), and / or L1 Reference Signal Received Power (RSRP). The BS can control the time and frequency resources used for the aforementioned CSI measurements and reporting by the UE.

[0418] For CSI measurement and reporting, the UE can receive configuration information for at least one of the following via higher-layer signaling: configuration information for N (≥1) CSI reports (CSI-ReportConfig), configuration information for M (≥1) RS transmission resources (CSI-ResourceConfig), or list information for one or two trigger states (CSI-AperiodicTriggerStateList, CSI-SemiPersistentOnPUSCH-TriggerStateList). More specifically, the above-mentioned configuration information for CSI measurement and reporting can be shown in Tables 32 to 38 below.

[0419] Table 32 below shows the CSI-ReportConFIG.

[0420] [Table 32]

[0421] IE CSI-ReportConfig is used to configure periodic or semi-persistent reports to be sent on the PUCCH of a cell that includes CSI-ReportConfig, or to configure semi-persistent or non-periodic reports to be sent on the PUSCH triggered by a DCI received on a cell that includes CSI-ReportConfig (in which case the cell on which the report is sent is determined by the received DCI). See TS 38.214

[19] , Clause 5.2.1.

[0422] CSI-ReportConfig Information Elements

[0423]

[0424]

[0425]

[0426]

[0427]

[0428]

[0429]

[0430]

[0431] Table 33 below shows the CSI-ResourceConFIG.

[0432] [Table 33]

[0433] IE CSI-ResourceConfig defines one or more of a set of NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet, and / or CSI-SSB-ResourceSet.

[0434] CSI-ResourceConfig Information Element

[0435]

[0436]

[0437]

[0438] Table 34 below shows the NZP-CSI-RS-ResourceSet.

[0439] [Table 34]

[0440] The IE NZP-CSI-RS-ResourceSet is a set of non-zero power (NZP) CSI-RS resources (with their IDs) and set-specific parameters.

[0441] NZP-CSI-RS-ResourceSet Information Element

[0442]

[0443]

[0444]

[0445] Table 35 below shows the CSI-SSB-ResourceSet.

[0446] [Table 35]

[0447] The IE CSI-SSB-ResourceSet is used to configure a set of SS / PBCH block resources, which refers to the SS / PBCH indicated in ServingCellConfigCommon.

[0448] CSI-SSB-ResourceSet Information Element

[0449]

[0450] Table 36 below shows the CSI-IM-ResourceSet.

[0451] [Table 36]

[0452] The IE CSI-IM-ResourceSet is used to configure one or more CSI Interference Management (IM) resources (with their IDs) and a set of set-specific parameters.

[0453] CSI-IM-ResourceSet Information Element

[0454]

[0455]

[0456] Table 37 below shows the CSI-AperiodicTriggerStateList.

[0457] [Table 37]

[0458] The CSI-AperiodicTriggerStateList IE is a list used to configure aperiodic trigger states for the UE. Each code point in the DCI field "CSI Request" is associated with a trigger state. Upon receiving a value associated with a trigger state, the UE will perform CSI-RS (reference signal) measurements and aperiodic reporting on L1 based on all entries in the associatedReportConfigInfoList used for that trigger state.

[0459] CSI-AperiodicTriggerStateList Information Element

[0460]

[0461]

[0462]

[0463] Table 38 below shows the CSI-SemiPersistentOnPUSCH-TriggerStateList.

[0464] [Table 38]

[0465] The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is a list of trigger states used to configure the UE for semi-persistent reporting of channel state information on L1. See also TS 38.214

[19] , Clause 5.2.

[0466] CSI-SemiPersistentOnPUSCH-TriggerStateList Information Element

[0467]

[0468]

[0469] For the aforementioned CSI report configurations (CSI-ReportConfig), each CSI-ReportConfig can be associated with a CSI resource configuration, which is associated with the report configuration and a DL BWP identified by the higher-layer parameter BWP ID (bwp-id) given as CSI-ResourceConFIG. As a time-domain report for each CSI-ReportConfig, "aperiodic," "semi-persistent," and "periodic" schemes can be supported, and can be configured from the BS to the UE via the reportConfigType parameter configured from the higher-layer. The semi-persistent CSI reporting method supports 'semi-persistent on PUCCH' and 'semi-persistent on PUSCH'. In the case of periodic or semi-persistent CSI reporting methods, the UE can receive the configuration of the PUCCH or PUSCH resources for transmitting CSI from the BS via higher-layer signaling. The period and slot offset of the PUCCH or PUSCH resources used for transmitting CSI can be provided as a parameter set for the UL BWP configured to transmit CSI reports. In the case of a non-periodic CSI reporting method, the UE can receive the scheduling of the PUSCH resources used for transmitting CSI from the BS via L1 signaling (DCI format 0_1 ​​above).

[0470] For the aforementioned CSI resource configurations (CSI-ResourceConfig), each CSI resource configuration (CSI-ReportConfig) may include S (≥1) CSI resource sets (given as the higher-layer parameter csi-RS-ResourceSetlist). The list of CSI resource sets may consist of an NZP CSI-RS resource set and an SS / PBCH block set or a CSI interference measurement (CSI-IM) resource set. Each CSI resource configuration may reside in a DL BWP identified by the higher-layer parameter bwp-id. CSI resource configurations may be connected to CSI reporting configurations of the same DL BWP. The time-domain operation of the CSI-RS resources in the CSI resource configuration may be set to one of "aperiodic," "periodic," or "semi-persistent" according to the higher-layer parameter resourcetype. For periodic or semi-persistent CSI resource configurations, the number of CSI-RS resource sets may be limited to S=1. The configuration period and slot offset may be given as a parameter set of the DL BWP identified by bwp-id. The UE may receive the configuration of one or more CSI resource configurations for channel or interference measurement from the BS via higher-layer signaling. For example, the following CSI resources may be included.

[0471] CSI-IM Resources for Interference Measurement

[0472] NZP CSI-RS Resources for Interference Measurement

[0473] NZP CSI-RS resources for channel measurements

[0474] For a set of CSI-RS resources associated with resources where the higher-level parameter resourceType is configured as "aperiodic", "periodic", or "semi-persistent", the trigger state of the resource configuration for channel or interference measurements of one or more component cells (CCs) and the CSI report configuration where reportType is set to "aperiodic" can be configured by the higher-level parameter CSI-AperiodicTriggerStateList.

[0475] UE aperiodic CSI reporting can use PUSCH, and periodic CSI reporting can use PUCCH. Semi-persistent CSI reporting can be performed using PUSCH when triggered or activated by DCI, or using PUCCH after activation by MAC control element (CE). As mentioned above, CSI resource configuration can also be configured aperiodicly, periodically, or semi-persistently. Combinations between CSI reporting configurations and CSI resource configurations can be supported based on Table 39 below.

[0476] [Table 39]

[0477] Table 5.2.1.4-1: Triggering / activation of CSI reports for possible CSI-RS configurations.

[0478]

[0479] Aperiodic CSI reports can also be triggered using the aforementioned DCI format 0_1 ​​"CSI Request" corresponding to the scheduling DCI for PUSCH. The UE can monitor the PDCCH, obtain DCI format 0_1, and acquire the scheduling information and CSI request indicator for PUSCH. The CSI request indicator can be set with NTS (=0, 1, 2, 3, 4, 5, or 6) bits and can be determined by higher-layer signaling (reportTriggerSize). One of one or more aperiodic CSI report trigger states, which can be configured by higher-layer signaling (csi-Aperiodic TriggerStateList), can be triggered by the CSI request indicator.

[0480] - When all bits of the CSI request field are 0, this can mean that a CSI report is not requested.

[0481] - If the number of CSI trigger states M in the configured CSI-AperiodicTriggerStateLite is greater than 2NTs-1, then the M CSI trigger states can be mapped to 2NTs-1 according to the predefined mapping relationship, and one of the trigger states can be indicated by the CSI request field.

[0482] If the number M of CSI trigger states in the configured CSI-AperiodicTriggerStateLite is equal to or less than 2NTs-1, then one of the M CSI trigger states can be indicated by the CSI Request field.

[0483] Table 40 below shows an example of the relationship between a CSI request indicator and the CSI triggering state that can be indicated by the indicator.

[0484] [Table 40]

[0485]

[0486] For a CSI resource in a CSI triggered state, triggered by the CSI request field, the UE can perform measurements and generate CSIs (including at least one or more of the aforementioned CQI, PMI, CRI, SSBRI, LI, RI, and L1-RSRP). The UE can transmit the acquired CSI via a PUSCH scheduled by the corresponding DCI format 0_1. When a bit corresponding to the UL data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "1", the UL data (UL-SCH) and the acquired CSI can be multiplexed onto the PUSCH resource scheduled by DCI format 0_1 ​​and transmitted. When a bit corresponding to the UL data indicator (UL-SCH indicator) in DCI format 0_1 ​​indicates "0", only the CSI, without UL data (UL-SCH), can be mapped onto the PUSCH resource scheduled by DCI format 0_1 ​​and transmitted.

[0487] Figure 13 An example of a non-periodic CSI reporting method is shown.

[0488] exist Figure 13 In Example 1300, the UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1301 and obtaining scheduling information and CSI request information for PUSCH 1305. The UE can obtain resource information for the CSI-RS 1302 to be measured from the received CSI request indicator. The UE can determine the time to perform the measurement on the CSI-RS (1302) resource based on the reception time of DCI format 0_1 ​​and the offset parameter (aperiodicTriggringOffset mentioned above) in the CSI resource set configuration (e.g., NZP CSI-RS resource set configuration (NZP-CSI-RS-ResourceSet)). Specifically, the UE can receive the configuration of the offset value X of the parameter aperiodicTriggeringOffset in the NZP-CSI-RS resource set configuration from the BS via higher-layer signaling, and the configured offset value X can refer to the offset between the time slot for receiving the DCI used to trigger the aperiodic CSI report and the time slot for transmitting the CSI-RS resource. For example, the aperiodicTriggeringOffset parameter value and the offset value X can have the mapping relationship shown in Table 41 below.

[0489] [Table 41]

[0490]

[0491] exist Figure 13Example 1300 illustrates an example where the aforementioned offset value is set to X=0. In this case, the UE can receive the DCI format 0_1 ​​used to trigger an aperiodic CSI report in the time slot (corresponding to...). Figure 13 The UE receives CSI-RS 1302 in time slot 0 (1306) and reports CSI information measured using the received CSI-RS to the BS via PUSCH 1305. The UE can obtain the scheduling information for PUSCH 1305 used for CSI reporting (information corresponding to each field of DCI format 0_1) from DCI format 0_1. As an example, the UE can obtain information about the time slot for transmitting PUSCH 1305 from the time-domain resource allocation information for PUSCH 1305 described above. Figure 13 In Example 1300, the UE obtains 3 as the K2 value corresponding to the slot offset value from PDCCH to PUSCH, so that PUSCH 1305 can be transmitted in slot 3 1309, which is three slots away from slot 0 1306, which is the reception time of PDCCH 1301.

[0492] exist Figure 13 In Example 1310, the UE can obtain DCI format 0_1 ​​by monitoring PDCCH 1311, obtaining scheduling information for PUSCH 1315, and CSI request information. The UE can obtain resource information for the CSI-RS 1312 to be measured from the received CSI request indicator. Figure 13 Example 1310 illustrates an example where the aforementioned offset value for CSI-RS is set to X=1. In this case, the UE can receive the DCI format 0_1 ​​used to trigger an aperiodic CSI report in the time slot (corresponding to...). Figure 13 The UE receives CSI-RS 1312 in the next time slot (corresponding to time slot 1317) after time slot 0 (1316), and reports the CSI information measured using the received CSI-RS to the BS via PUSCH 1315. The UE can obtain the scheduling information for PUSCH 1315 used for CSI reporting (information corresponding to each field of DCI format 0_1 ​​as described above) from DCI format 0_1. As an example, the UE can obtain information about the time slot for transmitting PUSCH 1315 from the time domain resource allocation information for PUSCH 1315 described above. Figure 13 In Example 1310, the UE obtains 3 as the K2 value corresponding to the slot offset value from PDCCH to PUSCH, so that PUSCH 1315 can be transmitted in slot 3 1319, which is three slots away from slot 0 1306, which is the reception time of PDCCH 1301.

[0493] Aperiodic CSI reports may include at least one or both of CSI Part 1 and CSI Part 2, and may be multiplexed with transport blocks when transmitted via PUSCH. For multiplexing, a CRC may be inserted into the input bits of the aperiodic CSI, followed by encoding and rate matching, and then mapped to resource elements in the PUSCH in a specific pattern and transmitted. Depending on the encoding method or the length of the input bits, the CRC insertion may be omitted. When multiplexing either CSI Part 1 or CSI Part 2 included in the aperiodic CSI report, the number of modulation symbols calculated for rate matching can be calculated as shown in Table 42 below.

[0494] [Table 42]

[0495]

[0496]

[0497] Specifically, in PUSCH repetition schemes A and B, the UE can multiplex and transmit the aperiodic CSI report only during the first repetition of a PUSCH repetition. This is why the multiplexed aperiodic CSI report information is encoded using a polar code scheme, and in this case, each PUSCH repetition should have the same frequency and time resource allocation for multiplexing across several PUSCH repetitions. Specifically, in PUSCH repetition type B, each actual repetition can have a different OFDM symbol length, allowing the aperiodic CSI report to be multiplexed and transmitted only during the first PUSCH repetition.

[0498] For PUSCH retransmission scheme B, when the UE receives a DCI for activating a semi-persistent CSI report or scheduling an aperiodic CSI report without scheduling a transport block, the nominal retransmission value can be assumed to be 1, even though the number of PUSCH retransmissions set by higher-layer signaling is greater than 1. When the UE schedules or activates an aperiodic or semi-persistent CSI report based on PUSCH retransmission scheme B without scheduling a transport block, the UE can expect the first nominal retransmission to be the same as the first actual retransmission. If, after activating the second CLI-RS using a DCI, the first nominal retransmission differs from the first actual retransmission for a PUSCH including a semi-persistent CSI sent based on PUSCH retransmission scheme B without scheduling a DCI, the first nominal retransmission can be ignored.

[0499] UE Capability Report

[0500] In LTE and NR, a UE can perform a process to report the capabilities supported by the UE to the corresponding BS while connected to the serving BS. In the following description, this is referred to as UE capability reporting.

[0501] The BS can transmit UE capability query messages to a UE in a connected state to request capability reports. This message can include UE capability requests for each Radio Access Technology (RAT) type of the BS. Requests for each RAT type can include supported frequency band combination information. In the case of UE capability query messages, corresponding UE capabilities for multiple RAT types can be requested through a single RRC message container, or the BS can include multiple UE capability query messages containing UE capability requests for each RAT type and transmit them to the UE. In other words, multiple UE capability queries can be repeated in a single message, and the UE can configure its corresponding UE capability information message and report it multiple times. In next-generation mobile communication systems, UE capability requests can be made for Multi-RAT Dual Connectivity (MR-DC) and NR, LTE, and E-UTRA-NR Dual Connectivity (EN-DC). Although UE capability query messages are typically sent earlier after the UE connects to the BS, they can also be requested by the BS under any circumstances, as needed.

[0502] After receiving the UE capability report request from the BS in the above steps, the UE configures its capabilities based on the RAT type and frequency band information requested from the BS. The method for configuring UE capabilities in the NR system is described below.

[0503] 1. If a list of LTE and / or NR bands is provided to the UE when requesting UE capabilities from the BS, the UE configures a band combination (BC) for EN-DC and NR Independent (SA). In other words, the UE configures a candidate list of BCs for EN-DC and NR SA based on the bands requested from the BS via the FreqBandlist. Band priorities can have the order of priority listed in the FreqBandlist.

[0504] 2. If the BS sets the “eutra-nr-only” flag or the “eutra” flag and requests a UE capability report, the UE completely removes those flags used for NR SA BC from the configured BC candidate list. This operation can only occur when the LTE BS (eNB) requests “eutra” capability.

[0505] 3. Then, the UE removes the fallback BC from the BC candidate list configured in the above steps. Here, a fallback BC refers to a BC that can be obtained by removing the frequency band corresponding to at least one SCell from any BC, and since the BC before removing the frequency band corresponding to at least one SCell can cover the fallback BC, it can be omitted. This step applies to MR-DC, i.e., LTE frequency bands also apply. The remaining BCs after this step constitute the final "candidate BC list".

[0506] 4. The UE selects a BC of the appropriate RAT type from the final "Candidate BC List" to choose the BC to report. In this step, the UE configures the supportedBandCombinationList in a predetermined order. In other words, the UE configures the BCs to be reported and UE capabilities according to a preset rat-Type order (nr->eutra-nr->eutra). The UE configures featureSetCombination for the configured supportedBandCombinationList and configures a "Candidate Feature Set Combination" list in the candidate BC list, in which the list of fallback BCs (including capabilities of the same or lower steps) has been removed. The "Candidate Feature Set Combination" can include the entire feature set combination for NR and EUTRA-NR BCs and can be obtained from the feature set combination of the UE-MRDC-Capabilities container and the UE-NR-Capabilities.

[0507] 5. Furthermore, if the requested rat type is eutra-nr and has effects, then featureSetCombinations are included in both containers of UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set only includes UE-NR-Capabilities.

[0508] After the UE capabilities are configured, the UE transmits a UE capability information message, including the UE capabilities, to the BS. The BS then performs appropriate scheduling and transmit / receive management on the UE based on the UE capabilities received from the UE.

[0509] [CA / DC related]

[0510] Figure 15 The radio protocol structures of the BS and UE in single-cell 1510, CA 1520 and dual-connectivity 1530 scenarios are shown according to embodiments.

[0511] Reference Figure 15The radio protocols of the next-generation mobile communication system include NR Service Data Adaptation Protocol (NR SDAP) S25 or S70, NR Packet Data Convergence Protocol (NR PDCP) S30 or S65, NR Radio Link Control (NR RLC) S35 or S60, and NR Media Access Control (NR MAC) S40 or S55 in each of the UE and BS.

[0512] The main functions of NR SDAP S25 and S70 may include some of the following functions.

[0513] Transmit user plane data

[0514] Mapping between QoS flows and DRB for both DL and UL

[0515] Mark QoS flow IDs in DL and UL groups

[0516] Reflected QoS flow to DRB mapping for UL SDAP PDU

[0517] For SDAP layer devices, the UE can configure whether to use SDAP layer functionality or the SDAP layer device header via RRC messages for each PDCP layer device, each bearer, or each logical channel. If the SDAP header is already configured, the UE can instruct the UE to update or reset the mapping information of data bearers and QoS flows for UL and DL via a one-bit NAS-reflected QoS indicator and a one-bit AS-reflected QoS indicator. The SDAP header can include QoS flow ID information indicating QoS. QoS information can be used as data prioritization or scheduling information to seamlessly support service.

[0518] The main functions of NR PDCP S30 and S65 may include some of the following functions.

[0519] Robust header compression and decompression

[0520] Transmission of user data

[0521] Sequential delivery of upper-layer PDUs

[0522] Unordered delivery of upper-layer PDUs

[0523] PDCP PDU reordering for received

[0524] Repeat detection of low-level SDUs

[0525] PDCP SDU retransmission

[0526] Encryption and decryption

[0527] Timer-based SDU discarding in UL

[0528] In the above context, the reordering of NR PDCP devices refers to the function of reordering PDC PDUs received from lower layers in sequence based on the PDCP sequence number (SN), and may include the function of transmitting data to higher layers in the reordered order. The reordering of NR PDCP devices may include immediate transmission regardless of order, recording PDCP PDUs lost during reordering, reporting the status of lost PDCP PDUs to the transmitting part, and requesting retransmission of lost PDCP PDUs.

[0529] The main functions of NR RLC S35 and S60 may include some of the following functions.

[0530] upper-layer PDU transmission

[0531] Sequential delivery of upper-layer PDUs

[0532] Unordered delivery of upper-layer PDUs

[0533] Error correction via ARQ

[0534] Cascading, segmentation, and reassembly of RLC SDUs

[0535] RLC data PDU resegmentation

[0536] RLC data PDU reordering

[0537] Duplicate detection

[0538] Protocol error detection

[0539] RLC SDU discard

[0540] RLC Reconstruction

[0541] In the above, the sequential delivery of NR RLC devices refers to the function of sequentially delivering RLC SDUs received from the lower layer to the upper layer. Sequential delivery of NR RLC devices may include the function of reassembling and transmitting several RLC SDUs for which one RLC SDU has been partitioned and received, and may include the function of reordering received RLC PDUs based on the RLC SN or PDCP SN, the function of reordering and recording lost RLC PDUs, the function of reporting the status of lost RLC PDUs to the transmitting side, and the function of requesting retransmission of lost RLC PDUs. Sequential delivery of NR RLC devices may include the function of sequentially transmitting only RLC SDUs (if any) preceding the lost RLC SDU, or may include the function of sequentially transmitting all RLC SDUs received before the scheduled timer expires, even if a lost RLC SDU exists. Sequential delivery of NR RLC devices may include the function of sequentially delivering all RLC SDUs received up to the current layer, even if a lost RLC SDU exists, if the scheduled timer expires. RLC PDUs can be processed in the order of reception (arrival order, regardless of SN order) and delivered to the PDCP device regardless of order (out-of-order delivery). For segments, segments stored in a buffer or to be received later can be received and reconstructed into a single complete RLC PDU. The entire RLC PDU is then processed and transmitted to the PDCP device. The NR RLC layer may not include concatenation functionality, and this functionality can be performed by the NR MAC layer or replaced by multiplexing functions of the NR MAC layer.

[0542] Out-of-order delivery of NR RLC devices refers to the immediate transmission of RLC SDUs received from the lower layer to the upper layer regardless of their order. If an original RLC SDU is split into several RLC SDUs and then received, out-of-order delivery may include reassembling and transmitting them and storing the RLC SN or PDCP SN of the received RLC PDUs, sorting them, and recording lost RLC PDUs.

[0543] NR MAC S40 and S55 can connect to several NR RLC layer devices configured in a UE, and the main functions of NR MAC can include some of the following functions.

[0544] Mapping between logical channels and transport channels

[0545] MAC SDU multiplexing / demultiplexing

[0546] Dispatch information reporting

[0547] Error correction via HARQ

[0548] Priority processing between logical channels of a UE

[0549] Priority processing among dynamically scheduled UEs

[0550] MBMS Service Identifier

[0551] Transmission format selection

[0552] filling

[0553] The NR PHY layers S45 and S50 can encode and modulate higher-layer data channels into OFDM symbols, transmit OFDM symbols via wireless channels, or demodulate OFDM symbols received via wireless channels, decode the channels, and transmit them to higher layers.

[0554] The detailed structure of a radio protocol architecture can vary depending on the carrier (or cell) operation scheme. As an example, when the BS transmits data to the UE based on a single carrier (or cell), the BS and UE use a protocol architecture with a single structure for each layer, as shown in reference numeral S00. However, when the BS transmits data to the UE based on a CA using multiple carriers in a single TRP, the BS and UE use a protocol architecture with a single structure up to the RLC, as shown in reference numeral S10, but multiplexing is performed at the PHY layer via the MAC layer. As another example, when the BS transmits data to the UE based on dual connectivity (DC) using multiple carriers in multiple TRPs, the BS and UE use a protocol architecture with a single structure up to the RLC, as shown in reference numeral S20, but multiplexing is performed at the PHY layer via the MAC layer.

[0555] Referring to the above description related to PDCCH and beam configuration, due to the lack of support for PDCCH retransmission, current Rel-15 and Rel-16 systems struggle to achieve the required reliability in scenarios demanding high reliability (such as URLLC). This disclosure provides a method for PDCCH retransmission via multiple TRPs, enhancing the PDCCH reception reliability of the UE. The specific method is described in detail below in the following embodiments.

[0556] Embodiments of this disclosure are described in detail below with reference to the accompanying drawings. This disclosure applies to both FDD and TDD systems. As used herein, the term "higher signaling" (or "higher layer signaling") may refer to a method of transmitting signals from a BS to a UE using a physical layer DL data channel or from a UE to a BS using a physical layer UL data channel, and may be used interchangeably with RRC signaling, PDCP signaling, or MAC CE.

[0557] In this disclosure, when determining whether cooperative communication is applicable, the UE may use various methods, such as having a specific format for the PDCCH that allows the allocation of the PDSCH to which cooperative communication is applicable, including specific indicators for indicating whether cooperative communication is applicable, scrambling the PDCCH that allows the allocation of the PDSCH to which cooperative communication is applicable with a specific RNTI, or assuming that cooperative communication is applicable during a specific time period indicated by a higher layer. Hereinafter, for ease of description, the UE receiving the PDSCH with applied cooperative communication under similar conditions is referred to as the NC-JT case.

[0558] In the following, in this disclosure, "determining the priority between A and B" may refer to various other ways, such as selecting the one with higher priority according to a predetermined priority rule and performing the operation accordingly, or omitting or discarding the operation of the one with lower priority.

[0559] In the following, within this disclosure, the above examples are described in conjunction with various embodiments. One or more embodiments may be applied simultaneously or in combination, rather than independently.

[0560] [NC-JT related]

[0561] According to an embodiment, Non-coherent Joint Transmission (NC-JT) can be used for the UE to receive PDSCH from multiple TRPs.

[0562] Unlike traditional methods, 5G wireless communication systems can support all of the following: services requiring high transmission rates, services with very short transmission latency, and services requiring high connection density. In wireless communication networks that include multiple cells, TRPs, or beams, coordinated transmission between cells, TRPs, and / or beams can increase the signal strength received by the UE or effectively perform interference control between cells, TRPs, and / or beams, thereby meeting various service requirements.

[0563] Joint transmission (JT) is a representative transmission technology for coordinated communication and is a technique that increases the strength or throughput of the signal received by a UE by transmitting signals to a UE through multiple different cells, TRPs, and / or beams. In this case, the inter-cell, TRP, and / or beam-UE channels can have significantly different characteristics. In particular, NC-JT supporting inter-cell, TRP, and / or beam-UE non-interference coding may require separate precoding, MCS, resource allocation, and TCI indication based on the per-link characteristics of the inter-cell, TRP, and / or beam-UE channels.

[0564] The aforementioned NC-JT transmission can be applied to at least one of the channels PDSCH, PDCCH, PUSCH, and PUCCH. During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI is indicated by DL DCI, and for NC-JT transmission, the transmission information should be indicated independently for each cell, TRP, and / or beam. This becomes a major factor increasing the payload required for DL ​​DCI transmission, which may negatively impact the reception performance of the PDCCH transmitting DCI. Therefore, to support JT for PDSCH, a careful trade-off between DCI information volume and control information reception performance needs to be designed.

[0565] Figure 16 An example of antenna port configuration and resource allocation for transmitting PDSCH using cooperative communication in a wireless communication system according to an embodiment is shown.

[0566] Reference Figure 16 Examples of PDSCH transmissions are described for each technology of JT, and examples of allocating radio resources for each TRP are shown.

[0567] Reference Figure 16 Example 1600 shows a coherent JT (C-JT) that supports inter-cell, TRP and / or inter-beam phase interference coding.

[0568] In the C-JT scenario, TRP A 1605 and TRP B 1610 send a single data (e.g., PDSCH) to UE 1615, and joint precoding can be performed across multiple TRPs. This may mean sending DMRS through the same DMRS port, causing TRP A 1605 and TRP B 1610 to send the same PDSCH. For example, TRP A 1605 and TRP B 1610 can send DMRS to the UE through DMRS ports A and B, respectively. In this case, the UE can receive DCI information for receiving a PDSCH to be demodulated based on the DMRS sent through DMRS ports A and B.

[0569] Figure 16 Example 1620 is also shown that supports NC-JT for inter-cell, TRP and / or inter-beam non-phase interference coding for PDSCH transmission.

[0570] In the NC-JT case, for each cell, TRP 1625, 1630, and / or beam, the PDSCH is sent to UE1635 (N035), and individual precoding can be applied to each PDSCH. Because each cell, TRP, and / or beam sends a different PDSCH or a different PDSCH layer to the UE, throughput can be enhanced relative to individual cell, TRP, and / or beam transmissions. Reliability relative to individual cell, TRP, and / or beam transmissions can also be enhanced because each cell, TRP, and / or beam repeatedly sends the same PDSCH to the UE. For ease of description, the cell, TRP, and / or beam are collectively referred to as the TRP.

[0571] In this case, various radio resource allocations can be considered, such as when the frequency and time resources used for PDSCH transmission are the same in multiple TRPs (1640), when the frequency and time resources used in multiple TRPs do not overlap (1645), and when some of the frequency and time resources used in multiple TRPs overlap (1650).

[0572] For NC-JT support, various forms, structures, and relationships of DCI can be considered to simultaneously assign multiple PDSCHs to a UE.

[0573] Figure 17 An example of a configuration for DCI in a wireless communication system according to an embodiment, which transmits different PDSCHs or different PDSCH layers of NC-JT to the UE for each TRP, is shown.

[0574] See Figure 17 Case #1 1700 is an example where (N-1) different PDSCHs are transmitted from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission. In this case, the control information for the PDSCHs transmitted in the (N-1) additional TRPs is transmitted independently from the control information for the PDSCHs transmitted in the serving TRP. In other words, the UE can obtain the control information for PDSCHs transmitted from different TRPs (TRP#0 to TRP#(N-1)) through independent DCIs (DCI#0 to DCI#(N-1)). The formats of the independent DCIs can be the same or different, and the payloads of the DCIs can also be the same or different. Case #1 above can fully guarantee the control or allocation degrees of freedom for each PDSCH; however, if each DCI is transmitted in different TRPs, coverage differences occur for each DCI, degrading reception performance.

[0575] Case #2 1705 is an example of sending DCIs for (N-1) additional TRPs separately, and in the case of sending (N-1) different PDSCHs from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) for a single PDSCH transmission, each DCI depends on the control information of the PDSCH sent from the serving TRP.

[0576] For example, DCI#0, which is the control information for PDSCH sent from the serving TRP (TRP#0), includes all the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, the shortened DCI (hereinafter referred to as sDCI) (sDCI#0 to sDCI#(N-2)) for the control information of PDSCH sent from the cooperating TRPs (TRP#1 to TRP#(N-1)) may only include some of the information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. Therefore, since the sDCI for the control information of PDSCH sent from the cooperating TRP has a smaller payload than the normal DCI (nDCI) for sending PDSCH-related control information from the serving TRP, it can include reserved bits compared to the nDCI.

[0577] In case #2 1705 above, the control or allocation degrees of freedom for each PDSCH can be restricted based on the content of the information elements included in the sDCI. However, since the reception performance of the sDCI is superior to that of the nDCI, the probability of coverage differences occurring for each DCI can be reduced.

[0578] Case #3 1710 is an example of sending a control message for (N-1) additional TRPs, and in the case of sending (N-1) different PDSCHs from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission, the DCI depends on the control message of the PDSCH sent from the serving TRP.

[0579] For example, the control information DCI#0 of PDSCH sent from the serving TRP (TRP#0) includes all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2. However, for the control information of PDSCH sent from the cooperating TRPs (TRP#1 to TRP#(N-1)), only some information elements from DCI format 1_0, DCI format 1_1, and DCI format 1_2 can be collected and sent to an "auxiliary" DCI (sDCI). For example, the sDCI may include at least one of the HARQ-related information, such as frequency domain resource allocation, time domain resource allocation, and the MCS of the cooperating TRP. Furthermore, information not included in the sDCI (such as BWP indicators or carrier indicators) may follow the serving TRP's DCI (DCI#0, normal DCI, and nDCI).

[0580] In Case #3 1710, the control or allocation degrees of freedom for each PDSCH can be restricted based on the content of the information elements included in the sDCI, but the reception performance of the sDCI can be adjusted, and the complexity of blind decoding of the UE's DCI can be reduced compared to Case #1 1700 or Case #2 1705.

[0581] Case #4 (N115) is an example where (N-1) different PDSCHs are sent from (N-1) additional TRPs (TRP#1 to TRP#(N-1)) other than the serving TRP (TRP#0) used for a single PDSCH transmission. The control information for the PDSCHs sent in the (N-1) additional TRPs is transmitted in the same DCI (long DCI) as the control information for the PDSCHs transmitted from the serving TRP. In other words, the UE can obtain the control information for PDSCHs sent from different TRPs (TRP#0 to TRP#(N-1)) through a single DCI. In Case #4 (N115), the complexity of the UE's blind DCI decoding may not increase, but the freedom of PDSCH control or allocation may decrease, similar to the number of cooperating TRPs limited by the long DCI payload limit.

[0582] In this document, sDCI can refer to various auxiliary DCIs, such as shortened DCIs, auxiliary DCIs, or normal DCIs that include PDSCH control information sent in the cooperative TRP (DCI formats 1_0 to 1_1 above), and unless otherwise stated, the corresponding descriptions can also be applied to auxiliary DCIs.

[0583] Cases #1 1700, #2 1705, and #3 1710, where one or more DCIs (PDCCHs) are used to support NC-JT, can be identified as NC-JT based on multiple PDCCHs, and case #4 1715, where a single DCI (e.g., PDCCH) is used to support NC-JT, can be identified as NC-JT based on a single PDCCH. In PDSCH transmission based on multiple PDCCHs, the CORESETs scheduled by the DCI of the serving TRP (TRP#0) and the CORESETs scheduled by the DCIs of the cooperating TRPs (TRP#1 to TRP#(N-1)) can be partitioned. As a method of partitioning CORESETs, there can be methods for partitioning by higher-layer indicators of each CORESET and methods for partitioning by beam configuration of each CORESET. NC-JT based on a single PDCCH can schedule a single PDSCH with multiple layers, rather than scheduling multiple PDSCHs through a single DCI, and can send multiple layers from multiple TRPs. In this case, the connection relationship between the layer and the TRP that sent the layer can be indicated by the TCI indication used for that layer.

[0584] In this article, in practical applications, “cooperative TRP” can be replaced by various terms such as “cooperative panel” or “cooperative beam”.

[0585] Here, "when NC-JT is applied" can be interpreted in various ways depending on the context, such as "when the UE receives one or more PDSCHs simultaneously in a BWP", "when the UE receives PDSCHs simultaneously in a BWP based on two or more TCI indications", or "when the PDSCHs received by the UE are associated with one or more DMRS port groups", but for ease of description, one expression is used.

[0586] The radio protocol architecture used for NC-JT can be used differently depending on the TRP scenario described in this paper. As an example, when there is little or no backhaul delay between cooperative TRPs, it is possible to use an architecture based on MAC layer multiplexing (e.g., a CA-like approach), such as... Figure 15 The attached figure is referenced to S10. However, when the backhaul delay between cooperative TRPs is too large to be ignored (e.g., when exchanging information such as CSI, scheduling, and HARQ-ACK between cooperative TRPs takes 2 ms or longer), it is possible to use an independent structure from each TRP of the RLC layer to ensure robustness (e.g., a DC-like approach), such as... Figure 15 The attached figure is labeled S20.

[0587] UEs supporting C-JT / NC-JT can receive C-JT / NC-JT related parameters or settings in higher-level configurations and set the UE's RRC parameters accordingly. For higher-level configurations, the UE can utilize UE capability parameters, such as tci-StatePDSCH. Here, the UE capability parameter (e.g., tci-StatePDSCH) can define TCI states for PDSCH transmission purposes, and the number of TCI states can be set to 4, 8, 16, 32, 64, or 128 in FR1 and 64 or 128 in FR2. Up to eight states can be set via MAC CE messages, indicated by the 3 bits of the DCI's TCI field. The maximum value of 128 is indicated by the value maxNumberConfiguredTCIstatesPerCC in the tci-StatePDSCH parameter included in the UE's capability signaling. Thus, a series of configuration procedures from higher-level configuration to MAC CE configuration can be applied to beamforming indications or beamforming change commands for at least one PDSCH in a TRP.

[0588] Multi-DCI-based Multi-TRP

[0589] According to an embodiment, the DL control channel for NC-JT transmission can be configured based on multiple PDCCHs.

[0590] When sending DCI for PDSCH scheduling for each TRP, an NC-JT based on multiple PDCCHs can have a CORESET or search space partitioned by TRP. The CORESET or search space for each TRP can be configured as at least one of the following:

[0591] High-level index configuration for each CORESET: The CORESET configuration information through high-level configuration can include index values, and the TRPs that send PDCCHs within the corresponding CORESET can be partitioned using the configured index values ​​for each CORESET. In other words, within a set of CORESETs with the same high-level index value, it can be assumed that the PDCCHs sent by them or the PDSCHs scheduled by the same TRP are sent. The aforementioned index for each CORESET can be referred to as the CORESETPoolIndex, and it can be assumed that for CORESETs with the same CORESETPoolIndex value, the PDCCHs are sent from the same TRP. CORESETs that do not have a CORESETPoolIndex value set can be considered to have a default CORESETPoolIndex value set, and the default value can be 0.

[0592] Multiple PDCCH-Config Configuration: Multiple PDCCH-Configs can be configured in a single BWP, and each PDCCH-Config can include PDCCH configurations for each TRP. In other words, a list of CORESETs and / or a list of search spaces per TRP can be configured in a single PDCCH-Config, and one or more CORESETs and one or more search spaces included in a single PDCCH-Config can be considered to correspond to a specific TRP.

[0593] CORESET Beam / Beamgroup Configuration: The TRP corresponding to the corresponding CORESET can be identified by the beam or beamgroup configured for each CORESET. For example, when the same TCI state is configured in multiple CORESETs, the corresponding CORESET can be considered to be transmitted through the same TRP or can be considered to be transmitted by the PDCCH of the PDSCH of the same TRP scheduled in the corresponding CORESET.

[0594] Search Space Beam / Beamgroup Configuration: Beams or beamgroups can be configured according to search spaces, thereby identifying the TRP used for each search space. For example, when the same beam / beamgroup or TCI state is configured in multiple search spaces, it can be assumed that the same TRP sends PDCCH in the corresponding search space, or that the PDCCH of the PDSCH scheduled for the same TRP is sent in the corresponding search space.

[0595] As described above, by identifying the CORESET or search space of each TRP, the PDSCH and HARQ-ACK information of each TRP can be classified, thereby generating a HARQ-ACK codebook independently for each TRP and using PUCCH resources independently.

[0596] The above configuration can be independent for each cell or for each BWP. For example, two different CORESETPoolIndex values ​​can be set in a PCell, while in a specific SCell, CORESETPoolIndex may not be set. In this case, it can be assumed that although NC-JT transmission is configured in the PCell, NC-JT transmission is not configured in the SCell where CORESETPoolIndex is not configured.

[0597] Multi-TRP based on a single DCI

[0598] According to another embodiment of this disclosure, the DL beam for NC-JT transmission can be configured based on a single PDCCH.

[0599] NC-JT based on a single PDCCH can utilize a DCI to schedule PDSCH transmissions from multiple TRPs. In this case, the number of TCI states can be used as a method to indicate the number of TRPs transmitting the PDSCH. In other words, if the number of TCI states indicated by the DCI scheduling the PDSCH is 2, it can be considered as an NC-JT transmission based on a single PDCCH, and if it is 1, it can be considered as a single TRP transmission. The TCI states indicated by the DCI can correspond to one or two TCI states activated by the MAC-CE. When the TCI states of the DCI correspond to two TCI states activated by the MAC-CE, a correlation can be established between the TCI code points indicated in the DCI and the TCI states activated by the MAC-CE, and this can be when the number of TCI states activated by the MAC-CE corresponding to the TCI code points is 2.

[0600] The above configuration can be independent for each cell or for each BWP. For example, although the maximum number of active TCI states corresponding to a TCI code point in a PCell is two, the maximum number of active TCI states corresponding to a TCI code point in a specific SCell can be one. In this case, it can be considered that although NC-JT transmission is configured in the PCell, NC-JT transmission is not configured in the SCell.

[0601] PHR

[0602] Figure 18 The process of controlling the UE's transmit power via the BS in a cellular system is illustrated.

[0603] Reference Figure 18In step 1810, the UE within the coverage of the BS can perform DL synchronization with the BS and obtain the SI. According to some embodiments, DL synchronization can be performed via a primary SS / secondary SS (PSS / SSS) received from the BS. The UE performing DL synchronization can receive the MIB and SIB from the BS and obtain the SI. In step 1815, the UE can perform UL synchronization with the BS and establish an RRC connection via the RA procedure. During the RA procedure, the UE can send an RA preamble and message 3 (msg3) to the BS via the UL. In this case, the UL TPC can be performed during the transmission of the RA preamble and message 3. Specifically, the UE can receive parameters for the UL TPC from the BS via the obtained SI (e.g., SIB), or can perform the UL TPC using agreed-upon parameters. In another embodiment of this disclosure, the UE can measure the RSRP based on the estimated path loss signal sent by the BS and estimate the DL path loss value, as shown in equation (7) below. Based on the estimated path loss value, the UL transmit power value for the transmission of message 3 and the RA preamble can be set based on the estimated path loss value.

[0604] [Equation 7]

[0605] DL path loss = BS signal transmit power - RSRP measured by UE

[0606] In equation (7), the transmit power of the BS signal indicates the transmit power of the DL estimated path loss signal transmitted by the BS. The DL estimated path loss signal transmitted by the BS can be a cell-specific reference signal (CRS) or an SS block (SSB). When the estimated path loss signal is a cell-specific reference signal (CRS), the transmit power of the BS signal indicates the transmit power of the CRS and can be transmitted to the UE via the reference SignalPower parameter of the SI. When the estimated path loss signal is an SSB, the transmit power of the BS signal indicates the transmit power of the SSS and DMRS transmitted to the PBCH and can be transmitted to the UE via the ss-PBCH-BlockPower parameter of the SI. In step 1820, the UE can receive RRC parameters for UL TPC from the BS via UE-specific RRC or common RRC. In this case, the received TPC parameters can differ from each other depending on the type of UL channel and the type of signal to be transmitted through the UL. In other words, the TPC parameters applied to the transmission of PUCCH, PUSCH, and SRS can differ from each other. As described above, the TPC parameters received by the UE from the BS via the SIB before the RRC connection is established, or the TPC parameters used by the UE as previously agreed values ​​before the RRC connection is established, can be included in the RRC parameters sent from the BS after the RRC connection is established. The UE can use the RRC parameter values ​​received from the BS after establishing an RRC connection for UL TPC. In step 1825, the UE can receive an estimated path loss signal from the BS. More specifically, the BS can configure the CSI-RS as the UE's estimated path loss signal after establishing the UE's RRC connection. In this case, the BS can send information about the transmit power of the CSI-RS to the UE via the powerControlOffsetSS parameter of the UE-specific RRC information. In this case, powerControlOffsetSS can refer to the transmit power difference (offset) between the SSB and the CSI-RS. In step 1830, the UE can estimate the DL path loss value and set the UL transmit power value. More specifically, the UE can use the CSI-RS to measure the DLRSRP and use the information about the transmit power of the CSI-RS received from the BS to estimate the DL path loss value using the above equation (1). Based on the estimated path loss value, the UL transmit power value for PUCCH, PUSCH, and SRS transmissions can be set. In step 1835, the UE can perform a power headroom reporting (PHR) to the BS. The power headroom can refer to the difference between the UE's current transmit power and the UE's maximum output power. In step 1840, the BS can optimize system operation based on the reported power headroom.For example, if a specific UE reports a positive power margin to the BS, the BS can increase system throughput by allocating more resources (RB) to the corresponding UE. In step 1845, the UE can receive a TPC command from the BS. For example, if a specific UE reports a negative power margin to the BS, the BS can reduce the transmit power of the corresponding UE by allocating fewer resources to the UE or by using a TPC command. Therefore, system throughput can be increased or unnecessary power consumption of the UE can be reduced. In step 1850, the UE can update its transmit power based on the TPC command. In this case, the TPC command can be sent to the UE via a UE-specific DCI or a group common DCI. Therefore, the BS can dynamically control the UE's transmit power via the TPC command. In step 1855, the UE can perform UL transmission based on the updated transmit power.

[0607] PUSCH power control

[0608] The PUSCH transmit power can be determined in equation (8) below.

[0609] [Equation 8]

[0610]

[0611] In equation (8), It is the maximum transmit power set for the UE on carrier f of serving cell c during PUSCH transmission time i. It is the reference transmit power setting value of the active UL BWP b based on the carrier f of the serving cell c, and varies depending on the various transmission types j. It can have various values, depending on whether the PUSCH transmission is a message 3 PUSCH for random access, or whether the PUSCH is a configured permitted PUSCH or a scheduled PUSCH. This indicates the frequency size of the PUSCH that has been allocated. The path loss compensation ratio of carrier f of serving cell c is indicated by the ULBWP b of carrier f, and can be set by higher-layer signals or can have different values ​​depending on j. It is the estimated DL path loss value of the UL BWP b of carrier f of serving cell c, which uses the value measured by a reference signal in the activated DL bandwidth portion. The reference signal can be an SS / PBCH block or CSI-RS. The DL path loss can be calculated as described above in equation (7). In another embodiment of this disclosure, This is the DL path loss value, which is the path loss calculated by the UE as shown in equation (7). The UE calculates the path loss based on reference signal resources associated with the SS / PBCH block or CSI-RS, depending on whether higher-layer signals are configured. Reference signal resources can be selected from one of several sets of reference signal resources using higher-layer signals or L1 signals. The UE calculates the path loss based on the reference signal resources. It is a value determined by the modulation and coding scheme (MCS) value of the PUSCH at the PUSCH transmission time i of the UL BWP b of the carrier f of the serving cell c. The power control adapter value can be dynamically adjusted using the TPC command.

[0612] TPC commands are divided into cumulative mode and absolute mode, with one of the two modes determined by a higher-level signal. In cumulative mode, the currently determined power control adaptive value is accumulated to the value indicated by the TPC command, and can be increased or decreased according to the TPC command. The relationship. This is the value indicated in the TPC command. The value for absolute mode is determined by the TPC command, regardless of the currently determined adaptive power regulation value, and has... The relationship. Table 43 below shows the values ​​that can be indicated in the TPC command.

[0613] [Table 43]

[0614]

[0615] PUCCH power control

[0616] The following equation (9) is used to determine the PUCCH transmit power.

[0617] [Equation 9]

[0618]

[0619] In equation (9), This is a reference setting for the transmit power setting, and varies depending on the transmission type. The values ​​can have different values, and these values ​​can be changed via higher-layer signals such as RRC or MAC CE. When the value is changed via MAC CE, if the time slot for sending HARQ-ACK for the PDSCH receiving the MAC CE is k, then the UE determines the value from k+k. offset The time slot applies the corresponding value. This depends on the subcarrier spacing, k. offset It can have different values, and can be, for example, 3ms. It is the size of the frequency resource area allocated to PUCCH. This is the estimated path loss value for the UE, and as described above in equation (7), it depends on whether higher-layer signals are configured and their types, calculated based on specific reference signals in various CSI-RS or SS / PBCH. For retransmitted PUCCH, The same applies to repeated PUCCH transmissions. The same applies.

[0620] [HARQ-ACK: Type 1 (semi-static) codebook related]

[0621] When the number of HARQ-ACK PUCCHs that a UE can send in a time slot is limited to one, if the UE receives a semi-static HARQ-ACK codebook configuration from a higher layer, the UE can report HARQ-ACK information for the SPS PDSCH release or received PDSCH in the HARQ-ACK codebook of the time slot indicated by the value of the PDSCH-to-HARQ_feedback timing indicator in DCI format 0_1 ​​or DCI format 1_1. The UE reports the HARQ-ACK information bit value as NACK in the HARQ-ACK codebook of the time slot not indicated by the PDSCH-to-HARQ_feedback timing indicator field in DCI format 1_0 or DCI format 1_1. If the UE is in the M... A,c In cases where only HARQ-ACK information for receiving a PDSCH or a SPSPDSCH release is reported, and the report is scheduled via DCI format 1_0 including information in which the counter DCI field is indicated as 1 in the Pcell, then the UE determines a HARQ-ACK codebook for the corresponding PDSCH reception or the corresponding SPSPDSCH release.

[0622] Otherwise, follow the HARQ-ACK codebook determination method based on the above method.

[0623] If the set of PDSCH reception candidates is MA,c in the serving cell c, then MA,c can be obtained through the following pseudocode step 1.

[0624] Pseudocode 1 begins

[0625] Step 1: Initialize j to 0, and set M... A,c Initialize to an empty set. Initialize the HARQ-ACK transmission timing index k to 0.

[0626] Step 2: Set R to a set of rows from a table that includes slot information, start symbol information, symbol count, or length information for PDSCH mapping. If the PDSCH potentially mapped symbol indicated by each value of R is set to a UL symbol according to the DL and UL configuration described above, then delete the corresponding row from R.

[0627] Step 3-1: If the UE can receive a PDSCH for unicast in a time slot and R is not an empty set, then set M... A,c Add one.

[0628] Step 3-2: If the UE is able to receive more than one PDSCH for unicast in a time slot, count the PDSCHs in the calculated R that can be assigned to different symbols and add them to M. A,c .

[0629] Step 4: Increase k by 1 and start over from step 2.

[0630] Pseudocode 1 ends

[0631] exist Figure 19 In the example, for pseudocode 1 above, to perform a HARQ-ACK PUCCH transmission in slot #k 1908, consider all slot candidates capable of PDSCH to HARQ-ACK timing that can indicate slot #k 1908. Figure 19 In this context, assuming that HARQ-ACK transmission is possible in time slot #k 1908 via PDSCH-to-HARQ-ACK timing combination, this PDSCH-to-HARQ-ACK timing combination is possible only for PDSCHs scheduled in time slots #n 1902, #n+1 1904, and #n+2 1906. Considering the time-domain resource configuration information for the schedulable PDSCHs in each of time slots 1902, 1904, and 1906, as well as information indicating whether the symbols in the time slots are DL or UL, the maximum number of schedulable PDSCHs per time slot is derived. For example, assuming maximum scheduling is possible for 2 PDSCHs in time slot 1902, 3 PDSCHs in time slot 1904, and 2 PDSCHs in time slot 1906, the maximum total number of PDSCHs included in the HARQ-ACK codebook transmitted in time slot 1908 is 7. This is referred to as the cardinality of the HARQ-ACK codebook.

[0632] In a specific time slot, step 3-2 is described in Table 44 below (default PDSCH time domain resource allocation A for normal CP).

[0633] [Table 44]

[0634]

[0635] Table 44 is the time resource allocation table for the UE's default operation before receiving time resource allocation via a separate RRC signal. For reference, the PDSCH time resource allocation value is determined by dmrs-TypeA-Position, which is the UE's common RRC signal, except for the row index value indicated separately via RRC. In Table 44 above, the end column and sequence column are values ​​added separately for ease of description and may not actually exist. The end column indicates the end symbol of the scheduled PDSCH, and the sequence column indicates the code position value located in a specific codebook within the semi-static HARQ-ACK codebook. Table 44 is applied to the time resource allocation in DCI format 1_0 of the PDCCH common search space.

[0636] The UE performs the following steps to determine the HARQ-ACK codebook by calculating the maximum number of non-overlapping PDSCHs in a specific time slot.

[0637] Step 1: Search for the PDSCH allocation value that ends first within the time slot across all rows of the PDSCH time resource allocation table. In Table 44, row index 14 can be identified as ending first. This is indicated as 1 in the sequence column. Other row indices that overlap with row index 14 by at least one sign are indicated as 1x in the sequence column.

[0638] Step 2: Among the remaining row indices not indicated in the sequence column, search for the first-ending PDSCH assignment value. In Table 44, the row with row index 7 and dmrs-typeA-Position value 3 corresponds to it. Other row indices that overlap with the corresponding row index by at least one sign are indicated as 2x in the sequence column.

[0639] Step 3: While repeating Step 2, add and display the sequence values. For example, among the row indices not indicated in the sequence column of Table 44, search for the first-ending PDSCH assignment value. The row with row index 6 and dmrs-typeA-Position value 3 corresponds to it. Other row indices that overlap with the corresponding row index by at least one sign are indicated as 3x in the sequence column.

[0640] Step 4: This step ends when the order is displayed for all row indices. The size of the corresponding order is the maximum number of PDSCHs that can be scheduled without time overlap in the corresponding time slots. Scheduling without time overlap means scheduling different PDSCHs in TDM.

[0641] In the sequence columns of Table 44, the maximum value of the sequence indicates the HARQ-ACK codebook size of the corresponding time slot, and the sequence value indicates the HARQ-ACK codebook point where the HARQ-ACK feedback bit for the corresponding scheduled PDSCH is located. For example, row index 16 in Table 44 means that it exists at the second code position in a semi-static HARQ-ACK codebook of size 3. If the set of PDSCH reception candidates (the timing of candidate PDSCH reception) in serving cell c is M A,c Then, the UE that sends HARQ-ACK feedback can obtain M through steps [pseudocode 1] or [pseudocode 2]. A,c M A,c This can be used to determine the number of HARQ-ACK bits the UE should send. Specifically, the HARQ-ACK codebook can use M... A,c Configured by the size (cardinality) of the set.

[0642] As another example, considerations for determining a semi-static HARQ-ACK codebook (or a type 1 HARQ-ACK codebook) can be shown in Table 45 below.

[0643] [Table 45]

[0644]

[0645] As another example, the pseudocode used for HARQ-ACK codebook determination can be shown in Table 46 below.

[0646] [Table 46]

[0647]

[0648]

[0649]

[0650]

[0651] The position of the HARQ-ACK codebook containing the HARQ-ACK information for the DCI indicating the release of the DL SPS in pseudocode 2 above is based on the position of the received DL SPS PDSCH. For example, when the start symbol of the transmitted DL SPS PDSCH starts from the fourth OFDM symbol relative to the time slot and its length is five symbols, the HARQ-ACK information for the DL SPS release, including the information indicating the release of the corresponding SPS, is assumed to be mapped from the fourth OFDM symbol of the time slot where the DL SPS release was transmitted, and the corresponding HARQ-ACK information is determined by the PDSCH-to-HARQ-ACK timing indicator and PUSCH resource indicator included in the control information indicating the DL SPS release. As another example, when the starting symbol of the DLSPS PDSCH is transmitted starting from the fourth OFDM symbol relative to the time slot and its length is five symbols, the HARQ-ACK information indicating the release of the corresponding SPS is included. It is assumed that the PDSCH starting from the fourth OFDM symbol of the time slot indicated by the Time Domain Resource Allocation (TDRA) as the DCI for the release of the DLSPS and having a length of five symbols is mapped, and the corresponding HARQ-ACK information is determined by the PDSCH-to-HARQ-ACK timing indicator and the PUSCH resource indicator included in the control information indicating the release of the DLSPS.

[0652] [HARQ-ACK: Type 2 (Dynamic) Codebook Related]

[0653] Based on K0, which serves as the time slot location information for the PDSCH scheduled in DCI format 1_0 or 1_1, and the PDSCH-to-HARQ_feedback timing value for PUCCH transmission of HARQ-ACK information in time slot n for SPS PDSCH release or PDSCH reception, the UE transmits HARQ-ACK information in a PUCCH within time slot n. Specifically, for the aforementioned HARQ-ACK information transmission, the UE determines the HARQ-ACK codebook for the PUCCH transmitted in the time slot determined by K0 and the PDSCH-to-HARQ_feedback timing based on the DAI included in the DCI indicating SPS PDSCH release or PDSCH.

[0654] The DAI consists of a counter DAI and a total DAI. The counter DAI indicates the position of the HARQ-ACK information in the HARQ-ACK codebook corresponding to a PDSCH scheduled in DCI format 1_0 or DCI format 1_1. Specifically, the value of the counter DAI in DCI format 1_0 or 1_1 indicates the accumulated value of SPS PDSCH releases or PDSCH receptions scheduled in a specific cell c by DCI format 1_0 or DCI format 1_1. This accumulated value is set based on the serving cell and the timing of PDCCH monitoring for scheduled DCI.

[0655] Total DAI is a value indicating the size of the HARQ-ACK codebook. Specifically, the total DAI value indicates the total number of previously scheduled PDSCH or SPS PDSCH releases, including the time of scheduling DCIs. Total DAI is a parameter used when the HARQ-ACK information in the serving cell c within the CA context also includes HARQ-ACK information for PDSCHs scheduled in other cells including serving cell c. In other words, the total DAI parameter does not exist in a system operating as a single cell.

[0656] exist Figure 20 An example of operation for DAI is shown in the figure. Figure 20 The changes in the values ​​of the counter DAI (C-DAI) and total DAI (T-DAI) indicated by the DCIs detected by each PDCCH monitoring timing set for each carrier are shown when the UE is configured with two carriers c and transmits a HARQ-ACK codebook based on the DAI selection in the nth time slot of carrier 9 2002 on PUCCH 2020. First, in the DCI detected at m=0 (2006), C-DAI and T-DAI each indicate a value of 1 (2012). In the DCI detected at m=1 (2008), C-DAI and T-DAI each indicate a value of 2 (2014). In the DCI detected for carrier 0 (c=0, 2002) at m=2 (2010), C-DAI indicates a value of 3 (2016). In the DCI detected for carrier 1 (c=1, 2004) with m=2 (2010), the C-DAI indication value is 4 (2018). In this case, if carriers 0 and 1 are scheduled at the same monitoring time, all T-DAIs are indicated as 4.

[0657] exist Figure 19 and Figure 20In this context, the HARQ-ACK codebook determines the operation within a time slot by sending only one PUCCH containing HARQ-ACK information. This is referred to as Mode 1. As an example method for determining a PUCCH transmission resource within a time slot, when PDSCHs scheduled in different DCIs are multiplexed into a single HARQ-ACK codebook and transmitted in the same time slot, the PUCCH resource selected for the HARQ-ACK transmission is determined to be the PUCCH resource indicated by the PUCCH resource field in the DCI that last scheduled the PDSCH. In other words, PUCCH resources indicated by the PUCCH resource field in DCIs scheduled before the aforementioned DCI are ignored.

[0658] In the following description, a HARQ-ACK codebook determination method and device are defined in the context of transmitting two or more PUCCHs containing HARQ-ACK information in a single time slot. This is referred to as Mode 2. A UE can operate only in Mode 1 (transmitting only one HARQ-ACK PUCCH in a single time slot) or only in Mode 2 (transmitting one or more HARQ-ACK PUCCHs in a single time slot). Alternatively, a UE supporting both Mode 1 and Mode 2 can be configured by higher-layer signaling to operate in only one mode, or Mode 1 and Mode 2 can be implicitly determined by DCI format, RNTI, DCI-specific field values, scrambling, etc. For example, a PDSCH scheduled in DCI format A and its associated HARQ-ACK information are based on Mode 1, and a PDSCH scheduled in DCI format B and its associated HARQ-ACK information are based on Mode 2. Whether the aforementioned HARQ-ACK codebook is semi-static or dynamic is determined by the RRC signal.

[0659] paging

[0660] UE paging allows the network to reach UEs in the RRC_IDLE and RRC_INACTIVE states via paging messages, and to notify UEs in the RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states of SI changes, Earthquake and Tsunami Warning System (ETWS) / Commercial Mobile Alert Service (CMAS) instructions. Both paging and short messages are addressed by the Paging (P)-RNTI in the PDCCH, but the former is sent via the Paging Control Channel (PCCH), while the latter is sent directly via the PDCCH.

[0661] In RRC_IDLE, the UE monitors the paging channel for paging initiated by the core network (CN), but in RRC_INACTIVE, it also monitors the paging channel for paging initiated by the RAN. However, the UE does not need to continuously monitor the paging channel. Paging Discrete Receive (DRX) is defined when the UE in RRC_IDLE or RRC_INACTIVE only needs to monitor the paging channel during one paging occurrence (PO) in each DRX cycle. The paging DRX cycle is configured by the network.

[0662] 1. In the case of paging initiated by CN, broadcast the default cycle in SI.

[0663] 2. In the case of paging initiated by CN, the UE can set a specific period through NAS signaling.

[0664] 3. In the case of paging initiated by the RAN, the UE sets specific periods via RRC signaling.

[0665] The UE uses the shortest period among the applicable DRX periods; that is, a UE with RRC_IDLE uses the shortest period among the first two periods mentioned above, and a UE with RRC_INACTIVE uses the shortest period among the three periods. The POs for UEs paging initiated by the CN and RAN are based on the same UE ID, and the two POs overlap. The number of different POs in the DRX period can be configured via SI, and the network can assign the UE to the corresponding PO based on its ID. In the case of RRC_CONNECTED, the UE monitors the paging channel at any PO signaled in the SI for SI change instructions and Common Warning System (PWS) notifications. In the case of BA, the UE with RRC_CONNECTED only monitors the paging channel of an active BWP that has established a common search space.

[0666] - Paging optimization for UEs in CM_IDLE: During UE context release, NG-RAN nodes can provide the AMF with a recommended list of cells and NG-RAN nodes as supplementary information for subsequent paging. The AMF can provide paging attempt information consisting of the paging attempt count and the expected number of paging attempts, and may include the next paging area range. When paging attempt information is included in the paging message, each paged NG-RAN node receives the same information during the paging attempt. The paging attempt count is incremented by 1 when a new paging attempt is made. The next paging area range indicates whether the AMF plans to modify the currently selected paging area in the next paging attempt. If the UE changes its state to CM CONNECTED, the UE resets the paging attempt count.

[0667] - Paging optimization for UEs in RRC_INACTIVE state: In RAN paging, the serving NG-RAN node provides RAN paging area information. The serving NG-RAN node can also provide RAN paging attempt information. Each paged NG-RAN node receives the same RAN paging attempt information when attempting to paging, which includes information such as the paging attempt count, the expected number of paging attempts, and the next paging area range. The paging attempt count is incremented by 1 when a new paging attempt is made. The next paging area range indicates whether the serving NG-RAN node plans to modify the currently selected RAN paging area in the next paging attempt. The paging attempt count is reset when the UE leaves the RRC_INACTIVE state.

[0668] Paging information is scheduled using DCI format 1_0, which includes CRC scrambled with P_RNTI, and transmitted from the BS to the UE. The resources for transmitting paging information can be scheduled using the components in Table 47 below.

[0669] [Table 47]

[0670]

[0671] In Table 47 above, the reserved bit field represents unlicensed frequency bands, but 8 bits are applied to FR2-2, while 6 bits are applied to others. The background for using the reserved bit field is to match DCI format 1_0, which includes CRC scrambling with other RNTIs, and the overall DCI size. Among the components in Table 47, the two-bit Short Message Indicator field is used to identify the type of message sent via DCI format 1_0 with P-RNTI, and includes the contents of Table 48 below.

[0672] [Table 48]

[0673]

[0674] Regarding paging information, according to Table 48, when the corresponding bit field indicates "01" or "11", paging-related scheduling information can be transmitted from the BS to the UE through the corresponding DCI format. When it indicates "10", paging-related scheduling information is not transmitted, and in this case, only the short message information described in Table 49 is transmitted.

[0675] The 8-bit short message field may or may not be sent with the paging information. If sent, it is sent based on the contents of Table 49. Bit 1 is the most significant bit (MSB).

[0676] [Table 49]

[0677]

[0678] Tables 50, 51, and 52 below can be configured as follows.

[0679] Table 50 shows an example of VRB to PRB mapping, Table 51 shows an example of MCS index table 1 for PDSCH, and Table 52 shows an example of the scaling factor for Ninfo for P-RNTI.

[0680] [Table 50]

[0681]

[0682] [Table 51]

[0683]

[0684]

[0685] [Table 52]

[0686]

[0687] Satellite communication architecture description

[0688] The characteristics of satellite communications are described below. Satellites used for communication can be classified according to their orbits into Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Orbit (GEO). Generally, GEO can refer to satellites at an altitude of approximately 36,000 km, MEO to satellites at an altitude of 5,000 to 15,000 km, and LEO to satellites at an altitude of 500 to 1,000 km. Of course, this is not limited to the examples described above. According to embodiments, the orbital period varies depending on each altitude. GEO has an orbital period of approximately 24 hours, MEO has an orbital period of approximately 6 hours, and LEO has an orbital period of approximately 90 to 120 minutes. LEO (below 2,000 km) satellites may have advantages over geostationary orbit (36,000 km) satellites in terms of propagation delay (which can be understood as the time required for a signal to travel from the transmitter to the receiver) and losses at relatively low altitudes.

[0689] Figure 21 The Earth orbit period of a communication satellite, depending on the satellite's altitude or elevation, is shown according to an embodiment.

[0690] Reference Figure 21Assuming UE 2101 communicates with a satellite at an altitude of 1200 km, the distance between the UE and the satellite can vary depending on the elevation angle between them. For example, when the elevation angle between the satellite and UE 2101 is 90 degrees (2112), the distance is 1200 km, but when the elevation angle is 10 degrees (2111 and 2113), the distance is approximately 3135 km. Therefore, in satellite communication, even if the UE is fixed, the distance between the satellite and the UE can vary due to the periodic orbit of satellites, such as low-Earth orbit satellites.

[0691] Generally, satellite communication has a lower received signal strength than terrestrial networks because the distance between the satellite and the UE is significantly greater than that of terrestrial networks. Therefore, if a UE has data to transmit via UL, it can perform UL communication by moving to an environment where satellite communication is better performed (such as a line-of-sight (LOS) environment or a place without obstacles). However, the situation where a UE receives data transmitted from a satellite via DL may not guarantee that it is always in a stable satellite communication environment because it is difficult to determine when DL data is being transmitted / received from the satellite. For example, the UE may be at home in a remote environment, or the UE may be stored in the user's possession. Even in this case, the satellite should be able to transmit data to the UE for DL ​​data transmission. When the UE is in the RRC_IDLE state, paging triggers an RRC state switch to RRC_CONNECTED for DL ​​data transmission / reception, and the UE is aware that DL data is arriving after receiving the paging from the satellite. Therefore, due to the above circumstances, satellite communication may require more reliable paging information transmission. Therefore, in this disclosure, as described above... Figure 22 The following are various methods for repeatedly sending paging messages.

[0692] Figure 22 An example of a method for repeatedly sending UE paging information according to an embodiment is shown. (Refer to...) Figure 22 In step 2201, the BS sends a PDCCH with P-RNTI to the UE. In this case, information related to paging repetition can be provided to the UE via the PDCCH with P-RNTI. In step 2202, the BS can repeatedly send a PDSCH including paging to the UE based on the information indicated in step 2201. The information related to paging repetition is described in detail in the following embodiments.

[0693] Conventionally, to enable a UE to receive paging signals, the UE identifies frequency and time resource synchronization by receiving one or more SSs. Based on the identified time and frequency resources, the UE receives the paging signal sent by the BS. The paging signal includes control information and data information. If the paging information reception determines that the UE has data to receive via DL, the UE switches from the RRC_IDLE state to the RRC_CONNECTED state. In a satellite communication environment, when the UE is in a channel state where it is difficult to meet the control and data information requirements for receiving paging signals, it is possible to consider when SSs can be received and when SSs may not be received at all. When the UE can receive SSs, it can identify frequency and time resource synchronization via SSs and receive independent and reliable alarm (notification) signals in addition to the aforementioned paging signals. Alternatively, when the UE can choose not to receive SSs, it can receive notification signals with a structure similar to or different from SSs. Notification signals may include at least one of control signals, data signals, and SSs. When the UE receives a notification signal, it can be alerted that DL data to be transmitted exists. The alert information can be of the type such as a text message or a pop-up message. Upon receiving an alarm, the UE can move to a location with good channel conditions to perform the expected paging signal reception and then receive DL data. Alternatively, as described below, the alarm signal can be included in a conventional paging signal and transmitted from the BS to the UE.

[0694] In the following embodiments, configuration information and associated DCI (e.g., DCI format 1_0 with P-RNTI) related to repeated paging transmissions can be transmitted from a satellite BS or a terrestrial BS to the UE. As an alternative embodiment, at least some of the configuration information and DCI related to repeated paging transmissions can be provided from a terrestrial BS. The UE can receive the configuration information and associated DCI related to repeated paging transmissions from at least one BS and receive repeated paging from the BS in the satellite. In this disclosure, the BS can be a satellite BS or a terrestrial BS that relays data transmission / reception between the satellite and the UE.

[0695] First Embodiment

[0696] The first embodiment does not allow simultaneous configuration of TRS-related higher-layer signals trs-ResourceSetConfig and paging information repeat transmission configuration related to higher-layer signals paging repeat (or If trs-ResourceSetConfig is set in DCI format 1_0 with P-RNTI, paging duplication is not enabled, and in this case, the PDSCH including paging information scheduled via DCI format 1_0 is sent / received only once. In DCI format 1_0 with P-RNTI, as described below... Figure 23In the embodiments, when paging repetition is set, the PDSCH containing paging information is repeatedly transmitted via the PDSCH scheduled by the corresponding DCI format 1_0, the number of times being transmitted is as many as the number of time slots (or the number of resources in the predetermined unit, such as symbols / subframes / paging frames) indicated by the value of the paging repetition factor field set by the paging repetition. Specifically, some components of the DCI format 1_0 described in Table 47 above can be changed to include the paging repetition factor, as shown in Table 53 below. The example in Table 53 is a method of subtracting the number of bits used in the paging repetition factor from the number of reserved bits. For example, if the paging repetition factor uses 2 bits, the number of reserved bits becomes 4 bits. If the paging repetition factor is set to 2 bits, the value of the paging repetition factor is indicated as 00, 01, 10, or 11, as shown in Table 54 below, and the number of paging repetition transmissions can be applied, such as 00 for one paging transmission, 01 for two repetitions, 10 for four repetitions, 11 for eight repetitions, etc. Table 54 shows that the value indicated by the paging repeat factor can be determined by the value of the higher-layer signal paging repeat setting. As an alternative embodiment, the paging repeat factor can be fixed to 1, 2, 4, or 8, instead of the examples in Table 54. The corresponding method can be applied only in the first embodiment, or can be applied equivalently or similarly to other embodiments.

[0697] [Table 53]

[0698]

[0699] [Table 54]

[0700]

[0701] Second Embodiment

[0702] The second embodiment allows simultaneous configuration of TRS-related higher-layer signals trs-ResourceSetConfig and paging information repeat transmission configuration related to higher-layer signals paging repeat (or Since the TRS availability indicator can use all 6 bits of the licensed band, the reserved bit field can be used in a limited manner or in a field other than the reserved bit field, and at least one or more of the following methods can be considered.

[0703] Method A-1: ​​This is a method in which the sum of the number of bits in the TRS availability indicator field set by the TRS-related higher-layer signal trs-ResourceSetConfig and the number of bits in the paging repeat factor field set by the paging repeat signal related to paging information does not exceed, for example, 6 bits set as reserved bits. For example, if the number of bits in the TRS availability indicator field is set to 4 bits, the number of bits in the paging repeat factor field is set to at most 2 bits. In this case, when the number of bits in the paging repeat factor field is 2 bits, the method described in the first embodiment can be applied. If the sum of the number of bits in the TRS availability indicator field set by the TRS-related higher-layer signal trs-ResourceSetConfig and the number of bits in the paging repeat factor field set by the paging repeat signal related to paging information exceeds 6 bits, the UE may consider this an error condition, or may prioritize either the TRS availability indicator field or the paging repeat factor field. Prioritizing the TRS availability indicator field can mean, for example, that when the number of bits in the TRS availability indicator field set by the TRS-related higher-layer signal trs-ResourceSetConfig is set to 4, and the number of bits in the paging repeat factor field set by the paging repeat signal related to paging information is set to 3, the UE can assume that the number of bits in the TRS availability indicator field is 4 and determine that the number of bits in the paging repeat factor field is actually 2. In other words, the number of bits in the paging repeat factor field can be determined such that the sum of the number of bits in the TRS availability indicator field and the number of bits in the paging repeat factor field set by the paging repeat signal related to paging information does not exceed the reserved number of bits. In this case, the number of bits in the TRS availability indicator field can be determined first, or the number of bits in the paging repeat factor field can be determined first within the range of the total number of bits. For example, the number of bits in the paging repeat factor field is set to 3, but in practice, only the first two bits (or the last two bits) are used to determine the paging repeat factor. The Prioritized Paging Repeat Factor field can mean, for example, that when the number of bits in the TRS Availability Indicator field, set by the TRS-related higher-layer signal trs-ResourceSetConfig, is set to 4, and the number of bits in the Paging Repeat Factor field, set by the paging repeat signal, is set to 3, the UE can assume that the number of bits in the TRS Availability Indicator field is actually 3 and determine that the number of bits in the Paging Repeat Factor field is 3. In this case, the number of bits in the TRS Availability Indicator field is set to 4, but in reality, the first three bits (or the last three bits) are used to determine the TRS(group) resource information. When the number of bits in the TRS Availability Indicator field is 4, four different TRS(group) resources can be configured, and four bits can be used to indicate whether each is applied.When using fewer than four bits, the TRS (group) resource corresponding to the deactivation bit can be determined to be always used (or scheduled) or not used.

[0704] Method A-2: This method uses the MCS field in DCI format 1_0 with P-RNTI, excluding the reserved bit field, to provide the paging repeat factor. For example, in the 5-bit MCS field, only 3 bits indicate the MCS index corresponding to the first MCS 0 to 7, and the remaining 2 bits are used to apply the paging repeat factor as shown in Table 54 above. As another example, in the 5-bit MCS field, only 4 bits indicate the MCS index corresponding to the first MCS 0 to 7, and the remaining 1 bit is used to apply the paging repeat factor in a manner similar to that in Table 54. For example, when the paging repeat factor is "0", no paging repeat is performed, and when the paging repeat factor is "1", a predetermined number of paging repeats can be performed. As another example, when the paging repeat factor is "0", a predetermined first number of paging repeats can be performed, and if the paging repeat factor is "1", a predetermined second number of paging repeats can be performed.

[0705] Method A-3: This method uses another TDRA field in DCI format 1_0 with P-RNTI, in addition to the reserved bit field, to provide the paging repeat factor. For example, in addition to providing the time resource of PDSCH for transmitting / receiving paging information via the regular DCI format 1_0 with P-RNTI through the TDRA field, a repeat factor value to be applied to each line index can also be provided. For example, conventionally, as shown in Table 55 below, the specific line index indicated by the TDRA value together indicates "dmrs-TypeA-Position" which means DMRS symbol position information, "PDSCH mapping type" which indicates the PDSCH mapping type, "K0" which is the offset between the time slot where the PDSCH is scheduled and the time slot where the PDCCH indicating the corresponding PDSCH information is transmitted / received, the start symbol of the PDSCH time resource "S", and the length of the PDSCH time resource "L". When providing higher-layer signaled paging repeat configuration information related to paging information, the same value can be applied to each line index, or different values ​​can be applied separately. As shown in Table 55, in addition to receiving regular values, UEs supporting this can also receive a "repetition factor" for repeated transmission values ​​of the PDSCH including paging information, and determine whether to repeatedly transmit PDSCH resources including paging information and the quantity thereof. In this case, repeated transmission is slot-level repeated transmission. In other words, the start symbol and length of the PDSCH are the same for each repeated transmission slot. Table 55 is a modification of the example in Table 44 above according to the embodiment to include a "repetition factor" containing repeated transmission values ​​of the PDSCH. The example values ​​("a" to "j") of the "repetition factor" in Table 55 are examples and can indicate various values ​​(or indices corresponding to the values) based on higher-layer signals (configuration information) associated with repeated transmission of paging information.

[0706] [Table 55]

[0707]

[0708] Method A-4: This method uses another TDRA field in DCI format 1_0 with P-RNTI, in addition to the reserved bit field, to provide the paging repeat factor. This differs from Method A-3 in that, for the traditionally four-bit TDRA field, only three or two bits are used, with the remaining one or two bits used to provide the paging repeat factor. Because the TDRA field is reduced from the traditional four bits to two or three bits, the range of row indices that can be indicated is reduced, thus requiring the definition of which row index value to indicate. Simply put, when the TDRA field has two bits, it can indicate row indices 1 through 4, and when the TDRA field has three bits, it can indicate row indices 1 through 8. Alternatively, Table 55 can be reconfigured by first selecting the row index with the largest L value.

[0709] Method A-5: This method uses an additional TB scaling field in DCI format 1_0 with P-RNTI, besides the reserved bit field, to provide the paging repetition factor. As shown in Table 52 above, the existing TB scaling field "11" is currently unused, so the corresponding value can be used to indicate the repetition factor. For example, if the TB scaling field indicates "11", it can be determined that the PDSCH containing paging information with a value setting the higher-layer signal repetition factor is being repeatedly transmitted / received.

[0710] Method A-6: This is a method of providing the paging repetition factor using another short message field in DCI format 1_0 with P-RNTI, in addition to the reserved bit field. As shown in Table 49 above, since four bits (bits 5 through 8) of the existing short message field are currently unused, the corresponding values ​​can be used to indicate the repetition factor. For example, two bits can be used to indicate four repetition factors. In this case, the fifth and sixth bits, or the seventh and eighth bits, can be used. The number of repeated transmissions set by the higher-layer signal repetition factor can be considered to determine the bit values, and the bit values ​​can be set and indicated as described in the first embodiment.

[0711] Figure 23 This is a flowchart illustrating the process of receiving repeated PUSCH transmissions including paging information according to an embodiment. Figure 23 In the example, assume the UE receives DL data including paging information from a satellite. Figure 23 In the example, the BS can be a satellite BS or a terrestrial BS. As an alternative embodiment, at least some or all of the repetitive transmission-related configuration information and the DCI for paging information can be provided to the UE from the terrestrial BS, and UE capability information related to repetitive paging transmission can be sent to the satellite BS or the terrestrial BS. The satellite BS and the terrestrial BS can also cooperate to repetitive paging transmissions to the UE.

[0712] Reference Figure 23 In step 2301, when at least one of the methods proposed in the first to second embodiments is supported, the UE reports the corresponding UE capability information to the BS. The UE capability information can be sent by the UE to a satellite BS or a ground BS. Operation 2301 can be performed selectively. Subsequently, in step 2302, the UE receives higher-layer signal configuration information related to the repeated transmission of paging information from the BS. Figure 23 The example shows that step 2302 is performed after step 2301, but the order of operations in this disclosure is not limited to this. Step 2302 can be performed first, and step 2301 can be performed afterward.

[0713] In step 2303, if the UE receives DCI format 1_0 with P-RNTI from the BS and determines, for example, that the DCI format contains paging information via a short message indicator, the UE determines the number of PDSCH retransmissions containing paging information using at least one or a combination of the methods described in the first and second embodiments. That is, the base station indicates whether to retransmit downlink data including paging information via downlink control information. In step 2304, the UE receives DL data from the BS in the PDSCH resource area indicated by the control information and detects paging information. Therefore, the UE can determine whether its UE information is included or whether there is information to be received by the UE.

[0714] Figure 24 The structure of a UE in a wireless / satellite communication system according to an embodiment is shown.

[0715] Reference Figure 24 The UE may include a transceiver comprising a UE receiver 2400 and a UE transmitter 2410, a memory (not shown), and a UE processing unit 2405 (or a UE controller or processor). Depending on the UE's... Figures 1 to 23 The transceiver 2400 and 2410, memory, and UE processor 2405 of the UE can operate in at least one of the communication methods described herein. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. The transceiver, memory, and processor may be implemented as a single chip.

[0716] A transceiver can send signals to or receive signals from a BS. These signals may include control information and data. For this purpose, a transceiver may include a radio frequency (RF) transmitter for up-converting and amplifying the transmitted signals, and an RF receiver for low-noise amplification of the received signals and down-converting the frequency of the received signals. However, this is merely an example of a transceiver, and the components of a transceiver are not limited to RF transmitters and RF receivers.

[0717] The transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0718] The memory can store the programs and data required for the operation of the UE. The memory can store control information or data included in signals sent / received by the UE. The memory can include storage media such as read-only memory (ROM), random access memory (RAM), hard disk, optical disc (CD)-ROM, and digital versatile optical disc (DVD), or combinations of storage media. Multiple memories can be provided.

[0719] The processor can control a series of processes, allowing the UE to... Figures 1 to 23 At least one of the embodiments can be used for operation. For example, the processor can control the UE operation of receiving DCI and retransmission-related configuration information about paging information from the BS in the satellite communication system, and receiving retransmitted paging information based on the configuration information and DCI. Multiple processors may exist. The processor can perform control operations on the components of the UE by executing programs stored in memory.

[0720] Figure 25 The structure of a BS in a wireless / satellite communication system according to an embodiment is shown. Figure 25 The BS can be a satellite BS or a terrestrial BS. The BS can be a terrestrial BS that receives data from a satellite and relays it to the UE.

[0721] Reference Figure 25 The BS may include a transceiver comprising a BS receiver 2500 and a BS transmitter 2510, a memory (not shown), and a BS processing unit 2505 (or a BS controller or processor). According to the above-described BS... Figures 1 to 23 The communication method described herein allows the operation of the BS transceivers 2500 and 2510, memory, and BS processor 2505. However, the components of the BS are not limited to these. For example, the BS may include more or fewer components than those described above. The transceivers, memory, and processor may be implemented as a single chip.

[0722] A transceiver can send signals to or receive signals from a UE. These signals may include control information and data. For this purpose, a transceiver may include an RF transmitter for up-converting and amplifying the transmitted signals, and an RF receiver for low-noise amplification of the received signals and down-converting the frequency of the received signals. However, this is merely an example of a transceiver, and the components of a transceiver are not limited to RF transmitters and RF receivers.

[0723] The transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0724] The memory can store the programs and data required for the operation of the BS / satellite. The memory can store control information or data included in signals transmitted / received by the BS / satellite. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Multiple memories may be provided.

[0725] The processor can control a series of processes by which the BS operates according to the above embodiments. For example, the processor can control the DCI (Distributed Communication Interface) for sending paging information from the BS in the satellite communication system to the UE, and the operation of repeatedly transmitting paging information to the UE based on the configuration information and DCI. Each component of the BS can be controlled. Multiple processors can exist. The processor can perform control operations on the components of the BS by executing programs stored in memory.

[0726] The methods described in the embodiments of this disclosure or in the claims can be implemented in hardware, software, or a combination of hardware and software.

[0727] When implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium are configured to be executed by one or more processors in an electronic device. The one or more programs include instructions that enable the electronic device to perform methods according to embodiments described in the specification or claims of this disclosure.

[0728] The program (software module or software) can be stored in RAM memory, non-volatile memory including flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM, DVD, or other types of optical storage devices or magnetic tape cartridges. The program can be stored in a memory consisting of all or some of these components. Multiple components of the memory may be included.

[0729] The program can be stored in an attachable storage device accessible via a communication network, such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or a combination thereof. The storage device can be connected to a device executing embodiments of this disclosure via an external port. A separate storage device on the communication network can be connected to a device executing embodiments of this disclosure.

[0730] As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.

[0731] The embodiments described herein can be combined in practice. For example, the BS and UE can operate in a combination of portions of one embodiment and another. For example, some of the first and second embodiments of this disclosure can be partially combined and operated by the BS and UE. Although the above embodiments are proposed based on FDD LTE systems, other modifications based on the technical spirit of the above embodiments can be implemented in other systems such as TDD LTE systems or 5G or NR systems.

[0732] Although this disclosure has been described with reference to various embodiments, various changes may be made without departing from the spirit and scope of this disclosure, which is not limited by the detailed description and embodiments, but by the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE) in a satellite communication system, the method comprising: Receive first configuration information related to repeated transmissions of paging information from the network; Based on the first configuration information, downlink control information indicating repeated transmissions of paging information and the number of repeated transmissions is received from the network; as well as Based on DCI, it receives paging information from the network that is repeatedly transmitted in a number of repetitive transmissions.

2. The method according to claim 1, wherein, The network includes at least one of satellite base stations and ground base stations.

3. The method according to claim 1, further comprising: Send UE capability information to the network indicating whether repeated transmission of paging information is supported.

4. The method according to claim 1, wherein, The first configuration information and the second configuration information related to the tracking reference signal are configured simultaneously for the UE.

5. The method according to claim 1, wherein, DCI includes a paging repeat field in a defined DCI format using the Paging Radio Network Temporary Identifier (P-RNTI). The paging repeat field is allocated using at least some reserved bits in the DCI format, and The number of paging duplicates corresponds to the value of the paging duplicate field among the multiple duplicates that can be indicated in the first configuration information.

6. The method according to claim 1, wherein, The first configuration information and the second configuration information related to the Tracking Reference Signal (TRS) are configurable simultaneously for the UE. The DCI includes the paging repeat field in the defined DCI format using P-RNTI. The defined DCI format includes TRS-related fields indicating TRS availability, and The number of bits in the paging repeat field is determined such that the sum of the number of bits in the paging repeat field and the number of bits in the TRS related field is less than or equal to the number of reserved bits.

7. The method according to claim 1, wherein, DCI includes a paging repeat field in a defined DCI format using a Paging Radio Network Temporary Identifier (P-RNTI), and The paging repeat field is a bit allocation using either the modulation and coding scheme field in the defined DCI format or the time-domain resource assignment field in the defined DCI.

8. A user equipment (UE) in a satellite communication system, the UE comprising: transceiver; and At least one processor is configured as follows: First configuration information related to repeated transmissions of paging information received from the network. Based on the first configuration information, downlink control information (DCI) indicating the repetition and number of paging information transmissions is received from the network, and... Based on DCI, it receives paging information from the network that is repeatedly transmitted in a number of repetitive transmissions.

9. The UE according to claim 8, wherein, The network includes at least one of satellite base stations and ground base stations.

10. The UE according to claim 8, wherein, The processor is also configured as follows: Send UE capability information to the network related to whether or not paging information retransmission is supported.

11. The UE according to claim 8, wherein, The first configuration information and the second configuration information related to the tracking reference signal are configured simultaneously for the UE.

12. A method performed by a base station in a satellite communication system, the method comprising: Send first configuration information related to the repeated transmission of paging information to the user equipment (UE); Based on the first configuration information, downlink control information (DCI) is sent to the UE indicating the repeated transmission of paging information and the number of repeated transmissions. as well as Based on DCI, paging information is repeatedly sent to the UE in the number of repeated transmissions.

13. The method of claim 12, further comprising: The UE receives UE capability information indicating whether it supports repeated transmission of paging information. The base station includes at least one of satellite base stations and ground base stations.

14. A base station (BS) in a satellite communication system, the BS comprising: transceiver; and At least one processor is configured as follows: Send first configuration information related to the repeated transmission of paging information to the user equipment (UE). Based on the first configuration information, downlink control information (DCI) indicating the retransmission of paging information and the number of retransmissions is sent to the UE, and Based on DCI, paging information is repeatedly sent to the UE in the number of repeated transmissions.

15. The BS according to claim 14, wherein, The processor is also configured as follows: The UE receives UE capability information indicating whether it supports repeated transmission of paging information. The base station includes at least one of satellite base stations and ground base stations.

Images