Terminal and communication method

Abstract

This terminal comprises: a control unit that generates uplink control information for reporting whether an uplink transmission opportunity within a plurality of periods respectively associated with a plurality of setting grant configurations is to be used by the terminal; and a transmission unit that transmits the uplink control information during one period from among the plurality of periods.

Description

Terminal and communication method

[0001] The present disclosure relates to a terminal and a communication method.

[0002] Long Term Evolution (LTE) has been specified for Universal Mobile Telecommunication System (UMTS) networks to achieve higher data rates and lower latency. Furthermore, successor systems to LTE are also being considered to achieve even greater bandwidth and speed than LTE. Examples of successor systems to LTE include LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), and New Radio (NR).

[0003] In NR, Release 15 specifies the configuration of a configured grant physical uplink scheduled channel (CG PUSCH) (see, for example, Non-Patent Document 1). The CG PUSCH includes a Type 1 CG PUSCH and a Type 2 CG PUSCH.

[0004] Additionally, Release 17 examines Extended Reality (XR), including virtual reality (VR) and mixed reality (MX), and considers XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. It states that the target requirements for XR should take into account capacity, latency (delay), mobility, and energy conservation.

[0005] Furthermore, Release 18 agreed to support dynamic indication of unused (or unused) CG PUSCH occasions (transmission opportunities) by a terminal using Uplink Control Information (UCI) (see, for example, Non-Patent Document 2). Note that the term "UTO-UCI" is used to refer to UCI that provides information about unused CG PUSCH occasions. UTO stands for Unused Transmission Occasion.

[0006] TS38.331 V16.2.0 (2020-09)RP-223502(December 12-16, 2022)

[0007] Although it has been decided that UTO-UCI will be supported in Release 18, some details of UTO-UCI have not yet been specified and are a topic for future study.

[0008] One aspect of the present disclosure provides a terminal and a communication method that can appropriately report dynamic indications of unused uplink transmission opportunities to a base station.

[0009] A terminal according to one aspect of the present disclosure includes a control unit that generates uplink control information that notifies whether an uplink transmission opportunity within a plurality of periods corresponding to each of a plurality of configured grant configurations will be used by the terminal, and a transmission unit that transmits the uplink control information during one of the plurality of periods.

[0010] FIG. 1 is a diagram illustrating an example of dual connectivity (DC). FIG. 2 is a diagram illustrating an example of a CG PUSCH. FIG. 3 is a diagram illustrating an example of a bitmap indicated by a UCO-UCI. FIG. 4 is a diagram illustrating an example of a UTO-UCI indicating used / unused information for multiple CG configurations. FIG. 5 is a diagram illustrating an example of a UTO-UCI indicating used / unused information for multiple CG configurations. FIG. 6 is a diagram illustrating an example of ordered separate bitmaps indicating used / unused information for multiple CG configurations. FIG. 7 is a diagram illustrating an example of ordered separate bitmaps indicating used / unused information for multiple CG configurations. FIG. 8 is a diagram illustrating an example of a single bitmap indicating used / unused information for multiple CG configurations. FIG. 9 is a flowchart illustrating an operation example of a terminal according to the present embodiment. FIG. 10 is a block diagram illustrating an example of a configuration of a base station according to the present embodiment. FIG. 11 is a block diagram illustrating an example of a configuration of a terminal according to the present embodiment. FIG. 12 is a diagram illustrating an example of hardware configurations of a base station and a terminal according to an embodiment of the present disclosure. FIG. 13 is a diagram illustrating an example of a configuration of a vehicle according to an embodiment of the present disclosure.

[0011] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings.

[0012] In a wireless communication system, a terminal (hereinafter also referred to as UE (User Equipment)) and a base station can communicate via multiple cells. Dual connectivity, an example of communication via multiple cells, will be described below.

[0013] <Dual Connectivity> Figure 1 is a diagram showing an example of dual connectivity (DC). In the example of Figure 1, the base station 10-1 may be a master node (MN). The base station 10-2 may be a secondary node (SN). As shown in the example of Figure 1, in DC, carriers between different base stations are aggregated.

[0014] 1, the base station 10-1 communicates with the terminal 20 via a primary cell (Pcell) and a secondary cell (Scell). In the example of Fig. 1, the terminal 20 establishes an RRC (Radio Resource Control) connection with the base station 10-1.

[0015] In the case of DC, since there may be a delay in communication between the base station 10-1 and the base station 10-2, it is difficult to notify the base station 10-2 of uplink control information (e.g., Uplink Control Information (UCI)) received in the Pcell of the base station 10-1 via a backhaul link (e.g., a wired or wireless link connecting the base station 10-1 and the base station 10-2) and reflect it in the scheduling of the Scell ​​under the base station 10-2. Therefore, in DC, in addition to the Pcell of the base station 10-1, one carrier under the base station 10-2 may be set as a Primary Scell ​​(PScell), and PUCCH transmission may be supported by the PScell. In this case, the terminal 20 transmits UCI to the base station 10-2 via the PScell.

[0016] In the example of FIG. 1, the terminal 20 configures an Scell ​​in addition to a Pcell for the base station 10-1. The terminal 20 also configures an Scell ​​in addition to a PScell ​​for the base station 10-2. The terminal 20 transmits UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. The terminal 20 also transmits UCI of each carrier under the control of the base station 10-2 on the PUCCH of the PScell. In the example of FIG. 1, the cell group (CG) under the control of the base station 10-1 may be referred to as a Master Cell-Group (MCG). The cell group under the control of the base station 10-2 may be referred to as a Secondary Cell-Group (SCG).

[0017] When DC is performed, terminal 20 may transmit PUCCH via a Pcell, a PScell, and / or a PUCCH-Scell. Generally, it is not expected that terminal 20 transmits PUCCH via an Scell ​​other than a Pcell, a PScell, and a PUCCH-Scell.

[0018] In the following description, when it is not necessary to distinguish between base stations, they will be referred to as base station 10.

[0019] <CG PUSCH> As described above, in NR, the configuration of the CG PUSCH was specified in Release 15 (for example, Non-Patent Document 1). The CG PUSCH includes Type 1 CG PUSCH and Type 2 CG PUSCH.

