Terminal, base station, and communication method

Abstract

To provide a terminal, a base station, and a communication method that reduce power consumption by controlling a BWP.SOLUTION: In a wireless communication system, a terminal includes: a reception unit configured to receive control information for changing a bandwidth to be used and a first setting related to a SPS-PDSCH or a second setting related to a CG-PUSCH from a base station; a communication unit configured to receive the SPS-PDSCH from the base station based on the first setting or to transmit the CG-PUSCH to the base station based on the second setting; and a control unit configured to change the bandwidth to be used based on the control information. The control unit determines a RB index of a frequency domain resource allocation in the changed bandwidth based on the control information. The communication unit receives the SPS-PDSCH from the base station or transmits the CG-PUSCH to the base station based on the RB index in the changed bandwidth.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a terminal, a base station, and a communication method in a wireless communication system. [Background technology]

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption are being considered (for example, Non-Patent Document 1).

[0003] In NR, a PUSCH based on a configured grant (CG) (CG PUSCH) is being considered for the uplink (UL), and a PDSCH based on semi-persistent scheduling (SPS) (SPS PDSCH) is being considered for the downlink (DL).

[0004] 3GPP (registered trademark) Release 16 specifies the configuration of a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) and the configuration of a Configured Grant Physical Uplink Scheduled Channel (CG-PUSCH) (for example, Non-Patent Document 1). Note that, hereinafter, the configuration of the SPS-PDSCH may be abbreviated as "SPS configuration." Also, hereinafter, the configuration of the CG-PUSCH may be abbreviated as "CG configuration."

[0005] 3GPP Release 17 also examines Extended Reality (XR), including virtual reality (VR) and mixed reality (MX), and considers XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. The target requirements for XR include capacity, latency (delay), mobility, and power saving. Furthermore, the above considerations are continuing in Release 18.

[0006] Furthermore, in order to achieve carbon neutrality and the Sustainable Development Goals (SDGs), the importance of reducing power consumption in base stations is increasing, and therefore 3GPP Release 18 is considering power saving measures for base stations (for example, Non-Patent Document 2). At present, however, 3GPP has not specified any technology for reducing power consumption in base stations. [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TS 38.300 V17.2.0(2022-09) [Non-patent document 2] "New SI: Study on network energy savings for NR", RP-213554, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 [Non-patent document 3] 3GPP TS 38.211 V17.3.0(2022-09) [Non-patent document 4] 3GPP TS 38.213 V17.3.0(2022-09) [Non-Patent Document 5] 3GPP TS 38.331 V17.2.0(2022-09) [Non-patent document 6] 3GPP TS 38.214 V17.3.0(2022-09) Summary of the Invention [Problem to be solved by the invention]

[0008] It has been decided to study ways to reduce network power consumption. For example, methods of switching the Bandwidth Part (BWP) to limit the bandwidth used for power saving are being studied. However, the detailed procedures for BWP control to reduce network power consumption when CG-PUSCH or SPS-PDSCH is configured have not been clear.

[0009] The present invention has been made in view of the above points, and has as its object to reduce power consumption in a wireless communication system by controlling BWP (Bandwidth Part). [Means for solving the problem]

[0010] According to the disclosed technology, there is provided a terminal including: a receiving unit that receives control information for changing a bandwidth to be used, and a first setting for a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting for a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) from a base station; a communication unit that receives the SPS-PDSCH from the base station based on the first setting or transmits the CG-PUSCH to the base station based on the second setting; and a control unit that changes the bandwidth to be used based on the control information, wherein the control unit determines a resource block (RB) index for frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit receives the SPS-PDSCH from the base station or transmits the CG-PUSCH to the base station based on the RB index, in the changed bandwidth. [Effects of the Invention]

[0011] According to the disclosed technology, it is possible to reduce power consumption in a wireless communication system by controlling a BWP (Bandwidth Part). [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram illustrating a configuration example (1) of a wireless communication system. [Figure 2] FIG. 10 is a diagram illustrating a configuration example (2) of a wireless communication system. [Figure 3] FIG. 1 is a diagram for explaining an example (1) of a common BWP according to an embodiment of the present invention. [Figure 4] FIG. 10 is a diagram for explaining an example (2) of a common BWP according to an embodiment of the present invention. [Figure 5] FIG. 10 is a sequence diagram illustrating an example of BWP switching according to an embodiment of the present invention. [Figure 6] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention. [Figure 8] 1 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 9] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0014] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but not limited to, the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR) unless otherwise specified.

[0015] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0016] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0017] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0018] Fig. 1 is a diagram showing a configuration example (1) of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0019] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is, for example, transmitted via NR-PBCH and is also referred to as broadcast information. The synchronization signal and system information may be referred to as SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in the downlink (DL) and receives control signals or data from the terminal 20 in the uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

[0020] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures the propagation path quality based on the reception results of the reference signals.

[0021] Terminal 20 is capable of performing carrier aggregation, which aggregates multiple cells (multiple CCs (Component Carriers)) to communicate with base station 10. In carrier aggregation, one PCell (Primary cell) and one or more SCells (Secondary cells) are used. Also, a PUCCH-SCell having a PUCCH may be used.

