Patent Application
20240267919
This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2023-0002108, filed on Jan. 6, 2023, in the Korean Intellectual Property Office, the disclosure of which is incorporated herein by reference in its entirety.
The disclosure relates generally to a wireless communication system, and more particularly, to a method of performing data channel transmission or reception with a user equipment (UE) that supports full-duplex communication in a wireless communication system.
Fifth generation (5G) mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in sub 6 gigahertz (GHz) bands such as 3.5 GHz, but also in above 6 GHz bands referred to as millimeter wave (mmWave) bands including 28 GHz and 39 GHz. In addition, it has been considered to implement sixth generation (6G) mobile communication technologies (referred to as beyond 5G systems) in terahertz (THz) bands (for example, 95 GHz to 3 THz bands) to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.
When the development of 5G mobile communication technologies began, to support services and to satisfy performance requirements in connection with enhanced mobile broadband (eMBB), ultra reliable low latency communications (URLLC), and massive machine-type communications (mMTC), there has been ongoing standardization regarding beamforming and massive multi-input multi-output (MIMO) for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (e.g., operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of a bandwidth part (BWP), new channel coding methods such as a low density parity check (LDPC) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.
Discussions persist regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as vehicle-to-everything (V2X) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, new radio unlicensed (NR-U) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.
There is also ongoing standardization in air interface architecture/protocol regarding technologies such as industrial Internet of things (IIoT) for supporting new services through interworking and convergence with other industries, integrated access and backhaul (IAB) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and dual active protocol stack (DAPS) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There is also ongoing standardization in system architecture/service regarding a 5G service based architecture or service based interface for combining network functions virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.
As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks. Thus, it is anticipated that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with extended reality (XR) for efficiently supporting augmented reality (AR), virtual reality (VR), mixed reality (MR) and the like, 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
Such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in THz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as full dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of THz band signals, high-dimensional space multiplexing technology using orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
A wireless communication system is advancing to a broadband wireless communication system for providing high-speed and high-quality packet data services using communication standards, such as high-speed packet access (HSPA) of 3GPP, LTE {long-term evolution or evolved universal terrestrial radio access (E-UTRA)}, LTE-advanced (LTE-A), LTE-pro, high-rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), IEEE 802.16e, and the like, as well as typical voice-based services.
As an example, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in the DL and employs a single carrier frequency division multiple access (SC-FDMA) scheme in a UL, which indicates a radio link through which a UE (or transmits data or control signals to a BS (eNode B), and the DL indicates a radio link through which the BS transmits data or control signals to the UE. The above multiple access scheme may separate data or control information of respective users by allocating and operating time-frequency resources for transmitting the data or control information for each user so as to avoid overlapping each other and to establish orthogonality.
Since a 5G communication system, which is a post-LTE communication system, must freely reflect various requirements of users, service providers, and the like, services satisfying various requirements must be supported. The services considered in the 5G communication system include eMBB communication, mMTC, URLLC, etc.
The eMBB aims at providing a data rate higher than that supported by existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, eMBB must provide a peak data rate of 20 Gbps in the DL and a peak data rate of 10 Gbps in the UL for a single BS. Furthermore, the 5G communication system must provide an increased user-perceived data rate to the UE, as well as the maximum data rate. To satisfy such requirements, transmission/reception technologies including a further enhanced MIMO transmission technique are required to be improved. In addition, the data rate required for the 5G communication system may be obtained using a frequency bandwidth more than 20 MHz in a frequency band of 3 to 6 GHz or 6 GHz or more, instead of transmitting signals using a transmission bandwidth up to 20 MHz in a band of 2 GHz used in LTE.
In addition, mMTC is being considered to support application services such as the Internet of Things (IOT) in the 5G communication system. mMTC has requirements, such as support of connection of a large number of UEs in a cell, enhancement coverage of UEs, improved battery time, a reduction in the cost of a UE, and the like, to effectively provide the IoT. Since the IoT provides communication functions while being provided to various sensors and various devices, it must support many UEs (e.g., 1,000,000 UEs/km2) in a cell. In addition, the UEs supporting mMTC may require wider coverage than those of other services provided by the 5G communication system because the UEs are likely to be located in a shadow area, such as a basement of a building, which is not covered by the cell due to the nature of the service. The UE supporting mMTC must be configured to be inexpensive, and may require a very long battery life-time such as 10 to 15 years because it is difficult to frequently replace the battery of the UE.
The URLLC, which is a cellular-based mission-critical wireless communication service, may be used for remote control for robots or machines, industrial automation, unmanned aerial vehicles, remote health care, emergency alert, and the like. Thus, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds (ms), and also requires a packet error rate of 10-5 or less. Therefore, for the services supporting URLLC, a 5G system must provide a transmit time interval (TTI) shorter than those of other services, and also may require a design for assigning a large number of resources in a frequency band to secure reliability of a communication link.
The three 5G services, that is, eMBB, URLLC, and mMTC, may be multiplexed and transmitted in a single system. To satisfy different requirements of the respective services, different transmission/reception techniques and transmission/reception parameters may be used between the services.
In the conventional art, however, scheduling in the wireless communication system is deficient. For example, when a frequency resource for uplink subband is scheduled in PDSCH, processing PDSCH might be inefficient.
As such, there is a need in the art for an improved PDSCH scheduling method in a wireless communication system.
The disclosure has been made to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below.
Accordingly, an aspect of the disclosure is to provide a method and apparatus for smoothly performing subband non-overlapping full duplex (SBFD)-based communication.
An aspect of the disclosure is to provide Disclosed herein is a method of determining a precoding resource block group (PRG) grid in consideration of an uplink (UL) subband configuration, a method of determining the size of a scheduled physical resource block (PRB), a method of interpreting downlink (DL) and UL BWPs, and a method of determining consecutive DL BWPs.
An aspect of the disclosure is to provide a method of managing a PRB in an SBFD-based communication and a method and apparatus for transmitting or receiving a reference signal (RS) in a wireless communication system.
In accordance with an aspect of the disclosure, there is provided a physical DL shared channel (PDSCH) scheduling method in a wireless communication system, including interpreting scheduling information with reference to information associated with a UL subband when a UE receives a PDSCH from a base station (BS). The interpretation method may be a method of interpreting the size of a scheduled PRB and a BWP size, which are appropriate for full-duplex communication. An embodiment may include a method of determining a PRG grid and a PRB bundling size, which are appropriate for full-duplex communication, when a UE receives a PDSCH from a BS.
In accordance with an aspect of the disclosure, a method includes receiving, from a BS, a first control signal; processing the received first control signal; transmitting, to the BS, a second control signal generated based on the processing.
The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.
Descriptions related to technical contents well-known in the art and not associated directly with the disclosure will be omitted for the sake of clarity and conciseness.
For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted, or schematically illustrated. The size of each element does not completely reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals.
The advantages and features of the disclosure and ways to achieve them will be apparent by making reference to embodiments as described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments set forth below, but may be implemented in various different forms. The following embodiments are provided only to completely disclose the disclosure and inform those skilled in the art of the scope of the disclosure. Throughout the specification, the same or like reference numerals designate the same or like elements. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification.
Herein, a BS is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a wireless access unit, a BS controller, and a node on a network. A terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Herein, the DL refers to a radio link via which a BS transmits a signal to a terminal, and a UL refers to a radio link via which a terminal transmits a signal to a BS. LTE or LTE-A systems may be described by way of example, but the embodiments of the disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include 5th generation mobile communication technologies (5G, new radio (NR), etc.) developed beyond LTE-A, and 5G covers the exiting LTE, LTE-A, or other similar services. Based on determinations by those skilled in the art, embodiments herein may also be applied to other communication systems through some modifications without significantly departing from the scope of the disclosure.
A unit herein refers to a software element or a hardware element, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), which performs a predetermined function. However, the unit does not always have a meaning limited to software or hardware. The unit may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the unit includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the unit may be either combined into a smaller number of elements, or a unit, or divided into a larger number of elements, or a unit. Moreover, the elements and units may be implemented to reproduce one or more CPUs within a device or a security multimedia card, and the unit may include one or more processors.
In the following description, terms for identifying access nodes and for referring to network entities, messages, interfaces between network entities, various identification information, and the like are illustratively used for the sake of descriptive convenience. Therefore, the disclosure is not limited by the terms as used below, and other terms referring to subjects having equivalent technical meanings may be used.
In the following description, terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standards or NR standards will be used for the sake of descriptive convenience. However, the disclosure is not limited by these terms and names, and may be applied in the same manner to systems that conform other standards.
Herein, a BS allocates resources to terminals, and may be at least one of a radio access network (RAN) node, a next generation node B (gNode B, gNB), an evolved node B (eNode B, eNB), a Node B, a wireless access unit, a BS controller, and a node on a network. In the disclosure, the term eNB may be interchangeably used with the term gNB. That is, a BS described as eNB may indicate gNB.
In the following description, a terminal may include a UE, a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Of course, examples of the BS and the terminal are not limited thereto.
In particular, the disclosure may be applied to 3GPP NR (5th generation mobile communication standard) and to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety-related services, etc.) on the basis of 5G communication technology and IoT-related technology. A terminal may refer to mobile phones, NB-IOT devices, sensors, and other wireless communication devices.
A method herein may include performing scheduling with reference to information associated with a UL subband when a BS configures PDSCH frequency resource information for a UE, an RB bundling method in consideration of a UL subband when the BS configures the PDSCH frequency resource information for the UE, a method of performing physical RB mapping in a virtual RB when the BS configures the PDSCH frequency resource information for the UE, and a method that does not consider information associated with a UL subband and a method that considers information associated with a UL subband.
Referring to
Referring to
The information is not limited to the above-described example, and various parameters related to a BWP in addition to the configuration information may be configured for a UE. The information may be transferred by a BS to a UE via higher layer signaling, e.g., radio resource control (RRC) signaling. At least one BWP among the configured one or multiple BWPs may be activated. Whether a configured BWP is activated may be transferred from a BS to a UE semi-statistically via RRC signaling, or dynamically via DL control information (DCI).
Prior to having a connection to an RRC, a UE may receive a configuration of an initial BWP for initial access from a BS via a master information block (MIB). More specifically, via the MIB at the initial access stage, the UE may receive configuration information associated with a search space and a control area (e.g., a control resource set (CORESET)) in which a physical DL control channel (PDCCH) is transmitted, to receive system information (e.g., remaining system information (RMSI) or system information block 1 (SIB1)) needed for initial access. The control area and the search space configured via the MIB may be regarded as an identity (ID) of 0, respectively. The BS may inform the UE of the configuration information, such as frequency allocation information, time allocation information, numerology, or the like, in association with control area #0, via the MIB. In addition, the BS may inform the UE of configuration information associated with a monitoring cycle and occasion with respect to control area #0, that is, configuration information for search space #0, via the MIB. The UE may consider, as an initial BWP for initial access, a frequency domain configured as control area #0 obtained from the MIB. In this instance, the identity (ID) of the initial BWP may be considered as 0.
A BWP configuration supported in 5G may be used for various purposes.
According to some embodiments, when a bandwidth supported by a UE is less than a system bandwidth, the BWP configuration may be used for backup. For example, a BS configures, for a UE, the frequency location of a BWP (configuration information 2) so that the UE is capable of transmitting or receiving data at a predetermined frequency location in the system bandwidth.
To support different numerologies, a BS may configure multiple BWPs for a UE. For example, to support data transmission or reception using both a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz for a UE, the two BWPs may be configured to have a subcarrier spacing of 15 kHz and a subcarrier spacing of 30 kHz, respectively. The different BWPs may be frequency division multiplexed (frequency division multiplexing), and when data transmission or reception based on a predetermined subcarrier spacing is needed, a BWP configured to have the corresponding subcarrier spacing may be activated.
A BS may configure BWPs having different bandwidths for a UE to reduce power consumption of the UE. For example, when the UE supports a bandwidth of 100 MHz, and always transmits or receives data using the corresponding bandwidth, a significantly large amount of power may be consumed. Particularly, when there is no traffic, monitoring an unnecessary DL control channel in a large bandwidth of 100 MHz may be inefficient from the perspective of power consumption. Accordingly, to reduce the power consumption of the UE, the BS may configure a BWP that is a relatively smaller bandwidth, for example, a BWP of 20 MHz, for the UE. When there is no traffic, the UE may perform monitoring in a BWP of 20 MHz, and when data is produced, the UE may transmit or receive the data in a BWP of 100 MHz according to an instruction form the BS.
In a method of configuring a BWP, UEs before being connected to an RRC may receive configuration information associated with an initial BWP via an MIB in the initial access stage. More specifically, the UE may receive, from the MIB of a physical broadcast channel (PBCH), a configuration of a control area for a DL control channel in which DCI that schedules a system information block (SIB) may be transmitted. The bandwidth of a control area configured via the MIB may be regarded as an initial BWP, and the UE may receive, via the configured initial BWP, a physical DL shared channel (PDSCH) that transmits an SIB. In addition to the purpose of receiving the SIB, the initial BWP may be utilized for other system information (OSI), paging, or random access.
When one or more BWPs are configured for a UE, a BS may indicate, to the UE, changing (or switching or shifting) of a BWP by using a BWP indicator field in DCI. For example, in
As described above, DCI-based BWP switching may be indicated by DCI that schedules a PDSCH or PUSCH, and thus, when a UE receives a BWP switch request, the UE may need to smoothly receive or transmit a PDSCH or PUSCH scheduled by the corresponding DCI in the switched BWP. To this end, the standard has defined requirements associated with a delay time (TBWP) required for BWP switching, and for example, the requirements may be defined as shown below in Table 3.
Note 1:
The requirements associated with a BWP delay time may support type 1 or type 2 depending on the capability of a UE. A UE may report a supportable BWP delay time type to a BS.
According to requirements for the BWP switch delay time, when the UE receives DCI including a BWP switch indicator in slot n, the UE may complete switching to a new BWP indicated by the BWP switch indicator at a point in time not later than slot n+TBWP, and may perform transmission or reception of a data channel that the corresponding DCI schedules in the new switched BWP. When a BS desires to schedule a data channel in a new BWP, the BS may determine time-domain resource allocation with respect to a data channel in consideration of a BWP switch delay time (TBWP) of a UE. That is, in the method in which s BS determines time-domain resource allocation with respect to a data channel when scheduling a data channel in a new data BWP, the corresponding data channel may be scheduled to be after the BWP switch delay time. Accordingly, the UE may not expect that the DCI indicating switching of a BWP indicates a slot offset (K0 or K2) value less than a TBWP.
When a UE receives DCI (e.g., DCI format 1_1 or 0_1) indicating switching of a BWP, the UE may not perform any transmission or reception during a time interval from a third symbol of a slot in which a PDCCH including the corresponding DCI is received to the start point of a slot indicated by a slot offset (K0 or K2) value indicated by a time-domain resource allocation indicator field in the corresponding DCI. For example, when a UE receives DCI indicating switching of a BWP in slot n and a slot offset value indicated by the corresponding DCI is K, the UE may not perform any transmission or reception from the third symbol of slot n to a symbol before slot n+K (i.e., the last symbol of slot n+K−1).
A synchronization signal (SS)/PBCH block may be a physical layer channel block including a primary SS (PSS), a secondary SS (SSS), and a PBCH. Specifically, elements included in an SS/PBCH block (or SSB) may be defined as below.
PSS is an RS for DL time/frequency synchronization, which provides part of information of a cell ID.
SSS acts as a reference for DL time/frequency synchronization, and provides the remaining cell ID information that the PSS does not provide. In addition, the SSS may act as an RS for demodulating a PBCH.
PBCH provides essential system information needed for a UE to perform data channel and control channel transmission or reception. The essential system information may include search space-related control information indicating radio resource mapping information of a control channel, scheduling control information associated with a separate data channel that transmits system information, and the like.
SS/PBCH block includes a combination of a PSS, an SSS, and a PBCH. A single SS/PBCH block or multiple SS/PBCH blocks may be transmitted within 5 ms, and each transmitted SS/PBCH block may be identified based on an index.
At the initial access stage, a UE may detect a PSS and an SSS, and may decode a PBCH. The UE may obtain an MIB from the PBCH, whereby CORESET #0 (corresponding to a control area having a control area index of 0) may be configured. The UE may assume that a selected SS/PBCH block and a demodulation RS (DMRS) transmitted in control area #0 are in a quasi co location (QCL) and may monitor control area #0. The UE may receive system information via DCI transmitted in control area #0. From the received system information, the UE may obtain random access channel (RACH)-related configuration information needed for initial access. The UE may transmit a physical RACH (PRACH) to a BS in consideration of the selected SS/PBCH index, and the BS that receives the PRACH may obtain information associated with the index of the SS/PBCH block that the UE selects. The BS may recognize a block that the UE selects among SS/PBCH blocks and the fact that the UE monitors control area #0 related to the selected block.
In the 5G system, scheduling information for a physical UL shared channel (PUSCH) or a physical DL shared channel (PDSCH) may be included in DCI and transferred from a BS to a UE. A UE may monitor (monitoring) a DCI format for fallback and a DCI format for non-fallback in association with a PUSCH or PDSCH. The fallback DCI format may be configured as a fixed field previously defined between a BS and a UE, and the non-fall back DCI format may include a field that is capable of being configured.
DCI may go through a channel-coding and modulating process, and may be transmitted in a PDCCH which is a DL physical control channel. A cyclic redundancy check (CRC) is added to a DCI message payload, and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to a UE identity. Different RNTIs may be used depending on the purpose of the DCI message, e.g., UE-specific data transmission, power control command, random access response (RAR), etc. That is, an RNTI is not explicitly transmitted, but is transmitted by being included in a CRC calculation process. When a UE receives a DCI message transmitted in a PDCCH, the UE may identify a CRC by using an allocated RNTI and may recognize that the corresponding message is transmitted for the UE in case a CRC identification result is right.
For example, DCI that schedules a PDSCH associated with system information (SI) may be scrambled by an SI-RNTI. DCI that schedules a PDSCH associated with an RAR message may be scrambled by an RA-RNTI. DCI that schedules a PDSCH associated with a paging message may be scrambled by a P-RNTI. A DCI that reports a slot format indicator (SFI) may be scrambled by an SFI-RNTI. DCI that reports a transmit power control (TPC) may be scrambled by a TPC-RNTI. DCI that schedules a UE-specific PDSCH or PUSCH may be scrambled by a cell RNTI (C-RNTI).
DCI format 0_0 may be used as a fallback DCI that schedules a PUSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 0_0 with a CRC, scrambled by a C-RNTI, may include, for example, the information shown below in Table 4.
DCI format 0_1 may be used as a non-fallback DCI that schedules a PUSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 0_1 with a CRC, scrambled by a C-RNTI, may include, for example, the information shown below in Table 5.
DCI format 1_0 may be used as a fallback DCI that schedules a PDSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 1_0 with a CRC, scrambled by a C-RNTI, may include, for example, the information shown below in Table 6.
DCI format 1_1 may be used as a non-fallback DCI that schedules a PDSCH. In this instance, a CRC may be scrambled by a C-RNTI. DCI format 1_1 with a CRC, scrambled by a C-RNTI, may include, for example, the information shown below in Table 7.
The above-described control area in 5G may be configured by a BS for a UE via higher layer signaling (e.g., system information, an MIB, RRC signaling). Configuring a control area for a UE may be providing information associated with the identity of the control area, the frequency location of the control area, the length of symbols of the control area, and the like. For example, pieces of information of Table 8 as shown below may be included.
In Table 8, tci-StatesPDCCH (or a transmission configuration indication (TCI) state) configuration information may include information associated with one or multiple SS)/PBCH blocks indices that are in QCL relationship with a DMRS transmitted in a corresponding control area or information associated with a channel state information RS (CSI-RS) index.
As illustrated in
The basic unit of a DL control channel of
A search space may be classified as a common search space and a UE-specific search space. A group of UEs or all UEs may investigate the common search space of a PDCCH to receive cell-common control information such as a dynamic scheduling or paging message associated with system information. For example, PDSCH scheduling allocation information for transmitting an SIB including operator information of a cell and the like may be received via investigation of the common search space for a PDCCH. The common search space may be defined as a set of predetermined CCEs since a group of UEs or all UEs may need to receive a PDCCH. Scheduling allocation information for a UE-specific PDSCH or a PUSCH may be received via investigation of a UE-specific search space for a PDCCH. The UE-specific search space may be defined to be specific to a UE by using an identity of the UE and a function with various system parameters.
In 5G, a parameter for the search space of a PDCCH may be configured for a UE by a BS via higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, a BS may configure, for a UE, the number of candidate PDCCHs at each aggregation level L, a monitoring cycle for a search space, search space monitoring occasion in units of symbols in a slot, a search space type (e.g., a common search space or UE-specific search space), a DCI format and RNTI combination desired to be monitored in the corresponding search space, the index of a control area in which a search space is desired to be monitored, and the like. For example, pieces of information of Table 9 shown below may be included.
According to the configuration information, a BS may configure, for a UE, a single search space set or multiple search space sets. A BS may configure search space set 1 and search space set 2 for a UE, may perform configuration so that the UE monitors DCI format A scrambled by X-RNTI in search space set 1 in a common search space, and may perform configuration so that the UE monitors DCI format B scrambled by Y-RNTI in search space set 2 in a UE-specific search space.
According to configuration information, a single search space set or multiple search space sets may be present in the common search space or UE-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as a UE-specific search space.
In a common search space, the following combinations of a DCI format and an RNTI may be monitored. However, this is not limited to the following example.
In a UE-specific search space, the following combinations of a DCI format and an RNTI may be monitored.
The RNTIs specified below may comply with the following definitions and use.
TPC for SRS RNTI (TPC-SRS-RNTI): for commanding power control for an SRS The above-described DCI formats may comply with the definitions shown below in Table 10.
In 5G, a search space at aggregation level L in search space set s and control area p may be expressed as given in Equation (1) below.
In Equation (1),
In a common search space, Yp,n
Yp,n
In 5G, multiple search space sets may be configured with different parameters in Table 9, and thus a set of search space sets that a UE monitors for each point in time may be different. For example, when search space set #1 is configured based on a X-slot cycle, search space set #2 is configured based on a Y-slot cycle, and X and Y are different, a UE may monitor both search space set #1 and search space set #2 in a predetermined slot, and may monitor one of search space set #1 and search space #2 in a predetermined slot.
When multiple search space sets are configured for a UE, a method of determining a search space set to be monitored by the UE may be performed in consideration of the following conditions.
When the UE is configured with r15monitoringcapability as the value of monitoringCapabilityConfig-r16 that is higher layer signaling, the UE may define the maximum value of the number of candidate PDCCUs that the UE is capable of monitoring and the maximum value of the number of CCEs included in the entire search space, which corresponds to the union area of multiple search space sets, for each slot. When the UE is configured with r16monitoringcapability as the value of monitoringCapabilityConfig-r16, the UE may define the maximum value of the number of candidate PDCCUs that the UE is capable of monitoring and the maximum value of the number of CCEs included in the entire search space for each span.
According to a configuration value of higher layer signaling as described above, when the maximum number M{circumflex over ( )}μ of candidate PDCCHs that the UE is capable of monitoring is defined based on a slot in a cell in which a subcarrier spacing of 15*2{circumflex over ( )}μ kHz is configured, the maximum number may comply with Table 11 shown below, and when the maximum number is defined based on a span, the maximum number may comply with Table 12 shown below.
According to a configuration value of higher layer signaling as described above, when the maximum number Cμ of CCEs included in the entire search space is defined based on a slot in a cell in which a subcarrier spacing of 15*2{circumflex over ( )}μ kHz is configured, the maximum number may comply with Table 13 shown below, and when the maximum number is defined based on a span, the maximum number may comply with Table 14 shown below.
For ease of description, a situation that satisfies both conditions 1 and 2 at a predetermined point in time is defined as “condition A”. Therefore, the fact that condition A is not satisfied implies that at least one of condition 1 and condition 2 is not satisfied.
When time and frequency resource A in which symbol sequence A is desired to be transmitted overlaps time and frequency resource B, rate matching or puncturing may be considered as an operation for transmitting or receiving channel A in consideration of resource C of an area where resource A and resource B overlap. A detailed operation is as follows.
A BS may map channel A to only a resource area remaining after excluding resource C corresponding to an area that overlaps with the resource B from the entire resource A in which symbol sequence A is desired to be transmitted, and may transmit the same to a UE. For example, when symbol sequence A is configured with {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4} and resource B is {resource #3, resource #5}, a BS sequentially map symbol sequence A to the resource {resource #1, resource #2, resource #4} remaining after excluding {resource #3} corresponding to resource C from resource A, and may transmit the same. Accordingly, the BS may map the symbol sequence {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively, and may transmit the same.
The UE may determine resource A and resource B based on scheduling information associated with symbol sequence A obtained from the BS, and thus may determine resource C that is the area where resource A and resource B overlap. The UE may assume that symbol sequence A is mapped to the remaining area excluding resource C from the entire resource A and is transmitted, and may receive symbol sequence A. For example, when symbol sequence A is configured with {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE may assume that symbol sequence A is sequentially mapped to the resource {resource #1, resource #2, resource #4} remaining after excluding {resource #3} corresponding to resource C from resource A, and may receive the same. Accordingly, the UE may assume that the symbol sequence {symbol #1, symbol #2, symbol #3} is mapped to {resource #1, resource #2, resource #4}, respectively, and is transmitted, and may perform a series of subsequent reception operations.
When resource C corresponding to an area that overlaps with resource B is present in the entire resource A in which symbol sequence A is desired to be transmitted to a UE, a BS may map symbol sequence A map to the entire resource A. However, the BS does not perform transmission in the resource area corresponding to resource C but may perform transmission only in the resource area remaining after excluding resource C from the resource A. For example, when symbol sequence A is configured with {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the BS may map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to the resource A {resource #1, resource #2, resource #3, resource #4}, respectively, and may transmit only a symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4} that is a resource remaining after excluding {resource #3} corresponding to resource C from resource A but may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. Accordingly, the BS may map the symbol sequence {symbol #1, symbol #2, symbol #4} to {resource #1, resource #2, resource #4}, respectively, and may transmit the same.
The UE may determine resource A and resource B based on scheduling information associated with symbol sequence A obtained from the BS, and thus may determine resource C that is the area where resource A and resource B overlap. The UE may assume that symbol sequence A is mapped to the entire resource A and is only transmitted in the remaining area excluding resource C from the entire resource A, and may receive symbol sequence A. For example, when symbol sequence A is configured with {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the UE may assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to the resource A {resource #1, resource #2, resource #3, resource #4}, respectively, and {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and may assume that corresponding symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4} that is a resource remaining after excluding {resource #3} corresponding to resource C from resource A and is transmitted, and may perform reception. Accordingly, the UE may assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is mapped to {resource #1, resource #2, resource #4}, respectively, and is transmitted, and may perform a series of subsequent reception operations.
Rate matching is performed to adjust the size of a signal in consideration of the amount of resource capable of transmitting the signal. For example, rate matching of a data channel is to adjust the size of data with respect to a predetermined time and frequency resource area, as opposed to mapping and transmitting the data channel.
In
Via an additional configuration, the BS may report whether to perform rate matching on a data channel in the configured rate matching resource part, to the UE dynamically via DCI (corresponding to a “rate matching indicator” in the above-described DCI format). Specifically, the BS may select some of the configured rate matching resources and may group them into a rate matching resource group, and may indicate whether to perform rate matching of a data channel for each rate matching resource group to the UE via DCI according to a bitmap scheme. For example, when 4 rate matching resources (RMR), that is, RMR #1, RMR #2, RMR #3, and RMR #4 are configured, the BS may configure rate matching groups such as rate matching group (RMG) #1={RMR #1, RMR #2} and RMG #2={RMR #3, RMR #4}, and may indicate whether to perform rate matching in each RMG #1 and RMG #2 to the UE via a bitmap by using 2 bits in a DCI field. For example, when rate matching needs to be performed, “1” is indicated, and otherwise, when rate matching is not needed, “O” is indicated.
In 5G, as a method of configurating a rate matching resource for a UE, granularity at an “RB symbol level” and granularity at an “RE level” may be supported. Particularly, the following configuration method may be used.
A maximum of four pieces of RateMatchPattern for each BWP may be configured for a UE via higher layer signaling, and a single piece of RateMatchPattern may include the following content.
As a reserved resource in a BWP, a time and frequency resource area of the corresponding reserved resource configured based on a combination of a bitmap at an RB level and a bitmap at a symbol level in the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicity AndPattern) in which a time and frequency resource area configured with a pair of a bitmap at an RB level and a bitmap at a symbol level is repeated may be additionally configured.
A time and frequency-domain resource area configured with a CORESET in a BWP, and a resource area corresponding to a time domain pattern configured based on a search space configuration in which the corresponding resource area is repeated may be included.
A UE may be configured with the following content via higher layer signaling.
As configuration information (lte-CRS-ToMatchAround) associated with an RE corresponding to an LTE cell-specific RS or common RS (LTE CRS) pattern, the number of ports of an LTE CRS (nrofCRS-Ports) and an LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of a center subcarrier of an LTE carrier based on a reference frequency point (e.g., reference point A), bandwidth size (carrierBandwidthDL) information of an LTE carrier, and subframe configuration information (mbsfn-SubframConfigList) corresponding to a multicast-broadcast single-frequency network (MBSFN), and the like may be included. Based on the above-described information, the UE may determine the location of a CRS in an NR slot corresponding to an LTE subframe.
Configuration information associated with a resource set corresponding to a single zero power (ZP) CSI-RS or multiple ZP CSI-RSs in a BWP may be included.
A BS may configure a table associated with time domain resource allocation information for a PDSCH and a PUSCH for a UE via higher layer signaling (e.g., an RRC signaling). The BS may configure a table including a maximum of 16 entries (maxNrofDL-Allocations=16) in association with a PDSCH, and may configure a table including a maximum of 16 entries (maxNrofUL-Allocations=16) in association with a PUSCH. In an embodiment, the time domain resource allocation information may include a PDCCH-to-PDSCH slot timing (a slot unit-based time interval between the point in time at which a PDCCH is receive and the point in time at which a PDSCH, scheduled by the received PDCCH, is transmitted, and denoted by K0) or a PDCCH-to-PUSCH slot timing (a slot unit-based time interval between the point in time at which a PDCCH is received and the point in time at which a PUSCH, scheduled by the received PDCCH, is transmitted, and denoted by K2), information associated with the location of a start symbol where a PDSCH or a PUSCH is scheduled in a slot and the length of symbols, a PDSCH or PUSCH mapping type, and the like. For example, information such as shown below in Table 15 or Table 16 may be transmitted from the BS to the UE.
The BS may inform the UE of one of the entries in the tables associated with the time domain resource allocation information via L1 signaling (e.g., DCI) (for example, via a ‘time domain resource allocation’ field in DCI). The UE may obtain the time domain resource allocation information associated with a PDSCH or PUSCH based on the DCI received from the BS.
Referring to
Referring to
Referring to
When a UE is configured via higher layer signaling, so as to use only resource type 1 as shown in diagram 7-05, some DCI that allocates a PDSCH to the corresponding UE may include frequency-domain resource allocation information including ┌log2 (NRBDL,BWP (NRBDL,BWP+1)/2┐ bits. The condition for the above will be described later. Based on the same, a BS may configure a starting VRB 7-20 and the length 7-25 of a frequency-domain resource consecutively allocated from the starting VRB 7-20.
When a UE is configured via higher layer signaling, so as to use both resource type 0 and resource type 1 as shown in diagram 7-10, some DCI that allocates a PDSCH to the corresponding UE may include frequency-domain resource allocation information configured with bits of a payload having a higher value 7-35 among a payload 7-15 for configuring resource type 0 and a payload 7-20 and 7-25 for configuring resource type 1. The condition for the above will be described later. In this instance, one bit may be added to the most significant bit (MSB) of the frequency-domain resource allocation information in the DCI. When the corresponding bit is ‘0’, this may indicate that resource type 0 is to be used, and when the corresponding bit is ‘1’, this may indicate that resource type 1 is to be used.
PDSCH: phase tracking RS (PTRS) When receiving a PDSCH from a BS, a UE may receive a PTRS for tracking a phase associated with a DL channel. For the UE, phaseTrackingRS that is a higher layer signaling parameter for a PTRS may be configured in DMRS-DownlinkConfig that is a higher layer signaling parameter. When phaseTrackingRS is configured for the UE by the BS via a higher signaling parameter, a resource in which a PTRS is transmitted in the frequency domain and the time domain may be configured via frequencyDensity and timeDensity. In the case of the UE, frequencyDensity in PTRS-DownlinkConfig that is a higher layer signaling parameter may indicate NRB0 or NRB1, and timeDensity may indicate ptrs-MCS1 or ptrs-MCS3.
The UE may determine PTRS density in the time domain (LPT-RS) and PTRS density (KPT-RS) in the frequency domain according to the MCS (IMCS) and the NRB of a scheduled PDSCH, as shown below in Table 18 and 19. In Table 18 shown below, although ptrs-MCS4 is not mentioned as a higher layer parameter, a BS and a UE may be aware that it is 29 or 28 according to the configured MCS table. In Table 19 shown below, an NRB is the number of RBs scheduled for a PDSCH.
A DMRS configured by the BS and an associated PTRS may be mapped to the same subcarrier location, and the same precoding may be assumed for the antenna ports of the DMRS and PTRS. For the UE, a single PTRS antenna port is defined for reception of a PTRS, and the PTRS antenna port may be associated with a DMRS antenna port based on a codeword. When a single codeword is transmitted, a PTRS antenna port may be associated with a DMRS antenna port having the lowest index, and when two codewords are transmitted, the PTRS antenna port may be associated with a DMRS antenna port having the lowest index for a scheduled codeword with a higher MCS.
A BS may determine the configuration of a precoding granularity in the frequency domain for a UE in units of consecutive resource blocks, that is, based on a PRB bundling size unit PBWP,i′. When the PRB bundling size PBWP,i′ is determined to be a “wideband”, the UE may not expect nonconsecutive PRB scheduling and the UE may apply the assumption of the same precoding, TCI state or QCL to the allocated frequency resource. When PBWP,i′ is determined to be one of {2, 4}, an ith BWP may be configured with a PRG including as many consecutive PRBs as PBWP,i′. In this instance, the actual number of consecutive PRBs included in the PRG with respect to the start point and the end point of a BWP may be less than a PRG size PBWP,i′. That is, the size of the BWP in the frequency domain may not be divided evenly by the PRG size. Therefore, the PRG at the start point of the BWP may be configured with PBWP,i′−NBWP,istart mod PBWP,i′ PRBs. In association with the size of a PRG at the end point of the BWP, when (NBWP,istart+NBWP,isize)mod PBWP,i′ is greater than 0, the size of the PRG may be determined to be (NBWP,istart+NBWP,isize)mod PBWP,i′. When (NBWP,istart+NBWP,isize)mod PBWP,i′ is 0, the size of the PRG may be determined to be PBWP,i′. In this instance, the UE may assume that the same precoding is applied to consecutive DL PRBs in the PRG.
Based on configuration and/or indication information from the BS, the UE may determine a PRG size PBWP,i′. When the BS schedules a PDSCH for the UE via DCI format 1_0 or DCI format 4_0, the UE may assume that the PRG size PBWP,i′ is 2. When prb-BundlingType in higher layer signaling information PDSCH-Config from the BS is not configured for the UE, and a PDSCH is scheduled via DCI format 1_1, the UE may assume that the PRG size PBWP,i′ is 2. When prb-BundlingType in higher layer signaling information PDSCH-Config from the BS is configured as ‘staticBundling’ for the UE, the UE may determine a single value indicated by bundliSzie in the higher layer signaling information PDSCH-Config as the PRG size PBWP,i′.
When prb-BundlingType in the higher layer signaling information PDSCH-Config from the BS is configured as ‘dynamicBundling’ for the UE, bundleSizeSet 1 and bundleSizeSet2 in the higher layer signaling information PDSCH-Config may be configured for the UE and the PRG size PBWP,i′ included in each bundleSizeSet may have one or two values among {2, 4, wideband}. A method in which the UE receives an indication associated with a PRG size from the BS via DCI format 1_1 may be as follows. When ‘bundling size indicator’ in DCI format 1_1 from the BS indicates 0 to the UE, the UE may receive a PDSCH by applying PBWP,i′ via a second set (bundleSizeSet2) among sets of PRG size PBWP,i′ (i.e., bundleSizeSet1 and bundleSizeSet2). When ‘bundling size indicator’ in DCI format 1_1 from the BS indicates 1 to the UE, the UE may perform reception by applying PBWP,i′ via bundleSizeSet1. In this instance, a combination included in bundleSizeSet1 may be present, and the combination may differ according to the following situation.
When the size of bundleSizeSet1 is 1 (i.e., the number of values included in bundleSizeSet1 is 1), n4 or a wideband may be configured in bundleSizeSet1.
When the size of bundleSizeSet1 is 2 (i.e., the number of values included in bundleSizeSet1 is 2), {n2-wideband} or {n4-wideband} may be configured in bundleSizeSet1.
When consecutive PRBs are scheduled, and a PRB that is scheduled is greater than NBWPsize/2, the number of scheduled RBs, that is, a wideband, may be applied. Otherwise, 2 or 4 may be applied.
Referring to
The main function of the NR SDAP S25 and S70 may include transfer of user plane data, mapping between a QoS flow and a DRB for both DL and UL and marking a QoS flow ID in both DL and UL packets.
In association with an SDAP layer device, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device may be configured for the UE via an RRC message for each PDCP layer device, for each bearer, or for each logical channel. When the SDAP header is configured, a NAS reflective QoS configuration one-bit indicator (NAS reflective QoS) and an AS reflective QoS configuration one-bit indicator (AS reflective QoS) of the SDAP header may provide an indication so that the UE updates or reconfigures mapping information between a QoS flow and a data bearer in a UL and a DL. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority information, scheduling information, or the like for supporting a smooth service.
The main functions of the NR PDCP S30 and S65 may include at least one of: ROHC only, transfer of user data, sequential transfer (in-sequence delivery of upper layer PDUs), non-sequential transfer (out-of-sequence delivery of upper layer PDUs), reordering (PDCP PDU reordering for reception), duplicate detection of lower layer SDUs, retransmission of PDCP SDUs, ciphering and deciphering, and timer-based SDU discard in the UL.
The mentioned reordering function of the NR PDCP device is sequentially reordering PDCP PDUs received in a lower layer according to a PDCP sequence number (PDCP SN), and may include transferring data to a higher layer in a reordered sequence. The reordering function of the NR PDCP device may include immediately transferring data irrespective of a sequence, recording lost PDCP PDUs after sequential reordering, reporting the states of lost PDCP PDUs to a transmission side, and requesting retransmission of lost PDCP PDUs.
The main function of the NR RLC S35 and S60 may include at least one of transfer of upper layer PDUs, sequential transfer (in-sequence delivery of upper layer PDUs), non-sequential transfer (out-of-sequence delivery of upper layer PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, reordering of RLC data PDUs, duplicate detection, protocol error detection, RLC SDU discard, and RLC re-establishment.
The mentioned in-sequence delivery function of the NR RLC device is sequentially transferring RLC SDUs, received from a lower layer, to a higher layer. In when a single original RLC SDU is divided into multiple RLC SDUs and the multiple RLC SDUs are received, the in-sequence delivery function of the NR RLC may include reassembling and transmitting the same. The in-sequence delivery function of the NR RLC device may include reordering received RLC PDUs according to an RLC sequence number (RLC SN) or a PDCP sequence number (PDCP SN), and recording lost RLC PDUs after sequential reordering, reporting the states of the lost RLC PDUs to a transmission side, and requesting retransmission of the lost RLC PDUs. The in-sequence delivery function of the NR RLC device may include sequentially transferring, to a higher layer, only RLC SDUs before a lost RLC SDU when there is a lost RLC SDU. Even though there is a lost RLC SDU, when a predetermined timer expires, the in-sequence delivery function may include sequentially transferring RLC SDUs, received before the timer starts, to a higher layer. Alternatively, the in-sequence delivery function of the NR RLC device may include sequentially transferring all RLC SDUs, received up to the present, to a higher layer even though there is a lost RLC SDU, when a predetermined timer expires. In addition, RLC PDUs are processed in order of reception (in order of arrival, irrespective of a serial number or a sequence number), and are transmitted to the PDCP device irrespective of a sequence (out-of-sequence delivery). In the case of segments, segments, which are stored in a buffer or which are to be received in the future, are received and reconfigured as a single intact RLC PDU, are processed, and are transmitted to the PDCP device. The NR RLC layer may not include a concatenation function, or may perform the function in the NR MAC layer or replace the function with a multiplexing function in the NR MAC layer.
The out-of-sequence delivery function of the NR RLC device is immediately transferring RLC SDUs, received from a lower layer, to a higher layer irrespective of a sequence. When a single original RLC SDU is divided into multiple RLC SDUs and the multiple RLC SDUs are received, the out-of-sequence delivery function may include reassembling and transmitting the same, and storing the RLC SN or PDCP SN of the received RLC PDUs, and performing sequential ordering, and recording lost RLC PDUs.
The NR MAC S40 and S55 may be connected to multiple NR RLC layer devices configured for a single UE, and the main functions of the NR MAC may include at least one of mapping between logical channels and transport channels, multiplexing and demultiplexing of MAC SDUs, scheduling information reporting, error correcting through HARQ, priority handling between logical channels of one UE, priority handling between UEs by dynamic scheduling, MBMS service identification, transport format selection, and padding.
The NR PHY layer S45 and S50 may perform channel-coding and modulating of higher layer data to produce an OFDM symbol, and transmit the OFDM symbol via a wireless channel, or may perform demodulating and channel-decoding of the OFDM symbol, received via a wireless channel, and transmit the demodulated and channel-decoded OFDM symbol to a higher layer.
The detailed structure of the radio protocol structure may be variously changed depending on a carrier (or cell) operation scheme. For example, when a BS transmits, based on a single carrier (or cell), data to a UE, the BS and the UE may use a protocol structure having a single structure for each layer as shown in diagram S00. Conversely, when, based on CA that uses multiple carriers in a single transmission and reception point (TRP), a BS transmits data to a UE, the BS and the UE may use a protocol structure that has a single structure up to RLC and performs multiplexing a PHY layer via a MAC layer, as shown in diagram S10. As another example, when, based on dual connectivity (DC) that uses multiple carriers in multiple TRPs, a BS transmits data to a UE, the BS and the UE may use a protocol structure that has a single structure up to RLC but performs multiplexing a PHY layer via a MAC layer, as shown in diagram S20.
Referring to the above-described PDCCH and the description related to configuration of a beam, repetitive PDCCH transmission is not supported in Release (Rel)-15 and Rel-16 NR currently, and thus it is difficult to obtain request reliability in a scenario that needs high-reliability such as URLLC and the like. The disclosure provides a repetitive PDCCH transmission method via multiple transmission points (TRP) so as to improve a PDCCH reception reliability of a UE. A method will be described in detail in the following embodiments.
Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings. The content provided in the disclosure may be applicable in FDD and TDD systems. Hereinafter, higher signaling (or higher layer signaling) is signal transferring from a BS to a UE via a DL data channel of a physical layer, or signal transferring from a UE to a BS via a UL data channel of a physical layer, which may also be referred to as RRC signaling, PDCP signaling, or MAC control element (CE).
Herein, when determining whether cooperative communication is applied, a UE may use various methods such as a method in which a PDCCH(s) that allocates a PDSCH to which cooperative communication is applied has a predetermined format, a method in which a PDCCH(s) that allocates a PDSCH to which cooperative communication is applied includes a predetermined indicator indicating whether cooperative communication is applied, a method in which a PDCCH(s) that allocates a PDSCH to which cooperative communication is applied is scrambled by a predetermined RNTI, a method in which application of cooperative communication is assumed in a predetermined interval indicated via a higher layer, or the like. For ease of description, when a UE receives a PDSCH to which cooperative communication is applied based on the conditions similar to the above is referred to as an NC-JT case.
Herein, determining priorities of A and B may be variously described such as the case of selecting one having a higher priority according to a predetermined priority rule and performing an operation corresponding thereto, or the case of omitting or dropping one that has a lower priority, or the like.
Although the disclosure describes the various examples via a plurality of embodiments, the embodiments are not independent from one another but one or more embodiments may be applicable together or in parallel.
In 3GPP, SBFD has been discussed as a new duplex scheme based on NR. In a TDD band (spectrum) of 6 GHz or lower frequency or 6 GHz or higher frequency, SBFD may receive, from a UE, as much UL transmission as a UL resource increased by utilizing some of a DL resource as a UL resource, may extend UL coverage of the UE, and may receive, from the UE, feedback with respect to DL transmission in the extended UL resource, so as to reduce a feedback delay. In the disclosure, a UE that is capable of receiving, from a BS, information associated with whether SBFD is supported, and performing UL transmission in a part of a DL resource (or a UE that has related capability and is capable of reporting capability to a BS) is referred to as an SBFD UE (SBFD-capable UE). To define the SBFD scheme in the standard, and to enable an SBFD UE to determine that the SBFD is supported in a predetermine cell (or frequency, frequency band), the following scheme may be considered.
In a first scheme, in addition to an existing frame structure type of an unpaired spectrum (or time division duplex (TDD)) or a paired spectrum (or frequency division duplex (FDD)), another frequency structure type (e.g., frame structure type 2) may be introduced to define the SBFD. Fame structure type 2 may define that SBFD is supported in the predetermined frequency or frequency band, or a BS may indicate whether SBFD is supported to a UE via system information. An SBFD UE may receive system information including whether the SBFD is supported and may determine whether SBFD is supported in the predetermined cell (or frequency, frequency band).
In a second scheme, without defining a new frame structure type, whether the SBFD is additionally supported in a predetermined frequency or frequency band of an existing unpaired spectrum (or TDD) may be indicated. In the second scheme, whether the SBFD is additionally supported in a predetermined frequency or frequency band of an existing unpaired spectrum may be defined, or a BS may indicate whether SBFD is supported to a UE via system information. An SBFD UE may receive system information including whether the SBFD is supported and may determine whether SBFD is supported in the predetermined cell (or frequency, frequency band).
In the first and second schemes, information associated with whether SBFD is supported may be information (e.g., SBFD resource configuration information to be described in
The SBFD UE may receive an SS block (i.e., an SS/PBCH block) and may obtain cell synchronization at an initial cell access for accessing a cell (or BS). The process of obtaining the cell synchronization may be identical between an SBFD UE and an existing TDD UE (or SBFD-incapable UE). Subsequently, the SBFD UE may determine whether the cell supports SBFD by obtaining an MIB or SIB or via a random access process.
System information to transmit information associated with whether the SBFD is supported may be system information that is distinguished from system information for a UE (e.g., an existing TDD UE) that supports a different version of standard in the cell, and is transmitted separately. The SBFD UE may determine the whole or part of the system information that is separately transmitted from the system information of the existing TDD UE, and may determine whether SBFD is supported in the corresponding cell. When the SBFD UE obtains only system information for the existing TDD UE or obtains system information indicating that SBFD is not supported, the SBFD UE may determine that the cell (or BS) supports only TDD.
When information associated with whether SBFD is supported is included in system information for a UE (e.g., an existing TDD UE) that supports a different version of standard, the information associated with whether the SBFD is supported may be inserted into the last portion of the system information so as not to affect obtaining of the system information of the existing TDD UE. When the SBFD UE fails to obtain information associated with whether SBFD is supported, which is inserted into the last portion, or obtains information indicating that SBFD is not supported, the SBFD UE may determine that the cell (or BS) supports only TDD.
When information associated with whether SBFD is supported is included in system information for a UE (e.g., an existing TDD UE) that supports a different version of standard, the information associated with whether the SBFD is supported may be transmitted via a separate PDSCH so as not to affect obtaining of the system information of the existing TDD UE. That is, an SBFD-incapable UE may receive a first SIB including existing TDD-related system information via a first PDSCH. An SBFD-capable UE may receive a first SIB including existing TDD-related system information via a first PDSCH, and may receive a second SIB including SBFD-related system information via a second PDSCH different from the first PDSCH. The first PDSCH and the second PDSCH may be scheduled via a first PDCCH and a second PDCCH, respectively, and cyclic redundancy codes (CRC) of the first PDCCH and the second PDCCH may be scrambled by the same RNTI (e.g., SI-RNTI). A search space for monitoring the second PDCCH may be obtained from the system information of the first PDSCH. When the UE does not obtain information associated with a search space for monitoring the second PDCCH from the system information of the first PDSCH (i.e., when the system information of the first PDSCH does not include information associated with the search space), the UE may receive the second PDCCH in a search space that is the same as the search space of the first PDCCH.
When the SBFD UE determines that the cell (or BS) supports only TDD, the SBFD UE may perform a random access procedure and data/control signal transmission or reception in the same manner as that of the existing TDD UE.
The BS may configure a random access resource separately for each of an existing TDD UE or an SBFD UE (e.g., an SBFD UE that supports duplex communication and an SBFD UE that supports half-duplex communication), and may transmit configuration information (control information or configuration information indicating a time-frequency resource usable for a PRACH) of the random access resource to the SBFD UE via system information. The system information to transmit information associated with the random access resource may be system information that is distinguished from system information for a UE (e.g., an existing TDD UE) that supports a different version of standard in the cell, and is transmitted separately.
The BS configures random access resources separately for the SBFD UE and the TDD UE that supports a different version of standard, and may distinguish whether the one that performs random access is the TDD UE that supports the different version of standard performs random access or the SBFD UE. For example, the random access resource separately configured for the SBFD UE may be a resource that the existing TDD UE identifies as a DL time resource, and the SBFD UE may perform random access via a UL resource (or a separate random access resource) configured in a part of the frequency of the DL time resource and the BS determines that a UE that attempts random access in the UL resource is the SBFD UE.
Alternatively, the BS may not configure a random access resource separately for the SBFD UE, but may configure a random access resource in common for all UEs in a cell. In this instance, configuration information for the random access resource may be transmitted to all UEs in the cell via system information, and an SBFD UE that receives the system information may perform random access in the random access resource. Subsequently, the SBFD UE may complete the random access process and may proceed with an RRC connection mode for performing data transmission or reception with a cell. After RRC connection mode, the SBFD UE may receive, from the BS, a higher or physical signal that enables determining that a part of the frequency resource of the DL time resource is configured as a UL resource, and may perform an operation related to SBFD (e.g., transmission of a UL signal in the UL resource).
When the SBFD UE determines that the cell supports SBFD, the SBFD UE may inform the BS that a UE that attempts accessing is an SBFD UE by transmitting capability information including at least one piece of information among information associated with whether the UE supports SBFD, information associated with whether full-duplex communication or half-duplex communication is supported, the number of transmission antennas that the UE is equipped with (or supports), or the number of reception antennas that the UE is equipped with (or supports). Alternatively, when supporting half-duplex communication is essential for the SBFD UE, whether the half-duplex communication is supported may be omitted from the capability information. In association with reporting of the capability information by the SBFD UE, the capability information may be reported to the BS via a random access process, may be reported to the BS after the random access process is completed, or may be reported to the BS after RRC access mode for data transmission or reception with a cell is performed.
The SBFD UE may support half-duplex communication that performs only UL transmission or DL reception at one instance in the same manner as the existing TDD UE or may support full-duplex communication that performs both UL transmission and DL reception at one instance. Therefore, whether half-duplex communication or full-duplex communication is supported may be reported by the SBFD UE to the BS via capability reporting, and after reporting, the BS may configure, for the SBFD UE, whether the half-duplex communication or the full-duplex communication is to be used when the SBFD UE performs transmission or reception. When the SBFD UE reports, to the BS, capability associated with the half-duplex communication, a switching gap for changing an RF between transmission and reception may be needed when operation is performed in FDD or TDD, since a duplexer is not present in general.
Part (a) In
In part (a) in
In part (b) in
In part (c) in
In part (d) in
Herein, a time-frequency resource in which UL transmission is available in a DL symbol or slot may be referred to as an SBFD resource. A symbol in which a UL subband is configured in DL symbols may be referred to as an SBFD symbol. A time-frequency resource in which DL reception is available in a UL symbol or slot may be referred to as an SBFD resource. A symbol in which a DL subband is configured in UL symbols may be referred to as an SBFD symbol.
For ease of description, a band that excludes a UL subband, and in which a DL channel or signal is capable of being received may be expressed as a DL subband. For the UE, a maximum of a single UL subband may be configurable and a maximum of two DL subbands may be configurable in a single symbol. For example, the UE may be configured with one of UL subband and DL subband, DL subband and UL subband, or first DL subband, UL subband, and second DL subband, in the frequency domain.
A PRG grid used for a UE to receive a PDSCH may be determined based on the start point and the size of a DL BWP and PRB bundling related configuration information that the UE receives from a BS. In this instance, the UE may need to determine an RPG grid in an SBFD symbol/slot in which a UL subband is present, as well as in the DL only symbol/slot. Since a UL subband is present in an SBFD symbol/slot, a PRG may not be divided evenly by a configured PRB size in the frequency resource area excluding the start point and the end point of a DL BWP, which is a drawback.
The BS may transmit, to the UE, information for configuring a frequency density related to PTRS transmission, and the frequency density of a PTRS may be determined based on the size of a scheduled PRB. However, in an SBFD symbol/slot, a DL frequency resource that is a UL subband less than that of a DL only symbol/slot may be used, and thus the size of a scheduled PRB that is actually used may be different. When the size of a scheduled PRB in the SBFD symbol/slot is interpreted to be the same as that in the DL only symbol/slot, the frequency density of the PTRS may be determined to be inappropriate for the SBFD symbol/slot.
Thus, disclosed herein is a method of determining a PRG grid in consideration of a UL subband, determining the size of a scheduled PRB in an SBFD symbol/slot, interpreting a DL BWP size, and assuming precoding when wideband PRB bundling is configured, and the like.
Referring to
When the SBFD system considers a UL subband, there may be ambiguity in performing a PRG grid determination method. For example, when a frequency resource of a UL subband is configured to be aligned with the start point of the existing PRG 1 and the end point of PRG 2 as shown in the case of UL subband 1 1210 (i.e., when the start point or the end point of the UL subband frequency resource are aligned with the boundary between different PRGs included in a PRG grid), there may be no problem occurring in the PRG grid determination method. However, when a UL subband frequency resource is configured as shown in the case of UL subband 2 1211 that is not aligned with an existing PRG grid (i.e., when the start point or end point of the UL subband frequency resource is not aligned with the boundary between different PRGs included in a PRG grid), there may be ambiguity when the UE and the BS determine a PRG grid. In the following embodiments, there may be provided methods to overcome the drawback.
A UE may determine a PRG grid in consideration of a UL subband by performing a modulo operation based on a UL subband frequency resource configuration received from a BS. The UE may receive configuration information related to a BWP and PRB bundling size from the BS via higher layer configuration information. In an SBFD system, the UE may receive configuration information associated with a UL subband frequency resource separately. In this instance, to determine a PRG grid, the UE may perform a modulo operation based on the received UL subband frequency resource configuration information.
A detailed method in which a UE determines a PRG grid by using UL subband frequency resource configuration information received from a BS may be as follows. When the result value of a modulo operation that the UE performs on the start point of a UL subband and a PRB bundling size is 0 (e.g., NULSBstart mod PBWP,i′) and the result value of a modulo operation performed on the end point of the UL subband and the PRB bundling size is 0 (e.g., (NULSBstart+NULSBsize)mod PBWP,i′=0), the UE may determine that the frequency resource of the UL subband is aligned with a PRG grid. When the result value of a modulo operation that the UE performs on the start point of the UL subband and the PRB bundling size is not 0 (e.g., NULSBstart mod PBWP,i′≠0) and the result value of a modulo operation performed on the start point and the end point of the UL subband and the PRB bundling size is not 0 (e.g., (NULSBstart+NULSBsize)mod PBWP,i′≠0), the UE may determine that the frequency resource of the UL subband is not aligned with a PRG grid.
Referring to
Referring to
According to the method provided in the embodiment, although explicit signaling is not separately provided between the BS and the UE, the UE may determine whether a UL subband is aligned with a PRG grid. The BS may implicitly inform the UE of whether a UL subband is aligned with a PRG grid, without signaling overhead of transmitting separate information to the UE. Through the above, the burden of signaling overhead in the SBFD system may be reduced.
A UE may determine a PRG size in consideration of a result obtained by determining whether a UL subband frequency resource is aligned with a PRG grid based on configuration information received from a BS. The UE may receive a DL BWP, a PRB bundling size, and UL subband configuration information from the BS via higher layer signaling, and may determine whether the PRG grid and the UL subband are aligned based on the received configuration information. In this instance, with respect to one or more PRGs excluding the start point and the end point of a DL BWP, the UE may determine a PRG size based on whether the PRG grid and the UL subband frequency resource are aligned with each other.
[Method 2-1: A Method of Determining a PRG Size when a PRG Grid is not Aligned with a Ul Subband]
A UE may perform a modulo operation on a UL subband frequency resource and a PRB bundling size by using configuration information received from a BS, and may determine, based on a result obtained by performing the modulo operation, a PRG grid size at a point where a PRG grid and a UL subband are not aligned with each other. Specifically, the fact that the PRG grid and the UL subband frequency resource are not aligned may imply the following three cases.
In Case 1 where NULSBstart mod PBWP,i′≠0, when a start point of a UL subband frequency resource is not aligned with a PRG grid.
In Case 2 where (NULSBStart+NULSBsize)mod PBWP,i′≠0, when an end point of a UL subband frequency is not aligned with a PRG grid.
In Case 3 where Case 1 and Case 2 are satisfied, when both the start point and the end point of a UL subband frequency resource are not aligned with a PRG grid.
Based on a result obtained by performing a modulo operation using the frequency resource of a UL subband and PRB bundling size configuration information, the UE may determine a PRG size for each case mentioned above.
In Case 1, the UE may determine the size of a PRG to be NULSBstart mod PBWP,i′ with respect to a predetermined PRG that is close to the start point of the UL subband. In Case 2, for a predetermined PRG that is close to the end point of the UL subband, the UE may determine the size of the corresponding PRG to be PBWP,i′−(NULSBstart+NULSBsize)mod PBWP,i′. In Case 3, for a PRG that is close to the start point of the UL subband, the UE may determine the size of the corresponding PRG to be NULSBstart mod PBWP,i′, and for a PRG close to the end point of the UL subband, the UE may determine the size of the corresponding PRG to be PBWP,i′−(NULSBstart+NULSBsize)mod PBWP,i′. In this instance, a PRG size corresponding to a part remaining after excluding the start point and the end point of a DL BWP may be identical to a PRB bundling size (PBWP,i′) configured via higher layer signaling.
Referring to
The BS may flexibly and efficiently configure a UL subband for a UE, and, particularly, may determine a PRG size in consideration of a UL subband even though the sizes of some PRGs are not explicitly and separately indicated to the UE. In addition, based on configuration information received from the BS, the UE may determine a PRG size in consideration of a UL subband and may be capable of determining a PRG size appropriate for an SBFD system.
Method 2-2: Determining a PRG Size when a PRG Grid is Aligned with a UL Subband
A UE may determine a PRG size based on a DL BWP, a PRB bundling size, and UL subband configuration information, which are received from a BS via higher layer signaling. According to the above-described embodiments, when the UE determines that both the start point and the end point of the frequency resource of a UL subband are aligned with a PRG grid, the UE may determine a PRG size without separate calculation. That is, for one or more PRGs excluding the start point and the end point of the DL BWP, the UE may determine each PRG size as a PRB bundling size (PBWP,i′).
Method 2-3: A BS Configures Only a UL Subband Frequency Resource Aligned with a PRG Grid
When a UE receives UL subband configuration information from a BS, the UE may assume that the frequency resource of a UL subband identified based on the received configuration information is always aligned with a PRG grid. In other words, the UE may not expect the BS to configure a UL subband in a manner that the start point or the end point of a UL subband frequency resource is not aligned with the PRG grid. Unlike the above-described method 2-1 or method 2-2, according to method 2-3, the frequency resource of the UL subband determined according to the UL subband configuration information transmitted from the BS to the UE is always aligned with the PRG grid, the UE may determine a PRG size based on a DL BWP and a PRB bundling size which are received from the BS via higher layer signaling. That is, for a PRG excluding the start point and the end point of the DL BWP, a PRG size may be determined to be a PRB bundling size (PBWP,i′).
The third embodiment provides a method in which a UE interprets the size (NRB) of a scheduled PRB to receive a PDSCH in an SBFD symbol/slot. A BS may transmit PDSCH related configuration information to the UE via higher layer signaling. In an SBFD system, it is assumed that the PDSCH transmission is performed only in an SBFD symbol/slot, it is assumed that the PDSCH transmission is performed only in a DL only symbol/slot, or it is assumed that the PDSCH transmission is performed in both the DL only symbol/slot and the SBFD symbol/slot. To allow PDSCH transmission only in a predetermined symbol/slot (DL only symbol/slot or SBFD symbol/slot) may limit the time resource of DL scheduling of the BS, and thus the overall system performance may deteriorate. Therefore, to secure flexibility in PDSCH scheduling of the BS in the SBFD system, transmission needs to be performed in both the DL only symbol/slot and the SBFD symbol/slot, which may be efficient from the perspective of system performance.
When a PDSCH is transmitted in both the DL only symbol/slot and SBFD symbol/slot, the UE needs a method of accurately interpreting a PRB size scheduled by the BS. For example, when configuration information that the UE receives from the BS includes information that requires to be calculated based on the size of a scheduled PRB such as a PTRS frequency density or a PRB bundling size, the UE may need to clearly define whether to use the size of a PRB scheduled in a DL only symbol/slot to interpret the information, or to use a PRB size excluding a UL subband frequency resource from an SBFD symbol/slot to interpret the information. For example, the BS may transmit information indicating dynamicBundling as a PRB bundling type to the UE via higher layer signaling. In this instance, a PRB bundling size may be determined based on DCI indication information and a condition of configuration information (whether consecutive PRBs are scheduled and the size of a scheduled PRB) which are obtained from the BS. Therefore, there is a need for a reference for interpreting the size of a scheduled PRB appropriate for an SBFD symbol/slot. In addition, in relation to a PTRS frequency density, granularity in the frequency resource area may be determined based on the size of a scheduled PRB. For example, when a PRB size is scheduled to be higher than a predetermined value, a PTRS frequency density may be mapped at intervals of 4 RBs. In this instance, the PTRS frequency density may be appropriate for a DL only symbol/slot but the corresponding PTRS frequency density may be inappropriate for an SBFD symbol/slot where a frequency resource area is small.
Referring to
Method 3-1: In an SBFD symbol/slot, a UE may interpret the size of a scheduled PRB to be the size of a PRB excluding a UL subband from a PDSCH frequency resource and may receive a PDSCH. In other words, the UE may interpret a PRB size of a scheduled PDSCH frequency resource to be the number of PRBs located in a DL subband in an SBFD symbol/slot, and may receive a PDSCH. Based on scheduling information that the UE receives from the BS, it is assumed that the size of the scheduled PDSCH frequency resource is NRB,PDSCH and the size of the frequency resource of the UL subband is NRB,UL subband. Based on the configuration information, the UE may interpret the size of a scheduled PRB in the SBFD symbol/slot to be NRB=NRB,PDSCH−NRB,UL subband. Based on the interpreted scheduled PRB size, the UE may perform operations such as determining a PRB bundling size and/or interpreting a PTRS frequency density or the like.
According to method 3-1 mentioned above, the UE may determine a PRB bunding size in consideration only a DL subband that is a resource appropriate for PDSCH reception in an SBFD system, and may determine a PTRS frequency density.
Method 3-2: In an SBFD symbol/slot, a UE may interpret the size of a scheduled PRB to be the size of a PRB configured as a PDSCH frequency resource and may receive a PDSCH. In other words, the UE may interpret the size of a PRB of the scheduled PDSCH frequency resource to be the number of PRBs as they are without taking into consideration a UL subband and a DL subband in the SBFD symbol/slot, and may receive a PDSCH. According to the scheduling information that the UE receives from a BS, it is assumed that the size of the scheduled PDSCH frequency resource is NRB,PDSCH. According to method 3-2, the UE may interpret the size of a scheduled PRB in the SBFD symbol/slot to be NRB=NRB,PDSCH. That is, the UE may interpret the size of a PRB configured as a PDSCH frequency resource to be a scheduled PRB, irrespective of the size of a UL subband. Based on the interpreted scheduled PRB size, the UE may perform operations such as determining a PRB bundling size and/or interpreting a PTRS frequency density or the like.
In
The fourth embodiment provides a description associated with a method in which a UE interprets the size (NBWP,isize) of a DL BWP to receive a PDSCH in an SBFD symbol/slot. As described in the third embodiment, for flexible scheduling in an SBFD system, there is a need to allow data transmission in both a DL only symbol/slot and an SBFD symbol/slot. For example, when dynamicBundling is configured for the UE by a BS as a PRB bundling configuration in a PDSCH configuration, it is ambiguous to interpret the size of a BWP in an SBFD system. Therefore, hereinafter, there is provided a method of interpreting the size of a configured BWP when a UE interprets configuration information configured by a BS or performs operation.
Method 4-1: In an SBFD symbol/slot, a UE interprets the size of a BWP to be a frequency resource excluding a UL subband from a configured DL BWP, and may perform operations in the DL BWP. For example, based on configuration information received from a BS, the UE may identify that the size of the DL BWP is NBWP,isize and may identify that the frequency resource size of the UL subband is NRB,UL subband. Based on the configuration information, the UE may interpret the size of the DL BWP in an SBFD symbol/slot to be NBWP,i,SBFDsize=NBWP,isize−NRB,UL subband, and may perform operation in the DL BWP. Based on the interpreted BWP size, the UE may perform operations such as determining of a PRB bundling size in the DL BWP, or the like.
Method 4-2: In an SBFD symbol/slot, a UE may interpret the size of a BWP to be the same as that of a configured DL BWP, and may perform operations in the DL BWP. For example, based on configuration information received from a BS, the UE may identify that the size of the DL BWP is NBWP,isize and may identify that the frequency resource size of the UL subband is NRB,UL subband. Based on the configuration information, the UE may interpret the size of the DL BWP in the SBFD symbol/slot to be NBWP,i,SBFDsize=NBWP,isize, and may perform operation in the DL BWP. Based on the interpreted BWP size, the UE may perform operations such as determining of a PRB bundling size in the DL BWP, or the like.
The content related to method 4-1 and method 4-2 will be described in detail with reference to the example of
In
In the fifth embodiment, there is provided a method of interpreting precoding when wideband PRB bundling is configured in an SBFD symbol/slot. A BS may include PRB bundling configuration information in PDSCH configuration information that the BS transmits to a UE. When the PDSCH configuration information that the UE receives from the BS includes configuration information indicating a wideband as a PRB bundling configuration, the UE may assume the same precoding for a configured PDSCH frequency resource. When a PDSCH frequency resource in the SBFD symbol/slot is a frequency resource area excluding a UL subband, a method of assuming precoding is provided as follows, to improve the channel estimation performance of the UE.
Method 5-1: Based on scheduling information received from a BS, a UE may assume that different precoding may be applied for each of the frequency resources which are separated by a UL subband in a scheduled PDSCH frequency resource area. In a description with reference to
Method 5-2: Based on scheduling information received from a BS, a UE may assume that the same precoding is applied in the entire frequency domain, without taking into consideration a frequency resource separated into parts due to a UL subband in a scheduled PDSCH frequency resource area (i.e., irrespective of whether a UL subband is present). In a description with reference to
A UE may transmit information associated with UE capability (or capability or ability) to a BS in operation 1900. The UE may receive configuration information produced with reference to the UE capability from the BS via higher layer signaling in operation 1905. The UE may receive, from the BS via dynamic signaling (e.g., DCI), scheduling information needed for receiving a PDSCH in operation 1910. Based on the configuration information received via higher layer signal and scheduling information received via dynamic signaling, the UE may apply one or more of the methods proposed in the first to fifth embodiments. For example, according to at least one of the third embodiment and the fourth embodiment, the UE may interpret the size of a scheduled PRB and a BWP size appropriate for a corresponding symbol/slot by using DL BWP configuration information, UL subband configuration information, and PDSCH scheduling information in operation 1915. As another example, according to the first embodiment, the second embodiment, and the fifth embodiment, the UE may determine whether UL subband is aligned with a PRG grid, and may determine and apply an appropriate PRG size (a PRB bundling size) based on whether the alignment is performed in operation 1915. Subsequently, the UE may receive a PDSCH from the BS according to a result of the operation performed in advance, in operation 1920.
A BS may receive information associated with UE capability (or capability or ability) from a UE in operation 2000. The BS may produce configuration information that refers to the received UE capability, and may transmit the configuration information to the UE via higher layer signaling in operation 2005. Subsequently, the BS may transmit, to the UE, scheduling information needed for PDSCH transmission via dynamic signaling (e.g., DCI) in operation 2010, and the BS may transmit a PDSCH to the UE in operation 2015 according to the methods proposed in the above-described first embodiment, second embodiment, and fifth embodiment.
Referring to
The transceiver may perform signal transmission or reception with a BS. A signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts a frequency, and the like. This is merely an example of the transceiver, and the component elements of the transceiver are not limited to an RF transmitter and an RF receiver.
In addition, the transceiver may receive a signal via a wireless channel and may output the same to the processor, and may transmit a signal output from the processor via a wireless channel.
The memory may store a program and data needed when the UE operates. In addition, the memory may store control information or data included in a signal transmitted or received by the UE. The memory may be embodied as a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, and the like, or a combination of storage media. In addition, multiple memories may be used.
The processor may control a series of processes so that the UE operates according to the above-described embodiment of the disclosure. For example, the processor may receive DCIs configured in two types of layers, and may control component elements of a UE so as to receive multiple PDSCHs in parallel. Multiple processors may be used, and a processor may implement a program stored in a memory so as to control component elements of the UE.
Referring to
The transceiver may perform signal transmission or reception with a UE. To this end, the transceiver may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts a frequency, and the like. However, this is merely one embodiment, and the component elements of the transceiver are not limited to the RF transmitter and the RF receiver.
In addition, the transceiver may receive a signal via a wireless channel and may output the same to the processor, and may transmit a signal output from the processor via a wireless channel.
The memory may store a program and data needed when the BS operates. In addition, the memory may store control information or data included in a signal transmitted or received by the BS. The memory may be embodied as a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, and the like, or a combination of storage media. In addition, multiple memories may be used.
The processor may control a series of processes such that the BS operates according to the above-described embodiment of the disclosure. For example, the processor may control each component element of the BS to configure DCIs in two types of layers that include allocation information associated with multiple PDSCHs and to transmit the same. Multiple processors may be used, and a processor may implement a program stored in a memory so as to control component elements of the BS.
The methods according to various embodiments described herein may be implemented by hardware, software, or a combination of hardware and software.
When the methods are implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured for execution by one or more processors within the electronic device. The at least one program may include instructions that cause the electronic device to perform the methods according to various embodiments disclosed herein.
The programs (software modules or software) may be stored in non-volatile memories including a random access memory and a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other type optical storage devices, or a magnetic cassette. Alternatively, any combination of some or all of them may form a memory in which the program is stored. A plurality of such memories may be included in the electronic device.
In addition, the programs may be stored in an attachable storage device which may access the electronic device through communication networks such as the Internet, Intranet, local area network (LAN), Wide LAN (WLAN), and storage area network (SAN) or a combination thereof. Such a storage device may access the electronic device via an external port. A separate storage device on the communication network may access a portable electronic device.
In the above-described detailed embodiments of the disclosure, an element included in the disclosure is expressed in the singular or the plural according to presented detailed embodiments. However, the singular form or plural form is selected appropriately to the presented situation for the convenience of description, and the disclosure is not limited by elements expressed in the singular or the plural. Therefore, either an element expressed in the plural may also include a single element or an element expressed in the singular may also include multiple elements.
The embodiments of the disclosure described and shown in the specification and the drawings are merely specific examples that have been presented to easily explain the technical contents of the disclosure and help understanding of the disclosure, and are not intended to limit the scope of the disclosure. That is, it will be apparent to those skilled in the art that other variants based on the technical idea of the disclosure may be implemented. Furthermore, the above respective embodiments may be employed in combination, as necessary. For example, a part of one embodiment of the disclosure may be combined with a part of another embodiment to operate a BS and a terminal. As an example, a part of embodiment 1 of the disclosure may be combined with a part of embodiment 2 to operate a BS and a terminal. Furthermore, although the above embodiments have been described on the basis of the FDD LTE system, other variant embodiments based on the technical idea of the above-described embodiments may also be implemented in other systems such as TDD LTE, 5G, or NR systems.
Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Furthermore, each block of the flowchart illustrations may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
While the disclosure has been illustrated and described with reference to various embodiments of the present disclosure, those skilled in the art will understand that various changes can be made in form and detail without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2023-0002108 | Jan 2023 | KR | national |
