Terminals, wireless communication methods, base stations and systems

Abstract

To improve the efficiency of resource utilization. [Solution] A terminal according to one aspect of the present disclosure has a receiving unit which receives setting information for resources available for an uplink (UL) which are arranged in the same time resources as resources available for a downlink (DL), and the resources available for DL ​​and the resources available for UL are set in a single serving cell, and a control unit which controls UL transmission in the resources available for UL based on the setting information.

Description

Technical Field

[0001] This disclosure relates to a terminal, a wireless communication method, a base station, and a system in a next-generation mobile communication system.

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was standardized for the purpose of further high-speed data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel.10-14) was standardized.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+(plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 and later, etc.) are also under consideration.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] In future wireless communication systems (e.g., NR), it is anticipated that multiple user terminals (User Equipment (UE)) will communicate in extremely high-density and high-traffic environments.

[0006] In this environment, it is anticipated that uplink (UL) resources will be insufficient compared to downlink (DL) resources.

[0007] However, previous NR specifications have not adequately considered methods for increasing uplink resources. If these methods cannot be properly controlled, system performance may deteriorate, such as increased latency and reduced coverage performance.

[0008] Therefore, one of the objectives of this disclosure is to provide terminals, wireless communication methods, base stations, and systems that improve resource utilization efficiency. [Means for solving the problem]

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives configuration information for resources available for an uplink (UL) that are arranged in the same time resources as resources available for a downlink (DL), and the resources available for the DL and the resources available for the UL are configured in a single serving cell, and a control unit that controls UL transmission on the resources available for the UL based on the configuration information. [Effects of the Invention]

[0010] According to one aspect of this disclosure, the efficiency of resource utilization can be improved. [Brief explanation of the drawing]

[0011] [Figure 1]Figure 1 shows the RRC information element "ServingCellConfig". [Figure 2] Figure 2 shows the RRC information element "PDSCH-Config". [Figure 3] Figure 3 shows the RRC information element "RateMatchPattern". [Figure 4] Figures 4A and 4B show an example of a slot configuration setting. [Figure 5] Figure 5 shows an example of an XDD configuration. [Figure 6] Figures 6A and 6B show examples of setting time-domain and frequency-domain resources for XDD operation. [Figure 7] Figure 7 shows an example of information elements related to the list of unavailable resource patterns according to Embodiment 1-1-1. [Figure 8] Figures 8A and 8B show examples of the application of unavailable resource patterns according to Embodiments 1-2-1 and 1-2-2. [Figure 9] Figures 9A and 9B show an example of the application of an unavailable resource pattern according to Embodiment 2-2. [Figure 10] Figure 10 shows an example of a schematic configuration of a wireless communication system according to one embodiment. [Figure 11] Figure 11 shows an example of the configuration of a base station according to one embodiment. [Figure 12] Figure 12 shows an example of the configuration of a user terminal according to one embodiment. [Figure 13] Figure 13 shows an example of the hardware configuration of a base station and a user terminal according to one embodiment. [Modes for carrying out the invention]

[0012] (TDD settings) In Release 15, for a UE, the settings of UL and DL (UL resources and DL resources) in Time Division Duplex (TDD) are performed. The UE may receive a higher layer parameter (TDD-UL-DL-ConfigCommon) regarding the cell-specific UL / DL TDD setting or a higher layer parameter (TDD-UL-DL-ConfigDedicated) regarding the UE-specific UL / DL TDD setting.

[0013] The higher layer parameter (TDD-UL-DL-ConfigCommon) regarding the cell-specific UL / DL TDD setting includes a parameter (referenceSubcarrierSpacing) for setting the reference subcarrier spacing and a parameter (TDD-UL-DL-Pattern) regarding the TDD UL and DL patterns.

[0014] The TDD-UL-DL-Pattern includes a parameter (dl-UL-TransmissionPeriodicity) for setting the period of the DL-UL pattern, a parameter (nrofDownlinkSlots) for setting the number of consecutive DL slots, a parameter (nrofDownlinkSymbols) for setting the number of consecutive DL symbols, a parameter (nrofUplinkSlots) for setting the number of consecutive UL slots, and a parameter (nrofUplinkSymbols) for setting the number of consecutive UL symbols.

[0015] In the higher layer parameter (TDD-UL-DL-ConfigDedicated) regarding the UE-specific UL / DL TDD setting, the slot setting and the slot index setting are performed.

[0016] The slot configuration is performed by the parameter TDD-UL-DL-SlotConfig. TDD-UL-DL-SlotConfig includes parameters related to the slot index (TDD-UL-DL-SlotIndex) and parameters related to the symbols constituting the slot (symbols). The parameter (symbols) related to the symbols constituting the slot sets any one of a parameter (allDownlink) indicating that all the symbols constituting the slot are used for DL, a parameter (allUplink) indicating that all the symbols constituting the slot are used for UL, or a parameter (explicit) explicitly indicating the number of symbols.

[0017] The parameter (explicit) explicitly indicating the number of symbols includes a parameter (nrofDownlinkSymbols) for setting the number of DL symbols and a parameter (nrofUplinkSymbols) for setting the number of UL symbols.

[0018] The UE determines the slot / symbol to be used for at least one of the transmission of UL signals / channels and the reception of DL signals / channels based on the above-mentioned parameters.

[0019] (Rate matching pattern of PDSCH) In NR defined up to Rel.16, the UE is defined for PDSCH resource mapping at the symbol level of the resource block (Resource Block (RB)).

[0020] The UE determines the resources for which the PDSCH is not mapped based on the set / indicated rate matching pattern.

[0021] The UE is configured with information about a list of rate match patterns included in the serving cell configuration information (e.g., the RRC information element "ServingCellConfig") (see Figure 1). This list contains configuration information (RateMatchPattern) for a maximum number of rate match patterns (e.g., 4) specified by maxNrofRateMatchPatterns. Each rate match pattern is identified by a rate match pattern ID (RateMatchPatternId).

[0022] The UE does not use the union of unavailable patterns (resources) set by one or more rate-matching patterns, which is included in the information about the list of rate-matching patterns, for mapping PDSCH resources. In other words, the UE performs PDSCH rate matching around the union of unavailable patterns (resources) set by one or more rate-matching patterns, which is included in the information about the list of rate-matching patterns.

[0023] Quasi-static rate matching may thus mean that PDSCH rate matching is based solely on higher-layer signaling (e.g., ServingCellConfig).

[0024] Furthermore, the UE is configured with information about a list of rate match patterns and information about rate match pattern groups (RateMatchPatternGroup), which are included in the UE-specific PDSCH configuration information (e.g., the RRC information element "PDSCH-Config"). This list contains the configuration information (RateMatchPattern) for a maximum of four rate match patterns, as defined by maxNrofRateMatchPatterns (see Figure 2). Each rate match pattern is identified by its rate match pattern ID (RateMatchPatternId).

[0025] The information regarding the RateMatchPatternGroup is determined by the information regarding the first RateMatchPatternGroup (rateMatchPatternGroup1) and the information regarding the second RateMatchPatternGroup (rateMatchPatternGroup2).

[0026] The information for the first rate match pattern group (rateMatchPatternGroup1) and the information for the second rate match pattern group (rateMatchPatternGroup2) each contain a number of rate match pattern IDs (RateMatchPatternId) specified by the maximum maxNrofRateMatchPatternsPerGroup (for example, 8).

[0027] The RateMatchPatternId included in the information for the first rate match pattern group (rateMatchPatternGroup1) and the information for the second rate match pattern group (rateMatchPatternGroup2) is associated with either the cell level (cellLevel) or the BWP level (bwpLevel) (see Figure 2).

[0028] The cell-level RateMatchPatternId is associated with the rate match pattern set in the ServingCellConfig information. Similarly, the BWP-level RateMatchPatternId is associated with the rate match pattern set in the PDSCH-Config information.

[0029] The UE activates a first rate match pattern group and a second rate match pattern group based on the rate match fields (rate match indicators) included in the DCI format (e.g., DCI format 1_1 / 1_2) used to schedule the PDSCH.

[0030] The number of bits in the rate matching field (rate matching indicator) ranges from 0 to 2 bits, depending on the number of rate matching pattern groups set.

[0031] When a first rate match pattern group and a second rate match pattern group are set, the UE determines whether to activate the first rate match pattern group based on the most significant bit (MSB) of the rate match field, and whether to activate the second rate match pattern group based on the least significant bit (LSB) of the rate match field.