[0020] Type 1 CG PUSCH The transmission parameters of Type 1 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". Activation and deactivation of Type 1 CG PUSCH depend on the RRC-configuration and are independent of Downlink Control Information (DCI).

[0021] Type 2 CG PUSCH The transmission parameters of Type 2 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "activation DCI". Activation and deactivation of Type 2 CG PUSCH depend on the RRC-configuration and DCI. One DCI can activate one CG PUSCH or multiple CG PUSCHs.

[0022] As mentioned above, XR is being considered in Release 17, and the target requirements for XR are to take into account capacity, latency, mobility, and energy saving. Therefore, it is assumed that CG PUSCH will be applied to XR services, and that multiple CGs will be used for one XR packet transmission.

[0023] 2 is a diagram illustrating an example of a CG PUSCH. Upper layer parameters cg-nrofSlots and cg-nrofPUSCH-InSlot are provided to a terminal 20. cg-nrofSlots indicates the number of consecutive slots allocated in a configured CG cycle. cg-nrofPUSCH-InSlot indicates the number of consecutive PUSCH allocations within a slot. FIG. 2 shows an example where cg-nrofSlots = 3 and cg-nrofPUSCH-InSlot = 2. The period of the CG PUSCH configuration (the period during which the CG PUSCH is transmitted, for example, 3 slots shown in FIG. 2) is repeated in the configured CG cycle.

[0024] The first PUSCH allocation is based on the Time Domain Resource Allocation (TDRA) in Type 1 CG PUSCH or higher layer configuration based on TS38.321. Alternatively, the first PUSCH allocation is based on the uplink (UL) grant received in the DCI in Type 2 CG PUSCH. The remaining PUSCH allocations have the same length and mapping type as the first PUSCH. Each PUSCH is added without gaps after the previous PUSCH.

[0025] <Agreements> At the RAN1 meeting, the following points were agreed upon in relation to CG enhancements in XR:

[0026] <Agreement 1> At the RAN1 #111 meeting, the following agreement was reached regarding support for CG extensions:

[0027] <Agreement 1-1> Supports dynamic indication of one or more unused CG PUSCH occasions based on UCI by the terminal.

[0028] For example, if there is an unused CG PUSCH occasion, the terminal may report the unused CG PUSCH occasion using UCI.

[0029] <Agreement 1-2> Support for multiple CG PUSCH occasions (multiple CG PUSCHs) during a single CG PUSCH configuration period.

[0030] For example, when multiple CG PUSCHs are configured, the terminal may configure multiple CG PUSCH occasions during the period of one of the CG PUSCH configurations.

[0031] <Agreement 2> Furthermore, at the RAN1 #112 meeting, it was agreed that the physical channel carrying UCI (UTO-UCI), which provides information on unused CG PUSCH occasions, is the CG PUSCH, i.e., the UTO-UCI is carried by the CG PUSCH.

[0032] <Agreement 3> In addition, at the RAN1 #112bis meeting, the following agreement was reached regarding the dynamic indication of unused CG PUSCH occasions:

[0033] <Agreement 3-1> With regard to the dynamic indication of unused CG PUSCH occasions based on UCI, the "unused" CG PUSCH occasions indicated by UTO-UCI in the CG PUSCH of one CG PUSCH configuration can be contiguous or non-contiguous CG PUSCH occasions (or transmission occasions (TOs))) in the time domain (within one CG PUSCH configuration period). However, it is not yet decided whether and how unused CG PUSCH occasions can be associated with multiple CG PUSCH configurations.