[0022] Fig. 2 is a diagram showing an example (2) of a wireless communication system according to an embodiment of the present invention. Fig. 2 shows an example of the configuration of a wireless communication system in which DC (Dual connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as an MN (Master Node) and a base station 10B serving as an SN (Secondary Node) are provided. The base station 10A and the base station 10B are each connected to a core network. The terminal 20 can communicate with both the base station 10A and the base station 10B.

[0023] A cell group provided by base station 10A, which is an MN, is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in a DC, an MCG is composed of one PCell and one or more SCells, and an SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.

[0024] The processing operations in this embodiment may be executed in the system configuration shown in FIG. 1, in the system configuration shown in FIG. 2, or in any other system configuration.

[0025] <CG PUSCH> Next, the CG PUSCH will be described. The CG PUSCH is a method of performing UL transmission using a PUSCH based on an UL grant configured by a higher layer (which may be called, for example, a configured grant or a configured UL grant). With the CG PUSCH, UL resources are already allocated to terminal 20, and terminal 20 can perform UL transmission autonomously using the configured resources, so that low-latency communication can be expected to be realized.

[0026] Release 16 specifies two types of CG PUSCH: Type 1 and Type 2. Activation / deactivation of Type 1 CG PUSCH depends only on RRC-configuration and does not depend on DCI. In Type 1 CG PUSCH, parameters used for uplink transmission (which may also be referred to as CG parameters, CG configuration (Configured Grant Configuration) information, etc.) are configured in terminal 20 using only higher layer signaling. Specifically, parameters of Type 1 CG PUSCH are provided by "ConfiguredGrantConfig," "pusch-Config," and "rrc-ConfiguredUplinkGrant." That is, base station 10 instructs terminal 20 of uplink transmission parameters using "ConfiguredGrantConfig," "pusch-Config," and "rrc-ConfiguredUplinkGrant." Terminal 20 stores the received parameters as a configuration grant.

[0027] When the Type 1 CG PUSCH is activated, the terminal 20 may determine that one or more configuration grants have been triggered (or activated), and may transmit PUSCHs using the configured resources (which may also be called CG resources, transmission occasions, etc.) without a dynamic grant.

[0028] Activation / deactivation of Type 2 CG PUSCH depends on the RRC configuration and DCI. One DCI can activate only one CG PUSCH and can deactivate multiple CG PUSCHs. In Type 2 CG PUSCH, parameters used for uplink transmission are configured in the terminal 20 using higher layer signaling. Some of the parameters used for uplink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of Type 2 CG PUSCH are provided by "ConfiguredGrantConfig," "pusch-Config," and "activation DCI." That is, the base station 10 instructs the terminal 20 of the uplink transmission parameters using "ConfiguredGrantConfig," "pusch-Config," and "activation DCI." The terminal 20 stores the received parameters.

[0029] When the Type 2 CG PUSCH is activated and an activation DCI is notified, the terminal 20 may determine that one or more configuration grants have been triggered (or activated) and may transmit a PUSCH without a dynamic grant using resources configured by a higher layer. The activation DCI may be CRC (Cyclic Redundancy Check) scrambled using a predetermined identifier (for example, a CS-RNTI: Configured Scheduling RNTI).

[0030] Furthermore, terminal 20 may release (also referred to as release, deactivate, etc.) resources (PUSCH) corresponding to a Configured Grant based on a deactivation DCI that deactivates the Configured Grant or the expiration of a predetermined timer (the passage of a predetermined time). The deactivation DCI may be CRC (Cyclic Redundancy Check) scrambled using a predetermined identifier (for example, a CS-RNTI: Configured Scheduling RNTI).

[0031] <SPS PDSCH> Next, the SPS PDSCH will be described. In the SPS PDSCH, periodic resources for downlink (DL) Semi-Persistent Scheduling (SPS) are configured by higher layers. Activation / deactivation (release) of transmission using the resources in the SPS PDSCH depends on activation DCI / deactivation DCI. The activation DCI / deactivation DCI may be CRC (Cyclic Redundancy Check) scrambled using a predetermined identifier (for example, CS-RNTI: Configured Scheduling RNTI).

[0032] In the SPS PDSCH, parameters used for downlink transmission (which may also be called SPS parameters, SPS configuration (Semi-Persistent Scheduling configuration) information, etc.) are configured in the terminal 20 using higher layer signaling. Some of the parameters used for downlink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of the SPS PDSCH are provided by "sps-Config" and "activation DCI." That is, the base station 10 instructs the terminal 20 on the downlink transmission parameters using "sps-Config" and "activation DCI." The terminal 20 stores the received parameters.

[0033] <CG PUSCHのパラメータ> Parameters in ConfiguredGrantConfig for Type 1 and / or Type 2 CG PUSCH (hereinafter referred to as "CGC-CG parameter(s)") include, for example, the following: Note that when CGC-CG parameters are provided by both ConfiguredGrantConfig and pusch-Config, terminal 20 may apply the CGC-CG parameters indicated in ConfiguredGrantConfig to PUSCH transmission. Furthermore, when there are CGC-CG parameters not provided by ConfiguredGrantConfig, terminal 20 may apply the CGC-CG parameters indicated in pusch-Config to PUSCH transmission.

[0034] (Example of CGC-CG parameters) periodicity: Used to indicate the periodicity of PUSCH transmission corresponding to the configured grant. ·repK: Used to indicate the number of repeated PUSCH transmissions. · repK-RV: Used to indicate information about the redundancy version of the repeated PUSCH transmission. · frequencyHopping: Used to set either intra-slot frequency hopping or inter-slot frequency hopping valid. If this field is not present, frequency hopping may not be applied. cg-DMRS-Configuration: Used to indicate the DMRS configuration of the PUSCH corresponding to the configured grant. mcs-Table: Used to indicate the MSC table that the terminal 20 uses for PUSCH without transform precoding. If this field is not present, the terminal 20 may use the 64QAM table. mcs-TableTransformPrecoder: Used to indicate the MSC table that the terminal 20 uses for PUSCH with transform precoding. If this field is not present, the terminal 20 may use the 64QAM table. uci-OnPUSCH: Used to indicate information about UCI transmission using PUSCH. · resourceAllocation: Used to indicate that one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switch' is set. ·rbg-Size: Used to indicate the RBG size of the PUSCH. · powerControlLoopToUse: Used to indicate the closed control loop to apply to PUSCH transmission. p0-PUSCH-Alpha: Used to calculate the PUSCH transmit power. ·transformPrecoder: Used to indicate whether to select transform precoding for PUSCH transmission. phy-PriorityIndex: Used to indicate the PHY priority of the CG PUSCH at least in collision processing in the PHY layer. Note that value p0 indicates low priority and value p1 indicates high priority. ·cg-nrofHARQ-Process: Used to indicate the HARQ process number. · cg-nrofSlots: Used to indicate the number of allocation slots set in the grant period following the time instance set in the grant offset. · betaOffsetCG-UCI: Used to indicate the beta offset of CG-UCI in CG-PUSCH. configuredGrantTimer: Used to indicate the initial value of the configured grant timer as a multiple of the periodicity. If cg-RetransmissonTimer is configured, and HARQ processes are shared between different configured grants on the same BWP, the periodicity of configuredGrantTimer is set to the same value as the configurations that share the HARQ processes on this BWP.

[0035] Parameters in rrc-ConfiguredUplinkGrant for Type 1 CG PUSCH (hereinafter referred to as "rrc-CUG-CG parameter(s)") include, for example, the following: Note that rrc-ConfiguredUplinkGrant is used to indicate information about the grant configured in Type 1 CG PUSCH.

[0036] (Example of rrc-CUG-CG parameters) timeDomainOffset: Used to indicate an offset relative to the system frame numbered 0. · timeDomainAllocation: Used to indicate the combination of the PUSCH mapping type, the start symbol of the PUSCH, and the number of consecutive allocated symbols. frequencyDomainAllocation: Used to indicate the frequency resource allocation of PUSCH. ·antennaPort: Used to indicate antenna port information for PUSCH transmission. ·dmrs-SeqInitialization: Identifier used for scrambling the DMRS sequence for PUSCH transmission. · precodingAndNumberOfLayers: Used to indicate the precoding and number of layers for PUSCH transmission. · srs-ResourceIndicator: Used to indicate the SRS (Sounding Reference Signal) resource to be used. · mcsAndTBS: Used to indicate modulation order, target coding rate, and transport block size. frequencyHoppingOffset: Used to indicate the frequency hopping offset. · pathlossReferenceIndex: Used to indicate the reference signal used for PUSCH pathloss estimation. pusch-RepTypeIndicator: Used to indicate whether the terminal 20 follows the operation for PUSCH repetition type A or the operation for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables "PUSCH repetition type A", and the value pusch-RepTypeB enables "PUSCH repetition type B". frequencyHoppingPUSCH-RepTypeB: Used to indicate the frequency hopping method for Type 1 CG when pusch-RepTypeIndicator is set to "pusch-RepTypeB". The value interRepetition enables "Inter-repetition frequency hopping", and the value interSlot enables "Inter-slot frequency hopping". Note that if this field is not present, frequency hopping is not enabled for Type 1 CG.

[0037] Parameters indicated by activation DCI for Type 2 CG PUSCH (hereinafter referred to as "DCI-CG parameter(s)") include, for example, the following:

[0038] (Example of DCI-CG parameters) · timeDomainAllocation: Used to indicate the start symbol and length combination and PUSCH mapping type. frequencyDomainAllocation: Used to indicate frequency domain resource allocation. ·MCS index: Used to indicate the index of the MCS (Modulation and Coding Scheme). ·antenna port indication: Used to indicate the antenna port. · precoding and number of layers indication: Used to indicate the precoding and number of layers. · SRS resource indicator: Used to indicate resources for SRS (Sounding Reference Signal). · power control related parameter indication: Used to indicate parameters related to transmission power control.

[0039] <SPS PDSCHのパラメータ> The parameters in the SPS-Config for the SPS PDSCH (hereinafter referred to as "SC-SPS parameter(s)") include, for example, the following:

[0040] (Example of SC-SPS parameters) periodicity: Used to indicate the period of the SPS PDSCH. n1PUCCH-AN: Used to indicate the HARQ-ACK (Hybrid automatic repeat request Acknowledgement) PUCCH resource for SPS PDSCH. · mcs-Table: Used to indicate the MCS table applied to receiving SPS PDSCH. · pdsch-AggregationFactor: Used to indicate the number of repeated PDSCH transmissions.

[0041] Parameters indicated by activation DCI for SPS PDSCH (hereinafter referred to as "DCI-SPS parameter(s)") include, for example, the following:

[0042] (Example of DCI-SPS parameters) · timeDomainAllocation: Used to indicate the start symbol and length combination and PDSCH mapping type. frequencyDomainAllocation: Used to indicate frequency domain resource allocation. ·MCS index: Used to indicate the index of the MCS (Modulation and Coding Scheme). TCI state indication: Used to indicate the status of the TCI (Transmission Configuration Indicator) for PDSCH. ·antenna port indication: Used to indicate the antenna port. Priority of HARQ-ACK: Used to indicate the priority of HARQ-ACK. · K1: Used to indicate the number of slots from the slot where data is scheduled on the PDSCH to the slot where HARQ-ACK for that PDSCH is transmitted.

[0043] <Other parameters> Parameters other than those mentioned above (hereinafter referred to as "other-CG / SPS parameter(s)") notified from base station 10 to terminal 20 include, for example, the following.

[0044] (Example of other-CG / SPS parameters) PDSCH / PUSCH length: Used to indicate the length of the PDSCH and / or PUSCH. · Number of PRBs: Used to indicate the number of PRBs (Physical Resource Blocks).

[0045] <bwp> In NR, the maximum bandwidth per carrier is, for example, 100 MHz at frequencies below 6 GHz, and 400 MHz above that, which is significantly larger than that of LTE. In order to enable a terminal 20 that supports only a smaller bandwidth than a carrier operating at such a wide bandwidth to communicate using the carrier, for example, Releases 15-17 of 3GPP (NR) support a technology called Bandwidth Part (BWP). For example, NR supports BWP (see, for example, Sec. 4.4.5 of Non-Patent Document 3).

[0046] The base station 10 sets (provides) information about BWPs to the terminal 20. For example, the terminal 20 is provided with parameters of the serving cell for each DL BWP (downlink BWP) or UL BWP (uplink BWP) in one set of DL BWPs (downlink BWPs) or UL BWPs (uplink BWPs) (see, for example, Sec. 12 of Non-Patent Document 4 and Sec. 4.4.5 of Non-Patent Document 5). For example, the terminal 20 is provided with the following parameters:

[0047] - Parameter "subcarrierSpacing" indicating subcarrier spacing - Parameter "CyclicPrefix" indicating cyclic prefix -Common RB: NBWPstart=Ocarrier+RBstart and number of consecutive RBs: NBWPsize=LRB - index within the set of DL BWPs or UL BWPs by their respective BWP-Ids - In the case of DL BWP, a set of BWP-common parameters and BWP-dedicated parameters by the parameter "BWP-DownlinkCommon" and the parameter "BWP-DownlinkDedicated", or in the case of UL BWP, a set of BWP-common parameters and BWP-dedicated parameters by the parameter "BWP-UplinkCommon" and the parameter "BWP-UplinkDedicated".

[0048] Note that the above common RB and the number of consecutive RBs are provided by the parameter "locationAndBandwidth" that indicates the offset RBstart and the length LRB as RIV according to the set value NBWPsize = 275 and the value Ocarrier provided by the parameter "offsetToCarrier" for the parameter "subcarrierSpacing". The RIV is determined by the following formula (for example, refer to Sec.6.1.2.2.2 of Non-Patent Document 6).

[0049] [Number]

[0050] [BWP Switching] In Releases 15 - 17 of 3GPP, a technology called BWP switching for switching BWP is supported. For example, the terminal 20 is instructed to perform BWP switching by a timer such as Radio Resource Control (RRC), Medium Access Control - Control Element (MAC-CE), Downlink Control Information (DCI), or an Inactivity timer.

[0051] For example, DCI formats 0_1 / 0_2 / 1_1 / 1_2 are used for BWP switching. The terminal 20 performs, for example, reception of PDSCH and / or transmission of PUSCH while dynamically switching the BWP.

[0052] The timer is used to allow the terminal 20 to fallback to the default DL BWP and enable misdetection of DCI indicating BWP switching. The timer is set by RRC in milliseconds.

[0053] The timer starts subtracting from the value configured by RRC, for example, or restarts (e.g., resets the value configured by RRC and starts subtracting) when there is a downlink or uplink grant or when there is a configured downlink or uplink channel.

[0054] That is, the timer does not expire if there is a downlink or uplink grant or if there is a configured downlink or uplink channel. , the terminal 20 does not fall back the BWP to the default DL BWP.

[0055] Otherwise, the timer decrements, for example, at the end of a subframe in the case of a frequency band in Frequency Range (FR) 1, or at the end of half of a subframe in the case of a frequency band in FR2. When the timer expires (for example, when the value set by RRC becomes 0), the terminal 20 falls back to the default DL BWP.

[0056] By the above operation, for example, even if the BWP assumed (set) by terminal 20 differs from the BWP assumed by base station 10 and terminal 20 cannot receive DCI indicating BWP switching, the BWP returns to the default DL BWP when the timer expires. Terminal 20 can receive DCI indicating BWP switching in the default DL BWP.

[0057] The default DL BWP is the BWP set by "defaultDownlinkBWP-Id" (if set), and the initial BWP in other cases. For example, if the default DL BWP is not set by "default DownlinkBWP-Id", the terminal 20 assumes that the initial BWP used for initial access is the default DL BWP.

[0058] Also, in the case of TDD, the DL BWP and the UL BWP are associated, so BWP switching is performed in both the downlink and the uplink.

[0059] <Power saving of base station 10> In order to achieve carbon neutrality and the Sustainable Development Goals (SDGs), it is becoming increasingly important to reduce the power consumption of base stations 10 (networks). However, technology for reducing the power consumption of base stations 10 has not been standardized by 3GPP.

[0060] 3GPP Release 16 specifies that the SPS configuration and / or CG configuration are set for each terminal and for each BWP. Note that, hereinafter, the SPS configuration and / or CG configuration may be abbreviated as "SPS / CG configuration."

[0061] Furthermore, power saving for base stations is being considered as one of the XR-related study items in 3GPP Release 18. When a base station limits the bandwidth used to save power, it instructs BWP switching for each terminal within the cell.

[0062] Each terminal performs BWP switching according to instructions from the base station. BWP switching is performed for network energy saving (NW ES) and traffic leveling of each band. If an SPS / CG configuration is set for each terminal, each time BWP switching is performed, each terminal needs to reset the SPS / CG configuration and activate the SPS PDSCH and CG PUSCH.

[0063] Therefore, if BWP switching is performed frequently, the SPS / CG configuration will be reset and the SPS PDSCH and CG PUSCH will be activated frequently, which will increase the overhead of higher layer signaling and DCI. The applicant of the present application has focused on the above-mentioned problem and has come up with this proposal.

[0064] <Proposal> In this proposal, it is proposed that the SPS / CG configuration be set for each cell or each group of terminals.

[0065] This may result in cases where it is not necessary to reset the SPS / CG configuration and activate the SPS PDSCH and CG PUSCH even when BWP switching is performed, which can suppress an increase in the overhead of higher layer signaling and DCI.

[0066] Below, we will explain the options (sometimes abbreviated as "Opt."), alternations (sometimes abbreviated as "Alt."), specific examples and / or variations of each proposal.

[0067] In the following, an SPS / CG configuration that is set uniquely for each cell may be referred to as a "cell-specific SPS / CG configuration," and an SPS / CG configuration that is set for each group of terminals may be referred to as a "group-common SPS / CG configuration." Furthermore, a cell-specific SPS / CG configuration and / or a group-common SPS / CG configuration may be referred to as a "cell-specific / group-common SPS / CG configuration."

[0068] An identifier (Id) indicating the cell-specific / group-common SPS / CG configuration is notified from the base station to each terminal in the cell by a parameter of higher layer signaling (higher layer parameter) such as RRC.

[0069] Here, a "group of terminals" in this application refers to each group after multiple terminals belonging to a specific cell are grouped into several groups. For example, if there are 12 terminals, UE1 to UE12, belonging to a specific cell, and terminals UE1 to UE3 are group A, terminals UE4 to UE6 are group B, terminals UE7 to UE9 are group C, and terminals UE10 to UE12 are group D, then each of groups A, B, C, and D is a "group of terminals" in this application. Note that a "terminal belonging to a specific cell" can also be referred to as a terminal communicating with the base station of the cell. In the above example, when a common SPS / CG configuration is configured for group A, the base station notifies terminals UE1 to UE3 of information indicating the group-common SPS / CG configuration by activation DCI or the like.

[0070] Note that the cell-specific SPS / CG configuration can be applied to any of the SPS PDSCH, Type 1 CG PU SCH, and Type 2 CG PUSCH, while the group-common SPS / CG configuration can be applied to the SPS PDSCH and Type 2 CG PUSCH.

[0071] <Proposal 1> In Proposal 1, when a common BWP is configured between a base station and a terminal, the relationship between the cell-specific / group-common SPS / CG configuration and the common BWP is proposed.

[0072] First, the common BWP will be explained using Fig. 3. Fig. 3 shows BWP1 to BWP4 of terminals UE1 to UE4 as an example. For example, terminals UE1 to UE4 switch from BWP1 to BWP4 to a common BWP as shown by arrow A in Fig. 3 based on an instruction from a base station or a timer. This operation narrows the communication bandwidth from the viewpoint of the base station, thereby realizing energy saving (ES).

[0073] A common BWP may be considered as a BWP in which the frequencies of BWPs of multiple terminals are aligned and the bandwidths of BWPs of multiple terminals are set to the same. A common BWP may also be called a NW ES BWP or ES BWP. NW is an abbreviation for network.

[0074] A plurality of common BWPs may be set. The plurality of common BWPs may have different bandwidths. One of the plurality of common BWPs with different bandwidths may be selected depending on, for example, the mode, service, or type of the NW ES.

[0075] The common BWP may be configured for each cell, for example, by using parameters that are commonly configured for all terminals in the cell.

[0076] The parameters are notified to the terminal from the base station, for example. The parameters may be parameters of higher layer signaling such as RRC (higher layer parameters). The parameters are parameters set for each cell (cell unit), and may be referred to as cell-specific parameters.

[0077] Specifically, the common BWP for NW ES is configured by a new upper layer parameter such as "EnergySavingBWP" included in "ServingCellConfigCommon" and / or "DownlinkConfigCommon" and / or "UplinkConfigCommon." "ServingCellConfigCommon," "DownlinkConfigCommon," and "UplinkConfigCommon" may be referred to as information elements (IEs) or parameters.

[0078] For example, when a common BWP is configured in common in DL and UL, the common BWP is configured in ServingCellConfigCommon. For example, when a common BWP is configured in common in DL and UL, higher layer parameters for the common BWP, such as EnergySavingBWP, are configured in ServingCellConfigCommon.

[0079] For example, when a common BWP is configured separately in DL and UL, the common BWP is configured in "DownlinkConfigCommon" and "UplinkConfigCommon", respectively. For example, when a common BWP is configured separately in DL and UL, the EnergySavingBWP parameter for the common BWP in DL is configured in DownlinkConfigCommon, and the EnergySavingBWP parameter for the common BWP in UL is configured in UplinkConfigCommon.

[0080] In Proposal 1, cell-specific / group-common SPS / CG configuration may be configured for (Alt. 1) common BWP or may not be configured for (Alt. 2) common BWP.

[0081] (Alt.1: When set for common BWP) FIG. 4 is a diagram illustrating an example of Proposal 1-Alt. 1. FIG. 4 shows BWP1 to BWP4 of terminals UE1 to UE4 as an example. Also, in FIG. 4, each of terminals UE1 to UE4 initially configures a UE-specific SPS / CG configuration. Thereafter, each of terminals UE1 to UE4 switches from BWP1 to BWP4 to a common BWP, as indicated by arrow B in FIG. 4, based on higher layer parameters (for example, RRC configuration). At this time, by making the SPS / CG configuration of each of terminals UE1 to UE4 cell-specific or group-common, there is no need to activate the SPS PDSCH and / or CG PUSCH. Furthermore, thereafter, when BWP switching from a common BWP to a terminal-specific BWP is performed and then BWP switching to a common BWP is performed again, there is no need to reset the SPS / CG configuration.

[0082] (Alt.1-1) When a cell-specific / group-common SPS / CG configuration is configured for a common BWP, the cell-specific / group-common SPS / CG configuration may be configured by a parameter such as EnergySavingBWP among cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and / or uplinkConfigCommon. Note that the BWP Id of the common BWP may be set in the EnergySavingBWP. The BWP Id is, for example, an identifier for identifying a BWP. That is, the BWP Id for identifying the common BWP may be set by the EnergySavingBWP.

[0083] (Alt.1-2) Alternatively, the index of the cell-specific and / or group-common SPS configuration and / or the index of the cell-specific and / or group-common CG configuration (hereinafter referred to as "cell-specific / group-common SPS / CG configuration index") may be set by a parameter such as EnergySavingBWP, and the CG PUSCH config (configuredGrantConfig) and / or SPS config (sps-config) may be set in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and / or uplinkConfigCommon, including EnergySavingBWP.

[0084] (Variation) When a group-common SPS / CG configuration is configured for a common BWP and multiple common BWPs are configured, the SPS / CG configuration may be configured for different common BWPs for each group. For example, assume that four groups A, B, C, and D are configured as groups of terminals belonging to a specific cell, and four common BWPs BWP1 to BWP4 are configured. In this case, the SPS / CG configuration of terminals belonging to group A may be configured for BWP1, the SPS / CG configuration of terminals belonging to group B may be configured for BWP2, the SPS / CG configuration of terminals belonging to group C may be configured for BWP3, and the SPS / CG configuration of terminals belonging to group D may be configured for BWP4.

[0085] (Alt.2: If not set for common BWP) If the cell-specific / group-common SPS / CG configuration is not configured for the common BWP, the cell-specific / group-common SPS / CG configuration may be configured for the cell in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and uplinkConfigCommon.

[0086] In this case, the common BWP and cell-specific / group-common SPS / CG configuration are configured together with the cell in cell-specific parameters such as ServingCellConfigCommon. Note that in Alt.2, the BWP Id of the common BWP may be configured by EnergySavingBWP, as in Alt.1.

[0087] (effect) As described above, according to Proposal 1, even if BWP switching to a common BWP is performed, the SPS / CG configuration is configured for each cell or each terminal group, so there is no need to reconfigure the SPS / CG configuration and activate the SPS PDSCH and CG PUSCH. This makes it possible to suppress an increase in the overhead of higher layer signaling and DCI. As a result, it is possible to improve resource efficiency and increase the number of terminals that can be accommodated.

[0088] <Proposal 2> In Proposal 2, we propose examples of parameters to be introduced into the cell-specific / group-common SPS / CG configuration.

[0089] The parameters introduced in the cell-specific / group-common SPS / CG configuration are commonly applied to all terminals in the cell and may include one or more of the following parameters: These parameters are included in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and / or uplinkConfigCommon.

[0090] <SPS PDSCHのパラメータ> For cell-specific and / or group-common SPS PDSCH, parameters in the SPS-Config include, for example:

[0091] periodicity: Used to indicate the period of the SPS PDSCH. ·nrofHARQ-Processes: Used to indicate the HARQ process number. n1PUCCH-AN: Used to indicate the HARQ-ACK PUCCH resource for SPS PDSCH. · mcs-Table: Used to indicate the MCS table applied to receiving SPS PDSCH. sps-ConfigIndex: Used to indicate the index of the SPS configuration. · harq-ProcID-Offset: Used to indicate the offset of the HARQ process identifier (ID). periodicityExt: Used to indicate the periodicity of the extended SPS PDSCH. · harq-CodebookID: Used to indicate the codebook identifier (ID) of HARQ-ACK. · pdsch-AggregationFactor: Used to indicate the number of repeated PDSCH transmissions.

[0092] <CG PUSCHのパラメータ> For cell-specific and / or group-common Type 1 and / or Type 2 CG PUSCH, the parameters in ConfiguredGrantConfig include, for example:

[0093] frequencyHopping: Used to set either intra-slot frequency hopping or inter-slot frequency hopping valid. If this field is not present, frequency hopping may not be applied. cg-DMRS-Configuration: Used to indicate the DMRS configuration of the PUSCH corresponding to the configured grant. mcs-Table: Used to indicate the MSC table that the terminal uses for PUSCH without transform precoding. If this field is not present, the terminal may use the 64QAM table. mcs-TableTransformPrecoder: Used to indicate the MSC table that the terminal uses for PUSCH with transform precoding. If this field is not present, the terminal may use the 64QAM table. uci-OnPUSCH: Used to indicate information about UCI transmission using PUSCH. resourceAllocation: Used to indicate that one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switch' is set. ·rbg-Size: Used to indicate the RBG size of the PUSCH. ·nrofHARQ-Processes: Used to indicate the HARQ process number. ·repK: Used to indicate the number of repeated PUSCH transmissions. · repK-RV: Used to indicate information about the redundancy version of the repeated PUSCH transmission. periodicity: Used to indicate the periodicity of PUSCH transmission corresponding to the configured grant. phy-PriorityIndex: Used to indicate the PHY priority of the CG PUSC H at least in collision processing in the PHY layer. Note that value p0 indicates low priority, and value p1 indicates high priority. configuredGrantConfigIndex: Indicates the index of the CG configuration within the BWP. · timeDomainAllocation: Used to indicate the combination of the PUSCH mapping type, the start symbol of the PUSCH, and the number of consecutive allocated symbols. frequencyDomainAllocation: Used to indicate the frequency resource allocation of PUSCH.

[0094] Note that different parameters may be introduced for each type of Type 1 CG PUSCH and Type 2 CG PUSCH. For example, timeDomainAllocation and frequencyDomainAllocation may be introduced only for Type 1 CG PUSCH. In this case, for Type 2 CG PUSCH, TDRA (Time Domain Resource Allocation) and FDRA (Frequency Domain Resource Allocation) may be notified by activation DCI.

[0095] (effect) As described above, according to Proposal 2, when the SPS / CG configuration is set for each cell or each group of terminals, parameters that are commonly applied to all terminals in the cell can be set.

[0096] <Proposal 3> Proposal 3 proposes a method for a terminal to determine whether a DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration. Proposal 3 can be applied to SPS PDSCH and Type 2 CG PUSCH.

[0097] (Opt.1: Identifier) The terminal may determine whether the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration based on a predetermined identifier of the received DCI (for example, CS-RNTI: Configured Scheduling RNTI or a new RNTI). In this case, the DCI format of the activation DCI may be an existing DCI format (for example, 0_1 / 0_2 / 1_1 / 1_2) or a newly introduced group-common DCI format.

[0098] The DCI format includes a DCI format identification field (ID for DCI formats), a frequency domain resource assignment field (FDRA: Frequency Domain Resource Assignment), a time domain resource assignment field (TDRA: Time Domain Resource Assignment), a frequency hopping flag field, an MCS field, a new data indicator (NDI) field, a redundancy version (RV) field, a HARQ process number (HPN) field, a transmission power control (TCP) field, a padding field, a UL / SUL indicator field, etc. Here, the NDI field indicates the value of the NDI. The RV field indicates the value of the RV. The HPN field indicates the HARQ process index. The TPC field indicates a value used to control the transmission power of the PUSCH. The padding field is used to align the number of bits (size) of DCI format 1_0 and DCI format 0_0. The UL / SUL indication field is a field that indicates whether the PUSCH is allocated to the first uplink component carrier or the second component carrier when the PUSCH is scheduled using a DCI format including the UL / SUL field.

[0099] For example, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0100] (Opt.2: DCI format) A new group-common DCI format for activating cell-specific / group-common SPS / CG configuration is introduced as the DCI format for activation DCI, and a terminal may determine whether the DCI format of a received DCI is a group-common DCI format or not, depending on whether the DCI format of the received DCI is a group-common DCI format or not, and determine whether the DCI is an activation DCI for activating cell-specific / group-common SPS / CG configuration or not.

