Patent Application
20250089035
The disclosure relates to a terminal and an operating method for cross division duplex (XDD) system for bandwidth part (BWP) switching and resource configuration.
To satisfy an increasing demand for wireless data traffic after the commercialization of a fourth-generation (4G) communication system, efforts have been made to develop an improved fifth-generation (5G) communication system or a pre-5G communication system. For this reason, the 5G communication system or the pre-5G communication system is referred to as a beyond 4G network communication system or a post long-term evolution (LTE) system.
To achieve a high data transmission rate, the implementation of the 5G communication system in a super high frequency (mmWave) band (e.g., 60 GHz band) is considered. To mitigate a path loss of radio waves and increase a transmission distance of radio waves in the super high frequency band, beamforming, massive multiple-input multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, and large scale antenna techniques have been discussed and developed for the 5G communication system. In addition, to improve a network of the system, techniques, such as an advanced small cell, an improved small cell, a cloud radio access network (RAN), an ultra-dense network, device-to-device communication (D2D), wireless backhaul, a moving network, cooperative communication, coordinated multi-points (COMP), and interference cancellation, have been developed. Furthermore, in the 5G system, hybrid FSK and QAM modulation (FQMA), which is advanced coding modulation (ACM), sliding window superposition coding (SWSC), filter bank multi-carrier (FBMC), which is an advanced connection technique, non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), have been developed.
The Internet has evolved from a human-centric connection network in which a person generates and consumes information to the Internet of Things (IoT) in which information is processed by transmitting and receiving the information among distributed components, such as an object. An Internet of Everything (IoE) technique, which is a combination of an IoT technique with a big data processing technique through the connection with a cloud server has also emerged. To implement the IoT techniques, such as a sensing technique, wired or wireless communication and network infrastructure, a service interface technique, and a security technique, are required, and thereby, a sensor network for the connection between objects, machine to machine (M2M), machine type communication (MTC) techniques have been recently studied. In an IoT environment, an intelligent internet technology (IT) service in which a new value is created to human lives by collecting and analyzing data generated from connected objects may be provided. The IoT may apply to fields, such as a smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, and cutting-edge medical service, through the fusion and combination of existing IT techniques with various industries.
Accordingly, various attempts have been made to apply the 5G communication system to an IoT network. For example, techniques, such as a sensor network, M2M, and MTC, have been implemented by 5G communication techniques, such as beamforming, MIMO, and array antenna. The application of a cloud RAN as a big data processing technique described above may be an example of the fusion of the 5G and IoT techniques.
To improve coverages of a base station and a terminal, like a time division duplex (TDD) system, uplink (UL) and downlink (DL) resources in a time domain may be divided according to a traffic ratio of a UL and a DL, and UL and DL resources may be divided in a frequency domain like a frequency domain division duplex (FDD) system. As described above, a system that enables flexibly dividing UL resources and DL resources in the time domain and the frequency domain may be referred to as a ‘cross-division duplex (XDD)’ system. Other terms, such as a flexible TDD system, a hybrid TDD system, a TDD-FDD system, and a hybrid TDD-FDD system, are also interchangeably used or referred to as an XDD system in the related art and in the disclosure. In the XDD, X may represent time or frequency.
Provided is a cross-division duplex (XDD) system that supports XDD configuration (or XDD resource configuration) in various schemes.
Provided is an XDD system that is able to perform XDD bandwidth part (BWP) switching.
Provided is an XDD system that defines a priority between an uplink (UL) signal/channel and a downlink (DL) signal/channel when a resource overlap between the UL signal/channel and the DL signal/channel occurs.
According to an aspect of the disclosure, a method of a terminal, includes: receiving, from a base station, first downlink (DL) bandwidth part (BWP) configuration information comprising an identifier (ID) of a first DL BWP; receiving, from the base station, first uplink (UL) BWP configuration information comprising an ID of a first UL BWP; receiving, from the base station, second DL BWP configuration information comprising an ID of a second DL BWP and an ID of a second UL BWP; and recognizing, through the ID of the second UL BWP, that the second DL BWP configuration information is information for DL-UL configuration of the terminal, wherein, in a first slot, when the first DL BWP and the first UL BWP are temporally separated from each other, DL communication and UL communication are not simultaneously performed, by the terminal, with the base station, and wherein, in a second slot, the DL communication and the UL communication are simultaneously performed, by the terminal, with the base station based on the second DL BWP configuration information.
According to an aspect of the disclosure, a method of a base station, includes: transmitting first downlink (DL) bandwidth part (BWP) configuration information comprising an identifier (ID) of a first DL BWP to a terminal; transmitting, to the terminal, first uplink (UL) BWP configuration information comprising an ID of a first UL BWP; and transmitting, to the terminal, second DL BWP configuration information comprising an ID of a second DL BWP and an ID of a second UL BWP for DL-UL configuration of the terminal, wherein, in a first slot, when the first DL BWP and the first UL BWP are temporally separated from each other, DL communication and UL communication are not simultaneously performed by the base station with the terminal, and wherein, in a second slot, the DL communication and the UL communication are not simultaneously performed by the base station with the terminal based on the second DL BWP configuration information.
In addition, various effects directly or indirectly ascertained through the disclosure may be provided.
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 will be described in detail with reference to the accompanying drawings. When describing the embodiments with reference to the accompanying drawings, like reference numerals refer to like elements and a repeated description related thereto will be omitted.
Herein, a base station may be an entity performing resource allocation of a terminal and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless connection unit, a base station controller, or a node in a network. A terminal may include user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system for performing a communication function. Herein, a downlink (DL) may be a wireless transmission path of a signal transmitted from a base station to a terminal and an uplink (UL) may be a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, herein, long-term evolution (LTE), LTE-advanced (LTE-A), or a fifth-generation (5G) system may be provided as an example, but embodiments of the disclosure may apply to other communication systems having similar technical backgrounds or channel types. For example, the 5G mobile communication technology (new radio (NR)) developed after LTE-A may be included therein and the 5G described hereinafter may be a concept including LTE, LTE-A, and other similar services. In addition, the disclosure may apply to other communication systems through partial modification without significantly departing from the scope of the disclosure based on the determination of a skilled person with technical knowledge.
The wireless communication system may depart from providing an early voice-oriented service and for example, may evolve into a wide-band wireless communication system that provides a high-speed and high-quality packet data service, such as high-speed packet access (HSPA) of 3GPP, LTE (LTE or evolved-universal terrestrial radio access (E-UTRA)), LTE-A, LTE-Pro, high rate packet data (HRPD) of 3GPP2, ultra-mobile broadband (UMB), and communication standards, such as IEEE 802.16e.
As a representative example of the wide-band wireless communication system, an LTE system may adopt orthogonal frequency division multiplexing (OFDM) in a DL and single carrier-frequency division multiple access (SC-FDMA) in a UL. The UL may refer to a wireless link for transmitting data or a control signal from a mobile station (MS) to a base station (an eNode B or a BS), and the DL may refer to a wireless link for transmitting data or a control signal from a base station to a terminal. The multiple access scheme described above may distinguish data or control information of each user by allocating and operating time-frequency resources to prevent an overlap of the time-frequency resources to carry data or control information for each user, in other words, to establish orthogonality.
Since a future communication system after LTE, in other words, the 5G communication system needs to freely reflect various requirements of a user and a service provider, a service that simultaneously satisfies various requirements may need to be supported. A service considered for the 5G communication system may be enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliability low latency communication (URLLC).
The eMBB may aim to provide more enhanced data transmission speed than the data transmission speed supported by the existing LTE, LTE-A, or LTE-Pro. For example, in the 5G communication system, eMBB may need to provide 20 Gbps of the maximum transmission speed (peak data rate) in the DL and 10 Gbps of the maximum transmission speed in the UL in an aspect of a base station. In addition, the 5G communication system may need to provide an increased user-perceived data rate of a terminal while providing the peak data rate. To satisfy the requirement described above, improvements in various transmission and reception techniques including more enhanced multiple-input multiple-output (MIMO) may be required. In addition, the 5G communication system may satisfy the data transmission speed required by the 5G communication system by using a frequency bandwidth wider than 20 MHz in a frequency band of 3 to 6 GHz or above 6 GHz whereas LTE transmits a signal using the transmission bandwidth up to 20 MHz in a 2 GHz band.
Simultaneously, in the 5G communication system, mMTC may be considered to support an application service, such as the Internet of Things (IoT). mMTC may require a large scale of terminal connection support in a cell, enhanced coverage of a terminal, enhanced battery time, and cost reduction of the terminal to efficiently provide IoT. Since the IoT is attached to various sensors and devices and provides a communication function, a large number of terminals (e.g., 1,000,000 terminals/km2) may need to be supported in a cell. In addition, since a terminal supporting mMTC is likely to be located in a shaded area that a cell is not able to cover, such as the basement of a building, the terminal may require wider coverage than other services provided by the 5G communication system. The terminal supporting mMTC may need to consist of a low-cost terminal, and since it is difficult to frequently change a battery of the terminal, a significantly long battery lifetime, such as 10 to 15 years, may be required.
URLLC may be a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, a service used for remote control of a robot or machinery, industrial automation, an unmanned aerial vehicle, remote health care, and an emergency alert may be considered. Accordingly, the communication provided by URLLC may need to provide significantly low latency and significantly high reliability. For example, the service supporting URLLC may need to satisfy air interface latency smaller than 0.5 milliseconds and a packet error rate less than or equal to 75. Accordingly, for the service supporting URLLC, the 5G system may need to provide a transmit time interval (TTI) that is smaller than other services and may require a design matter to allocate a wide resource in a frequency band to secure the reliability of a communication link.
The three services of 5G, which are eMBB, URLLC, and mMTC, may be multiplexed in a single system and may be transmitted. In this case, different transmission and reception methods and transmission and reception parameters may be used between services to satisfy different requirements of each service. The 5G is not limited to the three services described above.
Hereinafter, a frame structure of the 5G system is further described with reference to drawings.
Referring to
Referring to
Next, a bandwidth part (BWP) configuration in a 5G communication system is further described with reference to drawings.
Referring to
Configuration of the BWP is not limited to the example described above and various parameters related to the BWP other than the configuration information may be configured to the terminal. The configuration information may be transmitted by the base station to the terminal through higher layer signaling, for example, radio resource control (RRC) signaling. At least one BWP of the one or the plurality of configured BWPs may be activated. An activation status of the configured BWP may be semi-statically transmitted to the terminal from the base station through RRC signaling or may be dynamically transmitted through downlink control information (DCI).
According to an embodiment, for a terminal before RRC connection, an initial BWP for initial connection may be configured by the base station through a master information block (MIB). Specifically, the terminal may receive configuration information on a search space and a control resource set (CORESET) in which PDCCH for the reception of system information (may correspond to remaining system information (RMSI) or a system information block 1 (SIB 1)) required for the initial connection is transmitted through the MIB in an initial connection stage. The control resource set that is configured by the MIB may be regarded as an identifier (ID) (identity) 0. The base station may notify the terminal configuration information such as time allocation information, frequency allocation information, and numerology, etc., for a control resource set #0 through the MIB. In addition, the base station may notify the terminal of configuration information on a monitoring period and occasion for the control resource set #0, in other words, configuration information on a search space #0, through the MIB. The terminal may regard a frequency domain configured as the control resource set #0 obtained from the MIB as an initial BWP for the initial connection. In this case, the ID of the initial BWP may be regarded as 0.
The configuration of the BWP supported by the 5G wireless communication system may be used for various purposes.
According to an embodiment, when the system bandwidth is smaller than the bandwidth supported by the terminal, the configuration with respect to the BWP may be used. For example, the terminal may transmit or receive data at a specific frequency location in the system bandwidth as the base station configures the terminal with a frequency location (configuration information 2) of the BWP.
In addition, according to an embodiment, the base station may configure a plurality of BWPs to the terminal to support different numerologies. For example, the base station may configure two BWPs to subcarrier intervals of 15 kHz and 30 kHz, respectively, to support both data transmission and reception using the subcarrier interval of 15 kHz and the subcarrier interval of 30 kHz to a terminal. The different BWPs may be frequency division multiplexed and when the base station attempts to transmit or receive data at a specific subcarrier interval, the BWP configured to the subcarrier interval may be activated.
In addition, according to an embodiment, the base station may configure a BWP having different sizes of bandwidths to the terminal to reduce power consumption of the terminal. For example, when the terminal supports a significantly great bandwidth, for example, a bandwidth of 100 MHz and always transmits or receives data with the bandwidth, power may be significantly consumed. Specifically, performing monitoring on an unnecessary DL control channel with the great bandwidth of 100 MHz while there is no traffic, may be significantly inefficient in an aspect of power consumption. The base station may configure a BWP of a relatively small bandwidth, for example, a BWP of 20 MHz, to the terminal to reduce the power consumption of the terminal. The terminal may perform a monitoring operation in the 20 MHz BWP while there is no traffic and when data occurs, the terminal may transmit or receive data with the 100 MHz BWP according to the instruction of the base station.
In a method of configuring the BWP, terminals before the RRC connection may receive configuration information on an initial BWP through an MIB in an initial connection stage. Specifically, a control resource set for a DL control channel in which DCI that schedules a system information block (SIB) from an MIB of a physical broadcast channel (PBCH) may be configured to the terminal. The bandwidth of the control resource set that is configured to MIB may be regarded as an initial BWP and the terminal may receive a physical downlink shared channel (PDSCH) in which an SIB is transmitted through the configured initial BWP. The initial BWP may be utilized for other system information (OSI), paging, and random access other than receiving an SIB.
If one or more BWPs are configured to the terminal, the base station may instruct the terminal to change the BWP using a BWP indicator field in the DCI. As an example, when a currently activated BWP of the terminal of
As described above, since a change in a BWP based on DCI may be instructed by the DCI that schedules a PDSCH or a PUSCH, when the terminal receives a request for changing the BWP, the terminal may need to receive or transmit the PDSCH or PUSCH scheduled by the DCI in a changed BWP without a problem. For this, the standard may specify a requirement for latency TBWP required when changing a BWP and may be defined as, for example, Table 3 shown below.
Note 1
The requirement for BWP change latency may support type 1 or type 2 depending on the capability of the terminal. The terminal may report a supportable BWP latency type to the base station.
According to the requirement for the BWP change latency described above, when the terminal receives DCI including a BWP change indicator in a slot n, the terminal may complete a change to a new BWP indicated by the BWP change indicator at a time point no later than n+TBWP, and may transmit or receive a data channel scheduled by the DCI in the new changed BWP. When the base station attempts to schedule a data channel to the new BWP, the base station may determine time domain resource allocation to the data channel by considering the BWP change latency TBWP. In other words, when the base station schedules a data channel to the new BWP, in a method of determining a time domain resource allocation to a data channel, the base station may schedule the data channel after BWP change latency. Accordingly, the terminal may not expect that the DCI indicating the BWP change indicates a slot offset value (K0 or K2) that is less than the BWP change latency TBWP.
If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating the BWP change, the terminal may not perform any transmission or reception during a time interval from a third symbol of a slot that receives a PDCCH including the DCI to a start point of a slot indicated by a slot offset (K0 or K2) indicated in a time domain resource allocation indicator field in the DCI. For example, when the terminal receives DCI indicating a BWP change in a slot n and a slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from a third symbol of the slot n to a symbol previous to a slot n+K (in other words, a last symbol of a slot n+K−1).
Next, a synchronization signal (SS)/PBCH block in a 5G wireless communication system is described.
A SS/PBCH block may be a physical layer channel block including a primary SS (PSS), a secondary SS (SSS), and a PBCH. A detailed description thereof is as follows.
The terminal may detect a PSS and an SSS in an initial connection stage and may decode a PBCH. The MIB may be obtained from the PBCH and a control resource set (CORESET) #0 (may correspond to a control resource set of which a control resource set index is 0) may be configured therefrom. The terminal may assume that the selected SS/PBCH block and a demodulation reference signal (DMRS) transmitted by the control resource set #0 are quasi-colocated (QCLed) and may perform monitoring on the control resource set #0. The terminal may receive the system information as the DL control information transmitted by the control resource set #0. The terminal may obtain configuration information related to a random access channel (RACH) required for initial connection from the received system information. The terminal may transmit a physical RACH (PRACH) to the base station by considering the selected SS/PBCH index, and the base station receiving the PRACH may obtain information on the SS/PBCH block index selected by the terminal. The base station may know which block the terminal has selected from SS/PBCH blocks and whether the control resource set #0 related thereto is monitored.
Next, the DCI in a 5G wireless communication system is further described.
In the 5G system, scheduling information on UL data (or a physical uplink shared channel (PUSCH)) or DL data (or a physical downlink shared channel (PDSCH)) may be transmitted from a base station to a terminal through the DCI. The terminal may monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or the PDSCH. The fallback DCI format may include a predefined fixed field between the base station and the terminal and the non-fallback DCI format may include a configurable field.
The DCI may be transmitted via a physical downlink control channel (PDCCH), through channel coding and modulation processes. A cyclic redundancy check (CRC) may be attached to a DCI message payload and the CRC may be scrambled by a radio network temporary identifier (RNTI) corresponding to the identity of the terminal. Depending on the purpose of a DCI message, for example, UE-specific data transmission, a power control command, or a random access response, different RNTIs may be used. In other words, the RNTI may not be explicitly transmitted and may be transmitted by being included in a CRC calculation process. When the terminal receives the DCI message transmitted through the PDCCH, the terminal may check the CRC using the allocated RNTI and if a CRC check result is correct, the terminal may know that the message is transmitted to the terminal.
For example, the DCI that schedules the PDSCH for the system information (SI) may be scrambled by an SI-RNTI. DCI that schedules a PDSCH for a random access response (RAR) message may be scrambled by a random access (RA)-RNTI. DCI that schedules a PDSCH for a paging message may be scrambled by a P-RNTI. DCI that notifies a slot format indicator (SFI) may be scrambled by an SFI-RNTI. DCI that notifies 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), modulation coding scheme C-RNTI (MCS-C-RNTI), or a configured scheduling RNTI (CS-RNTI).
The DCI format 0_0 may be used as fallback DCI that schedules a PUSCH and in this case, the CRC may be scrambled by the C-RNTI. The DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include, for example, the information shown in Table 4 below.
(N
+ 1)/2┐ bits where
is defined in Subclause 7.3.1.0
most significant bit (MSB) bits are used to indicate the frequency offset
= 1 if the higher layer parameter
= 2 if the higher layer
(N
+ 1)/2┐ − NUL
bits provides the frequency domain resource
(N
+ 1)/2┐ bits provides the frequency domain resource
indicates data missing or illegible when filed
The DCI format 0_1 may be used as non-fallback DCI that schedules a PUSCH and in this case, the CRC may be scrambled by the C-RNTI. The DCI format 0_1 in which the CRC is scrambled by the C-RNTI may include, for example, the information shown in Table 5 below.
)┐ bits, where
, in which case the bandwidth part indicator is defined in Table
is the size of the active UL bandwidth part:
bits if only resource allocation type 0 is configured, where N
is defined in
(N
+ 1)/2)┐ bits if only resource allocation type 1 is configured, or
(N
+ 1)/2)┐, N
) + 1 bits if both resource allocation type 0 and 1 are configured.
LSBs provide the resource allocation as defined
(N
+ 1)/2)┐ LSBs provide the
MSB bits are used to indicate the frequency offset according to Subclause 6.3 of
= 1 if the higher layer parameter frequencyHoppingOffsetLists
= 2 if the higher layer parameter
(N
+ 1)/2)┐- N
bits provides the frequency domain resource
(N
+ 1)/2)┐ bits provides the frequency domain resource allocation
indicates data missing or illegible when filed
The DCI format 1_0 may be used as fallback DCI that schedules a PDSCH and in this case, the CRC may be scrambled by the C-RNTI. The DCI format 1_0 in which the CRC is scrambled by the C-RNTI may include, for example, the information shown in Table 6 below.
(N
+ 1)/2┐ bits where
indicates data missing or illegible when filed
The DCI format 1_1 may be used as non-fallback DCI that schedules a PDSCH and in this case, the CRC may be scrambled by the C-RNTI. The DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include, for example, the information shown in Table 7 below.
configured by higher layers, excluding the initial DL bandwidth part. The
)┐ bits, where
= n
+ 1 if n
≤ 3, in which case the bandwidth part indicator is
= n
, in which case the bandwidth part indicator is defined
is the size of the active DL bandwidth part:
bits if only resource allocation type 0 is configured, where N
is defined
(N
+ 1)/2┐ bits if only resource allocation type 1 is
(N
+ 1)/2┐ , N
) + 1 bits if both resource
LSBs provide the resource allocation as
(N
+ 1)/2┐ LSBs
+ 1)┐ bits, where n
is the
shall be determined according to the
indicates data missing or illegible when filed
Hereinafter, a method of allocating a time domain resource to a data channel in a 5G wireless communication system is described.
A base station may set a table for time domain resource allocation to a PDSCH and a PUSCH by higher layer signaling (e.g., RRC signaling). A table consisting of up to maxNrofDL-Allocations=16 entries may be set to the PDSCH and a table consisting of up to maxNrofUL-Allocations=16 entries may be set to the PUSCH. The time domain resource allocation information may include, for example, PDCCH-to-PDSCH slot timing (corresponding to a slot-wise time interval between a time point of receiving a PDCCH and a time point of transmitting a PDSCH scheduled by the received PDCCH, and displayed as K0) or PDCCH-to-PUSCH slot timing (corresponding to a slot-wise time interval between a time point of receiving a PDCCH and a time point of transmitting a PUSCH scheduled by the received PDCCH, and displayed as K2), information on a location and length of a start symbol in which a PDSCH or a PUSCH is scheduled in a slot, and a PDSCH or PUSCH mapping type. For example, the information shown in Table 8 and Table 9 below may be notified from the base station to the terminal.
The base station may notify the terminal of one of the entries of the table about the time domain resource allocation information through L1 signaling (e.g., DCI) (e.g., may indicate as a “time domain resource allocation” field in the DCI). The terminal may obtain the time domain resource allocation information on the PDSCH or the PUSCH based on the received DCI from the base station.
Hereinafter, a method of allocating a frequency domain resource to a data channel in a 5G wireless communication system is described.
In the 5G wireless communication system, two types, which are a resource allocation type 0 and a resource allocation type 1, may be supported as a method of indicating the frequency domain resource allocation information for a PDSCH and a PUSCH.
The RB allocation information may be notified to the terminal from the base station in the form of a bitmap for a resource block group (RBG). In this case, the RBG may consist of a set of consecutive virtual RBs (VRBs), and a size P of the RBG may be determined based on a value set to an higher layer parameter (rbg-Size) and a size value of a BWP defined as nominal RBG size P in Table 10 shown below.
The total number of RBGs of a BWPi of which the size is NBWP,isize may be defined as follows.
Each bit of a bitmap having the size of NRBG bit may correspond to each RBG. The RBGs may receive indexes in order of increasing frequency, starting from the lowest frequency location of a BWP. For NRBG RBGs in the BWP, from RBG #0 to RBG #NRBG−1 may be mapped from an MSB to an LSB of an RBG bitmap. If a specific bit value in the bitmap is 1, the terminal may determine that a corresponding RBG is allocated to the bit value, and if a specific bit value in the bitmap is 0, the terminal may determine that a corresponding RBG is not allocated to the bit value.
RB allocation information may be notified to the terminal from the base station as the information on a start position and length of consecutively allocated VRBs. In this case, interleaving or non-interleaving may be additionally applied to the consecutively allocated VRBs. A resource allocation field of the resource allocation type 1 may consist of a resource indication value (RIV), and the RIV may consist of a start point RBstart of the VRB and a length LRBS of the consecutively allocated RBs. More specifically, an RIV in a BWP having the size of NBWPsize may be defined as follows.
The base station may configure the terminal with a resource allocation type through higher layer signaling (e.g., an higher layer parameter resourceAllocation may be set to one of resourceAllocationType0, resourceAllocationType1, and dynamicSwitch). If the terminal is configured with the both the resource allocation types 0 and 1 (or identically, if the higher layer parameter resourceAllocation is set to dynamicSwitch), the base station may indicate whether a bit corresponding to a most significant bit (MSB) of a field indicating resource allocation in the DCI format indicating scheduling is the resource allocation type 0 or the resource allocation type 1. In addition, resource allocation information may be indicated by remaining bits other than the bit corresponding to the MSB based on the indicated resource allocation type and the terminal may interpret resource allocation field information of a DCI field based thereon. If the terminal is configured with one of the resource allocation type 0 and the resource allocation type 1 (or identically, if the higher layer parameter resourceAllocation is set to one of resourceAllocationType0 and resourceAllocationType1), resource allocation information may be indicated based on a resource allocation type in which a field indicating resource allocation in a DCI format indicating scheduling, and the terminal may interpret resource allocation field information of a DCI field based thereon.
Hereinafter, a modulation and coding scheme (MCS) used by a 5G wireless communication system is further described.
In 5G, a plurality of MCS index tables may be defined for PDSCH and PUSCH scheduling. Among the plurality of MCS tables, a MCS table assumed by the terminal may be set or indicated by higher layer signaling or L1 signaling from the base station to the terminal or an RNTI value assumed by the terminal during PDCCH decoding.
An MCS index table 1 for a PDSCH and a CP-OFDM-based PUSCH (or a PUSCH without transform precoding) may be the same as Table 11 (MCS index table 1 for PDSCH) shown below.
An MCS index table 2 for a PDSCH and a CP-OFDM-based PUSCH (or a PUSCH without transform precoding) may be the same as Table 12 (MCS index table 2 for PDSCH) shown below.
An MCS index table 3 for a PDSCH and a CP-OFDM-based PUSCH (or a PUSCH without transform precoding) may be the same as Table 13 (MCS index table 3 for PDSCH) shown below.
An MCS index table 1 for DFT-s-OFDM-based PUSCH (or a PUSCH with transform precoding) may be the same as Table 14 (MCS index table for PUSCH with transform precoding and 64 QAM) shown below.
An MCS index table 2 for DFT-s-OFDM-based PUSCH (or a PUSCH with transform precoding) may be the same as Table 15 (MCS index table 2 for PUSCH with transform precoding and 64QAM) shown below.
An MCS index table for a PUSCH to which transform precoding (transform precoding or discrete Fourier transform (DFT) precoding) and 64 QAM are applied may be the same as Table 16 shown below.
An MCS index table for a PUSCH to which transform precoding (transform precoding or DFT precoding) and 64 QAM are applied may be the same as Table 17 shown below.
Hereinafter, a DL control channel in a 5G wireless communication system is further described with reference to drawings.
Referring to
The control resource set in the 5G wireless communication system described above may be configured by the base station to the terminal through higher layer signaling (e.g., SI, MIB, RRC signaling). Configuring a control resource to a terminal may be providing information, such as a control resource set identifier, a frequency location of the control resource set, and a symbol length of the control resource set. For example, the information from Table 18 shown below may be included.
In Table 18, tci-StatesPDCCH (simply referred to as a TCI state) configuration information may include information on a CSI-reference signal (CSI-RS) index or one or a plurality of SS/PBCH block indexes in a QCL relationship with a DMRS transmitted from a corresponding control resource set.
In other words,
Referring to
As shown in
The basic unit of the DL control channel shown in
The search space may be classified as a common search space and a UE-specific search space. Terminals of a certain group or all terminals may search a common search space of a PDCCH to receive dynamic scheduling for system information or cell common control information, such as a paging message. For example, PDSCH scheduling allocation information for transmission of an SIB including business information of a cell may be received by searching the common search space of the PDCCH. Since the terminals of a certain group or all terminals need to receive a PDCCH, the common search space may be defined as a set of pre-arranged CCEs. The scheduling allocation information of a UE-specific PDSCH or PUSCH may be received by searching for a UE-specific search space of the PDCCH. The UE-specific search space may be UE-specifically defined as a function of various system parameters and the identity of the terminal.
In the 5G wireless communication system, a parameter for the search space of the PDCCH may be configured in the terminal by the base station through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station may configured the terminal with the number of PDCCH candidates at the aggregation level L, a monitoring period for the search space, a symbol-wise monitoring occasion in a slot for the search space, a search space type (a common search space or a UE-specific search space), a combination of an RNTI and a DCI format to be monitored in the search space, and a control resource set index to monitor the search space, to the terminal. For example, a parameter related to a search space for a PDCCH may include the information shown in Table 19 below.
Depending on the configuration information, the base station may configured one or a plurality of search space sets to the terminal. According to an embodiment, the base station may configure the terminal with a search space set 1 and a search space set 2. In the search space set 1, the base station may configure the terminal to monitor a DCI format A scrambled by an X-RNTI in a common search space, and in the search space set 2, the base station may configure the terminal to monitor a DCI format B scrambled by a Y-RNTI in a UE-specific search space.
According to the configuration information, one or a plurality of search space sets may exist in a common search space or a UE-specific search space. For example, a search space set #1 and a search space set #2 may be set as a common search space, and a search space set #3 and a search space set #4 may be set as a UE-specific search space.
In the common search space, a combination of a DCI format and an RNTI shown below may be monitored. The example is not limited thereto.
In the UE-specific search space, a combination of a DCI format and an RNTI shown below may be monitored. The example is not limited thereto.
The specified RNTIs may follow the definitions and purposes described below.
The DCI formats described above may follow the definitions shown in Table 20 below.
In the 5G wireless communication system, in a control resource set p and a search space set s, a search space of an aggregation level L may be expressed as the following equation.
In the case of a common search space, a Y_(p,nμs,f) value may correspond to 0.
In the case of a UE-specific search space, the Y_(p,nμs,f) value may correspond to a value that varies depending on the identify (C-RNTI or ID configured in the terminal by the base station) and a time index.
Referring to
First, a UL-DL of a symbol/slot may be semi-statically configured in a symbol through cell-specific configuration information 610 through system information. Specifically, the cell-specific UL-DL configuration information through the system information may include UL-DL pattern information and reference subcarrier information. The UL-DL pattern information may indicate a pattern periodicity 603, the number 611 of consecutive DL slots from a start point of each pattern, the number 612 of symbols of a following slot, the number 613 of consecutive UL slots from an end of the pattern, and the number 614 of symbols of a following slot. In this case, a slot and a symbol, which are not indicated by the UL and the DL, may be determined to be a flexible slot and a flexible symbol.
Second, through user-specific configuration information through dedicated higher layer signaling, slots 621 and 622 including a flexible slot or a flexible symbol may be indicated by numbers 623 and 625 of consecutive DL symbols from start symbols of the respective slots and numbers 624 and 626 of consecutive UL symbols from ends of the respective slots, or may be indicated by the entire slot DL or the entire slot UL.
Third, to dynamically change DL signal transmission and UL signal transmission sections, the symbols indicated by a flexible symbol in each slot (in other words, the symbols that are not indicated by the DL and the UL) may be indicated whether each symbol is a DL symbol, a UL symbol, or a flexible symbol, by slot format indicators (SFIs) 631 and 632 included in the DL control channel. The SFI may be selected by one index in a table in which 14 symbols of a UL-DL configuration in one slot is preset as shown in Table 21 (or Table 34 to be described below) below.
In an NR system, the terminal may transmit control information (uplink control information: UCI) to the base station through a PUCCH. The control information may include at least one of HARQ-ACK indicating the success of demodulation/decoding with respect to a transport block (TB) that the terminal receives through a PDSCH, a scheduling request (SR) requested by the terminal to a PUSCH base station for resource allocation to transmit uplink data, and CSI, which is information for reporting a channel state of the terminal.
A PUCCH resource may be divided into a long PUCCH and a short PUCCH depending on the length of an allocated symbol. In the NR system, a long PUCCH may have a length of at least four symbols in a slot, and a short PUCCH may have a length of less than or equal to two symbols in a slot.
To further describe the long PUCCH, the long PUCCH may be used to improve uplink cell coverage and therefore, may be transmitted in a DFT-S-OFDM scheme, which is single carrier transmission, rather than OFDM transmission. The long PUCCH may support transmission formats, such as PUCCH format 1, PUCCH format 3, and PUCCH format 4, depending on whether terminal multiplexing is supported through pre-DFT OCC support in an IFFT frontend and the number of supportable control information bits.
Firstly, the PUCCH format 1 may be a DFT-S-OFDM-based long PUCCH format capable of supporting control information up to 2 bits and may use a frequency resource by one RB. The control information may include each or a combination of HARQ-ACK and an SR. The PUCCH format 1 may iteratively include an OFDM symbol including a DMRS, which is a reference signal for demodulation, and an OFDM symbol including the UCI.
For example, when the number of transmission symbols of the PUCCH format 1 is eight, from a first starting symbol of the eight symbols, the symbols may be a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, a UCI symbol, a DMRS symbol, and a UCI symbol. The DMRS symbol may be spread using an orthogonal code (or an orthogonal sequence or a spreading code, wi(m)) on the time axis in a sequence corresponding to a length of 1 RB on the frequency axis in one OFDM symbol and may be transmitted after IFFT is performed.
The UCI symbol may be transmitted after the terminal generates d(0) by performing BPSK modulation on 1 bit control information and QPSK modulation on 2 bits control information, scrambles the generated d(0) by multiplying the generated d(0) by a sequence corresponding to a length of 1 RB on a frequency domain, spreads the scrambled sequence on a time domain by using an orthogonal code (or an orthogonal sequence or spreading code wi(m)), and performs IFFT on the spread sequence.
The terminal may generate a sequence based on a configured ID and group hopping or sequence hopping configuration configured by higher layer signaling from the base station, and may generate a sequence corresponding to the length of 1 RB by cyclic shifting the generated sequence with an initial cyclic shift (CS) value configured via an upper signal.
wi(m) may be determined as
when the length (NSF) of a spreading code is given, and specifically, is given as in Table 22 shown below. i may denote an index of the spreading code and m may denote an index of elements of the spreading code. In this case, numbers in the bracket [ ] in Table 22 may denote Φ(m), and for example, when the length of the spreading code is 2 and an index i of the set spreading code is 0, a spreading code w_i(m) may be wi(0)=ejπ·0/N
Next, the PUCCH format 3 may be a DFT-S-OFDM-based long PUCCH format capable of supporting control information of more than 2 bits and the number of used RBs may be configured through an higher layer. The control information may include each or a combination of HARQ-ACK, SR, and CSI. In the PUCCH format 3, a DMRS symbol location may be proposed in the following Table 23 depending on frequency hopping in a slot and additional DMRS symbol configuration.
For example, when the number of transmission symbols of the PUCCH format 3 is eight symbols, a first starting symbol of the eight symbols may start with 0 and a DMRS may be transmitted to a first symbol and a fifth symbol. [Table 23] may identically apply to a DMRS symbol location of a PUCCH format 4.
Next, the PUCCH format 4 may be a DFT-S-OFDM-based long PUCCH format capable of supporting control information of more than 2 bits, and may use a frequency resource by 1 RB. The control information may include each or a combination of HARQ-ACK, SR, and CSI. The PUCCH format 4 may be different from the PUCCH format 3 in an aspect that the PUCCH format 4 may multiplex the PUCCH format 4 of various terminals in one RB. The PUCCH format 4 of multiple terminals may be possible by applying pre-DFT orthogonal cover code (OCC) to the control information in IFFT frontend. However, the number of control information symbols transmitted by one terminal may decrease depending on the number of multiplexed terminals. The number of multiplexed terminals, in other words, the number of usable different OCCs may be 2 or 4, and the number of OCCs and an OCC index to be applied may be configured through an higher layer.
Next, a short PUCCH is described. A short PUCCH may be transmitted by both a DL centric slot and a UL-centric slot, and typically, may be transmitted by a last symbol of a slot, or an OFDM symbol in a rear portion (e.g., a last OFDM symbol, a second to last OFDM symbol, or last two OFDM symbols). The short PUCCH may be transmitted by an arbitrary location in the slot. In addition, the short PUCCH may be transmitted using one OFDM symbol or two OFDM symbols. The short PUCCH may be used to reduce latency compared to the long PUCCH in the case of decent UL cell coverage and may be transmitted by CP-OFDM.
The short PUCCH may support transmission formats, such as the PUCCH format 0 and the PUCCH format 2, depending on the number of supportable control information bits. Firstly, the PUCCH format 0 may be a short PUCCH format capable of supporting control information up to 2 bits and may use a frequency resource by 1 RB. The control information may include each or a combination of HARQ-ACK and an SR. The PUCCH format 0 may not transmit a DMRS and may have a structure for transmitting only a sequence mapped onto 12 subcarriers on the frequency axis in one OFDM symbol. The terminal may generate a sequence based on group hopping or sequence hopping configuration configured from the base station through an upper signal and configured ID, may cyclic-shift the generated sequence by using a final cyclic shift (CS) value obtained by adding a different CS value to an indicated initial CS value according to ACK or NACK, may map the cyclic-shifted sequence to 12 subcarriers, and transmit the mapped sequence.
For example, when HARQ-ACK is 1 bit, the terminal may generate a final CS by adding 6 to an initial CS value in the case of ACK as shown in Table 24 below, and may generate a final CS by adding 0 to an initial CS value in the case of NACK. “0” that is a CS value for NACK and “6” that is a CS value for ACK may be defined in the standard, and the terminal may transmit 1-bit HARQ-ACK by generating the PUCCH format 0 according to the value defined in the standard.
For example, when HARQ-ACK is 2 bits, the terminal may add 0 to an initial CS value in the case of (NACK, NACK) as shown in Table 25 below, may add 3 to the initial CS value in the case of (NACK, ACK), may add 6 to the initial CS value in the case of (ACK, ACK), and may add 9 to the initial CS value in the case of (ACK, NACK). 0 that is a CS value for (NACK, NACK), 3 that is a CS value for (NACK, ACK), 6 that is a CS value for (ACK, ACK), and 9 that is a CS value for (ACK, NACK) may be defined in the standard and the terminal may transmit a 2-bit HARQ-ACK by generating a PUCCH format 0 depending on a value defined in the standard.
When a final CS value obtained by adding a CS value according to ACK or NACK to the initial CS value exceeds 12, the length of sequence may be 12, and thereby, modulo 12 may apply to the final CS value.
Next, the PUCCH format 2 may be a short PUCCH format that supports control information exceeding 2 bits and the number of used RBs may be configured via an higher layer. The control information may include each or a combination of HARQ-ACK, SR, and CSI. When an index of the first subcarrier is #0, in PUCCH format 2, locations of subcarriers transmitting a DMRS in one OFDM symbol may be fixed to subcarriers having indexes of #1, #4, #7, and #10. After channel encoding and modulation, the control information may be mapped onto remaining subcarriers other than the subcarrier where the DMRS is located.
In addition, multi-slot repetition may be supported for the PUCCH formats 1, 3, and 4 to improve UL coverage and PUCCH repetition may be configured for each PUCCH format. The terminal may perform iterative transmission to a PUCCH including UCI by the number of slots configured through nrofSlots that is higher layer signaling. For iterative PUCCH transmission, PUCCH transmission of each slot may be performed using the same number of consecutive symbols, and the number of consecutive symbols may be configured through nrofSymbols that is higher layer signaling in PUCCH-format 1, PUCCH-format 3, or PUCCH-format 4. For iterative PUCCH transmission, the PUCCH transmission of each slot may be performed using a same starting symbol and the same starting symbol may be configured via startingSymbolIndex that is higher layer signaling in PUCCH-format 1, PUCCH-format 3, or PUCCH-format 4. For iterative PUCCH transmission, a single PUCCH-spatialRelationInfo may be configured for a single PUCCH resource. For iterative PUCCH transmission, if the terminal is configured to perform frequency hopping in the PUCCH transmission in different slots, the terminal may perform frequency hopping slot-wise. In addition, if the terminal is configured to perform frequency hopping in the PUCCH transmission in different slots, in an even-numbered slot, the terminal may start the PUCCH transmission from a first PRB index configured via startingPRB that is higher layer signaling, and in an odd-numbered slot, the terminal may start the PUCCH transmission from a second PRB index configured via secondHopPRB that is higher layer signaling. In addition, if the terminal is configured to perform frequency hopping in the PUCCH transmission in different slots, an index of a slot indicated to the terminal for the first PUCCH transmission may be 0, and during the entire configured PUCCH iterative transmissions, the number of PUCCH iterative transmissions may increase regardless of the PUCCH transmission in each slot. If the terminal is configured to perform frequency hopping in the PUCCH transmission in different slots, the terminal may not expect to configuration of frequency hopping in a slot during the PUCCH transmission. If the terminal is not configured to perform frequency hopping in the PUCCH transmission in different slots and is configured with frequency hopping within a slot, the first and second PRB indexes may be identically applied in the slot. If the number of UL symbols capable of PUCCH transmission is less than nrofSymbols configured via higher layer signaling, the terminal may not transmit a PUCCH. Even if the terminal fails to transmit a PUCCH for some reason in a slot during the PUCCH iterative transmissions, the terminal may increase the number of PUCCH iterative transmissions.
Next, PUCCH resource configuration of a base station or a terminal is described. The base station may configured a PUCCH resource for each BWP through an higher layer to a specific terminal. The PUCCH resource configuration may be as shown in Table 26 below.
According to Table 26, one or multiple PUCCH resource sets may be configured for a specific BWP in PUCCH resource configuration, and a maximum payload value for UCI transmission may be configured in a portion of the PUCCH resource sets. One or multiple PUCCH resources may belong to each PUCCH resource set and each PUCCH resource may belong to one of the PUCCH formats described above.
For the PUCCH resource set, a maximum payload value of a first PUCCH resource set may be fixed to 2 bits. Accordingly, a corresponding value may not be separately configured through an higher layer and the like. If a remaining PUCCH resource set is configured, an index of the PUCCH resource set may be configured in ascending order of the maximum payload value, and a maximum payload value may not be configured for the last PUCCH resource set. The higher layer configuration for the PUCCH resource set may be as shown in Table 27 below.
IDs of PUCCH resources belonging to the PUCCH resource set may be included in resourceList parameters of Table 27.
In the case of an initial connection or if a PUCCH resource set is not configured, a PUCCH resource set of Table 28 configured by multiple cell-specific PUCCH resources in an initial BWP may be used. A PUCCH resource used for the initial connection in the PUCCH resource set may be indicated by an SIB 1.
Each maximum payload of PUCCH resources included in the PUCCH resource set may be 2 bits in the case of PUCCH format 0 or 1, and the maximum payload for other formats may be determined by the symbol length, the number of PRBs, and a maximum code rate. The symbol length and the number of PRBs may be configured for each PUCCH resource and the maximum code rate may be configured for each PUCCH format.
Next, PUCCH resource selection for UCI transmission is described. In the case of SR transmission, a PUCCH resource for an SR corresponding to schedulingRequestID as shown in Table 29 may be configured through an higher layer. The PUCCH resource may be a resource belonging to the PUCCH format 0 or the PUCCH format 1.
For the configured PUCCH resource, a transmission period and an offset may be configured through a periodicity AndOffset parameter of Table 29. If there is UL data to be transmitted by the terminal at a time point corresponding to the configured period and offset, a corresponding PUCCH resource may be transmitted and otherwise, the corresponding PUCCH resource may not be transmitted.
In the case of CSI transmission, a PUCCH resource to transmit a semi-persistent or periodic CSI report through a PUCCH may be configured in a pucch-CSI-ResourceList parameter as shown in Table 30. The pucch-CSI-ResourceList parameter may include a list of PUCCH resources BWP-wise for a cell or a CC to transmit the corresponding CSI report. The PUCCH resource may be a resource belonging to the PUCCH format 2, the PUCCH format 3, or the PUCCH format 4.
For PUCCH resource, a transmission period and an offset may be configured through reportSlotConfig of Table 30.
In the case of HARQ-ACK transmission, a resource set of a PUCCH resource to be transmitted according to the payload of UCI including the HARQ-ACK may be selected first. In other words, a PUCCH resource set having a minimum payload no less than the UCI payload may be selected. Next, a PUCCH resource in the PUCCH resource set may be selected through a PUCCH resource indicator (PRI) in DCI that schedules a TB corresponding to the HARQ-ACK, and the PRI may be a PUCCH resource indicator specified in Table 6 or Table 7. The relationship between the PRI and the PUCCH resource selected by the PUCCH resource set may be as in Table 31 shown below.
If the number of PUCCH resources in the selected PUCCH resource set is greater than 8, the PUCCH resource may be selected by Equation 2.
In Equation 2, rPUCCH may denote an index of a selected PUCCH resource in a PUCCH resource set, RPUCCH may denote the number of PUCCH resources belonging to the PUCCH resource set, ΔpRI may denote a PRI value, NCCE,p may denote the total number of CCEs of a CORESET p to which reception DCI belongs, and nCCE,p may denote a first CCE index for the reception DCI.
A time point when the corresponding PUCCH resource is transmitted may be a K1 slot after from the TB transmission corresponding to the HARQ-ACK. A candidate of a K1 value may be configured via an higher layer and more specifically, may be set to a dl-DataToUL-ACK parameter in PUCCH-Config specified in Table 21. A K1 value of the candidates may be selected by a PDSCH-to-HARQ feedback timing indicator in the DCI that schedules a TB and the value may be specified in Table 5 or Table 6. In addition, the unit of the K1 value may be a slot unit or a sub-slot unit. In this case, the sub-slot may be a unit of length less than a slot, and one or a plurality of symbols may constitute one sub-slot.
In a 5G mobile communication service, an additional coverage expansion technique is adopted compared to an LTE communication service. However, in the actual 5G mobile communication service, a TDD system that is suitable for a service with a generally high UL traffic proportion may be used. In addition, as a center frequency increases to increase a frequency band, the coverage of the base station and the terminal may decrease, and thereby, the coverage enhancement may be a core requirement for the 5G mobile communication service. In particular, because transmission power of the terminal is generally lower than transmission power of the BS and a proportion of DL is higher than that of UL in the time domain to support a service having a higher DL traffic portion, the coverage enhancement of a UL channel may be the core requirement of the 5G mobile communication service. For a method of physically enhancing coverage of a UL channel of a terminal and a base station, methods of increasing a time resource of a UL channel, decreasing a center frequency, and increasing the transmission power of a terminal may exist. However, changing a frequency may be limited since a frequency band is determined for each network operator. In addition, since the maximum transmission power of the terminal is determined by regulations to reduce interference, increasing the maximum transmission power of the terminal may be limited to enhance the coverage.
Therefore, to enhance the coverage of the base station and the terminal, the resources of UL and DL in the time domain may be divided according to the traffic ratio of UL and DL as in the time division duplex (TDD) system, and the resources of UL and DL in a frequency domain may also be divided as a frequency domain division duplex (FDD) system. In an embodiment, a system that may flexibly divide the UL resource and the DL resource in the time domain and the frequency domain may be referred to as a cross-division duplex (XDD) system, a flexible TDD system, a hybrid TDD system, a TDD-FDD system, and a hybrid TDD-FDD system. For ease of description, the disclosure describes it as the XDD system. According to an embodiment, in XDD, X may be time or frequency.
The XDD configuration may be broadcasted through an SIB, may be configured through RRC signaling or higher layer signaling, or may be configured through MAC CE or DCI, or a combination thereof. In an embodiment, the XDD configuration may be configured to indicate the time or frequency resource used as the UL resource and the DL resource for the XDD system by each cell in a similar method to TDD UL-DL configuration. In an embodiment, the XDD configuration may be configured based on XDD BWP configuration information as a separate XDD BWP is defined for the XDD system or may be configured by configuring a portion of a slot or a symbol of DL BWP configuration or UL BWP configuration to the XDD and using as an XDD slot or a symbol in which both UL and DL resources exist. Depending on the configuration method, the XDD configuration may be configured with a corresponding PUCCH resource or may not have a corresponding PUCCH resource. Accordingly, hereinafter, when a PUCCH resource configuration corresponding to the XDD configuration exists, the PUCCH resource may be construed as a resource based on the corresponding PUCCH resource configuration. On the other hand, if there is no PUCCH resource configuration corresponding to the XDD configuration, the PUCCH resource may be determined based on PUCCH resource configuration that is configured for an initial UL BWP, may be determined based on configured PUCCH resource configuration that is configured for a most recently activated UL BWP, may be determined based on PUCCH resource configuration separately defined for the XDD system, or may be determined based on PUCCH resource configuration of a default BWP that is separately defined or configured for the XDD system.
In the example shown in
XDD-ConfigCommon of Table 32 shown above may denote the XDD common configuration information and may include reference SubcarrierSpacing (SCS), a pattern 1, and a pattern 2. The pattern 2 may be a pattern that appears after the pattern 1 is terminated. An XDD-pattern may be configured for each of the pattern 1 and the pattern 2.
The XDD-pattern of Table 32 shown above may include a period in which the pattern continues (XDD-TransmissionPeriodicity), the number of consecutive DL slots (nrofDownlinkSlots), the number of consecutive DL symbols (nrofDownlinkSymbols), the number of consecutive XDD slots (nrofXDDSlots), the number of consecutive XDD symbols (nrofXDDSymbols), a frequency location and bandwidth of the XDD (locationAndBandwidthforXDD), a parameter (Centerfrequencyposition) indicating whether locationAndBandwidthforXDD needs to be interpreted based on a center frequency of the frequency band, the number of consecutive UL slots (nrofUplinkSlots), and the number of consecutive UL symbols (nrofUplinkSymbols).
To the XDD-TransmissionPeriodicity, for example, 0.5 ms, 0.625 ms, 1 ms, 1.25 ms, 2 ms, 2.5 ms, 5 ms, or 10 ms may be set.
According to an embodiment, as shown in
In
According to an embodiment, the Centerfrequency position may be set to true or false. To locationAndBandwidthforXDD, information showing a frequency location and bandwidth of the XDD may be. For example, information showing a frequency location and bandwidth of the XDD may be set to locationAndBandwidthforXDD according to a bitmap scheme or an RIV scheme. In the example of
UE-specific XDD configuration is described with reference to
In the example of
XDD-ConfigDedicated of Table 33 shown above may represent the XDD-dedicated configuration information. XDD-ConfigDedicated may include slotSpecificConfigurationsToAddModList, and a list of XDD slot configurations (XDD-SlotConfig) may be set to slotSpecificConfigurationsToAddModList.
XDD-SlotConfig may include a slot index (slotIndex), locationAndBandwidthforXDD, and Centerfrequency position. To slotIndex, an identifier of the slot may be set. For example, the base station 810 may set an identifier of a slot to slotIndex to set to an XDD slot. The descriptions provided with reference to
XDD-SlotConfig may include the number of consecutive DL symbols (nrofDownlinkSymbols), the number of consecutive XDD symbols (nrofXDDSymbols), and the number of consecutive UL symbols (nrofUplinkSymbols).
According to an embodiment, as shown in
According to an embodiment, the number (e.g., 3) of consecutive DL symbols from the start of the slot a may be set to nrofDownlinkSymbols, the number (e.g., 5) of consecutive XDd symbols after the last DL symbol (the second symbol) may be set to nrofXDDSymbols, and the number (e.g., 3) of inversely consecutive UL symbols from the end of the slot a may be set to nrofUplinkSymbols. According to another embodiment, the total number (e.g., 8) of the DL symbols and the XDD symbols may be set to nrofDownlinkSymbols, and the number (e.g., 5) of the XDD symbols may be set to nrofXDDSymbols. In this case, the terminal 820 may recognize that inversely consecutive five symbols from a seventh symbol are XDD symbols through nrofDownlinkSymbols and nrofXDDSymbols, and may recognize that the first three symbols from the start of the slot a are DL symbols. The number (e.g., 3) of inversely consecutive UL symbols from the end of the slot a may be set to nrofUplinkSymbols.
According to an embodiment, the base station 810 may configure a UE-specific XDD slot (e.g., the slot a of
The dynamic XDD configuration is described with reference to
In the example of
According to an embodiment, the DCI 1010 may include, for example, an SFI set to one of formats n−x to n−x+a of Table 34 shown below.
In [Table 34] shown above, formats 0 to 55 may correspond to the formats 0 to 55 of Table 21 shown above.
The formats n−x to n−x+a may indicate an XDD slot and may be expressed by an XDD slot format indicator (XFI).
According to an embodiment, the base station 810 may transmit SFI entries (e.g., the formats n−x to n−x+a) among the SFI entries (formats 0 to n−x+a) of Table 34 shown above to the terminal 820 through RRC or SIB.
According to an embodiment, the base station 810 may set a valid duration (e.g., PDCCH monitoring periodicity) of the XDD configuration that is dynamically set, and when the set valid duration has elapsed, the base station 810 may transmit the SFI (or an XFI) to a terminal 802 (or a cell). For example, the base station 810 may set a parameter (e.g., the parameter of Table 19 shown above) for a search space for a PDCCH to the terminal 820 through higher layer signaling. In this case, a PDCCH monitoring period may be set. The base station 820 may determine or set the PDCCH monitoring period to be the valid duration of the dynamically set XDD configuration. When the valid duration has elapsed, the base station 810 may transmit an SFI to a cell.
In the example of
The valid duration may elapse and in the slot 2, the base station 810 may transmit an XFI to the cells 0 and 1. In this case, the base station 810 may transmit different XFIs to the cells 0 and 1.
The cells 0 and 1 may each configure a slot according to a slot format indicated by the received XFI. As shown in
In the example of
In an embodiment, the DL BWP configuration information may include, for example, the information in Table 35 shown below.
BWP-Downlink of Table 35 shown above may represent information to configure XDD based on a DL BWP. BWP-Downlink may include an ID (bwp-Id) of the DL BWP, a BWP ID (bwp-Id for UL) for UL, information (bwp-Common) to configure a common parameter of the DL BWP, and information (bwp-Dedicated) to configure a dedicated parameter of the DL BWP. The configured UL BWP through Table 35 shown above may be an UL BWP for XDD, and thereby, may be referred to as an XDD UL BWP.
The BWP of Table 35 shown above may include a parameter (XDD) to indicate that the DL BWP configuration information is for the configuration of the XDD, information (locationAndBandwidth) on a frequency location and bandwidth of the UL BWP (or the XDD UL BWP), subcarrierSpacing, and cyclicPrefix. According to an embodiment, the terminal 820 may identify the frequency location and bandwidth of the XDD UL BWP through locationAndBandwidth. For example, the terminal 820 may assume that center frequencies of the DL BWP and the XDD UL BWP activated in the same slot are the same. The terminal 820 may identify that a frequency location and bandwidth apart from the center frequency location of the activated DL BWP by a configuration value of locationAndBandwidth correspond to the XDD UL BWP. For example, when 1 is set to locationAndBandwidth, the terminal 820 may identify that the frequency location and bandwidth apart from the center frequency of the activated DL BWP by 1 correspond to the XDD UL BWP.
According to an embodiment, the parameter (XDD) may be omitted from the BWP in the table 35 shown above.
According to an embodiment, Centerfrequency position may be further included in the BWP of Table 35 shown above. The Centerfrequency position may represent whether locationAndBandwidth needs to be interpreted based on the center frequency location of the DL BWP.
According to an embodiment, when an ID is set to “bwp-Id for UL” in the DL BWP configuration information received from the base station 810, the terminal 820 may recognize that a UL of the ID set to “bwp-Id for UL” is an XDD UL. In other words, when an ID is set to “bwp-Id for UL” in the DL BWP configuration information received from the base station 810, the terminal 820 may recognize that the received DL BWP configuration information is for the XDD configuration. According to another embodiment, when an ID is not set to “bwp-Id for UL” in the DL BWP configuration information received from the base station 810 or “bwp-Id for UL” is omitted, the terminal 820 may recognize that the received DL BWP configuration information is for the configuration of the DL BWP.
According to an embodiment, the UL BWP configuration information may include, for example, information in Table 36 shown below.
BWP-Uplink of [Table 36] may represent information to configure XDD based on a UL BWP. BWP-Uplink may include an ID (bwp-Id) of the UL BWP, a BWP ID (bwp-Id for DL) for the DL, information (bwp-Common) to set a common parameter of the UL BWP, and information (bwp-Dedicated) to set a dedicated parameter of the UL BWP. The DL BWP configured through Table 36 shown above may be a DL BWP for XDD, and thereby, may be referred to as an XDD DL BWP.
The BWP of Table 36 may include a parameter (XDD) to indicate that the UL BWP configuration information is for the configuration of the XDD, information (locationAndBandwidth) on a frequency location and bandwidth of the DL BWP (or the XDD DL BWP), subcarrierSpacing, and cyclicPrefix. According to an embodiment, the terminal 820 may identify the frequency location and bandwidth of the XDD DL BWP through locationAndBandwidth. For example, the terminal 820 may assume that center frequencies of the UL BWP and the XDD DL BWP activated in the same slot are the same. The terminal 820 may identify that a frequency location and bandwidth apart from the center frequency location of the activated UL BWP by a configuration value of locationAndBandwidth correspond to the XDD DL BWP.
According to an embodiment, when an ID is set to “bwp-Id for DL” in the UL BWP configuration information received from the base station 810, the terminal 820 may recognize that a DL of the ID set to “bwp-Id for DL” is an XDD DL. In other words, when an ID is set to “bwp-Id for DL” in the UL BWP configuration information received from the base station 810, the terminal 820 may recognize that the received UL BWP configuration information is for the XDD configuration. According to another embodiment, when an ID is not set to “bwp-Id for DL” in the UL BWP configuration information received from the base station 810 or “bwp-Id for DL” is omitted, the terminal 820 may recognize that the received UL BWP configuration information is for the configuration of the UL BWP.
BWP switching when a DL BWP is linked to an XDD UL BWP is described with reference to
In the example of
In an embodiment, a DL BWP and a UL BWP having the same BWP ID and center frequency may be linked to each other. For example, an ID of the DL BWP 0 and an ID of the UL BWP 0 may be the same as 0, and a center frequency of the DL BWP 0 and a center frequency of the UL BWP 0 may be the same. The DL BWP 0 and the UL BWP 0 may be linked to each other. Similarly, the DL BWP 1 and the UL BWP may be linked to each other, and the DL BWP 2 and the UL BWP 2 may be linked to each other.
In the example of
In an embodiment, the UL BWP 3 may be linked to the initial DL BWP (or the default DL BWP). In another embodiment, the UL BWP 3 may be linked to a DL BWP according to a hardcoded scheme. For example, according to the hardcoded scheme, it may be determined to link a DL BWP having an ID of n to a UL BWP having an ID of (n+a). When a is 2, the UL BWP 3 may be linked to the DL BWP 1. In another embodiment, the terminal 820 may receive which DL BWP is linked to the XDD UL BWP through an SIB or RRC from the base station 810.
In a slot k 1210, the DL BWP 1 and the UL BWP 1 may be activated.
In the slot k 1210, the terminal 820 may perform DL communication and/or UL communication with the base station 810 according to a TDD scheme.
In the slot k 1210, the terminal 820 may receive UL DCI from the base station 810. The received UL DCI may include a BPI, and the BPI may indicate the UL BWP 3. In other words, the base station 810 may instruct the terminal 820 to perform a BWP change from the UL BWP 1 to the UL BWP 3 using the BPI. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k 1210. The UL BWP 3 (XDD UL BWP) may be activated in a slot k+1 1220. When the UL BWP 3 is linked to the initial DL BWP (or the default DL BWP), the DL BWP 0 may be activated in the slot k+1 1220.
The DL BWP 0 may be the UE bandwidth 1240, and thereby, a portion (a center frequency band) of the DL BWP 0 may overlap the UL BWP 3 in the slot k+1 1220. In this case, according to the priority between a UL signal/channel and a DL signal/channel, a signal/channel of lower priority may be dropped or rate matching may be performed. A related description is provided with reference to
In the slot k+1 1220, the terminal 820 may perform DL communication with the base station 810 via the DL BWP 0, and may perform UL communication with the base station 810 via the UL BWP 3. One or more symbols of the slot k+1 1220 may simultaneously include a DL resource and a UL resource, and thereby, the slot k+1 1220 may correspond to an XDD slot.
In the slot k+1 1220, the terminal 820 may receive DL DCI from the base station 810. The received DL DCI may include a BPI and the BPI may indicate the DL BWP 2. In other words, the base station 810 may instruct the terminal 820 to perform a BWP change from the DL BWP 0 to the DL BWP 2 using the BPI. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k+1 1220. The DL BWP 2 may be activated in a slot k+2 1230, and the UL BWP 2 linked to the DL BWP 2 may be activated.
In the slot k+2 1220, the terminal 820 may perform DL communication and UL communication with the base station 810 according to the TDD scheme.
BWP switching when a DL BWP is not linked to an XDD UL BWP is described with reference to
In the example of
In a slot k 1310, the DL BWP 1 and the UL BWP 1 may be activated.
In the slot k 1310, the terminal 820 may perform DL communication and UL communication with the base station 810 according to the TDD scheme.
In the slot k 1310, the terminal 820 may receive UL DCI from the base station 810. The received UL DCI may include a BPI, and the BPI may indicate the UL BWP 3. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k 1310. In a slot k+1 1320, the UL BWP 3 may be activated. In the example of
In the slot k+1 1320, the terminal 820 may simultaneously perform DL communication and UL communication with the base station 810. The slot k+1 1320 may correspond to an XDD slot.
In the slot k+1 1320, the terminal 820 may receive DL DCI from the base station 810. The received DL DCI may include a BPI and the BPI may indicate the DL BWP 2. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k+1 1220. The DL BWP 2 may be activated in a slot k+2 1330, and the UL BWP 2 linked to the DL BWP 2 may be activated.
In the slot k+2 1320, the terminal 820 may perform DL communication and UL communication with the base station 810 according to the TDD scheme.
Timer-based BWP switching is described with reference to
In the example of
In a slot k 1410, the DL BWP 1 and the UL BWP 1 may be activated.
In the slot k 1410, the terminal 820 may perform DL communication and UL communication with the base station 810 according to the TDD scheme.
In the slot k 1410, the terminal 820 may receive UL DCI from the base station 810. The BPI in the received UL DCI may indicate the UL BWP 3. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k 1410. The UL BWP 3 (XDD UL BWP) may be activated in a slot k+1 1420. In the example of
In the slot k+1 1420, the terminal 820 may simultaneously perform DL communication and UL communication with the base station 810. The slot k+1 1420 may correspond to an XDD slot.
A valid duration of the activated XDD BWP may be set. The valid duration may elapse while the terminal 820 does not receive an instruction for the BWP change from the base station 810.
In an embodiment, when the valid duration of the activated XDD BWP has elapsed, a recently activated DL BWP and a UL BWP before a XDD slot may be activated in a slot after the valid duration. For example, in the example of
In another embodiment, when the valid duration of the activated XDD BWP has elapsed, the initial DL BWP (or the default DL BWP) and the initial UL BWP (or the default UL BWP) may be activated. In the example of
In another embodiment, when the valid duration of the activated XDD BWP has elapsed, a preset DL BWP and a UL BWP may be activated. For example, when the valid duration has elapsed, the DL BWP 1 and the UL BWP 2 may be preset to be activated. When the valid duration has elapsed, the DL BWP 1 and the UL BWP 2 may be activated in the slot k+2 1430.
The BWP switching when an event occurs is described with reference to
In the example of
The DL BWP 1 and the UL BWP 1 may be activated in a slot k 1610.
In the slot k 1610, the terminal 820 may receive DL DCI from the base station 810. The received UL DCI may include a PDSCH-to-HARQ_feedback timing indicator, and the PDSCH-to-HARQ_feedback timing indicator may indicate a PUCCH resource and/or a DL symbol of the UL BWP 3. In other words, the terminal 820 may know that a resource to which HARQ ACK/NACK is transmitted for a PDSCH corresponds to the UL BWP 3 through the PDSCH-to-HARQ_feedback timing indicator. By considering latency TBWP required to change the BWP, the BWP change may be completed in the slot k 1610. In this case, the UL BWP 3 may be activated in a slot k+1 1620, and a DL BWP (e.g., the DL BWP 0) linked to the UL BWP 3 may be activated. As another example, the terminal 820 may know whether a resource to which the HARQ ACK/NACK is transmitted for the PDSCH and a resource for transmitting the CSI correspond to the UL BWP 3 through the PDSCH-to-HARQ_feedback timing indicator. When the resource to which the HARQ ACK/NACK is transmitted for the PDSCH and the resource for transmitting the CSI correspond to the UL BWP 3 and it is possible to complete a BWP change in the slot k 1610, the UL BWP 3 may be activated in the slot k+1 1620, and a DL BWP (e.g., the DL BWP 0) linked to the UL BWP 3 may be activated.
According to an embodiment, in the slot k+1 1620, when the terminal 820 transmits PDSCH-to-HARQ feedback (or both the PDSCH-to-HARQ feedback and the CSI) to the base station 810 through the UL BWP 3, the terminal 820 may return to last BWP configuration (e.g., the BWP configuration of a previous slot of the XDD slot). For example, after transmitting the PDSCH-to-HARQ feedback (or both the PDSCH-to-HARQ feedback and the CSI) through the UL BWP 3 in the slot k+1 160, the terminal 820 may configure a remaining symbol period (e.g., last six symbols of the slot k+1 1620) of the slot k+1 1620 according to the last BWP configuration (e.g., the configuration of the last six symbols of the slot k 1610). Accordingly, as the example shown in
According to an embodiment, as described with reference to
Referring to
In the example of
When the resource overlap occurs, it may be processed according to priority order between a UL channel/signal and a DL channel/signal. Table 37 shows an example of the priority.
In [Table 37], the priority may decrease from top to bottom. The priorities of “SS/PBCH on the Pcell”, “CORESET0/Searchspace0”, and “PDSCH associated with P-RNTI, RA-RNTI, or SI-RNTI on the Pcell” may be the highest, the priority of “PRACH transmission on the PCell” may be the second highest, and the priority of “SRS transmission, with aperiodic SRS having higher priority than semi-persistent and/or periodic SRS, or PRACH transmission on a serving cell other than the PCell” may be the lowest. The priorities of “SS/PBCH on the Pcell”, “CORESET0/Searchspace0”, and “PDSCH associated with P-RNTI, RA-RNTI, or SI-RNTI on the Pcell” may be the same.
According to an embodiment, when a resource overlap (e.g., a resource overlap between the XDD UL BWP 1720 and the DL BWP 0 1710) between a UL resource and a DL resource occurs, the terminal 820 may drop one with a lower priority between a UL channel/signal or a DL channel/signal. For example, the terminal 820 may be scheduled to receive a PDSCH associated with C-RNTI from the base station 810 through the DL BWP 0 1710 in the slot 1700 and may be scheduled to perform PUCCH transmission with CSI through the XDD UL BWP 1720. According to Table 37, the priority of PDSCH associated with C-RNTI may be lower than the priority of PUCCH transmission with CSI. In the slot 1700, the terminal 820 may drop PDSCH associated with C-RNTI and may perform PUCCH transmission with CSI first. The terminal 820 may transmit NACK for PDSCH associated with C-RNTI to the base station 810 according to the drop of PDSCH associated with C-RNTI.
According to an embodiment, when a resource overlap (e.g., a resource overlap between the XDD UL BWP 1720 and the DL BWP 0 1710) between a UL resource and a DL resource occurs, the terminal 820 may perform rate matching on one with a lower priority between a UL channel/signal and a DL channel/signal.
According to another embodiment, when a resource overlap (e.g., a frequency overlap between the XDD UL BWP 1720 and the DL BWP 0 1710) between a UL resource and a DL resource occurs, the terminal 820 may calculate a ratio (e.g., a ratio of an overlapping UL frequency band in the DL BWP or a ratio of an overlapping DL frequency band in the UL BWP) of an overlapping resource. For example, in the example of
Referring to
In operation 1820, the terminal 820 may receive first UL BWP configuration information including an ID of a first UL BWP (e.g., the UL BWP 1 of
In operation 1830, the terminal 820 may receive second DL BWP configuration information including an ID of a second DL BWP and an ID of a second UL BWP (e.g., the UL BWP 3 of
In operation 1840, the terminal 820 may recognize that the second DL BWP configuration information is information (e.g., XDD configuration information) for DL-UL configuration of the terminal 820 through the ID of the second UL BWP.
The first DL BWP and the first UL BWP may be configured in a first slot (e.g., the slot k 1210 of
According to an embodiment, the terminal 820 may receive UL DCI (e.g., the UL DCI with BWP ID=3 of
According to an embodiment, the terminal 820 may receive UL DCI (e.g., the UL DCI with BWP ID=3 of
According to an embodiment, the terminal 820 may receive UL DCI (e.g., the UL DCI with BWP ID=3 of
According to an embodiment, the terminal 820 may receive DL DCI from the base station 820 in the first slot (e.g., the slot k 1610 of
According to an embodiment, when an overlap between an allocated DL frequency resource (e.g., the DL BWP 0 1710 of
According to an embodiment, when overlap between an allocated DL frequency resource (e.g., the DL BWP 0 1710 of
According to an embodiment, the terminal 820 may receive XDD configuration information (e.g., common configuration information, dedicated configuration information, and an SFI) on the configuration of a UL resource and a DL resource from the base station 810. In an XDD slot (or an XDD symbol) based on the received XDD configuration information, the terminal 820 may be able to simultaneously perform DL communication and UL communication with the base station 810.
According to an embodiment, the terminal 820 may receive common configuration information (e.g., XDD-ConfigCommon of Table 32) on the configuration of a UL resource and a DL resource from the base station 810. The received common configuration information may include, for example, the number of DL slots, the number of DL symbols, the number of XDD slots, the number of XDD symbols, the number of UL slots, the number of UL symbols, information on a frequency location of an XDD and a bandwidth, and a parameter (e.g., Center frequency position of Table 32) whether a frequency location of the XDD needs to be interpreted based on a center frequency location of a frequency band allocated to the terminal 820. In the XDD slot or the XDD symbol according to the received first common configuration information, the terminal 820 may simultaneously perform DL communication and UL communication with the base station 810.
According to an embodiment, the terminal 820 may receive dedicated configuration information (e.g., XDD-ConfigDedicated of Table 33) on the configuration of a UL resource and a DL resource from the base station 810. The received dedicated configuration information may include, for example, an index of a slot (e.g., the slot a of
According to an embodiment, the terminal 820 may receive a first SFI from the base station 810, and may identify that a third slot (e.g., the slot 0 for the cell 0 of
According to an embodiment, when a valid duration has elapsed, the terminal 820 may receive a second SFI from the base station 810, and may identify that a fourth slot (e.g., the slot 2 of the cell 0 of
According to an embodiment, the valid duration may be determined based on a PDCCH monitoring period.
The embodiments described with reference to
Referring to
According to an embodiment, the RF transceiver 1920 may transmit and receive a signal to or from the terminal 820 through the antenna 1910. The transmitted and received signal may include, for example, control information and data.
According to an embodiment, the RF transceiver 1920 may receive a baseband signal from the processor 1930, may convert the baseband signal into an RF signal, and may transmit the RF signal to the terminal 820 through the antenna 1910. The RF transceiver 1920 may receive an RF signal of the terminal 820 through the antenna 1910, may convert the RF signal into a baseband signal, and may transmit the baseband signal to the processor 1930.
According to an embodiment, the processor 1930 may cause a base station (e.g., the base station 810, 1900) to perform an operation.
According to an embodiment, the base station 1900 may transmit first DL BWP configuration information including an ID of a first DL BWP to the terminal 820. The base station 1900 may transmit first UL BWP configuration information including an ID of a first UL BWP to the terminal 820. The base station 1900 may transmit, to the terminal 820, second DL BWP configuration information including an ID of a second DL BWP and an ID of a second UL BWP for DL-UL configuration of the terminal 820. In a first slot, the first DL BWP and the first UL BWP may be temporally separated from each other and the base station 1900 and the terminal 820 may be unable to simultaneously perform DL communication and UL communication. In a second slot, the base station 1900 and the terminal 820 may be able to perform DL communication and UL communication based on the second DL BWP configuration information.
According to an embodiment, the base station 1900 may transmit UL DCI including a BWP indicator indicating the second UL BWP from the first slot to the terminal 820. If a DL BWP linked to the second UL BWP exists, a BWP change from the first UL BWP to the second UL BWP may be performed, a BWP change from the first DL BWP to the linked DL BWP may be performed, the second UL BWP may be activated in the second slot, and the DL BWP linked to the second UL BWP may be activated. If a DL BWP linked to the second UL BWP does not exist, a BWP change from the first UL BWP to the second UL BWP may be performed, the first DL BWP may be maintained, and the second UL BWP and the first DL BWP may be activated in the second slot.
According to an embodiment, a BWP change from the first UL BWP to the second UL BWP may be performed, and after a BWP change from the first DL BWP to the DL BWP linked to the second UL BWP is performed, a valid duration may elapse. In this case, a BWP change from the second UL BWP to the first UL BWP or an initial UL BWP may be performed, and a BWP change from the linked DL BWP to the first DL BWP or an initial DL BWP may be performed.
According to an embodiment, the base station 1900 may transmit DL DCI including a first feedback timing indicator corresponding to the second UL BWP from the first slot to the terminal 820. A BWP change from the first UL BWP to the second UL BWP may be performed and a BWP change from the first DL BWP to the DL BWP linked to the second UL BWP may be performed. When the valid duration has elapsed, a BWP change from the second UL BWP to the first UL BWP or the initial UL BWP may be performed, and a BWP change from the DL BWP to the first DL BWP or the initial DL BWP may be performed.
The embodiments described with reference to
Referring to
According to an embodiment, the RF transceiver 2020 may transmit and receive a signal to or from the base station 810, 1900 through the antenna 2010. The transmitted and received signal may include, for example, control information and data.
According to an embodiment, the RF transceiver 2020 may receive a baseband signal from the processor 2030, may convert the baseband signal into an RF signal, and may transmit the RF signal to the base station 810, 1900 through the antenna 2010. The RF transceiver 2020 may receive an RF signal of the base station 810, 1900 through the antenna 2010, may convert the RF signal into a baseband signal, and may transmit the baseband signal to the processor 2030.
According to an embodiment, the processor 2030 may cause a terminal (e.g., the terminal 820, 2000) to perform an operation.
According to an embodiment, the processor 2030 may receive first DL BWP configuration information including an ID of a first DL BWP from the base station 810, 1900 through the antenna 2010 and the RF transceiver 2020. The processor 2030 may receive first UL BWP configuration information including an ID of a first UL BWP from the base station 810, 1900 through the antenna 2010 and the RF transceiver 2020. The processor 2030 may receive second DL BWP configuration information including an ID of a second DL BWP and an ID of a second UL BWP from the base station 810, 1900. The processor 1830 may recognize that the second DL BWP configuration information is information (e.g., XDD configuration information) for DL-UL configuration of the terminal 2000 through the ID of the second UL BWP.
The embodiments described with reference to
Referring to
The processor 2120 may execute, for example, software (e.g., a program 2140) to control at least one other component (e.g., a hardware or software component) of the electronic device 2101 connected to the processor 2120, and may perform various data processing or computation. According to one embodiment, as at least a part of data processing or computation, the processor 2120 may store a command or data received from another component (e.g., the sensor module 2176 or the communication module 2190) in a volatile memory 2132, process the command or the data stored in the volatile memory 2132, and store resulting data in a non-volatile memory 2134. According to one embodiment, the processor 2120 may include a main processor 2121 (e.g., a central processing unit (CPU) or an application processor) or an auxiliary processor 2123 (e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently of, or in conjunction with the main processor 2121. For example, when the electronic device 2101 includes the main processor 2121 and the auxiliary processor 2123, the auxiliary processor 2123 may be adapted to consume less power than the main processor 2121 or to be specific to a specified function. The auxiliary processor 2123 may be implemented separately from the main processor 2121 or as a part of the main processor 2121.
The auxiliary processor 2123 may control at least some of functions or states related to at least one (e.g., the display module 2160, the sensor module 2176, or the communication module 2190) of the components of the electronic device 2101, instead of the main processor 2121 while the main processor 2121 is in an inactive (e.g., sleep) state or along with the main processor 2121 while the main processor 2121 is in an active state (e.g., executing an application). According to one embodiment, the auxiliary processor 2123 (e.g., an ISP or a CP) may be implemented as a portion of another component (e.g., the camera module 2180 or the communication module 2190) that is functionally related to the auxiliary processor 2123. According to one embodiment, the auxiliary processor 2123 (e.g., an NPU) may include a hardware structure specified for artificial intelligence model processing. An AI model may be generated by machine learning. Such learning may be performed by, for example, the electronic device 2101 in which artificial intelligence is performed, or performed via a separate server (e.g., the server 2108). Learning algorithms may include, but are not limited to, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The AI model may include a plurality of artificial neural network layers. An artificial neural network may include, for example, a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more thereof, but is not limited thereto. The AI model may additionally or alternatively include a software structure other than the hardware structure.
The memory 2130 may store various data used by at least one component (e.g., the processor 2120 or the sensor module 2176) of the electronic device 2101. The various pieces of data may include, for example, software (e.g., the program 2140) and input data or output data for a command related thereto. The memory 2130 may include the volatile memory 2132 or the non-volatile memory 2134.
The program 2140 may be stored as software in the memory 2130 and may include, for example, an operating system (OS) 2142, middleware 2144, or an application 2146.
The input module 2150 may receive a command or data to be used by another component (e.g., the processor 2120) of the electronic device 2101, from the outside (e.g., a user) of the electronic device 2101. The input module 2150 may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).
The sound output module 2155 may output a sound signal to the outside of the electronic device 2101. The sound output module 2155 may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing record. The receiver may be used to receive an incoming call. According to one embodiment, the receiver may be implemented separately from the speaker or as a part of the speaker.
The display module 2160 may visually provide information to the outside (e.g., a user) of the electronic device 2101. The display module 2160 may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, the hologram device, and the projector. According to one embodiment, the display module 2160 may include a touch sensor adapted to sense a touch, or a pressure sensor adapted to measure an intensity of a force incurred by the touch.
The audio module 2170 may convert a sound into an electrical signal or vice versa. According to one embodiment, the audio module 2170 may obtain the sound via the input module 2150 or output the sound via the sound output module 2155 or an external electronic device (e.g., the electronic device 2102 such as a speaker or a headphone) directly or wirelessly connected to the electronic device 2101.
The sensor module 2176 may detect an operational state (e.g., power or temperature) of the electronic device 2101 or an environmental state (e.g., a state of a user) external to the electronic device 2101, and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module 2176 may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.
The interface 2177 may support one or more specified protocols to be used for the electronic device 2101 to be coupled with the external electronic device (e.g., the electronic device 2102) directly (e.g., by wire) or wirelessly. According to one embodiment, the interface 2177 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.
The connecting terminal 2178 may include a connector via which the electronic device 2101 may be physically connected to an external electronic device (e.g., the electronic device 2102). According to one embodiment, the connecting terminal 2178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).
The haptic module 2179 may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or an electrical stimulus which may be recognized by a user via his or her tactile sensation or kinesthetic sensation. According to one embodiment, the haptic module 2179 may include, for example, a motor, a piezoelectric element, or an electric stimulator.
The camera module 2180 may capture a still image and moving images. According to one embodiment, the camera module 2180 may include one or more lenses, image sensors, image signal processors, or flashes.
The power management module 2188 may manage power supplied to the electronic device 2101. According to one embodiment, the power management module 2188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).
The battery 2189 may supply power to at least one component of the electronic device 2101. According to one embodiment, the battery 2189 may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell.
The communication module 2190 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 2101 and the external electronic device (e.g., the electronic device 2102, the electronic device 2104, or the server 2108) and performing communication via the established communication channel. The communication module 2190 may include one or more communication processors that are operable independently of the processor 2120 (e.g., an AP) and that support a direct (e.g., wired) communication or a wireless communication. According to one embodiment, the communication module 2190 may include a wireless communication module 2192 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 2194 (e.g., a local area network (LAN) communication module, or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device 2104 via the first network 2198 (e.g., a short-range communication network, such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or the second network 2199 (e.g., a long-range communication network, such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multi components (e.g., multi chips) separate from each other. The wireless communication module 2192 may identify and authenticate the electronic device 2101 in a communication network, such as the first network 2198 or the second network 2199, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the SIM 2196.
The wireless communication module 2192 may support a 5G network after a 4G network, and a next-generation communication technology, e.g., a new radio (NR) access technology. The NR access technology may support enhanced mobile broadband (eMBB), massive machine type communications (mMTC), or ultra-reliable and low-latency communications (URLLC). The wireless communication module 2192 may support a high-frequency band (e.g., a mmWave band) to achieve, e.g., a high data transmission rate. The wireless communication module 2192 may support various technologies for securing performance on a high-frequency band, such as, e.g., beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), an array antenna, analog beam-forming, or a large scale antenna. The wireless communication module 2192 may support various requirements specified in the electronic device 2101, an external electronic device (e.g., the electronic device 2104), or a network system (e.g., the second network 2199). According to one embodiment, the wireless communication module 2192 may support a peak data rate (e.g., 20 Gbps or more) for implementing eMBB, loss coverage (e.g., 164 dB or less) for implementing mMTC, or U-plane latency (e.g., 0.5 ms or less for each of downlink (DL) and uplink (UL), or a round trip of 1 ms or less) for implementing URLLC.
The antenna module 2197 may transmit or receive a signal or power to or from the outside (e.g., the external electronic device). According to one embodiment, the antenna module 2197 may include an antenna including a radiating element including a conductive material or a conductive pattern formed in or on a substrate (e.g., a printed circuit board (PCB)). According to one embodiment, the antenna module 2197 may include a plurality of antennas (e.g., array antennas). In such a case, at least one antenna appropriate for a communication scheme used in a communication network, such as the first network 2198 or the second network 2199, may be selected by, for example, the communication module 2190 from the plurality of antennas. The signal or power may be transmitted or received between the communication module 2190 and the external electronic device via the at least one selected antenna. According to one embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 2197.
According to various embodiments, the antenna module 2197 may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a PCB, an RFIC disposed on a first surface (e.g., a bottom surface) of the PCB or adjacent to the first surface and capable of supporting a designated a high-frequency band (e.g., the mmWave band), and a plurality of antennas (e.g., array antennas) disposed on a second surface (e.g., a top or a side surface) of the PCB, or adjacent to the second surface and capable of transmitting or receiving signals in the designated high-frequency band.
At least some of the above-described components may be coupled mutually and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).
According to one embodiment, commands or data may be transmitted or received between the electronic device 2101 and the external electronic device 2104 via the server 2108 coupled with the second network 2199. Each of the external electronic devices 2102 and 2104 may be a device of the same type as or a different type from the electronic device 2101. According to one embodiment, all or some of operations to be executed by the electronic device 2101 may be executed at one or more of the external electronic devices 2102, 2104, or 2108. For example, if the electronic device 2101 needs to perform a function or a service automatically, or in response to a request from a user or another device, the electronic device 2101, instead of, or in addition to, executing the function or the service, may request one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request, and may transfer an outcome of the performing to the electronic device 2101. The electronic device 2101 may provide the result, with or without further processing the result, as at least part of a response to the request. To this end, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device 2101 may provide ultra low-latency services using, e.g., distributed computing or mobile edge computing. In one embodiment, the external electronic device 2104 may include an Internet-of-things (IoT) device. The server 2108 may be an intelligent server using machine learning and/or a neural network. According to one embodiment, the external electronic device 2104 or the server 2108 may be included in the second network 2199. The electronic device 2101 may be applied to intelligent services (e.g., a smart home, a smart city, a smart car, or healthcare) based on 5G communication technology or IoT-related technology.
The electronic device according to embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. According to one embodiment of the disclosure, the electronic device is not limited to those described above.
It should be appreciated that embodiments of the disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. In connection with the description of the drawings, like reference numerals may be used for similar or related components. It is to be understood that a singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A, B, or C,” each of which may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as “first”, “second”, or “first” or “second” may simply be used to distinguish the component from other components in question, and may refer to components in other aspects (e.g., importance or order) is not limited. It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively,” as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., by wire), wirelessly, or via a third element.
As used in connection with embodiments of the disclosure, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, for example, “logic,” “logic block,” “part,” or “circuitry.” A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to one embodiment, the module may be implemented in a form of an application-specific integrated circuit (ASIC).
Embodiments as set forth herein may be implemented as software (e.g., the program 2140) including one or more instructions that are stored in a storage medium (e.g., an internal memory 2136 or an external memory 2138) that is readable by a machine (e.g., the electronic device 2101). For example, a processor (e.g., the processor 2120) of the machine (e.g., the electronic device 2101) may invoke at least one of the one or more instructions stored in the storage medium and execute it. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term “non-transitory” simply means that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.
According to one embodiment, a method according to embodiments of the disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., PlayStore™), or between two user devices (e.g., smartphones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as a memory of the manufacturer's server, a server of the application store, or a relay server.
According to embodiments, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities, and some of the multiple entities may be separately disposed in different components. According to embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2022-0049649 | Apr 2022 | KR | national |
| 10-2022-0056335 | May 2022 | KR | national |
This application is a by-pass continuation application of International Application No. PCT/KR2023/002578, filed on Feb. 23, 2023, which is based on and claims priority to Korean Patent Application Nos. 10-2022-0049649, filed on Apr. 21, 2022, and 10-2022-0056335, filed on May 9, 2022, in the Korean Intellectual Property Office, the disclosures of which are incorporated by reference herein their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/KR2023/002578 | Feb 2023 | WO |
| Child | 18921943 | US |