[0034] <Agreement 3-2> Option 1: For one CG PUSCH configuration, all transmitted CG PUSCHs include UTO-UCI (this is Option 1 of the corresponding agreement in RAN1 #112). However, the details are yet to be determined.

[0035] <Agreement 3-3> The UTO-UCI will provide a bitmap in which each bit indicates whether one CG PUSCH occasion within a certain period / range is "unused" or not. However, the details including the period / range are yet to be determined.

[0036] <Agreement 4> Furthermore, at the RAN1 #113 meeting, the following agreement was reached regarding UTO-UCI instructions:

[0037] <Agreement 4-1> The UTO-UCI indication for one CGPUSCH configuration is applicable only to valid CG PUSCH occasions, i.e., the UTO-UCI indicates only valid transmission occasions. Note that if a CG PUSCH (occasion) is dropped due to a collision with a downlink (DL) symbol indicated by the parameter tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or SSB, the CG PUSCH (occasion) is considered invalid, and CG PUSCHs (occasions) other than those mentioned above are considered valid.

[0038] For example, in relation to <Agreement 3-3>, as shown in Fig. 3, the UTO-UCI provides a bitmap corresponding to CG PUSCH occasions using "used" information represented by "0" indicating that the CG PUSCH occasion is used by the terminal, or "unused" information (or non-use information) represented by "1" indicating that the CG PUSCH occasion is not used by the terminal. Here, the four CG PUSCH occasions corresponding to "used" or "unused" are valid CG PUSCH occasions.

[0039] <Agreement 4-2> The indication of UTO-UCI by multiple CG PUSCHs associated with one CG PUSCH configuration is enabled by setting an RRC parameter, i.e., UTO-UCI is enabled for one CG configuration by an RRC parameter.

[0040] <Agreement 4-3> For one CG PUSCH configuration for an enabled UTO-UCI indication, the following four options (A-1a, A-2a, Ba, B-b2) for further down-selection are considered to determine the CG PUSCH indicated by the UTO-UCI indication.

[0041] [Option A-1a] - Set the RRC parameter UTO_period (the value and range of UTO_period are yet to be determined). - The first period of the UTO cycle (UTO period) starts at the same time as the start time of the first period of the CG PUSCH configuration and ends after UTO_period. One or more subsequent UTO periods follow the first UTO period. - CG PUSCHs transmitted within a UTO period carry UTO-UCI that is applicable to the CG PUSCH occasions within that UTO period.

[0042] [Option A-2a] - Set the RRC parameter UTO_period (the value and range of UTO_period are undefined). - Set the RRC parameter UTO_offset (the value and range of UTO_offset are undefined). - A transmitted CG PUSCH restricted to the UTO period carries UTO-UCI that is applicable to a CG PUSCH occasion within the UTO_period and UTO_offset after the end of the CG PUSCH.

[0043] [Option Ba] - Set the RRC parameter UTO_period (the value and range of UTO_period are TBD). - UTO_offset is an offset value, which is provided by configuration (the value of UTO_offset is TBD) or is 0. - The transmitted CG PUSCH carries UTO-UCI that is applicable to valid CG PUSCH occasions that are restricted to a UTO_period that starts UTO_offset after the end of the CG PUSCH.

[0044] [Option B-b2] - Set the RRC parameter Nu (Nu is the size of the bitmap, the value of Nu is TBD). - UTO_offset is an offset value, provided by configuration (the value and range of UTO_offset is TBD) or 0. - The transmitted CG PUSCH carries UTO-UCI applicable to Nu consecutive valid CG PUSCH occasions starting UTO_offset after the end of the CG PUSCH.

[0045] Note that the value of UTO_period, the time spanned over Nu consecutive CG PUSCH occasions, may correspond to a certain period / range described in <Agreement 3-3> and may be referred to as the period associated with the CG PUSCH configuration.

[0046] <Analysis> As described above, it is agreed in RAN1 #113 that UTO-UCI can indicate multiple CG PUSCHs associated with one CG PUSCH configuration.

[0047] If this can be extended to multiple CG PUSCH configurations, it would be unnecessary to generate and transmit UTO-UCI for each CG PUSCH configuration, which would contribute to efficient signaling. However, whether and how to extend this to multiple CG PUSCH configurations remains to be considered. In other words, it is not clear whether UTO-UCI can indicate used / unused information for multiple CG PUSCH configurations and the details thereof.

[0048] If the dynamic indication of unused CG PUSCH occasions is not properly reported to the base station due to the above-mentioned clarification, it may affect the operation of the base station or the terminal, and may also cause problems in terms of resource utilization efficiency.

[0049] Based on the above analysis, in this embodiment, a proposal regarding details of UTO-UCI that indicates used / unused information for multiple CG PUSCH configurations will be described below.

[0050] Note that, hereinafter, "unused" may include "unused." A "CG PUSCH occasion" may be referred to as a "CG PUSCH transmission occasion (TO)." A "CG PUSCH configuration" may be referred to as a "configured grant configuration or CG configuration." A "CG PUSCH configuration period" may be referred to as a "CG PUSCH period" or a "CG period." A CG period may be periodic. A "UTO-UCI indicating use / unused information for multiple CG configurations" may be referred to as "uplink control information indicating whether (or not) uplink transmission opportunities in multiple periods associated with each of multiple CG configurations are used by a terminal and / or for uplink signal transmission." " / " may mean "and / or."

[0051] <Outline of the Proposal> The outline of the proposal described in this embodiment is as follows: (1) Support content of UTO-UCI that indicates used / unused information for multiple CG configurations (Proposal 1), (2) Method for determining multiple CG configurations to be instructed or reported (Proposal 2), and (3) Details regarding the bitmap indicated by UTO-UCI to indicate used / unused information for multiple CG configurations (Proposal 3).

[0052] (Proposal 1) First, the support content of UTO-UCI, which indicates used / unused information for multiple CG configurations, will be explained below.

[0053] In Example 1, the UTO-UCI in the CG PUSCH may indicate used / unused information for up to X CG configurations, where X may be defined by a specification / standard and / or may depend on UE capability. For example, the terminal 20 may report used / unused information for up to X CG configurations to the base station 10 in the UTO-UCI in the CG PUSCH.

[0054] In Example 2, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations in the same serving cell (e.g., two CG configurations in FIG. 4 ) as shown in FIG. 4 , or may indicate used / unused information for multiple CG configurations in different (or separate) serving cells (e.g., three CG configurations in FIG. 5 ) as shown in FIG. 5 . The same serving cell may refer to the same serving cell (e.g., cell #1 in FIG. 4 and FIG. 5 ) as the serving cell through which the CG PUSCH carrying or including the UTO-UCI (e.g., see the left side of FIG. 4 and FIG. 5 ) is communicated. The different serving cell may refer to a serving cell (e.g., cell #2 in FIG. 5 ) that is different from the serving cell (e.g., cell #1 in FIG. 5 ) through which the CG PUSCH carrying or including the UTO-UCI (e.g., see the left side of FIG. 4 and FIG. 5 ) is communicated. For example, the terminal 20 may report to the base station 10, in the UTO-UCI within the CG PUSCH, used / unused information for multiple CG configurations in the same serving cell as the serving cell through which the CG PUSCH is communicated and / or in a serving cell different from the serving cell through which the CG PUSCH is communicated.

[0055] In Example 3, when two Sounding Reference Signal (SRS) resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations associated with the same SRS resource set(s) in the same serving cell, or may indicate used / unused information for multiple CG configurations associated with different SRS resource sets, or both. That is, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations associated with the same TRP (Transmission and Reception Point) in the same serving cell, or may indicate used / unused information for multiple CG configurations associated with different TRPs in the same serving cell, or both. The same TRP may mean the same TRP as the TRP through which the CG PUSCH carrying the UTO-UCI is communicated. A different TRP may mean a TRP different from the TRP through which a CG PUSCH carrying a UTO-UCI is communicated. For example, the terminal 20 may report, to the base station 10, in the UTO-UCI in the CG PUSCH, used / unused information for multiple CG configurations that are associated with the TRP through which the CG PUSCH is communicated and / or that are associated with a TRP different from the TRP through which the CG PUSCH is communicated.

[0056] In Example 4, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations with the same UE capability value set index, or may indicate used / unused information for multiple CG configurations with different UE capability value set indexes, or both. Here, the UE capability value set index may be replaced with a UE panel. The same UE capability value set index may mean the same UE panel as the UE panel through which the CG PUSCH carrying the UTO-UCI is communicated. A different UE capability value set index may mean a UE panel different from the UE panel through which the CG PUSCH carrying the UTO-UCI is communicated. For example, the terminal 20 may report, to the base station 10, used / unused information for multiple CG configurations with the UE panel through which the CG PUSCH is communicated and / or a UE panel different from the UE panel through which the CG PUSCH is communicated, in the UTO-UCI in the CG PUSCH.

[0057] In Example 5, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations with the same CG period, or may indicate used / unused information for multiple CG configurations with different CG periods, or both. The same CG period may mean the same CG period as the CG period corresponding to the CG PUSCH carrying the UTO-UCI. A different CG period may mean a CG period different from the CG period corresponding to the CG PUSCH carrying the UTO-UCI. For example, the terminal 20 may report, to the base station 10, used / unused information for multiple CG configurations of the CG period corresponding to the CG PUSCH and / or a CG period different from the CG period corresponding to the CG PUSCH, in the UTO-UCI in the CG PUSCH.

[0058] In Example 6, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations of the same CG type, or may indicate used / unused information for multiple CG configurations of different CG types, or both. Here, the CG type may refer to type 1 CG (PUSCH) or type 2 CG (PUSCH). The same CG type may refer to the same CG type as the CG type corresponding to the CG PUSCH carrying the UTO-UCI. The different CG type may refer to a CG type different from the CG type corresponding to the CG PUSCH carrying the UTO-UCI. For example, the terminal 20 may report used / unused information for multiple CG configurations of the CG type corresponding to the CG PUSCH and / or a CG type different from the CG type corresponding to the CG PUSCH to the base station 10 in the UTO-UCI in the CG PUSCH.

[0059] In Example 7, the UTO-UCI in the CG PUSCH may indicate used / unused information for multiple CG configurations with the same PHY (physical layer) priority, or may indicate used / unused information for multiple CG configurations with different PHY priorities, or both. The same PHY priority may mean the same PHY priority as the PHY priority corresponding to the CG PUSCH carrying the UTO-UCI. The different PHY priority may mean a PHY priority different from the PHY priority corresponding to the CG PUSCH carrying the UTO-UCI. For example, the terminal 20 may report, to the base station 10, used / unused information for multiple CG configurations with a PHY priority corresponding to the CG PUSCH and / or a PHY priority different from the PHY priority corresponding to the CG PUSCH, in the UTO-UCI in the CG PUSCH.

[0060] Any combination of the above examples may also be applied.

[0061] According to Proposal 1, it is possible to clarify the content (scope) supported by UTO-UCI, and by a terminal transmitting UTO-UCI to a base station based on this support, the base station and terminal can operate appropriately and utilize resources efficiently.

[0062] (Proposal 2) Next, for UTO-UCI indicating used / unused information for multiple CG configurations, a method for determining multiple CG configurations to be indicated by UTO-UCI (or reported by a terminal) will be described. As described below, multiple CG configurations may be determined by specification / standard definition and / or RRC configuration and / or activation DCI indication.

[0063] [Option 1] In Option 1, multiple CG configurations may be defined by a specification / standard. For example, the UTO-UCI in the CG PUSCH may indicate used / unused information for all activated CG configurations, as in the example described in Proposal 1. For example, the terminal 20 may determine or set all activated CG configurations as targets for indicating or reporting used / unused information.

[0064] [Option 2] In option 2, multiple CG configurations may be configured by RRC. This RRC configuration may be referred to as information about the CG configuration, information specifying the CG configuration, etc.

[0065] In one example, one or more CG configuration indices (and corresponding serving cell indices) may be set for a CG configuration of a CG PUSCH carrying UTO-UCI (also referred to as a CG configuration carrying UTO-UCI).

[0066] In one example, if at least one of the CG configurations set for a UTO-UCI is not activated, the terminal 20 may not report to the base station 10 in the UTO-UCI the use / unused information for such at least one non-activated CG configuration.

[0067] In one example, the terminal 20 may not assume that the CG configurations set for the UTO-UCI are not activated or have not been activated. In other words, the terminal 20 may assume that all of the CG configurations set for the UTO-UCI are activated or have been activated.

[0068] In one example, if the serving cell of at least one of the CG configurations set for a UTO-UCI is deactivated, the terminal 20 may not report the used / unused information for such at least one CG configuration (in the deactivated serving cell) to the base station 10 in the UTO-UCI.

[0069] In one example, the terminal 20 may not assume that the serving cells of the CG configurations configured for the UTO-UCI are not deactivated or have not been deactivated. In other words, the terminal 20 may assume that the serving cells of all the CG configurations configured for the UTO-UCI are activated or have been activated.

[0070] For example, in option 2, the terminal 20 may receive information specifying the CC configuration from the base station 10 via RRC, determine or configure multiple CG configurations based on the received information, and report in the UTO-UCI to the base station 10 the used / unused information for the multiple CG configurations that have been determined or configured (activated).

[0071] [Option 3] In option 3, multiple CG configurations may be indicated (or notified) by a CG configuration activation DCI carrying a UTO-UCI. This activation DCI may be referred to as information about a CG configuration, information identifying a CG configuration, etc.

[0072] In one example, a list (candidate list) of candidate CG configurations (e.g., one or more CG configuration indices (and corresponding serving cell indices)) may be configured for the CG configuration carrying the UTO-UCI. Then, the activation DCI may indicate one or more indices from the candidate list.

[0073] In one example, if at least one of the CG configurations indicated by the activation DCI is not activated, the terminal 20 may not report in the UTO-UCI to the base station 10 the use / unused information for such at least one non-activated CG configuration.

[0074] In one example, the terminal 20 may not assume that the CG configurations indicated by the activation DCI are not activated or have not been activated. In other words, the terminal 20 may assume that all of the CG configurations indicated by the activation DCI are activated or have been activated.

[0075] In one example, if the serving cell of at least one of the CG configurations indicated by the activation DCI is deactivated, the terminal 20 may not report the used / unused information for such at least one CG configuration (in the deactivated serving cell) to the base station 10 in the UTO-UCI.

[0076] In one example, the terminal 20 may not assume that the serving cells of the CG configurations indicated by the activation DCI are not deactivated or have not been deactivated. In other words, the terminal 20 may assume that the serving cells of all the CG configurations indicated by the activation DCI are activated or have been activated.

[0077] For example, in option 3, the terminal 20 may receive a candidate list from the base station 10 via RRC, receive an activation DCI (information identifying a CC configuration) from the base station 10, determine or configure multiple CG configurations from the candidate list based on the activation DCI, and report used / unused information for the determined or configured (activated) multiple CG configurations to the base station 10 in the UTO-UCI.

[0078] [Variations] For options 2 and 3, the CG configuration carrying the UTO-UCI itself does not need to be configured / indicated. In other words, the UTO-UCI may always indicate whether the CG configuration is in use or not. Therefore, the activation DCI / RRC configuration may indicate / configure only the CG configuration additional to the UTO-UCI indication. For example, the activation DCI / RRC configuration may not include information identifying the CG configuration carrying the UTO-UCI, and may instead include information identifying CG configurations other than the CG configuration in question. This reduces the signaling overhead of the activation DCI / RRC configuration (control information).

[0079] According to Proposal 2, the terminal can determine multiple CG configurations to be indicated by UTO-UCI based on specification standard definitions and / or RRC settings and / or DCI instructions, and by the terminal transmitting UTO-UCI to the base station based on this determination, the base station and terminal can operate appropriately and utilize resources efficiently.

[0080] (Proposal 3) Next, a bitmap (a single bitmap or multiple separate bitmaps) indicated by the UTO-UCI to indicate used / unused information for multiple CG configurations will be described.

[0081] [Option 1] To indicate use / unuse information for multiple CG configurations, the UTO-UCI may indicate multiple separate bitmaps, one bitmap for each CG configuration. For example, the terminal 20 may generate, determine, or set one bitmap for each CG configuration.

[0082] The UTO-UCI related parameters (e.g., UTO_period and / or UTO_offset and / or Nu) as described above may be set / indicated separately, individually, or independently for each bitmap, or may be set / indicated commonly for all bitmaps. For example, the terminal 20 may receive such settings / indications from the base station 10 via RRC / MAC CE / DCI.

[0083] In Option 1, for each UTO-UCI bitmap, the bitmap may be determined as the case for a single CG configuration as described in Agreements 1-4 above.

[0084] The ordering of multiple bitmaps (for sequence ordering) may follow the following rules: 1. If the UTO-UCI indicates used / unused information for CG configurations in multiple serving cells, then the ordering shall be in ascending or descending order of the serving cell index. 2. Then the ordering shall be in ascending or descending order of the CG configuration index.

[0085] For example, as shown in FIG. 6 , assume there are two cells (#1 and #2). According to the above ordering rules, the cells are ordered first in the order of cell #1 (the bitmap for CG configuration #0 and the bitmap for CG configuration #1), followed by cell #2 (the bitmap for CG configuration #0). Next, in cell #1, the bitmap for CG configuration #0 and the bitmap for CG configuration #1 are ordered. Therefore, in the example shown in FIG. 6 , the cells are ordered overall in the order of the bitmap for CG configuration #0 in cell #1, the bitmap for CG configuration #1 in cell #1, and the bitmap for CG configuration #0 in cell #2.

[0086] If cell #2 does not exist, item 1 of the above ordering rule is omitted, and the bitmaps are ordered in the order of the bitmap for CG configuration #0 in cell #1, followed by the bitmap for CG configuration #1 in cell #1.

[0087] As a variation of the ordering rule, the CG configuration of the CG PUSCH carrying UTO-UCI may always be ordered as the first bitmap, and the order of other CG configurations may be determined according to the above ordering rule. The example of bitmap order shown in Figure 6 also follows this variation.

[0088] By defining the ordering rules as described above, the base station 10 and the terminal 20 can share the contents of the bitmap (used / unused information for multiple CG configurations).

[0089] For example, in option 1, the terminal 20 may generate, determine or set multiple separate ordered bitmaps, one bitmap per CG configuration, according to the ordering rules described above, and transmit the multiple bitmaps to the base station 10 in the UTO-UCI within the CG PUSCH.

[0090] For example, in option 1, one bitmap is generated for one set grant configuration, so that compatibility with previous agreements can be maintained.

[0091] [Option 2] To indicate used / unused information for multiple CG configurations, the UTO-UCI may indicate multiple separate bitmaps, one bitmap per serving cell. For example, the terminal 20 may generate, determine, or configure one bitmap for each serving cell.

[0092] The UTO-UCI related parameters (e.g., UTO_period and / or UTO_offset and / or Nu) as described above may be set / indicated separately, individually, or independently for each bitmap, or may be set / indicated commonly for all bitmaps. For example, the terminal 20 may receive such settings / indications from the base station 10 via RRC / MAC CE / DCI.

[0093] In option 2, when multiple CG configurations are associated (configured) with one serving cell, one bitmap is associated with the multiple CG configurations associated with one serving cell, and therefore the multiple CG PUSCHs (occasions) indicated by the multiple CG configurations need to be indexed for identification.

[0094] For each UTI-UCI bitmap, if there is only one CG configuration of the serving cell indicated by that UTI-UCI, the bitmap may be determined as in the single CG configuration case as described in Agreements 1 to 4 above.

[0095] On the other hand, for each UTI-UCI bitmap, if there are multiple CG configurations of the serving cell indicated by the UTI-UCI, the indexing of the CG PUSCHs indicated by the multiple CG configurations of the serving cell may follow at least one of the following two rules (Alt. 1 and Alt. 2).

[0096] Alt. 1: 1. First, order by ascending or descending CG PUSCH slot index. 2. Then, order by ascending or descending CG configuration index. 3. Then, order by ascending or descending start or end symbol index.

[0097] Alt. 2: 1. First, order by ascending or descending CG PUSCH slot index. 2. Then, order by ascending or descending start or end symbol index. 3. Then, order by ascending or descending CG configuration index.

[0098] In addition, in option 2, when UTO-UCI indicates used / unused information for CG configurations in multiple serving cells, the ordering of multiple bitmaps may follow the following rules: - The ordering shall be ascending or descending order of the serving cell index.

[0099] For example, suppose there are two cells (#1 and #2) as shown in Fig. 7. According to the above ordering rules, the cells are ordered in the order of cell #1 (the bitmap for all of CG configurations #0 and #1) and cell #2 (the bitmap for CG configuration #0).

[0100] As a variation of the ordering rule, the serving cell associated with the CG PUSCH carrying UTO-UCI may always be ordered as the first bitmap, and the order of the other CG configurations (the serving cells associated with them) may be determined according to the above ordering rule. The example of the bitmap order shown in Figure 7 also follows this variation.

[0101] By defining the indexing rules and ordering rules as described above, the base station 10 and the terminal 20 can share the contents of the bitmap (used / unused information for multiple CG configurations).

[0102] For example, in option 2, the terminal 20 may index the CG PUSCH according to the indexing rules described above, generate, determine or set multiple ordered bitmaps according to the ordering rules described above, with multiple separate bitmaps, one bitmap per serving cell, and transmit the multiple bitmaps to the base station 10 in the UTO-UCI.

[0103] [Option 3] To indicate used / unused information for multiple CG configurations, the UTO-UCI may indicate a single bitmap for all CG configurations (e.g., regardless of the number of serving cells). For example, the terminal 20 may generate, determine, or configure one bitmap for all multiple CG configurations in one or more serving cells.

[0104] For example, as shown in FIG. 8, even if there are two cells (#1 and #2), there may be one bitmap for all CG configurations (CC configuration #0 in cell #1, CC configuration #1 in cell #1, and CC configuration #0 in cell #2).

[0105] The UTO-UCI related parameters (e.g., UTO_period and / or UTO_offset and / or Nu) may be set / indicated for one bitmap. For example, the terminal 20 may receive such setting / indication from the base station 10 via RRC / MAC CE / DCI.

[0106] As in option 2, in option 3, one bitmap is associated with multiple CG configurations, so multiple CG PUSCHs indicating multiple CG configurations need to be indexed for identification.

[0107] In option 3, the indexing of the indicated CG PUSCH for multiple CG configurations may follow at least one of the following two rules (Alt. 1 and Alt. 2):

[0108] Alt. 1: 1. First, order by ascending or descending CG PUSCH slot index. 2. Then, order by ascending or descending serving cell index. 3. Then, order by ascending or descending CG configuration index. 4. Then, order by ascending or descending start or end symbol index.

[0109] Alt.2: 1. First, order by ascending or descending CG PUSCH slot index. 2. Then, order by ascending or descending start or end symbol index. 3. Then, order by ascending or descending serving cell index. 4. Then, order by ascending or descending CG configuration index.

[0110] By defining the indexing rules as described above, the base station 10 and the terminal 20 can share the contents of the bitmap (used / unused information for multiple CG configurations).

[0111] For example, in option 3, the terminal 20 may index the CG PUSCH according to the indexing rules described above, generate, determine or configure one bitmap for multiple CG configurations in one or more serving cells, and transmit one bitmap to the base station 10 in the UTO-UCI.

[0112] According to Proposal 3, a terminal can generate a UTO-UCI that indicates a single bitmap or multiple separate bitmaps according to indexing rules and ordering rules. When the terminal transmits the UTO-UCI thus generated to the base station, the base station and terminal can operate properly and utilize resources efficiently.

[0113] Meanwhile, the base station 10 transmits the RRC configuration related to the CG configuration to the terminal 20 and, if necessary, transmits an activation DCI to the terminal 20. The base station 10 receives the UTO-UCI generated and transmitted by the terminal 20 according to the above-described proposals 1 to 3 based on the RRC configuration (and, if necessary, the activation DCI).

[0114] <Operation Example> Next, an operation example of the terminal 20 will be described with reference to FIG.

[0115] In step S11, the terminal 20 generates UTO-UCI indicating used / unused information for multiple CG configurations. For example, the terminal 20 may generate UTO-UCI as described in the above-mentioned proposals 1 to 3 (for example, according to the ordering rules in the above-mentioned proposal 3). For example, the terminal 20 may generate uplink control information notifying whether the terminal 20 will use transmission opportunities within multiple time periods associated with each of multiple configured grant configurations.

[0116] In step S12, the terminal 20 transmits, via a CG PUSCH, the UTO-UCI generated in step S11 to the base station 10. For example, the terminal 20 may transmit the generated uplink control information in one of a plurality of periods associated with each of a plurality of configured grant configurations.

[0117] <UE capability> The UE capability indicating the capability of the terminal may include the following information indicating the capability of the terminal. The terminal 20 may report the following information indicating the capability of the terminal to the base station 10. Note that the information indicating the capability of the terminal may correspond to information defining the capability of the terminal.

[0118] Information defining whether the terminal supports UTO-UCI indicating used / unused information for multiple CG configurations. Information defining the maximum number of CG configurations for which UTO-UCI can indicate used / unused information. Information defining whether the terminal supports UTO-UCI indicating used / unused information for multiple CG configurations in different cells. Information defining whether the terminal supports UTO-UCI indicating used / unused information for multiple CG configurations for different TRPs (SRS resource sets). Information defining whether the terminal supports UTO-UCI indicating used / unused information for multiple CG configurations that use different UE panels (UE capability value set index).

[0119] <Example of Wireless Communication System> A wireless communication system according to this embodiment includes a base station 10 shown in FIG. 10 and a terminal 20 shown in FIG. 11. The number of base stations 10 and the number of terminals 20 are not particularly limited. For example, as shown in FIG. 1, the system may be one in which two base stations 10 (base station 10-1 and base station 10-2) communicate with one terminal 20. The wireless communication system may be a wireless communication system conforming to New Radio (NR). For example, the wireless communication system may be a wireless communication system conforming to a method called URLLC and / or IIoT.

[0120] The wireless communication system may be a wireless communication system conforming to a method called 5G, Beyond 5G, 5G Evolution, or 6G.

[0121] The base station 10 may be called an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). The terminal 20 may be called User Equipment (UE). The base station 10 may also be considered as a device included in a network to which the terminal 20 is connected.

[0122] The wireless communication system may include a Next Generation-Radio Access Network (hereinafter, referred to as NG-RAN). The NG-RAN includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). Note that the NG-RAN and 5GC may be simply referred to as a "network."

[0123] The base station 10 performs wireless communication with the terminal 20. For example, the wireless communication performed complies with NR. At least one of the base station 10 and the terminal 20 may support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements. Furthermore, at least one of the base station 10 and the terminal 20 may support Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CC). Furthermore, at least one of the base station 10 and the terminal 20 may support Dual Connectivity (DC), which performs communication between the terminal 20 and each of multiple base stations 10.

[0124] The wireless communication system may support multiple frequency bands. For example, the wireless communication system supports Frequency Range (FR) 1 and FR2. The frequency bands of each FR are, for example, as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz

[0125] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and may use a bandwidth (BW) of 5 MHz to 100 MHz. FR2, for example, is a higher frequency than FR1. FR2 may use an SCS of 60 kHz or 120 kHz, and may use a bandwidth (BW) of 50 MHz to 400 MHz. FR2 may also include an SCS of 240 kHz.

[0126] The wireless communication system according to this embodiment may support a frequency band higher than the FR2 frequency band. For example, the wireless communication system according to this embodiment may support a frequency band exceeding 52.6 GHz up to 114.25 GHz. Such a high frequency band may be called "FR2x."

[0127] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) having a larger Sub-Carrier Spacing (SCS) than the above-mentioned example may be applied. Furthermore, DFT-S-OFDM may be applied to both the uplink and the downlink, or to either one of them.

[0128] In a wireless communication system, a slot configuration pattern for time division duplexing (TDD) may be set. For example, the slot configuration pattern may specify a pattern indicating an order of two or more slots among a slot for transmitting a downlink (DL) signal, a slot for transmitting an uplink (UL) signal, a slot in which a DL signal, a UL signal, and a guard symbol are mixed, and a slot in which a signal to be transmitted is changed to flexible.

[0129] In addition, in a wireless communication system, a demodulation reference signal (DMRS) can be used for each slot to perform channel estimation of a PUSCH (or a PUCCH (Physical Uplink Control Channel)), and further, a DMRS allocated to each of multiple slots can be used to perform channel estimation of a PUSCH (or a PUCCH). Such channel estimation may be called joint channel estimation, or may be called by another name such as cross-slot channel estimation.

[0130] The terminal 20 may transmit, in multiple slots, the DMRS allocated to each of the multiple slots so that the base station 10 can perform joint channel estimation using the DMRS.

[0131] Next, the configurations of the base station 10 and the terminal 20 will be described. Note that the configurations of the base station 10 and the terminal 20 described below are examples of functions related to this embodiment. The base station 10 and the terminal 20 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0132] <Configuration of Base Station> Fig. 10 is a block diagram showing an example of the configuration of base station 10 according to this embodiment. Base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 10 communicates with terminal 20 (see Fig. 11) wirelessly.