[0032] The UE does not use the union of unavailable patterns (resources) set by one or more rate-match patterns related to the activated rate-match pattern group for PDSCH resource mapping. In other words, the UE performs PDSCH rate matching around the union of unavailable patterns (resources) set by one or more rate-match patterns related to the activated rate-match pattern group.

[0033] Dynamic rate matching may thus mean rate matching of PDSCH based on higher-layer signaling (e.g., at least one of ServingCellConfig and PDSCH-Config) and DCI.

[0034] The RateMatchPattern configuration information includes at least one of the following: information about the RateMatchPattern ID (rateMatchPatternId), information about the pattern type (patternType), and information about the subcarrier spacing (subcarrierSpacing) (see Figure 3).

[0035] The pattern type information (patternType) includes bitmap information consisting of resource block information (resourceBlocks), symbol information within resource blocks (symbolsInResourceBlock), periodicityAndPattern information, and CORESET ID information.

[0036] Information about resource blocks (resourceBlocks) may be a bitmap at the resource block level in the frequency domain. Information about symbols within resource blocks (symbolsInResourceBlock) may be a bitmap at the symbol level in the time domain.

[0037] In each bit of the resource block information (resourceBlocks), a bit indicating 1 sets an unavailable frequency position (to which rate matching will be applied) for the corresponding resource block. In Rel.16, the resource block information (resourceBlocks) can specify a range of up to 275 RB.

[0038] For each bit in the symbol information (symbolsInResourceBlock) within a resource block, a time position is set where the resource block corresponding to the bit showing 1 is unavailable (and rate matching is applied).

[0039] The information about symbols within a resource block (symbolsInResourceBlock) can be a bitmap representing symbols in one slot, or a bitmap representing symbols in two slots. In other words, in Rel.16, the information about resource blocks (resourceBlocks) can specify a range of up to two slots (28 symbols).

[0040] (XDD) Up to Rel.14, LTE primarily used Frequency Division Duplex (FDD), but also supported Time Division Duplex (TDD).

[0041] On the other hand, for NR from Rel.15 onwards, TDD was the main focus of consideration, while FDD was also supported at the same time (for example, migration of LTE bands).

[0042] In FDDs, DL reception and UL transmission can be performed simultaneously, which is preferable from the standpoint of reducing latency. On the other hand, in FDDs, the resource ratio of DL to UL is fixed (e.g., 1:1).

[0043] In TDD, it is possible to change the ratio of DL and UL resources. For example, in a typical environment where DL traffic is relatively high, it is possible to increase the amount of DL resources to improve DL throughput.

[0044] On the other hand, considering the time ratio of transmission and reception using Time Division Duplex (TDD) up to Rel.16, there are cases where the opportunities to transmit UL signals / channels are fewer than the opportunities to receive DL signals / channels. In such cases, the UE may not be able to transmit UL signals / channels frequently, raising concerns about delays in the transmission of important UL signals / channels. Furthermore, because the opportunities to transmit UL signals are fewer than the opportunities to receive DL signals, signal / channel congestion during UL transmission is also a concern. In addition, since the time resources available for transmitting UL signals / channels are limited in TDD, the application of UL coverage extension techniques such as repetition transmission is also limited.

[0045] In future wireless communication systems (e.g., Rel.17 / 18 and beyond), the introduction of a division duplex method combining TDD and Frequency Division Duplex (FDD) for UL and DL is being considered.

[0046] The division-duplex method may also be called XDD (Cross Division Duplex). XDD may mean a duplex method that frequency-division multiplexes DL and UL (allowing simultaneous use of DL and UL) within one component carrier (CC) of the TDD band, or across multiple CCs. When the duplex method is applied to multiple CCs, it may mean that in the time resources where DL is available in one CC, UL is available in another CC. The multiple CCs may be CCs in the same band.

[0047] Figure 4A shows an example of a TDD configuration as defined up to Rel.16. In the example shown in Figure 4A, the UE is configured with TDD slots / symbols using the bandwidth of one component carrier (CC) (which may also be called a cell or serving cell).

[0048] In the example shown in Figure 4A, the time ratio of DL slots to UL slots is 4:1. With this conventional TDD slot / symbol setting, sufficient UL time resources cannot be secured, which may lead to UL transmission delays and a decrease in coverage performance.

[0049] Figure 4B shows an example of an XDD configuration. In the example in Figure 4B, the resources used for receiving DL and the resources used for transmitting UL overlap in time within a single component carrier (CC). With such a resource configuration, UL resources can be secured, and the efficiency of resource utilization can be improved.

[0050] For example, as shown in the example in Figure 4B, by configuring DL (Downlink) at both ends of the frequency domain in a 1CC (One Carrier Convergence) and sandwiching UL (Ultralink) resources between the DLs, it is possible to avoid and mitigate cross-link interference (CLI) with neighboring carriers. In addition, a guard region may be set at the boundary between the DL resources and the UL resources.

[0051] Considering the complexity of handling self-interference, it is conceivable that only base stations use DL and UL resources simultaneously. In other words, for resources where DL and UL overlap in time, one UE may use the DL resource while another UE uses the UL resource.

[0052] Figure 5 shows an example of an XDD configuration. In the example shown in Figure 5, a portion of the DL resources in the TDD band are used as UL resources, resulting in a configuration where DL and UL partially overlap in time.

