Method and apparatus for allocating frequency resources in a wireless communication system
By identifying and configuring the types of protection bands and resource block sets, the problem of inflexible frequency resource allocation in wireless communication systems is solved, improving spectrum efficiency and network performance, and meeting the high data rate and low latency requirements of 6G communication systems.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SAMSUNG ELECTRONICS CO LTD
- Filing Date
- 2021-05-04
- Publication Date
- 2026-08-04
AI Technical Summary
Existing wireless communication systems have difficulty in effectively configuring and allocating uplink or downlink frequency resources, resulting in inflexible channel allocation and an inability to meet the high data rate and low latency requirements of 6G communication systems.
By identifying and configuring the types of protection bands and resource block sets, and combining frequency domain and time domain scheduling, the type of resource block set can be dynamically determined as downlink, uplink, or flexible resource block set, thereby achieving flexible allocation of frequency resources.
It enables flexible scheduling of frequency resources, improves the spectrum efficiency and network performance of wireless communication systems, and meets the requirements of 6G communication systems for high data rates and low latency.
Smart Images

Figure CN116018865B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a method and apparatus for configuring frequency resources for uplink or downlink transmission and reception in a wireless communication system. Background Technology
[0002] Given the successive generations of wireless communication development, these technologies have primarily been developed for human-oriented services such as voice calls, multimedia services, and data services. With the commercialization of 5G (fifth-generation) communication systems, the number of connected devices is expected to grow exponentially. These will increasingly connect to communication networks. Examples of the Internet of Things (IoT) might include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve in various forms, such as augmented reality glasses, virtual reality headsets, and holographic devices. To deliver a wide range of services by connecting hundreds of billions of devices and things in the 6G (sixth-generation) era, efforts have been underway to develop improved 6G communication systems. For these reasons, 6G communication systems are referred to as "beyond 5G" systems.
[0003] The 6G communication system, which is expected to be commercialized around 2030, will have peak data rates in the terabit (1,000 gigabits) range and radio latency of less than 100 microseconds (μsec), making it 50 times faster than 5G communication systems and having 1 / 10 of their radio latency.
[0004] To achieve such high data rates and ultra-low latency, 6G communication systems have been considered for implementation in the terahertz band (e.g., the 95 GHz to 3 THz band). It is anticipated that, due to the more severe path loss and atmospheric absorption in the terahertz band compared to the millimeter-wave bands introduced in 5G, technologies capable of ensuring signal transmission distance (i.e., coverage) will become even more critical. It is necessary to develop radio frequency (RF) components, antennas, novel waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive MIMO as key technologies for ensuring coverage. Furthermore, new technologies for improving terahertz band signal coverage have been discussed, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS).
[0005] Furthermore, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology enabling uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies that comprehensively utilize satellites, high-altitude platform stations (HAPS), etc.; improved network architectures to support mobile base stations, enabling network operation optimization and automation; dynamic spectrum sharing technology based on spectrum usage prediction to avoid conflicts; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by leveraging AI from the 6G development design phase and internalizing end-to-end AI support; and next-generation distributed computing technologies to overcome UE computing power limitations through ultra-high-performance communication and computing resources accessible on the network (such as mobile edge computing (MEC), cloud, etc.). In addition, efforts are continuing to enhance connectivity between devices, optimize networks, promote the software-defined networking of network entities, and increase the openness of wireless communication by designing new protocols to be used in 6G communication systems, developing mechanisms for achieving hardware-based secure environments and secure data usage, and developing technologies to maintain privacy.
[0006] The research and development of 6G communication systems in hyper-connectivity, including human-to-machine (P2M) and machine-to-machine (M2M) communication, is expected to bring the next hyper-connected experience. Specifically, services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas are anticipated to be provided through 6G communication systems. Furthermore, services such as remote surgery for enhanced security and reliability, industrial automation, and emergency response will be offered via 6G communication systems, enabling the technology to be applied to various fields such as industry, healthcare, automotive, and home appliances.
[0007] As mobile communication systems, as described above, are able to provide a variety of services, and wireless communication networks become more complex and diverse, there is a need for methods to allocate data channels more efficiently for downlink and uplink. Summary of the Invention
[0008] Technical issues
[0009] This disclosure provides a method and apparatus for efficiently configuring and allocating frequency resources for uplink or downlink transmission and reception in a wireless communication system.
[0010] This disclosure provides a method and apparatus for flexibly scheduling uplink and downlink transmission and reception in the frequency and time domains.
[0011] Technical solutions
[0012] According to embodiments of this disclosure, a method for configuring frequency domain resources for uplink transmission or downlink reception in a wireless communication system by a UE may include: identifying a guard band configured in the bandwidth of a cell or a bandwidth portion configured in the UE; identifying one or more resource block sets in a resource area other than the guard band in the bandwidth or bandwidth portion; and identifying whether configuration information regarding the type of the resource block set has been received. When configuration information is received, the type of each resource block set can be determined based on the configuration information as a downlink resource block set, an uplink resource block set, or a flexible resource block set. When no configuration information is received, the type of each resource block set can be determined based on whether the bandwidth or bandwidth portion is used for uplink transmission or downlink reception.
[0013] According to embodiments of this disclosure, a method for configuring frequency domain resources for uplink reception or downlink transmission by a base station in a wireless communication system may include: configuring a cell bandwidth or a guard band in a bandwidth portion configured in the UE; configuring one or more resource block sets in a resource area other than the guard band in the bandwidth or bandwidth portion for the UE; and providing the UE with configuration information about the type of the resource block sets. The configuration information may include information for determining whether each resource block set is a downlink resource block set, an uplink resource block set, or a flexible resource block set.
[0014] According to embodiments of this disclosure, a UE configured with frequency domain resources for uplink transmission or downlink reception in a wireless communication system may include a communication unit and a controller. The controller may be configured to identify a guard band configured in the bandwidth of a cell or a bandwidth portion configured in the UE, identify one or more resource block sets in a resource area outside the guard band within the bandwidth or bandwidth portion, and identify whether configuration information regarding the type of the resource block set has been received. When the configuration information is received through the communication unit, the controller determines, based on the configuration information, whether the type of each resource block set is a downlink resource block set, an uplink resource block set, or a flexible resource block set. And when the configuration information is not received, the controller determines, based on whether the bandwidth or bandwidth portion is used for uplink transmission or downlink reception, whether the type of each resource block is a downlink resource block set, an uplink resource block set, or a flexible resource block set.
[0015] According to embodiments of this disclosure, a base station configured with frequency domain resources for uplink reception or downlink transmission in a wireless communication system may include a communication unit and a controller. The controller may be configured to configure the bandwidth of a cell for a UE or a guard band within a bandwidth portion configured in the UE, configure one or more sets of resource blocks in a bandwidth or a resource area within a bandwidth portion other than the guard band for the UE, and provide the UE with configuration information regarding the type of the resource block sets. The configuration information may include information for determining whether each resource block set is a downlink resource block set, an uplink resource block set, or a flexible resource block set. Attached Figure Description
[0016] Figure 1 This is a view illustrating a wireless communication system according to an embodiment of the present disclosure;
[0017] Figure 2 This is a view illustrating the configuration of a base station in a wireless communication system according to an embodiment of the present disclosure;
[0018] Figure 3 This is a view illustrating the configuration of a UE in a wireless communication system according to an embodiment of the present disclosure;
[0019] Figure 4 This is a view illustrating the configuration of communication units in a wireless communication system according to an embodiment of the present disclosure;
[0020] Figure 5 This is a view showing the frame, subframe, and time slot structure of a 5G communication system;
[0021] Figure 6 This is a view showing the basic structure of a 5G communication system in the time-frequency domain;
[0022] Figure 7 This is a view showing the bandwidth portion of a 5G communication system;
[0023] Figure 8 This is a view showing an example of the control resource set configuration for the downlink control channel of a 5G communication system;
[0024] Figure 9 This is a view showing the structure of the downlink control channel in a 5G communication system;
[0025] Figure 10 This is a view illustrating an example of an uplink-downlink configuration in the time domain of a 5G communication system;
[0026] Figure 11 This is a view illustrating an example of uplink-downlink configuration in the frequency domain of a 5G communication system;
[0027] Figure 12A and Figure 12B This is a view illustrating an example configuration of guard bands and resource block sets in a wireless communication system according to embodiments of the present disclosure;
[0028] Figures 13A-13C This is a view illustrating an example configuration of a frequency domain resource block set for a downlink bandwidth portion in a wireless communication system according to an embodiment of the present disclosure;
[0029] Figures 14A-14D This is a view illustrating an example configuration of a frequency domain resource block set for an uplink bandwidth portion in a wireless communication system according to an embodiment of the present disclosure;
[0030] Figure 15 This is a view illustrating an example configuration of a frequency domain resource block set for a flexible bandwidth portion in a wireless communication system according to an embodiment of the present disclosure;
[0031] Figure 16 This is a view illustrating examples of time-domain uplink and downlink configurations and frequency-domain resource block set configurations in a wireless communication system according to embodiments of the present disclosure;
[0032] Figure 17 This is a flowchart illustrating the frequency domain resources configured by the UE for uplink transmission or downlink reception in a wireless communication system; and
[0033] Figure 18 This is a flowchart illustrating the frequency domain resources configured by the base station for uplink reception or downlink transmission in a wireless communication system. Detailed Implementation
[0034] In the following description, embodiments of the present disclosure are illustrated with reference to the accompanying drawings.
[0035] In describing this disclosure, descriptions of techniques known in the art and not directly related to the present invention have been omitted. This is to further clarify the essential points of the disclosure without making them unclear. The terminology used herein is defined with regard to its functionality and may be replaced with other terms depending on the intent or practice of the user or operator. Therefore, these terms should be defined based on the entire disclosure.
[0036] For the same reason, some elements may be exaggerated or shown schematically. The size of each element does not necessarily reflect its true size. In all figures, the same reference numerals are used to refer to the same elements.
[0037] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, can be understood from the embodiments described below in conjunction with the accompanying drawings. However, the invention is not limited to the embodiments disclosed herein, and various modifications can be made thereto. The embodiments disclosed herein are provided only to inform those skilled in the art of the scope of this disclosure. The invention is defined only by the appended claims. Throughout the specification, the same reference numerals denote the same elements. Detailed descriptions of known techniques or functions may be omitted when it is determined that the subject matter of the invention is unclear. The terminology used herein is defined in consideration of the functions in this disclosure and may be replaced with other terms depending on the intent or practice of the user or operator. Therefore, these terms should be defined based on the entire disclosure.
[0038] In the following description, a base station (BS) is an entity that performs resource allocation for a UE and can be at least one of a gNode B, eNode B, Node B (or xNode B (where x is a letter character including g and e)), radio access unit, base station controller, satellite, aircraft, or node on a network. A user equipment (UE) can include a mobile station (MS) capable of performing communication functions, a vehicle, satellite, aircraft, cellular phone, smartphone, computer, or multimedia system. In this disclosure, a downlink (DL) refers to a radio transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) refers to a radio transmission path of a signal transmitted from a terminal to a base station. Furthermore, sidelinks (SL) may exist representing radio transmission paths of signals transmitted from one UE to another.
[0039] While LTE, LTE-A, or 5G systems may be described below as examples, embodiments can be applied to other communication systems with similar technical backgrounds or channel modes. For example, embodiments of this disclosure can also be applied to 5G Advanced or NR Advanced or to sixth-generation mobile communication technologies (6G) developed after 5G mobile communication technology (or New Radio, NR). The next 5G may be a concept encompassing legacy LTE, LTE-A, and other similar services. Furthermore, it will be clear to those skilled in the art that embodiments can be modified without explicitly departing from the scope of the invention, and such modifications can be applied to other communication systems.
[0040] It should be understood that each block in a flowchart, and combinations of flowcharts, 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 apparatus, the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce means for performing the functions described in the combination of each flowchart(s). Since computer program instructions can be stored in a computer-usable or computer-readable memory that can be functionally implemented in a particular manner for the computer or other programmable data processing apparatus, the instructions stored in the computer-usable or computer-readable memory can produce an article comprising instruction means for performing the functions described in the combination of each flowchart(s). Since computer program instructions can be located in a computer or other programmable data processing apparatus, when a series of operational steps are performed on the computer or other programmable data processing apparatus, the instructions that generate the process executed by the computer and operate the computer or other programmable data processing apparatus can provide steps for performing the functions described in the combination of each flowchart(s).
[0041] Furthermore, each box can represent a module, code segment, or code section that includes one or more executable instructions for performing a specific logical function. It should also be noted that in some alternative execution examples, the functions mentioned in the boxes may appear in different orders. For example, depending on the corresponding function, two boxes shown consecutively may be executed substantially simultaneously or in reverse order.
[0042] As used herein, the term "cell" means a software element or hardware element, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). A cell plays a specific role. However, the term "cell" is not limited to referring to a software or hardware element. A "cell" may be configured in an addressable storage medium or may be configured to reproduce one or more processors. Thus, by way of example, a "cell" includes elements such as software elements, object-oriented software elements, class elements and task elements, procedures, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in an element or "cell" may be combined with additional elements or may be divided into sub-elements or sub-cells. Furthermore, an element or "cell" may be implemented as one or more CPUs in a reproduction device or secure multimedia card. According to embodiments, "...cell" may include one or more processors.
[0043] Wireless communication systems have evolved from voice-centric services to broadband wireless communication systems (such as 3GPP High-Speed Packet Access (HSPA), LTE or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-A Advanced, LTE-pro, 3GPP2 High-Speed Packet Data (HRPD), Ultra Mobile Broadband (UMB), and the IEEE 802.16e communication standard) to provide high data rates and high-quality packet data services.
[0044] As a representative example of this type of broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink. The uplink refers to the radio link through which the UE transmits data or control signals to the base station, and the downlink refers to the radio link through which the base station transmits data or control signals to the UE. This multiple access scheme typically allocates and operates time-frequency resources carrying data or control information for each user without overlap, i.e., maintaining orthogonality, thereby distinguishing the data or control information for each user.
[0045] The requirements for LTE communication systems (e.g., 5G communication systems) are to freely reflect the diverse needs of users and service providers, thereby supporting services that simultaneously meet various requirements. Services considered for 5G communication systems include, for example, enhanced mobile broadband (eMBB), massive machine-type communications (MMTC), and ultra-reliable low-latency communications (URLLC).
[0046] Compared to LTE, LTE-A, or LTE-pro, eMBB aims to provide further enhanced data transmission rates. For example, for a single base station, eMBB for a 5G communication system needs to provide a peak data rate of 20Gbps during download and 10Gbps during uplink. 5G communication systems also need to provide increased user-perceived data rates while delivering these peak data rates. To meet these requirements, various transmit (TX) / receive (RX) technologies and multiple-input multiple-output (MIMO) are needed to further enhance these capabilities. While LTE uses a maximum TX bandwidth of 20MHz in the 2GHz band to transmit signals, 5G communication systems employ wider frequency bandwidths in the 3GHz to 6GHz or higher bands to meet the data rates required by 5G communication systems.
[0047] mMTC is also considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To effectively deliver IoT, mMTC needs to support a large number of UEs in a cell, enhance UE coverage and battery life, and reduce UE costs. IoT terminals connect to various sensors or devices to provide communication functions; therefore, it needs to support multiple UEs per cell (e.g., 1,000,000 UEs / km). 2 Since UEs supporting mMTC are likely to be located in shadow areas not covered by the cell, such as underground in buildings, depending on the nature of the service, they may require wider coverage compared to other services provided by 5G communication systems. Due to the need for low cost and the difficulty of frequent battery replacements, UEs supporting mMTC may need to have very long battery life, such as 10 to 15 years.
[0048] URLLC is a cellular-based mission-critical wireless communication service. For example, URLLC can be considered for remote control of robots or machines, 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 lower packet error rates. Therefore, for services supporting URLLC, 5G communication systems may need to provide shorter transmission time intervals (TTIs) than other services, while ensuring reliable communication links by allocating extensive resources in the frequency band.
[0049] Three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this scenario, different TX / RX schemes and parameters can be used to meet their varying needs. Of course, 5G is not limited to these three services.
[0050] Figure 1 This is a view illustrating a wireless communication system according to an embodiment of the present disclosure. Figure 1 Base station 110, UE 120, and UE 130 are illustrated as nodes using a wireless channel in a wireless communication system. Although in Figure 1 Only one base station is shown as an example, but it may include one or more base stations that are the same as or similar to base station 110.
[0051] refer to Figure 1Base station 110 can be a network infrastructure that provides radio access to UEs 120 and 130. The coverage area of base station 110 is defined as a predetermined geographical area based on distance to reach, within which base station 110 can transmit radio signals. Base station 110 can be referred to by other terms such as 'access point (AP)', 'eNodeB (eNB)', 'gNodeB (gNB)', '5G node', 'radio point', or 'transmit / receive point (TRP)' or various other terms with equivalent technical meanings.
[0052] Each of UEs 120 and 130 is a user-usable device and can communicate with base station 110 via a radio channel. In some cases, at least one of UEs 120 and 130 can operate without user involvement. In other words, at least one of UEs 120 and 130 can be a device performing machine-type communication (MTC) and can be carried by no user. Each of UEs 120 and 130 may also be referred to by other terms such as user equipment (UE), mobile station, subscriber station, remote terminal, wireless terminal, user equipment, or various other terms with equivalent technical meanings.
[0053] Wireless communication environments can include wireless communication in licensed and unlicensed frequency bands. Base station 110, UE 120, and UE 130 can transmit and receive radio signals in unlicensed frequency bands (e.g., the 5 GHz to 7.125 GHz band, up to 71 GHz band). As one embodiment, a cellular communication system and another communication system (e.g., a wireless local area network, WLAN) can coexist in the unlicensed frequency band. To ensure fairness between the two communication systems, that is, to prevent the channel from being exclusively used by one system, base station 110, UE 120, and UE 130 can perform a channel access procedure for the unlicensed frequency band. As an example of a channel access procedure for an unlicensed frequency band, base station 110, UE 120, and UE 130 can perform Listen-Before-Speak (LBT).
[0054] Base station 110, UE 120, and UE 130 can transmit and receive radio signals in millimeter-wave frequency bands (e.g., 28 GHz, 30 GHz, 38 GHz, and 60 GHz). In this case, to enhance channel gain, base station 110, UE 120, and UE 130 can perform beamforming. Here, beamforming can include transmit beamforming and / or receive beamforming. In other words, base station 110, UE 120, and UE 130 can assign directionality to the transmitted or received signals. To this end, base station 110 and UEs 120 and 130 can select a serving beam through a beam search or beam management process. After the serving beam is selected, communication between base station 110 and UEs 120 and 130 can be performed using resources with a quasi-co-location (QCL) relationship to the resources transmitting the serving beam.
[0055] Base station 110 can select beam 112 or 113 in a specific direction. Base station 110 can use beam 112 or 113 in a specific direction to communicate with UE. For example, base station 110 can receive signals from UE 120 or send signals to UE 120 through beam 112. UE 120 can receive signals from base station 110 or send signals to base station 110 through beam 121. Furthermore, base station 110 can receive signals from UE 130 or send signals to UE 130 through beam 113. UE 130 can receive signals from base station 110 or send signals to base station 110 through beam 131.
[0056] Figure 2 This is a view illustrating the configuration of a base station in a wireless communication system according to an embodiment of the present disclosure. Figure 2 The configuration shown can be understood as Figure 1 The configuration of base station 110. Furthermore, the terms “…unit” and the suffix “…device” used herein refer to a unit that processes at least one function or operation, and can be implemented in hardware, software, or a combination thereof.
[0057] refer to Figure 2 The base station may include a wireless communication unit 210, a backhaul communication unit 220, a storage unit 230, and a controller 240.
[0058] The wireless communication unit 210 (which can be used interchangeably with a transceiver) can perform the function of transmitting and receiving signals via a wireless channel. For example, the wireless communication unit 210 can perform the conversion function between baseband signals and bit streams according to the system physical layer specifications. For example, when transmitting signals, the wireless communication unit 210 can generate complex symbols by encoding and modulating the transmitted bit stream. Furthermore, when receiving signals, the wireless communication unit 210 can recover the transmitted bit stream by demodulating and decoding the received baseband signals.
[0059] Furthermore, the wireless communication unit 210 can up-convert a baseband signal to a radio frequency (RF) band signal and transmit the converted signal via an antenna. The wireless communication unit 210 can also down-convert RF band signals received via the antenna back to baseband signals. For this purpose, the wireless communication unit 210 may include, for example, a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC). Additionally, the wireless communication unit 210 may include multiple RF chains corresponding to multiple transmit / receive paths. Furthermore, the wireless communication unit 210 may include at least one antenna array composed of multiple antenna elements.
[0060] In terms of hardware, the wireless communication unit 210 can be composed of digital units or analog units, and depending on the operating power and operating frequency, the analog unit can be composed of multiple sub-units. The digital unit can be implemented as at least one processor (e.g., a digital signal processor (DSP)).
[0061] The wireless communication unit 210 can transmit and receive signals as described above. Therefore, the entirety or part of the wireless communication unit 210 can be referred to as a 'transmitter', 'receiver', or 'transceiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel can also mean that the above-described processes are performed by the wireless communication unit 210. According to an embodiment, the wireless communication unit 210 may include at least one transceiver.
[0062] The backhaul communication unit 220 can provide an interface for communicating with other nodes in the network. In other words, the backhaul communication unit 220 can convert bit strings sent from a base station to another node (e.g., another access node, another base station, an upper-layer node, or the core network) into physical signals, and convert physical signals received from another node into bit streams.
[0063] Storage unit 230 may store basic programs, application programs, configuration information, or other data for operating the base station. Storage unit 230 may be configured as volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Storage unit 230 may provide the stored data upon request from controller 240. In one embodiment, storage unit 230 may include at least one memory.
[0064] Controller 240 can control the overall operation of the base station. For example, controller 240 can send and receive signals via wireless communication unit 210 or backhaul communication unit 220. Furthermore, controller 240 can record data in storage unit 230 and read data from storage unit 230. Controller 240 can perform the functions of the protocol stack required in the communication specification. In one embodiment, the protocol stack may be included in wireless communication unit 210. In one embodiment, controller 240 may include at least one processor.
[0065] Controller 240 can control the base station to perform operations according to at least one embodiment of the various embodiments described below. For example, controller 240 can perform a channel access procedure for an unlicensed frequency band. For example, after a transceiver (e.g., wireless communication unit 210) receives a signal transmitted in the unlicensed frequency band, controller 240 can compare the strength of the received signal with a threshold to determine whether the unlicensed frequency band is idle, the threshold being predefined or determined as a function value using, for example, bandwidth as a parameter. Furthermore, for example, controller 240 can transmit control signals to or receive control signals from the UE via the transceiver. Additionally, controller 240 can transmit data to or receive data from the UE via the transceiver. Controller 240 can determine the transmission result of the signal sent to the UE based on the control signal or data signal received from the UE.
[0066] Controller 240 can configure a downlink control information (DCI) for allocating one or more data channels to one or more cells, and can transmit the DCI to the UE via wireless communication unit 210. Furthermore, before transmitting the DCI, controller 240 can provide the UE with configuration information required for allocating one or more data channels by a DCI via higher-layer signaling. Additionally, controller 240 can transmit data channels to or receive data channels from the UE based on the configuration information and information fields included in the DCI.
[0067] Furthermore, as an example, controller 240 can maintain or change the length of the contention window (CW) of the channel access procedure (hereinafter referred to as 'contention window adjustment') based on the transmission results, i.e., based on the UE's reception results of control signals or data signals. According to an embodiment, controller 240 can determine a reference window for obtaining the transmission results used to adjust the contention window. Controller 240 can determine a data channel for adjusting the contention window within the reference window. Controller 240 can determine a reference control channel for adjusting the contention window within the reference window. If it is determined that an unlicensed frequency band is idle, controller 240 can occupy that channel.
[0068] Furthermore, the controller 240 can control the reception of uplink control information (UCI) from the UE via the wireless communication unit 210, and identify whether the downlink data channel needs to be retransmitted and / or whether the modulation and coding scheme needs to be changed by including one or more Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) messages and / or Channel State Information (CSI) in the uplink control information. Additionally, the controller 240 can control the scheduling of downlink data initiation or retransmission, generate downlink control information to request uplink control information transmission, and send the downlink control information to the UE via the wireless communication unit 210. Furthermore, the controller 240 can control the wireless communication unit 210 to receive (re)transmitted uplink data and / or uplink control information based on the downlink control information.
[0069] Despite Figure 2 The text describes each box as performing a different function, but this is merely for descriptive convenience, and each function is not necessarily distinguished in this way. For example, a base station may include... Figure 18 The controller and communication unit, and the communication unit can perform at least one function of the wireless communication unit 210 or the backhaul communication unit 220.
[0070] Figure 3 This is a view illustrating the configuration of a UE in a wireless communication system according to an embodiment of the present disclosure. Figure 3 The configuration shown can be understood as Figure 1 The configuration of UE 120 or 130. Furthermore, the terms “…unit” and the suffix “…device” used herein refer to a unit that processes at least one function or operation and can be implemented in hardware, software, or a combination thereof.
[0071] refer to Figure 3 The UE may include a wireless communication unit 310, a storage unit 320, and a controller 330.
[0072] The wireless communication unit 310 (which can be used interchangeably with a transceiver) can perform the functions of transmitting and receiving signals via a wireless channel. For example, the wireless communication unit 310 can perform conversion functions between baseband signals and bitstreams according to the system physical layer specifications. For example, when transmitting signals, the wireless communication unit 310 can generate complex symbols by encoding and modulating the transmitted bitstream. Furthermore, when receiving signals, the wireless communication unit 310 can recover the transmitted bitstream by demodulating and decoding the received baseband signals. In addition, the wireless communication unit 310 can up-convert baseband signals to RF band signals and transmit the converted signals via an antenna, and the wireless communication unit 310 can down-convert RF band signals received via the antenna back to baseband signals. For example, the wireless communication unit 310 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.
[0073] The wireless communication unit 310 may include multiple transmit / receive paths. Furthermore, the wireless communication unit 310 may include at least one antenna array composed of multiple antenna elements. In terms of hardware, the wireless communication unit 310 may be composed of digital and analog units (e.g., radio frequency integrated circuits (RFICs)). Here, the digital and analog units can be implemented in a single package. The wireless communication unit 310 may include multiple RF chains. Additionally, the wireless communication unit 310 may include at least one antenna array composed of multiple antenna elements, performing beamforming.
[0074] The wireless communication unit 310 can transmit and receive signals as described above. Therefore, the entirety or part of the wireless communication unit 310 can be referred to as a 'transmitter', 'receiver', or 'transceiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel can also mean that the above-described processes are performed by the wireless communication unit 310. According to an embodiment, the wireless communication unit 310 may include at least one transceiver.
[0075] Storage unit 320 can store basic programs, application programs, configuration information, or other data used to operate the UE. Storage unit 320 can be configured as volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Storage unit 320 can provide the stored data upon request from controller 330. According to an embodiment, storage unit 320 may include at least one memory.
[0076] The controller 330 can control the overall operation of the UE. For example, the controller 330 can send and receive signals via the wireless communication unit 310. The controller 330 records data in / reads data from the storage unit 320. The controller 330 can perform the functions of the protocol stack required in the communication specification. For this purpose, the controller 330 may include at least one processor or microprocessor, or may be part of a processor. According to an embodiment, the controller 330 may include at least one processor. Furthermore, according to an embodiment, the wireless communication unit 310 and / or a part of the controller 330 may be referred to as a communication processor (CP).
[0077] The controller 330 can control the UE to perform operations according to at least one embodiment of the various embodiments described below. For example, the controller 330 can receive downlink signals (downlink control signals or downlink data) transmitted by the base station via a transceiver (e.g., communication unit 310). Furthermore, for example, the controller 330 can determine the transmission result of the downlink signal. The transmission result is feedback regarding the transmitted downlink signal and may include, for example, an acknowledgment (ACK), a negative ACK (NACK), or discontinuous transmission (DTX). In this disclosure, the transmission result can be represented by various terms such as the reception status of the downlink signal, reception result, decoding result, and HARQ-ACK information. Furthermore, for example, the controller 330 can transmit uplink signals to the base station via a transceiver as a response signal to the downlink signal. The uplink signal may explicitly or implicitly include the transmission result of the downlink signal. Furthermore, for example, the controller 330 may include at least one or more of the aforementioned HARQ-ACK information and / or channel state information (CSI) in the uplink control information and transmit the uplink control information to the base station via the wireless communication unit 310. In this situation, uplink control information can be sent along with uplink data through the uplink data channel, or sent to the base station through the uplink data channel in the absence of uplink data.
[0078] The controller 330 can perform a channel access procedure for an unlicensed frequency band. For example, the wireless communication unit 310 receives a signal transmitted in the unlicensed frequency band, and the controller 330 can compare the strength of the received signal with a threshold to determine whether the unlicensed frequency band is idle. The threshold is predefined or determined as a function value using, for example, bandwidth as a parameter. The controller 330 can perform an access procedure for the unlicensed frequency band to transmit a signal to the base station. Furthermore, the controller 330 can use the result of performing the channel access procedure and at least one of the downlink control information received from the base station to determine uplink transmission resources for transmitting uplink control information, and transmit the uplink control information to the base station via a transceiver.
[0079] The controller 330 can receive higher-layer signaling from the base station via the wireless communication unit 310. This higher-layer signaling includes configuration information necessary to receive a downlink control information (DCI) configured to allocate one or more data channels to one or more cells. The controller 330 also receives the DCI and interprets the fields included in it based on the configuration information. Furthermore, the controller 330 can send data channels to or receive data channels from the base station based on the configuration information and the information fields included in the DCI.
[0080] Despite Figure 3 The text describes each box as performing a different function, but this is merely for descriptive convenience, and each function does not necessarily need to be distinguished in this way. For example, a UE may include... Figure 17 The controller and communication unit.
[0081] Figure 4 This is a view illustrating the configuration of communication units in a wireless communication system according to various embodiments of the present disclosure. Figure 4 It can be shown Figure 2 The wireless communication unit 210 or Figure 3 An example of a detailed configuration of the wireless communication unit 310. Specifically, Figure 4 The components used to perform beamforming can be exemplified as follows: Figure 2 The wireless communication unit 210 or Figure 3 It is part of the wireless communication unit 310.
[0082] refer to Figure 4 The wireless communication unit 210 or the wireless communication unit 310 may include an encoding / modulation unit 402, a digital beamforming unit 404, multiple transmission paths 406-1 to 406-N and an analog beamforming unit 408.
[0083] The encoding / modulation unit 402 performs channel coding. For channel coding, at least one of low-density parity-check (LDPC) codes, convolutional codes, or polar codes can be used. The encoding / modulation unit 402 can perform constellation mapping on the encoded bits to generate modulation symbols.
[0084] Digital beamforming unit 404 can perform beamforming on digital signals (e.g., modulation symbols). To do this, digital beamforming unit 404 can multiply the modulation symbols by beamforming weights. Here, beamforming weights can be used to change the amplitude and phase of the signal and can be referred to as a 'precoding matrix' or 'precoder'. Digital beamforming unit 404 can output digitally beamformed (i.e., precoded) modulation symbols to multiple transmission paths 406-1 to 406-N. In this case, the modulation symbols can be multiplexed using a multiple-input multiple-output (MIMO) transmission scheme, or the same modulation symbols can be provided to multiple transmission paths 406-1 to 406-N.
[0085] Multiple transmission paths 406-1 to 406-N can convert digital beamforming signals into analog signals. To this end, each of the multiple transmission paths 406-1 to 406-N may include an inverse Fast Fourier Transform (IFFT) calculation unit, a cyclic prefix (CP) insertion unit, a digital-to-analog converter (DAC), and an up-conversion unit. The CP insertion unit is used for Orthogonal Frequency Division Multiplexing (OFDM) schemes and can be excluded if a different physical layer scheme (e.g., filter bank multicarrier (FBMC)) is applied. The multiple transmission paths 406-1 to 406-N can provide independent signal processing for multiple streams generated via digital beamforming. Depending on the implementation, some components of the multiple transmission paths 406-1 to 406-N may be shared.
[0086] The analog beamforming unit 408 can perform beamforming on analog signals from multiple transmission paths 406-1 to 406-N and is connected to at least one antenna array composed of multiple antenna elements. To do this, the analog beamforming unit 408 can multiply the analog signals by beamforming weights. Here, the beamforming weights can be used to change the amplitude and phase of the signal. Depending on the connection structure between the multiple transmission paths 406-1 to 406-N and the antennas, the analog beamforming unit 408 can be configured in various ways. For example, each of the multiple transmission paths 406-1 to 406-N can be connected to an antenna array. As another example, the multiple transmission paths 406-1 to 406-N can be connected to a single antenna array. As yet another example, the multiple transmission paths 406-1 to 406-N can be adaptively connected to one antenna array or two or more antenna arrays.
[0087] The frame structure of the 5G system is described in more detail below with reference to the accompanying drawings.
[0088] Figure 5 This is a view showing the structure of frames, subframes, and time slots in a 5G communication system.
[0089] Figure 5Examples of the structure of frame 500, subframe 501, and time slots 502, 503, and 504 are shown for each of the cases where μ = 0 (505) indicates a subcarrier spacing of 15 kHz and μ = 1 (506) indicates a subcarrier spacing of 30 kHz. Figure 5 In the 5G system scenario shown, a frame 500 can be defined as 10 ms. A subframe 501 can be defined as 1 ms; therefore, a frame 500 can consist of a total of 10 subframes 501. A subframe 501 can consist of one or more time slots. A time slot can consist of or be defined by 14 OFDM symbols. In other words, the number of symbols in each time slot... It can be 14. In this case, the number of time slots per subframe is 501. The value (parameter set) μ(505, 506) indicating the subcarrier spacing can vary. When μ = 0, a subframe 501 can consist of one time slot 502, and when μ = 1, a subframe 501 can consist of two time slots 503 and 504.
[0090] The number of time slots per subframe can vary depending on the set subcarrier spacing value μ; therefore, the number of time slots per frame... They can be different. Each setting includes the subcarrier spacing value μ and the values based on μ. and It can be defined as shown in Table 1 below. When μ = 2, the UE can additionally receive configuration information about the cyclic prefix from the base station via higher-layer signaling.
[0091] [Table 1]
[0092]
[0093] In this disclosure, higher-layer signaling or higher-layer signals (or higher-level signals) may refer to at least one of Radio Resource Control (RRC) signaling, Packet Data Convergence Protocol (PDCP) signaling, or Media Access Control (MAC) control element (CE). Furthermore, higher-layer signaling or higher-layer signals may include system information, such as a System Information Block (SIB) publicly transmitted to multiple UEs, and information other than the Main Information Block (MIB) (e.g., the PBCH payload) transmitted via the Physical Broadcast Channel (PBCH) may also be included in higher-layer signaling or higher-layer signals. In this case, the MIB may also be represented as being included in the aforementioned higher-layer signaling or higher-layer signals.
[0094] Figure 6 This is a view showing the basic structure of a 5G communication system in the time-frequency domain. In other words, Figure 6This is a view showing the basic structure of the time-frequency domain, which is the radio resource area for transmitting data or control channels.
[0095] exist Figure 6 In this diagram, the horizontal axis refers to the time domain, and the vertical axis refers to the frequency domain. The basic unit of a resource in both the time and frequency domains is a resource element (RE) 601, which can be defined as corresponding to an orthogonal frequency division multiplexing (OFDM) symbol 602 in the time domain and a subcarrier 603 in the frequency domain. In the frequency domain, (For example) 12 consecutive REs can form a resource block (RB) 604.
[0096] For each subcarrier spacing setting value μ and carrier, by Subcarriers and A resource grid consisting of OFDM symbols can be defined as a Common Resource Block (CRB) indicated by higher-level signaling. To begin with, and for a given antenna port, subcarrier spacing setting μ, and transmission direction (e.g., downlink, uplink, or sidelink), a resource grid can exist.
[0097] The base station can transmit the carrier bandwidth (μ) for uplink and downlink subcarrier spacing settings to the UE via higher-layer signaling (e.g., higher-layer parameters 'carrierBandwidth' and 'offsetToCarrier'). and starting position In this case, the carrier bandwidth It can be set by the higher-level parameter 'carrierBandwidth' used to set the subcarrier spacing μ, and the starting position It is the frequency offset of the subcarrier with the lowest frequency among the available carrier resources, and can be set to 'offsetToCarrier' and expressed as the number of RBs. In this case, and This can be a value in units of subcarriers. The UE receiving this parameter can... and Knowing the starting position and size of the carrier bandwidth. Transmission. and Examples of higher-level signaling information are shown in Table 2.
[0098] [Table 2]
[0099]
[0100] Here, point A is the value that provides a common reference point for the resource block grid. In the case of PCell downlink, the UE can obtain point A via the higher-layer parameter 'offsetToPointA', and in all other cases, point A is obtained via the absolute radio frequency channel number (ARFCN) set by the higher-layer parameter 'absoluteFrequencyPointA'. Here, 'offsetToPointA' is the frequency offset between point A and the lowest subcarrier of the RB with the lowest frequency that overlaps with the synchronization signal / physical broadcast channel (SS / PBCH) selected or used by the UE during the initial cell selection process, and is expressed in RBs. The common resource block (CRB) number or index increments from 0 to 1 in the direction of increasing value in the frequency domain. In this case, the center of the common resource block with subcarrier spacing μ and subcarrier index 0 matches point A. Frequency domain common resource block index The RE of the subcarrier spacing μ is related to Here, k is a value defined relative to point A; in other words, k = 0 is point A.
[0101] The physical resource block (PRB) of subcarrier spacing μ is defined as the portion of the bandwidth (BWP) from 0 to μ. The number or index. Here, i is the number or index of the bandwidth section. The PRB in bandwidth section i and CRB The relationship is here, It is the number of CRBs from CRB 0 to the first RB starting from bandwidth part i.
[0102] <bwp>
[0103] The following describes the bandwidth configuration in a 5G communication system in detail with reference to the accompanying drawings.
[0104] Figure 7 This is a view showing an example configuration of the bandwidth portion of a 5G communication system.
[0105] refer to Figure 7 Multiple bandwidth sections can be configured within the carrier bandwidth or UE bandwidth 700, namely, bandwidth section #1 (BWP#1) 710, bandwidth section #2 (BWP#2) 750, and bandwidth section #3 (BWP#3) 790. Bandwidth section #3 790 occupies the entire UE bandwidth 700. Bandwidth section #1 710 and bandwidth section #2 750 can occupy the lower and upper halves of the UE bandwidth 700, respectively.
[0106] The base station can configure one or more bandwidth portions for the UE in the uplink or downlink. For each bandwidth portion, one or more of the following upper-layer parameters can be set. In this case, the bandwidth portion settings can be independent of the uplink and downlink. Table 3 shows an example of the higher-layer signaling information element BWP.
[0107] [Table 3]
[0108]
[0109] In Table 3, 'bwp-Id' indicates the bandwidth portion identifier, 'locationAndBandwidth' indicates the frequency domain location and bandwidth of the bandwidth portion, 'subcarrierSpacing' indicates the subcarrier spacing used in the bandwidth portion, and 'cyclicPrefix' indicates whether an extended cyclic prefix (CP) or a regular CP is used in the bandwidth portion. Various other bandwidth portion-related parameters can be configured for the UE in addition to the parameters mentioned above. These parameters can be transmitted from the base station to the UE via higher-layer signaling (e.g., RRC signaling). At least one of one or more configured bandwidth portions can be activated within a given time period. The instruction to activate a configured bandwidth portion can be semi-statically transmitted from the base station to the UE via RRC signaling or dynamically transmitted via downlink control information (DCI) used to schedule the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH).
[0110] According to an embodiment, prior to RRC connection, the UE may be configured by the base station via the Master Information Block (MIB) with an Initial Bandwidth Part (BWP) for initial access. More specifically, the UE may receive configuration information regarding the search space and control resource set (CORESET), wherein, during the initial access phase, the Physical Downlink Control Channel (PDCCH) may be transmitted via the MIB in this CORESET. In this case, each of the control resource set and the search space configured via the MIB can be considered as an identifier (or ID 0). The base station may provide the UE with frequency allocation information, time allocation information, and at least one or more pieces of information in the parameter set for control resource set #0 via the MIB. Here, the parameter set may include at least one of subcarrier spacing or CP. Here, CP may represent at least one of the following: the length of CP or information corresponding to the CP length (e.g., normal or extended).
[0111] Furthermore, the base station can provide the UE with configuration information regarding the timing and monitoring period of control resource set #0, i.e., the configuration information of search space #0, via the MIB. The UE can use the frequency domain set obtained from the MIB as control resource set #0 as the initial BWP for initial access. In this case, the identifier (ID) of the initial BWP can be considered as 0.
[0112] The bandwidth configurations supported in the aforementioned 5G can be used for various purposes.
[0113] According to an embodiment, when the bandwidth supported by the UE is less than the system bandwidth, the UE can be configured to support data transmission / reception within the system bandwidth. For example, the base station can configure the frequency domain location of the bandwidth portion in the UE to allow the UE to transmit / receive data at specific frequency locations within the system bandwidth.
[0114] According to an embodiment, to support different parameter sets, the base station can configure multiple bandwidth portions for the UE. For example, to support certain UEs using a 15kHz subcarrier spacing and a 30kHz subcarrier spacing to transmit / receive data, the base station can configure two bandwidths for the UE, namely 15kHz and 30kHz subcarrier spacings. Different bandwidth portions can be frequency-division multiplexed, and the bandwidth portion set to a specific subcarrier spacing can be activated when transmitting / receiving data at a specific subcarrier spacing.
[0115] According to an embodiment, to reduce the power consumption of the UE, the base station can configure bandwidth portions with different bandwidth sizes for the UE. For example, significant power consumption may occur when the UE supports bandwidths exceeding a very large bandwidth (e.g., 100MHz) and always uses that bandwidth to send / receive data. In particular, using a large bandwidth of 100MHz to monitor unnecessary downlink control channels in the absence of service is very inefficient in terms of power consumption. To reduce the power consumption of the UE, the base station can configure a relatively small bandwidth portion for the UE, such as a 20MHz bandwidth portion. In the absence of service, the UE can perform monitoring in the 20MHz bandwidth, and if data is available, the UE can send / receive data in the 100MHz bandwidth according to instructions from the base station.
[0116] As described above, prior to RRC connection, the UE can receive configuration information for the initial bandwidth portion via the MIB during the initial access phase. More specifically, the UE can be configured with a control resource set (CORESET) for the PDCCH based on the PBCH MIB. The bandwidth of the control resource set configured via the MIB can be considered as the initial downlink bandwidth portion, and the UE can receive the Physical Downlink Shared Channel (PDSCH) for transmitting SIBs via the configured initial bandwidth portion. Specifically, the UE can detect the PDCCH in the search space and control resource set configured with the MIB, receive the Remaining System Information (RMSI) or System Information Block (SIB) 1 required for initial access via the PDCCH-scheduled PDSCH, and obtain configuration information about the uplink initial bandwidth portion via SIB1 (or RMSI). The initial bandwidth portion can be used for other System Information (OSI), paging and random access, and receiving SIBs.
[0117] If the UE is configured with one or more bandwidth portions, the base station can use the bandwidth portion indicator in the DCI to indicate changes in the bandwidth portion to the UE.
[0118] As an example, when the currently active bandwidth portion of the UE is Figure 7 When the bandwidth portion #1 is 710 in the DCI, the base station can use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 is 750 to the UE, and the UE can change the bandwidth portion to bandwidth portion #2 is 750 based on the received bandwidth portion indicator in the DCI.
[0119] As described above, since DCI-based bandwidth portion changes can be indicated by DCI-scheduled PDSCH or PUSCH, if a bandwidth portion change request is received, the UE should be able to receive or transmit the DCI-scheduled PDSCH or PUSCH without difficulty within the changed bandwidth portion. To this end, the standard specifies the delay time T required when changing the bandwidth portion. BWP The requirements can be defined as shown in Table 4 below.
[0120] [Table 4]
[0121]
[0122] The bandwidth portion change delay requirement depends on the UE's capability to support either Type 1 or Type 2. The UE can report the supported bandwidth portion delay time type to the base station. If the UE receives a DCI in time slot n that includes a bandwidth portion change indicator according to the above-described bandwidth portion change delay time requirement, the UE can proceed no later than time slot n+T. BWP The time required for the change to the new bandwidth portion, as indicated by the bandwidth portion change indicator, is completed, and transmission / reception can be performed on the data channel scheduled by the DCI within the changed new bandwidth portion. When scheduling the data channel in the new bandwidth portion, the base station can consider the UE's bandwidth portion change delay time T. BWP This is used to determine the time-domain resource allocation of the data channel. In other words, when determining the time-domain resource allocation of the data channel when scheduling the data channel with a new bandwidth portion, the base station can change the delay time after the bandwidth portion of the data channel is changed. Therefore, the UE may not expect the DCI indication indicating the bandwidth portion change to be less than the bandwidth portion change delay time T. BWP The time slot offset (K0 or K2).
[0123] If the UE has already received a DCI indicating a partial bandwidth change (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving during the time period from the third symbol of the slot in which the PDCCH including the DCI was received to the first symbol of the slot indicated by the slot offset (K0 or K2) in the time domain resource allocation field of the DCI. For example, if the UE receives a DCI indicating a partial bandwidth change in slot n, and the slot offset value indicated by the DCI is K, the UE may refrain from transmitting or receiving during the period from the third symbol of slot n to the symbol preceding the previous symbol of slot n+K (i.e., the last symbol of slot n+K-1).
[0124] Next, the SS / PBCH block in 5G will be described.
[0125] The SS / PBCH block can refer to a physical layer channel block composed of the primary SS (PSS), secondary SS (SSS), and PBCH. Details are as follows.
[0126] PSS: A signal that serves as a downlink time / frequency synchronization reference and provides partial information about the cell ID.
[0127] SSS: Used as a reference for downlink time / frequency synchronization and provides additional information about the cell ID not provided by PSS. Additionally, it can also be used as a reference signal (RS) for PBCH demodulation.
[0128] PBCH: Provides the basic system information necessary for the UE to transmit and receive data and control channels. This basic system information may include search space-related control information indicating radio resource mapping information for control channels, or scheduling control information for separate data channels used to transmit system information.
[0129] SS / PBCH Blocks: An SS / PBCH block is composed of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within 5ms, and each sent SS / PBCH block can be distinguished by an index.
[0130] 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 thus be configured with Control Resource Set #0 (which may correspond to a Control Resource Set with Control Resource Set Index 0). Assuming the selected SS / PBCH block (or the SS / PBCH block successfully decoded in PBCH decoding) and the demodulation reference signal (DMRS) transmitted in Control Resource Set #0 are quasi-co-located (QCLed), the UE can monitor Control Resource Set #0. The UE can obtain system information through downlink control information transmitted in Control Resource Set #0. The UE can obtain configuration information related to the Random Access Channel (RACH) required for initial access from the obtained system information. The UE can send a Physical RACH (PRACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain the SS / PBCH block index selected by the UE. The base station can know which block the UE has selected from the SS / PBCH blocks and monitor the associated Control Resource Set #0.
[0131] <dci>
[0132] Next, we will describe the downlink control information (DCI) in the 5G system in detail.
[0133] In 5G systems, scheduling information for uplink data (or PUSCH) or downlink data (or PDSCH) is transmitted from the base station to the UE via DCI. For PUSCH or PDSCH, the UE may attempt to monitor or detect at least one of the DCI format used for backoff and the DCI format used for non-backoff. The backoff DCI format may consist of fields predefined between the base station and the UE, and the non-backoff DCI format may include configurable fields.
[0134] DCI can be transmitted via the PDCCH, which serves as the physical downlink control channel, through channel coding and modulation. Cyclic Redundancy Check (CRC) is added to the DCI payload, and the CRC is scrambled using a Radio Network Temporary Identifier (RNTI), which serves as the UE identifier. Different RNTIs can be used for DCI purposes, such as UE-specific data transmission, power control commands, or random access responses. In other words, the RNTI is not explicitly sent, but it is included in and transmitted during the CRC calculation process. When a DCI is received on the PDCCH, the UE can use the assigned RNTI to check the CRC, and if the CRC check is correct, the UE knows that the DCI has been sent.
[0135] For example, the DCI for scheduling PDSCH used for System Information (SI) can be scrambled to SI-RNTI. The DCI for scheduling PDSCH used for Random Access Response (RAR) messages can be scrambled to RA-RNTI. The DCI for scheduling PDSCH used for paging messages can be scrambled to P-RNTI. The DCI providing Slot Format Indicator (SFI) can be scrambled to SFI-RNTI. The DCI providing Transmit Power Control (TPC) can be scrambled to TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled to Cell RNTI (C-RNTI).
[0136] DCI format 0_0 can be used as a backoff DCI for scheduling PUSCH, and in this case, the CRC can be scrambled with at least one of C-RNTI, CS-RNTI, or MCS-C-RNTI. A DCI format 0_0 with a CRC scrambled with at least one of C-RNTI, configured scheduling (CS)-RNTI, and modulation and coding scheme (MCS)-C-RNTI may include at least one of the following information, for example.
[0137] DCI format identifier: An identifier used to identify the DCI format. For example, a UE receiving DCI through a one-bit identifier can identify that the DCI has a UL DCI format (e.g., DCI format 0_1) when the identifier value is 0, and has a DL DCI format (e.g., DCI format 1_0) when the identifier value is 1.
[0138] Frequency domain resource allocation: DCI format 0_0 only supports resource allocation type 1 schemes, and includes Each bit indicates the RB of the frequency domain resource allocated in the resource allocation type 1 scheme. Here, when the UE is monitoring DCI format 0_0 in the common search space, This is the size of the initial uplink bandwidth portion, and it is used when the UE is monitoring DCI format 0_0 in its UE-specific search space. This refers to the size of the uplink bandwidth portion currently in use. In other words, the bandwidth portion used to determine the size of the frequency domain resource allocation field can vary depending on the search space in which the fallback DCI format is transmitted.
[0139] In one embodiment, when performing PUSCH frequency hopping, in Of the bits, N can be used UL_hop The most significant bit (MSB) is used to indicate the frequency offset. Here, if N UL_hop =1 means that two offsets have been set by higher-level signaling. If N UL_hop =2 means that four offsets were set by higher-level signaling, and Each bit indicates the frequency domain resource area allocated according to resource allocation type 1 below.
[0140] According to the embodiment, when PUSCH frequency hopping is not performed, Each bit provides a frequency domain resource area allocated according to resource allocation type 1.
[0141] Time-domain resource allocation: 4 bits, indicating the row index of the time-domain resource allocation table, including the PUSCH mapping type, PUSCH transmission slot offset, PUSCH start symbol, and number of PUSCH transmission symbols. The time-domain resource allocation table can be configured via higher-layer signaling or pre-configured between the base station and the UE.
[0142] Frequency hopping flag: 1 bit, indicating whether to perform PUSCH frequency hopping (enabled) or not to perform PUSCH frequency hopping (disabled).
[0143] Modulation and coding scheme (MCS): Indicates the modulation and coding scheme used for data transmission.
[0144] New data indicator: Indicates whether HARQ is initial transmission or retransmission.
[0145] Redundant Version (RV): Indicates a redundant version of HARQ.
[0146] HARQ process count: Indicates the number of HARQ processes.
[0147] TPC command: Indicates the transmit power control command for PUSCH used for scheduling.
[0148] Padding bits: Fields used to match different DCI formats (e.g., DCI format 1_0) and sizes (total number of bits), and are inserted as 0 if necessary.
[0149] UL / SUL indicator: One bit. If the cell has two or more ULs, and the size of DCI format 1_0 before adding padding bits is greater than the size of DCI format 0_0 before adding padding bits, then the UL / SUL indicator has one bit; otherwise, the UL / SUL indicator is absent or has 0 bits. If the UL / SUL indicator is present, it is the last bit after the padding bits of DCI format 0_0.
[0150] ChannelAccess-CPext: Two bits, indicating the channel access type and CP extension for a cell operating in an unlicensed frequency band. It is absent or 0 bits when the cell is operating in a licensed frequency band.
[0151] For DCI formats other than DCI format 0_0, please refer to the 3GPP standardization documents.
[0152] <Time Domain Resource Allocation>
[0153] The following describes the time-domain resource allocation of data channels in a 5G communication system.
[0154] The base station can configure a table for the UE to allocate time-domain resources for the downlink data channel (PDSCH) and uplink data channel (PUSCH) through higher-level signaling (e.g., RRC signaling), or a table similar to Table 5, which can be a predefined time-domain resource allocation table between the base station and the UE.
[0155] For example, in the case of DCI fallback, the UE can use the predefined tables shown in Table 5, and in the case of non-DCI fallback, the UE can use the tables configured via higher-level signaling.
[0156] [Table 5]
[0157] row index PUSCH mapping type <![CDATA[K2]]> S L 1 Type A j 0 14 2 Type A j 0 12 3 Type A j 0 10 4 Type B j 2 10 5 Type B j 4 10 6 Type B j 4 8 7 Type B j 4 6 8 Type A j+1 0 14 9 Type A j+1 0 12 10 Type A j+1 0 10 11 Type A j+2 0 14 12 Type A j+2 0 12 13 Type A j+2 0 10 14 Type B j 8 6 15 Type A j+3 0 14 16 Type A j+3 0 10
[0158] In this context, for time-domain resource allocation configured via higher-layer signaling, a table with a maximum of maxNrofDL-Allocations = 16 entries can be configured for PDSCH, and a table with a maximum of maxNrofUL-Allocations = 16 entries can be configured for PUSCH. For example, each table may include at least one of the following: PDCCH to PDSCH time slot timing (specified as K0, corresponding to the time interval between the PDCCH reception time and the PDSCH transmission time scheduled by the received PDCCH) or PDCCH to PUSCH time slot timing (specified as K2, corresponding to the time interval between the PDCCH time and the PUSCH transmission time scheduled by the received PDCCH); wherein the position S of the starting symbol of the PDSCH or PUSCH scheduled in the time slot and the length L of the allocated symbol; and the mapping type of the PDSCH or PUSCH. When using higher-layer signaling, information elements can be provided from the base station to the UE, for example, as shown in Table 6 below.
[0159] [Table 6]
[0160]
[0161] Here, 'k0' is the offset in timeslots and indicates the timing from PDCCH to PDSCH; 'k2' is the offset in timeslots and indicates the timing from PDCCH to PUSCH; 'mappingType' indicates the mapping type of PDSCH or PUSCH; and 'startSymbolAndLength' indicates the start symbol and length of PDSCH or PUSCH. The base station can notify the UE of one of the entries in the time-domain resource allocation table via L1 signaling. For example, it can be indicated using the 'Time-Domain Resource Allocation' field in the DCI. The UE can obtain the time-domain resource allocation of PDSCH or PUSCH based on the fields in the DCI received from the base station.
[0162] <Frequency Domain Resource Allocation>
[0163] The following describes the frequency domain resource allocation of data channels in a 5G communication system.
[0164] As a method for indicating frequency domain resource allocation for downlink data channels (PDSCH) and uplink data channels (PUSCH), two types are supported: resource allocation type 0 and resource allocation type 1.
[0165] Resource allocation type 0 is a method for allocating resources in units of resource block groups (RBGs) consisting of P consecutive RBs, and can be notified to the UE from the base station in the form of a bitmap. In this case, the RBG can consist of a set of consecutive virtual RBs (VRBs), and the size P of the RBG (normal RBG size P) can be determined based on the value of the higher-level parameter "rbg-Size" and the bandwidth portion size defined in Table 7 below.
[0166] [Table 7]
[0167]
[0168]
[0169] Here, the size is The total number of RBGs in the bandwidth portion i (N) RBG )yes Here, the size of the first RBG is if The size of the last RBG yes otherwise It is P. The size of the RBG excluding this RBG is P. The size is N. RBG Each bit in the bitmap can correspond to its respective RBG. The RBG can be indexed in ascending order of frequency, starting from the lowest position of the bandwidth portion. For N in the bandwidth portion... RBG RBG, RBG#0 to RBG#(N) RBG -1) can be mapped to the most significant bit (MSB) to the least significant bit (LSB) of the RBG bitmap. When a specific bit in the bitmap is 1, the UE can determine that an RBG corresponding to that bit value has been allocated, and when a specific bit in the bitmap is 0, the UE can determine that no RBG corresponding to that bit value has been allocated.
[0170] Resource allocation type 1 is a method for allocating resources with a start position and length to consecutively allocated VRBs, and in this case, interleaving or non-interleaving can be additionally applied to the consecutively allocated VRBs. The resource allocation field of resource allocation type 1 can be configured with a resource indicator value (RIV), and the RIV can be determined by the start position (RB) of the VRB. start ) and the length of the continuously allocated RB (L) RB Composed of RB. start It can be the first PRB index at the start of resource allocation, and L RB This can be the length or number of the assigned consecutive PRBs. Specifically, the size is... The RIV in the bandwidth portion can be defined as follows.
[0171] if but
[0172] otherwise,
[0173] Among them, L RBs ≥1 and will not exceed
[0174] In this scenario, the DCI can vary depending on the search space in which the fallback format (e.g., DCI format 0_0 or DCI format 1_0) is transmitted. For example, when the fallback DCI format (DCI format 0_0) of the DCI (i.e., the uplink (UL) grant configured or scheduled for uplink transmission) is transmitted in the common search space (CSS), the initial uplink bandwidth portion size can be used. or As Similarly, when configuring or scheduling the backoff DCI format (DCI format 1_0) for downlink received DCI to be transmitted in the common search space (CSS), if control resource set #0 is configured in the cell, then and / or This controls the size of resource set #0, and if resource set #0 is not configured, then... and / or It is the size of the initial downlink bandwidth portion.
[0175] In this scenario, when the fallback DCI format, i.e., DCI format 0_0 or DCI format 1_0, is transmitted in the UE-specific search space (USS), or the size of the fallback DCI format transmitted in the UE-specific search space is determined by the size of the initial uplink bandwidth portion or the initial downlink bandwidth portion, but the DCI is applied to a size of... When the other part of the active bandwidth is used, RIV can correspond to and Furthermore, RIV can be defined as follows.
[0176] if but
[0177] otherwise,
[0178] Among them, L′ RBs =L RBs / K,RB′ start =RB start / K,L′ RBs No more than N BWP -RB′ start
[0179] In this case, if Then K is a set {1, 2, 4, 8} that satisfies The maximum value. Otherwise K is 1.
[0180] The base station can configure resource allocation types for the UE via higher-layer signaling. For example, the higher-layer parameter `resourceAllocation` can be set to one of `resourceAllocationtype0`, `resourceAllocationtype1`, or `dynamicSwitch`. If the UE is configured with resource allocation types 0 and 1, or if the higher-layer parameter `resourceAllocation` is set to `dynamicSwitch`, the most significant bit (MSB) of the resource allocation field in the scheduled DCI format can be indicated as either resource allocation type 0 or resource allocation type 1. Resource allocation information can be indicated based on the indicated resource allocation type via the remaining bits excluding the bit corresponding to the MSB, and based on this, the UE can interpret the resource allocation information of the DCI. If the UE is configured with resource allocation type 0 or resource allocation type 1, or if the higher-layer parameter `resourceAllocation` is set to `resourceAllocationtype0` or `resourceAllocationtype1`, the resource allocation field in the scheduled DCI format can indicate resource allocation information based on the configured resource allocation type, and the UE can interpret the resource allocation information of the DCI based on the configured resource allocation type.
[0181] <coreset>
[0182] The downlink control channel in a 5G communication system is described in more detail below with reference to the accompanying drawings.
[0183] Figure 8 This is a view illustrating an example configuration of the control resource set for the downlink control channel of a 5G communication system. In other words, Figure 8 This is a view illustrating an example of a control resource set (CORESET) in a 5G wireless communication system in which the downlink control channel is transmitted.
[0184] refer to Figure 8 Two control resource sets, namely control resource set #1801 and control resource set #2802, are configured in the frequency domain within the UE bandwidth portion 810 and in the time domain within a single time slot 820. Control resource sets 801 and 802 can be configured in the frequency domain within a specific frequency resource 803 of the UE bandwidth portion 810 and in the time domain as one or more OFDM symbols. An OFDM symbol can be defined as a control resource set length (control resource set duration) 804. In the example shown, control resource set #1 801 can be configured for a control resource set length of two symbols, and control resource set #2 802 can be configured for a control resource set length of one symbol.
[0185] Each of the aforementioned control resource sets can be configured for the UE by the base station via higher-level signaling (e.g., system information, Master Information Block (MIB), or Radio Resource Control (RRC) signaling). Configuring a control resource set for the UE means providing the UE with information such as the identifier (ID) of the control resource set, the frequency location of the control resource set, and the symbol length of the control resource set. For example, higher-level signaling information elements for configuring control resource sets may include information as shown in Table 8.
[0186] [Table 8]
[0187]
[0188] Here, 'controlResourceSetId' indicates the control resource set identifier, 'frequencyDomainResources' indicates frequency domain resources, 'duration' indicates the time range of the control resource set (i.e., time domain resources), 'cce-REG-Mappingtype' indicates the CCE-to-REG mapping scheme, 'reg-BundleSize' indicates the REG bundle size, 'interleaverSize' indicates the interleaver size, and 'shiftIndex' indicates the interleaver shift. Furthermore, tci-StatesPDCCH is configuration information regarding the Transmission Configuration Indication (TCI) state and may include one or more SS / PBCH block indices or Channel State Information Reference Signal (CSI-RS) indices, which have a quasi-co-address (QCL) relationship with the DMRS transmitted in the corresponding control resource set.
[0189] Figure 9 This is a view showing the structure of the downlink control channel in a 5G communication system. In other words, Figure 9 This is a view illustrating an example of the basic units that constitute the time and frequency resources available in a 5G wireless communication system for the downlink control channel.
[0190] refer to Figure 9 The basic unit constituting the time and frequency resources of the downlink control channel can be called a resource element group (REG) 903, and the REG 903 can be defined in the time domain by an OFDM symbol 901 and in the frequency domain by a PRB 902 (i.e., 12 subcarriers). The base station can configure the downlink control channel allocation unit by cascading at least one REG 903.
[0191] In 5G, when the basic unit for allocating downlink control channels is a Control Channel Element (CCE) 904, a CCE 904 can be composed of multiple REG 903s. In the example of REG 903 shown, a REG 903 can consist of 12 REs, and if a CCE 904 consists of 6 REG 903s, then a CCE 904 can consist of 72 REs. An area configuring a downlink control resource set can consist of multiple CCE 904s, and a specific downlink control channel can be mapped to one or more CCE 904s within the control resource set according to the aggregation level (AL). CCE 904s in the control resource set are distinguished by numbers, and in this case, the CCE 904 numbers can be assigned according to a logical mapping scheme.
[0192] The basic unit of the downlink control channel (i.e., REG 903) may include the region of the RE mapped to by the DCI and the region mapped to by the DMRS 905 for demodulating the DCI. At least one (in) can be transmitted in a single REG 903. Figure 9 The example shown uses three DMRS 905s. Depending on the aggregation level (AL), the number of CCEs required to transmit the downlink control channel can be, for example, 1, 2, 4, 8, or 16, and link adaptation of the downlink control channel can be achieved using different numbers of CCEs. For example, if AL = L, a downlink control channel can be transmitted via L CCEs. The UE needs to detect the signal in the control resource set without knowing the existence of the downlink control channel, and for this blind decoding, a search space indicating the CCE set is defined. 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 to bundle 1, 2, 4, 8, or 16 CCEs, the UE has multiple search spaces. The search space set can be defined as the set of search spaces under all configured aggregation levels.
[0193] <Search Space>
[0194] The search space for PDCCH can be categorized into a common search space (CSS) and a UE-specific search space (USS). A predetermined group of UEs, or all UEs, can search the common search space to receive dynamic scheduling of cell common control information, such as paging messages or system information. For example, PDSCH scheduling allocation information for transmitting SIBs, including those of the cell service provider, can be detected by examining the common search space. The common search space can be defined as a pre-agreed set of CCEs that allow a predetermined group of UEs, or all UEs, to receive PDCCHs. Scheduling allocation information for UE-specific PDSCHs or PUSCHs can be detected by examining the UE-specific search space. The UE-specific search space can be explicitly defined using various system parameters and functions of UE identification.
[0195] In 5G wireless communication systems, the parameters of the PDCCH search space can be configured by the base station in the UE via higher-level signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can configure the UE, such as the number of PDCCH candidates under each aggregation level L, the monitoring period of the search space, the symbol-based monitoring timing in the search space time slots, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the search space, and the index of the control resource set to be monitored in the search space. For example, higher-level signaling information elements configuring the PDCCH search space parameters may include information as shown in Table 9.
[0196] [Table 9]
[0197]
[0198] Here, 'searchSpaceId' indicates the search space identifier, 'controlResourceSetId' indicates the control resource set identifier, 'monitoringSlotPeriodicityAndOffset' indicates the monitoring slot period, 'duration' indicates the length of the time range to be monitored, 'monitoringSymbolsWithinSlot' indicates the symbols used for PDCCH monitoring in the slot, 'nrofCandidates' indicates the number of PDCCH candidate groups under each aggregation level, 'searchSpaceType' indicates the search space type, 'common' includes parameters for the common search space, and 'ue-Specific' includes parameters for the UE-specific search space. Based on the configuration information, the base station can configure one or more search space sets for the UE. According to an embodiment, the base station can configure search space set 1 and search space set 2 for the UE, and configure them to monitor DCI format A scrambled to X-RNTI in search space set 1 within the common search space, and monitor DCI format B scrambled to Y-RNTI in search space set 2 within the UE-specific search space.
[0199] According to the configuration information, one or more search space sets can exist in a public search space or a terminal-specific search space. For example, search space set #1 and search space set #2 can be configured in a public search space, and search space set #3 and search space set #4 can be configured in a UE-specific search space.
[0200] 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.
[0201] 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.
[0202] DCI format 2_0, with CRC scrambled by SFI-RNTI.
[0203] DCI format 2_1, with CRC scrambled by INT-RNTI.
[0204] DCI format 2_2, with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI.
[0205] DCI format 2_3, with CRC scrambled by TPC-SRS-RNTI.
[0206] Within the UE-specific search space, combinations of DCI formats and RNTI can be monitored. Of course, this is not limited to the examples described below.
[0207] DCI format 0_0 / 1_0, with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.
[0208] DCI format 1_0 / 1_1, with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.
[0209] The specified RNTI can be defined and used as follows.
[0210] C-RNTI (Cell RNTI): Used for scheduling UE-specific PDSCH
[0211] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH
[0212] Configurable Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCH random access with semi-static configuration. RNTI (RA-RNTI): Used to schedule PDSCH during the random access phase.
[0213] Paging RNTI (P-RNTI): Used to schedule the PDSCH sent in the paging process.
[0214] System Information RNTI (SI-RNTI): This is the PDSCH used to schedule the transmission of system information.
[0215] Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been perforated.
[0216] PUSCH transmit power control RNTI (TPC-PUSCH-RNTI): Used to indicate the power control commands for the PUSCH.
[0217] PUCCH Transmit Power Control RNTI (TPC-PUCCH-RNTI): Used to indicate the power control commands of the PUCCH.
[0218] SRS Transmit Power Control RNTI (TPC-SRS-RNTI): Used to indicate power control commands for the Sounding Reference Signal (SRS).
[0219] The above DCI format may follow the definition in Table 10 below.
[0220] [Table 10]
[0221]
[0222] In a 5G communication system such as NR, physical channels and physical signals may be divided as follows. For example, uplink / downlink physical channels refer to a set of resource elements (REs) used to transmit information transmitted through higher layers and typically include PDCCH, PUCCH, PDSCH, and PUSCH. Uplink / downlink physical signals refer to signals used in the physical layer without transmitting information transmitted through higher layers and typically include DM-RS, CSI-RS, and SRS. As described above, in the present disclosure, physical channels and physical signals may be referred to as "signals" without distinguishing between them. For example, a base station transmitting a downlink signal may mean that the base station transmits at least one of a downlink physical channel and a downlink physical signal (such as PDCCH, PDSCH, DM-RS, or CSI-RS). In other words, the term'signal' in the present disclosure includes at least one of a channel and a signal, and they may be distinguished from each other according to the context if necessary.
[0223] <TCI state>
[0224] A method for configuring TCI states for PDCCH (or PDCCH DMRS) in a 5G communication system is described in detail below.
[0225] TCI states are used to indicate the quasi-co-location (QCL) relationship between PDCCH (or PDCCH DMRS) and another reference signal (RS) or channel. Here, antenna port A of a certain reference signal (reference RS#A) and antenna port B of a target reference signal (target RS#B) being QCLed means that the UE is allowed to apply all or some of the channel-related parameters estimated at antenna port A when measuring the channel from antenna port B. QCL-related parameters may include at least one of the following: 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, and different parameters need to be associated according to the context. NR may support four types of QCL relationships as shown in Table 11 below.
[0226] [Table 11]
[0227] QCL type Large-scale features A Doppler frequency shift, Doppler spread, average delay, delay spread B Doppler frequency shift, Doppler spread C Doppler shift, average delay D Space Reception (Rx) Parameters <I
[0228] Here, spatial Rx parameters can be collectively referred to as all or some of various parameters such as Angle of Arrival (AoA), Power Angle Spectrum (PAS) of AoA, Angle of Departure (AoD), PAS of AoD, Transmit / Receive Channel Correlation, Transmit / Receive Beamforming, and Spatial Channel Correlation. QCL relationships can be configured for the UE using TCI states and QCL information as RRC signaling parameters, as shown in Table 12 below. Referring to Table 12, the base station 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) referencing the TCI state ID. Indicating up to two QCL relationships is merely an example; the base station can indicate more than two QCL relationships for the target RS to the UE. In this case, the QCL information (QCL-Info) included in each TCI state can include 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 12.
[0229] [Table 12]
[0230]
[0231] Here, tci-StateId represents the TCI state ID, qcl-Type1 includes QCL information for the first target RS referencing the TCI state ID, and qcl-Type2 includes QCL information for the second target RS referencing the TCI state ID. For each QCL information, 'cell' indicates the serving cell index of the UE configured with the RS indicated by the QCL information, 'bwp-Id' indicates the BWP index of the RS indicated by the QCL information, and 'csi-rs' or 'ssb' indicates the CSI-RS ID or Synchronization Signal / Sequence Block (SSB) ID indicated by the QCL information. The base station can use one or more beams to perform communication with the UE. To this end, the base station can transmit information about N different beams to the UE through N different TCI states. For example, when N=3, the base station allows the qcl-Type parameter (e.g., qcl-Type2) included in the three TCI states to be associated with the CSI-RS or SSB corresponding to different beams, and sets it to QCL type D, indicating to the UE that the antenna port referencing different TCI states is associated with different spatial Rx parameters (i.e., different beams).
[0232] Specifically, example combinations of TCI states applicable to the PDCCH DMRS antenna port are shown in Table 13 below. In Table 13, the fourth row is the combination assumed by the UE before RRC configuration, and this row cannot be configured for the UE after RRC configuration.
[0233] [Table 13]
[0234]
[0235]
[0236] The base station supports hierarchical signaling for dynamic TCI state allocation for the PDCCH beam to the UE. Specifically, the base station can configure N TCI states (TCI#0, TCI#1, ..., TCI#M-1) for the UE via RRC signaling, and configure some of them as the TCI states of CORESET. Subsequently, the base station can indicate and activate one of the TCI states of CORESET via MAC CE signaling (e.g., a MAC CE activation command for providing the TCI states of CORESET). The UE receiving the MAC CE signaling can receive it from the time slot (e.g., time slot k) after sending the HARQ-ACK information for the PDSCH providing the MAC CE signaling. Starting from the first time slot after the previous time slot, the state indicated by the MAC CE signaling is applied, and the PDCCH is received based on beam information including the TCI state. Here, It is the number of time slots included in each subframe for subcarrier spacing μ.
[0237] In this configuration, the MAC CE used to indicate the TCI state of the PDCCH can consist of 2 bytes (16 bits) and may include a 5-bit serving cell ID field, a 4-bit CORESET ID field, and a 7-bit TCI state ID field. The serving cell ID field indicates the ID of the serving cell to which the MAC CE is applied, and the CORESET ID field indicates the ID of the CORESET to which the MAC CE is indicated or applied. The TCI state ID field indicates the TCI state applied to the CORESET identified by the CORESET ID field. If the CORESET ID is 0, the TCI state ID field may indicate one of 64 TCI states starting from the first TCI state configured via 'tci-States-ToAddModList' and 'tci-States-ToReleaseList' in the 'PDSCH-Config' used as higher-layer signaling for activating the bandwidth portion. If CORESETID is set to a value other than 0, the TCI State ID field can indicate one of the TCI states configured by 'tci-StatesPDCCH-ToAddModList' and 'tci-StatesPDCCH-ToReleaseList', which are higher-level signalings of the CORESET indicated by the CORESET ID field.
[0238] A UE that receives a CORESET TCI status indication and / or is active via MAC CE signaling can assume that the same QCL information is applied to all or one search space connected to CORESET until another TCI status is indicated via another MAC CE signaling.
[0239] <TCI Status for Radio Link Monitoring (RLM)>
[0240] If the UE is not configured with or has not received higher-level configuration information related to RLM-RS, but the TCI status configured or received by the UE for PDCCH reception includes one or more CSI-RS, the UE may operate as follows.
[0241] When the TCI state activated to receive PDCCH includes only one RS, the UE uses that RS to perform RLM operations.
[0242] The UE does not need to use aperiodic RS or semi-persistent RS to perform RLM.
[0243] When L max When = 4, the UE selects N from the search space with the shortest PDCCH monitoring period from the search space associated with the CORESET in which the PDCCH is transmitted, within the RS that is activated and provides the TCI state for PDCCH reception. RLM One RS. When the search space of one or more CORESETs has the same PDCCH monitoring period, the UE can determine the order of CORESET selection as starting from the highest CORESET index.
[0244] A UE configured with multiple downlink bandwidth portions for its serving cell can perform RLM using RS as follows. RS is the RS corresponding to an RS index configured or provided via higher-layer signaling 'RadioLinkMonitoringRS' for the activated downlink bandwidth portion. Alternatively, if not configured or provided via higher-layer signaling 'RadioLinkMonitoringRS' for the activated downlink bandwidth portion, the RS in TCI state is configured and activated to the CORESET received by the PDCCH in the activated downlink bandwidth portion.
[0245] <TCI status used for PDCCH dispatch>
[0246] A UE receiving the search space ID as a type 0 / 0A / 2 PDCCH CSS set and C-RNTI can determine the PDCCH monitoring timing for the type 0 / 0A / 2 PDCCH CSS set and monitor PDCCH candidates at the PDCCH monitoring timing associated with the SS / PBCH block. Here, the SS / PBCH block can be determined based on at least one of the following.
[0247] The SS / PBCH block is co-located with the CSI-RS quasi-co-address included in the TCI state indicated or activated by the MAC CE activation indicator in the active bandwidth portion including CORESET index 0, or
[0248] SS / PBCH blocks used in a recent contention-based random access procedure
[0249] For a UE that does not receive TCI status information indicating the QCL information of the DM-RS antenna port of the PDCCH transmitted in the CORESET, it can be assumed that the DM-RS antenna port of the PDCCH transmitted in the CORESET configured by the configuration information transmitted via the MIB, the DM-RS antenna port of the PDSCH scheduled via the PDCCH, and all the averaged gain, QCL-Type A and QCL-Type D quasi-co-address features in the SS / PBCH block that transmits the MIB are all quasi-co-addressable.
[0250] For a CORESET with index 0, the UE may assume that the DM-RS antenna port of the PDCCH received in the CORESET is quasi-co-located with the downlink RS or SS / PBCH block, as shown below. In other words, when the TCI state is indicated or activated by a MAC CE activation command of the CORESET, the UE may assume that one or more downlink RSs configured by the TCI state are quasi-co-located with the DM-RS antenna port of the PDCCH. When no MAC CE activation command indicating or activating the TCI state of the CORESET is received after the most recent random access procedure in any random access procedure other than a non-contention-based random access procedure triggered by a PDCCH command, the UE may assume that it is quasi-co-located with the SS / PBCH block identified by the UE during the most recent random access procedure.
[0251] When the UE does not receive TCI state configuration information through the CORESET configuration information shown in Table 8 for any CORESET other than the one with index 0, or when the UE receives initial configuration for multiple TCI states but does not receive a MAC CE activation command indicating or activating one TCI state of the CORESET, the UE may assume that the DM-RS antenna port of the PDCCH received in the CORESET is quasi-co-located with the SS / PBCH block identified during the initial access process.
[0252] When, for any CORESET other than the one with index 0, as part of a synchronized reconfiguration process, the UE receives configuration information for the TCI state via the CORESET configuration information as shown in Table 8, but does not receive a MAC CE activation command indicating or activating a TCI state of the CORESET, the UE may assume that the DM-RS antenna port of the PDCCH received in the CORESET is quasi-co-located with the CSI-RS or SS / PBCH block identified in the random access process initiated by the synchronized reconfiguration process.
[0253] For any CORESET other than the one with index 0, when the UE receives a TCI state of the CORESET or receives a MAC CE activation command indicating or activating a TCI state of the CORESET, the UE may assume that the DM-RS antenna port of the PDCCH received in the CORESET is co-located with one or more RS quasi-co-located by the TCI state.
[0254] For a CORESET with index 0, the UE can receive the QCL-TypeD attribute of the CSI-RS configured by the TCI state indicated or activated via the MAC CE activation command from the SS / PBCH.
[0255] The UE receiving MAC CE signaling begins receiving MAC CE signaling from the time slot (e.g., time slot k) after sending HARQ-ACK information for the PDSCH providing MAC CE signaling via PUCCH. Starting from the first time slot after the previous time slot, the TCI state indicated by the MACCE signaling is applied, and the PDCCH is received based on beam information including the TCI state. Here, It is the number of time slots included in each subframe for subcarrier spacing μ.
[0256] <Slot Format Indicator (SFI)>
[0257] In 5G communication systems, the downlink and uplink signal transmission windows can be dynamically changed. To this end, the base station can indicate to the UE via a Slot Format Indicator (SFI) whether each OFDM symbol constituting a time slot is a downlink symbol, an uplink symbol, or a flexible symbol. Here, a flexible symbol can represent a symbol that is neither a downlink nor an uplink symbol, or it can be changed to a downlink or uplink symbol through UE-specific control or scheduling information. In this case, the flexible symbol can include gap protection necessary during the handover from downlink to uplink.
[0258] A UE receiving a time slot format indicator can perform downlink signal reception operations from a base station in a symbol indicated as a downlink symbol, and perform uplink signal transmission operations to a base station in a symbol indicated as an uplink symbol. For a symbol indicated as a flexible symbol, the UE can at least perform PDCCH monitoring operations, and via another indicator (e.g., DCI), the UE can perform downlink signal reception operations from a base station (e.g., when receiving DCI format 1_0 or 1_1), or perform uplink signal transmission operations to a base station (e.g., DCI format 0_0 or 0_1).
[0259] Figure 10 This is a view showing an example of UL-DL configuration (UL / DL configuration) in a 5G system, illustrating the three steps of UL-DL configuration for symbols / time slots.
[0260] refer to Figure 10 In the first step, cell-specific configuration information 1010, such as SIB or similar system information, is used to configure the uplink-downlink of symbols / slots in a semi-static manner for uplink-downlink configuration of uplink-downlink. Specifically, the cell-specific uplink-downlink configuration information 1010 in the system information may include uplink-downlink mode information and information indicating reference subcarrier spacing. The uplink-downlink mode information may indicate the transmission period 1003 for each mode, the number of consecutive full DL slots at the beginning of each DL-UL mode 1011, the number of consecutive DL symbols at the beginning of a slot after the last full DL slot 1012, the number of consecutive full UL slots at the end of each DL-UL mode 1013, or the number of consecutive UL symbols at the end of a slot before the first full UL slot 1014. In this case, the UE can determine that slots / symbols not indicated as uplink or downlink can be flexible slots / symbols.
[0261] In the second step, UE-specific configuration information 1020 transmitted via UE-specific higher-layer signaling (i.e., RRC signaling) indicates the symbols that will be configured as downlink or uplink in one or more flexible time slots 1021 and 1022, which include flexible symbols. As an example, UE-specific uplink-downlink configuration information 1020 may include time slot indices indicating time slots 1021 and 1022 including flexible symbols, the number of consecutive DL symbols at the beginning of time slots 1023 and 1025, the number of consecutive UL symbols at the end of time slots 1024 and 1026, or information indicating the entire downlink for each time slot, or information indicating the entire uplink. In this case, the symbols / time slots configured as uplink or downlink in the first step via cell-specific configuration information 1010 cannot be changed to downlink or uplink via UE-specific higher-layer signaling 1020.
[0262] Finally, to dynamically change the downlink and uplink signal transmission windows, the downlink control information of the downlink control channel includes a slot format indicator 1030, which indicates whether each symbol in each of multiple slots from the slot where the UE detects the downlink control information is a downlink symbol, an uplink symbol, or a flexible symbol. In this case, for a symbol / slot configured as uplink or downlink in the first and second steps, the slot format indicator cannot indicate it as downlink or uplink. The slot format of each slot 1031 and 1032, which includes at least one symbol not configured as uplink or downlink in the first and second steps, can be indicated by the corresponding downlink control information.
[0263] As shown in Table 14, the slot format indicator can indicate the uplink-downlink configuration of 14 symbols in a slot. The slot format indicator can be sent simultaneously to multiple UEs via the UE group (or cell) common control channel. In other words, downlink control information including the slot format indicator can be sent using an identifier different from the UE-specific C-RNTI (cell-RNTI) (e.g., PDCCH CRC scrambling using SFI-RNTI). The downlink control information can include slot format indicators for one or more slots (i.e., N slots). Here, N can be an integer greater than 0, or a value set by the UE from a previously defined set of possible values via higher-layer signaling from the base station. The size of the slot format indicator can be set for the UE by the base station via higher-layer signaling.
[0264] [Table 14]
[0265]
[0266] In Table 14, D represents a downlink symbol, U represents an uplink symbol, and F represents a flexible symbol. According to Table 14, the total number of time slot formats that a time slot can support is 256. In NR systems, the maximum bit size of the information bits that can be used to indicate the time slot format is 128 bits, and it can be set by the base station for the UE via higher-layer signaling (e.g., 'dci-PayloadSize').
[0267] In this context, cells operating in unlicensed frequency bands may employ one or more additional time slot formats, or modify at least one or more existing time slot formats, thereby configuring and indicating the additional time slot formats, as shown in Table 15. Table 15 illustrates examples of additional time slot formats, where one time slot consists only of an uplink symbol and a flexible symbol F.
[0268] [Table 15]
[0269]
[0270] In one embodiment, the downlink control information used to indicate the slot format can indicate multiple slot formats of multiple serving cells, and each serving cell's multiple slot formats can be identified by the serving cell ID. Furthermore, the downlink control information can indicate a combination of slot formats for one or more slots of each serving cell. For example, when a slot format indicator index field in the downlink control information is 3 bits in size and indicates the slot format of one serving cell, the 3-bit slot format indicator index field can indicate a total of eight slot formats (or combinations of slot formats), and the base station can indicate the slot format indicator index field through UE group common downlink control information. In one embodiment, at least one slot format indicator index field included in the downlink control information can be configured as a slot format combination indicator for multiple slots. For example, Table 16 shows a 3-bit slot format combination indicator composed of the slot formats in Tables 14 and 15. In the values of the slot format combination indicator, {0, 1, 2, 3, 4} indicate the slot format of one slot. The remaining three values {5, 6, 7} indicate the slot format of the four slots, and the UE can sequentially apply the indicated slot format to the four slots starting from the slot where downlink control information including the slot format combination indicator is detected.
[0271] [Table 16]
[0272]
[0273]
[0274] <xdd>
[0275] 5G wireless communication systems (e.g., NR systems) typically use higher center frequencies than LTE systems, resulting in reduced communication service coverage between the base station and the UE, thus requiring coverage enhancement. Specifically, uplink coverage enhancement is crucial in Time Division Duplex (TDD) systems where the UE's transmit power is typically lower than the base station's transmit power and downlink traffic constitutes a higher proportion of service. Methods to physically enhance uplink channel coverage between the base station and the UE could include increasing uplink time resources, lowering the center frequency of the uplink carrier, using a lower center frequency, or increasing the UE's transmit power. However, changing the frequency may be limited because frequency bands are determined for each network operator. Furthermore, increasing the maximum UE transmit power is also limited because the maximum permissible transmit power is constrained by per-area or per-band limits used to reduce interference.
[0276] Therefore, to enhance the coverage of base stations and UEs, it may be necessary to have systems that allow for increased uplink time resources by allocating uplink and downlink resources in the frequency domain (as in an FDD system), rather than allocating uplink and downlink resources only in the time domain according to the uplink and downlink traffic ratio in a TDD system. In this disclosure, a system that can flexibly allocate and use uplink and downlink resources in the time and / or frequency domains is defined as an XDD system. In this context, 'X' in XDD may mean time and / or frequency. Furthermore, an XDD system may also be referred to as an enhanced TDD system, a flexible TDD system, a hybrid TDD system, a TDD-FDD system, a hybrid TDD-FDD system, a full-duplex system, or a hybrid frequency division duplex (HDD) system, at least one or more of these. For ease of description, it is referred to as an XDD system in this disclosure.
[0277] Figure 11 This is a view illustrating the uplink-downlink configuration of an XDD system according to embodiments of the present disclosure, in which uplink and downlink resources are flexibly partitioned in the time and frequency domains. Figure 11 The time domain can be in units of one or more symbols or one or more time slots.
[0278] refer to Figure 11 In the embodiment shown on the left, from the base station's perspective, in the uplink-downlink configuration 1100 of the entire XDD system, for the entire frequency band 1101, uplink resources 1105 and downlink resources 1103 can be flexibly allocated per symbol or time slot 1102 according to the uplink and downlink service ratio. In this case, a guard band 1104 and / or flexible resources can be allocated between the downlink resources 1103 and uplink resources 1105 in the frequency band. In other words, guard band 1104 and / or flexible resources can be allocated to reduce interference in uplink channel or signal reception caused by out-of-band transmission or unintended transmission when the base station transmits downlink channels or signals in downlink resource 1103. Figure 11 In the embodiment shown on the right, by configuring the base station, downlink and uplink resources can be allocated in the time domain to UE1 1110 and UE2 1120, which have more services on the downlink than on the uplink. Figure 11 The diagram shows that UE3 1130, located at the cell boundary and lacking sufficient uplink coverage, was allocated only uplink resources within certain timeframes due to base station configuration. Conversely, UE4 1140, operating at the cell boundary and therefore lacking sufficient uplink coverage but possessing relatively high downlink and uplink traffic, could be allocated more uplink resources for uplink coverage in the time domain and more downlink resources in the frequency band.
[0279] More downlink resources in the time domain can be allocated to UEs operating relatively close to the cell center, while more uplink resources can be allocated to UEs operating relatively close to the cell boundary with insufficient uplink coverage, thereby extending uplink coverage. In this case, the XDD system can have the advantage of being able to allocate uplink and downlink transmit / receive resources more flexibly in the time and frequency domains according to the uplink and downlink traffic ratio, as well as extending uplink coverage. For example, the XDD system can also be used when providing URLLC services that require minimizing uplink transmit latency or simultaneous uplink and downlink transmit / receive (such as in Integrated Access and Backhaul (IAB) systems or trunks).
[0280] This disclosure provides a method for configuring uplink-downlink resources in the time and frequency domains in an XDD system capable of flexibly allocating uplink and downlink resources in the time and / or frequency domains, as well as a channel and signal transmission / reception method and apparatus according to this method. This disclosure also proposes uplink-downlink transmission / reception methods and apparatus for base stations and UEs under the assumption of an XDD system. However, this disclosure is not limited to XDD systems, but can be applied to uplink-downlink transmission / reception methods and apparatus for base stations and UEs in other split-duplex or full-duplex systems that can be provided in 5G systems.
[0281] Embodiments of this disclosure relate to methods and apparatus for configuring resources for uplink or downlink transmission / reception in the frequency domain within a bandwidth or bandwidth portion of an XDD system. According to embodiments of this disclosure, by means of the method for configuring resources for uplink or downlink transmission / reception, a UE can be configured with at least one of the following: uplink resources capable of uplink transmission in the frequency domain within a bandwidth or bandwidth portion for a specific time (symbol unit or time slot unit); downlink resources capable of downlink reception; or flexible resources capable of both uplink transmission and downlink reception.
[0282] Furthermore, unlike TDD systems, which can only configure uplink or downlink transmission / reception resources in the time domain, XDD systems can allocate or configure uplink and downlink transmission / reception resources separately not only in the time domain but also in the frequency domain. In this case, if uplink and downlink resources are configured together in a bandwidth or bandwidth segment, interference may occur due to at least one of the following: interference between uplink and downlink transmission and reception, out-of-band transmission, or unwanted transmission. Therefore, a guard band may be needed between uplink and downlink resources. In this disclosure, the guard band is specified by a frequency range, and according to embodiments, it may include a guard period, wherein the guard band is specified by a time range. In embodiments of this disclosure, the guard band may be predefined or selected from multiple frequency bands configured via higher-layer signaling. According to embodiments of this disclosure, by configuring resources for uplink or downlink transmission and reception, one or more guard bands can be configured for the UE between uplink and downlink resources in a bandwidth or bandwidth segment in the frequency domain at a specific time (symbol unit or time slot unit). In other words, the UE can configure or define one or more resource block sets using the configured guard band. In this disclosure, a resource block set may include one or more resource blocks, and according to embodiments, may be composed of smaller units (e.g., resource elements) than resource blocks. Reference Figure 12A and Figure 12B This describes the operation of a UE using a configured protection band to configure or determine one or more resource block sets.
[0283] To minimize or eliminate the impact of interference that may occur during uplink and downlink transmission / reception, UEs supporting XDD systems can be configured with one or more intra-cell guard bands for a cell or carrier via higher-layer signals from the base station, or intra-cell guard bands can be configured using predefined guard bands. In this case, the intra-cell guard band can be configured independently or equally for each of the downlink cell or carrier and the uplink cell or carrier.
[0284] Meanwhile, for ease of description, in the various embodiments of this disclosure, it is assumed that the UE is configured with a guard band for each cell, but the UE may be configured with a guard band by bandwidth portion and by cell or carrier.
[0285] Figure 12A and Figure 12B An example is shown of configuring one or more intra-cell guard bands in a cell that supports XDD or in the carrier bandwidth or UE bandwidth or bandwidth portion that uses XDD. Figure 12A An example is shown of configuring three resource block sets (RB sets) in the carrier bandwidth, UE bandwidth, or bandwidth portion, and... Figure 12B An example is shown where two resource block sets (RB sets) are configured in the carrier bandwidth, UE bandwidth, or bandwidth portion.
[0286] N can be configured for the UE in the cell or carrier through higher-layer signaling. RB-set,x -1 guard band. Here, x = DL or UL, where DL represents the downlink cell or carrier, and UL represents the uplink cell or carrier. Table 17 is an example of higher-layer signaling. Higher-layer signaling may include, for example, UL-DL-GuardBand.
[0287] [Table 17]
[0288]
[0289] In Table 17, startCRB is as follows: Figure 12A and Figure 12B The index of the starting CRB of the intra-cell guard band in B or D. And nrofCRBs is as follows Figure 12A and Figure 12B The length or size of the intra-cell guard band in B' or D' `startCRB` and `nrofCRBs` can be represented as the number of CRBs, N, or the number of PRBs, N. In this case, B' and D' can be the same as or different from each other. In Table 17, examples of X0, X1, and X2 can be 4, 274, and 15. Meanwhile, `nrofCRBs` can be an indicator such as... Figure 12A and Figure 12B The index of the last CRB in the guard band within the cell, indicated by C or E. The value of `nrofCRBs`. If `nrofCRBs` is 0, it means that there is no guard band in the cell, or the size of the guard band is 0. Guard band information can include one or more values (`startCRB`, `nrofCRBs`). The first of every two values is the lowest CRB index of the guard band within the cell. Furthermore, the second value can represent the length or size of the protection band within the cell. Here, the CRB index can be replaced by the PRB index.
[0290] According to embodiments of this disclosure, the UE can use the sequence length of the UL-DL-GuardBand information (e.g., sequence length / 2) or the amount of information about CRBs included in the UL-DL-GuardBand information (startCRB, nrofCRBs) to determine the number of uplink / downlink intra-cell guard bands configured from the base station (e.g., N). RB-set,x -1). The UE can determine the number of resource block sets (e.g., N) based on the number of protected frequency bands within the determined cell. RB-set,x ).
[0291] As described above, a UE configured with an intra-cell guard band can divide the bandwidth or a portion of the bandwidth other than the intra-cell guard band into N. RB-set Each resource block set (RB set) or resource region is used to perform uplink / downlink transmission / reception using the resources included in each resource block set. In this case, the frequency resource region of each resource block set can be determined as follows.
[0292] The first or starting CRB index of the first resource block set ( Figure 12A 'A' and Figure 12B (e.g., resource block set index 0):
[0293] The last or end CRB index of the first resource block set ( Figure 12A 'B' and Figure 12B (in the 'B'):
[0294] The final resource block set (e.g., resource block set index N) RS-set-1 The first or starting CRB index () Figure 12A The 'E' and Figure 12B (C in the text)
[0295] The last or end CRB index of the last resource block set ( Figure 12A and Figure 12B (in the 'F'):
[0296] The first or starting CRB index of one or more resource block sets between the first resource block set and the last resource block set. Figure 12A (C in the text)
[0297]
[0298] The last or end CRB index of one or more resource block sets between the first and last resource block sets. Figure 12A (D in the text)
[0299]
[0300] In this case, the resource block set s can be derived from... It consists of RBs, among which Furthermore, based on the subcarrier spacing configuration μ, s = 0, 1, ..., N can be configured using higher-layer signals, with the first RB and the available bandwidth of the carrier. RB-set,x -1、 and
[0301] If the UE is configured such that the guard band size of the entire guard band is 0 within a certain time range, the UE can determine that there is no guard band in the cell or carrier within the corresponding time range.
[0302] If the UE is not configured with an intra-cell guard band via higher-layer signaling (UL-DL-GuardBand), the UE can use the resource block set pattern and intra-cell guard band previously defined with the base station to determine the frequency resource area and intra-cell guard band of (multiple) resource block sets. The resource block set pattern can be, for example, as follows: Figure 13A , 13B As shown in Figure 13C, the DL bandwidth portion has various numbers of resource block sets and guard bands. In this case, the intra-cell guard band and resource block set pattern can be predefined according to the subcarrier spacing and the size of the carrier or bandwidth portion. Furthermore, intra-cell guard bands can be predefined independently for downlink and uplink, or configured via higher-layer signals, and at least one of the positions or sizes of the downlink intra-cell guard bands can be the same as or different from at least one of the positions or sizes of the uplink intra-cell guard bands. Here, predefining intra-cell guard bands can mean that, for each intra-cell guard band, the first or starting CRB index of the predefined intra-cell guard band... Size of the protection frequency band within the community Or finally or end the CRB index. At least one of them.
[0303] In this scenario, for a cell or carrier, the UE can determine, for the uplink or downlink bandwidth portion i, as well as Here, 0≤s0≤s1≤N RB-set,x -1. In the bandwidth part i, it can be arranged from 0 to... The ascending order determines the resource block set index. Here, This refers to the number of resource block sets included in bandwidth portion i. According to embodiments of this disclosure, RBset#0 of bandwidth portion i may correspond to RBset#s0 of a cell or carrier, and the bandwidth portion i... It can correspond to RBset#s1 of a cell or carrier.
[0304] In this scenario, higher-layer signals can be used to configure the UE whether each specific set of resource blocks is a set of resource blocks for downlink or uplink. Alternatively, higher-layer signals can be used to configure the UE as a flexible set of resource blocks, which can be either downlink or uplink. In other words, higher-layer signals can be used to configure the UE whether a frequency domain resource is for uplink, downlink, or flexible use, and examples of these higher-layer signals are shown in Table 18.
[0305] [Table 18]
[0306]
[0307] In other words, for N RB-set,x or Each resource block set can be configured by the base station via XDD-UL-DL-Configuration to determine whether it is a resource block set for downlink (hereinafter referred to as the downlink resource block set), a resource block set for uplink (hereinafter referred to as the uplink resource block set), or a flexible resource block set that can be either downlink or uplink (hereinafter referred to as the flexible resource block set). Figure 12A In the example, RBset#0 can be configured as the downlink resource block set, RBset#1 can be configured as the flexible resource block set (or the uplink resource block set), and RBset#2 can be configured as the downlink resource block set. Figure 12B In the example, RBset#0 can be configured as a flexible resource block set (or an uplink resource block set), and RBset#1 can be configured as a downlink resource block set. In this case, the resource block set can be configured for the UE for each of the uplink and downlink cell or carrier or bandwidth portions via higher-level signals. For example, for the uplink cell or carrier or bandwidth portion, the resource block set can be configured via XDD-UL-DL-Configuration or XDD-UL-DL-Configuration-UL, and for the downlink cell or carrier or bandwidth portion, it can be configured via XDD-UL-DL-Configuration or XDD-UL-DL-Configuration-DL. In this case, the higher-level signals are merely examples, and other signals can be used. Furthermore, information regarding XDD-UL-DL-Configuration can be configured for the UE via UL-DL-GuardBand.
[0308] If XDD-UL-DL-Configuration is not configured or provided, the UE can determine N. RB-set,x or All resource block sets are flexible resource block sets. In this case, for downlink bandwidth or downlink bandwidth portions, the UE can determine N. RB-set,DL or All resource block sets are downlink resource block sets, and for uplink bandwidth or uplink bandwidth portions, the UE can determine N. RB-set,UL or The entire resource block set consists of uplink resource block sets.
[0309] Figures 13A-13C This is a view showing an example of a frequency domain resource block set configuration for a UE that is configured with two or three resource block sets for the downlink bandwidth portion.
[0310] like Figure 13A As shown, according to embodiments of this disclosure, the UE can be configured via a higher-layer signal (XDD-UL-DL-Configuration) with RBset#0 and RBset#2 as downlink resource block sets, and RBset#1 as a flexible resource block set. Alternatively, as Figure 13C As shown, RBset#0, RBset#1, and RBset#2 can all be configured as downlink resource block sets (XDD-UL-DL-Configuration) via higher-layer signals. Figure 13B As shown, the UE can be configured with two resource block sets for the downlink bandwidth portion, and through a higher-layer signal (XDD-UL-DL-Configuration), it is configured with RBset#1 as the downlink resource block set and RBset#0 as the flexible resource block set. Meanwhile, Figures 13A-13C This example only shows a configuration of the resource block set for the downlink bandwidth portion; other applications are also possible.
[0311] Figure 14A , 14B Views 14C and 14D are examples of frequency domain resource block set configurations for UEs configured with two or three resource block sets in the uplink bandwidth portion.
[0312] like Figure 14A As shown, according to an embodiment of this disclosure, a UE configured with three resource block sets for uplink bandwidth partitioning can be configured via a higher-layer signal (XDD-UL-DL-Configuration) to have RBset#0 and RBset#2 as flexible resource block sets and RBset#1 as an uplink resource block set.
[0313] like Figure 14B As shown, according to an embodiment of this disclosure, a UE configured with two resource block sets for uplink bandwidth partitioning can be configured with RBset#1 as a flexible resource block set and RBset#0 as an uplink resource block set via a higher-layer signal (XDD-UL-DL-Configuration).
[0314] like Figure 14C As shown, according to embodiments of this disclosure, a UE configured with three resource block sets for uplink bandwidth partitioning can be configured via a higher-layer signal (XDD-UL-DL-Configuration) to have RBset#0 and RBset#2 as uplink resource block sets and RBset#1 as a flexible resource block set. Alternatively, as... Figure 14D As shown, a UE configured with three resource block sets for uplink bandwidth partitioning can determine, through a single explicit signal, that RBset#0, RBset#1, and RBset#2 are all uplink resource block sets, or that RBset#0, RBset#1, and RBset#2 are all uplink resource block sets. Meanwhile, Figures 14A-14D This only shows an example of the resource block set configuration for the uplink bandwidth portion; other applications are also possible.
[0315] Figures 13A-13C and Figures 14A-14D An example is shown where the UE explicitly configures the type of each resource block set via signals from the base station. Alternatively, the UE can use information about one or more configured guard bands to determine the type of each resource block set. For example, regarding a resource block set between two guard bands, the UE can determine whether the resource block set is an uplink resource block set, a downlink resource block set, or a flexible resource block set based on the size occupied by those two guard bands (e.g., in kHz).
[0316] In this case, a new bandwidth configuration can be used to support XDD systems. For example, such as Figure 15 As shown, the UE can be configured with a flexible bandwidth portion, rather than an uplink bandwidth portion or a downlink bandwidth portion. Figure 15 This is a view illustrating an example of a flexible bandwidth portion configured to support an XDD system. The flexible bandwidth portion can be determined as, for example, an uplink bandwidth portion, a downlink bandwidth portion, or a hybrid (or XDD) bandwidth portion of uplink and downlink bandwidth portions, according to at least one or a combination of the methods described below. For example, at least one set of resource blocks configured in the flexible bandwidth portion can be determined as one of an uplink resource block set, a downlink resource block set, or a flexible resource block set. Simultaneously, the flexible bandwidth portion can be additionally configured in at least one bandwidth portion of the uplink or downlink bandwidth portion, configured to replace at least one bandwidth portion of the uplink or downlink bandwidth portion, or configured independently in the absence of an uplink or downlink bandwidth portion configuration.
[0317] The UE can determine whether to use the flexible resource block set for uplink transmission or downlink reception. In other words, one or more methods described below can be used to determine whether the flexible resource block set is a downlink resource block set or an uplink resource block set.
[0318] Method 1: Determined based on uplink transmission or downlink reception information indicated in the DCI.
[0319] A UE can determine whether a flexible resource block set is a downlink or uplink resource block set by receiving a DCI from the base station. For example, when at least one RB of frequency resources allocated to PDSCH is included in the flexible resource block set, a UE scheduled to receive PDSCH via DCI can determine that the flexible resource block set is a downlink resource block set. As another example, when at least one RB of frequency resources allocated to PUSCH is included in the flexible resource block set, a UE scheduled to transmit PUSCH via DCI can determine that the flexible resource block set is an uplink resource block set. Similarly, when at least one RB or RE of frequency resources allocated to aperiodic CSI-RS, SRS, or PRACH is included in the flexible resource block set, a UE receiving a DCI indicating, for example, aperiodic CSI-RS reception, SRS transmission, or PRACH transmission can determine whether the flexible resource block set is a downlink or uplink resource block set.
[0320] use Figure 13A The example describes a method for a UE to determine the frequency domain configuration of a set of resource blocks(s) in the downlink bandwidth portion. If the UE receives a DCI indicating the reception of aperiodic CSI-RS, and at least one RE or RB in the aperiodic CSI-RS indicated by the DCI is included in or across a flexible resource block set (RBset#1), then the UE can determine that the flexible resource block set (RB set#1) is a downlink resource block set.
[0321] Similarly, using Figure 14C The example describes a method for a UE to determine the frequency domain configuration of a resource block set in the uplink bandwidth portion. If the UE receives a DCI indicating SRS or PRACH transmission, and at least one RE or RB in the SRS or PRACH resources indicated by the DCI is included in or across a flexible resource block set (RBset#1), then the UE can determine that the flexible resource block set (RB set#1) is an uplink resource block set.
[0322] Method 2: Determine by the indicator of the DCI.
[0323] The base station may include a field in at least one of the DCIs received by the UE (e.g., a group public DCI commonly sent to multiple UE groups), wherein the field may inform or indicate information about whether the flexible resource block set is a downlink resource block set or an uplink resource block set, and send it to the UE. In this case, sending this information via a group public DCI is merely an example, and the information may also be sent via a cell public DCI or a UE-specific DCI.
[0324] A UE receiving DCI from a base station can determine which resource set (e.g., a flexible resource block set) is a downlink or uplink resource block set based on information included in the DCI fields. For example, the base station can configure a bitmap of the same size (i.e., N bits) as the number N resource block sets included in one of the cell, carrier, or bandwidth portions, and use this bitmap to indicate to the UE whether the resource block set is a downlink or uplink resource block set. In this case, the most significant bit to the least significant bit of the bitmap can be sequentially mapped in ascending order of resource block set index from the resource block set with the lowest resource block set index. For example, bitmap values of 0 and 1 can be predefined between the base station and the UE to represent the downlink resource block set and the uplink resource block set, respectively. Alternatively, the base station can configure multiple bitmap values for the UE via higher-layer signals. In the foregoing example, a bitmap value of 0 is defined as representing the uplink resource block set and 1 as representing the downlink resource block set, but they can be defined in other ways.
[0325] At the same time, using bitmaps is just an example, and more can be included in DCI. Information represented by one or fewer bits, or a table consisting of combinations of information, or a field consisting of corresponding information. In this case, it can be predefined between the base station and the UE, or configured for the UE via higher-level signals from the base station. Information represented by one or fewer bits, or a table consisting of combinations of information, or information corresponding to such information.
[0326] The following is for reference. Figures 13A-13C The example describes a method for a UE to determine the frequency domain configuration of resource block sets for a downlink bandwidth portion. The base station configures a 3-bit bitmap for a cell, carrier, or bandwidth portion consisting of three resource block sets (N=3) and sends a DCI including bitmap information to the UE. The UE receiving the DCI determines the resource block set configuration for each resource block set using the bitmap information. For example, when... Figure 13A When the value of the bitmap received by the UE is 0 0 0, the UE can determine that RBset#0, RBset#1, and RBset#2 are all downlink resource block sets. As another example, when the value of the received bitmap is 0-1-0, the UE can determine that RBset#0 and RBset#2 are downlink resource block sets, and RBset#1 is an uplink resource block set.
[0327] The following is for reference. Figure 14A The example describes a method by which the UE determines the frequency domain configuration of resource block sets for the uplink bandwidth portion. When the bitmap value included in the DCI received by the UE from the base station is 1 0 1, the UE can determine that RBset#0 and RBset#2 are uplink resource block sets, and RBset#1 is a downlink resource block set. When the received bitmap value is 1 11, the UE can determine that RBset#0, RBset#1, and RBset#2 are all uplink resource block sets. In this case, when the resource block set is configured as an uplink resource block set or a downlink resource block set via a higher-layer signal (e.g., XDD-UL-DL-Configuration), the base station may not be allowed to indicate a resource block set configured as an uplink resource block set via a higher-layer signal as a downlink resource block set via the DCI, or vice versa.
[0328] In other words, the base station, through the DCI, always indicates a set of resource blocks configured as an uplink resource block set via a higher-layer signal (XDD-UL-DL-Configuration) as an uplink resource block set (or a flexible resource block set), and through the DCI, always indicates a set of resource blocks configured as a downlink resource block set via a higher-layer signal (XDD-UL-DL-Configuration) as a downlink resource block set (or a flexible resource block set). Meanwhile, the UE can assume that for a set of resource blocks configured as a flexible resource block set via a higher-layer signal (XDD-UL-DL-Configuration) or a set of resource blocks that are not configured or have not received a higher-layer signal (XDD-UL-DL-Configuration), the resource block set can be either a downlink resource block set or an uplink resource block set.
[0329] In this scenario, for a cell, carrier, or bandwidth portion, the base station can use a bitmap of the same size as the number of flexible resource block sets included in one of the cell, carrier, or bandwidth portions to indicate to the UE whether the flexible resource block set is a downlink resource block set or an uplink resource block set. In this case, the size of the bitmap can be equal to the number of flexible resource block sets included in each of the uplink and downlink bandwidth portions, or it can be determined as the maximum number of flexible resource block sets included in both the uplink and downlink bandwidth portions.
[0330] The most significant bit to the least significant bit of the bitmap can be sequentially mapped according to the resource block set index, increasing from the flexible resource block set with the lowest resource block set index. In this case, bitmap value 0 can be predefined between the base station and the UE to represent the downlink resource block set, and bitmap value 1 to represent the uplink resource block set. Alternatively, the base station can configure (multiple) bitmap values for the UE via higher-layer signals. In the aforementioned example, bitmap value 0 is defined to represent the uplink resource block set, and bitmap value 1 is defined to represent the downlink resource block set, but they can be defined in other ways.
[0331] exist Figure 13B In the example, for a cell, carrier, or bandwidth portion consisting of two resource block sets, the base station can use higher-layer signals transmitted to the UE to configure resource block set RBset#1 as a downlink resource block set or an uplink resource block set, and RBset#0 as a flexible resource block set. Furthermore, the base station can configure bitmap information, where the bitmap information includes a bitmap of the same size (i.e., N1 bits) as the number of resource block sets N1 configured as flexible resource block sets via higher-layer signals in the resource block sets included in the cell, carrier, or bandwidth portion, and transmit a DCI including the bitmap information to the UE. The UE receiving the DCI determines the resource block set configuration for each resource block set included in the cell, carrier, or bandwidth portion based on the bitmap information. For example, if the value corresponding to the received bitmap information is 0, the UE can determine that RBset#0 is a downlink resource block set. Conversely, when the value corresponding to the received bitmap information is 1, the UE can determine that RBset#0 is an uplink resource block set.
[0332] According to embodiments of this disclosure, each bit of the bitmap can indicate to the UE one or more resource block sets in which downlink reception or uplink transmission is possible (or impossible). In other words, the base station can include a field in at least one DCI (e.g., a group public DCI publicly sent to multiple UE groups) received by the UE, wherein the field can inform or indicate information about resource block sets that are capable of (or incapable of) downlink reception or uplink transmission, and send it to the UE. The type of DCI used in this case is not limited to a group public DCI, and the information can also be sent via a cell public DCI or a UE-specific DCI.
[0333] A UE receiving DCI from a base station can determine whether the flexible resource block set is a resource block set that can (or cannot) perform downlink reception. Alternatively, the UE can determine whether the flexible resource block set is a resource block set that can (or cannot) perform uplink transmission.
[0334] The following is for reference. Figure 13A The example describes a method used by the UE to determine whether a flexible resource block set is a set of resource blocks capable (or incapable) of downlink reception for the downlink bandwidth portion. When the bitmap value included in the DCI received by the UE from the base station is 1 1 1, the UE can determine that RBset#0, RBset#1, and RBset#2 are all resource block sets capable of downlink reception. If the bitmap value received by the UE is 1 0 1, the UE can determine that RBset#0 and RBset#2 are resource block sets capable of downlink reception, but RBset#1 is a resource block set incapable of downlink reception.
[0335] The following is for reference. Figure 14A The example describes a method used by the UE to determine whether a flexible resource block set is a set of resource blocks capable (or incapable) of uplink transmission for the uplink bandwidth portion. When the bitmap value included in the DCI received by the UE from the base station is 1 1 1, the UE can determine that RBset#0, RBset#1, and RBset#2 are all resource block sets capable of uplink transmission. If the bitmap value received by the UE is 0 1 1, the UE can determine that RBset#0 and RBset#2 are resource block sets capable of uplink transmission, but RBset#0 is a resource block set incapable of uplink transmission.
[0336] Figure 16 This is a view illustrating a method for determining time-domain and frequency-domain uplink and downlink configurations by a UE configured with uplink and downlink configurations in the frequency domain (e.g., XDD-UL-DL-Configuration) and / or configured with uplink and downlink configurations in the time domain (e.g., TDD-UL-DL-Configuration) via higher-layer signals from a base station. Figure 16 Assuming the UE is configured as follows Figure 13A The set of downlink resource blocks shown, such as Figure 14A The uplink resource block set shown and as follows Figure 15 The set of flexible resource blocks shown.
[0337] The UE can determine the time-domain uplink and downlink configuration information using at least one of the time-domain uplink and downlink configuration information configured by the base station and the time slot format indicator received via DCI. Figure 16 This illustrates the case where, in the UE, time slots n, n+1, n+2, and n+3 are indicated as downlink time slots, downlink time slots, flexible time slots, and uplink time slots, respectively, representing time-domain uplink and downlink configuration information. For ease of description, although it is assumed that they are indicated as downlink time slots, flexible time slots, and uplink time slots in units of time slots, the same approach can be applied even if they are indicated as downlink symbols, flexible time slots, or uplink symbols in units of symbols within a time slot.
[0338] In slots n and n+1, which are indicated as downlink slots, the UE determines RBset#0, RBset#1, and RBset#2 as downlink resource block sets, flexible resource block sets, and downlink resource block sets, respectively, based on the block set configuration information of the frequency domain resources in the downlink bandwidth portion. As in method 2 above, by using the bitmap information in the DCI received from the base station, the UE can determine whether the resource block set identified as a flexible resource block set is a resource block set capable of (or unable to) perform downlink reception, or whether the resource block set identified as a flexible resource block set is a resource block set capable of (or unable to) perform uplink transmission. In this case, it can be determined whether the bitmap information is about the downlink bandwidth portion or the uplink bandwidth portion based on the indication of the slot format indicator or the uplink and downlink configuration in the time domain.
[0339] For example, when bitmap information is in Figure 16 When the time slot format indicator or the uplink and downlink configuration in the time domain, where time slot n and time slot n+1 are configured or indicated as downlink time slots, are 1 0 1, the UE can determine that RBset#0 and RBset#2 are downlink resource block sets or resource block sets capable of downlink reception within the resource block sets in the downlink bandwidth portion. Furthermore, the UE can determine that RBset#1 is an uplink resource block set or a resource block set incapable of downlink reception. Based on the determination result of the (multiple) resource block sets, the UE can perform or not perform downlink reception. In other words, the UE can choose not to perform downlink reception on RBset#1. In this case, RBset#0 and RBset#2 can be resource block sets configured as downlink resource block sets through different configurations, or can be determined as resource block sets capable of downlink reception regardless of the bitmap information, or can be considered as downlink resource block sets without a separate determination process.
[0340] When bitmap information is Figure 16 When the slot format indicator or the slot n+3 configured or indicated as a downlink slot in the uplink and downlink configuration in the time domain is 1 0 1, the UE can determine that RBset#0 and RBset#2 are uplink resource block sets or resource block sets capable of uplink transmission in the resource block set in the uplink bandwidth portion. In this case, RBset#1 may be a resource block set configured as an uplink resource block set through different configurations, determined as a resource block set capable of uplink transmission regardless of the bitmap information, or regarded as an uplink resource block set regardless of the individual determination process. Based on the determination result of the (multiple) resource block sets, the UE may or may not perform uplink reception.
[0341] When the UE is not configured with the type of the resource block set(s) of the flexible bandwidth portion, the UE can assume that the flexible bandwidth portion is a downlink bandwidth portion or an uplink bandwidth portion. In this case, the UE can determine whether one or more flexible resource block sets in the bandwidth portion are resource block sets capable of downlink reception or not (when assumed to be a downlink bandwidth portion), and the UE can determine whether the flexible resource block sets are resource block sets capable of uplink transmission or not (when assumed to be an uplink bandwidth portion). For example, based on... Figure 16 When the slot format indicator or the uplink and downlink configuration in the time domain configures or indicates slot n+2 as a flexible slot, the UE can determine whether the flexible resource block set is a set of resource blocks that can be received by downlink or a set of resource blocks that cannot be received by downlink by applying bitmap information (e.g., 10 1) and assuming the downlink bandwidth portion.
[0342] When a UE is configured with a set of (multiple) resource blocks in its flexible bandwidth portion, the UE can determine whether the set of (multiple) flexible resource blocks is capable of (or incapable of) downlink reception or capable of (or incapable of) uplink transmission by applying bitmap information to the flexible bandwidth portion. For example, the UE can determine that a bitmap value of 0 indicates a set of resource blocks capable of (or incapable of) downlink reception, and that a bitmap value of 0 indicates a set of resource blocks capable of (or incapable of) downlink reception. Figure 1 It is a set of resource blocks that can (or cannot) perform uplink transmission, and performs uplink transmission or downlink reception based on the determination result.
[0343] Bitmap information, whether it is a valid, persistent, or remaining range of slots or symbols, can be determined as follows.
[0344] The UE can determine whether the bitmap information is valid or persistent from the first (or last) symbol of the PDCCH in which the DCI containing bitmap information is transmitted, or from the first (or last) symbol of the control resource set in which the PDCCH is transmitted.
[0345] In one embodiment, the UE can determine whether the bitmap information is valid or persistent, depending on the time slot or symbol corresponding to one of the following.
[0346] The downlink slot or symbol is configured or indicated based on the slot format indicator or the uplink and downlink configuration in the time domain.
[0347] The slot or symbol immediately preceding the first uplink slot or symbol configured or indicated according to the slot format indicator or the uplink and downlink configuration in the time domain.
[0348] Downlink slots or symbols configured or indicated based on slot format indicators or uplink and downlink configurations in the time domain, as well as flexible slots or symbols.
[0349] The symbol immediately preceding the first symbol of the subsequent control resource set or subsequent PDCCH, which includes subsequent bitmap information, can be sent. Here, the subsequent PDCCH or subsequent control resource set can be sent periodically.
[0350] Other embodiments of resource block set configuration for indicating a flexible resource block set included in a cell, carrier, or bandwidth portion are described below.
[0351] In one embodiment, the base station may indicate or provide to the UE information regarding a Resource Block Set Format Indicator (RB Set Format Indicator (RFI)) or a Resource Block Set Format Indicator Mode via DCI. The Resource Block Set Format Indicator or Resource Block Set Format Indicator Mode indicates that, for a cell, carrier, or bandwidth portion, the flexible resource block set included in one of the cell, carrier, or bandwidth portions is at least one of a downlink resource block set, a flexible resource block set, or an uplink resource block set.
[0352] In the following description, for ease of description, the resource block set format indicator may be referred to as indicator information or indicator configuration information. In the following description of this disclosure, the indicator information is considered to be indicator information for a resource block set configured as a flexible resource block set via higher-layer signals, as described herein. As one embodiment, the indicator information can provide format indicator information for a resource block set configured as an uplink or downlink resource block set via higher-layer signals and a resource block set configured as a flexible resource block set. As one embodiment, a resource block set configured as an uplink or downlink resource block set via higher-layer signals cannot be indicated or changed to a downlink resource block set or an uplink resource block set by the indicator information. In other words, for a resource block set configured as an uplink or downlink resource block set via higher-layer signals, the indicator information can be indicated as an uplink or downlink resource block set.
[0353] Table 19 shows examples of indicator information for each of the N flexible resource block sets, indicating at least one of the downlink resource block set, flexible resource block set, or uplink resource block set. Here, for uplink or downlink cell, carrier, or bandwidth portion, N can be a maximum number of values representing the number of flexible resource block sets included in one of the uplink or downlink cell, carrier, or bandwidth portions. Furthermore, as described above, the DCI can be a DCI commonly associated with a group of UEs including at least one UE and / or a DCI associated with a specific UE. A UE receiving the indicator information for the flexible resource block set via the DCI (e.g., one of the RFI configurations in Table 19) can determine that, according to the indicated RFI configuration, each flexible resource block set is one of the downlink resource block set, flexible resource block set, or uplink resource block set.
[0354] [Table 19]
[0355] RFI Configuration First RB set Second RB set …… The Nth RB set 0 DL(UL) DL(UL) …… DL(UL) 1 X DL(UL) …… DL(UL) 2 DL(UL) X …… DL(UL) …… …… …… …… …… K-1 X X …… DL(UL) K X X …… X
[0356] In Table 19, the UE receiving the indicator information can determine the resource block set indicated as X as follows. In one embodiment, for a time slot indicated as a downlink time slot by the time slot format indicator, the UE can determine whether the resource block set indicated as X is a flexible resource block set or an uplink resource block set; and for a time slot indicated as an uplink time slot by the time slot format indicator, the UE can determine whether the resource block set indicated as X is a flexible resource block set or a downlink resource block set. In one embodiment, the UE can determine that the resource block set indicated as X is a flexible resource block set, regardless of the time slot format indicated by the time slot format indicator. In Table 19, K can be equal to or less than 2. N -1 (which is the number of cases required to provide indicator information for a set of N resource blocks). Furthermore, K can be equal to or less than 2. M -1 (which is the number of configurations that can be indicated by the size (M bits) of the field indicating indicator information in the DCI). As an example, the UE can be configured from the base station via higher-layer signals or receive at least one value of M or K from the base station.
[0357] In the embodiments described below, the base station can indicate, via a Resource Block Set Format Indicator (RFI) provided by the DCI, whether, for a cell, carrier, or bandwidth portion, a flexible resource block set included in one of the cell, carrier, or bandwidth portions is a resource block set capable of downlink reception or uplink transmission, or whether the flexible resource block set is a resource block set incapable of downlink reception or uplink transmission. Hereinafter, for ease of description, the resource block set format indicator may be referred to as indicator information or indicator configuration information.
[0358] Table 20 shows an example of indicator information that indicates whether each of the N flexible resource block sets is a set of resource blocks capable of downlink reception or uplink transmission, or a set of resource blocks incapable of downlink reception or uplink transmission.
[0359] [Table 20]
[0360]
[0361]
[0362] In Table 20, the UE receiving the indicator information can determine whether the indicated flexible resource block set is a set of resource blocks capable of downlink reception or uplink transmission, or a set of resource blocks incapable of downlink reception or uplink transmission.
[0363] In one embodiment, for a set of resource blocks indicated as available in a time slot designated as a downlink time slot by a time slot format indicator, the UE may receive downlink signals or channels in the indicated flexible resource block set, such as at least one of the PDCCH, CSI-RS, or SS / PBCH configured to be received in the flexible resource block set. For a set of resource blocks indicated as unavailable in a time slot designated as a downlink time slot by a time slot format indicator, the UE may not receive downlink signals or channels in the indicated flexible resource block set, such as at least one of the PDCCH, CSI-RS, or SS / PBCH configured to be received in the flexible resource block set. In one embodiment, when some resources of a configured downlink signal or channel (e.g., at least one PRB or at least one of RE, REG, or CCE) overlap with or are included in a set of resource blocks indicated as unavailable, the UE may not receive the entire downlink signal or channel. In one embodiment, the UE may not receive downlink signals or channels only in areas overlapping with a set of resource blocks that are indicated as unavailable.
[0364] In one embodiment, for a set of resource blocks indicated as available in a time slot designated as an uplink time slot by a time slot format indicator, the UE may transmit uplink signals or channels in the indicated flexible resource block set, such as at least one of PUCCH, PUSCH, SRS, or PRACH configured to be transmitted in the flexible resource block set. For a set of resource blocks indicated as unavailable in a time slot designated as an uplink time slot by a time slot format indicator, the UE may not transmit uplink signals or channels in the indicated flexible resource block set, such as at least one of PUCCH, PUSCH, SRS, or PRACH configured to be transmitted in the flexible resource block set. In one embodiment, when some resources (e.g., at least one PRB or at least one RE) of the configured uplink signals or channels overlap with or are included in the set of resource blocks indicated as unavailable, the UE may not transmit the entire uplink signal or channel. In one embodiment, the UE may not transmit uplink signals or channels only in areas overlapping with a set of resource blocks that are indicated as unavailable.
[0365] In Table 20, K can be equal to or less than 2. N -1 (which is the number of cases required to provide indicator information for a set of N resource blocks). Furthermore, K can be equal to or less than 2. M -1 (which is the amount of configuration information that can be indicated by the size (M bits) of the field indicating indicator information in the DCI). As an example, the UE can be configured from the base station via higher-layer signals or receive at least one value of M or K from the base station.
[0366] As an example, information regarding the set of resource blocks(s) indicated by each configuration (i.e., RFI configuration) in Tables 19 and 20 can be predefined between the base station and the UE, or provided to the UE via higher-level signals from the base station or configured for the UE.
[0367] For example, RFI configuration 2 in Table 19 can indicate that among the N resource block sets configured by the base station for the UE via higher-layer signals, the first resource block set is DL (or UL), the second resource block set is X, ..., and the Nth resource block set is DL (or UL). For example, RFI configuration 2 in Table 20 can indicate that among the N resource block sets configured by the base station for the UE via higher-layer signals, the first resource block set is capable of downlink reception or uplink transmission, the second resource block set is not capable of downlink reception or uplink transmission, ..., and the Nth resource block set is capable of downlink reception or uplink transmission.
[0368] This will be referenced below. Figure 16 The examples are described in more detail here. Figure 16 This is a view illustrating a method for determining time-domain and frequency-domain uplink and downlink configurations by a UE configured with uplink and downlink configurations in the frequency domain (e.g., XDD-UL-DL-Configuration) and / or configured with uplink and downlink configurations in the time domain (e.g., TDD-UL-DL-Configuration) via higher-layer signals from a base station. Figure 16 Assuming the UE is configured as follows Figure 13A The set of downlink resource blocks shown, such as Figure 14A The uplink resource block set shown and as follows Figure 15 The set of flexible resource blocks shown.
[0369] The UE can determine the time-domain uplink and downlink configuration information using at least one of the time-domain uplink and downlink configuration information configured by the base station and the time slot format indicator received via DCI. Figure 16 This illustrates the case where, in the UE, time slots n, n+1, n+2, and n+3 are indicated as downlink time slots, downlink time slots, flexible time slots, and uplink time slots, respectively, representing time-domain uplink and downlink configuration information. For ease of description, although it is assumed that they are indicated as downlink time slots, flexible time slots, and uplink time slots in units of time slots, the same approach can be applied even if they are indicated as downlink symbols, flexible time slots, or uplink symbols in units of symbols within a time slot.
[0370] The UE determines the resource block set configuration information based on the frequency domain resources used for the downlink bandwidth portion. In slot n and slot n+1, which are indicated as downlink slots, resource block set #0, resource block set #1 and resource block set #2 are the downlink resource block set, the flexible resource block set and the downlink resource block set, respectively.
[0371] As an example, as in Method 2 and Table 19 above, the UE can determine whether the resource block set identified as the flexible resource block set is the downlink resource block set, the uplink resource block set, or the flexible resource block set by using the indicator information in the DCI received from the base station.
[0372] As another example, as in Method 2 and Table 20 above, the UE can determine whether the resource block set identified as a flexible resource block set is a resource block set capable of (or incapable of) downlink reception, or whether the resource block set identified as a flexible resource block set is a resource block set capable of (or incapable of) uplink transmission, by using the indicator information in the DCI received from the base station.
[0373] In this case, it can be determined whether the indicator information applies to the downlink bandwidth portion or the uplink bandwidth portion based on the indication of the timeslot format indicator or the uplink and downlink configuration in the time domain. For example, when the indicator information is in Figure 16 When the time slot format indicator or the uplink and downlink configuration in the time domain is configured or indicated as a downlink time slot in time slot n and time slot n+1, indicating configuration 2 in Table 19, the UE can determine that the indicator information is applied to the downlink bandwidth portion, and that in the resource block set of the downlink bandwidth portion, resource block set #2 is a flexible resource block set or a resource block set that does not receive downlink signals or channels. In this case, resource block set #0 and resource block set #1 can be determined as downlink resource block sets.
[0374] As another example, when the indicator information is in Figure 16 When the time slot format indicator or the uplink and downlink configuration in the time domain is configured or indicated as a flexible time slot in time slot n+2, indicating configuration 1 in Table 19, if a flexible bandwidth portion is configured, the UE can determine that the indicator information is applied to the flexible bandwidth portion. If no flexible bandwidth portion is configured, the UE can determine that the indicator information is applied to the downlink bandwidth portion.
[0375] When the UE does not configure a flexible bandwidth portion, in time slot n+2, the UE can determine to apply indicator information to the downlink bandwidth portion of symbols configured to receive downlink signals or channels (e.g., PDCCH or CSI-RS reception) and to apply indicator information to the uplink bandwidth portion of symbols configured to transmit uplink signals or channels (e.g., at least one of SRS, PUCCH, PUSCH, or PRACH).
[0376] As one embodiment, the range of valid, persistent, or remaining time slots or symbols indicated by the indicator information can be determined as follows.
[0377] The UE can determine whether the indicator information is valid or persistent from the first (or last) symbol of the PDCCH in which the indicator information is transmitted by the DCI, or from the first (or last) symbol of the control resource set in which the PDCCH is transmitted.
[0378] The UE can determine whether the indicator information is valid or persistent based on the time slot or symbol corresponding to one of the following.
[0379] The downlink slot or symbol is configured or indicated based on the slot format indicator or the uplink and downlink configuration in the time domain.
[0380] The time slot or symbol immediately preceding the first uplink time slot or symbol configured or indicated according to the time slot format indicator or the uplink and downlink configuration in the time domain.
[0381] Downlink slots or symbols configured or indicated based on slot format indicators or uplink and downlink configurations in the time domain, as well as flexible slots or symbols.
[0382] The symbol immediately preceding the first symbol of the subsequent control resource set or subsequent PDCCH, which includes subsequent indicator information, can be sent by the DCI. Here, the subsequent PDCCH or subsequent control resource set can be sent periodically.
[0383] Figure 17 This is a flowchart illustrating frequency domain resources in a wireless communication system that are configured by the UE for uplink transmission or downlink reception.
[0384] The UE's controller identifies one or more guard bands (1710) configured in the frequency domain. The frequency domain is, for example, the cell bandwidth or a portion of the bandwidth configured in the UE. The one or more guard bands can be predefined or selected from multiple bands configured via higher-level signaling.
[0385] The UE's controller identifies one or more sets of resource blocks in a resource area outside of one or more guard bands within the bandwidth portion or cell bandwidth configured in the UE (1720). This operation can be performed using, for example, one or more guard bands. Alternatively, the resource block sets can be configured without configuring guard bands. In this case, the number of guard bands identified in step 1710 can be 0. The UE's controller can determine whether configuration information regarding the type of resource block sets has been received (1730).
[0386] According to embodiments of this disclosure, the configuration information can be provided periodically, and the UE can determine that the configuration information is valid until subsequent configuration information is provided.
[0387] When configuration information is received, the UE's controller determines the type of each resource block set based on the configuration information: a resource block set for downlink, a resource block set for uplink, or a flexible resource block set (or a resource block set for XDD) (1740). When no configuration information is received, the UE's controller determines the type of each resource block set based on whether the bandwidth or bandwidth portion is used for uplink transmission or downlink reception (1750). In this case, for a time range that is downlink bandwidth or a portion of downlink bandwidth, the controller may determine that one or more resource block sets are all downlink resource block sets; for a time range that is uplink bandwidth or a portion of uplink bandwidth, it may determine that one or more resource block sets are all uplink resource block sets; and for other cases, it may determine that one or more resource block sets are flexible resource block sets.
[0388] The UE's controller can use predefined resource block set pattern information to determine specific frequency regions for one or more resource block sets and one or more guard bands. In this case, one or more guard bands and resource block set patterns can be defined based on subcarrier spacing and bandwidth or bandwidth portion size.
[0389] The UE's controller can receive downlink control information (DCI) from the base station via the communication unit. The UE's controller can determine whether a set of resource blocks designated as a flexible resource block set should be used for downlink reception or uplink transmission based on channels or signals scheduled by the DCI and located within that set. Channels or signals may include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Aperiodic Channel State Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), or Physical Random Access Channel (PRACH).
[0390] The UE's controller can determine whether the set of flexible resource blocks scheduled in the DCI is a downlink resource block set or an uplink resource block set based on an indicator included in the DCI. This indicator can be a bitmap of the same size as the number of flexible resource blocks scheduled in the DCI.
[0391] If the set of flexible resource blocks scheduled in the DCI is included in the downlink bandwidth portion, the UE's controller can determine whether downlink reception is possible within the flexible block set based on indicators included in the DCI. Alternatively, if the set of flexible resource blocks scheduled in the DCI is included in the uplink bandwidth portion, the controller can determine whether uplink reception is possible within the flexible resource block set based on indicators included in the DCI. The UE's controller can then perform downlink reception or uplink transmission based on the determination result.
[0392] Figure 18 This is a flowchart illustrating frequency domain resources in a wireless communication system that are configured by a base station for uplink reception or downlink transmission.
[0393] The base station controller configures one or more guard bands in the frequency domain for the UE (1810). The frequency domain is, for example, the cell bandwidth or a portion of the bandwidth configured in the UE. The one or more guard bands can be selected from a plurality of predetermined frequency bands. Alternatively, a set of resource blocks can be configured without configuring guard bands. In this case, the number of guard bands identified in step 1810 can be 0.
[0394] The base station controller configures one or more sets of resource blocks in a resource area outside of one or more guard bands within the bandwidth portion configured in the UE or the cell bandwidth (1820). This operation can be performed using, for example, one or more guard bands. The base station controller can control the communication unit to provide the UE with configuration information about the type of resource block set (1830).
[0395] Configuration information may include information used to determine whether each resource block set is a downlink resource block set, an uplink resource block set, or a flexible resource block set. Configuration information may be provided to the UE periodically or non-periodically. This configuration information may be considered valid until subsequent configuration information is provided.
[0396] The protection band can be predefined or selected from multiple bands configured via higher-level signaling.
[0397] The base station can send downlink control information (DCI) to the UE via a communication unit. In this case, based on the channel or signal scheduled in the DCI, it can be determined whether the resource block set identified as a flexible resource block set is used for downlink reception or uplink transmission. The channel or signal may include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Aperiodic CSI-RS, SRS, or Physical Random Access Channel (PRACH). Alternatively, the DCI may include an indicator for determining whether the flexible resource block set scheduled in the DCI is a downlink resource block set or an uplink resource block set.
[0398] The methods described in the embodiments of this disclosure or the claims can be implemented in hardware, software, or a combination of hardware and software.
[0399] When implemented in software, a computer-readable storage medium or computer program product storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium or computer program product 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.
[0400] The program (software module or software) can be stored in random access memory, including non-volatile memory such as flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM, digital versatile disc (DVD), or other types of optical storage devices or magnetic tape. Alternatively, the program can be stored in a memory consisting of all or some of these components. Multiple memories may be included as each component memory.
[0401] 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.
[0402] In this disclosure, the terms "computer program product" or "computer-readable medium" are used collectively to refer to media, such as memory, hard disks mounted in hard disk drives, and signals. "Computer program product" or "computer-readable medium" can be used for frequency resource allocation in wireless communication systems according to this disclosure.
[0403] In the specific embodiments described above, depending on the proposed specific embodiments, the components included in this disclosure are represented in a singular or plural form. However, the singular or plural form is chosen to suit the context suggested for ease of description, and this disclosure is not limited to singular or plural components. As used herein, the singular forms "a," "an," and "the" are also intended to include the plural forms unless the context clearly indicates otherwise.
[0404] The embodiments provided herein are merely illustrative of the invention and should not be construed as limiting the invention. In other words, it will be apparent to those skilled in the art that various modifications can be made without departing from the scope of the invention. Furthermore, these embodiments can be implemented in combination. For example, the base station and the UE can operate in a combination of portions of one embodiment and another. The embodiments of this disclosure can be applied to other communication systems and can be modified in various ways based on the technical spirit of the embodiments of this disclosure. For example, the embodiments of this disclosure can also be applied to LTE systems, 5G, or NR systems.< / xdd> < / coreset> < / dci> < / bwp>
Claims
1. A method in a wireless communication system for configuring frequency domain resources for uplink transmission or downlink reception, performed by a user equipment (UE), the method comprising: Identify the guard band configured in the cell's bandwidth or the bandwidth portion configured for the UE; Identify one or more sets of resource blocks in the bandwidth or a resource region outside the guard band within the bandwidth portion; Identify whether configuration information about the type of the resource block set has been received; Upon receiving the configuration information, the type of each resource block set is determined based on the configuration information: downlink resource block set, uplink resource block set, or flexible resource block set. as well as In the absence of the configuration information, based on whether the bandwidth or a portion of the bandwidth is used for uplink transmission or downlink reception, determine the type of each resource block set as a downlink resource block set, an uplink resource block set, or a flexible resource block set.
2. The method according to claim 1, wherein, The one or more resource block sets are identified using the guard band, wherein the guard band is predefined or selected from multiple bands configured via higher-level signaling.
3. The method according to claim 1, further comprising: The guard band and the frequency region of the one or more resource block sets are determined using predefined resource block set pattern information, wherein the guard band and the resource block set pattern information are defined based on the subcarrier spacing and the size of the bandwidth or the size of the bandwidth portion.
4. The method according to claim 1, further comprising: Without receiving the configuration information, it is determined that for a time range that is downlink bandwidth or a portion of downlink bandwidth, all of the one or more resource block sets are downlink resource block sets, and for a time range that is uplink bandwidth or a portion of uplink bandwidth, all of the one or more resource block sets are uplink resource block sets.
5. The method according to claim 1, further comprising: Receive downlink control information (DCI); as well as Based on the channel or signal scheduled by DCI, within the set of resource blocks identified as flexible resource blocks, it is determined whether the set of resource blocks to be used for downlink reception or uplink transmission is to be used. The channels or signals include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Aperiodic Channel State Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), or Physical Random Access Channel (PRACH).
6. The method according to claim 1, further comprising: Receive DCI; as well as Based on the indicators included in the DCI, it is determined whether the set of flexible resource blocks scheduled in the DCI is a set of downlink resource blocks or a set of uplink resource blocks. The indicator includes a bitmap of the same size as the number of flexible resource block sets scheduled in the DCI, or indicator information indicating that each flexible resource block set in at least one of the uplink or downlink cell, carrier, or bandwidth portion is one of the downlink resource block set, flexible resource block set, or uplink resource block set.
7. The method according to claim 1, further comprising: Receive DCI; When the set of flexible resource blocks scheduled in the DCI is included in the downlink bandwidth portion, it is determined whether downlink reception in the set of flexible resource blocks is possible based on the indicator included in the DCI. as well as When the set of flexible resource blocks scheduled in the DCI is included in the uplink bandwidth portion, it is determined whether uplink transmission in the set of flexible resource blocks is possible based on the indicators included in the DCI.
8. A method in a wireless communication system for configuring frequency domain resources for uplink reception or downlink transmission, performed by a base station, the method comprising: Configure the user equipment (UE) with information indicating the bandwidth of the cell or the guard band in the bandwidth portion configured for the UE; Configure the UE with information indicating one or more sets of resource blocks in a resource region outside the guard band of the bandwidth; Determine whether to send configuration information about the type of the resource block set; as well as If the configuration information is determined to be sent, configuration information about the type of resource block set is provided to the UE. This configuration information includes information for determining whether each resource block set is a downlink resource block set, an uplink resource block set, or a flexible resource block set. In the case where it is determined not to send the configuration information, the type of each resource block set, whether it is a downlink resource block set, an uplink resource block set, or a flexible resource block set, is determined based on whether the bandwidth or a portion of the bandwidth is used for uplink reception or downlink transmission.
9. The method according to claim 8, wherein, The protection band is predefined or selected from multiple bands configured via higher-level signaling.
10. The method of claim 8, further comprising: Send downlink control information (DCI) to the UE. Specifically, based on the channel or signal scheduled by DCI, it is determined whether the set of resource blocks identified as a flexible resource block set should be used for downlink transmission or uplink reception, and The channels or signals include one or more of the following: Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Aperiodic Channel State Information Reference Signal (CSI-RS), Sounding Reference Signal (SRS), or Physical Random Access Channel (PRACH).
11. The method of claim 8, further comprising: Send DCI to the UE, The DCI includes an indicator for determining whether the set of flexible resource blocks scheduled in the DCI is a set of downlink resource blocks or a set of uplink resource blocks, and The indicator includes a bitmap of the same size as the number of flexible resource block sets scheduled in the DCI, or indicator information indicating that each flexible resource block set in at least one of the uplink or downlink cell, carrier, or bandwidth portions is one of the downlink resource block set, flexible resource block set, or uplink resource block set.
12. A user equipment (UE) in a wireless communication system for configuring frequency domain resources for uplink transmission or downlink reception, comprising: Communication unit; and A controller, wherein the controller is configured to perform the method as described in any one of claims 1-7.
13. A base station in a wireless communication system for configuring frequency domain resources for uplink reception or downlink transmission, comprising: Communication unit; and A controller, wherein the controller is configured to perform the method as described in any one of claims 8-11.