[0133] The transmitter 101 transmits a downlink (DL) signal to the terminal 20. For example, under the control of the controller 103, the transmitter 101 transmits the DL signal (for example, information related to the CG configuration).

[0134] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of the terminal 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0135] The channels used for transmitting DL signals include, for example, a downlink data channel and a downlink control channel. For example, the downlink data channel may include a PDSCH (Physical Downlink Shared Channel), and the downlink control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits downlink control information to the terminal 20 using the PDCCH and transmits downlink data signals using the PDSCH.

[0136] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0137] The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 20. For example, the receiving unit 102 receives an UL signal (e.g., UTO-UCI, etc.) under the control of the control unit 103.

[0138] The control unit 103 controls the communication operations of the base station 10 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0139] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0140] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the terminal 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the terminal 20.

[0141] 11 is a block diagram showing an example of the configuration of terminal 20 according to this embodiment. Terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. Terminal 20 communicates with base station 10, for example, wirelessly.

[0142] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal (for example, information related to a CG configuration) under the control of the control unit 203. For example, the receiving unit 201 may receive information specifying a plurality of configured grant configurations, excluding a configured grant configuration associated with one period in which uplink control information generated by the control unit 203 is transmitted, from among a plurality of periods associated with each of the plurality of configured grant configurations.

[0143] The transmitter 202 transmits an UL signal to the base station 10. For example, the transmitter 202 transmits the UL signal (e.g., UTO-UCI, etc.) under the control of the controller 203. For example, the transmitter 202 may transmit uplink control information generated by the controller 203 in one of a plurality of periods associated with each of a plurality of configured grant configurations.

[0144] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the terminal 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

[0145] Channels used for transmitting UL signals include, for example, an uplink data channel and an uplink control channel. For example, the uplink data channel includes a PUSCH (Physical Uplink Shared Channel), and the uplink control channel includes a PUCCH (Physical Uplink Control Channel). For example, the terminal 20 transmits uplink control information to the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.

[0146] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).

[0147] The control unit 203 controls the communication operations of the terminal 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0148] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

[0149] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or a scheduling request (SR). The information to be fed back to the base station 10 may be included in UCI.

[0150] For example, the control unit 203 may generate uplink control information notifying whether the terminal 20 will use transmission opportunities within multiple time periods associated with each of the multiple configured grant configurations. For example, the control unit 203 may determine the multiple configured grant configurations based on information identifying the configured grant configurations received by the receiving unit 201. For example, the control unit 203 may generate uplink control information notifying, for each of the multiple configured grant configurations, using one bitmap, whether the terminal 20 will use transmission opportunities within multiple time periods associated with each of the multiple configured grant configurations. For example, when the multiple configured grant configurations are associated with any of multiple cells, the control unit 203 may generate uplink control information notifying, for each of the multiple cells, using one bitmap, whether the terminal 20 will use transmission opportunities within multiple time periods associated with each of the multiple configured grant configurations. For example, the control unit 203 may generate uplink control information that notifies, in a single bitmap, whether the terminal 20 will use transmission opportunities within multiple periods associated with each of multiple configured grant configurations.

[0151] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned example. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0152] With the above configuration, the terminal 20 can appropriately report the dynamic indication of unused CG PUSCH occasions to the base station 10 .

[0153] <Summary of the embodiment> As described above, according to one aspect of the present disclosure, there is provided a terminal including: a control unit that generates uplink control information that notifies whether an uplink transmission opportunity within a plurality of periods that correspond to each of a plurality of configured grant configurations will be used by the terminal; and a transmission unit that transmits the uplink control information during one of the plurality of periods.

[0154] With the above configuration, uplink control information indicating whether uplink transmission opportunities are to be used for multiple configured grant configurations is transmitted in one period, so that the terminal can appropriately report dynamic notification of unused uplink transmission opportunities to the base station, thereby enabling the base station and terminal to operate appropriately and to utilize resources efficiently.

[0155] In one example, the terminal further includes a receiving unit that receives information identifying the plurality of configuration grant configurations excluding the configuration grant configuration associated with the one period, and the control unit determines the plurality of configuration grant configurations based on the information.

[0156] With the above configuration, information specifying the grant configuration associated with one period is not signaled, so signaling overhead can be reduced.

[0157] In one example, the control unit generates the uplink control information notifying whether the uplink transmission opportunity will be used by the terminal using one bitmap for each of the plurality of configured grant configurations.

[0158] With the above configuration, one bitmap is generated for one set grant configuration, which allows compatibility with previous agreements and allows the contents of the bitmap to be shared appropriately.

[0159] In one example, the multiple configured grant configurations correspond to any of multiple cells, and the control unit generates the uplink control information that notifies each of the multiple cells in a single bitmap whether the uplink transmission opportunity will be used by the terminal.

[0160] With the above configuration, the contents of the bitmap can be shared appropriately.

[0161] In one example, the control unit generates the uplink control information that notifies, in a single bitmap, whether the uplink transmission opportunity will be used by the terminal.

[0162] With the above configuration, the contents of the bitmap can be shared appropriately.

[0163] According to one aspect of the present disclosure, a communication method is provided in which a terminal generates uplink control information that notifies whether uplink transmission opportunities within multiple periods corresponding to each of multiple configured grant configurations will be used by the terminal, and transmits the uplink control information during one of the multiple periods.

[0164] With the above configuration, uplink control information indicating whether uplink transmission opportunities are to be used for multiple configured grant configurations is transmitted in one period, so that the terminal can appropriately report dynamic notification of unused uplink transmission opportunities to the base station, thereby enabling the base station and terminal to operate appropriately and to utilize resources efficiently.

[0165] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0166] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, 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 assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0167] For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0168] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0169] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0170] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