[0101] For example, if the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0102] (Opt.3:DCI field value) The terminal may determine whether the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration based on whether the field of the DCI is set to a predetermined value.

[0103] For example, if the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0104] (Opt.4: Combination) The terminal may combine some of the above Options 1 to 3 to determine whether the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration.

[0105] For example, as a combination of Opt.1 and Opt.2, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI and the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0106] Alternatively, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, or if the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0107] Furthermore, as a combination of Opt.1 and Opt.3, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI and the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0108] Alternatively, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, or if the RV field and HPN field of the received DCI are all set to '0', the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration, and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0109] Furthermore, as a combination of Opt.2 and Opt.3, if the DCI format of the received DCI is a group-common DCI format and the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration, and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0110] Alternatively, if the DCI format of the received DCI is a group-common DCI format, or if the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration, and may enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0111] (Variation) The activation DCI can indicate additional parameters. For example, as described in Proposal 2 above, if timeDomainAllocation and frequencyDomainAllocation are introduced only in Type 1 CG PUSCH, TDRA and FDRA may be notified to the terminal by the activation DCI in Type 2 CG PUSCH and / or SPS PDSCH.

[0112] The activation DCI can dynamically update parameters already set by higher layer parameters. For example, the peridicity set by the RRC parameters can be updated by the activation DCI.