[0053] In the example shown in Figure 5, during the DL-only period, each of the multiple UEs (UE#1 and UE#2 in Figure 5) receives the DL channel / signal.

[0054] Furthermore, during periods when DL and UL overlap in time, one UE (UE#1 in the example in Figure 5) receives the DL channel / signal, while another UE (UE#2 in the example in Figure 5) transmits the UL channel / signal. During this period, the base station performs simultaneous transmission and reception of DL and UL.

[0055] Furthermore, during UL-only periods, each of the multiple UEs transmits a UL channel / signal.

[0056] In existing NRs (e.g., those defined up to Rel. 15 / 16), DL frequency resources and UL frequency resources in a UE carrier are configured as DL Bandwidth Parts (BWPs) and UL BWPs, respectively. Switching between DL / UL frequency resources requires the configuration of multiple BWPs and a BWP adaptation mechanism.

[0057] Furthermore, in existing NRs, the time resources in the TDD carrier for UE are configured in the TDD settings as at least one of DL, UL, and Flexible (FL).

[0058] Methods for configuring time-domain and frequency-domain resources for XDD operation are being considered. For example, for UE#1 in Figure 5, it is conceivable to configure the XDD resources (the period during which DL and UL overlap) while avoiding the use of portions of the UL resources used by other UEs (e.g., UE#2) (see Figure 6A).

[0059] Furthermore, for example, for UE#2 in Figure 5, it is possible to configure the XDD resources while avoiding the use of the DL resources used by other UEs (e.g., UE#1) (see Figure 6B).

[0060] However, the configuration of XDD resources for UE has not been sufficiently considered.

[0061] For example, for UE#1 in Figure 5, the time resource for the XDD portion is set as DL. However, there has been insufficient consideration as to whether the frequency resource for the XDD portion should be set separately from the frequency resource for the DL portion that is not the XDD portion (pure DL portion).

[0062] Resources unavailable to UE#1 in the XDD section can be used as ULs by other UEs, raising concerns that receiving DL signals / channels on those resources may cause CLIs to occur.

[0063] Furthermore, it is necessary to consider disabling the allocation of DL resources to resources that UE#1 in the XDD section cannot use. This consideration should be considered, for example, when allocating the remaining resources other than the unavailable resource to one UE or one RS.

[0064] Therefore, when setting / instructing DL resources in the XDD portion and DL resources outside the XDD portion separately, it is being considered to set an unavailable resource (e.g., a rate match pattern) that includes the UL portion in the XDD portion, so that the UE does not perform DL reception in that UL portion.

[0065] However, there are some limitations to the rate match patterns in the existing specifications. For example, existing rate match patterns are only applicable to PDSCH reception, and only one quasi-static rate match pattern and two dynamic rate match patterns can be configured.

[0066] Furthermore, for example, in UE#2 in Figure 5, the time resource for the XDD portion is set as UL. However, there has been insufficient consideration as to whether the frequency resource for the XDD portion should be set separately from the frequency resource for the UL portion that is not the XDD portion (pure UL portion).

[0067] In particular, it is conceivable that the configuration of resources for specific UL channels / signals (e.g., configured grant PUSCH / PUCCH / SRS / PRACH) may be restricted in the XDD portion. In order to transmit these specific UL channels / signals using UL resources in the XDD portion, separate configurations may be required for UL resources in the XDD portion and for UL resources outside the XDD portion.

[0068] It is also possible to apply common settings to both the UL resources in the XDD portion and the UL resources that are not in the XDD portion, but the available UL resources will be limited.

[0069] If separate UL resources for the XDD portion and non-XDD portion are configured for each specific UL channel / signal, the signaling overhead will increase.

[0070] Therefore, in order to reduce signaling overhead, when setting / instructing UL resources in the XDD portion and UL resources outside the XDD portion separately, it is being considered to set an unavailable resource (e.g., a rate match pattern) that includes the DL portion in the XDD portion, so that the UE does not perform UL transmission in that DL portion.

[0071] However, there has been insufficient consideration given to how to configure / instruct resources that are unavailable for DL / UL. If the method for configuring / instructing resources is unclear, proper transmission and reception may not be possible, potentially leading to a decrease in communication quality and throughput.

[0072] Therefore, the inventors conceived a method that can achieve resource configuration / instruction without requiring changes to the BWP / slot format, and avoid inefficient limitations in DL / UL resource configuration.

[0073] The embodiments of this disclosure will be described in detail below with reference to the drawings. Each wireless communication method according to the embodiments may be applied individually or in combination.

[0074] (Wireless communication method) The DL signals / channels in this disclosure may be transmitted using unicast or using multicast / broadcast to multiple UEs. The multicast / broadcast / unicast configuration may be performed using higher-layer signaling.

[0075] In this disclosure, "channel" and "signal" may be interpreted interchangeably. Also, in this disclosure, the transmission of a UL channel / signal may be simply referred to as "UL transmission." Also, in this disclosure, the reception of a DL channel / signal may be simply referred to as "DL reception."

[0076] UL signals / channels in this disclosure include, for example, uplink control channels (e.g., PUCCH), uplink shared channels (e.g., PUSCH), measurement reference signals (e.g., sounding reference signals (SRS)), random access channels (e.g., physical random access channels (PRACH)), sidelink control channels (e.g., physical sidelink control channels (PSCCH)), sidelink shared channels (e.g., physical sidelink shared channels (PSSCH)), sidelink feedback channels (e.g., physical sidelink feedback channels (PSFCH)), sidelink synchronization signals (e.g., sidelink primary synchronization signals (S-PSS) or sidelink secondary synchronization signals (S-SSS)), and sidelink broadcast channels (e.g., physical sidelink broadcast channels). It may be at least one of the Channels (PSBCH).

[0077] The DL signal / channel in this disclosure may be at least one of the following: downlink control channel (e.g., PDCCH), downlink shared channel (e.g., PDSCH), Channel State Information Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Positioning Reference Signal (PRS), Synchronization Signal Block (SSB), Broadcast Channel (PBCH), Sidelink Control Channel (e.g., PSCCH), Sidelink Shared Channel (e.g., PSSCH), Sidelink Feedback Channel (e.g., PSFCH), Sidelink Synchronization Signal (e.g., S-PSS or S-SSS), or Sidelink Broadcast Channel (e.g., PSBCH).

[0078] In this disclosure, A / B may mean at least one of A and B. In this disclosure, "A / B / C" may mean "at least one of A, B and C".

[0079] In this disclosure, the upper-layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.

[0080] MAC signaling may use, for example, MAC Control Elements (MAC CEs) or MAC Protocol Data Units (PDUs). Broadcast information may also include, for example, Master Information Blocks (MIBs), System Information Blocks (SIBs), Remaining Minimum System Information (RMSIs), or Other System Information (OSIs).

[0081] Physical layer signaling may include, for example, downlink control information (DCI).

[0082] In this disclosure, the terms port, antenna, antenna port, panel, beam, Uplink (UL) transmission entity, Transmission / Reception Point (TRP), spatial relationship information, spatial relationship, Transmission Configuration Indication (TCI) or Transmission Configuration Indicator (TCI-state), Quasi-Co-Location (QCL) assumption, Control Resource Set (CORESET), PDSCH, codeword, base station, predetermined antenna port (e.g., Demodulation Reference Signal (DMRS) port), predetermined antenna port group (e.g., DMRS port group), predetermined group (e.g., Code Division Multiplexing (CDM) group, predetermined reference signal group, CORESET group, panel group, beam group, spatial relationship group, PUCCH group), and CORESET pool may be interpreted interchangeably.

[0083] In this disclosure, the reception of DL signals / channels and the transmission of UL signals / channels may be transmitted and received using the same BWP / CC / bandwidth / operating band, or they may be transmitted and received using different BWP / CC / bandwidth / operating bands.

[0084] The following drawings in this disclosure illustrate the configuration in a single CC, but the number of resources in the frequency direction is not limited to this, and multiple CCs may be used. In other words, the XDD may be operated intra-carrier or inter-carrier.

[0085] In this disclosure, BWP, CC, cell, serving cell, band, carrier, operational band, physical resource block group (PRG), PRB, RB, RE, and resource may be interpreted as mutually exclusive.

[0086] In this disclosure, the phrases "A overlaps with B," "A is redundant with B," and "At least a part of A is redundant with at least a part of B" may be interpreted interchangeably.

[0087] Each embodiment of the present disclosure may apply under at least one of the following conditions: the UE reports to the NW a UE capability corresponding to at least one function / capability in each embodiment; or the UE is configured / activated / instructed by upper-layer signaling for a UE capability corresponding to at least one function / capability in each embodiment. Each embodiment of the present disclosure may also apply to the UE when a specific upper-layer parameter is configured / activated / instructed.

[0088] In this disclosure, the terms "time domain (period / part) in which DL resources and UL resources within a specific number of CCs of the TDD band are simultaneously available," "XDD portion," "XDD period," "XDD configuration," "first DL / UL portion," "first period," "period in which DL reception / UL transmission is restricted," "period in which DL and UL are mixed," "period in which UL transmission is possible during the DL period," and "period in which unavailable resources may be set / instructed" may be interpreted interchangeably.

[0089] DL / UL resources in the XDD portion may be interpreted as XDD DL / UL resources, XDD DL / UL, the first DL / UL resource, the first DL / UL portion, DL / UL resources for which unavailable resources may be set / instructed, and DL / UL portions for which unavailable resources may be set / instructed.

[0090] DL / UL resources in the TDD band where DL and UL do not overlap in time may be interpreted as non-XDD DL / UL resources, pure DL / UL resources, non-XDD DL / UL resources, second DL / UL resources, second DL / UL portion, DL / UL resources where no unavailable resources are set / instructed, second period of DL / UL portion where no unavailable resources are set / instructed, etc.

[0091] The XDD operation may describe the operation during the period in which the XDD DL / UL resources are configured, or it may describe the operation of the entire TDD in which XDD may be used.

[0092] Furthermore, in this disclosure, DL / UL BWP in the TDD band, DL / UL BWP as defined up to Rel. 15 / 16, and ordinary DL / UL BWP may be interpreted interchangeably.

[0093] In this disclosure, the XDD portion may mean at least one of the time resources in which a UL resource is configured with the same time resources as a DL resource, or the time resources in which a DL resource is configured with the same time resources as a UL resource. The XDD portion may also mean at least one of the time resources in which an FL resource (a resource available for DL ​​and UL) is configured with the same time resources as a DL resource, or the time resources in which an FL resource (a resource available for DL ​​and UL) is configured with the same time resources as a UL resource.

[0094] In this disclosure, information, configuration information, instruction information, information element, parameter, field, and code point may be interpreted interchangeably. In this disclosure, configuration information, RRC information element, RRC parameter, upper layer parameter, and upper layer signaling may be interpreted interchangeably.

[0095] In this disclosure, terms such as drop, suspension, cancellation, puncture, rate match, and postponement may be interpreted interchangeably.

[0096] In this disclosure, unavailable resources, patterns of unavailable resources, unavailable resources, patterns of unavailable resources, unused resources, patterns of unused resources, rate matching patterns, rate matching patterns, puncture patterns, puncturing patterns, muting resource patterns, invalid resources, invalid resource patterns, etc., may be interpreted interchangeably.

[0097] Each embodiment of this disclosure is applicable not only to cases where XDD is used, but also to cases where TDD / FDD is used, and the use of XDD is not required.

[0098] <First Embodiment> In the first embodiment, the configuration / instruction / activation of DL resources will be described.

[0099] Embodiment 1-1 In Embodiment 1-1, the UE may configure / instruct resources unavailable for DL ​​based on upper-layer signaling, physical layer signaling, and combinations thereof.

[0100] [Implementation 1-1-1] For example, the UE may configure resources to be unavailable for DL ​​based on specific RRC parameters.

[0101] For example, the specific RRC parameter may be included in the information regarding the serving cell configuration. The information regarding the serving cell configuration may be at least one of the following: information regarding the serving cell configuration specific to a UE (e.g., ServingCellConfig) and information regarding the serving cell configuration common to multiple UEs (e.g., ServingCellConfigCommon).

[0102] The specific RRC parameter in question may, for example, be information from a list containing one or more patterns of unavailable resources.

[0103] For example, information regarding the serving cell configuration may include at least one of the following: information for adding / modifying patterns of unavailable resources; information for releasing patterns of unavailable resources; and information for groups of patterns of unavailable resources.

[0104] The above list may include information on up to a specific number of unavailable resource patterns. This specific number may be predefined in the specifications.

[0105] In this disclosure, information regarding a list of unavailable resource patterns may mean at least one of the following: information regarding a list for adding / modifying unavailable resource patterns; information regarding a list for releasing unavailable resource patterns; or information regarding a group of unavailable resource patterns. Similarly, information regarding a list of PDSCH rate match patterns may mean at least one of the following: information regarding a list for adding / modifying PDSCH rate match patterns; information regarding a list for releasing PDSCH rate match patterns; or information regarding a group of PDSCH rate match patterns.

[0106] Information regarding groups of unavailable resource patterns may be configured for multiple (e.g., two) groups. For example, information regarding the serving cell configuration may include information about a first group of unavailable resource patterns and information about a second group of unavailable resource patterns.

[0107] In this disclosure, the case where the number of groups is two is described, but the number of groups may be three or more. The number of groups may be predetermined in the specification, set in the UE by upper-layer signaling, or determined based on the UE's capabilities.

[0108] Information regarding groups of patterns of unavailable resources may correspond to a specific frequency resource level. For example, information regarding groups of patterns of unavailable resources may correspond to either the cell level or the BWP level.

[0109] The UE may determine which resources are unavailable for DL ​​based on the union of one or more patterns (resources) included in the list.

[0110] Figure 7 shows an example of information elements related to the list of unavailable resource patterns according to Embodiment 1-1-1. In the example shown in Figure 7, ServingCellConfig includes information on a list for adding / modifying unavailable resource patterns (rateMatchPatternXDDToAddModList), information on a list for releasing unavailable resource patterns (rateMatchPatternXDDToReleaseList), and information on the serving cell configuration, including information on a first group of unavailable resource patterns (rateMatchPatternXDDGroup1) and information on a second group of unavailable resource patterns (rateMatchPatternXDDGroup2).

[0111] Furthermore, RRC information elements used for rate matching in PDSCH (e.g., RateMatchPattern) may be used for setting patterns of unavailable resources (see Figure 2).

[0112] The bit sizes and names of the parameters in each embodiment of this disclosure are merely examples and are not limited to those described.

[0113] Furthermore, the configuration information for patterns of unavailable resources may also be RRC information elements / parameters newly defined in Rel.17 and later.

[0114] [Embodiment 1-1-2] For example, the UE may indicate resources unavailable for DL ​​in the XDD portion based on specific RRC parameters and specific instruction information / indicators.

[0115] The specific RRC parameter may be at least one of the parameters described in Embodiment 1-1-1 above.

[0116] The specific instruction information / indicator may be communicated to the UE using at least one of MAC CE and DCI.

[0117] For example, specific instruction information / indicators may be specific fields included in a particular DCI format. This particular DCI format may be the DCI format used to schedule the PDSCH (e.g., DCI format 1_1 / 1_2) or any other DCI format.

[0118] For example, the number of bits in a particular instruction / indicator may be determined based on the number of groups of patterns of unavailable resources. For example, the number of bits in a particular instruction / indicator may be the same as the number of groups of patterns of unavailable resources. In this case, the particular instruction / indicator may be configured as a bitmap such that the Nth bit of the particular instruction / indicator corresponds to the Nth group of patterns of unavailable resources.

[0119] According to Embodiment 1-1, resources unavailable for DL ​​can be appropriately configured / instructed to the UE using at least one of upper-layer signaling and physical layer signaling.

[0120] Embodiment 1-2 Based on the configuration / instructions for resources unavailable to DL, resources available to UL may be configured / instructed.

[0121] Resources unavailable for DL ​​and resources available for UL may be the same time and frequency resources. Alternatively, resources available for UL may be configured / instructed to be included in the same time and frequency resources as resources unavailable for DL.

[0122] The configuration / instruction of resources unavailable to DL may be performed in addition to / in place of the configuration / instruction of existing PDSCH rate match patterns. The configuration / instruction of resources unavailable to DL may be performed quasi-statically or dynamically.

[0123] The configuration of resources unavailable for quasi-static DL may also mean the configuration of resources unavailable for DL ​​based on upper-layer signaling. The configuration of resources unavailable for dynamic DL may also mean the configuration of resources unavailable for DL ​​based on upper-layer signaling and physical layer signaling (DCI).

[0124] [Embodiment 1-2-1] Embodiment 1-2-1 describes the configuration of resources that are unavailable for DL ​​based on upper-layer signaling.

[0125] The UE may configure resources that are unavailable for DL, in common with the setting of the PDSCH rate match pattern (Embodiment 1-2-1-1).

[0126] For example, the number of bits for the parameter related to the rate match pattern of the PDSCH may be the same as the number of bits for the parameter related to the pattern of unavailable resources.

[0127] For example, the number of rate match patterns included in the list of PDSCH rate match patterns may be the same as the number of patterns included in the list of unavailable resource patterns.

[0128] For example, the granularity of resources indicated by the PDSCH rate match pattern may be the same as the granularity of resources indicated by the unavailable resource pattern. The granularity of resources may be set for each specific frequency resource and for each specific time resource. For example, the granularity of resources may be set for each RB and for each symbol.

[0129] For example, the resource range indicated by the PDSCH rate match pattern and the resource range indicated by the unavailable resource pattern may be the same. The resource range may be at least one of the maximum number of specific frequency resources that can be specified and the maximum number of specific time resources that can be specified. For example, the maximum number of specific frequency resources that can be specified may be 275 RB. Also, the maximum number of specific time resources that can be specified may be 2 slots (28 symbols).

[0130] Furthermore, the UE may configure resources that are unavailable for DL ​​separately from the setting of the PDSCH rate match pattern (Embodiment 1-2-1-2).

[0131] For example, the number of bits for the parameter related to the PDSCH rate match pattern and the number of bits for the parameter related to the pattern of unavailable resources may be set / defined separately.

[0132] For example, the number of rate match patterns included in the PDSCH rate match pattern list and the number of patterns included in the list of unavailable resource patterns may be set separately.

[0133] For example, the granularity of resources indicated by the PDSCH rate match pattern and the granularity of resources indicated by the unavailable resource pattern may be defined separately. The granularity of resources may be set for each specific frequency resource and for each specific time resource. For example, the granularity of resources may be set for each RB and for each symbol.

[0134] For example, the range of resources indicated by the PDSCH rate match pattern and the range of resources indicated by the unavailable resource pattern may be defined separately. The resource range may be at least one of the maximum number of specific frequency resources that can be specified and the maximum number of specific time resources that can be specified. For example, for resources indicated by the unavailable resource pattern, the maximum number of specific frequency resources that can be specified may be greater than (or less than) 275 RB. Also, the maximum number of specific time resources that can be specified may be greater than (or less than) 2 slots (28 symbols).

[0135] Additionally, the UE may be provided with at least one of the following separately from the PDSCH rate match pattern list: information on a list for adding / modifying patterns of unavailable resources, information on a list for releasing patterns of unavailable resources, and information on groups of patterns of unavailable resources. There may be one or more lists of patterns of unavailable resources.

[0136] Figure 8A shows an example of the application of an unavailable resource pattern according to Embodiment 1-2-1. In the example shown in Figure 8A, a pattern of resources unavailable for DL, which is set by upper-layer signaling, is applied.

[0137] [Embodiment 1-2-2] Embodiment 1-2-2 describes the configuration / instruction of resources that are unavailable for DL ​​based on upper layer signaling and physical layer signaling (DCI).

[0138] In Embodiment 1-2-2, the setting of resources unavailable for DL ​​by upper-layer signaling to the UE may be at least one of the methods described in Embodiment 1-2-1 above.

[0139] The UE may use certain fields included in the DCI that schedules the DL transmission (e.g., DCI format 1_0 / 1_1 / 1_2) to determine whether to instruct / activate resources unavailable for DL ​​(Embodiment 1-2-2-1).

[0140] The specific field in question may be a different field from the field related to PDSCH's rate match.

[0141] The specific field may be a field that enables (or disables) or activates patterns of resources unavailable for the configured DL. In this case, the specific field may have a specific number of bits. This specific number may be the same as the number of groups of unavailable resource patterns configured in the higher-layer signaling.

[0142] Furthermore, the UE may use specific fields included in a DCI format other than the DCI used to schedule DL transmissions to determine the indication / activation of resources unavailable for DL ​​(Embodiment 1-2-2-2). This DCI format may be, for example, a group-common DCI format. A group-common DCI format is suitably applicable in cases where a pattern of unavailable resources is applied to the reception of channels / signals other than PDSCH.

[0143] Furthermore, the UE may determine whether to instruct / activate resources unavailable to DL based on at least one of the following: Radio Network Temporary Identifier (RNTI) applied to the DL channel / signal, sequence, reference signal sequence, or format (Embodiment 1-2-2-3).

[0144] Furthermore, the UE may determine whether to activate / deactivate resources unavailable for DL ​​based on specific fields contained in a particular MAC CE (Embodiment 1-2-2-4).

[0145] Figure 8B shows an example of the application of an unavailable resource pattern according to Embodiment 1-2-2. In the example shown in Figure 8B, a pattern of resources unavailable to DL, set / instructed by upper-layer signaling and DCI, is applied.

[0146] According to Embodiment 1-2, resources unavailable for DL ​​can be appropriately configured / instructed / activated to the UE using at least one of upper-layer signaling and physical layer signaling.

[0147] Embodiments 1-3 Embodiments 1-3 describe DL channels / signals to which settings / instructions for resources unavailable for DL ​​are applied.

[0148] The DL channels / signals to which the configuration / instructions for resources unavailable to DL apply may be at least one of the channels / signals listed below: PDSCH. PDCCH. CSI-RS. • Tracking CSI-RS (Tracking Reference Signal (TRS)). ·Positioning Reference Signal (PRS). SSB. • Physical Sidelink Control Channel (PSCCH). • Physical Sidelink Shared Channel (PSSCH). • Physical Sidelink Feedback Channel (PSFCH). • Sidelink synchronization signal (for example, Sidelink Primary Synchronization Signal (S-PSS) or Sidelink Secondary Synchronization Signal (S-SSS))). • Physical Sidelink Broadcast Channel (PSBCH).

[0149] For example, setting / instructing resources unavailable for DL ​​may be applied only to PDSCH (Embodiment 1-3-1).

[0150] In Embodiment 1-3-1, the UE does not need to anticipate that the reception of DL channels / signals other than the PDSCH will be scheduled on resources unavailable for the configured / instructed DL (resources available for UL).

[0151] In Embodiment 1-3-1, if PDSCH scheduling is performed on an unavailable resource, the UE may rate match the PDSCH around that resource.

[0152] Furthermore, in Embodiment 1-3-1, the UE may also follow the settings / instructions for receiving DL channels / signals other than the PDSCH.

[0153] Furthermore, for example, the setting / instruction of resources unavailable for DL ​​may be applied to PDSCH and DL channels / signals other than PDSCH (hereinafter referred to as other DL channels / signals) (Embodiment 1-3-2).

[0154] In Embodiment 1-3-2, if a UE is instructed to configure / activate a resource that is unavailable for DL, and that resource overlaps with other DL channels / signals, the UE does not need to receive those other DL channels / signals (Embodiment 1-3-2-1).

[0155] Furthermore, in Embodiment 1-3-2, if the UE is instructed to configure / activate a resource that is unavailable for DL, and that resource overlaps with other DL channels / signals, the UE may rate match / puncture the other DL channels / signals around that resource (Embodiment 1-3-2-2).

[0156] In Embodiments 1-3, separate settings / instructions / activations of unavailable resources may be performed separately for each different channel / signal. For example, different rate matching patterns / puncturing patterns may be set / instructed for different channels / signals.

[0157] According to Embodiments 1-3, resources unavailable for DL ​​can be appropriately applied not only to PDSCH but also to channels / signals other than PDSCH.

[0158] Embodiments 1-4 UE capability information may be provided indicating support for the functions / features described in at least one of the embodiments 1-1 to 1-3 described above. The UE may report such UE capability information to the network (e.g., base stations).

[0159] The capability information may be reported per UE, per frequency range, per band, per feature set (FS) (per band in a combination of multiple bands), or per cell in an FS (per CC for each band in a combination of multiple bands).

[0160] The capability information may be specified for TDD only, for FDD and TDD, or separately for FDD and TDD.

[0161] Based on the above UE capabilities / higher layer parameters, the UE can achieve the above functions while maintaining compatibility with existing specifications.

[0162] According to the first embodiment described above, resources can be appropriately configured / instructed / activated in DL.

[0163] <Second Embodiment> In the second embodiment, the configuration / instruction of UL resources will be described.

[0164] Embodiment 2-1 UL channel / signal configuration may be performed separately for UL during periods when resources unavailable for UL may be configured / instructed (first period) and for UL during periods when resources unavailable for UL may not be configured / instructed (second period).

[0165] In this disclosure, "resources unavailable for UL" may mean resources that are unavailable for certain types of UL transmissions.

[0166] For example, in addition to the existing UL channel / signal settings, UL channel / signal settings may be made for the UL in a second period.

[0167] Additionally, for example, the maximum number of configurable resources in an existing UL channel / signal configuration may be increased.

[0168] For example, for a single configured grant pusher, the UE may be given multiple (e.g., two) different frequency domain resource allocation (FDRA) settings, which can be instructed / modified quasi-statically or dynamically using upper-layer signaling / DCI. For example, one of the two settings may apply to the configured grant pusher in the first period of the UL, and the other to the configured grant pusher in the second period of the UL. For example, the UE may instruct / modify based on at least one of the following: the configuration / pattern of the XDD, or an instruction to change (switch) or not.

[0169] In this disclosure, configured grant PUSCH may mean a PUSCH that is quasi-statically scheduled using only upper-layer signaling, or using both upper-layer signaling and physical layer signaling. For example, a PUSCH that is quasi-statically scheduled using upper-layer signaling may be a configured grant type 1 PUSCH. Also, for example, a PUSCH that is quasi-statically scheduled using both upper-layer signaling and physical layer signaling may be a configured grant type 2 PUSCH.

[0170] For example, the PUCCH resource / resource set for the first period and the PUCCH resource / resource set for the second period may be set separately.

[0171] Furthermore, for example, multiple PUCCH resources / resource sets may be configured, and the selection / determination of PUCCH resources / resource sets may be made based on quasi-static / dynamic configuration / instructions by upper-layer signaling / DCI. The quasi-static / dynamic configuration / instructions by upper-layer signaling / DCI may be based on at least one of the following: XDD configuration / patterns, PUCCH resource patterns, or PUCCH resource indicators.

[0172] For example, the SRS resources / resource sets for the first period and the SRS resources / resource sets for the second period may be configured separately.

[0173] Furthermore, for example, multiple SRS resources / resource sets may be configured, and the selection / determination of SRS resources / resource sets may be based on quasi-static / dynamic configuration / instructions by higher-layer signaling (e.g., RRC signaling / MAC CE) / DCI. The quasi-static / dynamic configuration / instructions by higher-layer signaling / DCI may be based on at least one of the following: XDD configuration / patterns, SRS resource patterns, or SRS resource indicators.

[0174] For example, the settings for PRACH in the first period and the settings for PRACH in the second period may be performed separately.

[0175] According to Embodiment 2-1, even when there are periods in which resources unavailable to UL may be set / instructed, and periods in which resources unavailable to UL may not be set / instructed, the UL channel / signal can be properly configured.

[0176] Embodiment 2-2 In Embodiment 2-2, the UE may configure / instruct / activate resources unavailable to the UL based on upper-layer signaling, physical layer signaling, and combinations thereof.

[0177] A method for configuring / instructing / activating resources unavailable to the UL for the UE may be applied by replacing "DL" with "UL" and "UL" with "DL," respectively, with the method described in at least one of the embodiments 1-1 and 1-2 above.

[0178] Based on the configuration / instruction of resources unavailable to UL, resources available to DL may be configured / instructed.

[0179] Resources unavailable for UL and resources available for DL ​​may be the same time and frequency resources. Alternatively, resources available for DL ​​may be configured / instructed to be included in the same time and frequency resources as resources unavailable for UL.

[0180] The configuration / instruction of resources unavailable to UL may be performed in addition to / in place of the configuration / instruction of existing PDSCH rate match patterns. The configuration / instruction of resources unavailable to UL may be performed quasi-statically or dynamically.

[0181] For example, the configuration / instruction of resources not available to the UL may be performed using at least one of the upper-layer signaling (e.g., RRC signaling / MAC CE) and physical layer signaling (e.g., DCI). The DCI may be at least one of the DCI that schedules UL / DL channels / signals and a group common DCI common to multiple UEs.

[0182] Figure 9A shows an example of the application of an unavailable resource pattern according to Embodiment 2-2. In the example shown in Figure 9A, a pattern of unavailable resources for UL, which is set by upper-layer signaling, is applied.

[0183] Figure 9B shows another example of the application of the unavailable resource pattern according to Embodiment 2-2. In the example shown in Figure 9B, the unavailable resource pattern for UL is applied, which is set / instructed by upper-layer signaling and DCI.

[0184] Patterns of resources unavailable for UL may be set / instructed in addition to the settings / instructions for patterns of resources unavailable for DL. In other words, patterns of resources unavailable for UL may be set / instructed separately from the settings / instructions for patterns of resources unavailable for DL.

[0185] Furthermore, patterns of resources unavailable to UL may be set / instructed together with the settings / instructions for patterns of resources unavailable to DL. For example, higher-layer parameters that set patterns of resources unavailable to UL and patterns of resources unavailable to DL may be included in a common information element. Also, the DCI that instructs patterns of resources unavailable to UL and patterns of resources unavailable to DL may be a DCI common to multiple UEs.

[0186] Patterns of resources unavailable to UL may be applied to specific UL channels / signals. Such specific channels may be at least one of PUSCH, Configured Grant PUSCH, PUCCH, SRS, or PRACH scheduled using DCI.

[0187] Furthermore, the specific channel in question may be a UL channel / signal other than a PUSCH scheduled using DCI. The UE may assume that patterns of resources unavailable to the UL will not be applied to PUSCHs scheduled using DCI.

[0188] In Embodiment 2-2, different unavailable resources may be configured / instructed / activated separately for each channel / signal. For example, different rate matching patterns / puncturing patterns may be configured / instructed for different channels / signals.

[0189] According to Embodiment 2-2, resources unavailable to UL can be appropriately configured / instructed for multiple UL channels / signals.

[0190] Embodiment 2-3 UE capability information may be provided indicating support for the functions / features described in at least one of the embodiments 2-1 and 2-2 described above. The UE may report such UE capability information to the network (e.g., base stations).

[0191] The capability information may be reported per UE, per frequency range, per band, per feature set (FS) (per band in a combination of multiple bands), or per cell in an FS (per CC for each band in a combination of multiple bands).

[0192] The capability information may be specified for TDD only, for FDD and TDD, or separately for FDD and TDD.

[0193] The capability information related to the first embodiment described above (for example, capability information regarding resources unavailable for DL) and the capability information related to the second embodiment described above (for example, capability information regarding resources unavailable for UL) may be set in common or separately.

[0194] Based on the above UE capabilities / higher layer parameters, the UE can achieve the above functions while maintaining compatibility with existing specifications.

[0195] Embodiment 2-4 When UL channel / signal transmission is scheduled / triggered using DCI, the pattern of resources available to the UL may be configured using only upper-layer signaling.

[0196] Furthermore, when UL channel / signal transmission is scheduled / triggered using DCI, the pattern of resources available for the UL may be indicated using the DCI being scheduled / triggered.

[0197] When UL channel / signal transmission is configured using upper-layer signaling, the pattern of resources available for the UL may be configured using only upper-layer signaling. The UL channel / signal configured using upper-layer signaling may be at least one of the following: periodic UL transmission (e.g., SRS), semi-persistent scheduled UL transmission, configured grant UL transmission (e.g., PUSCH), or repetitive transmission (e.g., PUSCH / PUCCH).

[0198] In this embodiment 2-4, "UL" may be appropriately replaced with "DL". The first embodiment described above may also be applied by replacing "UL" with "DL" in this embodiment 2-4.

[0199] According to Embodiment 2-4, for example, even if the UL is dynamically instructed on available resources and the UE fails to detect such instruction, it is possible to avoid sending and receiving data on unavailable resources and thus avoid the occurrence of CLI.

[0200] According to the second embodiment described above, it is possible to appropriately configure / instruct / activate resources that are unavailable to UL.

[0201] <Variation> In the first embodiment described above, DL reception may be configured / instructed to span a DL during a period in which unavailable resources may be configured / instructed (first period) and a DL during a period in which unavailable resources are not configured / instructed (second period).

[0202] For example, the DL reception may be a repetition.

[0203] When the DL reception is configured / instructed, the UE may apply the pattern of unavailable resources only to resources in the first period.

[0204] Furthermore, when the DL reception is set / instructed, the UE may apply the pattern of unavailable resources for the DL to the resources in the first period and the resources in the second period.

[0205] Furthermore, when the DL reception is configured / instructed, the UE does not need to assume that the pattern of unavailable resources for the DL applies only to resources in either the first period or the second period.

[0206] In the first embodiment described above, the UE may assume that no settings / instructions are made for DL ​​reception spanning the DL of the first period and the DL of the second period.

[0207] In the second embodiment described above, a UL transmission may be configured / instructed that spans a period during which unavailable resources may be configured / instructed (first period) and a period during which unavailable resources are not configured / instructed (second period).

[0208] For example, the UL transmission may be a repetition.

[0209] When such UL transmission is configured / instructed, the UE may apply the pattern of unavailable resources only to resources in the first period.

[0210] Furthermore, when the UL transmission is configured / instructed, the UE may apply the pattern of unavailable resources for the UL to the resources in the first period and the resources in the second period.

[0211] Furthermore, when such UL transmission is configured / instructed, the UE does not have to assume that the pattern of unavailable resources for the UL applies only to resources in either the first period or the second period.

[0212] In the first embodiment described above, the UE may assume that no UL transmission settings / instructions are made that span between the UL for the first period and the UL for the second period.

[0213] (Wireless communication system) The configuration of a wireless communication system according to one embodiment of this disclosure will be described below. In this wireless communication system, communication is performed using any or a combination thereof of the wireless communication methods according to the above embodiments of this disclosure.

[0214] Figure 10 shows an example of a schematic configuration of a wireless communication system according to one embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc., as specified by the Third Generation Partnership Project (3GPP).

[0215] Furthermore, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and so on.

[0216] In EN-DC, the LTE (E-UTRA) base station (eNB) is the Master Node (MN), and the NR base station (gNB) is the Secondary Node (SN). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

[0217] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity where both MN and SN are NR base stations (gNB) (NR-NR Dual Connectivity (NN-DC))).