[0171] The processor 1001 also reads programs (program codes), 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0172] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0173] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0174] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

[0175] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

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

[0177] Furthermore, the base station 10 and the 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0178] (Supplementary Notes on the Embodiments) Although the embodiments of the present disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present disclosure; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (unless inconsistent). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing procedures described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, base stations and terminals have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of a base station in accordance with an embodiment of the present disclosure, and the software operated by the processor of a terminal in accordance with an embodiment of the present disclosure may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0179] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described in the present disclosure and may be performed using other methods. For example, notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB))), other signals, or a combination thereof. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0180] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0181] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0182] <Operation of Base Station> In the present disclosure, specific operations described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0183] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0184] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

[0185] <Determination method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0186] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0187] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0188] <Software> Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0189] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0190] Information, Signals, etc., described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0191] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0192] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0193] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0194] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0195] <Base Station> In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0196] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0197] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0199] A mobile station may also be referred to by those skilled in the art as 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 suitable terminology.

[0200] <Base Station / Mobile Station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0201] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal may be configured to have the functions of the base station described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0202] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station may be configured to have the functions of the terminal described above.

[0203] Fig. 13 shows an example configuration of a vehicle 2001. As shown in Fig. 13, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0204] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0205] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0206] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0207] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0208] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0209] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0210] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2029, which are provided in the vehicle 2001.

[0211] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0212] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0213] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0214] <Meaning and Interpretation of Terms> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), ascertaining something that is considered to be a "judging" or "determining," and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like that are considered to be a "judging" or "determining." Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0215] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0216] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.

[0217] <Meaning of "based on"> As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0218] "First," "Second" Any reference to an element using a designation such as "first," "second," etc., 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 method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0219] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.

[0220] Open Format: When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0221] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0222] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0223] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.

[0224] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0225] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0226] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0227] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0228] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0229] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0230] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0231] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0232] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0233] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0234] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0235] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0236] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0237] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0238] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0239] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

[0240] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0241] Articles In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0242] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0243] One aspect of the present disclosure is useful in wireless communication systems.

[0244] 10 Base station 20 Terminal 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A terminal comprising: a control unit that generates uplink control information that notifies whether an uplink transmission opportunity within a plurality of periods corresponding to each of a plurality of configured grant configurations will be used by the terminal; and a transmission unit that transmits the uplink control information during one of the plurality of periods.

2. The terminal of claim 1, further comprising a receiving unit that receives information identifying the plurality of configuration grant configurations excluding a configuration grant configuration associated with the one period, wherein the control unit determines the plurality of configuration grant configurations based on the information.

3. The terminal according to claim 1, wherein the control unit generates the uplink control information notifying, by one bitmap for each of the plurality of configured grant configurations, whether the uplink transmission opportunity will be used by the terminal.

4. The terminal according to claim 1, wherein the plurality of configured grant configurations correspond to any of a plurality of cells, and the control unit generates the uplink control information that notifies each of the plurality of cells in a single bitmap whether the uplink transmission opportunity will be used by the terminal.

5. The terminal according to claim 1, wherein the control unit generates the uplink control information notifying, in a single bitmap, whether the uplink transmission opportunity will be used by the terminal.

6. A communication method in which a terminal generates uplink control information notifying whether an uplink transmission opportunity within a plurality of periods corresponding to each of a plurality of configured grant configurations will be used by the terminal, and transmits the uplink control information during one of the plurality of periods.

Images