WO2024106418A1 - Terminal, station de base et procédé de communication - Google Patents

Terminal, station de base et procédé de communication Download PDF

Info

Publication number
WO2024106418A1
WO2024106418A1 PCT/JP2023/040885 JP2023040885W WO2024106418A1 WO 2024106418 A1 WO2024106418 A1 WO 2024106418A1 JP 2023040885 W JP2023040885 W JP 2023040885W WO 2024106418 A1 WO2024106418 A1 WO 2024106418A1
Authority
WO
WIPO (PCT)
Prior art keywords
sps
pusch
terminal
base station
bwp
Prior art date
Application number
PCT/JP2023/040885
Other languages
English (en)
Japanese (ja)
Inventor
優元 ▲高▼橋
聡 永田
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Publication of WO2024106418A1 publication Critical patent/WO2024106418A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows

Definitions

  • the present invention relates to a terminal, a base station, and a communication method in a wireless communication system.
  • Non-Patent Document 1 For NR (New Radio) (also known as “5G”), the successor system to LTE (Long Term Evolution), technologies are being considered that meet the requirements of a large-capacity system, high data transmission speed, low latency, simultaneous connection of many terminals, low cost, and low power consumption (for example, Non-Patent Document 1).
  • a PUSCH (CG PUSCH) based on CG (Configured Grant) is being considered for the uplink (UL), and a PDSCH (SPS PDSCH) based on SPS (Semi-Persistent Scheduling) is being considered for the downlink (DL).
  • CG PUSCH based on CG
  • SPS PDSCH based on SPS (Semi-Persistent Scheduling) is being considered for the downlink (DL).
  • 3GPP (registered trademark) Release 16 specifies the configuration of the SPS-PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) and the CG-PUSCH (Configured Grant Physical Uplink Shared Channel) (for example, Non-Patent Document 1).
  • SPS-PDSCH Semi-Persistent Scheduling Downlink Shared Channel
  • CG-PUSCH Configured Grant Physical Uplink Shared Channel
  • 3GPP Release 17 also considers Extended Reality (XR), including virtual reality (VR) and mixed reality (MX), and considers XR scenarios, requirements, key performance indicators (KPIs) and evaluation methods.
  • XR Extended Reality
  • VR virtual reality
  • MX mixed reality
  • KPIs key performance indicators
  • the target requirements for XR are to take into account capacity, latency (delay), mobility and power saving aspects. Furthermore, the above considerations are continuing in Release 18.
  • 3GPP Release 18 is considering ways to reduce the power consumption of base stations (for example, Non-Patent Document 2). At present, however, 3GPP has not specified any technology to reduce the power consumption of base stations.
  • 3GPP TS 38.300 V17.2.0 (2022-09) "New SI: Study on network energy savings for NR", RP-213554, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 3GPP TS 38.211 V17.3.0 (2022-09) 3GPP TS 38.213 V17.3.0 (2022-09) 3GPP TS 38.331 V17.2.0 (2022-09) 3GPP TS 38.214 V17.3.0 (2022-09)
  • the present invention has been made in consideration of the above points, and aims to reduce power consumption in wireless communication systems by controlling the BWP (Bandwidth Part).
  • a terminal includes a receiver that receives control information for changing the bandwidth to be used and a first setting for an SPS-PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) or a second setting for a CG-PUSCH (Configured Grant Physical Uplink Shared Channel) from a base station, a communication unit that receives an SPS-PDSCH from the base station based on the first setting or transmits a CG-PUSCH to the base station based on the second setting, and a control unit that changes the bandwidth to be used based on the control information, the control unit determining a resource block (RB) index for frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit receiving an SPS-PDSCH from the base station or transmitting a CG-PUSCH to the base station based on the RB index in the changed bandwidth.
  • SPS-PDSCH Semi-Persistent Scheduling Downlink Shared Channel
  • CG-PUSCH Configured Grant Physical Uplink Shared Channel
  • the disclosed technology makes it possible to reduce power consumption in a wireless communication system by controlling the BWP (Bandwidth Part).
  • FIG. 1 is a diagram showing a configuration example (1) of a wireless communication system.
  • FIG. 1 is a diagram showing a configuration example (2) of a wireless communication system.
  • FIG. 1 is a diagram for explaining an example (1) of a common BWP according to an embodiment of the present invention.
  • FIG. 13 is a diagram for explaining an example (2) of a common BWP according to an embodiment of the present invention.
  • FIG. 11 is a sequence diagram for explaining an example of BWP switching according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to an embodiment of the present invention.
  • 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention.
  • FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an
  • LTE Long Term Evolution
  • NR NR
  • SS Synchronization signal
  • PSS Primary SS
  • SSS Secondary SS
  • PBCH Physical broadcast channel
  • PRACH Physical random access channel
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Shared Channel
  • NR corresponds to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc.
  • NR- even if a signal is used in NR, it is not necessarily specified as "NR-".
  • the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or another method (e.g., Flexible Duplex, etc.).
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • another method e.g., Flexible Duplex, etc.
  • radio parameters and the like when radio parameters and the like are “configured,” this may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are configured.
  • FIG. 1 is a diagram showing a configuration example (1) of 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.
  • FIG. 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple of each.
  • the base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20.
  • the physical resources of a wireless signal are defined in the time domain and the frequency domain, where the time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks.
  • the base station 10 transmits a synchronization signal and system information to the terminal 20.
  • the synchronization signal is, for example, NR-PSS and NR-SSS.
  • the system information is, for example, transmitted by NR-PBCH and is also called broadcast information.
  • the synchronization signal and system information may be called SSB (SS/PBCH block). As shown in FIG.
  • the base station 10 transmits a control signal or data to the terminal 20 in DL (Downlink) and receives a control signal or data from the terminal 20 in UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. In addition, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).
  • SCell Secondary Cell
  • PCell Primary Cell
  • CA Carrier Aggregation
  • the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10
  • the terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or a communication module for M2M (Machine-to-Machine). As shown in FIG. 1, the terminal 20 receives control signals or data from the base station 10 in DL and transmits control signals or data to the base station 10 in UL, thereby utilizing various communication services provided by the wireless communication system. The terminal 20 also receives various reference signals transmitted from the base station 10, and performs measurement of the propagation path quality based on the reception results of the reference signals.
  • M2M Machine-to-Machine
  • the terminal 20 is capable of performing carrier aggregation, which bundles multiple cells (multiple CCs (Component Carriers)) together to communicate with the base station 10.
  • carrier aggregation one PCell (Primary cell) and one or more SCells (Secondary cells) are used.
  • a PUCCH-SCell having a PUCCH may also be used.
  • FIG. 2 is a diagram showing an example (2) of a wireless communication system in an embodiment of the present invention.
  • FIG. 2 shows an example of the configuration of a wireless communication system when DC (Dual connectivity) is implemented.
  • a base station 10A serving as a MN (Master Node) and a base station 10B serving as a SN (Secondary Node) are provided.
  • Base station 10A and base station 10B are each connected to a core network.
  • Terminal 20 can communicate with both base station 10A and base station 10B.
  • the cell group provided by base station 10A which is an MN
  • the MCG Master Cell Group
  • the cell group provided by base station 10B which is an SN
  • the SCG Secondary Cell Group
  • the MCG is composed of one PCell and one or more SCells
  • the SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.
  • the processing operations in this embodiment may be performed in the system configuration shown in FIG. 1, in the system configuration shown in FIG. 2, or in a system configuration other than these.
  • CG PUSCH is a method of performing UL transmission using PUSCH based on an UL grant (which may be called, for example, a configured grant or a configured UL grant) configured by a higher layer.
  • UL grant which may be called, for example, a configured grant or a configured UL grant
  • UL resources are already assigned to terminal 20, and terminal 20 can perform UL transmission autonomously using the configured resources, so that realization of low-latency communication can be expected.
  • Type 1 CG PUSCH parameters used for uplink transmission (which may be called CG parameters, CG configuration (Configured Grant Configuration) information, etc.) are configured in the terminal 20 using only higher layer signaling. Specifically, parameters of Type 1 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config” and "rrc-ConfiguredUplinkGrant". That is, the base station 10 instructs the terminal 20 of the parameters for uplink transmission using "ConfiguredGrantConfig", “pusch-Config” and “rrc-ConfiguredUplinkGrant". The terminal 20 stores the received parameters as a configuration grant.
  • the terminal 20 may determine that one or more configuration grants have been triggered (or activated), and may transmit PUSCHs without a dynamic grant using the configured resources (which may also be called CG resources, transmission opportunities, etc.).
  • Type 2 CG PUSCH Activation/deactivation of Type 2 CG PUSCH depends on RRC configuration and DCI.
  • One DCI can activate only one CG PUSCH and can deactivate multiple CG PUSCHs.
  • parameters used for uplink transmission are configured in the terminal 20 using higher layer signaling. Some of the parameters used for uplink transmission are notified to the terminal by DCI.
  • the transmission parameters of Type 2 CG PUSCH are provided by "ConfiguredGrantConfig", "pusch-Config” and "activation DCI”. That is, the base station 10 instructs the terminal 20 of the parameters for uplink transmission using "ConfiguredGrantConfig", "pusch-Config” and "activation DCI".
  • the terminal 20 stores the received parameters.
  • the terminal 20 may determine that one or more configuration grants have been triggered (or activated) and transmit a PUSCH without a dynamic grant, using resources configured in a higher layer.
  • the activation DCI may be CRC (Cyclic Redundancy Check) scrambled by a specified identifier (e.g., CS-RNTI: Configured Scheduling RNTI).
  • the terminal 20 may release (which may be called release, deactivate, etc.) the resources (PUSCH) corresponding to the Configured Grant based on a deactivation DCI that deactivates the Configured Grant or the expiration of a specified timer (the passage of a specified time).
  • the deactivation DCI may be CRC (Cyclic Redundancy Check) scrambled using a specified identifier (e.g., CS-RNTI: Configured Scheduling RNTI).
  • SPS PDSCH ⁇ SPS PDSCH> Next, the SPS PDSCH will be described.
  • periodic resources for downlink (DL) Semi-Persistent Scheduling (SPS) are configured by higher layers.
  • Activation/deactivation (release) of transmission using the resources in the SPS PDSCH depends on activation DCI/deactivation DCI.
  • the activation DCI/deactivation DCI may be CRC (Cyclic Redundancy Check) scrambled by a predetermined identifier (e.g., CS-RNTI: Configured Scheduling RNTI).
  • parameters used for downlink transmission (which may be called SPS parameters, SPS configuration (Semi-Persistent Scheduling configuration) information, etc.) are configured in the terminal 20 using higher layer signaling.
  • SPS parameters which may be called SPS parameters, SPS configuration (Semi-Persistent Scheduling configuration) information, etc.
  • DCI DCI-Config
  • activation DCI the transmission parameters of the SPS PDSCH are provided by "sps-Config" and "activation DCI”. That is, the base station 10 instructs the terminal 20 of the downlink transmission parameters using "sps-Config" and "activation DCI”.
  • the terminal 20 stores the received parameters.
  • CGC-CG parameters Parameters in ConfiguredGrantConfig for Type 1 and/or Type 2 CG PUSCH (hereinafter referred to as "CGC-CG parameters (group)") include, for example, the following. Note that when CGC-CG parameters are provided by both ConfiguredGrantConfig and pusch-Config, the terminal 20 may apply the CGC-CG parameters indicated in ConfiguredGrantConfig to PUSCH transmission. Also, when there are CGC-CG parameters not provided by ConfiguredGrantConfig, the terminal 20 may apply the CGC-CG parameters indicated in pusch-Config to PUSCH transmission.
  • periodicity Used to indicate the periodicity of PUSCH transmission corresponding to the configured grant.
  • repK Used to indicate the number of repeated PUSCH transmissions.
  • repK-RV Used to indicate information about the redundancy version of the repeated PUSCH transmission.
  • frequencyHopping Used to effectively set either intra-slot or inter-slot frequency hopping. If the field is not present, frequency hopping may not be applied.
  • cg-DMRS-Configuration Used to indicate the DMRS configuration of the PUSCH corresponding to the grant being configured.
  • mcs-Table Used to indicate the MSC table that the terminal 20 uses for PUSCH without transform precoding. If this field is not present, the terminal 20 may use the 64QAM table.
  • mcs-TableTransformPrecoder Used to indicate the MSC table that the terminal 20 uses for PUSCH with transform precoding. If this field is not present, the terminal 20 may use the 64QAM table.
  • uci-OnPUSCH Used to indicate information regarding transmission of UCI using PUSCH.
  • resourceAllocation Used to indicate that one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switch' is to be configured.
  • rbg-Size Used to indicate the RBG size of the PUSCH.
  • powerControlLoopToUse Used to indicate the closed control loop to apply to the PUSCH transmission.
  • p0-PUSCH-Alpha Used to calculate the PUSCH transmit power.
  • transformPrecoder Used to indicate whether to select transform precoding for PUSCH transmission.
  • phy-PriorityIndex Used to indicate the PHY priority of the CG PUSCH at least in collision processing of the PHY layer, where 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 in the grant period following the time instance specified 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-RetransmissonTimer is configured, and HARQ processes are shared between different configured grants on the same BWP, the periodicity of configuredGrantTimer is set to the same value as the configurations sharing the HARQ processes on this BWP.
  • rrc-ConfiguredUplinkGrant for Type 1 CG PUSCH (hereinafter referred to as "rrc-CUG-CG parameters (group)") are as follows. Note that rrc-ConfiguredUplinkGrant is used to indicate information about the grant configured in Type 1 CG PUSCH.
  • timeDomainOffset used to indicate an offset relative to system frame number 0.
  • timeDomainAllocation Used to indicate a combination of a PUSCH mapping type, a start symbol of the PUSCH, and the number of consecutive symbols to be allocated.
  • frequencyDomainAllocation Used to indicate frequency resource allocation for PUSCH.
  • antennaPort Used to indicate antenna port information for PUSCH transmission.
  • dmrs-SeqInitialization An identifier used for scrambling the DMRS sequence for PUSCH transmission.
  • precodingAndNumberOfLayers Used to indicate the precoding and number of layers for PUSCH transmission.
  • srs-ResourceIndicator Used to indicate the SRS (Sounding Reference Signal) resource to be used.
  • mcsAndTBS Used to indicate the modulation order, the target coding rate, and the size of the transport block.
  • frequencyHoppingOffset used to indicate the frequency hopping offset.
  • pathlossReferenceIndex Used to indicate the reference signal used for PUSCH pathloss estimation.
  • pusch-RepTypeIndicator Used to indicate whether the terminal 20 follows an operation for PUSCH repetition type A or an operation for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables "PUSCH repetition type A", and the value pusch-RepTypeB enables "PUSCH repetition type B".
  • frequencyHoppingPUSCH-RepTypeB Used to indicate the frequency hopping method for Type 1 CG if pusch-RepTypeIndicator is set to "pusch-RepTypeB". Value interRepetition enables "Inter-repetition frequency hopping" and value interSlot enables "Inter-slot frequency hopping”. Note that if this field is not present, frequency hopping is not enabled for Type 1 CG.
  • DCI-CG parameters (group) The parameters specified by the activation DCI for Type 2 CG PUSCH (hereinafter referred to as "DCI-CG parameters (group)") are, for example:
  • timeDomainAllocation Used to indicate a combination of starting symbol and length and a PUSCH mapping type.
  • frequencyDomainAllocation used to indicate frequency domain resource allocation.
  • MCS index Used to indicate the MCS (Modulation and Coding Scheme) index.
  • ⁇ antenna port indication Used to indicate an antenna port.
  • precoding and number of layers indication Used to indicate precoding and number of layers.
  • SRS resource indicator Used to indicate resources for SRS (Sounding Reference Signal).
  • power control related parameter indication used to indicate parameters related to transmission power control.
  • SPS-Config for the SPS PDSCH (hereinafter referred to as "SC-SPS parameter(s)")
  • SC-SPS parameter(s) Parameters in the SPS-Config for the SPS PDSCH
  • n1PUCCH-AN Used to indicate HARQ-ACK (Hybrid automatic repeat request Acknowledgement) PUCCH resource for SPS PDSCH.
  • mcs-Table Used to indicate the MCS table applied to receive the SPS PDSCH.
  • pdsch-AggregationFactor Used to indicate the number of repeated PDSCH transmissions.
  • DCI-SPS parameter(s) The parameters indicated by the activation DCI for the SPS PDSCH (hereinafter referred to as "DCI-SPS parameter(s)") are, for example, as follows:
  • timeDomainAllocation Used to indicate the starting symbol and length combination and PDSCH mapping type.
  • frequencyDomainAllocation used to indicate frequency domain resource allocation.
  • MCS index Used to indicate the MCS (Modulation and Coding Scheme) index.
  • TCI state indication Used to indicate the status of the TCI (Transmission Configuration Indicator) for the 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 data is scheduled on the PDSCH to the slot where the HARQ-ACK for that PDSCH is sent.
  • 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).
  • ⁇ BWP> the maximum bandwidth per carrier is, for example, 100 MHz at frequencies below 6 GHz, and 400 MHz at frequencies above 6 GHz, which is significantly larger than that of LTE.
  • 3GPP (NR) Release 15-17 supports a technology called Bandwidth Part (BWP).
  • BWP Bandwidth Part
  • NR supports BWP (see, for example, Sec. 4.4.5 of Non-Patent Document 3).
  • the base station 10 sets (provides) information about the BWP to the terminal 20.
  • the terminal 20 is provided with the parameters of the serving cell for each DL BWP (downlink BWP) or UL BWP (uplink BWP) in one set of DL BWPs or UL BWPs (see, for example, Sec. 12 of Non-Patent Document 4 and Sec. 4.4.5 of Non-Patent Document 5).
  • the following parameters are provided to the terminal 20.
  • the RIV is determined by the following formula (see, for example, Sec. 6.1.2.2.2 in Non-Patent Document 6):
  • BWP switching In 3GPP Releases 15-17, a technique called BWP switching for switching BWPs is supported.
  • the terminal 20 is instructed to perform BWP switching by a timer such as Radio Resource Control (RRC), Medium Access Control - Control Element (MAC-CE), Downlink Control Information (DCI), or an inactivity timer.
  • RRC Radio Resource Control
  • MAC-CE Medium Access Control - Control Element
  • DCI Downlink Control Information
  • DCI formats 0_1/0_2/1_1/1_2 are used for BWP switching.
  • the timer is used by the terminal 20 to fall back to the default DL BWP to allow false detection of a DCI indicating a BWP switch.
  • the timer is set by the RRC in milliseconds.
  • the timer starts decrementing from the value configured by RRC, for example, or restarts (e.g., resets the value configured by RRC and starts decrementing) when there is a downlink or uplink grant, or when there is a configured downlink or uplink channel.
  • the timer does not expire and the terminal 20 does not fall back the BWP to the default DL BWP.
  • the timer decrements the remaining period of the timer, for example, at the end of the subframe in the case of the Frequency Range (FR) 1 frequency band, or at the end of half of the subframe in the case of the FR2 frequency band.
  • the timer expires (for example, when the value set by the RRC becomes 0)
  • the terminal 20 falls back to the default DL BWP.
  • the BWP assumed (set) by the terminal 20 differs from the BWP assumed by the base station 10 and the terminal 20 cannot receive a DCI indicating a BWP switch
  • the BWP will return to the default DL BWP when the timer expires.
  • the terminal 20 can receive a DCI indicating a BWP switch in the default DL BWP.
  • the default DL BWP is the BWP set by "defaultDownlinkBWP-Id" (if set), and otherwise the initial BWP. For example, if a default DL BWP is not set by "defaultDownlinkBWP-Id", the terminal 20 assumes that the initial BWP used for initial access is the default DL BWP.
  • the DL BWP and UL BWP are associated, so BWP switching is performed on both the downlink and uplink.
  • 3GPP Release 16 specifies that the SPS configuration and/or CG configuration are set for each terminal and for each BWP.
  • the SPS configuration and/or CG configuration may be abbreviated to "SPS/CG configuration”.
  • 3GPP Release 18 also considers power saving for base stations as one of the items under consideration for XR. When a base station restricts the bandwidth used to save power, the base station will instruct BWP switching for each terminal within the cell.
  • Each terminal performs BWP switching according to instructions from the base station. BWP switching is performed for network energy saving (NW ES) and traffic equalization of each band. If the SPS/CG configuration is set for each terminal, each time BWP switching is performed, it is necessary for each terminal to reconfigure the SPS/CG configuration and activate the SPS PDSCH and CG PUSCH.
  • NW ES network energy saving
  • an SPS/CG configuration that is set uniquely for each cell may be referred to as a "cell-specific SPS/CG configuration”
  • an SPS/CG configuration that is set for each group of terminals may be referred to as a "group-common SPS/CG configuration”.
  • cell-specific SPS/CG configuration and/or group-common SPS/CG configuration may be referred to as a "cell-specific/group-common SPS/CG configuration”.
  • a "group of terminals” in this application refers to each group after multiple terminals belonging to a specific cell are grouped into several groups. For example, if there are 12 terminals, UE1 to UE12, that belong to a specific cell, and terminals UE1 to UE3 are group A, terminals UE4 to UE6 are group B, terminals UE7 to UE9 are group C, and terminals UE10 to UE12 are group D, then each of groups A, B, C, and D is a "group of terminals" in this application.
  • a "terminal belonging to a specific cell” can also be said to be a terminal that is communicating with the base station of that cell.
  • the base station notifies terminals UE1 to UE3 of information indicating the group-common SPS/CG configuration by means of activation DCI or the like.
  • the cell-specific SPS/CG configuration can be applied to any of the SPS PDSCH, Type 1 CG PU SCH, and Type 2 CG PUSCH.
  • the group-common SPS/CG configuration can be applied to the SPS PDSCH and Type 2 CG PUSCH.
  • Proposal 1 when a common BWP is configured in a base station and a terminal, the relationship between the cell-specific/group-common SPS/CG configuration and the common BWP is proposed.
  • Figure 3 shows BWP1 to BWP4 of 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 3. This action narrows the communication bandwidth from the base station's perspective, achieving Energy Saving (ES).
  • ES Energy Saving
  • a common BWP may be considered as a BWP that aligns the frequencies of the BWPs of multiple terminals and sets the bandwidth of the BWPs of multiple terminals to the same value.
  • a common BWP may also be called an NW ES BWP or ES BWP. NW is an abbreviation for network.
  • Multiple common BWPs may be set.
  • the multiple common BWPs may each have a different bandwidth.
  • One of the multiple common BWPs with different bandwidths may be selected depending on, for example, the mode, service, or type of the NW ES.
  • the common BWP may be set for each cell.
  • the common BWP may be set using parameters that are set commonly to all terminals in the cell.
  • the parameters are notified, for example, from the base station to the terminal.
  • the parameters may be, for example, parameters of higher layer signaling such as RRC (higher layer parameters).
  • the parameters are, for example, parameters that are set for each cell (cell unit) and may be referred to as cell-specific parameters.
  • the common BWP for NW ES is configured by new higher layer parameters such as "EnergySavingBWP" included in “ServingCellConfigCommon” and/or “DownlinkConfigCommon” and/or "UplinkConfigCommon".
  • "ServingCellConfigCommon”, “DownlinkConfigCommon” and “UplinkConfigCommon” may be referred to as Information Elements (IEs) or may be referred to as parameters.
  • IEs Information Elements
  • the common BWP is configured in "DownlinkConfigCommon" and "UplinkConfigCommon".
  • the EnergySavingBWP parameter for the common BWP in DL is configured in DownlinkConfigCommon
  • the EnergySavingBWP parameter for the common BWP in UL is configured in UplinkConfigCommon.
  • cell-specific/group-common SPS/CG configuration may be configured for (Alt.1) the common BWP or may not be configured for (Alt.2) the common BWP.
  • FIG. 4 is a diagram for explaining an example of Proposal 1-Alt.1.
  • FIG. 4 shows BWP1 to BWP4 of terminals UE1 to UE4 as an example. Also, in FIG. 4, each terminal UE1 to UE4 initially sets UE specific SPS/CG configuration. After that, each terminal UE1 to UE4 switches from BWP1 to BWP4 to a common BWP as shown by arrow B in FIG. 4 based on higher layer parameters (e.g., RRC configuration).
  • higher layer parameters e.g., RRC configuration
  • the cell-specific/group-common SPS/CG configuration may be configured by a parameter such as EnergySavingBWP in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and/or uplinkConfigCommon.
  • the BWP Id of the common BWP may be configured in the EnergySavingBWP.
  • the BWP Id is, for example, an identifier for identifying the BWP. That is, the BWP Id for identifying the common BWP may be configured by the EnergySavingBWP.
  • 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 may be set by a parameter such as EnergySavingBWP, and the CG PUSCH config (configuredGrantConfig) and/or SPS config (sps-config) may be set in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon and/or uplinkConfigCommon, including EnergySavingBWP.
  • the SPS/CG configuration may be set for each group for different common BWPs. For example, assume that 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.
  • the SPS/CG configuration of terminals belonging to group A may be set for BWP1
  • the SPS/CG configuration of terminals belonging to group B may be set for BWP2
  • the SPS/CG configuration of terminals belonging to group C may be set for BWP3
  • the SPS/CG configuration of terminals belonging to group D may be set for BWP4.
  • the cell-specific/group-common SPS/CG configuration may be configured for the cell in cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon, and uplinkConfigCommon.
  • the common BWP and cell-specific/group-common SPS/CG configuration are configured together with the cell in cell-specific parameters such as ServingCellConfigCommon.
  • the BWP Id of the common BWP may be set by the EnergySavingBWP.
  • the parameters introduced in the cell-specific/group-common SPS/CG configuration are commonly applied to all terminals in the cell and may include one or more of the following parameters. These parameters are included in the cell-specific parameters such as ServingCellConfigCommon, downlinkConfigCommon and/or uplinkConfigCommon.
  • SPS PDSCH parameters Parameters in the SPS-Config for cell-specific and/or group-common SPS PDSCH include, for example:
  • Periodicity Used to indicate the period of the SPS PDSCH.
  • nrofHARQ-Processes Used to indicate the HARQ process number.
  • n1PUCCH-AN Used to indicate HARQ-ACK PUCCH resource for SPS PDSCH.
  • mcs-Table Used to indicate the MCS table applied to receive the SPS PDSCH.
  • sps-ConfigIndex Used to indicate the index of the SPS configuration.
  • harq-ProcID-Offset Used to indicate the offset of the HARQ process identifier (ID).
  • periodicityExt Used to indicate the periodicity of the Extended SPS PDSCH.
  • harq-CodebookID Used to indicate the codebook identifier (ID) for HARQ-ACK.
  • pdsch-AggregationFactor Used to indicate the number of repeated PDSCH transmissions.
  • ⁇ CG PUSCH parameters Parameters in ConfiguredGrantConfig for cell-specific and/or group-common Type 1 and/or Type 2 CG PUSCH include, for example:
  • frequencyHopping Used to effectively set either intra-slot or inter-slot frequency hopping. If the field is not present, no frequency hopping may be applied.
  • cg-DMRS-Configuration Used to indicate the DMRS configuration of the 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 is not present, the terminal may use the 64QAM table.
  • mcs-TableTransformPrecoder Used to indicate the MSC table that the terminal uses for PUSCH with transform precoding. If this field is not present, the terminal may use the 64QAM table.
  • uci-OnPUSCH Used to indicate information regarding transmission of UCI using PUSCH.
  • resourceAllocation Used to indicate that one of 'resource allocation type 0', 'resource allocation type 1', and 'dynamic switch' is to be configured.
  • rbg-Size Used to indicate the RBG size of the PUSCH.
  • nrofHARQ-Processes Used to indicate the HARQ process number.
  • repK Used to indicate the number of repeated PUSCH transmissions.
  • repK-RV Used to indicate information about the redundancy version of the repeated PUSCH transmission.
  • periodicity Used to indicate the periodicity of PUSCH transmission corresponding to the configured grant.
  • phy-PriorityIndex Used to indicate the PHY priority of the CG PUSC H at least in collision processing of the PHY layer.
  • configuredGrantConfigIndex Indicates the index of the CG configuration within the BWP.
  • timeDomainAllocation Used to indicate a combination of a PUSCH mapping type, a start symbol of the PUSCH, and the number of consecutive symbols to be allocated.
  • frequencyDomainAllocation Used to indicate frequency resource allocation for PUSCH.
  • Type 1 CG PUSCH different parameters may be introduced for each type of Type 1 CG PUSCH and Type 2 CG PUSCH.
  • timeDomainAllocation and frequencyDomainAllocation may be introduced only for Type 1 CG PUSCH.
  • TDRA Time Domain Resource Allocation
  • FDRA Frequency Domain Resource Allocation
  • Proposal 3 proposes a method for a terminal to determine whether or not the activation DCI is for activating a cell-specific/group-common SPS/CG configuration. Proposal 3 can be applied to the SPS PDSCH and Type 2 CG PUSCH.
  • 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 (e.g., CS-RNTI: Configured Scheduling RNTI or a new RNTI) of the received DCI.
  • a predetermined identifier e.g., CS-RNTI: Configured Scheduling RNTI or a new RNTI
  • 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.
  • the DCI format includes a DCI format identification field (ID for DCI formats), a frequency domain resource assignment field (FDRA: Frequency Domain Resource Assignment), a time domain resource assignment field (TDRA: Time Domain Resource Assignment), a frequency hopping flag field, an MCS field, an NDI (New Data Indicator) field, an RV (Redundancy Version) field, an HPN (HARQ Process Number) field, a TCP (Transmission Power Control) field, a Padding field, and a UL/SUL indicator field.
  • ID DCI format identification field
  • FDRA Frequency Domain Resource Assignment
  • TDRA Time Domain Resource Assignment
  • a frequency hopping flag field an MCS field
  • NDI New Data Indicator
  • RV Redundancy Version
  • HPN HARQ Process Number
  • TCP Transmission Power Control
  • Padding field a UL/SUL indicator field
  • the NDI field is a field that indicates the NDI value.
  • the RV field is a field that indicates the RV value.
  • the TPC field is a field that indicates a value used to control the transmission power of the PUSCH.
  • the Padding field is a field used to align the number of bits (size) of DCI format 1_0 and DCI format 0_0.
  • the UL/SUL indication field is a field that indicates whether the PUSCH is to be placed on the first uplink component carrier or the second component carrier when the PUSCH is scheduled by a DCI format including the UL/SUL field.
  • 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.
  • a new group-common DCI format for activating cell-specific/group-common SPS/CG configuration is introduced as the DCI format for activation DCI, and the terminal may determine whether the DCI is an activation DCI for activating cell-specific/group-common SPS/CG configuration depending on whether the DCI format of the received DCI is a group-common DCI format.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine whether the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration depending on whether the field of the DCI is set to a predetermined value.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may combine some of the above Options 1 to 3 to determine whether the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine that the received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration and may enable the SPS PDSCH and/or Type 2 CG PUSCH.
  • the activation DCI can indicate additional parameters. For example, as described in Proposal 2 above, when timeDomainAllocation and frequencyDomainAllocation are introduced only in Type 1 CG PUSCH, in Type 2 CG PUSCH and/or SPS PDSCH, TDRA and FDRA may be notified to the terminal by the activation DCI.
  • the activation DCI can dynamically update parameters that have already been set by higher layer parameters. For example, the periodicity set by RRC parameters may be updated by the activation DCI.
  • a terminal in an SPS PDSCH and a Type 2 CG PUSCH, a terminal can determine whether or not a received DCI is an activation DCI for activating a cell-specific/group-common SPS/CG configuration.
  • Proposal 4 proposes a method for a terminal to determine whether a deactivation DCI is for deactivating a cell-specific/group-common SPS/CG configuration. Proposal 4 can be applied to an SPS PDSCH and a Type 2 CG PUSCH.
  • 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 (e.g., CS-RNTI: Configured Scheduling RNTI or a new RNTI) of the DCI.
  • a predetermined identifier e.g., CS-RNTI: Configured Scheduling RNTI or a new RNTI
  • 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.
  • 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 (deactivate) one or more of the SPS PDSCH and/or Type 2 CG PUSCH.
  • a new group-common DCI format for deactivating a cell-specific/group-common SPS/CG configuration is introduced as a DCI format for a deactivation DCI, and a terminal may determine whether or not a received DCI is a deactivation DCI for deactivating a cell-specific/group-common SPS/CG configuration depending on whether the DCI format of the received DCI is a group-common DCI format.
  • the terminal may determine that the received DCI is a deactivation DCI for deactivating the cell-specific/group-common SPS/CG configuration, and may release (disable) one or more of the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may determine whether the received DCI is a deactivation DCI for deactivating a cell-specific/group-common SPS/CG configuration depending on whether the field of the DCI is set to a predetermined value.
  • 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 of the SPS PDSCH and/or Type 2 CG PUSCH.
  • the terminal may combine some of the above Options 1 to 3 to determine whether the received DCI is a deactivation DCI for deactivating a cell-specific/group-common SPS/CG configuration.
  • 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 (deactivate) one or more of the SPS PDSCH and/or Type 2 CG PUSCH.
  • 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 (deactivate) one or more of the SPS PDSCH and/or Type 2 CG PUSCH.
  • 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 of the SPS PDSCH and/or Type 2 CG PUSCH.
  • 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 (deactivate) one or more of the SPS PDSCH and/or Type 2 CG PUSCH.
  • 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 of the SPS PDSCH and/or Type 2 CG PUSCH.
  • 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 of the SPS PDSCH and/or Type 2 CG PUSCH.
  • the deactivation DCI can dynamically update parameters already set by higher layer parameters. For example, the periodicity set by the RRC parameters may be updated by the deactivation DCI.
  • a terminal in an SPS PDSCH and a Type 2 CG PUSCH, a terminal can determine whether or not a received DCI is a deactivation DCI for deactivating a cell-specific/group-common SPS/CG configuration.
  • Proposal 5 In Proposal 5, we propose the number of configurable cell-specific/group-common SPS/CG configurations.
  • the number of cell-specific/group-common SPS/CG configurations may be set independently of the number of UE specific SPS/CG configurations.
  • the number of UE-specific SPS configurations is "8"
  • the number of cell-specific/group-common SPS configurations may be "X" (X is an integer greater than or equal to 1), and the total number of SPS configurations may be "8 + X”.
  • the number of UE-specific CG configurations is "12"
  • the number of cell-specific/group-common CG configurations may be "Y" (Y is an integer equal to or greater than 1), and the total number of CG configurations may be "12 + Y”.
  • 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 is constant.
  • the number of UE-specific SPS configurations may be "X" (X is an integer between 1 and 7), and the number of cell-specific/group-common SPS configurations may be "8-X”.
  • the number of UE-specific CG configurations may be "Y" (Y is an integer between 1 and 11), and the number of cell-specific/group-common CG configurations may be "12-Y".
  • Proposal 6 proposes terminal behavior regarding SPS/CG configuration during BWP switching.
  • Option 2 When a terminal is instructed by a base station to perform BWP switching from a terminal-specific BWP to a common BWP, the terminal may assume reception of a cell-specific/group-common SPS configuration and/or transmission of a cell-specific/group-common SPS configuration without receiving an activation DCI.
  • the terminal can be operated appropriately with respect to the SPS/CG configuration during BWP switching.
  • Proposal 7 proposes a method for determining frequency domain resources when switching active BWPs when CG PUSCH and/or SPS PDSCH are configured.
  • the RB index allocation for frequency domain resource allocation is determined within the terminal's BWP as specified by the BWP indicator field contained in the DCI.
  • the CG PUSCH and SPS PDSCH were deactivated when the BWP was switched, and an activation DCI was required for the new BWP, so there was no way to determine the RB index allocation for the CG PUSCH and SPS PDSCH when switching between active BWPs.
  • FIG. 5 is a sequence diagram for explaining an example of BWP switching according to an embodiment of the present invention.
  • the base station 10 transmits settings for the CG PUSCH and/or SPS PDSCH to the terminal 20.
  • the base station 10 and the terminal 20 transmit and receive the CG PUSCH and/or SPS PDSCH.
  • the base station 10 transmits an active BWP switching instruction by DCI to the terminal 20.
  • the terminal 20 determines the RB index of the FDRA for the CG PUSCH and/or SPS PDSCH in the switched BWP. Furthermore, based on the determined RB index, it determines the resources to be used for transmitting the CG PUSCH and/or receiving the SPS PDSCH in the switched BWP.
  • the RB index of the FDRA for the CG PUSCH and/or SPS PDSCH in the BWP after the switch may be determined within the BWP of the UE notified by the BWP indicator field included in the DCI received in step S13.
  • the terminal 20 When the terminal 20 detects a PDCCH for its own device carrying the DCI, it may first determine a UL or DL BWP for the CG PUSCH or SPS PDSCH. Then, the terminal 20 may determine a resource allocation within the determined BWP. The terminal 20 may start the RB index allocation or numbering from the lowest RB of the UL or DL BWP determined for the CG PUSCH or SPS PDSCH.
  • the above BWP switching may be performed by group-common DCI or UE-specific DCI.
  • the CG PUSCH may be type 1 and/or type 2.
  • type 0 or type 1 may be used.
  • FDRA type for the CP PUSCH type 0, type 1 or type 2 may be used.
  • the same FDRA type may or may not be used in the target BWP as in the previous BWP or source BWP. For example, if FDRA type 0 was used in the previous BWP, FDRA type 0 may be used in the target BWP after the BWP switch.
  • FDRA type 0 for SPS PDSCH may use a bitmap that specifies the assigned RBG (Resource Block Group) (see non-patent document 6).
  • FDRA type 1 for SPS PDSCH may use a resource indication value (RIV) that specifies the start position of the assigned virtual RB and the length of consecutive RBs (see non-patent document 6).
  • RBG Resource Block Group
  • FDRA type 1 for SPS PDSCH may use a resource indication value (RIV) that specifies the start position of the assigned virtual RB and the length of consecutive RBs (see non-patent document 6).
  • RBG Resource Block Group
  • FDRA type 0 for CG PUSCH may use a bitmap that specifies the assigned RBG (see non-patent document 6).
  • FDRA type 1 for CG PUSCH may be an RIV that specifies the start position of the assigned virtual RB and the length of consecutive RBs (see non-patent document 6).
  • FDRA type 2 for CG PUSCH may specify up to M interlace indices (see non-patent document 6).
  • step S15 the base station 10 and the terminal 20 continue to transmit and receive the CG PUSCH and/or SPS PDSCH in the switched BWP.
  • any of a plurality of options is applied to one setting.
  • which of a plurality of proposals/options is applied and/or which of a plurality of options is applied may be determined in the following manner.
  • the higher layer parameters may be RRC parameters, Medium Access Control (MAC) parameters, or a combination of these.
  • Dynamic SPS PDSCH parameter updates and/or CG PUSCH parameter updates can be applied in conjunction with the configuration of cell-specific/group-common SPS/CG configuration parameters.
  • the terminal may report the following terminal capabilities to the base station as UE capability.
  • the information indicating the terminal capabilities may correspond to information defining the terminal capabilities. Whether or not a common BWP for NW ES is supported Whether or not bandwidth adaptation within a BWP is supported Whether or not bandwidth adaptation by BWP switching is supported Whether or not the terminal supports cell-specific/group-common SPS/CG configuration
  • the above-described embodiment allows the wireless communication system to achieve power saving by adaptively switching the bandwidth used.
  • communication can be continued without deactivation and reactivation, thereby reducing signaling overhead.
  • the base station 10 and the terminal 20 include functions for implementing the above-mentioned embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions in the embodiments.
  • Fig. 6 is a diagram showing an example of the functional configuration of the base station 10 in the embodiment of the present invention.
  • the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140.
  • the functional configuration shown in Fig. 6 is merely an example. As long as the operation related to the embodiment of the present invention can be executed, the names of the functional divisions and the functional units may be any.
  • the transmitting unit 110 and the receiving unit 120 may be called a communication unit.
  • the transmitting unit 110 has a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly.
  • the transmitting unit 110 also transmits inter-network node messages to other network nodes.
  • the receiving unit 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signals.
  • the transmitting unit 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signals, etc. to the terminal 20.
  • the receiving unit 120 also receives inter-network node messages from other network nodes.
  • the setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20.
  • the contents of the setting information include, for example, information related to the BWP.
  • the control unit 140 performs control related to the BWP as described in the embodiment.
  • the functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
  • Fig. 7 is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention.
  • the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240.
  • the functional configuration shown in Fig. 7 is merely an example. As long as the operation related to the embodiment of the present invention can be executed, the names of the functional divisions and functional units may be any.
  • the transmitting unit 210 and the receiving unit 220 may be called a communication unit.
  • the transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly.
  • the receiver 220 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals.
  • the receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL/UL/SL control signals, etc. transmitted from the base station 10.
  • the transmitter 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to another terminal 20 as D2D communication, and the receiver 220 receives PSCCH, PSSCH, PSDCH, PSBCH, etc. from the other terminal 20.
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220.
  • the setting unit 230 also stores setting information that is set in advance.
  • the contents of the setting information include, for example, information related to the BWP.
  • the control unit 240 performs control related to the BWP as described in the embodiment.
  • the functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
  • each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.).
  • the functional block may be realized by combining the one device or the multiple devices with software.
  • Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment.
  • a functional block (component) that performs the transmission function is called a transmitting unit or transmitter.
  • the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure.
  • FIG. 8 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 in one embodiment of the present disclosure.
  • the above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.
  • the term "apparatus" can be interpreted as a circuit, device, unit, etc.
  • the hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.
  • the functions of the base station 10 and the terminal 20 are realized by loading specific software (programs) onto hardware such as the processor 1001 and the storage device 1002, causing the processor 1001 to perform calculations, control communications by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.
  • the processor 1001 for example, operates an operating system to control the entire computer.
  • the processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, registers, etc.
  • CPU central processing unit
  • control unit 140, control unit 240, etc. may be realized by the processor 1001.
  • the processor 1001 reads out a program (program code), software module, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to the program.
  • the program is a program that causes a computer to execute at least a part of the operations described in the above-mentioned embodiment.
  • the control unit 140 of the base station 10 shown in FIG. 6 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001.
  • the control unit 240 of the terminal 20 shown in FIG. 7 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001.
  • the processor 1001 may be implemented by one or more chips.
  • the program may be transmitted from a network via a telecommunication line.
  • the storage device 1002 is a computer-readable recording medium and may be composed of, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc.
  • the storage device 1002 may also be called a register, a cache, a main memory, etc.
  • the storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method relating to one embodiment of the present disclosure.
  • the auxiliary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc.
  • the above-mentioned storage medium may be, for example, a database, a server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.
  • 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, for example, a network device, a network controller, a network card, a communication module, etc.
  • the communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize at least one of, for example, Frequency Division Duplex (FDD) and Time Division Duplex (TDD).
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the transmitting/receiving antenna, an amplifier unit, a transmitting/receiving unit, a transmission path interface, etc. may be realized by the communication device 1004.
  • the transmitting/receiving unit may be implemented as a transmitting unit or a receiving unit that is physically or logically separated.
  • the input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside.
  • the output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one structure (e.g., a touch panel).
  • each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
  • the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware.
  • the processor 1001 may be implemented using at least one of these pieces of hardware.
  • FIG. 9 shows an example configuration of a vehicle 2001.
  • the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013.
  • a communication device mounted on the vehicle 2001 and may be applied to the communication module 2013, for example.
  • the drive unit 2002 is composed 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 handlebar), and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
  • the electronic control unit 2010 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001.
  • the electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
  • Signals from the various sensors 2021-2029 include a current signal from a current sensor 2021 that senses the motor current, a front and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front and rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
  • the information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices.
  • the information service unit 2012 uses information acquired from an external device via the communication module 2013 or the like to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.
  • the information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.
  • input devices e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.
  • output devices e.g., a display, a speaker, an LED lamp, a touch panel, etc.
  • the driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as a millimeter wave radar, LiDAR (Light Detection and Ranging), a camera, a positioning locator (e.g., GNSS, etc.), map information (e.g., high definition (HD) maps, autonomous vehicle (AV) maps, etc.), a gyro system (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chip, and AI processor, as well as one or more ECUs that control these devices.
  • the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.
  • the communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port.
  • the communication module 2013 transmits and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided on the vehicle 2001.
  • the communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication.
  • the communication module 2013 may be located either inside or outside the electronic control unit 2010.
  • the external device may be, for example, a base station, a mobile station, etc.
  • the communication module 2013 may transmit at least one of the signals from the various sensors 2021-2028 described above input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication.
  • the electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input.
  • the PUSCH transmitted by the communication module 2013 may include information based on the above input.
  • the communication module 2013 receives various information (traffic information, signal information, vehicle distance 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 be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 2013).
  • the communication module 2013 also stores various information received from an external device in a memory 2032 that can be used by the microprocessor 2031.
  • the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.
  • a terminal having a receiving unit that receives control information for changing a bandwidth to be used and a first setting for an SPS-PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) or a second setting for a CG-PUSCH (Configured Grant Physical Uplink Shared Channel) from a base station, a communication unit that receives an SPS-PDSCH from the base station based on the first setting or transmits a CG-PUSCH to the base station based on the second setting, and a control unit that changes the bandwidth to be used based on the control information, wherein the control unit determines an RB (Resource Block) index of a frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit receives an SPS-PDSCH from the base station or transmits a CG-PUSCH to the base station based on the RB index in the changed bandwidth.
  • SPS-PDSCH Semi-Persistent Scheduling Downlink Shared Channel
  • CG-PUSCH Configured Grant
  • the above configuration allows the wireless communication system to achieve power savings by adaptively switching the bandwidth used.
  • communication can be continued without deactivation and reactivation, reducing signaling overhead.
  • power consumption can be reduced by controlling the BWP (Bandwidth Part).
  • the control unit does not need to disable and re-enable the SPS-PDSCH or CG-PUSCH when changing the bandwidth to be used.
  • the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used.
  • communication can be continued without deactivating and reactivating, thereby reducing signaling overhead.
  • the control unit may start the numbering of the RB index from the RB at the lower end of the changed bandwidth.
  • the control unit may use the same frequency domain resource allocation method for the bandwidth before the change and the bandwidth after the change.
  • the wireless communication system can achieve power saving by adaptively switching the bandwidth to be used.
  • communication can be continued without deactivation and reactivation, thereby reducing signaling overhead.
  • a base station having a transmission unit that transmits control information for changing the bandwidth to be used and a first setting for an SPS-PDSCH (Semi-Persistent Scheduling Downlink Shared Channel) or a second setting for a CG-PUSCH (Configured Grant Physical Uplink Shared Channel) to a terminal, a communication unit that transmits an SPS-PDSCH to the terminal based on the first setting or receives a CG-PUSCH from the terminal based on the second setting, and a control unit that changes the bandwidth to be used based on the control information, the control unit determining an RB (Resource Block) index of a frequency domain resource allocation in the changed bandwidth based on the control information, and the communication unit transmitting an SPS-PDSCH to the terminal or receiving a CG-PUSCH from the terminal based on the RB index in the changed bandwidth.
  • SPS-PDSCH Semi-Persistent Scheduling Downlink Shared Channel
  • CG-PUSCH Configured Grant Physical Uplink Shared Channel
  • the above configuration allows the wireless communication system to achieve power savings by adaptively switching the bandwidth used.
  • communication can be continued without deactivation and reactivation, reducing signaling overhead.
  • power consumption can be reduced by controlling the BWP (Bandwidth Part).
  • a method includes the steps of receiving control information for changing a bandwidth to be used and a first setting for a Semi-Persistent Scheduling Downlink Shared Channel (SPS-PDSCH) or a second setting for a Configured Grant Physical Uplink Shared Channel (CG-PUSCH) from a base station, receiving an SPS-PDSCH from the base station based on the first setting or transmitting a CG-PUSCH to the base station based on the second setting, and changing the bandwidth to be used based on the control information.
  • SPS-PDSCH Semi-Persistent Scheduling Downlink Shared Channel
  • CG-PUSCH Configured Grant Physical Uplink Shared Channel
  • a communication method in which a terminal executes a procedure of determining a resource block (RB) index of a frequency domain resource allocation in a changed bandwidth based on the control information, and a procedure of receiving an SPS-PDSCH from the base station or transmitting a CG-PUSCH to the base station in the changed bandwidth based on the RB index.
  • RB resource block
  • the above configuration allows the wireless communication system to achieve power savings by adaptively switching the bandwidth used.
  • communication can be continued without deactivation and reactivation, reducing signaling overhead.
  • power consumption can be reduced by controlling the BWP (Bandwidth Part).
  • the operations of multiple functional units may be physically performed by one part, or the operations of one functional unit may be physically performed by multiple parts.
  • the order of processing procedures described in the embodiment may be changed as long as there is no contradiction.
  • the base station 10 and the terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof.
  • the software operated by the processor possessed by the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor possessed by the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.
  • the notification of information is not limited to the aspects/embodiments described in the present disclosure and may be performed using other methods.
  • the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these.
  • RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.
  • Each aspect/embodiment described in this disclosure is a mobile communication system that is compatible with 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 (x is, for example, an integer or decimal number)), FRA (Future Ra).
  • the present invention may be applied to at least one of systems using IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, and next-generation systems that are expanded, modified, created, or defined based on these. It may also be applied to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G, etc.).
  • certain operations that are described as being performed by the base station 10 may in some cases be performed by its upper node.
  • various operations performed for communication with a terminal 20 may be performed by at least one of the base station 10 and other network nodes other than the base station 10 (such as, but not limited to, an MME or S-GW).
  • the base station 10 may be a combination of multiple other network nodes (such as an MME and an S-GW).
  • the information or signals described in this disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may be input and output via multiple network nodes.
  • the determination in this disclosure may be based on a value represented by one bit (0 or 1), a Boolean (true or false) value, or a comparison of numerical values (e.g., a comparison with a predetermined value).
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Software, instructions, information, etc. may also be transmitted and received via a transmission medium.
  • a transmission medium For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.
  • wired technologies such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)
  • wireless technologies such as infrared, microwave
  • the information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies.
  • the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
  • the channel and the symbol may be a signal (signaling).
  • the signal may be a message.
  • the component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
  • system and “network” are used interchangeably.
  • a radio resource may be indicated by an index.
  • the names used for the above-mentioned parameters are not limiting in any respect. Furthermore, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure.
  • the various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.
  • base station BS
  • wireless base station base station
  • base station device fixed station
  • NodeB nodeB
  • eNodeB eNodeB
  • gNodeB gNodeB
  • access point e.g., "transmission point”
  • gNodeB gNodeB
  • a base station may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
  • a base station can accommodate one or more (e.g., three) cells.
  • a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)).
  • RRH Remote Radio Head
  • the term "cell” or “sector” refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.
  • a base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
  • MS Mobile Station
  • UE User Equipment
  • a mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
  • 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 be a device mounted on a moving object, the moving object itself, etc.
  • the moving object is a movable object, and the moving speed is arbitrary. It also includes the case where the moving object is stopped.
  • the moving object includes, but is not limited to, for example, a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an artificial satellite, a drone (registered trademark), a multicopter, a quadcopter, a balloon, and objects mounted thereon.
  • the moving object may also be a moving object that travels autonomously based on an operation command.
  • At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations.
  • at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read as a user terminal.
  • each aspect/embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)).
  • the terminal 20 may be configured to have the functions of the base station 10 described above.
  • terms such as "uplink” and "downlink” may be read as terms corresponding to terminal-to-terminal communication (for example, "side").
  • the uplink channel, downlink channel, etc. may be read as a side channel.
  • the user terminal in this disclosure may be interpreted as a base station.
  • the base station may be configured to have the functions of the user terminal described above.
  • determining may encompass a wide variety of actions.
  • Determining and “determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), and considering ascertaining as “judging” or “determining.”
  • determining and “determining” may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and considering ascertaining as “judging” or “determining.”
  • judgment” and “decision” can include considering resolving, selecting, choosing, establishing, comparing, etc., to have been “judged” or “decided.” In other words, “judgment” and “decision” can include considering some action to have been “judged” or “decided.” Additionally, “judgment (decision)” can be interpreted as “assuming,” “ex
  • connection refers to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” to each other.
  • the coupling or connection between elements may be physical, logical, or a combination thereof.
  • “connected” may be read as "access.”
  • two elements may be considered to be “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
  • the reference signal may also be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • any reference to an element using a designation such as "first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
  • a radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
  • Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.
  • SCS subcarrier spacing
  • TTI transmission time interval
  • radio frame structure a specific filtering process performed by the transceiver in the frequency domain
  • a specific windowing process performed by the transceiver in the time domain etc.
  • 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 be a time unit based on numerology.
  • a slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot.
  • a PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A.
  • a PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
  • Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name that corresponds to the radio frame, subframe, slot, minislot, and symbol.
  • one subframe may be called a Transmission Time Interval (TTI)
  • TTI Transmission Time Interval
  • multiple consecutive subframes may be called a TTI
  • one slot or one minislot may be called a TTI.
  • at least one of the subframe and the 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.
  • the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
  • TTI refers to, for example, the smallest time unit for scheduling in wireless communication.
  • a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units.
  • wireless resources such as frequency bandwidth and transmission power that can be used by each terminal 20
  • TTI is not limited to this.
  • the TTI may be a transmission time unit for a channel-coded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc.
  • the time interval e.g., the number of symbols
  • the time interval in which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit of scheduling.
  • the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.
  • 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.
  • TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
  • a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms
  • a short TTI e.g., a shortened TTI, etc.
  • TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.
  • a resource block is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain.
  • the number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12.
  • the number of subcarriers included in an RB may be determined based on the numerology.
  • the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length.
  • One TTI, one subframe, etc. may each be composed of one or more resource blocks.
  • one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
  • PRB physical resource block
  • SCG sub-carrier group
  • REG resource element group
  • PRB pair an RB pair, etc.
  • a resource block may be composed of one or more resource elements (REs).
  • REs resource elements
  • one RE may be a radio resource area of one subcarrier and one symbol.
  • a bandwidth part which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by an index of the RB relative to a common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within the BWP.
  • the BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP).
  • UL BWP UL BWP
  • DL BWP DL BWP
  • One or more BWPs may be configured for a UE within one carrier.
  • At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP.
  • BWP bitmap
  • radio frames, subframes, slots, minislots, and symbols are merely examples.
  • the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.
  • 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 “combined” may also be interpreted in the same way as “different.”
  • notification of specific information is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).
  • Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotational speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Landscapes

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

Abstract

La présente invention comprend : une unité de réception qui reçoit, en provenance d'une station de base, des informations de commande pour changer la bande passante à utiliser, et un premier réglage concernant un canal physique partagé descendant de planification semi-persistante (SPS-PDSCH) ou un second réglage concernant un canal physique partagé montant à autorisation configurée (CG-PUSCH) ; une unité de communication qui reçoit le SPS-PDSCH en provenance de la station de base, sur la base du premier réglage, ou transmet le CG-PUSCH à la station de base, sur la base du second réglage ; et une unité de commande qui modifie la bande passante à utiliser sur la base des informations de commande. L'unité de commande détermine un indice de bloc de ressources (RB) pour une attribution de ressources de région de fréquence dans la bande passante modifiée, sur la base des informations de commande. Dans la bande passante modifiée, l'unité de communication reçoit le SPS-PDSCH en provenance de la station de base ou transmet le CG-PUSCH à la station de base, sur la base de l'indice RB.
PCT/JP2023/040885 2022-11-18 2023-11-14 Terminal, station de base et procédé de communication WO2024106418A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022185295 2022-11-18
JP2022-185295 2022-11-18

Publications (1)

Publication Number Publication Date
WO2024106418A1 true WO2024106418A1 (fr) 2024-05-23

Family

ID=91084862

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/040885 WO2024106418A1 (fr) 2022-11-18 2023-11-14 Terminal, station de base et procédé de communication

Country Status (1)

Country Link
WO (1) WO2024106418A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 17)", 3GPP TS 38.214, no. V17.3.0, 21 September 2022 (2022-09-21), pages 1 - 233, XP052210882 *
SAMSUNG: "Discussion on FDM solution for in-device co-existence interference avoidance", 3GPP TSG RAN WG 2 #119-E, R2-2207844, 10 August 2022 (2022-08-10), XP052261161 *
SUKCHEL YANG, LG ELECTRONICS: "Discussion on physical layer techniques for network energy savings", 3GPP TSG RAN WG 1 #111 R1-2212302, 7 November 2022 (2022-11-07), XP052222860 *

Similar Documents

Publication Publication Date Title
WO2024106418A1 (fr) Terminal, station de base et procédé de communication
WO2023243064A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2023209914A1 (fr) Terminal et procédé de communication sans fil
WO2024095486A1 (fr) Terminal et procédé de communication
WO2024079796A1 (fr) Terminal et procédé de communication
WO2024095487A1 (fr) Terminal et procédé de communication
WO2024201816A1 (fr) Terminal, station de base et procédé de communication
WO2024100746A1 (fr) Terminal, station de base et procédé de communication
WO2024180915A1 (fr) Terminal, station de base, et procédé de communication
WO2024100892A1 (fr) Terminal, station de base et procédé de communication
WO2024181544A1 (fr) Terminal et procédé de communication
WO2024219119A1 (fr) Terminal et procédé de communication
WO2024069989A1 (fr) Terminal et procédé de communication
WO2023210010A1 (fr) Terminal et procédé de communication
WO2024043295A1 (fr) Terminal, station de base et procédé de communication
WO2024043086A1 (fr) Terminal, station de base et procédé de communication
WO2024181445A1 (fr) Terminal, et procédé de communication sans fil
WO2024100905A1 (fr) Terminal, station de base et procédé de communication
WO2024219387A1 (fr) Terminal et procédé de communication
WO2024084839A1 (fr) Terminal et procédé de communication
WO2024069904A1 (fr) Terminal, et procédé de communication
WO2024069903A1 (fr) Terminal, et procédé de communication
WO2023209915A1 (fr) Terminal, station de base et procédé de communication sans fil
WO2024209649A1 (fr) Terminal, station de base, et procédé de communication
WO2024218887A1 (fr) Terminal, station de base et procédé de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23891565

Country of ref document: EP

Kind code of ref document: A1