[0113] (effect) As described above, according to Proposal 3, in the SPS PDSCH and Type 2 CG PUSCH, the terminal can determine whether or not the received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration.

[0114] <Suggestion 4> Proposal 4 proposes a method for a terminal to determine whether a deactivation DCI is for deactivating a cell-specific / group-common SPS / CG configuration. Proposal 4 can be applied to SPS PDSCH and Type 2 CG PUSCH.

[0115] (Opt.1: Identifier) The terminal may determine whether the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration based on a predetermined identifier of the DCI (e.g., CS-RNTI: Configured Scheduling RNTI or a new RNTI). In this case, the DCI format of the deactivation DCI may be an existing DCI format (e.g., 0_1 / 0_2 / 1_1 / 1_2) or a newly introduced group-common DCI format.

[0116] For example, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0117] (Opt.2: DCI format) A new group-common DCI format for deactivating cell-specific / group-common SPS / CG configuration is introduced as the DCI format for deactivation DCI, and the terminal may determine whether the DCI format of the received DCI is a deactivation DCI for deactivating cell-specific / group-common SPS / CG configuration depending on whether the DCI format of the received DCI is a group-common DCI format.

[0118] For example, if the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0119] (Opt.3:DCI field value) The terminal may determine whether the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration based on whether the field of the DCI is set to a predetermined value.

[0120] For example, if the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0121] (Opt.4: Combination) The terminal may combine some of the above Options 1 to 3 to determine whether the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration.

[0122] For example, as a combination of Opt.1 and Opt.2, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI and the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0123] Alternatively, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, or if the DCI format of the received DCI is a group-common DCI format, the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0124] Furthermore, as a combination of Opt.1 and Opt.3, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI and the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0125] Alternatively, if the CRC of the DCI format of the received DCI is scrambled with the CS-RNTI or a new RNTI, or if the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PU SCH.

[0126] Furthermore, as a combination of Opt.2 and Opt.3, if the DCI format of the received DCI is a group-common DCI format and the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0127] Alternatively, if the DCI format of the received DCI is a group-common DCI format, or if the RV field and HPN field of the received DCI are all set to "0", the terminal may determine that the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration, and may release (deactivate) one or more of the SPS PDSCH and / or Type 2 CG PUSCH.

[0128] (Variation) The deactivation DCI can dynamically update parameters already set by higher layer parameters. For example, the periodicity set by the RRC parameters may be updated by the deactivation DCI.

[0129] (effect) As described above, according to Proposal 4, in the SPS PDSCH and Type 2 CG PUSCH, the terminal can determine whether or not the received DCI is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration.

[0130] <Suggestion 5> In Proposal 5, we propose the number of configurable cell-specific / group-common SPS / CG configurations.