[0218] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with relatively wide coverage, and base stations 12 (12a-12c) located within the macrocell C1 that form a small cell C2 that is narrower than the macrocell C1. User terminals 20 may be located within at least one cell. The arrangement and number of each cell and user terminal 20 are not limited to the configuration shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

[0219] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of Carrier Aggregation (CA) using multiple Component Carriers (CC) and Dual Connectivity (DC).

[0220] Each CC may be included in at least one of the first frequency band (Frequency Range 1 (FR1)) and the second frequency band (Frequency Range 2 (FR2)). A macrocell C1 may be included in FR1, and a small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may fall in a frequency band higher than FR2.

[0221] Furthermore, the user terminal 20 may communicate using at least one of the following methods at each CC: Time Division Duplex (TDD) and Frequency Division Duplex (FDD).

[0222] Multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wireless (e.g., NR communication). For example, if NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is the upstream station, may be called an Integrated Access Backhaul (IAB) donor, and base station 12, which is the relay station, may be called an IAB node.

[0223] Base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0224] The user terminal 20 may be a terminal that supports at least one of the following communication methods: LTE, LTE-A, 5G, etc.

[0225] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access scheme may be used. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc., may be used in at least one of the downlink (DL) and uplink (UL).

[0226] The wireless access method may also be called a waveform. In wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0227] In the wireless communication system 1, a Physical Downlink Shared Channel (PDSCH), a Broadcast Channel (PBCH), or a Physical Downlink Control Channel (PDCCH) may be used as the downlink channel, shared by each user terminal 20.

[0228] Furthermore, in the wireless communication system 1, the uplink channel may include a Physical Uplink Shared Channel (PUSCH), a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), or the like, all of which are shared by each user terminal 20.

[0229] User data, higher-layer control information, and System Information Blocks (SIBs) are transmitted via PDSCH. User data and higher-layer control information may also be transmitted via PUSCH. Furthermore, Master Information Blocks (MIBs) may be transmitted via PBCH.

[0230] Lower-layer control information may be transmitted by PDCCH. The lower-layer control information may include, for example, Downlink Control Information (DCI) which includes scheduling information for at least one of PDSCH and PUSCH.

[0231] Furthermore, the DCI that schedules PDSCH may be called a DL assignment or DL ​​DCI, and the DCI that schedules PUSCH may be called a UL grant or UL DCI. Furthermore, PDSCH may be interpreted as DL data, and PUSCH may be interpreted as UL data.

[0232] PDCCH detection may utilize a Control Resource Set (CORESET) and a search space. A CORESET corresponds to the resources used to search for DCIs. A search space corresponds to the search area and search method for PDCCH candidates. A single CORESET may be associated with one or more search spaces. The UE may monitor CORESETs associated with a particular search space based on the search space configuration.

[0233] A single search space may correspond to one or more PDCCH candidates corresponding to aggregation levels. One or more search spaces may be referred to as a search space set. In this disclosure, "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," and "CORESET configuration" may be interpreted interchangeably.

[0234] PUCCH may transmit uplink control information (UCI) which includes at least one of the following: channel state information (CSI), delivery acknowledgment (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). PRACH may transmit a random access preamble for establishing a connection with the cell.

[0235] In this disclosure, downlinks, uplinks, etc., may be expressed without the prefix "link." Also, the prefix "physical" may be omitted when describing various channels.

[0236] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc., may be transmitted. In the wireless communication system 1, as DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc., may be transmitted.

[0237] The synchronization signal may be, for example, at least one of a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, SS Block (SSB), etc. SS, SSB, etc., may also be called reference signals.

[0238] Furthermore, in the wireless communication system 1, the Uplink Reference Signal (UL-RS) may transmit the Sounding Reference Signal (SRS), Demodulation Reference Signal (DMRS), etc. The DMRS may also be called the User-Specific Reference Signal (UE-specific Reference Signal).

[0239] (base station) Figure 11 shows an example of the configuration of a base station according to one embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, transceiver unit 120, transceiver antenna 130, and transmission line interface 140 may be provided.

[0240] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0241] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, control circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0242] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may also control transmission and reception, measurement, etc., using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140. The control unit 110 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transceiver unit 120. The control unit 110 may also perform call processing of communication channels (setting, releasing, etc.), status management of the base station 10, management of radio resources, etc.

[0243] The transmitting / receiving unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transmitting / receiving unit 120 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0244] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 1211 and an RF unit 122. The receiving unit may consist of a receiving processing unit 1212, an RF unit 122 and a measuring unit 123.

[0245] The transmitting and receiving antenna 130 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0246] The transmitting / receiving unit 120 may transmit the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 120 may also receive the uplink channel, uplink reference signal, etc.

[0247] The transmitting / receiving unit 120 may form at least one of the transmitting beam and the receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0248] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform processing on data and control information acquired from the control unit 110, for example, at the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer (e.g., RLC retransmission control), the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc., to generate a bit sequence to be transmitted.

[0249] The transmitting / receiving unit 120 (transmission processing unit 1211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0250] The transmitting / receiving unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 130.

[0251] On the other hand, the transmitting / receiving unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 130.

[0252] The transmitting / receiving unit 120 (receiving processing unit 1212) may apply reception processing to the acquired baseband signal, such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, to acquire user data, etc.

[0253] The transmitting / receiving unit 120 (measurement unit 123) may perform measurements related to the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc., based on the received signal. The measurement unit 123 may also measure received power (e.g., Reference Signal Received Power (RSRP)), reception quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0254] The transmission path interface 140 may send and receive signals (backhaul signaling) with devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0255] In this disclosure, the transmitting and receiving units of the base station 10 may consist of at least one of a transmitting / receiving unit 120, a transmitting / receiving antenna 130, and a transmission path interface 140.

[0256] The transmitting / receiving unit 120 may transmit at least one of the following: setting information for a pattern of resources unavailable for DL ​​in a given time resource, and instruction information regarding the pattern of said resources. The control unit 110 may use at least one of the setting information and the instruction information to instruct DL reception to be performed on resources other than those unavailable for DL, and to instruct not to perform DL reception on resources unavailable for DL ​​(first embodiment).

[0257] The transmitting / receiving unit 120 may transmit at least one of the following: setting information for a pattern of resources unavailable for a specific type of UL transmission in a given time resource, and instruction information relating to the resource pattern. The control unit 110 may use at least one of the setting information and the instruction information to instruct that the specific type of UL transmission be performed on resources other than those unavailable for UL, and not to perform the specific type of UL transmission on resources unavailable for UL (second embodiment).

[0258] (User terminal) Figure 12 shows an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that one or more of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230 may be provided.

[0259] In this example, the functional blocks of the characteristic parts of this embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each part described below may be omitted.

[0260] The control unit 210 controls the entire user terminal 20. The control unit 210 can be composed of a controller, control circuit, etc., as described based on common understanding in the technical field related to this disclosure.

[0261] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may also control transmission and reception, measurement, etc., using the transmitting / receiving unit 220 and the transmitting / receiving antenna 230. The control unit 210 may generate data to be transmitted as signals, control information, sequences, etc., and transfer them to the transmitting / receiving unit 220.

[0262] The transmitting / receiving unit 220 may 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 can be composed of a transmitter / receiver, RF circuit, baseband circuit, filter, phase shifter, measurement circuit, transmitting / receiving circuit, etc., as described based on common understanding in the art relating to this disclosure.

[0263] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or it may be composed of a transmitting unit and a receiving unit. The transmitting unit may consist of a transmitting processing unit 2211 and an RF unit 222. The receiving unit may consist of a receiving processing unit 2212, an RF unit 222 and a measuring unit 223.

[0264] The transmitting and receiving antenna 230 can be composed of an antenna described based on common understanding in the art relating to this disclosure, such as an array antenna.

[0265] The transmitting / receiving unit 220 may receive the downlink channel, synchronization signal, downlink reference signal, etc. The transmitting / receiving unit 220 may also transmit the uplink channel, uplink reference signal, etc.

[0266] The transmitting / receiving unit 220 may use digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like to form at least one of the transmitting beam and the receiving beam.

[0267] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc., on data and control information acquired from the control unit 210, etc., to generate a bit sequence to be transmitted.

[0268] The transmitting / receiving unit 220 (transmission processing unit 2211) may perform transmission processing on the bit sequence to be transmitted, such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion, and output a baseband signal.

[0269] Whether or not to apply DFT processing may be based on the transform precoding settings. The transmitting / receiving unit 220 (transmission processing unit 2211) may perform DFT processing as part of the transmission process to transmit a channel (for example, PUSCH) using a DFT-s-OFDM waveform if transform precoding is enabled for that channel, or it may not perform DFT processing as part of the transmission process if transform precoding is not enabled for that channel.

[0270] The transmitting / receiving unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc., of the baseband signal to the radio frequency band and transmit the signal in the radio frequency band via the transmitting / receiving antenna 230.

[0271] On the other hand, the transmitting / receiving unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc., on the radio frequency band signal received by the transmitting / receiving antenna 230.

[0272] The transmitting / receiving unit 220 (receiving processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal to acquire user data, etc.

[0273] The transmission / reception unit 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure 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 be output to the control unit 210.

[0274] Note that the transmission unit and reception unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.

[0275] The transmission / reception unit 220 may receive at least one of the setting information of the pattern of resources unavailable for DL in a certain time resource and the instruction information regarding the pattern of the resources. The control unit 210 may control to perform DL reception on resources other than the resources unavailable for DL based on at least one of the setting information and the instruction information, and may control not to perform the DL reception on the resources unavailable for DL (the first embodiment).

[0276] The certain time resource may be a resource in which DL and the uplink are set to overlap in time (e.g., the resource of the XDD part) (the first embodiment).

[0277] The number of bits of the parameter included in the setting information may be equal to the number of bits of the parameter included in the setting information regarding the rate matching pattern of the DL shared channel (the first embodiment).

[0278] The setting information may be set separately for each DL channel or DL signal (the first embodiment).

[0279] The transmitting / receiving unit 220 may receive at least one of the following: setting information for a pattern of resources unavailable for a specific type of UL transmission in a given time resource, and instruction information relating to the resource pattern. The control unit 210 may, based on at least one of the setting information and the instruction information, control the system to perform the specific type of UL transmission on resources other than those unavailable for UL, and control the system not to perform the specific type of UL transmission on resources unavailable for UL (second embodiment).

[0280] The aforementioned specific type of UL transmission may be at least one of a UL shared channel, a UL control channel, a sounding reference signal, and a random access channel, which are configured using upper-layer signaling (second embodiment).

[0281] The control unit may also control the transmission of UL shared channels scheduled using downlink control information on resources unavailable to UL (second embodiment).

[0282] The aforementioned configuration information may be set separately for each UL channel or UL signal (second embodiment).

[0283] (Hardware configuration) The block diagrams used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0284] Here, functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission may be called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0285] For example, a base station, user terminal, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 13 is a diagram showing an example of the hardware configuration of a base station and user terminal according to one embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0286] In this disclosure, terms such as apparatus, circuit, device, section, and unit are interchangeable. The hardware configuration of the base station 10 and the user terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0287] For example, although only one processor 1001 is shown in the diagram, there may be multiple processors. Furthermore, processing may be performed by one processor, or by two or more processors simultaneously, sequentially, or by other means. Note that processor 1001 may be implemented using one or more chips.

[0288] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication via the communication device 1004, or to control at least one of the reading and writing of data in the memory 1002 and storage 1003.

[0289] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, at least a part of the control unit 110 (210) and the transmitting / receiving unit 120 (220) described above may be implemented by the processor 1001.

[0290] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly.

[0291] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. Memory 1002 may also be called a register, cache, or main memory. Memory 1002 can store executable programs (program code), software modules, etc., for carrying out a wireless communication method according to one embodiment of this disclosure.

[0292] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (Compact Disc ROM (CD-ROM)), a digital multipurpose disk, a Blu-ray disk), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, stick, key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be called an auxiliary storage device.

[0293] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting / receiving unit 120 (220), transmitting / receiving antenna 130 (230), etc., may be implemented by the communication device 1004. The transmitting / receiving unit 120 (220) may be implemented with physically or logically separated implementations of a transmitting unit 120a (220a) and a receiving unit 120b (220b).

[0294] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, light-emitting diode (LED) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0295] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0296] In addition, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0297] (Modified Example) In addition, terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be read interchangeably with each other. Also, a signal may be a message. A reference signal may also be abbreviated as RS and may be called a pilot, a pilot signal, etc. depending on the applicable standard. Further, a component carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, etc.

[0298] A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the radio frame may be called a subframe. Further, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that does not depend on numerology.

[0299] Here, the neuralelogy may be communication parameters applied to at least one of the transmission and reception of a signal or channel. The neuralelogy may be, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, or specific windowing processes performed by the transceiver in the time domain.

[0300] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). Alternatively, a slot may be a time unit based on neurology.

[0301] A slot may include multiple mini-slots. Each mini-slot may consist of one or more symbols in the time domain. Mini-slots may also be called sub-slots. Mini-slots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (PUSCH) mapping type B.

[0302] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Wireless frames, subframes, slots, minislots, and symbols may each be referred to by different names. Furthermore, the units of time such as frames, subframes, slots, minislots, and symbols in this disclosure may be interpreted as interchangeable.

[0303] For example, one subframe may be called TTI, multiple consecutive subframes may be called TTI, or one slot or one mini-slot may be called TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. Note that the unit representing TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0304] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0305] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0306] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0307] A TTI with a time length of 1 ms may also be called a normal TTI (TTI in 3GPP Rel.8-12), a long TTI, a normal subframe, a long subframe, or a slot. A TTI shorter than a normal TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, or a slot.

[0308] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0309] A Resource Block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0310] Furthermore, an RB may contain one or more symbols in the time domain and may have the length of one slot, one minislot, one subframe, or one TTI. Each TTI, subframe, etc., may consist of one or more resource blocks.

[0311] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

[0312] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0313] A Bandwidth Part (BWP) (also called a partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0314] A BWP may include UL BWPs (BWPs for UL) and DL BWPs (BWPs for DL). One or more BWPs may be configured within a single carrier for a UE.

[0315] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0316] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative examples. For instance, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots within a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0317] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information. For example, wireless resources may be indicated by a predetermined index.

[0318] The names used for parameters and other elements in this disclosure are not restrictive in any way. Furthermore, mathematical formulas and other elements that use these parameters may differ from those expressly disclosed in this disclosure. Various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0319] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0320] Furthermore, information, signals, etc., can be output from upper layers to lower layers and from lower layers to upper layers, or to at least one of the two. Information, signals, etc., may also be input and output via multiple network nodes.

[0321] Input and output information and signals may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information and signals may be overwritten, updated, or appended to. Output information and signals may be deleted. Input information and signals may be transmitted to other devices.

[0322] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification in this disclosure may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), Medium Access Control (MAC) signaling), other signals, or a combination thereof).

[0323] Physical layer signaling may also be called Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signals), L1 control information (L1 control signals), etc. RRC signaling may also be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc. MAC signaling may also be communicated using, for example, MAC Control Element (CE).

[0324] Furthermore, notification of the specified information (for example, notification that "X is the case") is not limited to explicit notification, but may also be made implicitly (for example, by not notifying the specified information or by notifying other information).

[0325] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented as true or false, or by a numerical comparison (for example, a comparison with a predetermined value).

[0326] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0327] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0328] The terms “system” and “network” as used in this disclosure may be used interchangeably. “Network” may also mean the equipment included in the network (e.g., base stations).

[0329] In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "quasi-co-location (QCL)," "transmission configuration indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

[0330] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", and "serving cell" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0331] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0332] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0333] A mobile station may also be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.

[0334] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0335] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0336] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the user terminal 20 described above.

[0337] In this disclosure, operations performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes with base stations, it is clear that various operations performed for communication with terminals may be performed by the base station, one or more network nodes other than the base station (for example, a Mobility Management Entity (MME), a Serving Gateway (S-GW), etc., but not limited to these), or a combination thereof.

[0338] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between during execution. Furthermore, the processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be rearranged in order, provided they are consistent. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to that specific order.

[0339] Each aspect / embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM®), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), and IEEE This may be applied to systems utilizing 802.20, Ultra-WideBand (UWB), Bluetooth®, or other appropriate wireless communication methods, as well as next-generation systems that extend these. It may also be applied in combination with multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0340] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0341] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, the references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

[0342] The term “determining” as used in this disclosure may encompass a wide variety of actions. For example, “determining” may be considered to include judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in tables, databases, or other data structures), ascertaining, etc.

[0343] Furthermore, "judgment (decision)" may be considered as "judging (deciding)" things like receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory).

[0344] Furthermore, "judgment (decision)" can be considered as "judging (deciding)" something like resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment (decision)" can be considered as "judging (deciding)" something about an action.

[0345] Furthermore, "judgment (decision)" can be replaced with "assuming," "expecting," or "considering."

[0346] As used in this disclosure, the terms “connected,” “coupled,” and any variations thereof mean any direct or indirect connection or coupling between two or more elements, and may include one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be replaced with “access.”

[0347] In this disclosure, when two elements are connected, they can be considered to be “connected” or “coupled” to each other using one or more wires, cables, printed electrical connections, etc., and, in some non-exclusive and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, or optical domain (both visible and invisible).

[0348] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0349] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0350] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0351] Although the invention described herein has been explained in detail above, it will be clear to those skilled in the art that the invention described herein is not limited to the embodiments described herein. The invention described herein can be implemented in modified and altered forms without departing from the spirit and scope of the invention as defined in the claims. Therefore, the descriptions herein are for illustrative purposes only and do not imply any limitation on the invention described herein.

Claims

1. The receiving unit receives configuration information for resources available for the uplink (UL) that are allocated within the same time resources as the resources available for the downlink (DL), and the resources available for the DL and the resources available for the UL are configured in a single serving cell. A terminal having a control unit that controls UL transmission using resources available for the UL based on the aforementioned configuration information.

2. The terminal according to claim 1, wherein the aforementioned configuration information is included in the serving cell configuration.

3. The system receives configuration information for resources available for the uplink (UL) that are located within the same time resources as the resources available for the downlink (DL), and the resources available for the DL and the resources available for the UL are configured in the same serving cell. A wireless communication method for a terminal, comprising the step of controlling UL transmission on resources available for UL based on the aforementioned configuration information.

4. The system transmits configuration information for resources available for the uplink (UL) that are located within the same time resources as the resources available for the downlink (DL), and the resources available for the DL and the resources available for the UL are configured in the same serving cell. A base station having a control unit that uses the aforementioned configuration information to instruct UL transmission on resources available for UL.

5. A system having a base station and a terminal, The base station has a transmission unit that transmits configuration information for resources available for the uplink (UL) that are arranged in the same time resources as the resources available for the downlink (DL), and the resources available for the DL and the resources available for the UL are configured in the same serving cell. The aforementioned terminal is A receiving unit that receives the aforementioned setting information, A system comprising: a control unit that controls UL transmission using resources available for the UL based on the aforementioned configuration information.

Images