CN117044342A - Terminal, wireless communication method and base station - Google Patents

Terminal, wireless communication method and base station Download PDF

Info

Publication number
CN117044342A
CN117044342A CN202180096279.6A CN202180096279A CN117044342A CN 117044342 A CN117044342 A CN 117044342A CN 202180096279 A CN202180096279 A CN 202180096279A CN 117044342 A CN117044342 A CN 117044342A
Authority
CN
China
Prior art keywords
tci state
pdcch
coreset
mac
pdsch
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202180096279.6A
Other languages
Chinese (zh)
Inventor
松村祐辉
永田聪
孙薇淇
王静
陈岚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NTT Docomo Inc filed Critical NTT Docomo Inc
Publication of CN117044342A publication Critical patent/CN117044342A/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/12Wireless traffic scheduling

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

One mode of the terminal of the present disclosure has: a reception unit that receives a MAC CE containing information related to activation of a transmission setting index (TCI) state of a physical shared channel; and a control unit configured to determine a TCI state corresponding to a physical shared channel based on a field related to a TCI state included in at least one of a plurality of pieces of downlink control information transmitted through the plurality of downlink control channels, when one physical shared channel is scheduled through the plurality of downlink control channels supporting application of different control resource set pool indexes.

Description

Terminal, wireless communication method and base station
Technical Field
The present disclosure relates to a terminal, a wireless communication method, and a base station in a next generation mobile communication system.
Background
In a universal mobile telecommunications system (Universal Mobile Telecommunications System (UMTS)) network, long term evolution (Long Term Evolution (LTE)) has been standardized for the purpose of further high-speed data rates, low latency, and the like (non-patent document 1). Further, for the purpose of further large capacity, high altitude, and the like of LTE (third generation partnership project (Third Generation Partnership Project (3 GPP)) Release (rel.) 8, 9), LTE-Advanced (3 GPP rel.10-14) has been standardized.
Subsequent systems of LTE (e.g., also referred to as fifth generation mobile communication system (5 th generation mobile communication system (5G)), 5g+ (plus), sixth generation mobile communication system (6 th generation mobile communication system (6G)), new Radio (NR)), 3gpp rel.15 later, and the like are also being studied.
Prior art literature
Non-patent literature
Non-patent document 1:3GPP TS 36.300V8.12.0"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); overall description; stage 2 (Release 8) ", 4 th 2010
Disclosure of Invention
Problems to be solved by the invention
In future wireless communication systems (e.g., beyond 5G/6G after rel.17), it is envisaged that one or more Transmission/Reception points (TRPs) transmit DL transmissions (e.g., PDSCH transmissions) to terminals (User terminals, user Equipment (UE)) using one or more panels (multi-panels).
In this case, it is assumed that repeated transmission (e.g., repetition) is applied to a specific channel (e.g., PDCCH). For example, consider that scheduling of DL transmission/UL transmission (e.g., one PDSCH/PUSCH) is controlled with multiple PDCCHs repeatedly transmitted (e.g., repetition) from a multi-panel/TRP being applied.
However, in the conventional system (for example, rel.16, before), there is no sufficient study on how to control the scheduling of PDSCH/PUSCH using PDCCH/DCI repeatedly transmitted from one or more TRPs.
Accordingly, an object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform communication even when scheduling is performed using PDCCH/DCI repeatedly transmitted from one or more TRPs.
Means for solving the problems
The terminal according to one aspect of the present disclosure includes: a reception unit that receives a MAC CE containing information related to activation of a transmission setting index (TCI) state of a physical shared channel; and a control unit configured to determine a TCI state corresponding to a physical shared channel based on a field related to a TCI state included in at least one of a plurality of pieces of downlink control information transmitted through the plurality of downlink control channels, when one physical shared channel is scheduled through the plurality of downlink control channels supporting application of different control resource set pool indexes.
ADVANTAGEOUS EFFECTS OF INVENTION
According to an aspect of the present disclosure, even when scheduling is performed using PDCCH/DCI repeatedly transmitted from one or more TRPs, communication can be performed appropriately.
Drawings
Fig. 1A to 1D are diagrams showing an example of a multi-TRP scene.
Fig. 2 is a diagram showing an example of scheduling PDSCH by PDCCH repetition.
Fig. 3 is a diagram showing an example of a MAC CE used for activating the TCI state.
Fig. 4 is a diagram for explaining a TCI state applied to PDSCH repeatedly scheduled by PDCCH.
Fig. 5A to 5C are diagrams showing an example of the MAC CE according to the first embodiment.
Fig. 6A to 6C are diagrams illustrating an example of the MAC CE according to the second embodiment.
Fig. 7A and 7B are diagrams illustrating an example of the mapping between the TCI code point and the TCI state ID according to the second embodiment.
Fig. 8A to 8C are diagrams illustrating an example of the MAC CE according to the third embodiment.
Fig. 9A and 9B are diagrams showing another example of the MAC CE related to the variation (variation) 1.
Fig. 10 is a diagram showing an example of TCI states applied to PDSCH according to variation 2.
Fig. 11 is a diagram for explaining a scheduling offset between PDCCH repetition and PDSCH.
Fig. 12 is a diagram for explaining default TCI/QCL applied to PDSCH according to the fourth aspect.
Fig. 13 is a diagram for explaining default TCI/QCL applied to the PDSCH according to the fourth aspect.
Fig. 14 is a diagram showing an example of a schematic configuration of a radio communication system according to an embodiment.
Fig. 15 is a diagram showing an example of a configuration of a base station according to an embodiment.
Fig. 16 is a diagram showing an example of a configuration of a user terminal according to an embodiment.
Fig. 17 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment.
Detailed Description
(multiple TRP)
In NR, one or more Transmission/Reception points (TRPs)) are being studied for DL Transmission to a UE using one or more panels (multi-panels). Furthermore, the UE is under study for UL transmission of one or more TRP.
In addition, the plurality of TRPs may correspond to the same cell identifier (cell Identifier (ID)) or may correspond to different cell IDs. The cell ID may be either a physical cell ID or a virtual cell ID.
Fig. 1A to 1D are diagrams showing an example of a multi-TRP scene. In these examples, it is contemplated that each TRP is capable of transmitting 4 different beams, but is not limited thereto.
Fig. 1A shows an example of a case where only one TRP (TRP 1 in this example) among the multiple TRPs transmits to the UE (may also be referred to as a single mode, a single TRP, or the like). In this case, TRP1 transmits both control signal (PDCCH) and data signal (PDSCH) to the UE.
Fig. 1B shows an example of a case where only one TRP (TRP 1 in this example) among the multiple TRPs transmits a control signal to the UE, and the multiple TRP transmits a data signal (may also be referred to as Shan Zhumo). The UE receives PDSCH transmitted from the multi-TRP based on one piece of downlink control information (Downlink Control Information (DCI))).
Fig. 1C shows an example of a case where a plurality of TRP, each of which transmits a data signal (may also be referred to as a master-slave mode), transmits a part of a control signal to a UE. Part 1 of the control signal (DCI) may be transmitted to TRP1, and part 2 of the control signal (DCI) may be transmitted to TRP 2. Part 2 of the control signal may also depend on part 1. The UE receives PDSCH transmitted from the multi-TRP based on the part of the DCI.
Fig. 1D shows an example of a case where a plurality of TRP, which transmits a data signal (may also be referred to as a multi-master mode), transmits different control signals to a UE, respectively. The first control signal (DCI) may be transmitted to TRP1, and the second control signal (DCI) may be transmitted to TRP 2. Based on these DCIs, the UE receives PDSCH transmitted from the multi-TRP.
In a case where a plurality of PDSCH from a plurality of TRPs (may also be referred to as a plurality of PDSCH (multiple PDSCH)) is scheduled using one DCI as in fig. 1B, the DCI may also be referred to as a single DCI (S-DCI, single PDCCH). In addition, when a plurality of pdis are used to schedule a plurality of PDSCH from a plurality of TRPs, respectively, as in fig. 1D, these plurality of DCIs may also be referred to as a multi-DCI (M-DCI, multi PDCCH (multiple PDCCH)).
Different Code Words (CW) and different layers may be transmitted from each TRP of the multiple TRPs. As a scheme of multi-TRP transmission, incoherent joint transmission (Non-Coherent Joint Transmission (NCJT)) is being studied.
In NCJT, for example, TRP1 performs modulation mapping on a first codeword and layer mapping and transmits a first PDSCH using a first precoding for a first number of layers (e.g., 2 layers). In addition, TRP2 performs modulation mapping on the second codeword and layer mapping and transmits the second PDSCH using the second precoding for a second number of layers (e.g., 2 layers).
In addition, a plurality of PDSCH (multiple PDSCH) that are NCJT may also be defined as partially or completely overlapping with respect to at least one of the time domain and the frequency domain. In other words, at least one of time and frequency resources of the first PDSCH from the first TRP and the second PDSCH from the second TRP may also overlap.
It is also conceivable that these first PDSCH and second PDSCH are not in a Quasi Co-located (QCL) relationship (not Quasi-Co-located). The reception of multiple PDSCH may be replaced by simultaneous reception of PDSCH that is not of a certain QCL type (e.g., QCL type D).
In URLLC for multi-TRP, repetition (repetition) of PDSCH (transport block (TB) or Codeword (CW)) supported across multi-TRP is being studied. The iterative approach (URLLC scheme, e.g., schemes 1, 2a, 2b, 3, 4) supported across multiple TRPs in the frequency domain or layer (spatial) domain or time domain is being studied. In scheme 1, multiple PDSCH from multiple TRP is space division multiplexed (space division multiplexing (SDM)). In schemes 2a and 2b, PDSCH from multiple TRP is frequency division multiplexed (frequency division multiplexing (FDM)). In scheme 2a, the redundancy version (redundancy version (RV)) is the same for multiple TRP. In scheme 2b, the RV may be the same or different for multiple TRPs. In schemes 3 and 4, multiple PDSCH from multiple TRP are time division multiplexed (time division multiplexing (TDM)). In scheme 3, a multi PDSCH from multiple TRPs is transmitted within one slot. In scheme 4, multiple PDSCH from multiple TRPs are transmitted in different time slots.
According to such a multi-TRP scenario, more flexible transmission control using a channel of good quality can be performed.
NCJTs using multiple TRP/panels have the possibility to use high ranks. To support backhaul (backhaul) between ideal (ideal) and non-ideal (non-ideal) among multiple TRPs, both single DCI (single PDCCH, e.g. fig. 1B) and multiple DCI (multiple PDCCH, e.g. fig. 1D) may also be supported. The maximum number of TRP may also be 2 for both single DCI and multiple DCI.
Extensions to TCI are being investigated for single PDCCH designs (mainly for ideal backhaul). Each TCI code point within the DCI may also correspond to one or two TCI states. The size of the field associated with the TCI state may also be the same as in the case of rel.15.
(PDCCH/DCI repetition)
After rel.17, it is also conceivable that repeated transmission (PDCCH repetition) is applied to PDCCHs (or DCIs) transmitted from one or more TRPs. For example, scheduling or transmission/reception instruction of one or more signals/channels is considered to be performed by using a plurality of PDCCHs (or, DCIs) transmitted from one or more TRPs.
The PDCCH/DCI to which repeated transmission is applied may also be referred to as multi-PDCCH/multi-DCI. The repeated transmission of the PDCCH may be replaced with a PDCCH repetition, multiple transmissions of the PDCCH, multiple PDCCH transmissions, or multiple PDCCH transmissions.
Multiple PDCCH/multiple DCI may also be transmitted from different TRPs, respectively. The different TRP may correspond to, for example, a different CORESET Chi Suoyin (hereinafter also referred to as CORESET pool ID).
The multi-PDCCH/DCI may also be multiplexed by time multiplexing (TDM)/frequency multiplexing (FDM)/spatial multiplexing (SDM). For example, in the case of repetition of PDCCH (TDM PDCCH repetition) by time multiplexing, PDCCHs transmitted from different TRPs are allocated to different time domains.
Fig. 2 shows an example of scheduling of one PDSCH (e.g., the same PDSCH) by repeating transmission of PDCCH. The PDCCH #1 is used for transmission of DCI #1 and corresponds to the first CORESET pool ID (here, # 0). The PDCCH #2 is used for transmission of DCI #2 and corresponds to the second CORESET pool ID (here, # 1). Here, the case where the number of repetitions of PDCCH (or repetition factor) is 2 is shown, but the number of repetitions may be 3 or more.
The content of DCI (e.g., DCI payload)/coded bits (coded bits)/CCE number) to be transmitted in each PDCCH may be the same. In addition, coding/rate matching of each DCI may be controlled based on each repetition.
Each PDCCH (e.g., PDCCH #1, PDCCH # 2) that is repeatedly transmitted may also be referred to as a PDCCH candidate (e.g., PDCCH candidates). Each PDCCH candidate is explicitly associated (or linked), and the UE may grasp the link of the PDCCH candidate (or the PDCCH candidate to be associated) before performing the decoding process.
For PDCCH repetition, the association (or linking) of multiple (e.g., two) search space sets may also be set by higher layer signaling/MAC CEs. The two search space sets may also correspond to CORESETs corresponding to respective iterations of transmissions. CORESET utilized for PDCCH inverse multiplexing may also correspond to two CORESETs associated with two linked sets of search spaces.
In PDCCH repetition, two PDCCH candidates of two search spaces may also be linked in a manner having the same Aggregation (AL) and the same candidate index. The two search space sets that are linked may also consist of the same number of candidates for each AL. In other words, two linked PDCCH candidates for PDCCH inverse multiplexing may also be two PDCCH candidates having the same Aggregation Level (AL) and the same index in two linked search space sets.
(TCI State activation based on MAC CE)
In the existing system (e.g., rel.16 ago), when the CORESET pool ID is set, activation of the TCI state of the PDSCH is activated for each CORESET pool ID (e.g., TRP). In other words, the MAC CE utilized in the notification of the activation of the TCI state is associated with the CORESET pool ID (e.g., TRP) (see fig. 3).
In the MAC CE shown in fig. 3, a case is assumed in which the CORESET pool ID is set to 1. In this case, the mapping of the activated TCI state and the code point of the TCI state field included in the DCI designated by the MAC CE may be applied to the PDSCH scheduled such that the CORESET pool ID is 1.
In the MAC CE shown in fig. 3, a case is assumed in which the CORESET pool ID is set to 1. In this case, the mapping of the activated TCI state and the code point of the TCI state field in the DCI indicated by the MAC CE may be applied to the PDSCH scheduled such that the CORESET pool ID is 1.
In the MAC CE shown in fig. 3, a case is assumed in which the CORESET pool ID is set to 0. In this case, the mapping of the activated TCI state and the code point of the TCI state field in the DCI indicated by the MAC CE may be applied to the PDSCH scheduled such that the CORESET pool ID is 0.
Thus, in the conventional system, a TCI state list (here, two TCI state lists) is set for each CORESET pool ID.
As shown in fig. 4, it is also considered that two concatenated PDCCH candidates (e.g., PDCCH #1 and PDCCH # 2) of PDCCH inverse multiplex are transmitted with two CORESETs having different CORESET pool IDs, respectively. For example, it is also contemplated that pdcch#1 corresponds to a first CORESET pool ID and pdcch#2 corresponds to a second CORESET pool ID.
In this way, in the case where PDSCH is scheduled by a plurality of PDCCHs (e.g., linked PDCCH candidates) corresponding to different CORESET pool IDs during PDCCH repetition transmission, how to control the TCI state applied to PDSCH becomes a problem.
For example, how the UE envisages/interprets the mapping of the code points of the TCI state field of the DCI with the activated TCI state becomes a problem. Alternatively, how the UE determines/decides the TCI state applied to the PDSCH based on the code point of the TCI state field of the DCI becomes a problem.
Alternatively, in a case where the offset between a PDCCH (e.g., a plurality of PDCCHs having different CORESET pool IDs) to be repeatedly transmitted and a PDSCH scheduled by the plurality of PDCCHs is smaller than a specific value, how to control the TCI state/QCL (e.g., default TCI state/default QCL) applied to the PDSCH becomes a problem.
Accordingly, the present inventors have studied a control method in a case where a shared channel (for example, PDCCH/PUSCH) is scheduled by applying a PDCCH (or multi-PDCCH/DCI) that is repeatedly transmitted, and have conceived this embodiment.
In one aspect of the present disclosure, when one physical shared channel (e.g., PDSCH/PUSCH) is scheduled by a plurality of PDCCHs/DCIs supporting applications of different CORESET pool IDs, a UE determines a TCI state corresponding to the physical shared channel based on a field (TCI state field) related to a TCI state included in at least one of the plurality of DCIs.
Embodiments according to the present disclosure will be described in detail below with reference to the accompanying drawings. Each mode (or the configuration and the wireless communication method shown in each mode) may be applied separately or in combination.
In the present disclosure, "a/B", "at least one of a and B" may also be replaced with each other. In the present disclosure, "at least one of a/B/C", "A, B, and C" may also be replaced with each other. In the present disclosure, cells, serving cells, CCs, carriers, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, band may also be replaced with each other. In this disclosure, the index, ID, indicator, resource ID may also be replaced with each other. In the present disclosure, support, control, enable control, operate, enable operation, and the like may also be interchanged.
In the present disclosure, setting (configuration), activation (update), indication (indication), activation (enable), designation (specific), selection (selection) may also be replaced with each other.
In the present disclosure, the higher layer signaling may also be any one of radio resource control (Radio Resource Control (RRC)) signaling, medium access control (Medium Access Control (MAC)) signaling, broadcast information, or the like, or a combination of these, for example. In the present disclosure, RRC signaling, RRC parameters, higher layer parameters, RRC Information Element (IE), RRC messages may also be replaced with each other.
MAC signaling may also use, for example, MAC control elements (MAC Control Element (MAC CE)), MAC protocol data units (Protocol Data Unit (PDU)), and the like. The broadcast information may be, for example, a master information block (Master Information Block (MIB)), a system information block (System Information Block (SIB)), minimum system information (remaining minimum system information (Remaining Minimum System Information (RMSI))), other system information (Other System Information (OSI)), or the like.
In this disclosure, MAC CE, activate/deactivate commands may also be substituted for each other.
Pools, sets, groups, lists, candidates may also be substituted for each other in this disclosure.
In the present disclosure, DMRS ports, antenna ports may also be replaced with each other.
In the present disclosure, the special (specific) cells SpCell, PCell, PSCell may also be replaced with each other.
In this disclosure, beams, spatial domain filters, spatial settings, TCI states, TCI hypotheses, QCL parameters, quasi co-location, spatial domain receive filters, UE receive beams, DL receive beams, DL precoders, DL-RS, RS of QCL type D of TCI states/QCL hypotheses, RS of QCL type a of TCI states/QCL hypotheses, spatial relationships, spatial domain transmit filters, UE transmit beams, UL transmit beams, UL precoders, PL-RS may also be interchanged. In the present disclosure, QCL type X-RS, DL-RS associated with QCL type X, DL-RS with QCL type X, source of DL-RS, SSB, CSI-RS, SRS may also be replaced with each other.
In the present disclosure, TRP ID, TRP association ID, CORESET pool ID, the position of one of two TCI states (ordinal, first TCI state or second TCI state) corresponding to one code point of a field within DCI, TRP may also be replaced with each other.
In the present disclosure, TRP, transmission point, panel, DMRS port group, CORESET pool, one of two TCI states associated with one code point of TCI field may also be replaced with each other.
In the following description, a case where the content (for example, DCI payload (DCI payload)/coded bits (coded bits)/CCE number) of DCI transmitted through each PDCCH during repetition of PDCCH transmission is the same will be described as an example. For example, the code point of the TCI field of the DCI transmitted through the first PDCCH may be set in the same manner as the code point of the TCI field of the DCI transmitted through the second PDCCH. The present embodiment is not limited to this, and may be applied to a case where the code points of DCI are different.
(first mode)
The first method determines the TCI state by referring to one PDCCH candidate (or CORESET pool ID) for the PDSCH when scheduling of one physical shared channel is supported by a plurality of PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs. Alternatively, the UE determines the TCI state of the PDSCH based on the MAC CE corresponding to the specific CORESET pool ID.
In this disclosure (or otherwise), PDCCH (or PDCCH candidates) may also be replaced with DCI (or DCI candidates). In the present disclosure (or other embodiments), the physical shared channel is described as an example by taking PDSCH, but the same applies to PUSCH.
The UE may also receive information related to activation/deactivation of the TCI state. Information related to activation of the TCI state may also be received through the MAC CE. The MAC CE may also be utilized as a MAC CE utilized in notification of activation of TCI state for PDSCH in an existing system (e.g., rel. 16) (e.g., TCI state activation/deactivation (TCI States Activation/Deactivation for UE-specific PDSCH MAC CE) for UE-specific PDSCH).
Fig. 5A and 5B show an example of a MAC CE used for notifying the activation of the TCI state. Fig. 5A shows a case where CORESET pool id=0 is specified. In addition, in fig. 5A, the case where TCI states #0, #10, #12, #13 are activated is shown. The TCI state that is activated is an example, and is not limited to this.
Fig. 5B shows a case where CORESET pool id=1 is specified. In addition, in fig. 5B, the case where TCI states #1, #3, #4, #5 are activated is shown. The TCI state that is activated is an example, and is not limited to this.
In two CORESETs having different CORESET pool IDs, a case is assumed in which one PDSCH is scheduled by the PDCCH candidate to which association (or linking) is performed (see fig. 5C). Fig. 5C shows a case where one PDSCH is scheduled by pdcch#1/dci#1 (corresponding to CORESET pool id#0) and pdcch#2/dci#2 (corresponding to CORESET pool id#1). Here, a case is shown in which 0 (e.g., "000") is designated as a code point of a TCI status field of DCI of each PDCCH. The code point of the TCI status field included in the DCI may also be referred to as a TCI code point.
For this PDSCH, when the TCI state activated by the MAC CE is mapped to the TCI code point in the DCI, one (or a specific) PDCCH candidate out of the plurality of PDCCH candidates may be referred to. One PDCCH candidate (may also be referred to as a reference PDCCH candidate, a reference PDCCH) among the plurality of PDCCH candidates may also be applied with at least one of options 1-1 to 1-6 below.
< option 1-1 >)
May also be referenced to the PDCCH candidate corresponding to the first CORESET pool index (e.g., # 0) or the first CORESET pool ID. The referenced first CORESET pool ID may also refer to a TCI state of the PDSCH selected to be associated with the first CORESET pool index.
The UE may also apply the TCI state activated by the MAC CE corresponding to the first CORESET pool index (# 0) in the case of receiving information (e.g., MAC CE of fig. 5A, 5B) related to the activated TCI state corresponding to each CORESET pool ID. In other words, the UE may also assume that the TCI state activated by the MAC CE corresponding to the first CORESET pool index (# 0) is mapped to the TCI code point of the DCI.
For example, TCI state #0, which is instructed to be activated by the MAC CE (see fig. 6A) corresponding to the first CORESET pool index (# 0), may be mapped to TCI code point "000", and TCI state #10 may be mapped to TCI code point "001".
< options 1-2 >
In the case where 0 ("000") is designated as a TCI code point, the UE may also apply TCI state #0 to the PDSCH. May also be referenced to a PDCCH candidate corresponding to the second CORESET Chi Suoyin (e.g., # 1) or the second CORESET pool ID.
The UE may also apply the TCI state activated by the MAC CE corresponding to the second CORESET Chi Suoyin (# 1) in the case of receiving information (e.g., MAC CE of fig. 5A, 5B) related to the activated TCI state corresponding to each CORESET pool ID. In other words, the UE can also be conceived that the TCI state activated by the MAC CE corresponding to the second CORESET Chi Suoyin (# 1) is mapped to the TCI code point.
For example, TCI state #1 instructed to be activated by the MAC CE (see fig. 6B) corresponding to the second CORESET Chi Suoyin (# 1) may be mapped to TCI code point "000", and TCI state #3 may be mapped to TCI code point "001". For example, in a case where 0 ("000") is designated as a TCI code point, the UE may also apply TCI state #1 to the PDSCH.
< options 1-3 >
May also be referenced to a first PDCCH candidate (or PDCCH candidate of a first PDCCH monitoring occasion) of a plurality of PDCCH candidates (or a plurality of PDCCH monitoring occasions). The first may refer to the earliest transmission in the time domain (or the UE initially received) or the smallest index of the monitoring occasion.
Alternatively, the last PDCCH candidate (or PDCCH candidate of the last PDCCH monitoring occasion) among the plurality of PDCCH candidates (or the plurality of PDCCH monitoring occasions) may be referred to. Finally, it may be the latest transmitted in the time domain (or the last received by the UE), or the largest index of the monitoring occasion.
The UE may also determine the TCI state of the PDSCH using the MAC CE specifying the CORESET pool ID corresponding to the first PDCCH candidate (or the last PDCCH candidate). For example, the UE may also assume that the TCI state activated by the MAC CE is mapped to the TCI code point contained in the DCI.
< options 1-4 >
May also be referenced to the PDCCH candidate of CORESET with the lowest CORESET ID. Alternatively, the PDCCH candidate of CORESET with the highest CORESET ID may also be referenced.
The UE may also determine the TCI state of the PDSCH using the MAC CE specifying the CORESET pool ID set to the lowest (or highest) CORESET index. For example, the UE may also assume that the TCI state activated by the MAC CE is mapped to the TCI code point included in the DCI.
< options 1-5 >
The PDCCH candidate of CORESET with the lowest search space set ID may also be referenced. Alternatively, the PDCCH candidate of CORESET with the highest search space set ID may also be referenced.
The UE may also determine the TCI state of the PDSCH using the MAC CE specifying the CORESET pool ID corresponding to the lowest (or highest) index search space set. For example, the UE may also assume that the TCI state activated by the MAC CE is mapped to the TCI code point included in the DCI.
< options 1-6 >
The method for determining the reference PDCCH candidates may be set from the base station to the UE. For example, a plurality of options from options 1-1 to 1-5 may be supported, and the options may be set and indicated quasi-statically or dynamically by higher layer signaling/MAC CE/DCI, depending on which option is applied.
In the above option, the fact that one of the linked PDCCH candidates is referred to may mean that, in the mapping between the TCI code point included in the DCI and the activated TCI state, the MAC CE for TCI state activation, in which the CORESET pool ID is set to the same CORESET pool ID as the reference PDCCH candidate, is applied.
The rule for determining the reference for TCI state indication may be matched with the rule for determining the reference for timing offset/HARQ codebook/DAI/PUCCH resource determination. Alternatively, the rule for determining the reference for TCI status indication may be different from the rule for determining the reference for timing offset/HARQ codebook/DAI/PUCCH resource determination.
In this way, in the first aspect, mapping of the TCI state activated with reference to one (or a specific) PDCCH candidate among the plurality of PDCCH candidates and the TCI code point is performed. Thus, even when scheduling of one PDSCH is supported by a plurality of PDCCHs corresponding to different CORESET pool IDs, the TCI state for the PDSCH can be appropriately determined.
(second mode)
In the second aspect, when scheduling of one physical shared channel is supported by a plurality of PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs, the UE determines the TCI state in consideration of MAC CEs corresponding to the CORESET pool IDs.
The UE may also interpret the mapping between the TCI state activated through the MAC CE and the TCI code point of the DCI using a new rule different from the existing system for PDSCH scheduled through PDCCH repetition with two different CORESET pool IDs.
For example, the UE may also envisage that both TCI states activated by MAC CEs corresponding to a first CORESET pool ID and TCI states activated by MAC CEs corresponding to a second CORESET pool ID are mapped to TCI code points.
The UE may also receive information related to activation/deactivation of the TCI state. Information related to activation of the TCI state may also be received through the MAC CE. The MAC CE may also be utilized as a MAC CE utilized in notification of activation of TCI state for PDSCH in an existing system (e.g., rel. 16) (e.g., TCI state activation/deactivation (TCI States Activation/Deactivation for UE-specific PDSCH MAC CE) for UE-specific PDSCH).
Fig. 6A and 6B show an example of a MAC CE used for notifying the activation of the TCI state. Fig. 6A shows the case of the assigned CORESET pool ID # 0. In addition, in fig. 6A, the case of activated TCI states #0, #10, #12, #13 is shown. The TCI state that is activated is an example, and is not limited to this.
Fig. 6B shows the case of the assigned CORESET pool ID # 1. In addition, in fig. 6B, the case of activated TCI states #1, #3, #4, #5 is shown. The TCI state that is activated is an example, and is not limited to this.
In two CORESETs having different CORESET pool IDs, a case is assumed in which one PDSCH is scheduled by associating (or linking) PDCCH candidates (see fig. 6C). Fig. 6C shows a case where one PDSCH is scheduled by pdcch#1/dci#1 (corresponding to CORESET pool id#0) and pdcch#2/dci#2 (corresponding to CORESET pool id#1).
For this PDSCH, when the TCI state activated by the MAC CE is mapped to the TCI code point in the DCI, a plurality of MAC CEs corresponding to different CORESET pool IDs may be omitted. As the mapping rule, at least one of the following options 2-1 to 2-2 may also be applied.
< option 2-1 >)
TCI code points may also be mapped to TCI states that were initially activated in the order of CORESET pool IDs, with the same CORESET pool IDs mapped in the order of TCI state IDs.
For example, the first to (x+1) -th TCI states, in which the TCI state field (Ti field) of the MAC CE of the first CORESET pool ID (# 0) is set to '1', may be mapped to TCI code point values 0 to x. The first to y-th TCI states set to '1' in the TCI state field (Ti field) of the MAC CE set to the second CORESET pool ID (# 1) may also be mapped to the TCI code point values x+1 to x+y.
In the cases shown in fig. 6A and 6B, TCI states #0, #10, #12, #13 activated by the MAC CE corresponding to the first CORESET pool ID are mapped to TCI code points 0, 1, 2, and 3, respectively (see fig. 7A). TCI states #1, #3, #4, #5 activated by the MAC CE corresponding to the second CORESET pool ID are mapped to TCI code points 4, 5, 6, 7, respectively.
In fig. 7A, a case where the number of TCI states activated by the MAC CE corresponding to the first CORESET pool ID is the same as the number of TCI states activated by the MAC CE corresponding to the second CORESET pool ID is shown, but is not limited thereto.
< option 2-2 >)
TCI code points may also be mapped to TCI states that are activated in the order of TCI state IDs.
For example, the TCI state of the MAC CE with the first CORESET pool ID (# 0) set to the TCI state of '1' and the TCI state of the MAC CE with the second CORESET pool ID (# 1) set to the TCI state of '1' may also be mapped to the TCI code point values 0 to x.
In the cases shown in fig. 6A and 6B, TCI states #0, #10, #12, #13 activated by the MAC CE corresponding to the first CORESET pool ID and TCI states #1, #3, #4, #5 activated by the MAC CE corresponding to the second CORESET pool ID are mapped to TCI code points 0 to 7, respectively, in the order of TCI state IDs (see fig. 7B).
In fig. 7B, a case where the number of TCI states activated by the MAC CE corresponding to the first CORESET pool ID is the same as the number of TCI states activated by the MAC CE corresponding to the second CORESET pool ID is shown, but is not limited thereto.
In option 2-1/option 2-2, the size of the TCI status field may also be set to 3 bits. In such a case, the maximum aggregate count of TCI states activated by MAC CEs for the first CORESET pool ID and the second CORESET pool ID may also be 8.
The size of the TCI state field may also be applied to a size greater than 3 bits (e.g., 4 bits). In this case, the maximum number of TCI states activated by the MAC CEs corresponding to the CORESET pool IDs may be 8.
Alternatively, the maximum aggregate count of TCI states activated by MAC CEs for the first CORESET pool ID and the second CORESET pool ID is set to 8, and a maximum of 4 TCI states activated for each CORESET pool ID may be selected based on the MAC CEs. For example, in case that the number of activated TCI states in the MAC CE of the first CORESET pool ID #0/#1 is greater than 4, the first (or last) 4 TCI states in which the TCI state field is set to 1 may also be mapped to the TCI code point of the DCI.
In case of PDSCH scheduled through unlinked PDCCH, 8 activated TCI states based on MAC CE may also be applied to the rule of the existing system mapped to TCI code points of DCI.
In this way, in the second aspect, TCI states that are activated by MAC CEs set with different CORESET pool IDs are mapped to TCI code points, respectively. Accordingly, since the activated TCI state corresponding to the different CORESET pool IDs can be specified by DCI, the TCI state applied to the PDSCH can be flexibly set.
(third mode)
In the third aspect, when scheduling of one physical shared channel is supported by a plurality of PDCCHs (or PDCCH candidates) corresponding to different CORESET pool IDs, the UE determines the TCI state in consideration of MAC CEs not corresponding to the CORESET pool IDs (or MAC CEs not including CORESET pool ID fields).
The UE may also apply the TCI state activated by the new MAC CE for PDSCH scheduled over PDCCH repetition with two different CORESET pool IDs. The new MAC CE may also be defined/set separately from the MAC CE of the existing system (e.g., a MAC CE with CORESET pool ID field).
For example, the new MAC CE may be a structure that does not contain a field specifying the CORESET pool ID. The UE may also assume that the TCI state activated by the new MAC CE is mapped to the TCI code point for PDSCH scheduled over PDCCH repetition with two different CORESET pool IDs.
The UE may also receive information related to activation/deactivation of the TCI state. Information related to activation of the TCI state may also be received through the MAC CE. The UE may also envisage both MAC CEs (e.g., TCI state activation/deactivation (TCI States Activation/Deactivation for UE-specific PDSCH MAC CE) for UE-specific MAC CEs) and new MAC CEs that are utilized in the notification of the activation of TCI states for PDSCH in existing systems (e.g., rel.16). The new MAC CE (e.g., enhanced TCI state activation/deactivation (Enhanced TCI States Activation/Deactivation for UE-specific PDSCH MAC CE) for the UE-specific PDSCH) may also be applied only under certain conditions (e.g., where set by higher layer signaling).
Fig. 8A and 8B show an example of a MAC CE used for notifying the activation of the TCI state. Fig. 8A shows a MAC CE containing a field informing the CORESET pool ID. In addition, the first CORESET pool ID or the second CORESET pool ID may be set in this field.
Fig. 8B shows an example of a new MAC CE. In the new MAC CE, the field notifying the CORESET pool ID may not be included. In addition, in fig. 8B, the case of activated TCI states #6, #8, #10, #11 is shown. The TCI state that is activated is an example, and is not limited to this.
In two CORESETs having different CORESET pool indexes, a case is assumed in which one PDSCH is scheduled by associating (or linking) PDCCH candidates (see fig. 8C). Fig. 8C shows a case where one PDSCH is scheduled by pdcch#1/dci#1 (corresponding to CORESET Chi Suoyin #0) and pdcch#2/dci#2 (corresponding to CORESET Chi Suoyin #1). Here, a case is shown in which 0 (e.g., "000") is designated as a TCI code point of DCI of each PDCCH.
In this case, the UE may control reception of the PDSCH in consideration of the TCI state activated by the new MAC CE (see fig. 8B). For example, the UE may also envisage that the TCI state activated by the new MAC CE is mapped to the TCI code point of the DCI.
In the case shown in fig. 8B, the UE can also assume that TCI states #6, #8, #10, #11, … … activated by a new MAC CE are mapped to TCI code points, respectively. For example, TCI state #6 may be mapped to TCI code point 0, TCI states #8, #10, #11, and # … … may be mapped to TCI code points 1, 2, and 3 … …, respectively, and TCI state #6 may be mapped to TCI code point 0.
In the case where 0 ("000") is designated as a TCI code point, the UE may also apply TCI state #6 to the PDSCH.
The MAC CE shown in fig. 8A may also be applied for PDSCH scheduled by PDCH without repetition (or without a link with other PDCCH candidates/CORESET/search space set) or PDSCH scheduled by multiple PDCCH candidates to which the same CORESET index is applied.
In this way, the TCI state-activating MAC CE (or new MAC CE) extended from rel.16 may be configured to be selectively applied to PDSCH scheduled by the two PDCCH candidates linked in the two CORESETs having different CORESET pool IDs.
In the third aspect, when scheduling of one PDSCH is supported by a plurality of PDCCHs corresponding to different CORESET pool IDs, the TCI state can be activated (or the TCI state and TCI code point can be mapped) by using a new MAC CE. The TCI state applied to the PDSCH can be flexibly set.
< Change 1 >
The new MAC CE may also be utilized in the activation of the TCI state of the PDSCH scheduled by the PDCCH repetition of the PDCCH candidate linked in two coreets with different CORESET pool IDs and the activation of the TCI state corresponding to a particular CORESET pool ID.
The specific field (e.g., X field) of the MAC CE may also represent a core pool id=0 ("00"), a core pool id=1 ("01"), or a PDCCH repetition PDCCH with a different core pool ID (e.g., PDCCH repetition with a core pool id=0, core pool id=1 (PDCCH repetition with CORESETPoolID =0 and CORESETPoolID =1)) ("10") (see fig. 9A). In this case, the UE may consider only a new MAC CE, and may not consider an existing MAC CE for TCI state activation.
In fig. 9A, the case of activated TCI states #6, #8, #10, #11 is shown. The TCI state that is activated is an example, and is not limited to this.
Consider the case where PDSCH is scheduled through two PDCCH candidates linked within two CORESETs with different CORESET pool IDs (see fig. 9B). In this case, the TCI state activated by setting the MAC CE having the PDCCH repetition (PDCCH repetition with CORESETPoolID =0 and CORESETPoolID =1) of CORESET pool id=0 and CORESET pool id=1 in the X field may be mapped to the TCI code point of the DCI.
In the case shown in fig. 9B, the UE can also assume that TCI states #6, #8, #10, #11 … … activated by a new MAC CE are mapped to TCI code points 0, 1, 2, 3 … …, respectively. Here, since the code point of the TCI state field is notified of 0, the UE may apply TCI state #6 to the PDSCH.
Consider the case of PDSCH scheduled by PDCH without repetition (or without a link with other PDCCH candidates) or PDSCH scheduled by multiple PDCCH candidates with the same CORESET pool index applied. In the case where PDCCH corresponds to CORESET pool id=0, TCI state activated by a new MAC CE with CORESET pool id=0 set in the X field may also be mapped to TCI code point of DCI. If PDCCH corresponds to CORESET pool id=1, the TCI state activated by the new MAC CE with CORESET pool id=1 set in the X field may be mapped to the TCI code point of DCI.
< Change 2 >
Both TCI states for PDSCH of single TRP (for example, TCI state for PDSCH for S-TRP) and TCI states for PDSCH of multiple TRP based on multiple DCI (for example, TCI state for PDSCH or M-DCI M-TRP) may be set. In this case, the TCI state for PDSCH of a single TRP may be selected for PDSCH scheduled by PDCCH (e.g., linked PDCCH, repeated PDCCH) associated with a different CORESET pool ID (see fig. 10).
(fourth mode)
In the fourth aspect, in the repetition of PDCCH, when an offset (also referred to as a scheduling offset) between PDCCH/DCI and PDSCH scheduled by the PDCCH/DCI is smaller than a specific value (e.g., timeduration fortcl), a TCI state/QCL concept applied to PDSCH will be described.
In the conventional system (e.g., rel.16), when the offset between PDCCH/DCI and PDSCH is smaller than a specific value (e.g., timeduration forqcl), CORESET having different CORESET pool IDs, and a specific higher layer parameter is set, a specific QCL may be applied to PDSCH. The specific higher level parameters may also be higher level parameters that set a default TCI state per CORESET pool index (e.g., enabledefaulttcistatatepercoresetpoil index-r 16).
For example, for PDSCH scheduled through PDCCH with CORESET pool id=0, QCL of CORESET with the smallest CORESET ID among CORESETs with CORESET pool id=0 in the latest slot (e.g., last slot) may also be utilized as default QCL of PDSCH. The latest time slot may be the latest time slot in which monitoring of CORESET (for example, CORESET corresponding to CORESET pool ID # 0) is performed. In other words, the default TCI state/QCL for PDSCH with CORESET pool id=0 may also be determined based on the smallest CORESET ID associated with CORESET pool id=0 in the most recent monitoring slot.
For example, for PDSCH scheduled through PDCCH with CORESET pool id=1, QCL of CORESET with the smallest CORESET ID among CORESETs with CORESET pool id=1 in the latest slot (e.g., last slot) may also be utilized as default QCL of PDSCH. The latest time slot may be the latest time slot in which monitoring of CORESET (for example, CORESET corresponding to CORESET pool ID # 1) is performed. In other words, the default TCI state/QCL for PDSCH with CORESET pool id=1 may also be determined based on the smallest CORESET ID associated with CORESET pool id=1 in the most recent monitoring slot.
In this way, in the conventional system, when higher-layer parameters in the default TCI state are set for each CORESET pool index and the offset between DCI and PDSCH is smaller than the specific value, the default QCL to be applied to PDSCH is determined in consideration of the CORESET pool ID corresponding to the DCI (or PDCCH). In other words, the default QCL applied to the PDSCH is determined based on the CORESET pool ID corresponding to the PDCCH/DCI scheduling the PDSCH.
On the other hand, a case is also envisaged in which a plurality of PDCCH candidates (e.g., linked PDCCH candidates) for PDCCH inverse multiplexing are transmitted by two CORESETs having different CORESET pool IDs (see fig. 11).
Fig. 11 shows an example of scheduling of one PDSCH (e.g., the same PDSCH) by repeating transmission of PDCCH. The case where pdcch#1/dci#1 corresponds to a first CORESET pool ID (here, # 0), and pdcch#2/dci#2 corresponds to a second CORESET pool ID (here, # 1). Here, the case where the number of repetitions of PDCCH (or repetition factor) is 2 is shown, but the number of repetitions may be 3 or more.
In fig. 11, when the scheduling offset between at least one (or all) of the PDCCH and DCI repeatedly transmitted and the PDSCH is smaller than a specific value (e.g., timeduration for QCL), how to determine the default QCL (or default beam) applied to the PDSCH becomes a problem.
In the present embodiment, when the scheduling offset between at least one (or all) of the PDCCH and DCI to be repeatedly transmitted and the PDSCH is smaller than the bit value, at least one of the following alt.4-1 to alt.4-3 may be applied. In the following description, the present invention can be applied to both a case where the offset value between at least one PDCCH/DCI of the repeatedly transmitted PDCCHs/DCIs and PDSCH is smaller (scheduling offset value estimation # 1) and a case where the offsets between a plurality of PDCCHs/DCIs and PDSCH are smaller than the predetermined value (scheduling offset value estimation # 2).
Alt.4-1 is controlled so that, when the scheduling offset between at least one (or all) of the PDCCHs and DCIs that are repeatedly transmitted and the PDSCH is smaller than a specific value, the default TCI state is not set for each CORESET pool ID. Alt.4-2/4-3 is controlled to set a default TCI state for each CORESET pool ID when a scheduling offset between at least one (or all) of the PDCCHs/DCIs to be repeatedly transmitted and the PDSCH is smaller than a bit value.
<Alt.4-1>
In the case where a UE sets a plurality of (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) for PDCCH inverse multiplexing in two CORESETs having different CORESET pool IDs, it is not conceivable to set a specific higher layer parameter (e.g., enabledefaulttcistatepercoreset-r 16) of a default TCI state for each CORESET pool index (see fig. 12). In other words, in case that a plurality of PDCCH candidates linked for PDCCH inverse multiplexing are transmitted through two CORESETs having different CORESET pool IDs, the UE may also assume that the default TCI state is not set per CORESET pool index.
If the offset between the reception of PDCCH/DCI and the reception of the corresponding PDSCH is smaller than the specific value without setting the specific higher-layer parameter, the UE may use the QCL of CORESET having the smallest CORESET ID among CORESETs having been monitored for CORESET, regardless of CORESET pool IDs (or irrespective of CORESET pool IDs), as the default QCL of PDSCH.
In other words, the default TCI state/QCL of PDSCH may also be determined based on the minimum CORESET ID in the most recent CORESET monitoring slot, regardless of CORESET pool ID.
In addition, the UE may also operate in the existing system (e.g., rel.16) with the UE not set a specific higher layer parameter (e.g., enabledefaulttcistatepercoresetpolindex-r 16) applied.
The UE may also envisage that the DM-RS port of PDSCH of the serving cell is quasi co-located with RS (the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with amonitored search space with the lowest controlResourceSetId in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.) with respect to the QCL parameter used in the PDCCH quasi co-located indication (e.g., PDCCH quasi co-location indication) of the CORESET associated with the monitored search space with the smallest CORESET ID (e.g., lowest controlResourceSetID) in the latest time slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.
<Alt.4-2>
In the case where a plurality of (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) for which PDCCHs are inversely multiplexed are set in two coreets having different coreet pool IDs, the UE may be supported to set a specific higher layer parameter of a default TCI state for each coreet pool index (see fig. 13). In other words, in case that a plurality of PDCCH candidates linked for PDCCH inverse multiplexing are transmitted through two CORESETs having different CORESET pool IDs, the UE may also be conceived to be supported for setting of a default TCI state per CORESET pool index.
The specific high-level parameter for setting the default TCI state for each CORESET pool index may be, for example, enabledefaulttcistatepercoresetpoillindex-r 16 or a new high-level parameter.
It is assumed that a specific higher layer parameter is set and an offset between reception of PDCCH and DCI and reception of the corresponding PDSCH is smaller than a specific value (see fig. 13). In this case, the UE may determine a default QCL/default beam with reference to one (or a specific) PDCCH candidate among the linked PDCCH candidates for the PDSCH scheduled by the linked PDCCH candidate among two CORESETs having different CORESET pool IDs.
One PDCCH candidate (also referred to as a reference PDCCH candidate, a reference PDCCH) among the plurality of PDCCH candidates may also be applied with at least one of the following options 4-2-1 to 4-2-6.
[ option 4-2-1]
May also be referenced to the PDCCH candidate corresponding to the first CORESET pool index (e.g., # 0) or the first CORESET pool ID. Reference to the first CORESET pool ID may also refer to the TCI state of the PDSCH being the TCI state/QCL assumption of the smallest CORESET ID associated with CORESET pool id=0 in the latest slot.
The UE may also assume that QCL of CORESET with the smallest CORESET ID among CORESETs with CORESET pool id=0 in the latest slot (e.g., last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH. The latest time slot may be the latest time slot in which monitoring of CORESET (for example, CORESET corresponding to CORESET pool ID # 0) is performed.
[ option 4-2-2]
May also be referenced to a PDCCH candidate corresponding to the second CORESET Chi Suoyin (e.g., # 1) or the second CORESET pool ID. Reference to the second CORESET pool ID may also refer to the TCI state of the PDSCH being the TCI state/QCL assumption of the smallest CORESET ID associated with CORESET pool id=1 in the latest slot.
The UE may also assume that QCL of CORESET with the smallest CORESET ID among CORESETs with CORESET pool id=1 in the latest slot (e.g., last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH. The latest time slot may be the latest time slot in which monitoring of CORESET (for example, CORESET corresponding to CORESET pool ID # 1) is performed.
[ options 4-2-3]
May also be referenced to a first PDCCH candidate (or PDCCH candidate of a first PDCCH monitoring occasion) of the plurality of PDCCH candidates (or a plurality of PDCCH monitoring occasions). The first may refer to the earliest transmission in the time domain (or the UE initially received) or the smallest index of the monitoring occasion.
Alternatively, the last PDCCH candidate (or PDCCH candidate of the last PDCCH monitoring occasion) among the plurality of PDCCH candidates (or the plurality of PDCCH monitoring occasions) may be referred to. Finally, it may be the latest transmitted in the time domain (or the last received by the UE), or the largest index of the monitoring occasion.
Consider the case of CORESET pool id=0 corresponding to the first PDCCH candidate (or the last PDCCH candidate). In this case, the UE may also assume that QCL of CORESET with the smallest CORESET ID among CORESETs with CORESET pool id=0 in the latest slot (e.g., last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
Consider the case of CORESET pool id=1 corresponding to the first PDCCH candidate (or the last PDCCH candidate). In this case, the UE may also assume that the QCL of CORESET having the smallest CORESET ID among CORESETs having CORESET pool id=1 in the latest slot (for example, last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
[ options 4-2-4]
May also be referenced to the PDCCH candidate of CORESET with the lowest CORESET ID. Alternatively, the PDCCH candidate of CORESET with the highest CORESET ID may also be referenced.
Consider the case where CORESET pool id=0 corresponding to the PDCCH candidate of CORESET with the lowest (or highest) CORESET ID. In this case, the UE may also assume that the QCL of CORESET having the smallest CORESET ID among CORESETs having CORESET pool id=0 in the latest slot (for example, last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
Consider the case where CORESET pool id=1 corresponding to the PDCCH candidate of CORESET with the lowest (or highest) CORESET ID. In this case, the UE may also assume that QCL of CORESET having the smallest CORESET ID among CORESETs having CORESET pool id=1 in the latest slot (e.g., last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
[ options 4-2-5]
The PDCCH candidate of CORESET with the lowest search space set ID may also be referenced. Alternatively, the PDCCH candidate of CORESET with the highest search space set ID may also be referenced.
Consider the case where CORESET pool id=0 corresponding to the PDCCH candidate of CORESET with the lowest (or highest) search space set ID. In this case, the UE may also assume that the QCL of CORESET having the smallest CORESET ID among CORESETs having CORESET pool id=0 in the latest slot (for example, last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
Consider the case where CORESET pool id=1 corresponding to the PDCCH candidate of CORESET with the lowest (or highest) search space set ID. In this case, the UE may also assume that the QCL of CORESET having the smallest CORESET ID among CORESETs having CORESET pool id=1 in the latest slot (for example, last slot) is the default QCL of PDSCH for PDSCH scheduled by repeating PDCCH.
[ options 4-2-6]
The method for determining the reference PDCCH candidates may be set from the base station to the UE. For example, a plurality of options among the supported options 4-2-1 to 4-2-5 may be set/indicated quasi-statically or dynamically by higher layer signaling/MAC CE/DCI for which option is applied.
In the above option, setting the default QCL with reference to one of the linked PDCCH candidates may also mean that the QCL of CORESET having the smallest CORESET ID among CORESETs of CORESET pool IDs in the latest slot (for example, the latest slot) is determined as the default QCL of the PDSCH in consideration of CORESET pool IDs corresponding to the referenced PDCCH candidates.
Specifically, the UE may also envisage that the QCL parameters used in the PDCCH quasi co-location indication of the coret associated with the monitored search space with the smallest CORESET ID in the CORESET set with the same "reference PDCCH candidate" between two linked PDCCH candidates that schedule the PDSCH in the latest slot in which one or more coreets are monitored by the UE in association with the same "reference PDCCH candidate" between two linked PDCCH candidates that schedule the serving cell in the activated BWP are also quasi co-located with the RS by means of DM-RS ports of the PDSCH scheduled by the two linked PDCCH candidates associated with different CORESET IDs (the UE may assume that the DM-RS ports of PDSCH scheduled by two linked PDCCH candidates associated with different CORESETPoolID are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId among CORESETs, which are configured with the same value of CORESETPoolIndex as the "reference PDCCH candidate" between the two linked PDCCH candidates scheduling that PDSCH, in the latest slot in which one or more CORESETs associated with the same value of CORESETPoolIndex as the "reference PDCCH candidate" between the two linked PDCCH candidates scheduling that PDSCH within the active BWP of the serving cell are monitored by the UE.).
The rule for determining the reference for TCI status indication may be identical to the rule for determining the reference for timing offset/HARQ codebook/DAI/PUCCH resource determination. Alternatively, the rule for determining the reference for TCI status indication may be different from the rule for determining the reference for timing offset/HARQ codebook/DAI/PUCCH resource determination.
<Alt.4-3>
In the case where a plurality of (e.g., two) PDCCH candidates (e.g., linked PDCCH candidates) for which PDCCHs are inversely multiplexed are set in two coreets having different coreet pool IDs, the UE may be supported to set a specific higher layer parameter of a default TCI state for each coreet pool index (see fig. 13). In other words, in case that a plurality of PDCCH candidates linked for PDCCH inverse multiplexing are transmitted through two CORESETs having different CORESET pool IDs, the UE may also be conceived as a setting of a default TCI state supported per CORESET pool index.
The specific high-level parameter for which the default TCI state is set for each CORESET pool index may be, for example, enabledefaulttcistatepercoresetpoil index-r16 or a new high-level parameter.
It is assumed that a specific higher layer parameter is set and an offset between reception of PDCCH and DCI and reception of the corresponding PDSCH is smaller than a specific value (see fig. 13). In this case, the UE may also decide QCL/default beam based on the CORESET having the smallest ID among CORESETs set as PDCCH inverse multiplexing and linked with other coreets having different CORESET pool IDs (or apply TCI state/QCL corresponding to the CORESET as default QCL/default beam).
For example, consider a case where PDSCH is scheduled by pdcch#1/dci#1 corresponding to CORESET pool id=0 and pdcch#2/dci#2 corresponding to CORESET pool id=1. The UE may also apply a TCI state/QCL corresponding to CORESET having the smallest ID among CORESET corresponding to the PDCCH #1 and CORESET corresponding to the PDCCH #2 as a default QCL/default beam of the PDSCH.
In particular, the UE may also envisage that in relation to QCL parameters used in a PDCCH quasi co-location indication (e.g. PDCCH quasi co-location indication) of the coret associated with the monitored search space with the smallest CORESET ID (e.g. lowest controlResourceSetID) among CORESETs linked with different CORESET pool IDs that are set to be demultiplexed with the PDCCH in the latest time slot in which the other CORESETs linked with different CORESET pool IDs that are set to be demultiplexed with the PDCCH within the active BWP of the serving cell are monitored by the UE, DM-RS ports of PDSCH scheduled by two linked PDCCH candidates associated with different CORESET pool IDs are quasi co-located with RSs (the UE may assume that the DM-RS ports of PDSCH scheduled by two linked PDCCH candidates associated with different CORESETPoolID are quasi co-located with the RS(s) with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest controlResourceSetId among CORESETs, which are configured with linkage with another CORESET with different CORESETPoolID for PDCCH repetition, in the latest slot in which one or more CORESETs configured with linkage with another CORESET with different CORESETPoolID for PDCCH repetition that within the active BWP of the serving cell are monitored by the UE.).
Alternatively, when the offset between the reception of PDCCH/DCI and the reception of the corresponding PDSCH is smaller than the predetermined value, the UE may use the QCL of CORESET having the smallest CORESET ID among CORESETs of the latest slots (for example, last slots) in which CORESET monitoring is performed as the default QCL of the PDSCH. The latest time slot may be the latest time slot in which monitoring of CORESET (for example, CORESET corresponding to CORESET pool ID #0/# 1) is performed.
For example, it is assumed that an offset between at least one of PDCCH and DCI (for example, pdcch#2 in fig. 13) to be repeatedly transmitted and PDSCH is smaller than a specific value (when an offset between pdcch#1 and PDSCH is equal to or greater than a specific value). In this case, the UE may determine a default TCI state/QCL for the PDSCH based on the TCI state/QCL corresponding to pdcch#1 (CORESET pool id=0). For example, TCI state/QCL corresponding to pdcch#1 (CORESET pool id=0) may be used as default TCI state/QCL.
(UE capability information)
In the first to fourth aspects, the following UE capability (UE capability) may be set. The following UE capabilities may be replaced with parameters (e.g., higher layer parameters) set to the UE from the network (e.g., base station).
UE capability information related to repetition of a PDCCH supporting multiple TRPs (e.g., M-TRP) may also be defined.
UE capability information related to whether PDCCH repetition with multiple TRPs of PDCCH candidates linked by two CORESETs having different CORESET pool IDs is supported may also be defined.
It may also be defined if the UE capability information related to the default QCL/default beam is supported for PDSCH scheduled by PDCCH repetition in two CORESETs with different CORESET pool IDs in case the scheduling offset is small than a certain value (e.g. timeduration forqcl).
The first to fourth aspects may be applied to a UE supporting/reporting at least one of the UE capabilities described above. Alternatively, the first to fourth aspects may be applied to UEs to which corresponding higher-layer parameters are set from the network.
(Wireless communication System)
The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the embodiments of the present disclosure or a combination thereof.
Fig. 14 is a diagram showing an example of a schematic configuration of a radio communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication by using long term evolution (Long Term Evolution (LTE)) standardized by the third generation partnership project (Third Generation Partnership Project (3 GPP)), the fifth generation mobile communication system new wireless (5 th generation mobile communication system New Radio (5G NR)), or the like.
The wireless communication system 1 may support dual connection (Multi-RAT dual connection (Multi-RAT Dual Connectivity (MR-DC))) between a plurality of radio access technologies (Radio Access Technology (RATs)). MR-DC may also include a dual connection of LTE (evolved universal terrestrial radio Access (Evolved Universal Terrestrial Radio Access (E-UTRA))) with NR (E-UTRA-NR dual connection (E-UTRA-NR Dual Connectivity (EN-DC))), NR with LTE (NR-E-UTRA dual connection (NR-E-UTRA Dual Connectivity (NE-DC))), etc.
In EN-DC, a base station (eNB) of LTE (E-UTRA) is a Master Node (MN), and a base station (gNB) of NR is a Slave Node (SN). In NE-DC, the base station (gNB) of NR is MN and the base station (eNB) of LTE (E-UTRA) is SN.
The wireless communication system 1 may also support dual connections between multiple base stations within the same RAT (e.g., dual connection (NR-NR dual connection (NR-NR Dual Connectivity (NN-DC))) of a base station (gNB) where both MN and SN are NRs).
The radio communication system 1 may further include: a base station 11 forming a macro cell C1 having a relatively wide coverage area, and base stations 12 (12 a-12C) disposed in the macro cell C1 and forming a small cell C2 narrower than the macro cell C1. The user terminal 20 may also be located in at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to those shown in the drawings. Hereinafter, the base station 11 and the base station 12 are collectively referred to as a base station 10 without distinction.
The user terminal 20 may also be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) using a plurality of component carriers (Component Carrier (CC)) and Dual Connection (DC).
Each CC may be included in at least one of the first Frequency band (Frequency Range 1 (FR 1)) and the second Frequency band (Frequency Range 2 (FR 2))). The macrocell C1 may be included in the FR1 and the small cell C2 may be included in the FR 2. For example, FR1 may be a frequency band of 6GHz or less (lower than 6GHz (sub-6 GHz)), and FR2 may be a frequency band higher than 24GHz (above-24 GHz)). The frequency bands, definitions, and the like of FR1 and FR2 are not limited thereto, and for example, FR1 may correspond to a frequency band higher than FR 2.
The user terminal 20 may communicate with at least one of time division duplex (Time Division Duplex (TDD)) and frequency division duplex (Frequency Division Duplex (FDD)) in each CC.
The plurality of base stations 10 may also be connected by wire (e.g., optical fiber based on a common public radio interface (Common Public Radio Interface (CPRI)), an X2 interface, etc.) or wireless (e.g., NR communication). For example, when NR communication is utilized as a backhaul between the base stations 11 and 12, the base station 11 corresponding to a higher-level station may be referred to as an integrated access backhaul (Integrated Access Backhaul (IAB)) donor (donor), and the base station 12 corresponding to a relay station (relay) may be referred to as an IAB node.
The base station 10 may also be connected to the core network 30 via other base stations 10 or directly. The Core Network 30 may include at least one of an evolved packet Core (Evolved Packet Core (EPC)), a 5G Core Network (5 GCN), a next generation Core (Next Generation Core (NGC)), and the like, for example.
The user terminal 20 may be a terminal supporting at least one of communication schemes such as LTE, LTE-a, and 5G.
In the wireless communication system 1, a wireless access scheme based on orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing (OFDM)) may be used. For example, cyclic prefix OFDM (Cyclic Prefix OFDM (CP-OFDM)), discrete fourier transform spread OFDM (Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access (OFDMA)), single carrier frequency division multiple access (Single Carrier Frequency Division Multiple Access (SC-FDMA)), and the like may be used in at least one of Downlink (DL)) and Uplink (UL).
The radio access scheme may also be referred to as waveform (waveform). In the radio communication system 1, other radio access schemes (for example, other single carrier transmission schemes and other multi-carrier transmission schemes) may be applied to the UL and DL radio access schemes.
In the radio communication system 1, as the downlink channel, a downlink shared channel (physical downlink shared channel (Physical Downlink Shared Channel (PDSCH))), a broadcast channel (physical broadcast channel (Physical Broadcast Channel (PBCH)))), a downlink control channel (physical downlink control channel (Physical Downlink Control Channel (PDCCH))), or the like shared by the user terminals 20 may be used.
In the radio communication system 1, an uplink shared channel (physical uplink shared channel (Physical Uplink Shared Channel (PUSCH))), an uplink control channel (physical uplink control channel (Physical Uplink Control Channel (PUCCH))), a random access channel (physical random access channel (Physical Random Access Channel (PRACH))), or the like shared by the user terminals 20 may be used as the uplink channel.
User data, higher layer control information, system information blocks (System Information Block (SIBs)) and the like are transmitted through the PDSCH. User data, higher layer control information, etc. may also be transmitted through PUSCH. In addition, a master information block (Master Information Block (MIB)) may also be transmitted through the PBCH.
Lower layer control information may also be transmitted through the PDCCH. The lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI))) including scheduling information of at least one of PDSCH and PUSCH.
The DCI for scheduling PDSCH may be referred to as DL assignment, DL DCI, or the like, and the DCI for scheduling PUSCH may be referred to as UL grant, UL DCI, or the like. The PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.
In the detection of PDCCH, a control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may also be utilized. CORESET corresponds to searching for the resources of DCI. The search space corresponds to a search region of PDCCH candidates (PDCCH candidates) and a search method. A CORESET may also be associated with one or more search spaces. The UE may also monitor CORESET associated with a certain search space based on the search space settings.
One search space may also correspond to PDCCH candidates corresponding to one or more aggregation levels (aggregation Level). One or more search spaces may also be referred to as a set of search spaces. In addition, "search space", "search space set", "search space setting", "search space set setting", "CORESET setting", and the like of the present disclosure may also be replaced with each other.
Uplink control information (Uplink Control Information (UCI)) including at least one of channel state information (Channel State Information (CSI)), acknowledgement information (for example, also referred to as hybrid automatic repeat request acknowledgement (Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)), ACK/NACK, etc.), and scheduling request (Scheduling Request (SR)) may be transmitted through the PUCCH. The random access preamble for establishing a connection with a cell may also be transmitted through the PRACH.
In addition, in the present disclosure, downlink, uplink, etc. may also be expressed without "link". It may be expressed that the "Physical" is not provided at the beginning of each channel.
In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted. In the wireless communication system 1, as DL-RS, a Cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), and the like may be transmitted.
The synchronization signal may be at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)), for example. The signal blocks including SS (PSS, SSs) and PBCH (and DMRS for PBCH) may also be referred to as SS/PBCH blocks, SS blocks (SSB)), or the like. In addition, SS, SSB, etc. may also be referred to as reference signals.
In the wireless communication system 1, as an uplink reference signal (Uplink Reference Signal (UL-RS)), a reference signal for measurement (sounding reference signal (Sounding Reference Signal (SRS))), a reference signal for Demodulation (DMRS), and the like may be transmitted. In addition, the DMRS may also be referred to as a user terminal specific reference signal (UE-specific Reference Signal).
(base station)
Fig. 15 is a diagram showing an example of a configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transmitting/receiving unit 120, a transmitting/receiving antenna 130, and a transmission path interface (transmission line interface (transmission line interface)) 140. The control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided with one or more components.
In this example, the functional blocks of the characteristic part in the present embodiment are mainly shown, and it is also conceivable that the base station 10 has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
The control unit 110 performs control of the entire base station 10. The control unit 110 can be configured by a controller, a control circuit, or the like described based on common knowledge in the technical field of the present disclosure.
The control unit 110 may also control generation of signals, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission/reception, measurement, and the like using the transmission/reception unit 120, the transmission/reception antenna 130, and the transmission path interface 140. The control unit 110 may generate data, control information, a sequence (sequence), and the like transmitted as signals, and forward the generated data to the transmitting/receiving unit 120. The control unit 110 may perform call processing (setting, release, etc.) of the communication channel, state management of the base station 10, management of radio resources, and the like.
The transmitting/receiving unit 120 may include a baseband (baseband) unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may also include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting/receiving unit 120 may be configured of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter (phase shifter), a measurement circuit, a transmitting/receiving circuit, and the like, which are described based on common knowledge in the technical field of the present disclosure.
The transmitting/receiving unit 120 may be configured as an integral transmitting/receiving unit, or may be configured by a transmitting unit and a receiving unit. The transmission unit may be composed of the transmission processing unit 1211 and the RF unit 122. The receiving unit may be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.
The transmitting/receiving antenna 130 may be constituted by an antenna described based on common knowledge in the technical field of the present disclosure, for example, an array antenna or the like.
The transmitting/receiving unit 120 may transmit the downlink channel, the synchronization signal, the downlink reference signal, and the like. The transmitting/receiving unit 120 may receive the uplink channel, the uplink reference signal, and the like.
The transmitting-receiving unit 120 may also form at least one of a transmit beam and a receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), and the like.
The transmission/reception section 120 (transmission processing section 1211) may perform processing of a packet data convergence protocol (Packet Data Convergence Protocol (PDCP)) layer, processing of a radio link control (Radio Link Control (RLC)) layer (for example, RLC retransmission control), processing of a medium access control (Medium Access Control (MAC)) layer (for example, HARQ retransmission control), and the like with respect to data, control information, and the like acquired from the control section 110, for example, to generate a bit sequence to be transmitted.
The transmission/reception section 120 (transmission processing section 1211) may perform transmission processing such as channel coding (error correction coding may be included), modulation, mapping, filter processing, discrete fourier transform (Discrete Fourier Transform (DFT)) processing (if necessary), inverse fast fourier transform (Inverse Fast Fourier Transform (IFFT)) processing, precoding, and digital-to-analog conversion on a bit string to be transmitted, and output a baseband signal.
The transmitting/receiving unit 120 (RF unit 122) may perform modulation, filter processing, amplification, etc. for the baseband signal in the radio frequency band, and transmit the signal in the radio frequency band via the transmitting/receiving antenna 130.
On the other hand, the transmitting/receiving unit 120 (RF unit 122) may amplify, filter-process, demodulate a baseband signal, and the like, with respect to a signal in a radio frequency band received through the transmitting/receiving antenna 130.
The transmission/reception section 120 (reception processing section 1212) may apply, to the acquired baseband signal, reception processing such as analog-to-digital conversion, fast fourier transform (Fast Fourier Transform (FFT)) processing, inverse discrete fourier transform (Inverse Discrete Fourier Transform (IDFT)) processing (if necessary), filter processing, demapping, demodulation, decoding (error correction decoding may be included), MAC layer processing, RLC layer processing, and PDCP layer processing, and acquire user data.
The transmitting-receiving unit 120 (measuring unit 123) may also perform measurements related to the received signals. For example, measurement section 123 may perform radio resource management (Radio Resource Management (RRM)) measurement, channel state information (Channel State Information (CSI)) measurement, and the like based on the received signal. The measurement unit 123 may also measure reception power (for example, reference signal reception power (Reference Signal Received Power (RSRP))), reception quality (for example, reference signal reception quality (Reference Signal Received Quality (RSRQ)), signal-to-interference-plus-noise ratio (Signal to Interference plus Noise Ratio (SINR)), signal-to-noise ratio (Signal to Noise Ratio (SNR))), signal strength (for example, received signal strength indicator (Received Signal Strength Indicator (RSSI))), propagation path information (for example, CSI), and the like. The measurement results may also be output to the control unit 110.
The transmission path interface 140 may transmit and receive signals (backhaul signaling) to and from devices, other base stations 10, and the like included in the core network 30, or may acquire and transmit user data (user plane data), control plane data, and the like for the user terminal 20.
In addition, the transmitting unit and the receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.
The transmitting/receiving unit 120 may transmit a MAC CE including information related to activation of a transmission setting index (TCI) state of a physical shared channel. When one physical shared channel is scheduled by a plurality of downlink control channels supporting application of different control resource set pool indexes, the control unit 110 may indicate a TCI state corresponding to the physical shared channel by using a field related to a TCI state included in at least one of a plurality of downlink control information transmitted by the plurality of downlink control channels, respectively.
The transmitting/receiving unit 120 may transmit one physical shared channel scheduled by a plurality of downlink control channels supporting applications of different control resource set pool indexes to the terminal. The control unit 110 may determine that the physical shared channel is received based on a default TCI state set for each control resource pool index or a default TCI state set without association with the control resource pool index in the terminal when an offset between at least one of the plurality of downlink control channels and the physical shared channel is smaller than a specific value.
(user terminal)
Fig. 16 is a diagram showing an example of a configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting/receiving unit 220, and a transmitting/receiving antenna 230. The control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided with one or more types.
In this example, the functional blocks of the characteristic part in the present embodiment are mainly shown, and it is also conceivable that the user terminal 20 has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.
The control unit 210 performs control of the entire user terminal 20. The control unit 210 can be configured by a controller, a control circuit, or the like described based on common knowledge in the technical field of the present disclosure.
The control unit 210 may also control the generation of signals, mapping, etc. The control unit 210 may control transmission/reception, measurement, and the like using the transmission/reception unit 220 and the transmission/reception antenna 230. The control unit 210 may generate data, control information, a sequence, and the like transmitted as signals, and forward the generated data to the transmitting/receiving unit 220.
The transceiver unit 220 may also include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transmitting/receiving unit 220 may be configured of a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting/receiving circuit, and the like, which are described based on common knowledge in the technical field of the present disclosure.
The transmitting/receiving unit 220 may be configured as an integral transmitting/receiving unit, or may be configured by a transmitting unit and a receiving unit. The transmission means may be constituted by the transmission processing means 2211 and the RF means 222. The receiving unit may be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.
The transmitting/receiving antenna 230 may be constituted by an antenna described based on common knowledge in the technical field of the present disclosure, for example, an array antenna or the like.
The transceiver unit 220 may also receive the above-described downlink channel, synchronization signal, downlink reference signal, and the like. The transceiver unit 220 may transmit the uplink channel, the uplink reference signal, and the like.
The transmitting-receiving unit 220 may also form at least one of a transmit beam and a receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), and the like.
The transmission/reception section 220 (transmission processing section 2211) may perform, for example, PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control) and the like for the data, control information and the like acquired from the control section 210, and generate a bit sequence to be transmitted.
The transmission/reception section 220 (transmission processing section 2211) may perform transmission processing such as channel coding (error correction coding may be included), modulation, mapping, filter processing, DFT processing (as needed), IFFT processing, precoding, digital-to-analog conversion, and the like for a bit string to be transmitted, and output a baseband signal.
Further, whether to apply DFT processing may be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is activated (enabled), the transmission/reception section 220 (transmission processing section 2211) may perform DFT processing as the transmission processing for transmitting the channel using a DFT-s-OFDM waveform, or, if not, the transmission/reception section 220 (transmission processing section 2211) may not perform DFT processing as the transmission processing.
The transmitting/receiving unit 220 (RF unit 222) may perform modulation, filter processing, amplification, etc. for the baseband signal in the radio frequency band, and transmit the signal in the radio frequency band via the transmitting/receiving antenna 230.
On the other hand, the transmitting/receiving unit 220 (RF unit 222) may amplify, filter-process, demodulate a baseband signal, and the like, with respect to a signal in a radio frequency band received through the transmitting/receiving antenna 230.
The transmitting/receiving section 220 (reception processing section 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, decoding (error correction decoding may be included), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data.
The transceiver unit 220 (measurement unit 223) may also perform measurements related to the received signals. For example, the measurement unit 223 may also perform RRM measurement, CSI measurement, and the like based on the received signal. The measurement unit 223 may also measure for received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may also be output to the control unit 210.
The transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.
The transmitting/receiving unit 220 may also receive a MAC CE including information related to activation of a transmission setting index (TCI) state of a physical shared channel.
When one physical shared channel is scheduled by a plurality of downlink control channels supporting application of different control resource set pool indexes, control section 210 may determine a TCI state corresponding to the physical shared channel based on a field related to a TCI state included in at least one of a plurality of pieces of downlink control information transmitted by the plurality of downlink control channels, respectively.
The code points contained in the field associated with the TCI state may also be associated with the TCI state that is activated by the MAC CE corresponding to the particular control resource set pool index. Alternatively, the code point included in the field related to the TCI state may be associated with a TCI state activated by the MAC CE corresponding to the first control resource set pool index and a TCI state activated by the MAC CE corresponding to the second control resource set pool index. Alternatively, the code points contained in the field related to the TCI state may also be associated with a TCI state that is activated by a MAC CE that does not contain information related to the control resource set pool index.
The transceiver unit 220 may also receive a plurality of downlink control channels for applications that are supported by different control resource set pool indexes.
The control unit 210 may control reception of the physical shared channel based on a default TCI state set for each control resource pool index or a default TCI state set without associating with the control resource pool index when an offset between at least one of the plurality of downlink control channels and the physical shared channel scheduled by the plurality of downlink control channels is smaller than a specific value.
The control unit 210 may determine the quasi co-location of the physical shared channel based on a specific control resource set among the control resource sets monitored in the most recent time slot in which the control resource set is monitored. Alternatively, the control unit 210 may determine the quasi co-location of the physical shared channel based on a specific control resource set corresponding to the control resource pool index of a specific downlink control channel among the plurality of downlink control channels. Alternatively, the control unit 210 may determine the quasi co-location of the physical shared channel based on a specific control resource set among control resource sets corresponding to at least one of the plurality of downlink control channels.
(hardware construction)
The block diagrams used in the description of the above embodiments show blocks of functional units. These functional blocks (structural units) are implemented by any combination of at least one of hardware and software. The implementation method of each functional block is not particularly limited. That is, each functional block may be realized by one device physically or logically combined, or two or more devices physically or logically separated may be directly or indirectly connected (for example, by a wire, a wireless, or the like) and realized by these plural devices. The functional blocks may also be implemented by combining the above-described device or devices with software.
Here, the functions include, but are not limited to, judgment, decision, judgment, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, establishment, comparison, assumption, expectation, view, broadcast (broadcasting), notification (notification), communication (communication), forwarding (forwarding), configuration (configuration), reconfiguration (reconfiguration), allocation (mapping), assignment (allocation), and the like. For example, a functional block (structural unit) that realizes the transmission function may also be referred to as a transmission unit (transmitting unit), a transmitter (transmitter), or the like. As described above, the implementation method is not particularly limited.
For example, a base station, a user terminal, and the like in one embodiment of the present disclosure may also function as a computer that performs the processing of the wireless communication method of the present disclosure. Fig. 17 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to one embodiment. The base station 10 and the user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.
In addition, in the present disclosure, terms of devices, circuits, apparatuses, parts (sections), units, and the like can be replaced with each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to not include a part of the devices.
For example, the processor 1001 is shown as only one, but there may be multiple processors. Further, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or by other means. The processor 1001 may be realized by one or more chips.
Each function in the base station 10 and the user terminal 20 is realized by, for example, reading specific software (program) into hardware such as the processor 1001 and the memory 1002, performing an operation by the processor 1001, controlling communication via the communication device 1004, or controlling at least one of reading and writing of data in the memory 1002 and the memory 1003.
The processor 1001, for example, causes an operating system to operate to control the entire computer. The processor 1001 may be configured by a central processing unit (Central Processing Unit (CPU)) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, at least a part of the control unit 110 (210), the transmitting/receiving unit 120 (220), and the like described above may be implemented by the processor 1001.
Further, the processor 1001 reads out a program (program code), a software module, data, or the like from at least one of the memory 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiments can be used. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and operated in the processor 1001, and the same may be implemented for other functional blocks.
The Memory 1002 may be a computer-readable recording medium, and may be configured from at least one of a Read Only Memory (ROM), an erasable programmable Read Only Memory (Erasable Programmable ROM (EPROM)), an electrically erasable programmable Read Only Memory (Electrically EPROM (EEPROM)), a random access Memory (Random Access Memory (RAM)), and other suitable storage media. The memory 1002 may also be referred to as a register, a cache, a main memory (main storage), or the like. The memory 1002 can store programs (program codes), software modules, and the like executable to implement a wireless communication method according to one embodiment of the present disclosure.
The storage 1003 may also be a computer-readable recording medium, for example, constituted by at least one of a flexible disk (flexible Disc), a soft (registered trademark)) disk, an magneto-optical disk (for example, a Compact disk read only memory (CD-ROM), etc., a digital versatile disk, a Blu-ray (registered trademark) disk, a removable magnetic disk (removables), a hard disk drive, a smart card (smart card), a flash memory device (for example, card, stick, key drive), a magnetic stripe (strip), a database, a server, and other suitable storage media. The storage 1003 may also be referred to as secondary storage.
The communication device 1004 is hardware (transmission/reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like, for example. In order to realize at least one of frequency division duplexing (Frequency Division Duplex (FDD)) and time division duplexing (Time Division Duplex (TDD)), the communication device 1004 may be configured to include a high frequency switch, a duplexer, a filter, a frequency synthesizer, and the like. For example, the transmitting/receiving unit 120 (220), the transmitting/receiving antenna 130 (230), and the like described above may be implemented by the communication device 1004. The transmitting/receiving unit 120 (220) may be implemented by physically or logically separate transmitting units 120a (220 a) and receiving units 120b (220 b).
The input device 1005 is an input apparatus (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives an input from the outside. The output device 1006 is an output apparatus (for example, a display, a speaker, a light emitting diode (Light Emitting Diode (LED)) lamp, or the like) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
The processor 1001, the memory 1002, and other devices are connected by a bus 1007 for communicating information. The bus 1007 may be configured by a single bus or may be configured by different buses between devices.
The base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (Digital Signal Processor (DSP)), an application specific integrated circuit (Application Specific Integrated Circuit (ASIC)), a programmable logic device (Programmable Logic Device (PLD)), and a field programmable gate array (Field Programmable Gate Array (FPGA)), or may use the hardware to realize a part or all of the functional blocks. For example, the processor 1001 may also be implemented with at least one of these hardware.
(modification)
In addition, with respect to terms described in the present disclosure and terms required for understanding the present disclosure, terms having the same or similar meanings may be substituted. For example, channels, symbols, and signals (signals or signaling) may also be interchanged. In addition, the signal may also be a message. The Reference Signal (RS) can also be simply referred to as RS, and may also be referred to as Pilot (Pilot), pilot Signal, or the like, depending on the standard applied. In addition, the component carrier (Component Carrier (CC)) may also be referred to as a cell, a frequency carrier, a carrier frequency, or the like.
A radio frame may also consist of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the radio frame may also be referred to as a subframe. Further, a subframe may also be formed of one or more slots in the time domain. The subframes may also be a fixed length of time (e.g., 1 ms) independent of the parameter set (numerology).
Here, the parameter set may also refer to a communication parameter applied in at least one of transmission and reception of a certain signal or channel. For example, the parameter set may also represent at least one of a subcarrier spacing (SubCarrier Spacing (SCS)), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (Transmission Time Interval (TTI)), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by a transceiver in a frequency domain, a specific windowing (windowing) process performed by a transceiver in a time domain, and the like.
A slot may also be formed from one or more symbols in the time domain, orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing (OFDM)) symbols, single carrier frequency division multiple access (Single Carrier Frequency Division Multiple Access (SC-FDMA)) symbols, and so on. Furthermore, the time slots may also be time units based on parameter sets.
The time slot may also contain a plurality of mini-slots. Each mini-slot may also be formed of one or more symbols in the time domain. In addition, the mini-slot may also be referred to as a sub-slot. Mini-slots may also be made up of a fewer number of symbols than slots. PDSCH (or PUSCH) transmitted in a larger time unit than the mini-slot may also be referred to as PDSCH (PUSCH) mapping type a. PDSCH (or PUSCH) transmitted using mini-slots may also be referred to as PDSCH (PUSCH) mapping type B.
The radio frame, subframe, slot, mini-slot, and symbol each represent a unit of time when a signal is transmitted. The radio frames, subframes, slots, mini-slots, and symbols may also use other designations that each corresponds to. In addition, the frame, subframe, slot, mini-slot, symbol, and the like units in the present disclosure may also be replaced with each other.
For example, one subframe may also be referred to as a TTI, a plurality of consecutive subframes may also be referred to as a TTI, and one slot or one mini-slot may also be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the conventional LTE, may be a period (for example, 1 to 13 symbols) shorter than 1ms, or may be a period longer than 1 ms. The unit indicating the TTI may be referred to as a slot, a mini-slot, or the like, instead of a subframe.
Here, TTI refers to, for example, a scheduled minimum time unit in wireless communication. For example, in the LTE system, a base station performs scheduling for each user terminal to allocate radio resources (frequency bandwidth, transmission power, and the like that can be used in each user terminal) in TTI units. In addition, the definition of TTI is not limited thereto.
The TTI may be a transmission time unit of a data packet (transport block), a code block, a codeword, or the like subjected to channel coding, or may be a processing unit such as scheduling or link adaptation. In addition, when a TTI is given, a time interval (e.g., the number of symbols) to which a transport block, a code block, a codeword, etc. is actually mapped may also be shorter than the TTI.
In addition, in the case where one slot or one mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may also be the minimum time unit of scheduling. In addition, the number of slots (mini-slots) constituting the minimum time unit of the schedule can also be controlled.
A TTI having a time length of 1ms may also be referred to as a normal TTI (TTI in 3gpp rel.8-12), a standard TTI, a long TTI, a normal subframe, a standard subframe, a long subframe, a slot, etc. A TTI that is shorter than a normal TTI may also be referred to as a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini-slot, a sub-slot, a slot, etc.
In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be replaced with a TTI having a time length exceeding 1ms, and a short TTI (e.g., a shortened TTI, etc.) may be replaced with a TTI having a TTI length less than the long TTI and a TTI length of 1ms or more.
A Resource Block (RB) is a Resource allocation unit of a time domain and a frequency domain, and may include one or a plurality of consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the parameter set, and may be 12, for example. The number of subcarriers included in the RB may also be decided based on the parameter set.
Further, the RB may also contain one or more symbols in the time domain, and may be one slot, one mini-slot, one subframe, or one TTI length. One TTI, one subframe, etc. may also be respectively composed of one or more resource blocks.
In addition, one or more RBs may also be referred to as Physical Resource Blocks (PRBs), subcarrier groups (SCGs), resource element groups (Resource Element Group (REGs)), PRB pairs, RB peering.
Furthermore, a Resource block may also be composed of one or more Resource Elements (REs). For example, one RE may be a subcarrier and a radio resource area of one symbol.
A Bandwidth Part (BWP) (which may also be referred to as a partial Bandwidth or the like) may also represent a subset of consecutive common RBs (common resource blocks (common resource blocks)) for a certain parameter set in a certain carrier. Here, the common RB may also be determined by an index of the RB with reference to the common reference point of the carrier. PRBs may be defined in a BWP and numbered in the BWP.
The BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). For the UE, one or more BWP may be set in one carrier.
At least one of the set BWP may be active, and the UE may not contemplate transmission and reception of a specific channel/signal other than the active BWP. In addition, "cell", "carrier", etc. in the present disclosure may also be replaced with "BWP".
The above-described configurations of radio frames, subframes, slots, mini slots, symbols, and the like are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the Cyclic Prefix (CP) length, and the like can be variously changed.
The information, parameters, and the like described in the present disclosure may be expressed in absolute values, relative values to a specific value, or other corresponding information. For example, radio resources may also be indicated by a particular index.
In the present disclosure, the names used for parameters and the like are not restrictive names in all aspects. Further, the mathematical expression or the like using these parameters may also be different from that explicitly disclosed in the present disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting names in all respects.
Information, signals, etc. described in this disclosure may also be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips (chips), and the like may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.
Further, information, signals, etc. can be output in at least one of the following directions: from higher layer (upper layer) to lower layer (lower layer), and from lower layer to higher layer. Information, signals, etc. may also be input and output via a plurality of network nodes.
The input/output information, signals, and the like may be stored in a specific location (for example, a memory), or may be managed by a management table. The input and output information, signals, etc. may be overwritten, updated, or added. The outputted information, signals, etc. may also be deleted. The input information, signals, etc. may also be transmitted to other devices.
The notification of information is not limited to the embodiment described in the present disclosure, but may be performed by other methods. For example, notification of information in the present disclosure may also be implemented by physical layer signaling (e.g., downlink control information (Downlink Control Information (DCI))), uplink control information (Uplink Control Information (UCI)))), higher layer signaling (e.g., radio resource control (Radio Resource Control (RRC)) signaling, broadcast information (master information block (Master Information Block (MIB)), system information block (System Information Block (SIB)) or the like), medium access control (Medium Access Control (MAC)) signaling), other signals, or a combination thereof.
The physical Layer signaling may be referred to as Layer 1/Layer 2 (L1/L2)) control information (L1/L2 control signal), L1 control information (L1 control signal), or the like. The RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration)) message, or the like. The MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).
Note that the notification of specific information (for example, notification of "X") is not limited to explicit notification, and may be performed implicitly (for example, by notification of no specific information or notification of other information).
The determination may be performed by a value (0 or 1) represented by one bit, a true or false value (boolean) represented by true or false, or a comparison of values (e.g., with a specific value).
Software, whether referred to as software (firmware), middleware (middleware-ware), microcode (micro-code), hardware description language, or by other names, should be broadly interpreted as meaning instructions, instruction sets, codes (codes), code segments (code fragments), program codes (program codes), programs (programs), subroutines (sub-programs), software modules (software modules), applications (applications), software applications (software application), software packages (software packages), routines (routines), subroutines (sub-routines), objects (objects), executable files, threads of execution, procedures, functions, and the like.
In addition, software, instructions, information, etc. may also be transmitted and received via a transmission medium. For example, in the case where software is transmitted from a website, server, or other remote source (remote source) using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (Digital Subscriber Line (DSL)), etc.) and wireless technology (infrared, microwave, etc.), at least one of the wired technology and wireless technology is included in the definition of transmission medium.
The terms "system" and "network" as used in this disclosure can be used interchangeably. "network" may also refer to devices (e.g., base stations) contained in a network.
In the context of the present disclosure of the present invention, terms such as "precoding", "precoder", "weight", "Quasi Co-Location", "transmission setting instruction state (Transmission Configuration Indication state (TCI state))", "spatial relation", "spatial filter (spatial domain filter)", "transmission power", "phase rotation", "antenna port group", "layer number", "rank", "resource set", "resource group", "beam width", "beam angle", "antenna element", "panel", and the like can be used interchangeably.
In the present disclosure, terms such as "Base Station (BS))", "radio Base Station", "fixed Station", "NodeB", "eNB (eNodeB)", "gNB (gndeb)", "access Point", "Transmission Point (Transmission Point (TP))", "Reception Point (RP))", "Transmission Reception Point (Transmission/Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", and the like can be used interchangeably. There are also cases where the base station is referred to by terms of a macrocell, a small cell, a femtocell, a picocell, and the like.
The base station can accommodate one or more (e.g., three) cells. In the case of a base station accommodating a plurality of cells, the coverage area of the base station can be divided into a plurality of smaller areas, each of which can also provide communication services through a base station subsystem, such as a small base station for indoor use (remote radio head (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a portion or the entirety of the coverage area of at least one of the base station and the base station subsystem that is in communication service within that coverage area.
In the present disclosure, terms such as "Mobile Station (MS)", "User terminal", "User Equipment (UE)", and "terminal" are used interchangeably.
There are also situations where a mobile station is referred to by a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, hand-held communicator (hand set), user agent, mobile client, or several other suitable terms.
At least one of the base station and the mobile station may also be referred to as a transmitting apparatus, a receiving apparatus, a wireless communication apparatus, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile body, or the like. The mobile body may be a vehicle (e.g., a vehicle, an airplane, etc.), a mobile body that moves unmanned (e.g., an unmanned aerial vehicle (clone), an autonomous vehicle, etc.), or a robot (manned or unmanned). In addition, at least one of the base station and the mobile station includes a device that does not necessarily move when performing a communication operation. For example, at least one of the base station and the mobile station may be an internet of things (Internet of Things (IoT)) device such as a sensor.
In addition, the base station in the present disclosure may be replaced with a user terminal. For example, the various modes/embodiments of the present disclosure may also be applied to a structure in which communication between a base station and a user terminal is replaced with communication between a plurality of user terminals (for example, may also be referred to as Device-to-Device (D2D)), vehicle-to-evaluation (V2X), or the like. In this case, the user terminal 20 may have the functions of the base station 10 described above. In addition, terms such as "uplink", "downlink", and the like may be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, the uplink channel, the downlink channel, etc. may be replaced with a side channel.
Likewise, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.
In the present disclosure, an operation performed by a base station is sometimes performed by an upper node (upper node) thereof, as the case may be. Obviously, in a network comprising one or more network nodes (network nodes) with base stations, various operations performed for communication with a terminal may be performed by a base station, one or more network nodes other than the base station (e.g. considering a mobility management entity (Mobility Management Entity (MME)), a Serving-Gateway (S-GW)), or the like, but not limited thereto, or a combination thereof.
The embodiments described in the present disclosure may be used alone, in combination, or switched according to execution. The processing procedures, sequences, flowcharts, and the like of the embodiments and embodiments described in this disclosure may be changed in order as long as they are not contradictory. For example, for the methods described in the present disclosure, elements of the various steps are presented using the illustrated order, but are not limited to the particular order presented.
The various modes/embodiments described in the present disclosure can also be applied to long term evolution (Long Term Evolution (LTE)), LTE-Advanced (LTE-a), LTE-Beyond (LTE-B), upper 3G, IMT-Advanced, fourth generation mobile communication system (4 th generation mobile communication system (4G)), fifth generation mobile communication system (5 th generation mobile communication system (5G)), sixth generation mobile communication system (6 th generation mobile communication system (6G)), x-th generation mobile communication system (xth generation mobile communication system (xG) (xG (x is, for example, an integer, a small number)), future wireless access (Future Radio Access (FRA)), new-Radio Access Technology (RAT)), new wireless (New Radio (NR)), new wireless access (NX)), new generation wireless access (Future generation Radio access (FX)), global system (Global System for Mobile communications (GSM (registered trademark)), 2000, ultra mobile broadband (Ultra Mobile Broadband (IEEE) 802.11 (Fi-802.16 (Wi) (registered trademark)), wireless communication system (20, ultra-WideBand (registered trademark)), wireless communication systems (Bluetooth (20, ultra-WideBand), and the like, and other suitable methods based on them are obtained, multiple systems may also be applied in combination (e.g., LTE or LTE-a, in combination with 5G, etc.).
The term "based on" as used in the present disclosure does not mean "based only on" unless otherwise specified. In other words, the expression "based on" means "based only on" and "based at least on" both.
Any reference to elements using references to "first," "second," etc. in this disclosure does not fully define the amount or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, references to a first and second element do not indicate that only two elements may be employed, or that the first element must take precedence over the second element in some manner.
The term "determining" used in the present disclosure is in the case of including various operations. For example, the "judgment (decision)" may be a case where judgment (decision), calculation (calculation), processing (processing), derivation (development), investigation (investigation), search (lookup), search, inquiry (search in a table, database, or other data structure), confirmation (acceptance), or the like is regarded as "judgment (decision)".
The "determination (decision)" may be a case where reception (e.g., reception of information), transmission (e.g., transmission of information), input (input), output (output), access (processing) (e.g., access to data in a memory), or the like is regarded as "determination (decision)".
The "judgment (decision)" may be a case where resolution (resolution), selection (selection), selection (setting), establishment (establishment), comparison (comparison), or the like is regarded as "judgment (decision)". That is, the "judgment (decision)" may be a case where some actions are regarded as making the "judgment (decision)".
Further, "judgment (decision)" may be replaced with "assumption", "expectation", "consider", or the like.
The terms "connected", "coupled", or all variants thereof as used in this disclosure mean all connections or couplings, either direct or indirect, between two or more elements thereof, and can include the case where one or more intervening elements are present between two elements that are "connected" or "coupled" to each other. The combination or connection of the elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access".
In the present disclosure, in the case of connecting two elements, it can be considered that one or more wires, cables, printed electrical connections, etc. are used, and electromagnetic energy having wavelengths in the radio frequency domain, the microwave region, the optical (both visible and invisible) region, etc. are used as several non-limiting and non-inclusive examples to "connect" or "combine" with each other.
In the present disclosure, the term "a is different from B" may also mean that "a is different from B". In addition, the term may also mean that "A and B are each different from C". Terms such as "separate," coupled, "and the like may also be similarly construed as" different.
In the present disclosure, when "including", and variations thereof are used, these terms are meant to be inclusive in the same sense as the term "comprising". Further, the term "or" as used in this disclosure does not mean exclusive or.
In the present disclosure, for example, in the case where an article is appended by translation as in a, an, and the in english, the present disclosure may also include the case where a noun following the article is in plural form.
While the invention according to the present disclosure has been described in detail, it will be apparent to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as a modification and variation without departing from the spirit and scope of the invention defined based on the description of the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not intended to limit the invention in any way.

Claims (6)

1. A terminal, comprising:
a receiving unit that receives a MAC CE containing information related to activation of a transmission setting index TCI state of a physical shared channel; and
when one physical shared channel is scheduled by a plurality of downlink control channels supporting applications of different control resource pool indexes, a control unit determines a TCI state corresponding to the physical shared channel based on a field related to a TCI state included in at least one of a plurality of pieces of downlink control information transmitted by the plurality of downlink control channels, respectively.
2. The terminal of claim 1, wherein,
The code point contained in the field related to the TCI state is associated with the TCI state activated by the MAC CE corresponding to the particular control resource set pool index.
3. The terminal of claim 1, wherein,
the code point contained in the field related to the TCI state is associated with a TCI state activated by a MAC CE corresponding to the first control resource set pool index and a TCI state activated by a MAC CE corresponding to the second control resource set pool index.
4. The terminal of claim 1, wherein,
the code points contained in the field associated with the TCI state are associated with a TCI state that is activated by a MAC CE that does not contain information related to the control resource set pool index.
5. A wireless communication method for a terminal includes:
a step of receiving a MAC CE containing information related to activation of a transmission setting index TCI state of a physical shared channel; and
and a step of determining a TCI state corresponding to a physical shared channel based on a field related to the TCI state included in at least one of a plurality of pieces of downlink control information transmitted through the plurality of downlink control channels, when one physical shared channel is scheduled through a plurality of downlink control channels supporting applications of different control resource set pool indexes.
6. A base station, comprising:
a transmission unit that transmits a MAC CE including information related to activation of a transmission setting index TCI state of a physical shared channel; and
when one physical shared channel is scheduled by a plurality of downlink control channels supporting applications of different control resource pool indexes, a control unit indicates a TCI state corresponding to the physical shared channel by using a field related to a TCI state included in at least one of a plurality of pieces of downlink control information transmitted by the plurality of downlink control channels, respectively.
CN202180096279.6A 2021-04-05 2021-04-05 Terminal, wireless communication method and base station Pending CN117044342A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2021/014548 WO2022215141A1 (en) 2021-04-05 2021-04-05 Terminal, wireless communication method, and base station

Publications (1)

Publication Number Publication Date
CN117044342A true CN117044342A (en) 2023-11-10

Family

ID=83545246

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202180096279.6A Pending CN117044342A (en) 2021-04-05 2021-04-05 Terminal, wireless communication method and base station

Country Status (2)

Country Link
CN (1) CN117044342A (en)
WO (1) WO2022215141A1 (en)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3997832A4 (en) * 2019-07-11 2022-10-19 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
MX2022001654A (en) * 2019-08-08 2022-03-11 Ntt Docomo Inc Terminal and wireless communication method.

Also Published As

Publication number Publication date
WO2022215141A1 (en) 2022-10-13

Similar Documents

Publication Publication Date Title
CN113228773B (en) User terminal and wireless communication method
EP3914002A1 (en) User terminal and wireless communication method
CN114402687A (en) Terminal and wireless communication method
CN113940107B (en) Terminal, wireless communication method and system
CN114946239A (en) Terminal and wireless communication method
CN114830549A (en) Terminal and wireless communication method
CN116918397A (en) Terminal, wireless communication method and base station
CN116235586A (en) Terminal, wireless communication method and base station
CN114026912B (en) Terminal, base station, system and wireless communication method
CN116569630A (en) Terminal, wireless communication method and base station
CN116636243A (en) Terminal, wireless communication method and base station
CN116325854A (en) Terminal, wireless communication method and base station
CN116235589A (en) Terminal, wireless communication method and base station
CN114009118A (en) User terminal and wireless communication method
CN113455069A (en) User terminal and wireless communication method
CN116325858A (en) Terminal, wireless communication method and base station
CN116349353A (en) Terminal, wireless communication method and base station
CN116391425A (en) Terminal, wireless communication method and base station
WO2021090451A1 (en) Terminal and wireless communication method
CN116420402A (en) Terminal, wireless communication method and base station
CN116210256A (en) Terminal, wireless communication method and base station
CN116326040A (en) Terminal, wireless communication method and base station
CN116326026A (en) Terminal, wireless communication method and base station
CN114788235A (en) Terminal and wireless communication method
CN114128347A (en) User terminal and wireless communication method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination