Terminal, base station, and wireless communication method

Abstract

This terminal comprises: a reception unit for receiving a configuration of a semi-persistent scheduling downlink shared channel (SPS PDSCH) and / or a configuration of a configured grant physical uplink shared channel (CG PUSCH); and a control unit for controlling reception of the SPS PDSCH on the basis of the configuration of the SPS PDSCH and / or controlling transmission of the CG PUSCH on the basis of the configuration of the CG PUSCH. The configuration of the SPS PDSCH and / or the configuration of the CG PUSCH is set to be cell-specific or to be common to a group.

Description

[Technical Field]

[0001] This disclosure relates to terminals, base stations, and wireless communication methods. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has standardized the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)), and is also working on standardizing the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] In NR, CG-based PUSCH (CG PUSCH) is being considered for uplink (UL), and SPS-based PDSCH (SPS PDSCH) is being considered for downlink (DL).

[0004] 3GPP Release 16 specifies the configurations for SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and CG PUSCH (Configured Grant Physical Uplink Schered Channel) (for example, Non-Patent Document 1). In the following text, the SPS PDSCH configuration may be abbreviated as "SPS configuration," and the CG PUSCH configuration may be abbreviated as "CG configuration."

[0005] Furthermore, Release 17 examines augmented 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 considering aspects such as capacity, latency, mobility, and power efficiency. Moreover, these considerations are being continued in Release 18.

[0006] Furthermore, given the increasing importance of reducing power consumption at base stations in order to achieve carbon neutrality and the Sustainable Development Goals (SDGs), Release 18 considers ways to reduce power consumption at base stations (for example, Non-Patent Document 2). However, at present, no technology for reducing base station power consumption is specified in 3GPP (Release 18). [Prior art documents] [Non-patent literature]

[0007] [Non-Patent Document 1] 3GPP TS38.331 V17.0.0 (2022-03) [Non-Patent Document 2] “New SI: Study on network energy savings for NR”, RP-213554, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 [Overview of the project]

[0008] 3GPP (Release 18) is considering allowing base stations to instruct terminals to switch Bandwidth Parts (BWP switching) for purposes such as power saving.

[0009] However, when BWP switching is performed, there has been insufficient consideration given to how to specifically configure the SPS configuration and / or CG configuration.

[0010] One aspect of this disclosure provides a terminal, a base station, and a wireless communication method that can appropriately configure SPS configuration and / or CG configuration when BWP switching is performed.

[0011] A terminal according to one aspect of this disclosure comprises a receiving unit that receives the configuration of an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or the configuration of a CG PUSCH (Configured Grant Physical Uplink Schered Channel), and a control unit that controls the reception of the SPS PDSCH based on the SPS PDSCH configuration and / or controls the transmission of the CG PUSCH based on the CG PUSCH configuration, wherein the configuration of the SPS PDSCH and / or the CG PUSCH are set to be cell-specific or group-common.

[0012] A base station according to one aspect of the present disclosure comprises a transmitting unit that transmits a configuration for an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration for a CG PUSCH (Configured Grant Physical Uplink Schered Channel), and a control unit that controls the transmission of the SPS PDSCH based on the SPS PDSCH configuration and / or controls the reception of the CG PUSCH based on the CG PUSCH configuration, wherein the SPS PDSCH configuration and / or the CG PUSCH configuration are set to be cell-specific or group-common.

[0013] A wireless communication method according to one aspect of this disclosure involves a terminal receiving a configuration for SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration for CG PUSCH (Configured Grant Physical Uplink Schered Channel), The reception of the SPS PDSCH is controlled based on the configuration of the SPS PDSCH, and / or the transmission of the CG PUSCH is controlled based on the configuration of the CG PUSCH, and the configuration of the SPS PDSCH and / or the configuration of the CG PUSCH are set to be cell-specific or group-common. [Brief explanation of the drawing]

[0014] [Figure 1] This is a diagram illustrating a wireless communication system according to one embodiment. [Figure 2] This is a block diagram showing an example of the configuration of a base station according to one embodiment. [Figure 3] This is a block diagram showing an example of the configuration of a terminal according to one embodiment. [Figure 4] This diagram illustrates an example of BWP. [Figure 5] This is a diagram for explaining an example of a BWP. [Figure 6] This is a diagram for explaining an example of a BWP. [Figure 7] This is a diagram for explaining an example of a common BWP. [Figure 8] This is a diagram for explaining an example of Proposal 1 - Alt.1. [Figure 9] This is a diagram for explaining an example of the RRC configuration of Proposal 1 - Alt.1 - 1. [Figure 10] This is a diagram for explaining an example of the RRC configuration of Proposal 1 - Alt.1 - 2. [Figure 11] This is a diagram for explaining an example of the RRC configuration of Proposal 1 - Alt.2. [Figure 12] This is a diagram showing an example of the hardware configuration of a terminal and a base station according to an embodiment. [Figure 13] This is a diagram showing an example of the configuration of a vehicle in an embodiment of the present invention.

Embodiments for Carrying Out the Invention

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

[0016] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are appropriately used. The existing technology is, for example, existing NR, but is not limited to existing NR.

[0017] Also, in this specification, terms used in existing NR or LTE specifications such as PUSCH, PDSCH, RRC (Radio Resource Control), MAC (Media Access Control), DCI (Downlink Control Information), etc. are used. However, those represented by the channel names, protocol names, signal names, function names, etc. used in this specification may be called by other names.

[0018] <System Configuration> Figure 1 is a diagram illustrating a wireless communication system in an embodiment of the present invention. The wireless communication system in the embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Although Figure 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple base stations 10 and terminals 20.

[0019] The wireless communication system may be a wireless communication system conforming to New Radio (NR). Alternatively, the wireless communication system may be a wireless communication system conforming to a method called 5G, Beyond 5G, 5G Evolution, or 6G. For example, the wireless communication system may be a wireless communication system conforming to a method called URLLC and / or IIoT.

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

[0021] The physical resources of a radio signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. In addition, the Transmission Time Interval (TTI) in the time domain may be a slot, or the TTI may be a subframe.

[0022] At least one of the base station 10 and the terminal 20 may support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements. At least one of the base station 10 and the terminal 20 may also support carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together. At least one of the base station 10 and the terminal 20 may also support dual connectivity (DC), which enables communication between the terminal 20 and multiple base stations 10.

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

[0024] In FR1, a Sub-Carrier Spacing (SCS) of 15kHz, 30kHz, or 60kHz may be used, and a bandwidth (BW) of 5MHz to 100MHz may be used. FR2 is, for example, a higher frequency than FR1. In FR2, a 60kHz or 120kHz SCS may be used, and a bandwidth (BW) of 50MHz to 400MHz may be used. FR2 may also include a 240kHz SCS.

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

[0026] Furthermore, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM), which has a larger Sub-Carrier Spacing (SCS) than the example described above, may also be applied. Additionally, DFT-S-OFDM may be applied to both the uplink and downlink, or to either one.

[0027] In a wireless communication system, a time-division duplex (TDD) slot configuration pattern may be defined. For example, the slot configuration pattern may specify a sequence of two or more slots that include a slot for transmitting a DL signal, a slot for transmitting an UL signal, a slot containing a mixture of DL signals, UL signals, and guard symbols, and a slot in which the transmitted signal is flexibly modified.

[0028] Furthermore, in a wireless communication system, channel estimation of PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using a demodulation reference signal (DMRS) for each slot, and it is also possible to perform channel estimation of PUSCH (or PUCCH) using DMRS assigned to each of multiple slots. Such channel estimation may be called joint channel estimation, or it may be called by another name, such as cross-slot channel estimation. In this case, terminal 20 may transmit the DMRS assigned to each of the multiple slots in multiple slots so that base station 10 can perform joint channel estimation using DMRS.

[0029] Furthermore, in the wireless communication system, enhanced functionality may be added to the feedback function from the terminal 20 to the base station 10. For example, enhanced functionality may be added to the terminal's feedback regarding HARQ-ACK (Hybrid automatic repeat request Acknowledgement).

[0030] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. Base station 10 may also be called NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). Alternatively, base station 10 may be considered as a device included in the network to which terminal 20 is connected.

[0031] Base station 10 is capable of performing carrier aggregation, which involves bundling multiple cells (multiple CCs (component carriers)) together to communicate with terminal 20. Carrier aggregation uses one primary cell (PCell) and one or more secondary cells (SCell).

[0032] The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. Alternatively, the synchronization signals may be SSB. The system information is transmitted, for example, via NR-PBCH or PDSCH, and is also called broadcast information. As shown in Figure 1, the base station 10 transmits control signals or data to the terminal 20 via DL and receives control signals or data from the terminal 20 via UL. Here, signals transmitted on control channels such as PUCCH and PDCCH are called control signals, and signals transmitted on shared channels such as PUSCH and PDSCH are called data, but this is just one example of terminology.

[0033] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, 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. Terminal 20 may also be referred to as User Equipment (UE).

[0034] Terminal 20 may also notify base station 10 of terminal capability information (UE capability), which defines information about the terminal's capabilities.

[0035] Next, the configuration of the base station 10 and terminal 20 will be described. The configuration of the base station 10 and terminal 20 described below is an example of the functions related to this embodiment. The base station 10 and terminal 20 may have functions not shown. Furthermore, the function classification and / or the name of the function unit are not limited, as long as the function performs the operations related to this embodiment.

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

[0037] The transmitting unit 101 transmits the DL signal to the terminal 20. For example, the transmitting unit 101 transmits the DL signal under the control of the control unit 103.

[0038] The DL signal may include, for example, data signals for the downlink and control information (e.g., DCI). The DL signal may also include information indicating the scheduling of signal transmission by terminal 20 (e.g., UL grant). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include a reference signal.

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

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

[0041] The receiving unit 102 receives the UL signal transmitted from the terminal 20. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

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

[0043] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the reception unit 102 to the upper layer.

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

[0045] In particular, the control unit 103 determines the transmission method for PDSCH and / or the transmission method for PUSCH (reception method at base station 10), generates information regarding the determined transmission method, and transmits the information from the transmission unit 101. The control unit 103 also performs transmission control and / or reception control based on the determined transmission method for PDSCH and / or the transmission method for PUSCH. For example, the control unit 103 may receive feedback information (e.g., HARQ-ACK) generated based on the transmission method for PDSCH via the reception unit 102, and perform retransmission control based on the feedback information.

[0046] <Device Configuration> Figure 3 is a block diagram showing an example of the configuration of a terminal 20 according to this embodiment. The terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 20 communicates with, for example, a base station 10 wirelessly.

[0047] The receiving unit 201 receives DL signals transmitted from the base station 10. For example, the receiving unit 201 receives DL signals under the control of the control unit 203.

[0048] The transmitting unit 202 transmits the UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0049] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of terminal 20 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

[0050] The channels used to transmit UL signals include, for example, a data channel and a control channel. For example, the data channel includes PUSCH (Physical Uplink Shared Channel), and the control channel includes PUCCH (Physical Uplink Control Channel). For example, terminal 20 receives control information from base station 10 using PUCCH and transmits uplink data signals using PUSCH.

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

[0052] The control unit 203 controls the communication operation of the terminal 20, including the receiving process in the receiving unit 201 and the transmission process in the transmitting unit 202.

[0053] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

[0054] For example, the control unit 203 controls the transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, a HARQ-ACK, Channel State Information (CSI), or a Scheduling Request (SR). The information to be fed back to the base station 10 may be included in the UCI. The UCI is transmitted using the PUCCH resource.

[0055] In particular, the control unit 203 acquires information regarding the PDSCH transmission method (reception method at terminal 20) and / or the PUSCH transmission method, and performs transmission control and / or reception control based on the acquired information. For example, the control unit 203 may generate feedback information (e.g., HARQ-ACK) based on the PDSCH transmission method and perform control to transmit the generated feedback information via the transmission unit 202.

[0056] The channels used for transmitting DL signals and UL signals are not limited to the examples described above. For example, the channels used for transmitting DL signals and UL signals may include RACH (Random Access Channel) and PBCH (Physical Broadcast Channel). RACH may be used, for example, for transmitting DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI).

[0057] <CG PUSCH> Next, we will explain CG PUSCH. CG PUSCH is a method of performing UL transmission using PUSCH based on UL grants (which may also be called configured grants or configured UL grants) set by the upper layer. With CG PUSCH, UL resources are already allocated to terminal 20, and terminal 20 can spontaneously transmit ULs using the configured resources, so low-latency communication can be expected.

[0058] Release 16 defined two types of CG PUSCH: Type 1 and Type 2.

[0059] Activation / deactivation of Type 1 CG PUSCH depends solely on RRC-configuration and not on DCI. In Type 1 CG PUSCH, parameters used for uplink transmission (which may also be called CG parameters, CG configuration (Configured Grant Configuration) information, etc.) are set on terminal 20 using only upper-layer signaling. Specifically, the parameters for Type 1 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". That is, base station 10 uses "ConfiguredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant" to instruct terminal 20 on the parameters for uplink transmission. Terminal 20 stores the received parameters as a configuration grant.

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

[0061] The activation / deactivation of a Type 2 CG PUSCH depends on RRC-configuration and DCI. One DCI can activate only one CG PUSCH and deactivate multiple CG PUSCHs. In a Type 2 CG PUSCH, the parameters used for uplink transmission are set on the terminal 20 using upper-layer signaling. In addition, some of the parameters used for uplink transmission are notified to the terminal by DCI. Specifically, the transmission parameters of a Type 2 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config", and "activation DCI". That is, the base station 10 uses "ConfiguredGrantConfig", "pusch-Config", and "activation DCI" to instruct the terminal 20 on the parameters for uplink transmission. The terminal 20 stores the received parameters.

[0062] If terminal 20 is activated and an activation DCI is notified, it may determine that one or more configuration grants have been triggered (or activated) and may send a PUSCH without dynamic grants using resources configured at the upper layer. The activation DCI may be scrambled using a Cyclic Redundancy Check (CRC) by a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI).

[0063] Furthermore, terminal 20 may release (or deactivate, etc.) the resource (PUSCH) corresponding to the Configured Grant based on a deactivation DCI that deactivates the Configured Grant or the expiration of a predetermined timer (elapsed time). The deactivation DCI may be scrambled with a Cyclic Redundancy Check (CRC) by a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI).

[0064] <SPS PDSCH> Next, we will explain SPS PDSCH. In SPS PDSCH, the upper layer configures periodic resources for Semi-Persistent Scheduling (SPS) of the downlink (DL). In SPS PDSCH, activation / deactivation (release) of transmissions using these resources depends on activation DCI / deactivation DCI. These activation DCI / deactivation DCI may be scrambled with a Cyclic Redundancy Check (CRC) by a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI).

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

[0066] <CG PUSCHのパラメータ> For Type 1 and / or Type 2 CG PUSCH, the parameters in ConfiguredGrantConfig (hereinafter referred to as "CGC-CG parameters (group)") include, for example, the following. Note that if CGC-CG parameters are provided by both ConfiguredGrantConfig and push-Config, terminal 20 may apply the CGC-CG parameters shown in ConfiguredGrantConfig to the PUSCH transmission. Also, if there are CGC-CG parameters not provided by ConfiguredGrantConfig, terminal 20 may apply the CGC-CG parameters shown in push-Config to the PUSCH transmission.

[0067] (Example of CGC-CG parameters) • periodicity: Used to indicate the period of PUSCH transmission corresponding to the set grant. • repK: Used to indicate the number of repeated PUSCH transmissions. • repK-RV: Used to indicate information about the redundancy version of repeated PUSCH transmissions. • frequencyHopping: Used to enable either intra-slot frequency hopping or inter-slot frequency hopping. If this field does not exist, frequency hopping may not be applied. • cg-DMRS-Configuration: Used to indicate the DMRS configuration of PUSCH corresponding to the grant being configured. • mcs-Table: Used to indicate the MSC table that terminal 20 uses for PUSCH without transform precoding. If this field does not exist, terminal 20 may use the 64QAM table. • mcs-TableTransformPrecoder: Used to indicate the MSC table that terminal 20 will use for PUSCH with transform precoding. If this field does not exist, terminal 20 may use the 64QAM table. • uci-OnPUSCH: Used to indicate information regarding UCI transmission using PUSCH. • resourceAllocation: Used to indicate that one of the following will be set: 'Resource Allocation Type 0', 'Resource Allocation Type 1', or 'Dynamic Switch'. • rbg-Size: Used to indicate the RGB size of the PUSCH. • powerControlLoopToUse: Used to indicate a closed control loop applied to PUSCH transmissions. • p0-PUSCH-Alpha: Used to calculate the PUSCH transmission power. • transformPrecoder: Used to indicate whether to select transform precoding for PUSCH transmissions. • phy-PriorityIndex: Used to indicate the PHY priority of CG PUSCH in collision processing at least in the PHY layer. 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 allocated slots set by the grant period, following the time instance set by 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 periodicity. If cg-RetransmissionTimer is configured, and different configured grants on the same BWP share a HARQ process, the periodicity of configuredGrantTimer will be set to the same value for all configurations sharing the HARQ process on this BWP.

[0068] For Type 1 CG PUSCH, the parameters in rrc-ConfiguredUplinkGrant (hereinafter referred to as "rrc-CUG-CG parameters") include the following. Note that rrc-ConfiguredUplinkGrant is used to indicate grant information set in Type 1 CG PUSCH.

[0069] (Example of rrc-CUG-CG parameters) • timeDomainOffset: Used to indicate the offset associated with system frame number 0. • timeDomainAllocation: Used to indicate the mapping type of PUSCH, the start symbol of PUSCH, and the number of consecutively assigned symbols. • frequencyDomainAllocation: Used to indicate the frequency resource allocation for PUSCH. • antennaPort: Used to indicate antenna port information for PUSCH transmission. • dmrs-SeqInitialization: An identifier used for scrambling DMRS sequences 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 being used. • mcsAndTBS: Used to indicate the modulation order, target coding rate, and transport block size. • frequencyHoppingOffset: Used to indicate the frequency hopping offset. • pathlossReferenceIndex:PUSCH Used to indicate the reference signal used for path loss estimation. • push-RepTypeIndicator: Used to indicate whether terminal 20 follows the behavior for PUSCH repetition type A or PUSCH repetition type B for each Type 1 configured grant configuration. valuepusch-RepTypeA enables "PUSCH repetition type A", and valuepusch-RepTypeB enables "PUSCH repetition type B". The `frequencyHoppingPUSCH-RepTypeB:pusch-RepTypeIndicator` field is used to indicate the frequency hopping method for Type 1 CG when it is set to "pusch-RepTypeB". `Value interRepetition` enables "Inter-repetition frequency hopping", and `value interSlot` enables "Inter-slot frequency hopping". If this field is not present, frequency hopping will not be enabled for Type 1 CG.

[0070] The parameters indicated by the activation DCI for Type 2 CG PUSCH (hereinafter referred to as "DCI-CG parameters") include, for example, the following:

[0071] (Example of DCI-CG parameters) • timeDomainAllocation: Used to indicate the combination of start symbol and length and the PUSCH mapping type. • frequencyDomainAllocation: Used to indicate resource allocation in the frequency domain. • MCS index: Used to indicate the index of the MCS (Modulation and Coding Scheme). • Antenna port indication: Used to indicate an antenna port. • Precoding and number of layers indication: Used to indicate precoding and the 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 transmit power control.

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

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

[0074] The parameters indicated by activation DCI for SPS PDSCH (hereinafter referred to as "DCI-SPS parameters") include, for example, the following:

[0075] (Example of DCI-SPS parameters) • timeDomainAllocation: Used to indicate the combination of start symbol and length and the PDSCH mapping type. • frequencyDomainAllocation: Used to indicate resource allocation in the frequency domain. • MCS index: Used to indicate the index of the MCS (Modulation and Coding Scheme). • TCI state indication: Used to indicate the state of the TCI (Transmission Configuration Indicator) for PDSCH. • Antenna port indication: Used to indicate an 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 the data is scheduled on the PDSCH to the slot to which the HARQ-ACK is sent to that PDSCH.

[0076] <Other parameters> Other parameters notified from base station 10 to terminal 20 (hereinafter referred to as "other-CG / SPS parameters (group)") include, for example, the following:

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

[0078] <bpw> In NR, the maximum bandwidth per carrier is significantly larger than in LTE, for example, 100MHz at frequencies below 6GHz and 400MHz above that. To enable terminals that support smaller bandwidths to communicate using carriers operating with such wide bandwidths, a technology called Bandwidth Part (BWP) is supported, for example, in 3GPP (NR) Release 15-17. For example, BWP is supported in NR as shown in Figure 4 (see, for example, 3GPP TS38.211 V17.1.0 Sec.4.4.5).

[0079] The base station configures (provides) BWP information to the terminal. For example, the terminal is provided with serving cell parameters for each DL BWP (downlink BWP) or UL BWP (uplink BWP) within a set of DL BWPs or UL BWPs, as shown in Figures 5 and 6 (see, for example, 3GPP TS38.213 V17.1.0 Sec.12 and 3GPP TS38.331 V17.1.0 Sec.4.4.5). For example, the terminal is provided with the following parameters:

[0080] - The parameter "subcarrierSpacing" indicates the subcarrier spacing. - The parameter "CyclicPrefix" indicates a cyclic prefix. - Common RB:N BWP start =O carrier +RB start The number of consecutive RBs is N. BWP size =L RB - Indexes within a set of DL BWPs or UL BWPs based on each BWP-Id - For a DL BWP, a set of BWP-common by the parameters "BWP-DownlinkCommon" and "BWP-DownlinkDedicated", and a set of BWP-dedicated parameters, or for a UL BWP, a set of BWP-common by the parameters "BWP-UplinkCommon" and "BWP-UplinkDedicated", and a set of BWP-dedicated parameters

[0081] Note that the above common RBs and the number of consecutive RBs are the set values N provided by the parameter "offsetToCarrier" for the parameter "subcarrierSpacing". BWP size = 275 and value O carrier According to this, offset RBs start and length L RB are provided by the parameter "locationAndBandwidth" that indicates them as RIV. The RIV is determined by the following formula (see, for example, 3GPP TS38.214 V17.1.0 Sec.6.1.2.2.2).

[0082]

Equation

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

[0084] For example, the DCI format 0_1 / 0_2 / 1_1 / 1_2 is used for BWP switching. The terminal dynamically switches BWPs while performing actions such as receiving PDSCH and / or transmitting PUSCH.

[0085] The timer is used to allow the terminal to fall back to the default DL BWP, enabling false detection of DCI indicating BWP switching. The timer is set by RRC in milliseconds.

[0086] The timer starts subtracting from a value set by RRC, for example, or restarts (for example, resetting the value set by RRC and starting subtraction again) if a downlink or uplink grant is granted or if there is a configured downlink or uplink channel.

[0087] In other words, if downlink or uplink is permitted, or if there is a configured downlink or uplink channel, the timer will not expire, and the terminal will not fall back to the default DL BWP.

[0088] Otherwise, the timer subtracts the remaining time at the end of a subframe in the FR1 frequency band, or at the end of half a subframe in the FR2 frequency band. When the timer expires (for example, when the value set by RRC becomes 0), the terminal falls back to the default DL BWP.

[0089] As a result of the above operation, even if, for example, the BWP expected (configured) by the terminal differs from the BWP expected by the base station, and the terminal cannot receive the DCI indicating BWP switching, the BWP will revert to the default DL BWP when the timer expires. The terminal can then receive the DCI indicating BWP switching in the default DL BWP.

[0090] Note that the default DL BWP is the BWP set by "defaultDownlinkBWP-Id" (if set), otherwise it is the initial BWP. For example, if the default DL BWP is not set by "defaultDownlinkBWP-Id", the terminal will assume, for example, the initial BWP used for initial access as the default DL BWP.

[0091] Furthermore, in the case of TDD, since DL BWP and UL BWP are associated, BWP switching is performed on both the downlink and uplink.

[0092] <Background leading to this disclosure> 3GPP Release 16 stipulates that the SPS configuration and / or CG configuration must be configured for each terminal and each BWP. In the following text, the SPS configuration and / or CG configuration may be abbreviated as "SPS / CG configuration".

[0093] Furthermore, in Release 18, one of the considerations regarding XR is the reduction of power consumption at base stations. When a base station limits the bandwidth used to reduce power consumption, the base station instructs each terminal within the cell to perform BWP switching.

[0094] Each terminal performs BWP switching according to the base station's instructions. BWP switching is performed for purposes such as NW ES (Network Energy Saving) and traffic leveling across different bandwidths. If an SPS / CG configuration is set for each terminal, each terminal will need to reconfigure its SPS / CG configuration and activate its SPS PDSCH and CG PUSCH each time BWP switching occurs.

[0095] Therefore, frequent BWP switching leads to frequent reconfiguration of the SPS / CG configuration and activation of the SPS PDSCH and CG PUSCH, increasing the overhead of upper-layer signaling and DCI. The applicant of this application focused on the above problem and came to propose this solution.

[0096] <Proposal> This proposal suggests that the SPS / CG configuration should be set per cell or per group of terminals.

[0097] This means that even if BWP switching occurs, it may not be necessary to reconfigure the SPS / CG configuration or start the SPS PDSCH and CG PUSCH. As a result, the increase in overhead for upper-layer signaling and DCI can be suppressed.

[0098] The following describes the options (sometimes abbreviated as "Opt."), alternatives (sometimes abbreviated as "Alt."), specific examples, and / or variations for each proposal.

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

[0100] The identifier (Id) indicating the cell-specific / group-common SPS / CG configuration is notified from the base station to each terminal within the cell by higher-layer signaling parameters (higher-layer parameters) such as RRC.

[0101] Here, "group of terminals" in this application refers to each group after grouping multiple terminals belonging to a particular cell into several groups. For example, if there are 12 terminals belonging to a particular cell, from UE1 to UE12, 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 groups A, B, C, and D are each "group of terminals" in this application. Note that "terminals belonging to a particular cell" can also be said to be terminals that are communicating with the base station of that cell. In the above example, when setting a common SPS / CG configuration for group A, the base station notifies terminals UE1 to UE3 of information indicating the group-common SPS / CG configuration via activation DCI, etc.

[0102] Furthermore, the cell-specific SPS / CG configuration can be applied to SPS PDSCH, Type 1 CG PUSCH, and Type 2 CG PUSCH. The group-common SPS / CG configuration can be applied to SPS PDSCH and Type 2 CG PUSCH.

[0103] <Proposal 1> Proposal 1 proposes a relationship between cell-specific / group-common SPS / CG configuration and common BWP when a common BWP is configured for both the base station and the terminal.

[0104] First, the common BWP will be explained using Figure 7. Figure 7 shows BWP1 to BWP4 for terminals UE1 to UE4 as an example. Terminals UE1 to UE4 switch from BWP1 to BWP4 to the common BWP, as shown by arrow A in Figure 7, based on instructions from the base station or a timer. This operation reduces the communication bandwidth from the base station's perspective, thereby achieving Energy Saving (ES).

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

[0106] Multiple common BWPs may be configured. Each of these common BWPs may have a different bandwidth. Of these multiple common BWPs with different bandwidths, one may be selected depending, for example, on the NW ES mode, service, or type.

[0107] A common BWP may be set for each cell. For example, a common BWP may be set using a parameter that is set in common for all terminals within a cell.

[0108] Parameters are notified, for example, from the base station to the terminal. Parameters may be, for example, parameters of higher-layer signaling such as RRC (higher-layer parameters). Parameters may be, for example, parameters set for each cell (on a cell basis) and may be called cell-specific parameters.

[0109] Specifically, the common BWP for NW ES is configured by a new higher-layer parameter called "EnergySavingBWP" contained within "ServingCellConfigCommon" and / or "DownlinkConfigCommon" and / or "UplinkConfigCommon". "ServingCellConfigCommon", "DownlinkConfigCommon", and "UplinkConfigCommon" may also be referred to as Information Elements (IEs) or parameters.

[0110] For example, if a common BWP is set in common for DL ​​and UL, the common BWP is set in ServingCellConfigCommon. For example, if a common BWP is set in common for DL ​​and UL, higher-level parameters for the common BWP, such as EnergySavingBWP, are set in ServingCellConfigCommon.

[0111] For example, if a common BWP is configured separately for DL ​​and UL, the common BWP is configured in "DownlinkConfigCommon" and "UplinkConfigCommon" respectively. For example, if a common BWP is configured separately for DL ​​and UL, the EnergySavingBWP parameter for the DL's common BWP is configured in DownlinkConfigCommon, and the EnergySavingBWP parameter for the UL's common BWP is configured in UplinkConfigCommon.

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

[0113] (Alt.1: When set for common BWP) Figure 8 illustrates an example of Proposal 1-Alt.1. As an example, Figure 8 shows BWP1-BWP4 for terminals UE1-UE4. In Figure 8, each terminal UE1-UE4 initially has a UE-specific SPS / CG configuration. Subsequently, each terminal UE1-UE4 switches from BWP1-BWP4 to a common BWP based on higher-level layer parameters (e.g., RRC configuration), as shown by arrow B in Figure 8. At this time, by making the SPS / CG configuration of each terminal UE1-UE4 cell-specific or group-common, the need to activate the SPS PDSCH and / or CG PUSCH is eliminated. Furthermore, if a BWP switching from the common BWP to a terminal-specific BWP occurs, and then a BWP switching back to the common BWP occurs again, the need to reconfigure the SPS / CG configuration is eliminated.

[0114] (Alt.1-1) When a cell-specific / group-common SPS / CG configuration is set for a common BWP, as shown in Figure 9, the cell-specific / group-common SPS / CG configuration may be set by a parameter such as EnergySavingBWP among cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and / or uplinkConfigCommon. EnergySavingBWP may be set to the BWP ID of the common BWP. The BWP ID is, for example, an identifier that identifies the BWP. That is, the BWP ID that identifies the common BWP may be set by EnergySavingBWP.

[0115] (Alt.1-2) Alternatively, as shown in Figure 10, 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 parameters such as EnergySavingBWP, and the CG PUSCH config (configuredGrantConfig) and / or SPS config (sps-config) may be set by cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and / or uplinkConfigCommon, which include EnergySavingBWP.

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

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

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

[0119] (effect) As described above, according to Proposal 1, even if BWP switching to a common BWP occurs, the SPS / CG configuration is set for each cell or group of terminals, so it is not necessary to reconfigure the SPS / CG configuration or start the SPS PDSCH and CG PUSCH. This reduces the increase in overhead for upper-layer signaling and DCI. As a result, resource efficiency can be improved and the number of terminals that can be accommodated can be increased.

[0120] <Proposal 2> Proposal 2 proposes examples of parameters to be introduced into the cell-specific / group-common SPS / CG configuration.

[0121] The parameters introduced in the cell-specific / group-common SPS / CG configuration are common to all terminals within 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 (see Figure 9).

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

[0123] • Periodicity: Used to indicate the periodicity of 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 SPS PDSCH reception. • 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 identifier (ID) of the HARQ-ACK codebook. • pdsch-AggregationFactor: Used to indicate the number of repeated PDSCH transmissions.

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

[0125] • frequencyHopping: Used to enable either intra-slot frequency hopping or inter-slot frequency hopping. If this field does not exist, frequency hopping may not be applied. • cg-DMRS-Configuration: Used to indicate the DMRS configuration of PUSCH corresponding to the grant being configured. • mcs-Table: Used to indicate the MSC table that the terminal uses for PUSCH without transform precoding. If this field does not exist, the terminal may use the 64QAM table. • mcs-TableTransformPrecoder: Used to indicate the MSC table that the terminal will use for PUSCH with transform precoding. If this field does not exist, the terminal may use the 64QAM table. • uci-OnPUSCH: Used to indicate information regarding UCI transmission using PUSCH. • resourceAllocation: Used to indicate that one of the following will be set: 'Resource Allocation Type 0', 'Resource Allocation Type 1', or 'Dynamic Switch'. • rbg-Size: Used to indicate the RGB 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 repeated PUSCH transmissions. • periodicity: Used to indicate the period of PUSCH transmission corresponding to the set grant. • phy-PriorityIndex: Used to indicate the PHY priority of CG PUSCH in collision processing at least in the PHY layer. Value p0 indicates low priority, and value p1 indicates high priority. ·configuredGrantConfigIndex • timeDomainAllocation: Used to indicate the mapping type of PUSCH, the start symbol of PUSCH, and the number of consecutively assigned symbols. • frequencyDomainAllocation: Used to indicate the frequency resource allocation for PUSCH.

[0126] Furthermore, for Type 1 CG PUSCH and Type 2 CG PUSCH, different parameters may be introduced for each type. 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.

[0127] (effect) As described above, according to Proposal 2, when the SPS / CG configuration is set for each cell or each group of terminals, it is possible to set parameters that apply commonly to all terminals within a cell.

[0128] <Proposal 3> Proposal 3 proposes a method for determining whether a terminal is an activation DCI for activating a cell-specific / group-common SPS / CG configuration. Note that Proposal 3 may be applicable to SPS PDSCH and Type 2 CG PUSCH.

[0129] (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 DCI (e.g., 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 (e.g., 0_1 / 0_2 / 1_1 / 1_2) or a newly introduced group-common DCI format.

[0130] The DCI format includes fields such as the DCI format ID (ID for DCI formats), Frequency Domain Resource Assignment (FDRA), Time Domain Resource Assignment (TDRA), hopping flag, MCS field, NDI (New Data Indicator) field, RV (Redundancy Version) field, HPN (HARQ Process Number) field, TCP (Transmission Power Control) field, Padding field, and UL / SUL indicator field. The NDI field indicates the value of NDI. The RV field indicates the value of RV. The HPN field indicates the HARQ process index. The TCP field indicates a value used to control the transmit power of PUSCH. The Padding field is used to match the number of bits (size) of DCI format 1_0 and DCI format 0_0. The UL / SUL instruction field is a field that indicates whether the PUSCH is placed on the first uplink component carrier or the second component carrier when the PUSCH is scheduled using a DCI format that includes the UL / SUL field.

[0131] For example, if the CRC of the received DCI format is scrambled with 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 enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0132] (Opt.2: DCI format) A new group-common DCI format has been introduced for activating cell-specific / group-common SPS / CG configurations as the DCI format for activation DCIs. A terminal may determine whether a received DCI is an activation DCI for activating a cell-specific / group-common SPS / CG configuration based on whether the DCI format of the DCI is the group-common DCI format.

[0133] For example, if the DCI format of the received DCI is the 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 activate the SPS PDSCH and / or Type 2 CG PUSCH.

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

[0135] For example, if the RV and HPN fields of a 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 enable the SPS PDSCH and / or Type 2 CG PUSCH.

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

[0137] For example, if, as a combination of Opt.1 and Opt.2, the CRC of the received DCI's DCI format is scrambled with CS-RNTI or a new RNTI, and the received DCI's DCI format 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 activate the SPS PDSCH and / or Type 2 CG PUSCH.

[0138] Alternatively, if the CRC of the received DCI's DCI format is scrambled with CS-RNTI or a new RNTI, or if the received DCI's DCI format 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 activate the SPS PDSCH and / or Type 2 CG PUSCH.

[0139] Furthermore, as a combination of Opt.1 and Opt.3, if the CRC of the received DCI format is scrambled with 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 activate the SPS PDSCH and / or Type 2 CG PUSCH.

[0140] Alternatively, if the CRC of the received DCI format is scrambled with CS-RNTI or a new RNTI, or if the RV and HPN fields 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 enable the SPS PDSCH and / or Type 2 CG PUSCH.

[0141] Furthermore, as a combination of Opt.2 and Opt.3, if the DCI format of the received DCI is the 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 activate the SPS PDSCH and / or Type 2 CG PUSCH.

[0142] Alternatively, if the DCI format of the received DCI is the group-common DCI format, or if the RV and HPN fields 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 enable the SPS PDSCH and / or Type 2 CG PUSCH.

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

[0144] Activation DCI can dynamically update parameters that have already been set by higher-layer parameters. For example, the periodicity parameter set by the RRC parameter can be updated by activation DCI.

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

[0146] <Proposal 4> Proposal 4 proposes a method for determining whether a terminal is a deactivation DCI for deactivating a cell-specific / group-common SPS / CG configuration. Note that Proposal 4 may be applicable to SPS PDSCH and Type 2 CG PUSCH.

[0147] (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.

[0148] For example, if the CRC of the received DCI format is scrambled with 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 release (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

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

[0150] For example, if the DCI format of the received DCI is the 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 release (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

[0151] (Opt.3: Value of DCI field) 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 fields of the DCI are set to predetermined values.

[0152] For example, if the RV and HPN fields of a 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 (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

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

[0154] For example, if, as a combination of Opt.1 and Opt.2, the CRC of the received DCI's DCI format is scrambled with CS-RNTI or a new RNTI, and the received DCI's DCI format 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 (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

[0155] Alternatively, if the CRC of the received DCI's DCI format is scrambled with CS-RNTI or a new RNTI, or if the received DCI's DCI format 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 release (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

[0156] Furthermore, as a combination of Opt.1 and Opt.3, if the CRC of the received DCI's DCI format is scrambled with 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 the cell-specific / group-common SPS / CG configuration, and may release (disable) one or more SPS PDSCH and / or Type 2 CG PUSCH.

[0157] Alternatively, if the CRC of the received DCI format is scrambled with CS-RNTI or a new RNTI, or if the RV and HPN fields 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 release (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

[0158] Furthermore, as a combination of Opt.2 and Opt.3, if the DCI format of the received DCI is the 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 the cell-specific / group-common SPS / CG configuration, and may release (disable) one or more SPS PDSCH and / or Type 2 CG PUSCH.

[0159] Alternatively, if the DCI format of the received DCI is the group-common DCI format, or if the RV and HPN fields 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 release (disable) one or more SPS PDSCHs and / or Type 2 CG PUSCHs.

[0160] (Variations) The deactivation DCI can dynamically update parameters that have already been set by higher-level layer parameters. For example, the periodicity parameter set by the RRC parameter can be updated by the deactivation DCI.

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

[0162] <Proposal 5> Proposal 5 proposes the number of configurable cell-specific / group-common SPS / CG configurations.

[0163] (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.

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

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

[0166] (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.

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

[0168] Furthermore, if the total number of CG configurations is "12", the number of UE-specific CG configurations may be set to "Y" (where Y is an integer between 1 and 11), and the number of cell-specific / group-common CG configurations may be set to "12-Y".

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

[0170] <Proposal 6> Proposal 6 proposes how terminals should behave regarding SPS / CG configuration during BWP switching.

[0171] (Opt.1) When a terminal is instructed by the base station to perform a BWP switching from a common BWP to a terminal-specific BWP, it does not need to anticipate receiving and / or sending a cell-specific / group-common SPS configuration.

[0172] (Opt.2) When a terminal is instructed by the base station to perform a BWP switching from its own BWP to a common BWP, it may expect to receive and / or transmit a cell-specific / group-common SPS configuration without receiving an activation DCI.

[0173] (effect) In summary, according to Proposal 6, the terminal can be operated appropriately regarding the SPS / CG configuration during BWP switching.

[0174] (Variations) As shown above, for a given setting, one of several options may apply. For example, which of the multiple suggestions / options applies, and / or which of the multiple choices applies, may be determined in the following way. • Set by parameters of the higher layer. • Set by DCI / UCI • UE reports it as UE Capabilities(ies). • It is stated in the specifications. • Determined based on the settings of the upper layer parameters and the reported UE capability. • Determined by a combination of two or more of the above decisions. The parameters of the upper layer may be RRC parameters, MAC CE (Media Access Control Control Element), or a combination of these.

[0175] Dynamic SPS PDSCH parameter updates and / or CG PUSCH parameter updates can be applied in conjunction with the setting of cell-specific / group-common SPS / CG configuration parameters.

[0176] <UE capability> The terminal may report the following terminal capabilities to the base station as UE Capability. Note that the information indicating the terminal's capabilities may correspond to the information defining the terminal's capabilities. • Information that defines whether the terminal supports cell-specific / group-common SPS / CG configuration.

[0177] This concludes the explanation of this disclosure. The division of items in the above explanation is not essential to this disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other).

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

[0179] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

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

[0181] In the following explanation, the term "device" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the base station 100 and terminal 200 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

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

[0183] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control units 103 and 203 described above may be implemented by the processor 1001.

[0184] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 103 of the base station 100 and the control unit 203 of the terminal 200 may be implemented by control programs stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

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

[0186] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0187] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201 and transmitting unit 202 may be implemented by the communication device 1004. The communication device 1004 may be implemented with physically or logically separated transmitting and receiving units.

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

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

[0190] Furthermore, the base station 100 and terminal 200 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0191] (Supplement to the embodiment) While embodiments of this disclosure have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but 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 this disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 100 and terminal 200 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 100 in accordance with the embodiments of this disclosure and the software operated by the processor of the terminal 200 in accordance with the embodiments of this disclosure 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.

[0192] <Information notification, signaling> Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0193] <Applicable Systems> Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0194] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

[0196] <Input / Output Direction> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0197] <Handling of input / output information, etc.> Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

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

[0199] <Variations in form, etc.> Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0200] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

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

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

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

[0204] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0205] <Systems, Networks> The terms “system” and “network” as used in this disclosure are interchangeable.

[0206] <Parameters, channel name> Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.

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

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

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

[0210] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

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

[0212] 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 several other appropriate terms.

[0213] <Base station / mobile station> At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do 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.

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

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

[0216] Figure 13 shows an example of the configuration of vehicle 2001. As shown in Figure 13, 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 this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0217] The drive unit 2002 consists of, for example, 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, which is operated by the user.

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

[0219] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0220] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0221] Information Services Section 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

[0222] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0224] 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 external devices. For example, it can send and receive various types of information to and from external devices 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 or a mobile station.

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

[0226] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers 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 the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in 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-2029, etc., provided in the vehicle 2001.

[0227] (Summary of the embodiments) As described above, according to one aspect of the present disclosure, a terminal is provided that includes a receiving unit that receives a configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration of CG PUSCH (Configured Grant Physical Uplink Schered Channel), and a control unit that controls reception of SPS PDSCH based on the configuration of the SPS PDSCH and / or controls transmission of CG PUSCH based on the configuration of the CG PUSCH, wherein the configuration of the SPS PDSCH and / or the configuration of the CG PUSCH is set cell-specifically or group-common.

[0228] With the above configuration, there are cases where even when BWP switching is performed, it is not necessary to reconfigure the SPS / CG configuration and to activate the SPS PDSCH and CG PUSCH. As a result, an increase in the overhead of upper layer signaling and DCI can be suppressed. As a result, improvement in resource efficiency and an increase in the number of terminals that can be accommodated can be achieved.

[0229] In one embodiment, the control unit may set the configuration of the SPS PDSCH and / or the configuration of the CG PUSCH that is cell-specific or group-common when switching to a common bandwidth part. According to this embodiment, even when BWP switching to a common BWP is performed, since the SPS / CG configuration is set for each cell or for each group of terminals, it is not necessary to reconfigure the SPS / CG configuration and to activate the SPS PDSCH and CG PUSCH. As a result, an increase in the overhead of upper layer signaling and DCI can be suppressed. As a result, improvement in resource efficiency and an increase in the number of terminals that can be accommodated can be achieved.

[0230] Also, according to one aspect of the present disclosure, a transmitting unit that transmits a configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration of CG PUSCH (Configured Grant Physical Uplink Schered Channel), and a control unit that controls the transmission of SPS PDSCH based on the configuration of the SPS PDSCH and / or controls the reception of CG PUSCH based on the configuration of the CG PUSCH are provided, and the configuration of the SPS PDSCH and / or the configuration of the CG PUSCH are set cell-specifically or group-common.

[0231] With the above configuration, there may be a case where even when BWP switching is performed, it is not necessary to reconfigure the SPS / CG configuration and start the SPS PDSCH and CG PUSCH. As a result, an increase in the overhead of upper layer signaling and DCI can be suppressed. As a result, improvement in resource efficiency and an increase in the number of terminals that can be accommodated can be achieved.

[0232] In one embodiment, the control unit may notify the configuration of the SPS PDSCH and / or the configuration of the CG PUSCH that is cell-specific or group-common when the terminal switches to a common bandwidth part. According to this embodiment, even when BWP switching to a common BWP is performed, since the SPS / CG configuration is set for each cell or each group of terminals, it is not necessary to reconfigure the SPS / CG configuration and start the SPS PDSCH and CG PUSCH. As a result, an increase in the overhead of upper layer signaling and DCI can be suppressed. As a result, improvement in resource efficiency and an increase in the number of terminals that can be accommodated can be achieved.

[0233] A wireless communication method is provided in which a terminal receives a configuration for SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration for CG PUSCH (Configured Grant Physical Uplink Schered Channel), controls the reception of SPS PDSCH based on the SPS PDSCH configuration, and / or controls the transmission of CG PUSCH based on the CG PUSCH configuration, wherein the SPS PDSCH configuration and / or the CG PUSCH configuration are set to be cell-specific or group-common.

[0234] With the above configuration, even if BWP switching occurs, it may not be necessary to reconfigure the SPS / CG configuration or start the SPS PDSCH and CG PUSCH. This reduces the increase in overhead for upper-layer signaling and DCI. As a result, resource efficiency can be improved and the number of terminals that can be accommodated can be increased.

[0235] A wireless communication method is provided in which a base station transmits a configuration for an SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or a configuration for a CG PUSCH (Configured Grant Physical Uplink Schered Channel), controls the transmission of the SPS PDSCH based on the SPS PDSCH configuration, and / or controls the reception of the CG PUSCH based on the CG PUSCH configuration, wherein the SPS PDSCH configuration and / or the CG PUSCH configuration are set to be cell-specific or group-common.

[0236] With the above configuration, even if BWP switching occurs, it may not be necessary to reconfigure the SPS / CG configuration or start the SPS PDSCH and CG PUSCH. This reduces the increase in overhead for upper-layer signaling and DCI. As a result, resource efficiency can be improved and the number of terminals that can be accommodated can be increased.

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

[0238] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

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

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

[0242] <Means> In the configuration of each of the above devices, the "means" may be replaced with "section", "circuit", "device", etc.

[0243] <Open format> In the present disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0244] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be referred to as a sub-frame. A sub-frame may further be composed of one or more slots in the time domain. The sub-frame may have a fixed time length (e.g., 1 ms) independent of numerology.

[0245] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate at least one of, for example, sub-carrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

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

[0247] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots 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.

[0248] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0249] 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 mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

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

[0251] TTI may be a transmission time unit such as a channel-coded data packet (transport block), code block, codeword, etc., or may be a processing unit such as scheduling and link adaptation. Note that when TTI is given, the time interval (e.g., the number of symbols) in which a transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

[0252] Note that when one slot or one mini-slot is called TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit of scheduling. Also, the number of slots (mini-slot numbers) constituting the minimum time unit of the scheduling may be controlled.

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

[0254] Note that a long TTI (e.g., a normal TTI, subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, or a short TTI (e.g., a shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and not less than 1 ms.

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

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

[0257] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

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

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

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

[0262] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0263] <Maximum transmission power> The term "maximum transmit power" as used in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0266] This disclosure is useful for wireless communication systems. [Explanation of symbols]

[0267] 10 base station 20 devices 101,202 Transmitter 102, 201 Receiver 103,203 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device< / bpw>

Claims

1. A receiving unit that receives the configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or the configuration of CG PUSCH (Configured Grant Physical Uplink Schered Channel), A control unit that controls the reception of the SPS PDSCH based on the configuration of the SPS PDSCH and / or controls the transmission of the CG PUSCH based on the configuration of the CG PUSCH, It is equipped with, The configuration of the SPS PDSCH and / or the CG PUSCH is set to be cell-specific or group-common. When switching to a common bandwidth portion, the control unit sets the SPS PDSCH configuration and / or the CG PUSCH configuration to be cell-specific or group-common. Terminal.

2. A transmitting unit that transmits the configuration of SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or the configuration of CG PUSCH (Configured Grant Physical Uplink Schered Channel), A control unit that controls the transmission of the SPS PDSCH based on the configuration of the SPS PDSCH and / or controls the reception of the CG PUSCH based on the configuration of the CG PUSCH, It is equipped with, The configuration of the SPS PDSCH and / or the CG PUSCH is set to be cell-specific or group-common. The control unit notifies the cell-specific or group-common SPS PDSCH configuration and / or CG PUSCH configuration when the terminal switches to a common bandwidth portion. Base station.

3. The device, Receive the configuration for SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or CG PUSCH (Configured Grant Physical Uplink Schered Channel), Based on the configuration of the SPS PDSCH, the reception of the SPS PDSCH is controlled, and / or based on the configuration of the CG PUSCH, the transmission of the CG PUSCH is controlled. The configuration of the SPS PDSCH and / or the CG PUSCH is set to be cell-specific or group-common. When switching to a common bandwidth portion, set the SPS PDSCH configuration and / or CG PUSCH configuration to be cell-specific or group-common. Wireless communication method.

4. The base station, Send the configuration for SPS PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and / or the configuration for CG PUSCH (Configured Grant Physical Uplink Schered Channel), The system controls the transmission of the SPS PDSCH based on the configuration of the SPS PDSCH, and / or controls the reception of the CG PUSCH based on the configuration of the CG PUSCH. The configuration of the SPS PDSCH and / or the CG PUSCH is set to be cell-specific or group-common. When a terminal switches to a common bandwidth portion, it notifies the cell-specific or group-common SPS PDSCH configuration and / or CG PUSCH configuration. Wireless communication method.

Images