[0131] (Opt.1) The number of cell-specific / group-common SPS / CG configurations may be set independently of the number of UE-specific SPS / CG configurations.

[0132] For example, if the number of UE-specific SPS configurations is "8", the number of cell-specific / group-common SPS configurations may be "X" (X is an integer greater than or equal to 1), and the total number of SPS configurations may be "8+X".

[0133] Also, if the number of UE-specific CG configurations is "12", the number of cell-specific / group-common CG configurations may be "Y" (Y is an integer greater than or equal to 1), and the total number of CG configurations may be "12+Y".

[0134] (Opt.2) The number of cell-specific / group-common SPS / CG configurations may be set in relation to the number of UE-specific SPS / CG configurations so that the total number of SPS / CG configurations remains constant.

[0135] For example, if the total number of SPS configurations is "8", the number of UE-specific SPS configurations may be "X" (X is an integer between 1 and 7), and the number of cell-specific / group-common SPS configurations may be "8-X".

[0136] Also, if the total number of CG configurations is "12", the number of UE-specific CG configurations may be "Y" (Y is an integer greater than or equal to 1 and less than or equal to 11), and the number of cell-specific / group-common CG configurations may be "12-Y".

[0137] (effect) As described above, Proposal 5 allows the number of cell-specific / group-common SPS / CG configurations to be appropriately set.

[0138] <Suggestion 6> Proposal 6 proposes terminal behavior regarding SPS / CG configuration during BWP switching.

[0139] (Opt.1) When a base station instructs a terminal to perform BWP switching from a common BWP to a terminal-specific BWP, the terminal may not be required to receive a cell-specific / group-common SPS configuration and / or transmit a cell-specific / group-common SPS configuration.

[0140] (Opt.2) When a terminal is instructed by a base station to perform BWP switching from a terminal-specific BWP to a common BWP, the terminal may assume reception of a cell-specific / group-common SPS configuration and / or transmission of a cell-specific / group-common SPS configuration without receiving an activation DCI.

[0141] (effect) As described above, according to Proposal 6, the terminal can be operated appropriately with respect to the SPS / CG configuration during BWP switching.

[0142] <Suggestion 7> Proposal 7 proposes a method for determining frequency domain resources when switching the active BWP when CG PUSCH and / or SPS PDSCH are configured.

[0143] As described above, in order to save network energy, a method of switching BWP without deactivating and reactivating the CG PUSCH and / or SPS PDSCH is being considered.

[0144] In the current release, for active BWP switching, the RB index allocation for frequency domain resource allocation (FDRA) is determined within the BWP of the terminal as specified by the BWP indicator field included in the DCI.

[0145] However, conventionally, when BWPs are switched, the CG PUSCH and SPS PDSCH are deactivated and activation DCI is required for the new BWP, so there is no way to determine the RB index allocation for the CG PUSCH and SPS PDSCH when the active BWP is switched.

[0146] Therefore, it is clarified how to determine RB index allocation for the CG PUSCH and the SPS PDSCH when switching between active BWPs without reactivating and deactivating the CG PUSCH and / or the SPS PDSCH.

[0147] 5 is a sequence diagram illustrating an example of BWP switching according to an embodiment of the present invention. In step S11, base station 10 transmits configuration of CG PUSCH and / or SPS PDSCH to terminal 20. In the following step S12, base station 10 and terminal 20 transmit and receive CG PUSCH and / or SPS PDSCH. In the following step S13, base station 10 transmits an active BWP switching instruction by DCI to terminal 20.

[0148] In the following step S14, terminal 20 determines RB indices of FDRA for CG PUSCH and / or SPS PDSCH in the BWP after switching, and further determines resources to be used for transmitting CG PUSCH and / or receiving SPS PDSCH in the BWP after switching, based on the determined RB indices.

[0149] For example, the RB index of the FDRA for the CG PUSCH and / or SPS PDSCH in the BWP after switching may be determined within the BWP of the UE indicated by the BWP indicator field included in the DCI received in step S13.

[0150] When terminal 20 detects a PDCCH for its own device carrying the DCI, terminal 20 may first determine a UL or DL ​​BWP for a CG PUSCH or an SPS PDSCH. Then, terminal 20 may determine resource allocation within the determined BWP. Terminal 20 may start RB index allocation or numbering from the lowest RB of the UL or DL ​​BWP determined for the CG PUSCH or the SPS PDSCH.

[0151] The BWP switching may be performed by a group-common DCI or a UE-specific DCI. The CG PUSCH may be Type 1 and / or Type 2. The FDRA type for the SPS PDSCH may be Type 0 or Type 1. The FDRA type for the CP PUSCH may be Type 0, Type 1, or Type 2.

[0152] The target BWP may or may not use the same FDRA type as the previous BWP or source BWP. For example, if FDRA type 0 was used in the previous BWP, FDRA type 0 may be used in the target BWP after the BWP switch.

[0153] The FDRA type 0 for SPS PDSCH may use a bitmap that specifies the allocated RBG (Resource Block Group) (see Non-Patent Document 6). The FDRA type 1 for SPS PDSCH may use a resource indication value (RIV) that specifies the start position of the allocated virtual RB and the length of the consecutive RBs (see Non-Patent Document 6).

[0154] Note that the FDRA type 0 for CG PUSCH may use a bitmap that specifies the assigned RBGs (see Non-Patent Document 6). The FDRA type 1 for CG PUSCH may use an RIV that specifies the start position of the assigned virtual RBs and the length of consecutive RBs (see Non-Patent Document 6). The FDRA type 2 for CG PUSCH may specify up to M interlace indices (see Non-Patent Document 6).

[0155] In the following step S15, the base station 10 and the terminal 20 continue to transmit and receive the CG PUSCH and / or the SPS PDSCH in the BWP after the switch.

[0156] (effect) As described above, according to Proposal 7, communication can be continued without deactivation and reactivation of the SPS / CG configuration during BWP switching, thereby reducing signaling overhead.

[0157] (Variation) In the above, it has been shown that one of multiple options is applied to one setting. For example, which of multiple proposals / options is applied and / or which of multiple options is applied may be determined in the following manner. - Set by upper layer parameters. Set by DCI / UCI. · The UE reports it as UE capability(ies). -It is stated in the specifications. Determined based on higher layer parameter settings and reported UE capability. · Determined by a combination of two or more of the above decisions. The higher layer parameters may be RRC parameters, MAC CE (Medium Access Control Element), or a combination thereof.

[0158] Dynamic SPS PDSCH parameter update and / or CG PUSCH parameter update may be applied jointly with the configuration of cell-specific / group-common SPS / CG configuration parameters.

[0159] <Terminal Capabilities> The terminal may report the following terminal capabilities to the base station as UE capability: Note that information indicating the terminal capabilities may correspond to information defining the terminal capabilities. ·Whether to support common BWP for NW ES ·Whether to support bandwidth adaptation within BWP ·Whether to support bandwidth adaptation by BWP switching - Whether the terminal supports cell-specific / group-common SPS / CG configuration

[0160] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

[0161] According to the above-described embodiment, the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used. Furthermore, regarding the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead.

[0162] That is, in a wireless communication system, it is possible to reduce power consumption by controlling the BWP (Bandwidth Part).

[0163] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0164] <Base station 10> Fig. 6 is a diagram showing an example of the functional configuration of the base station 10 in the embodiment of the present invention. As shown in Fig. 6, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 6 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called communication units.

[0165] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0166] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to the BWP.

[0167] The control unit 140 performs control related to the BWP as described in the embodiment. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0168] <Terminal 20> Fig. 7 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Fig. 7, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 7 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations related to the embodiment of the present invention. Transmitting unit 210 and receiving unit 220 may be called communication units.

[0169] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 220 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0170] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The setting information includes, for example, information related to the BWP.

[0171] The control unit 240 performs control related to the BWP as described in the embodiment. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0172] (Hardware configuration) The block diagrams (FIGS. 6 and 7) 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 be realized by combining the single device or the multiple devices with software.

[0173] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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.

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

[0175] In the following description, the term "apparatus" can be read 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.

[0176] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0177] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as 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 140, control unit 240, etc. may be realized by the processor 1001.

[0178] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. 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 140 of the base station 10 shown in FIG. 6 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 7 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. 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 be transmitted from a network via a telecommunications line.

[0179] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by 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 storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0180] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0181] 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, or a communication module. 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, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0182] The input device 1005 is an input device (for example, 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 (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0183] Furthermore, each device such as the processor 1001 and the storage device 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.

[0184] Furthermore, base station 10 and 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, processor 1001 may be implemented using at least one of these pieces of hardware.

[0185] Fig. 9 shows an example configuration of a vehicle 2001. As shown in Fig. 9, 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.

[0186] 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.

[0187] 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).

[0188] 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.

[0189] 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 for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0190] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as a millimeter-wave radar, a LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high-definition (HD) map, autonomous vehicle (AV) map, etc.), a gyro system (e.g., an IMU (Inertial Measurement Unit), an INS (Inertial Navigation System), etc.), an AI (Artificial Intelligence) chip, and an AI processor, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0191] 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 29, which are provided in the vehicle 2001.

[0192] 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.

[0193] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 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-2028, 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.

[0194] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance 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, etc. provided in the vehicle 2001.

[0195] (Summary of the embodiment) As described above, according to the embodiments of the present invention, there is provided a terminal including: a receiving unit that receives control information for changing a bandwidth to be used, and a first setting for a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting for a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) from a base station; a communication unit that receives the SPS-PDSCH from the base station based on the first setting or transmits the CG-PUSCH to the base station based on the second setting; and a control unit that changes the bandwidth to be used based on the control information, wherein the control unit determines RB (Resource Block) indexes for frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit receives the SPS-PDSCH from the base station or transmits the CG-PUSCH to the base station in the changed bandwidth based on the RB index.

[0196] With the above configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth used. Furthermore, regarding the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead. In other words, in the wireless communication system, power consumption can be reduced by controlling the BWP (Bandwidth Part).

[0197] The control unit does not need to disable and re-enable the SPS-PDSCH or CG-PUSCH when changing the bandwidth to be used. With this configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used. Furthermore, with regard to the SPS / CG configuration during BWP switching, communication can be continued without deactivating and reactivating it, thereby reducing signaling overhead.

[0198] The control unit may start numbering the RB indexes from the RB at the lower end of the changed bandwidth. With this configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used. Furthermore, with regard to the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead.

[0199] The control unit may use the same frequency domain resource allocation method for the bandwidth before and after the change. With this configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used. Furthermore, with regard to the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead.

[0200] Furthermore, according to an embodiment of the present invention, there is provided a base station including: a transmitter unit that transmits control information for changing a bandwidth to be used, and a first setting for a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting for a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) to a terminal; a communication unit that transmits the SPS-PDSCH to the terminal based on the first setting or receives the CG-PUSCH from the terminal based on the second setting; and a controller that changes the bandwidth to be used based on the control information, wherein the controller determines RB (Resource Block) indexes for frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit transmits the SPS-PDSCH to the terminal or receives the CG-PUSCH from the terminal in the changed bandwidth based on the RB index.

[0201] With the above configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth used. Furthermore, regarding the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead. In other words, in the wireless communication system, power consumption can be reduced by controlling the BWP (Bandwidth Part).

[0202] Furthermore, according to an embodiment of the present invention, a procedure for receiving, from a base station, control information for changing a bandwidth to be used and a first setting for a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting for a Configured Grant Physical Uplink Shared Channel (CG-PUSCH); a procedure for receiving an SPS-PDSCH from the base station based on the first setting or transmitting an CG-PUSCH to the base station based on the second setting; and a procedure for changing the bandwidth to be used based on the control information. A communication method is provided in which a terminal performs a procedure of determining RB (Resource Block) indexes of frequency domain resource allocation in a changed bandwidth based on the control information, and a procedure of receiving an SPS-PDSCH from the base station or transmitting a CG-PUSCH to the base station in the changed bandwidth based on the RB indexes.

[0203] With the above configuration, the wireless communication system can achieve power saving by adaptively switching the bandwidth used. Furthermore, regarding the SPS / CG configuration during BWP switching, communication can be continued without deactivation and reactivation, thereby reducing signaling overhead. In other words, in the wireless communication system, power consumption can be reduced by controlling the BWP (Bandwidth Part).

[0204] (Supplementary explanation of the embodiment) Although the embodiments of the present invention 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 invention; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the 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 the processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams. However, such devices may be implemented using hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

[0205] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), 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), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the 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.

[0206] Each aspect / embodiment described in the present disclosure may be any of the following: 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 decimal number)), 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 The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other appropriate 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 at least one of LTE and LTE-A with 5G).

[0207] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be changed unless it is consistent. 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.

[0208] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0209] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0210] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0211] In the present disclosure, the determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0212] 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.

[0213] 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.

[0214] The 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. that 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.

[0215] Note that terms explained 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.

[0216] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0217] Furthermore, the information, parameters, etc. 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.

[0218] 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.

[0219] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0220] 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 divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within this coverage.

[0221] 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.

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

[0223] 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.

[0224] 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 an autonomous mobile object operating 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.

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

[0226] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0227] 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 in a table, database, or other data structure), ascertaining, 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. 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.

[0228] 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.

[0229] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0230] 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."

[0231] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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 in some way precede the second element.

[0232] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

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

[0234] 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.

[0235] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as 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.

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

[0237] 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.

[0238] 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.

[0239] 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.

[0240] 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 wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0241] 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.

[0242] 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.

[0243] 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.

[0244] 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 equal to or greater than 1 ms.

[0245] A resource block (RB) is a resource allocation unit in the time domain and 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 also be determined based on numerology.

[0246] 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.

[0247] 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, or the like.

[0248] 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.

[0249] 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 given BWP and numbered within that BWP.

[0250] 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.

[0251] 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."

[0252] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of 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. may be changed in various ways.

[0253] 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.

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

[0255] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, 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).

[0256] 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. [Explanation of symbols]

[0257] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (IO port)< / bwp>

Claims

1. A receiver that receives control information for changing a bandwidth to be used and a first setting related to a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting related to a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) from a base station; a communication unit that receives an SPS-PDSCH from the base station based on the first setting or transmits a CG-PUSCH to the base station based on the second setting; a control unit that changes a bandwidth to be used based on the control information; The control unit determines a resource block (RB) index of a frequency domain resource allocation in the changed bandwidth based on the control information; The communication unit receives an SPS-PDSCH from the base station or transmits a CG-PUSCH to the base station based on the RB index in the changed bandwidth.

2. The terminal according to claim 1, wherein the control unit does not disable or re-enable SPS-PDSCH or CG-PUSCH when changing the bandwidth to be used.

3. The terminal according to claim 1 , wherein the control unit starts the numbering of the RB indexes from the RB at the lower end of the changed bandwidth.

4. The terminal according to claim 1 , wherein the control unit uses the same frequency domain resource allocation scheme for the bandwidth before the change and the bandwidth after the change.

5. A transmitter that transmits control information for changing the bandwidth to be used and a first setting related to an SPS-PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) or a second setting related to a CG-PUSCH (Configured Grant Physical Uplink Shared Channel) to a terminal; a communication unit that transmits an SPS-PDSCH to the terminal based on the first setting or receives a CG-PUSCH from the terminal based on the second setting; a control unit that changes a bandwidth to be used based on the control information; The control unit determines a resource block (RB) index of a frequency domain resource allocation in the changed bandwidth based on the control information; The communication unit transmits an SPS-PDSCH to the terminal or receives a CG-PUSCH from the terminal based on the RB index in the changed bandwidth.

6. A procedure for receiving control information for changing a bandwidth to be used and a first configuration related to a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second configuration related to a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) from a base station; receiving an SPS-PDSCH from the base station based on the first configuration or transmitting a CG-PUSCH to the base station based on the second configuration; a step of changing a bandwidth to be used based on the control information; determining a resource block (RB) index of a frequency domain resource allocation in the changed bandwidth based on the control information; and a procedure of receiving an SPS-PDSCH from the base station or transmitting a CG-PUSCH to the base station in the changed bandwidth based on the RB index.

Images