Terminal and communication method

Abstract

The terminal has a reception section that receives, from a base station, signaling that sets a resource related to an on-demand SSB (SS / PBCH Block) and signaling that indicates activation of a secondary cell, and a control section that performs a process of activating the secondary cell using the on-demand SSB.

Description

Technical Field

[0001] This invention relates to terminals and communication methods in wireless communication systems. Background Technology

[0002] In NR (New Radio) (also known as "5G"), which is the successor system to LTE (Long Term Evolution), technologies are being researched to meet the requirements of high-capacity systems, high-speed data transmission, low latency, simultaneous connection of multiple terminals, low cost, and power saving (e.g., Non-Patent Literature 1).

[0003] In addition, in 3GPP (registered trademark) version 18, in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), and reduction of operating costs, methods for increasing the importance of network energy savings and implementing energy-saving measures were studied (e.g., non-patent literature 2).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-patent document 1: 3GPP TS 38.300 V18.0.0 (2023-12)

[0007] Non-patent literature 2: "New WID: Network energy savings for NR", RP-223540, 3GPPTSG RAN Meeting #98-e, December 2022

[0008] Non-patent document 3: 3GPP TS 38.331 V18.0.0 (2023-12) Summary of the Invention

[0009] The problem that the invention aims to solve

[0010] To achieve carbon neutrality and the SDGs, the importance of saving base station power consumption is increasing, and the introduction of intermittent transmission and reception in base stations is being studied. In cells that support power saving (Energy Saving, ES), the resource allocation method for on-demand transmission of SSBs (SS / PBCH Blocks) when activating a secondary cell is unclear.

[0011] The present invention was made in view of the above aspects, and its object is to activate the sub-cell in a base station that can migrate to a power-saving state.

[0012] Methods for solving problems

[0013] According to the disclosed technology, a terminal is provided, comprising: a receiving unit that receives from a base station signaling that sets resources related to an on-demand transmission SSB (SS / PBCH Block) and signaling that instructs the activation of a secondary cell; and a control unit that performs a process of activating the secondary cell using the on-demand transmission SSB.

[0014] The effects of the invention

[0015] According to the disclosed technology, secondary cells can be activated in base stations that are able to migrate to a power-saving state. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating a wireless communication system according to an embodiment of the present invention.

[0017] Figure 2 This is a diagram used to illustrate CDRX in NR version 15.

[0018] Figure 3 This is a diagram used to illustrate WUS in NR version 16.

[0019] Figure 4 This is a diagram illustrating the intermittent reception of a base station in Embodiment 1 of the present invention.

[0020] Figure 5 This is a diagram illustrating the parameters of Embodiment 1 of the present invention.

[0021] Figure 6 This is a diagram illustrating the intermittent transmission of a base station in Embodiment 5 of the present invention.

[0022] Figure 7 This is a diagram illustrating the parameters of Embodiment 5 of the present invention.

[0023] Figure 8 This is a timing diagram for illustrating Example (1) of OSI transmission in Embodiment 9 of the present invention.

[0024] Figure 9 This is a timing diagram for illustrating Example (2) of OSI transmission in Embodiment 9 of the present invention.

[0025] Figure 10 This is a diagram illustrating an example of an on-demand SSB according to Embodiment 9 of the present invention.

[0026] Figure 11 This is a flowchart illustrating Example (1) of the operation related to On-Demand SSB in Embodiment 9 of the present invention.

[0027] Figure 12 This is a flowchart illustrating Example (2) of the operation related to On-Demand SSB in Embodiment 9 of the present invention.

[0028] Figure 13 This is a diagram illustrating an example of the functional structure of a base station according to an embodiment of the present invention.

[0029] Figure 14 This is a diagram illustrating an example of the functional structure of a terminal according to an embodiment of the present invention.

[0030] Figure 15 This is a diagram illustrating an example of the hardware structure of a base station or terminal according to an embodiment of the present invention.

[0031] Figure 16 This is a diagram illustrating an example of the structure of a vehicle according to an embodiment of the present invention. Detailed Implementation

[0032] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. Furthermore, the embodiments described below are merely examples, and the application of the present invention is not limited to the embodiments described below.

[0033] In the operation of the wireless communication system according to embodiments of the present invention, existing technologies may be appropriately used. These existing technologies include, for example, existing NR or LTE, but are not limited to, existing NR or LTE. Furthermore, unless otherwise stated, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and subsequent methods (e.g., NR).

[0034] Furthermore, in the embodiments of the present invention described below, the terms SS (Synchronization Signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in conventional LTE are used. These are for ease of description, and the same signals and functions may also be referred to by other names. In addition, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily explicitly written as "NR-".

[0035] Furthermore, in embodiments of the present invention, the duplex mode can be TDD (Time Division Duplex), FDD (Frequency Division Duplex), or other modes (e.g., Flexible Duplex).

[0036] Furthermore, in embodiments of the present invention, the "configure" wireless parameters can be pre-configured predetermined values ​​or wireless parameters notified from a base station or terminal.

[0037] (System Structure)

[0038] Figure 1 This is a diagram illustrating a wireless communication system according to embodiments of the present invention. For example... Figure 1 As shown, the wireless communication system in this embodiment of the invention includes a base station 10 and a terminal 20. Figure 1 The image shows one base station 10 and one terminal 20, but this is just one example; there can be multiple terminals.

[0039] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time and frequency domains. The time domain can be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain can be defined by the number of subcarriers or resource blocks. Furthermore, the TTI (Transmission Time Interval) in the time domain can be a time slot, or a subframe.

[0040] Base station 10 sends synchronization signals and system information to terminal 20. Synchronization signals may be, for example, NR-PSS and NR-SSS. System information may be transmitted via NR-PBCH, also known as broadcast information. Synchronization signals and system information can also be referred to as SSB (SS / PBCH block: synchronization signal / physical broadcast channel block). Figure 1 As shown, base station 10 sends control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of beamforming for signal transmission and reception. Furthermore, both base station 10 and terminal 20 can apply MIMO (Multiple Input Multiple Output) based communication to DL or UL. Additionally, base station 10 and terminal 20 can also communicate via CA (Carrier Aggregation) based secondary cells (SCell) and primary cells (PCell). Moreover, terminal 20 can also communicate via DC (Dual Connectivity) based primary cells of base station 10 and primary SCG cells of other base stations 10.

[0041] Terminal 20 is a communication device with wireless communication capabilities, such as a smartphone, mobile phone, tablet computer, wearable terminal, or M2M (Machine-to-Machine) communication module. Figure 1 As shown, terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Furthermore, terminal 20 receives various reference signals transmitted from base station 10 and performs propagation path quality measurements based on the reception results of these reference signals. Alternatively, terminal 20 can be referred to as UE, and base station 10 as gNB.

[0042] Next, the discussion on power saving in base stations in NR Release 18 will be explained. From the perspectives of both the transmitting and receiving sides of the base station, methods for improving network power saving in base stations and terminals are being studied. For example, methods are being studied to achieve more efficient dynamic and / or semi-static and finer-grained adaptation in transmission and / or reception by using potential support / feedback and potential auxiliary information from terminals, through one or more network power saving techniques in the time domain, frequency domain, spatial domain, and power domain.

[0043] Next, the intermittent reception (DRX: Discontinuous Reception) or connected mode DRX (CDRX: Connected Mode Discontinuous Reception) in conventional terminals will be explained.

[0044] Figure 2 This is a diagram used to illustrate CDRX in NR version 15. In the CDRX action of NR version 15, the terminal monitors the PDCCH during the DRX enable period.

[0045] Figure 3 This diagram illustrates WUS in NR Release 16. In NR Release 16, the PDCCH-based Wake-Up Signal (WUS) can instruct more than one terminal whether the terminal should monitor the PDCCH during the next DRX activation period.

[0046] DCI format 2_6, which scrambles CRC (Cyclic Redundancy Check) using PS-RNTI (Power Saving - Radio Network Temporary Identifier), is used as a PDCCH-based WUS and is also known as DCP (DCI with CRC scrambled by PS-RNTI).

[0047] The timing of WUS monitoring is set by offsetting the period from when the terminal-based function is enabled. When WUS indicates "inactive" (i.e., when the terminal is not transmitting or receiving data), the terminal can skip monitoring during the enabled period and immediately switch to sleep mode. Furthermore, for example, if PDCCH-based WUS is not detected due to a detection error, a default terminal action can be set.

[0048] DCI format 2_6 contains a 1-bit startup indication message indicating whether the device is "activated" or "inactive".

[0049] (Previous issues)

[0050] Next, we will discuss the previous issues. To achieve carbon neutrality and the SDGs, saving base station power consumption is becoming increasingly important. However, in the past, there has been a problem that methods for saving base station power consumption have not been standardized.

[0051] (Summary of this implementation method 1)

[0052] Therefore, in this embodiment, an example of reducing base station power consumption from a time-domain perspective will be described. Hereinafter, Examples 1 to 4 will be described as specific embodiments.

[0053] (Example 1)

[0054] In this embodiment, the definitions of actions and associated concepts in the case of intermittent reception by the base station are explained.

[0055] Figure 4 This is a diagram illustrating the intermittent reception of a base station in Embodiment 1 of the present invention. The period during which the base station 10 sets the receiving unit to invalid / valid is introduced as the intermittent reception (gNB CDRX) function of the base station (hereinafter referred to as base station intermittent reception).

[0056] The concept of intermittent reception at base station 10 is the same as that at terminal 20. Invalid receiving units and / or parameters can be each port, panel, beam, or carrier (or cell).

[0057] Figure 5 This diagram illustrates the parameters of Embodiment 1, which describes the implementation of the present invention. The base station CDRX can be defined by several parameters listed below. Furthermore, the units of the parameters can be symbols, time slots, subframes, milliseconds, or seconds, etc. The units can be different or the same across the parameters.

[0058] • drx-onDurationTimer: The period at the start of the DRX cycle

[0059] • drx-SlotOffset: The delay before drx-onDurationTimer starts

[0060] • drx-InactivityTimer: The period during which terminal 20 performs uplink transmission after the uplink receive timing.

[0061] • drx-LongCycleStartOffset: Defines when the long DRX cycle and short DRX cycle start, the long DRX cycle (i.e., drx-LongCycle), and drx-StartOffset.

[0062] •drx-ShortCycle: Short DRX cycle

[0063] • drx-ShortCycleTimer: The period during which base station 10 follows a short DRX cycle.

[0064] ·drx-RetransmissionTimerUL: The maximum period until an authorization for uplink retransmission is received.

[0065] ·drx-HARQ-RTT-TimerUL: The minimum period until an uplink retransmission authorization can be expected.

[0066] When intermittent reception at the base station becomes effective, the base station 10 can receive the uplink channel transmitted from the terminal 20 when executing drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL.

[0067] When the base station intermittently receives data, the terminal 20 can perform any of the following actions.

[0068] <Option 1>

[0069] Terminal 20 can perform actions that envision intermittent reception from the base station. Specifically, terminal 20 identifies the state of intermittent reception from the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception from the base station. Further details regarding DCI-based indications will be described later in Embodiment 3.

[0070] When the intermittent reception of the base station becomes effective, the terminal 20 can transmit the uplink channel during the execution of drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL.

[0071] <Option 2>

[0072] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0073] Furthermore, base station 10 can perform scheduling or settings that take into account intermittent base station reception when it is effective, or it can perform scheduling or settings that are unrelated to intermittent base station reception. When scheduling or settings that take intermittent base station reception into account are performed, the intermittent base station reception function is achieved even if terminal 20 ignores intermittent base station reception. Conversely, when scheduling or settings that do not take intermittent base station reception into account are not performed, if terminal 20 ignores intermittent base station reception, useless signals are transmitted, thus wasting the power consumption of terminal 20.

[0074] On the other hand, even when intermittent reception by the base station is ineffective, the base station 10 can still receive the uplink channel transmitted from the terminal 20 regardless of the intermittent reception parameters. That is, the base station 10 can also maintain the state of having its receiving unit enabled and continuously receive the uplink channel from the terminal 20.

[0075] In the event of intermittent failure of base station reception, terminal 20 may perform any of the following actions.

[0076] <Option 1>

[0077] Terminal 20 can perform actions that envision intermittent reception from the base station. Specifically, terminal 20 identifies the state of intermittent reception from the base station via RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 envisions receiving DCI from base station 10 indicating the state of intermittent reception from the base station. Further details regarding DCI-based indications will be described later in Embodiment 3.

[0078] In the event that the base station intermittent reception is invalid, the terminal 20 performs uplink transmission as scheduled or set by the base station 10, regardless of the state of the intermittent reception.

[0079] <Option 2>

[0080] Terminal 20 may also ignore intermittent reception from the base station. Specifically, terminal 20 performs uplink transmission as scheduled or set by base station 10, regardless of the state of intermittent reception from the base station.

[0081] In addition, base station 10 may also receive terminal assistance information in order to determine the aforementioned parameter values ​​during the wake-up / sleep period.

[0082] Terminal assistance information can be a periodic representation of terminal services. Base station 10 can receive terminal assistance information at higher layers. Base station 10 considers the terminal assistance information reported by terminal 20 to determine the value of parameters.

[0083] Terminal 20 can also send terminal auxiliary information such as the service cycle of the terminal to base station 10.

[0084] According to this embodiment, intermittent reception of base station 10 can be achieved.

[0085] (Example 2)

[0086] This embodiment illustrates an example of a method for triggering intermittent reception at a base station.

[0087] The activation / deactivation of intermittent base station reception can also be performed using any of the following options.

[0088] <Option 1>

[0089] Base station 10 can enable / disable intermittent reception of the base station when the RRC parameter representing the enable / disable of intermittent reception of the base station is set by terminal 20 or other network nodes (such as the core network or other base stations).

[0090] <Option 2>

[0091] Base station 10 can also enable / disable intermittent reception when it receives a MAC-CE command indicating the enable / disable of intermittent reception from terminal 20 or other network nodes (such as the core network or other base stations).

[0092] <Option 3>

[0093] When base station 10 receives a UCI included in PUCCH or PUSCH from terminal 20, it can enable / disable intermittent reception of base station based on the enable / disable instruction of intermittent reception of base station included in the UCI.

[0094] The UCI that includes the indication of the activation / deactivation of intermittent base station reception can be a newly defined UCI type, different from the previous ones. Alternatively, the UCI can be the same UCI type as before, such as HARQ-ACK, CSI, SR, etc.

[0095] Terminal 20 can send a PUCCH or PUSCH to base station 10 to enable / deactivate intermittent reception of the base station.

[0096] Terminal 20 can receive a DCI (Distributed Intermittent Receiver Code) representing the intermittent reception state of the base station from base station 10 to identify whether the UCI-based indication has been correctly decoded by base station 10, and whether there is a common understanding of the intermittent reception state between base station 10 and terminal 20. Further details regarding the DCI will be described later in Embodiment 3.

[0097] <Option 4>

[0098] Under certain conditions, base station 10 can enable / disable intermittent reception. For example, base station 10 can enable intermittent reception if it does not receive uplink channel from terminal 20 for a certain period of time. This certain period of time can be a symbol, time slot, subframe, millisecond, second, etc.

[0099] In order to achieve a shared understanding between base station 10 and terminal 20 regarding the state of intermittent reception at the base station, terminal 20 may also receive a DCI (Distributed Information Citation) indicating the state of intermittent reception at the base station from base station 10. Further details regarding the DCI will be described later in Embodiment 3.

[0100] <Option 5>

[0101] Base station 10 can enable / disable intermittent reception by combining the above options.

[0102] In addition, as a process of enabling / disabling intermittent reception at the base station, the base station 10 may also perform any of the following actions.

[0103] <Option 1>

[0104] Base station 10 can immediately enable / disable intermittent base station reception when executing any of the aforementioned trigger options for enabling / disabling intermittent base station reception.

[0105] <Option 2>

[0106] Base station 10 can also receive a timing indication for the activation / deactivation of intermittent base station reception, which can be a certain time interval or a specified moment from the date of receiving the indication. The unit for specifying the time interval or moment can be a symbol, time slot, subframe, millisecond, second, etc. That is, base station 10 can also activate / deactivate intermittent base station reception at a specified time when executing any of the aforementioned trigger options for activating / deactivating intermittent base station reception.

[0107] <Option 3>

[0108] Base station 10 can enable / disable intermittent reception based on a newly introduced timer. The timers for enabling / disabling reception can be the same or different. The unit of the timer can be a symbol, time slot, subframe, millisecond, second, etc. Base station 10 or other network nodes such as terminal 20 can set the timer via RRC, or specify the timer via MAC-CE or UCI / DCI.

[0109] That is, when any of the aforementioned trigger options for enabling / disabling intermittent base station reception are executed, a timer is executed. When the timer expires, base station 10 can enable / disable intermittent base station reception.

[0110] The advantages of a timer will be explained. Even if intermittent reception by the base station is indicated as valid, due to processing by terminal 20, the actual uplink transmission from terminal 20 may sometimes occur with a certain delay after the indication. Even in such cases, by introducing a timer, intermittent reception by the base station can be made valid after a certain period of time, thus reducing the power consumption of base station 10.

[0111] Furthermore, even if intermittent base station reception is indicated as invalid, actual uplink transmissions from terminal 20 may continue for a period of time after the indication due to processing by terminal 20. Even in such cases, by introducing a timer, intermittent base station reception can be invalidated after a certain period, thus improving the performance of terminal 20.

[0112] According to this embodiment, it is possible to trigger intermittent reception of the base station, and to perform the action of activating / deactivating the base station when it is triggered.

[0113] (Example 3)

[0114] In this embodiment, an example is described whereby a terminal receives an indication related to intermittent reception by a base station via a DCI.

[0115] If terminal 20 identifies the intermittent reception state of the base station and this is mutually understood by both terminal 20 and base station 10, a mechanism needs to be considered to indicate the intermittent reception state from base station 10 to terminal 20. DCI-based indication is expected to provide timely guidance.

[0116] In addition, as a mutually understood advantage, when the base station is intermittently receiving data, the terminal 20 can stop uplink transmission, thus saving power consumption of the terminal 20.

[0117] To indicate the intermittent reception state of the base station, a new RNTI can be introduced. The new RNTI can be set as gNBCDRX-RNTI (GC-RNTI) for example.

[0118] Furthermore, the introduction of the DCI field can be any of the following options.

[0119] <Option 1>

[0120] A new DCI field can be introduced to represent the intermittent reception status of the base station. The introduced DCI field can be 1 bit in size, with "1" representing a valid state and "0" representing an invalid state. Alternatively, it can be the other way around.

[0121] <Option 2>

[0122] Alternatively, the new DCI field can be omitted. That is, the intermittent reception status of the base station can be represented by existing fields. For example, if the corresponding DCI format is scrambled with a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0", the terminal 20 can still recognize that the intermittent reception status of the base station is valid.

[0123] Furthermore, for example, if the corresponding DCI format is scrambled with a new RNTI such as GC-RNTI, and the HPN and RV fields are all set to "0" and the MCS field is all set to "1", the terminal 20 can also recognize that the intermittent reception state of the base station is invalid.

[0124] In addition, the corresponding DCI format can be any of the following options.

[0125] <Option 1>

[0126] It can be the DCI inherent in terminal 20.

[0127] <Option 1-1>

[0128] Base station 10 can also use a new DCI format, different from the past, to represent the state of intermittent reception of the base station.

[0129] <Options 1-2>

[0130] Base station 10 can use existing DCI formats 0_1, 0_2, 1_1, 1_2 or other DCI formats to represent the state of intermittent reception of the base station.

[0131] <Option 2>

[0132] It can be a group-common DCI of terminal 20.

[0133] <Option 2-1>

[0134] Base station 10 can also use a new DCI format, different from the previous one, to represent the state of intermittent reception by the base station. The aforementioned new DCI field can also be introduced in the new DCI format together with other new DCI fields used for power-saving technology of base station 10. Base station 10 can scramble the new DCI format using the aforementioned new RNTI (GC-RNTI, etc.).

[0135] <Option 2-2>

[0136] Base station 10 can also use the conventional DCI format 2_6 or other common DCI formats to represent the intermittent reception status of the base station.

[0137] When using DCI format 2_6, previous DCI fields can be reinterpreted to indicate the state of intermittent reception by the base station. For example, the "Wake-up indication" can be reinterpreted. Alternatively, "1" can represent a valid state and "0" a invalid state, or vice versa.

[0138] To distinguish it, base station 10 may also scramble DCI format 2_6 using the aforementioned new RNTI (GC-RNTI, etc.) instead of PS-RNTI.

[0139] According to this embodiment, terminal 20 identifies the intermittent reception state of the base station, thereby enabling both terminal 20 and base station 10 to understand it together.

[0140] (Example 4)

[0141] In this embodiment, an example is described of mutually reporting capability information of the base station or terminal related to intermittent reception of the base station.

[0142] The following capability information can be introduced.

[0143] Base station capability information representing the capabilities of base station 10 can be introduced. That is, base station 10 sends base station capability information to terminal 20 or other network nodes. Terminal 20 or other network nodes that receive the base station capability information can infer the capabilities of base station 10 based on the received base station capability information.

[0144] Base station capability information may also include information indicating whether intermittent reception by the base station is supported. Additionally, base station capability information indicating whether intermittent reception by the base station is supported may also be introduced, along with DCI-indicated base station capability information.

[0145] In addition, the following terminal capability information can also be introduced. For example, terminal capability information indicating whether intermittent base station reception is supported can be introduced. Furthermore, terminal capability information indicating whether intermittent base station reception is supported can also be introduced.

[0146] Terminal 20 can also identify whether the intermittent base station reception function is effective or ineffective if it has the terminal capability to support the status identification of intermittent base station reception. For example, terminal 20 can also perform the operation of option 1 shown in embodiment 1. In addition, if terminal 20 does not have the terminal capability to support the status identification of intermittent base station reception, it can also perform the operation of option 2 shown in embodiment 1.

[0147] In addition, terminal capability information indicating whether DCI indications, which indicate the state of intermittent reception by the base station, are supported can also be introduced. Furthermore, terminal capability information indicating whether new terminal-specific / group-common DCI formats are supported can also be introduced.

[0148] The dependency relationship between base station capability information and terminal capability information can be any of the following options.

[0149] <Option 1>

[0150] To enable intermittent base station reception, it can also be configured to require separate reports from both the base station capability information and the terminal capability information indicating support for intermittent base station reception.

[0151] <Option 2>

[0152] To utilize intermittent base station reception, it is also possible to report only either the base station capability information or the terminal capability information that indicates support for intermittent base station reception.

[0153] According to this embodiment, they can mutually report information about the capabilities of the base station or the terminal related to intermittent reception by the base station.

[0154] The terminal capabilities in the above embodiments can be limited to the case where terminal 20 is a feature-reduced terminal, or they can be applied to the case where terminal 20 is not a feature-reduced terminal.

[0155] (Summary of this implementation method 2)

[0156] Furthermore, to reduce power consumption in base station 10, cell DTX / DRX is being studied. For example, the alignment of cell DTX / DRX with UE-DRX in RRC connection mode and information exchange between nodes related to cell DTX / DRX are being investigated. Additionally, cell DTX / DRX can be replaced by cell DTX and cell DRX, or by cell DTX or cell DRX.

[0157] Mechanisms for enabling or disabling the transceiver units of base station 10 are important for reducing power consumption in base station 10. Adaptive technologies for DL ​​transmission and UL reception are being investigated to reduce power consumption in base station 10.

[0158] Cell DTX / DRX is useful for achieving adaptive DL transmission and UL reception. However, the operational details of cell DTX / DRX are not clearly defined. Therefore, embodiments 5 to 8 are described below as specific implementations related to cell DTX / DRX.

[0159] (Example 5)

[0160] In Example 5, the definition of cell DTX / DRX is explained. Cell DRX can also be defined as in Examples 1-4 above. Whether cell DRX is implemented is determined by higher-layer parameters, and the period, start time slot, offset, and duration can also be set. Furthermore, the application of cell DRX can also be determined based on semi-static, dynamic, or flexible network conditions.

[0161] Cell DTX can also be defined as described later. Whether to perform cell DTX is determined by higher-layer parameters, and the period, start time slot, offset, and duration can also be set. Furthermore, the application of cell DTX can be determined based on semi-static, dynamic, or flexible network conditions.

[0162] <Option 1>

[0163] Figure 6 This is a diagram illustrating the intermittent transmission of a base station in Embodiment 5 of the present invention. (See diagram for example.) Figure 6 As shown, the period during which the base station 10 invalidates or activates its own transmission unit can also be introduced as cell DTX.

[0164] The invalidated transmission unit and / or parameter can be per port, per panel, per beam, per carrier, or per cell. Cell DTX can be defined by some or all of the parameters shown in 1)-6) below. The unit of this parameter can be a symbol, time slot, subframe, millisecond, or second, or other units. The units can be the same or different among these parameters.

[0165] 1) dtx-onDurationTimer: The period starting from the beginning of the DTX cycle.

[0166] 2) dtx-SlotOffset: The delay period before dtx-onDurationTimer starts.

[0167] 3) dtx-InactivityTimer: The period that begins after the DL transmission timing (the timing when base station 10 performs DL transmission and terminal 20 receives DL transmission).

[0168] 4) dtx-LongCycleStartOffset: Defines the dtx-StartOffset for the start of the long DTX cycle (i.e., dtx-LongCycle) and the long and short DTX cycles.

[0169] 5) dtx-ShortCycle: Short DTX cycle. This can also be optional.

[0170] 6) dtx-ShortCycleTimer: The period during which base station 10 executes a short DTX cycle. A short DTX begins when DL reception occurs during a long DTX. This can also be optional.

[0171] Figure 7 This is a diagram illustrating the parameters of Embodiment 5 of the present invention. For example... Figure 7As shown, starting from the beginning of dtx-LongCycle, dtx-onDurationTimer becomes the active time after dtx-SlotOffset. If a DL reception occurs within dtx-LonCycle, the active time ends after dtx-InactivityTimer from the point of DL reception, and dtx-ShortCycle begins. If a DL reception occurs within dtx-ShortCycleTimer, dtx-ShortCycle continues. If no DL reception occurs within dtx-ShortCycleTimer, dtx-LongCycle begins.

[0172] When cell DTX is active, base station 10 can also transmit DL channel or DL ​​signal while dtx-onDurationTimer or dtx-InactivityTimer is in operation. As an action of terminal 20, when cell DTX is active, terminal 20 can receive DL channel or DL ​​signal while dtx-onDurationTimer or dtx-InactivityTimer is in operation. Terminal 20 can also assume receiving DL channel or DL ​​signal when dtx-onDurationTimer or dtx-InactivityTimer is not in operation.

[0173] When the cell DTX is disabled, terminal 20 can also receive the DL channel or DL ​​signal in the same way as notifying or setting the base station 10.

[0174] The DL channel or DL ​​signal can be any one of PDCCH, PDSCH, SPS (Semi Persistent Scheduling)-PDSCH, CSI-RS (Channel State Information - Reference Signal), PT-RS (Phase Tracking - Reference Signal), or DM-RS (Demodulation - Reference Signal).

[0175] The UL channel or UL signal can be any one of PRACH, PUCCH, PUSCH, CG-PUSCH, SRS, PT-RS, or DM-RS.

[0176] (Example 6)

[0177] In Example 6, the cell DTX / DRX settings are explained.

[0178] <Option 1>

[0179] Joint configuration can be performed. Cell DTX and cell DRX can be jointly configured through common parameters. With common parameters (e.g., CellDTXDRX-Config) set, cell DTX and DRX can be enabled. Terminal 20 can also appropriately perform the actions of Embodiment 5.

[0180] Public parameters may include any one or both of the information elements shown in 1) and 2) below.

[0181] 1) Common parameters in DTX and DRX. Some parameters are common to both DTX and DRX. For example, parameters representing the on-duration timer are common to both DTX and DRX. Similarly, parameters representing the period are also common to both DTX and DRX.

[0182] 2) Separate parameters in DTX and DRX. Some parameters can be set independently in DTX and DRX. For example, the parameter representing the slot offset can be set independently in DTX and DRX.

[0183] Option 1 can reduce the overhead of RRC signaling.

[0184] <Option 2>

[0185] Separate settings can also be performed. Cell DTX and cell DRX can be configured independently using separate parameters. Cell DTX can be enabled when DTX-oriented parameters (e.g., CellDTX-Config) are set. Cell DRX can be enabled when DRX-oriented parameters (e.g., CellDRX-Config) are set. DTX-oriented parameters can include those described in Example 5. DRX-oriented parameters can also include those described in Example 1.

[0186] Option 2 provides greater flexibility in setting up cell DTX or cell DRX.

[0187] (Example 7)

[0188] In Example 7, the activation or deactivation of cell DTX / DRX is explained. When cell DTX and cell DRX are jointly configured (Option 1 of Example 6), cell DTX and cell DRX can be activated or deactivated as follows.

[0189] <Option 1>

[0190] Cell DTX and cell DRX can be enabled or disabled via RRC signaling. With RRC parameters set, cell DTX and cell DRX can be enabled or disabled. For example, these RRC parameters can be common parameters from Example 6 (e.g., CellDTXDRX-Config).

[0191] <Option 2>

[0192] Cell DTX and cell DRX can be enabled or disabled via MAC-CE. When terminal 20 receives MAC-CE, cell DTX and cell DRX can be enabled or disabled.

[0193] <Option 3>

[0194] Cell DTX and cell DRX can be enabled or disabled via DCI. Terminal 20 can also be dynamically notified via DCI that cell DTX and cell DRX have been enabled or disabled. This DCI-based notification can be executed as shown in 1)-4) below.

[0195] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0196] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

[0197] 3) RNTI can be an existing RNTI (e.g., C-RNTI, SFI-RNTI) or a new RNTI can be defined.

[0198] 4) DCI fields can be groups of existing fields and / or new fields. For example, in the case of groups of existing fields, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable cell DTX and cell DRX.

[0199] Alt.1) When scrambling using an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can dynamically enable cell DTX and cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", terminal 20 can dynamically disable cell DTX and cell DRX.

[0200] Alt.2) When scrambling is performed using a new RNTI, and for example, all HPNs are set to "0" and all RVs are set to "00", terminal 20 can dynamically enable cell DTX and cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can dynamically disable cell DTX and cell DRX.

[0201] For example, with a new DCI field, the cell DTX and cell DRX can be enabled or disabled using this new DCI field. This new DCI field can also be called the "Cell DTX / DRX identifier". For example, if the cell DTX / DRX identifier is set to "1", the terminal 20 can dynamically enable the cell DTX and cell DRX. Alternatively, if the cell DTX / DRX identifier is set to "0", the terminal 20 can dynamically disable the cell DTX and cell DRX. Furthermore, the DCI including this new DCI field can be scrambled using either the existing RNTI or the new RNTI.

[0202] Furthermore, when cell DTX and cell DRX are configured separately (option 2 of embodiment 6), cell DTX and cell DRX can also be enabled or disabled as follows.

[0203] <Option 1>

[0204] Cell DTX or cell DRX can be enabled or disabled via RRC signaling. With RRC parameters set, cell DTX or cell DRX can be enabled or disabled. For example, these RRC parameters can be the separate parameters in Example 6 (e.g., CellDTX-Config, CellDRX-Config).

[0205] <Option 2>

[0206] MAC-CE can be used to enable or disable cell DTX or cell DRX. When terminal 20 receives MAC-CE, cell DTX or cell DRX can be enabled or disabled.

[0207] <Option 3>

[0208] Terminal 20 can also be dynamically notified via DCI that cell DTX or cell DRX has been activated or deactivated. This DCI-based notification can be executed as shown in 1)-4) below.

[0209] 1) The DCI format can be either a UE-specific DCI format or a group-common DCI format.

[0210] 2) The DCI format can be an existing format (e.g., DCI format 1_1, 1_2, 2_0) or a newly defined one (e.g., 1_x, 2_x).

[0211] 3) RNTI can be an existing RNTI (e.g., C-RNTI, SFI-RNTI) or a new RNTI can be defined.

[0212] 4) DCI fields can be groups of existing fields and / or new fields. For example, different groups of DCI fields can be used to represent either cell DTX or cell DRX in order to enable or disable cell DTX or cell DRX. For example, in the case of existing field groups, as shown in Alt.1) and Alt.2) below, some fields can be used to enable or disable cell DTX and cell DRX.

[0213] Alt.1) When scrambling using an existing RNTI such as CS-RNTI, and for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can dynamically enable cell DTX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can dynamically disable cell DTX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", and all TDRAs are set to "1", terminal 20 can dynamically enable cell DRX. Furthermore, for example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all TDRAs are set to "1", the terminal 20 can dynamically disable the cell DRX.

[0214] Additionally, the PRI and TDRA fields can be added to indicate which of the CG-PUSCH / SPS-PDSCH and cell DTX / cell DRX is the object for an active or inactive DCI.

[0215] Additionally, fields that are used in the same way as PRI and TDRA as described above (e.g., TDRA) can also be used to indicate which of CG-PUSCH / SPS-PDSCH and cell DTX / cell DRX is being considered. When using different DCI formats, the DCI format can be used to indicate whether the cell DTX or cell DRX is being considered. For example, DCI format 0_0 can enable or disable cell DRX, while DCI format 1_0 can enable or disable cell DTX.

[0216] Alt.2) When scrambling using the new RNTI, for example, when all HPNs are set to "0", all RVs are set to "00", and all PRIs are set to "1", terminal 20 can dynamically enable cell DTX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", all FDRAs are set to "1", and all PRIs are set to "1", terminal 20 can dynamically disable cell DTX. For example, when all HPNs are set to "0" and all RVs are set to "00", terminal 20 can also dynamically enable cell DRX. For example, when all HPNs are set to "0", all RVs are set to "00", all MCSs are set to "1", and all FDRAs are set to "1", terminal 20 can also dynamically disable cell DRX.

[0217] Additionally, while PRI is used as described above, the field added to indicate which of the cell DTX and cell DRX is being considered can be omitted. When using different DCI formats, the DCI format can be used to indicate whether the cell DTX or cell DRX is being considered. For example, DCI format 0_0 can enable or disable cell DRX, while DCI format 1_0 can enable or disable cell DTX.

[0218] For example, in the case of a new DCI field, the cell DTX or cell DRX can be enabled or disabled through this new DCI field. This new DCI field can also be called the "Cell DTX identifier" or the "Cell DRX identifier".

[0219] When cell DTX and cell DRX are separately notified through separate fields, for example, if the cell DTX identifier is set to "1", terminal 20 can also dynamically enable cell DTX. Furthermore, for example, if the cell DTX identifier is set to "0", terminal 20 can also dynamically disable cell DTX. Similarly, if the cell DRX identifier is set to "1", terminal 20 can also dynamically enable cell DRX. Furthermore, for example, if the cell DRX identifier is set to "0", terminal 20 can also dynamically disable cell DRX.

[0220] Furthermore, this new DCI field can also be referred to as the "Cell DTX / DRX identifier". When the cell DTX and cell DRX are jointly notified through a common field, for example, when the cell DTX / DRX identifier is set to "01", terminal 20 can dynamically enable or disable the cell DTX. For example, when the cell DTX / DRX identifier is set to "10", terminal 20 can dynamically enable or disable the cell DTX. For example, when the cell DTX / DRX identifier is set to "11", terminal 20 can dynamically enable both cell DTX and cell DRX. For example, when the cell DTX / DRX identifier is set to "00", terminal 20 can dynamically enable both cell DTX and cell DRX. The bit mapping of the cell DTX and cell DRX described above can be reversed.

[0221] In addition, the DCI including this new DCI field can be scrambled using either the existing RNTI or the new RNTI.

[0222] The timing for the activation or deactivation of the application cell DTX or cell DRX notified by MAC-CE or DCI can be as shown in 1) or 2) below.

[0223] 1) Terminal 20 can immediately activate or deactivate. When notified of the activation or deactivation of cell DTX or cell DRX via MAC-CE or DCI, cell DTX or cell DRX can be activated or deactivated immediately.

[0224] 2) Terminal 20 can also activate or deactivate at the notified time. The timing of activating or deactivating cell DTX or cell DRX can be determined as an interval or a specific moment from the notified activation or deactivation time, via RRC signaling, MAC-CE, or DCI. The unit of time can be a symbol, time slot, subframe, millisecond, or second, etc. When notified of the activation or deactivation of cell DTX or cell DRX via MAC-CE or DCI, the cell DTX or cell DRX can be activated or deactivated at the pre-notified time.

[0225] (Example 8)

[0226] In Example 8, the associated operation of cell DTX / DRX and UE DRX is explained. When the time positions of cell DTX and UE DRX are not aligned, and DL transmission is not performed due to cell DTX, terminal 20 may be woken up to receive DL channel or DL ​​signal.

[0227] Therefore, the actions can also be performed as shown in options 1-5 below.

[0228] <Option 1>

[0229] If the UE DRX (e.g., DRX-Config) is configured, the terminal 20 may not assume that the cell DTX is configured.

[0230] <Option 2>

[0231] If the cell DTX is configured, the terminal 20 may not need to have the UE DRX (e.g., DRX-Config) configured. Alternatively, the cell DTX parameters can be those described in Example 6.

[0232] <Option 3>

[0233] When a UE DRX (e.g., DRX-Config) is configured, terminal 20 may not assume that the cell DTX is configured at a time location different from the UE DRX. When the time locations of the cell DTX and UE DRX are consistent, the cell DTX and UE DRX can also be configured jointly.

[0234] <Option 4>

[0235] When a cell DTX is configured, terminal 20 may not assume that a UE DRX (e.g., DRX-Config) with a time location inconsistent with the cell DTX is configured. When the time locations of the cell DTX and UE DRX are consistent, the cell DTX and UE DRX can also be configured jointly.

[0236] <Option 5>

[0237] Regardless of whether the time positions of cell DTX and UE DRX are consistent or inconsistent, cell DTX and UE DRX can be set for terminal 20. Furthermore, if cell DTX is set in addition to UE DRX, the parameters of cell DTX can be prioritized. Terminal 20 can ignore the parameters of UE DRX. Terminal 20 can also operate as in Embodiment 5. Furthermore, if cell DTX is set in addition to UE DRX, the parameters of both can be applied. Terminal 20 can also be woken up at the activation time of both cell DTX and cell DRX.

[0238] The above-mentioned "the time positions of the cell DTX and UE DRX are aligned" can also be defined as shown in option 1 or option 2 below.

[0239] <Option 1>

[0240] When the long cycle is the same in both cell DTX and UE DRX, it can also be defined as the time positions of cell DTX and UE DRX being consistent.

[0241] <Option 1-1>

[0242] Furthermore, when the long cycle is the same in both cell DTX and UE DRX, it can be defined as the time position of cell DTX and UE DRX being consistent, regardless of the activation time within the long cycle. That is, when the long cycle of cell DTX (e.g., dtx-LongCycle) and the long cycle of UE DRX (e.g., drx-LongCycle) are the same, it can be defined as the time position being consistent.

[0243] <Options 1-2>

[0244] If the long cycle is the same in both the cell DTX and UE DRX, the time position of the cell DTX and UE DRX can be defined as consistent, depending on the activation time within the long cycle. If the timers and slot offsets (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) are the same in both the cell DTX and UE DRX during the on-time period of the long cycle, the time position of the cell DTX and UE DRX can also be defined as consistent. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) can be additionally considered to determine whether these parameters satisfy this definition.

[0245] <Option 2>

[0246] Besides the long cycle, if the short cycle is the same in both cell DTX and UE DRX, it can also be defined as the time positions of cell DTX and UE DRX being consistent. Option 2 can also be applied to situations that satisfy the conditions of option 1-1 or option 1-2.

[0247] <Option 2-1>

[0248] Furthermore, when the short cycle is the same in both cell DTX and UE DRX, it can be defined as the time position of cell DTX and UE DRX being consistent, regardless of the activation time within the short cycle. That is, when the short cycle (e.g., dtx-ShortCycle) of cell DTX is the same as the short cycle (e.g., drx-ShortCycle) of UE DRX, it can be defined as the time position being consistent.

[0249] <Option 2-2>

[0250] When the short cycle is the same in both the cell DTX and UE DRX, the time position of the cell DTX and UE DRX can also be defined as consistent, depending on the activation time within the short cycle. When the short cycle timer and short cycle (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same in both the cell DTX and UE DRX, the time position of the cell DTX and UE DRX can be defined as consistent.

[0251] (Summary of this implementation method 3)

[0252] (Example 9)

[0253] Here, the following technologies are studied regarding network energy saving (NES).

[0254] On-demand SSB and / or SIB1 transmission is under investigation. For example, the transmission of on-demand S1B1 or SSB to idle UEs, and the transmission of on-demand SSB and other DL signaling to connected UEs in a SCell, are under investigation. Furthermore, SSB can also be replaced with an SS / PBCH block. Additionally, " / " can be replaced with any of "and / or", "and", or "or".

[0255] To trigger on-demand SSB and / or SIB1 transmission, the methods shown in 1)-3) below are being investigated.

[0256] 1) Triggered based on the UE's UL-WUS (Wake up signal). For example, it can be used in non-CA scenarios, or it can be an existing signal or a new signal.

[0257] 2) Triggered based on the backhaul signal that notifies the cell to be ON or OFF.

[0258] 3) Triggering based on SCell activation or deactivation signaling.

[0259] Furthermore, the use of no SSB and / or SIB1 can also be implemented in multi-carrier scenarios. For example, assuming that the UE can use other carriers (e.g., anchor cells), idle or inactive UEs can also operate without SSB and / or SIB1 in non-anchor NES cells.

[0260] The choice between using on-demand SSB and / or SIB1 transmission, or no SSB and / or SIB1, can be determined based on the advantages in the target scenario. Furthermore, optimization of common signal and / or channel transmission is being investigated.

[0261] Figure 8 This is a timing diagram of Example (1) of OSI (On-demand system information) transmission in Embodiment 9 of the present invention. Figure 8This is an example of an SIB request based on MSG1 (Message 1 in the random access procedure), which can be envisioned as CFRA (Contention-free Random Access). In step S101, terminal 20 sends a system information request indicating a specific SIB type to base station 10 by using pre-allocated PRACH resources and a preamble for MSG1. In step S102, base station 10 sends MSG2 to terminal 20 as a response. In step S103, base station 10 sends the requested system information to terminal 20.

[0262] Figure 9 This is a timing diagram for illustrating Example (2) of OSI transmission in Embodiment 9 of the present invention. Figure 9 This is an example of an SIB request based on MSG3 (Message 3 in the random access procedure), which can be envisioned as CBRA (Contention-based Random Access). In step S201, terminal 20 sends MSG1 to base station 10. In step S202, base station 10 sends MSG2 to terminal 20. In step S203, terminal 20 sends MSG3 containing information indicating a system information request to base station 10. In step S204, base station 10 sends MSG4 to terminal 20. In step S205, base station 10 sends the requested system information to terminal 20.

[0263] Figure 10 This diagram illustrates an example of an on-demand SSB according to Embodiment 9 of the present invention. The on-demand SSB can be notified or transmitted during various carrier aggregation processes. It is envisioned that the basic information of the on-demand SSB is set via RRC signaling, and then an activation command is notified just before actual transmission via MAC-CE, etc.

[0264] like Figure 10 As shown, regarding actions related to On-Demand SSB, as scenario #2, the actions are being studied when the SCell is set to an inactive state. As scenario #2A, the actions are being studied when a SCell activation command is received. As scenario #3A, the actions are being studied from the time the SCell activation command is received until the SCell activation is complete. As scenario #3B, the actions are being studied when the SCell activation is complete or after the SCell activation is complete.

[0265] Alternatively, upon receiving the SCell activation command in scenario #2A, information related to the On-Demand SSB can be notified at a set time. The On-Demand SSB sent during SCell activation can be used for SCell activation.

[0266] In addition, similar to the functionality used in SCell activation by on-demand SSB, fast SCell activation using TRS (CSI-RS for tracking) is being investigated.

[0267] Here, when the UE uses SSBs sent on demand or burstily (e.g., not periodically or not semi-statically) for SCell activation, the resource setting method, the resource characteristics and configuration (e.g., number, interval, etc.) of the SSBs envisioned by the UE are unclear.

[0268] By ensuring consistency in the resource setting method and understanding of on-demand SSBs used for SCell activation between the BS and UE, actions (such as L3 / L1 measurement, SCell, AGC, synchronization, and channel estimation) using appropriate SSBs or on-demand SSBs can be performed between the UE and BS.

[0269] For example, on-demand SSB resources for SCell activation can be configured. The UE's actions upon receiving a notification of on-demand SSB can also be specified. The resource configuration for the on-demand SSB envisioned by the UE can be determined.

[0270] In addition, an existing SSB can refer to any one of the following 1)-4), or any combination of the following 1)-4).

[0271] 1) SSB configured via RRC signaling prior to version 18

[0272] 2) Service Communities

[0273] 3) Cell-defined SSB or non-cell-defined SSB

[0274] 4) Serving cell config under SCell configuration

[0275] Additionally, an on-demand SSB can refer to any one of 1)-12) below, or any combination of 1)-12) below, or an SSB triggered in any one of 1)-12) below, or an SSB triggered in any combination of 1)-12) below. Furthermore, " / " can be replaced with "and / or", "and", or "or".

[0276] 1) Trigger SSB sending itself.

[0277] 2) Triggering SSB transmission within a certain period X, SSB transmission above or below a certain period X, or longer or shorter than a certain period X, SSB transmission with a shorter period compared to the current transmission, current setting, or the most recently received SSB by the UE, SSB transmission with a longer period compared to the current transmission, current setting, or the most recently received SSB by the UE, or maintaining SSB transmission according to the current period.

[0278] 3) Trigger the sending / non-sending of a specific SS burst (trigger the sending of an SSB at a certain time). Multiple SSB bursts can be triggered to be sent / non-sent.

[0279] 4) Trigger the sending / non-sending of an SS burst within a certain period (trigger the sending of an SSB at a certain time). Multiple SSB bursts can be triggered to be sent / non-sent.

[0280] 5) Number of SB transmissions / Fewer SSB transmissions / More SSB transmissions / Maintaining the status quo in SSB transmissions.

[0281] 6) Trigger the following SSB transmission counts within a given SS burst: fewer SSB transmissions, more SSB transmissions, or maintain the current SSB transmission count.

[0282] 7) Trigger a certain SSB.

[0283] 8) Trigger an SSB with a different index / position.

[0284] 9) Trigger a specific SSB within a specific SS burst.

[0285] 10) Trigger an SSB with a different index / position within a certain SS burst.

[0286] 11) Trigger SSB transmission with a predetermined QCL relationship with the transmitting beam / another RS.

[0287] 12) Trigger transmission of an SSB that has a predetermined QCL relationship with the transmit beam of each SSB that is different from the one used for the SSB index / location / another RS.

[0288] Additionally, On-Demand SSB can be replaced with On-Demand SIB1. Furthermore, embodiments of the present invention can be applied outside of SCell activation (e.g., before SCell activation and after SCell setup, and after SCell activation completion), and this process may not be conceived outside of SCell activation.

[0289] Figure 11This is a flowchart illustrating Example (1) of the actions related to on-demand SSB in Embodiment 9 of the present invention. In step S301, the resource for transmitting or being able to transmit on-demand SSB can be set based on predetermined parameters of predetermined dedicated signaling sent from a predetermined cell of the BS, or the information required for the resource can be obtained. The on-demand SSB can be set in association with SCell activation, and the UE can perform a predetermined SCell activation process using the on-demand SSB according to the set information.

[0290] Action 1) Resources, multiple sets of resources, or a list of resources that can be sent or sent on demand by a BS can be sent from a predetermined cell (e.g., PCell) in (A) dedicated signaling. The required information can be obtained based on the predetermined parameters. Alternatively, the predetermined parameters can be set semi-statically via RRC signaling. The required information can also be obtained based on the predetermined parameters.

[0291] In addition, (B) the on-demand SSB can be configured in association with SCell activation, and the UE can also perform a predetermined SCell activation process using the on-demand SSB based on the configured information.

[0292] (A) The predetermined parameters of the predetermined special signaling may be parameters set in the RRC Reconfiguration of the PCell, or any one of the multiple settings in the RRC signaling set and enabled / disabled by MAC-CE and / or DCI, or any one of the following parameters.

[0293] Regarding the method for setting the predetermined parameters (under which parameter the setting is located), the UE can obtain the predetermined information related to on-demand SSB from the RRC parameters set below (see Non-Patent Document 3). The BS can set the predetermined information related to on-demand SSB under the following parameters. The UE can set the following parameters.

[0294] Setting up secondary communities: sCelltoAddModList > sCellConfig > (subordinate parameters), for example, smtc Service area settings: sCellConfigCommon > ServingCellConfigCommon > (subordinate parameters), for example, Ssb-positionsInBurst Ssb-periodicyServingCell ss-PBCH-BlockPower DL-BWP settings: Parameters associated with or subordinate to DL BWP, such as BWP-DownlinkCommon [Rel-17] Non-cell defining SSB association / subordinate parameters sCellConfigDedicated(subordinate parameters), for example, Csi-measConfig Parameters associated with or subordinate to DL BWP, such as BWP-DownlinkDedicated [Rel-17] Non-cell defining SSB association / subordinate parameters • Parameters related to L3 and / or L1 measurements, for example, Settings related to CSI measurements: CSI-MeasConfig (sub-parameters) CSI-ResourceConfig NZP-CSI-RS-Resource CSI-SSB-ResourceSet >SSB-Index Settings related to measurement: MeasObjectNR (subordinate parameters) ssbFrequency ssbSubcarrierSpacing smtc1 PeriodicityAndOffset Duration smtc2 Pci-list freqBandIndicatorNR measCycleSCell The predetermined parameter can be any one of the following, or any combination thereof. The UE can obtain predetermined information related to the on-demand SSB from the RRC parameters set below, or it can include any one of the following contents. The BS can set any one of the following parameters, and the UE can also set any one of the following parameters.

[0295] • Cell ID or cell ID list: serving cell index or serving cell index list, and / or PCI or PCI list, and / or CGI or CGI list.

[0296] • Frequency or frequency list: ARFCN-NR or ARFCN-NR list.

[0297] • Feature candidates related to on-demand SSB in SCells, or feature candidates related to on-demand SSB in SCells associated with cells or frequencies.

[0298] - Period or a list of periods: for example, 10, 20, 40, 80, 160, 320, 640 [ms].

[0299] - Temporal behavior: Aperiodic, semi-peristent, periodic. Depending on the temporal behavior, other configurable characteristics can be specified, or different other characteristics can be set. For example, periodicity can be set only in periodic or semi-peristent cases, and the number of SS bursts can be set only in aperiodic cases.

[0300] -Time offset, time offset from the predetermined cell (PCell or predetermined SCell).

[0301] • Half Frame Index (e.g., 0 or 1). Indicates whether the SSB is located in the first or second half of the frame. A value of 0 indicates that the SSB is in the first half of the frame, and a value of 1 indicates that the SSB is in the second half of the frame.

[0302] • Subframe Offset (integerSubframeOffset). Represents the boundary offset of the subframe of the cell transmitting SSB.

[0303] • SFN (System Frame Number) 0 offset (sfn0-Offset) represents the time offset of SFN0 slot 0 relative to SFN0 slot 0 of PCell or the intended serving cell.

[0304] • SFN Offset. Represents the SFN offset relative to the PCell transmitting the SSB or the intended serving cell. This offset indicates the total number of radio frames from the start of radio frame #0 of the PCell or the intended serving cell to the start of radio frame #0 of the cell transmitting the most recent subsequent SSB.

[0305] • Offset between SFN and SSB (sfn-SSB-Offset). Represents the SFN offset of the transmitted SSB relative to the start of the SSB period. A value of 0 indicates that the SSB is transmitted in the initial SFN. A value of 1 indicates that the SSB is transmitted in the second SFN (9th SFN). The network sets this field according to the SSB period so that the notified system frames do not exceed the set SSB period.

[0306] • Symbol offset or slot offset

[0307] In addition, negative values ​​can be set, and other parameters can be used to set parameters representing the absolute value of the offset and parameters representing positive and negative values. Parameters can also be set to indicate that the offset is below or within a certain value.

[0308] - A certain SS burst (at a certain time). After triggering, it triggers 1, 2, 3, ..., N SS bursts or SSB transmissions, or triggers M cycles of SSB transmissions, or triggers X [ms] SSB transmissions.

[0309] • When Y bitmaps are notified and the bits are 0 or 1, SS bursts or multiple SS bursts can also be sent at the corresponding time.

[0310] Regarding the bitmap, each bit can represent one or a predetermined number of SS bursts.

[0311] - The time and / or frequency gap between a certain SS burst (at a certain time) or multiple SS bursts.

[0312] • Alternatively, an integer N can be set in units of symbols, time slots, subframes, half-frames, frames, radio frames, SFN, HFN (Hyper Frame Number), milliseconds, sub-milliseconds, or seconds. The gap can be applied uniformly to multiple time intervals between SS bursts (e.g., setting more than three SS bursts), or multiple gaps can be set and applied independently to multiple time intervals (in this case, the range of SS bursts applying a certain gap #X can be set by index, time width, or number of times). When this gap is set, the UE can interpret it as setting two or more SS bursts. The start point of this gap can be the start or end position of the previous SS burst's transmission, and the end point of the gap can be the start or end position of the subsequent SS burst's transmission. In addition, the start / end position of transmission can be a symbol, time slot, subframe, half frame, frame, radio frame, SFN, HFN, millisecond, sub-millisecond or second where an SS burst exists, or it can be a symbol of the SSB index or position where an SS burst actually exists. The gap unit and the gap start and end position can be specified / set in the same unit.

[0313] - A specific SSB location or number of transmissions, or an SSB index, location, or number of transmissions within a specific SS burst.

[0314] - Transmit beams applied to each SSB, transmit beams applied to SSBs with different SSB indices or locations, envisioned receive beams, and reference signals with envisioned predetermined QCL relationships (e.g., type D).

[0315] • Whether beam repetition is set, the RS that can achieve the predetermined QCL relationship can be only a specific RS (e.g., TRS or CSI-RS that is not set to repetition, transmitted within X symbols / slots, or within the same PRB or Y PRB frequencies).

[0316] The above-mentioned (B) association setting for on-demand SSB and SCell activation means that it can be used according to the following SCell status, each use case, and any combination of the following (assuming it is sent). The on-demand SSB, resource, or list can also be set independently. The on-demand SSB, resource, or list used by the UE for SCell activation can be associated through any of the above parameters (e.g., Csi-measConfig) set in the SCell that sends the PCell or on-demand SSB.

[0317] The SCell status can be any of the following: SCell activated (and in activation), SCell before activation, SCell during activation, SCell in dormancy, or SCell deactivated.

[0318] Use cases can be any of the following: SCell activation, L1 measurement, L3 measurement, time or frequency synchronization for SCell, recovery from sleep for channel estimation (QCL), or migration of known cells.

[0319] Action 2) Figure 12 This is a flowchart illustrating Example (2) of the actions related to on-demand SSB in Embodiment 9 of the present invention. In step S601, when the UE receives a signaling instruction to activate a predetermined SCell from a predetermined cell of the BS, the signaling notifies the predetermined content. In step S602, the UE may envision that the on-demand SSB set during a predetermined period or after a predetermined delay is sent, and may also perform predetermined SCell activation using the on-demand SSB based on this envision. In addition, the SCell activation may be fast SCell activation.

[0320] When the UE receives (A) signaling instructing the activation of a predetermined SCell from a predetermined cell (e.g., PCell) of the BS, and if the signaling notifies (B) predetermined content (including predetermined parameters), (C) the UE may envision that the on-demand SSB notified and / or set after a predetermined period or predetermined delay will be sent. Based on these assumptions, the UE may perform (D) the predetermined SCell activation procedure (or SCell-related procedure) using the on-demand SSB.

[0321] (A) The signaling indicating the activation of the scheduled SCell can be any one of the following, or any combination thereof.

[0322] • RRC signaling, RRC signaling containing settings to activate or deactivate SCells, RRC signaling to set up on-demand SSBs, or RRC signaling containing settings to activate or deactivate on-demand SSBs.

[0323] • MAC-CE that enables or disables a SCell, MAC-CE that enables or disables an Enhanced SCell, MAC-CE that enables or disables a Rel-17 Enhanced SCell, MAC-CE that enables or disables an On-Demand SSB, MAC-CE that enables or disables both an On-Demand SSB and a SCell, MAC-CE that enables or disables a Rel-19 On-Demand SSB, or MAC-CE that enables or disables both a Rel-19 On-Demand SSB and a SCell. The signaling indicating the activation of a predetermined SCell can be signaling that notifies either the activation or deactivation of the SCell or the transmission of an On-Demand SSB, or it can be limited to signaling that includes the notified parameters, or it can be limited to signaling that indicates activation (e.g., the field of the predetermined MAC-CE is 1).

[0324] • Group-common or UE-specific DCI, or group-common or UE-specific DCI sent by the notification on demand SSB.

[0325] (B) The pre-defined content or pre-defined parameters notified by the signaling can be any one of the following or any combination thereof.

[0326] Cell ID or cell ID list: Serving cell index or ID and / or serving cell index or ID list and / or PCI and / or PCI list and / or CGI and / or CGI list and / or SCell index or ID list

[0327] Frequency or On-Demand SSB, Frequency or On-Demand SSB List: This lists ARFCN-NR, ARFCN-NR list, smtc, smtc ID, measobject, measobject ID, CSI-RS resource, CSI-RS resource set, CSI-RS resource set list, CSI-RS resource index or ID, SSB, SSB index, On-Demand SSB settings, On-Demand SSB settings set to the ID or index of the list of sets.

[0328] On-demand SSB features: The setting of any one or more lists described in Action 1) can be notified by one or more indices, and in the absence of notification, the 0th (e.g., index 0 or the first) of the RRC setting can also be implicitly notified.

[0329] (C) The scheduled period / scheduled delay may be after the scheduled time width described below from the scheduled reference point, or it may be during that time.

[0330] The reference point can be any of the following: the moment when the UE receives a predetermined setting, notification, or signaling from the BS, or after receiving it, the moment when the UE sends or sends a predetermined UL response to the signaling from the BS, or after sending it, or a reference time (SFN, slot number, symbol number) set by the BS.

[0331] The time width can be any of the following: a time width set by the BS, a time width specified by the specification, a time width determined by the UE's capabilities, a time width defined by a predetermined time unit X (time window), a time width defined by a predetermined time unit X that differs according to the SCS (Signal Classification System), a time width defined by a predetermined time unit X set by signaling through the BS, or a time width defined by a predetermined time unit X that differs according to the UE's UL response. The time width can be specified or set by any of the following: sub-milliseconds, milliseconds, seconds, symbols, time slots, subframes, frames, or SFNs.

[0332] The reference point and / or time width can be counted in any of the DL signaling, UL response, PCell, pre-defined serving cell, or SCell transmitting on-demand SSB. A pre-defined time or gap offset can be applied, which can be the reference slot 'n+k' or the processing delay of MAC-CE.

[0333] (D) The pre-defined SCell activation procedure (or SCell-related procedure) using the on-demand SSB can be any of the following.

[0334] • Attempt to receive SSB, obtain SSB's DMRS and / or PBCH and / or associated SIB1, cell identification, cell ID identification, cell search.

[0335] • Channel estimation using time-frequency synchronization, AGC, channel estimation, and QCL relationships.

[0336] • The pre-defined action related to SCell can be any of the following, or it can be a pre-defined action that satisfies the RAN4 and / or RRM requirements involved in any one of the actions.

[0337] - SCell addition, SCell release

[0338] -SCell activation and SCell deactivation

[0339] • The predetermined action related to L1 or L3 measurement can be any of the following, or it can be a predetermined action that satisfies the RAN4 and / or RRM requirements involved in any one of the actions.

[0340] -L1 / CSI measurements, L3 measurements, L3 measurements during RRC idle and / or RRC connected (e.g., RSRP measurements, RSRQ measurements, SINR measurements), L3 measurements of CSI-RS and / or SSB.

[0341] Furthermore, the scheduled period can be any of the following, or it can be determined based on the scheduled parameters set from the BS.

[0342] The predetermined period can also be a time span predetermined from a predetermined reference point. The predetermined reference point can be a predetermined DL / UL signal transmission / reception time and / or a reference time (SFN, slot number, symbol number) set by the BS.

[0343] The unit for time direction can be symbol, time slot, radio frame, system frame, sub-millisecond, millisecond, or second.

[0344] The predetermined time window can be a parameter set by the BS and / or a period of time window specified in the specification and / or determined according to the UE's capabilities, or after a certain delay (application delay, processing delay).

[0345] The predetermined time width can be a parameter set by the BS and / or specified in the specification (pre-defined) and / or determined according to the UE's capabilities and / or different according to the SCS and / or different according to the UE's Timing Advanced value and / or during the time window period from the reference point, or from the reference point and / or after a certain delay (application delay, processing delay).

[0346] The UE can determine the predetermined period by taking either the min (smaller value) or the max (larger value) of a predetermined value. A predetermined value can be 1 symbol / 1 slot / 1 millisecond, or a value determined by the following.

[0347] The values ​​are determined by parameters set by the BS and / or pre-defined by the specification, and / or by the UE's capabilities and / or by the SCS.

[0348] The reserved cell of BS can be any one of SpCell, Pcell, PSCell at DC, active SCell, or cell that meets the reserved conditions.

[0349] The UE can be in any of the following states: idle, inactive, or RRCconnected. Different actions can be taken depending on the UE state.

[0350] The UE can perform predetermined functions / actions and / or report under predetermined UE capabilities. Predetermined UE capabilities can be set at any of the following granularities: UE, FR1, FR2, FR2-1, FR2-2, SCS, frequency band, frequency band combination, feature combination, and / or FSPC unit; UE, Cell, TDD, FDD unit.

[0351] In addition, the scheduled settings / notifications can be any of the following.

[0352] Setting / notifying can be done through any of RRC, MAC-CE, or DCI. The parameter list set / notified through any of RRC, MAC-CE, or DCI can be associated with an identifier (index). Alternatively, the identifier can be notified to the UE through other notifications (MAC CE, DCI), thereby determining the parameter list for UE activation / application / use (deactivation, non-application, use).

[0353] Identifiers can be implicitly associated through the order of a list defined by RRC, or they can be associated by explicitly setting a number.

[0354] The UE can respond to any signal with an acknowledgment signal (NACK, ACK, feedback, retransmission request).

[0355] The UE can set, change, and release multiple parameter lists as "AddModlist" and / or "releaselist" via RRC.

[0356] The configuration / notification can be an SI / SIB RRC message or a UE-specific RRC message (such as RRCReconfiguration) for the UE in the RRC connection.

[0357] Dedicated RRC configuration, RRC release, and RRC setup can be settings or notifications.

[0358] SS / PBCH / SIB1 / SIBX / dedicated RRC configuration / RRC release / RRC setup can be used for setting / notification.

[0359] The SS / PBCH / SIB1 / SIBX / dedicated RRCconfiguration / RRC release / RRC setup of a certain cell / frequency band / carrier can be configured / notified.

[0360] The SS / PBCH / SIB1 / SIBX / dedicated RRC configuration / RRC release / RRC setup of a certain / multiple cells / frequency bands / carriers can be configured / notified.

[0361] The settings / notifications can be a predefined DCI format scrambled by X-RNTI. X-RNTI can be NES-RNTI, SI-RNTI, or other formats, and can also be a new DCI format and / or RNTI.

[0362] For all parameters, the UE can use the default value / action when the BS does not set / notify. The default action can be as follows.

[0363] • Do not perform any action

[0364] • Repeatedly perform the preceding action

[0365] • Perform RRC Release / Perform RRC Re-establishment

[0366] • Send scheduled notification to BS

[0367] • Send the scheduled notification to the UE's higher-level management

[0368] The default values ​​can be the following.

[0369] Always 0 / 1

[0370] • Value used immediately before

[0371] • The value that was just set / notified

[0372] • The (pre-)defined value in the specification

[0373] Other settings / notification parameter values

[0374] • Preset timer value

[0375] For all UE actions #A, the UE can perform the default action #B if a certain action #A cannot be performed.

[0376] Furthermore, the use of any of the above embodiments can be configured through higher-layer parameters, reported from terminal 20 to base station 10 as a UE capability, specified through a standard, and configured through higher-layer parameters, or notified via DCI. The base station-oriented WUS (Wake-up signal) can be used not only for cell DRX but also for cell DTX.

[0377] Additionally, UE capabilities indicating whether cell DTX and cell DRX are supported can be defined. UE capabilities indicating whether dynamic activation or deactivation of cell DTX and cell DRX can also be defined. UE capabilities indicating whether cell DTX and cell DRX accompanying UE DRX or CDRX can also be defined.

[0378] Additionally, cell DTX / DRX can be replaced with cell DTX and / or cell DRX. Activation / deactivation can be replaced with activation and / or deactivation, activation and / or deactivation, etc.

[0379] Through the above embodiments, by ensuring consistency in the resource setting method and resource configuration of the on-demand SSB used to activate SCell between the BS and UE, actions using appropriate SSBs and on-demand SSBs (e.g., L3 / L1 measurement, SCell addition, AGC (Auto gain control), synchronization, and channel estimation) can be performed between the UE and BS.

[0380] That is, providing a technology to activate sub-cells in base stations that can migrate to a power-saving state.

[0381] (Device structure)

[0382] Next, an example of the functional structure of the base station 10 and terminal 20 performing the processes and actions described above will be explained. The base station 10 and terminal 20 include the functions to perform the above embodiments. However, the base station 10 and terminal 20 may each only have the functions proposed in any of the embodiments.

[0383] <Base Station 10>

[0384] Figure 13 This is a diagram illustrating an example of the functional structure of a base station. (For example...) Figure 13 As shown, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130 and a control unit 140. Figure 13 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional units can be arbitrary. The transmitting unit 110 and the receiving unit 120 can also be referred to as communication units.

[0385] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and wirelessly transmitting the signal. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining, for example, higher-level information from the received signals. Furthermore, the transmitting unit 110 has the function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, DL data, etc., to the terminal 20. In addition, the transmitting unit 110 transmits setting information, etc., as described in the embodiment.

[0386] The setting unit 130 stores preset setting information and various setting information sent to the terminal 20 into a storage device, and reads it from the storage device as needed. The control unit 140 performs, for example, overall control of the base station 10, including control related to signal transmission and reception. Alternatively, the signal transmission-related functions of the control unit 140 may be included in the transmitting unit 110, and the signal reception-related functions of the control unit 140 may be included in the receiving unit 120. Furthermore, the transmitting unit 110 and the receiving unit 120 may be referred to as a transmitter and a receiver, respectively.

[0387] Terminal 20

[0388] Figure 14 This is a diagram illustrating an example of the functional structure of a terminal. For example... Figure 14 As shown, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. Figure 14 The functional structure shown is only one example. As long as the actions involved in the embodiments of the present invention can be performed, the functional distinctions and names of the functional units can be arbitrary. The transmitting unit 210 and the receiving unit 220 can also be referred to as communication units.

[0389] The transmitting unit 210 generates a transmission signal based on the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the transmitting unit 210 transmits HARQ-ACK, and the receiving unit 220 receives setting information, etc., as described in the embodiment.

[0390] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 into a storage device, and reads it from the storage device as needed. In addition, the setting unit 230 also stores pre-set setting information. The control unit 240 performs overall control of the terminal 20, including control related to signal transmission and reception. Alternatively, the signal transmission-related functions of the control unit 240 can be included in the transmitting unit 210, and the signal reception-related functions of the control unit 240 can be included in the receiving unit 220. Furthermore, the transmitting unit 210 and the receiving unit 220 can be referred to as a transmitter and a receiver, respectively.

[0391] The terminal or base station in this embodiment can be configured as shown in the following descriptions. Furthermore, the following communication methods can also be implemented.

[0392] <Structures related to this embodiment>

[0393] (Item 1)

[0394] A terminal having: The receiving unit receives from the base station signaling that configures resources related to the on-demand transmission of the SSB (SS / PBCH Block) and signaling indicating the activation of the sub-cell; and The control unit performs the process of activating the secondary cell using the SSB transmitted on demand.

[0395] (Item 2)

[0396] According to the terminal described in item 1, the control unit determines the time offset between the on-demand SSB and a certain cell based on the signaling of the resources related to the setting of the on-demand SSB.

[0397] (Item 3)

[0398] According to the terminal described in item 1, the control unit envisions that the signaling for setting resources related to on-demand transmission of SSBs is associated with the signaling for indicating the activation of the sub-cell.

[0399] (Item 4)

[0400] According to the terminal described in item 1, the control unit obtains the signaling indicating the activation of the secondary cell based on the DCI (Downlink Control Information) sent to notify the on-demand SSB.

[0401] (Item 5)

[0402] According to the terminal described in item 1, the control unit obtains the characteristics of the on-demand SSB from the signaling indicating the activation of the sub-cell.

[0403] (Item 6)

[0404] A communication method in which a terminal performs the following steps: Receives from the base station signaling that configures resources related to on-demand transmission of SSB (SS / PBCH Block) and signaling that instructs the activation of secondary cells; and The process of activating the secondary cell using the SSB sent on demand is performed.

[0405] According to any of the above structures, a technique for activating sub-cells in a base station capable of migrating to a power-saving state is provided. According to items 2 to 5, by ensuring consistency in the resource setting method and resource configuration understanding of the on-demand SSB used to activate SCell between the BS and UE, actions using appropriate SSBs and on-demand SSBs (e.g., L3 / L1 measurement, SCell addition, AGC (Auto gain control), synchronization, and channel estimation) can be performed between the UE and BS.

[0406] (Hardware structure)

[0407] The block diagram used in the description of the above embodiments ( Figure 13 and Figure 14 The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software within the aforementioned single or multiple devices.

[0408] The functions include judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning, but are not limited to these. For example, a functional block (structural unit) that performs the sending function is called a transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0409] For example, in one embodiment of this disclosure, the base station 10, terminal 20, etc., can also function as a computer for processing the wireless communication method of this disclosure. Figure 15This is a diagram illustrating an example of the hardware structure of a base station 10 and a terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 may also be configured as a computer device that physically includes a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0410] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of base station 10 and terminal 20 can be configured to include one or more of the devices shown in the figures, or it can be configured to not include any of them.

[0411] The functions in base station 10 and terminal 20 are implemented by reading predetermined software (programs) into hardware such as processor 1001 and storage device 1002, so that processor 1001 performs calculations and controls the communication of communication device 1004 or controls at least one of reading and writing data in storage device 1002 and auxiliary storage device 1003.

[0412] The processor 1001 controls the computer as a whole by instructing the operating system to operate. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the aforementioned control unit 140, control unit 240, etc., can also be implemented using the processor 1001.

[0413] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage devices 1003 and communication devices 1004, and performs various processes accordingly. As a program, a program is used that causes the computer to perform at least a portion of the actions described in the above embodiments. For example, Figure 13 The control unit 140 of the base station 10 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. And, for example, Figure 14 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and operated in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, the various processes described above can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by more than one chip. In addition, the program can also be sent from the network via a telecommunications line.

[0414] Storage device 1002 is a computer-readable recording medium, and may be composed of at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Storage device 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Storage device 1002 can store programs (program code), software modules, etc., that are executable for implementing the communication method according to one embodiment of this disclosure.

[0415] The auxiliary storage device 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (CompactDisc ROM) or other optical discs, hard disks, floppy disks, magneto-optical discs (e.g., compact discs, digital multifunction discs, Blu-ray discs), smart cards, flash memory (e.g., cards, sticks, key drives), floppy disks, magnetic stripes, etc. The aforementioned storage medium may, for example, be a database, server, or other suitable media that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0416] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network. It may also be referred to as a network device, network controller, network interface card (NIC), communication module, etc. The communication device 1004 may, for example, be configured to include a high-frequency switch, duplexer, filter, frequency synthesizer, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, transceiver antennas, amplifiers, transceiver units, transmission path interfaces, etc., can also be implemented using the communication device 1004. The transceiver unit may also be physically or logically separated into a transmitting unit and a receiving unit.

[0417] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0418] Furthermore, the processor 1001 and storage device 1002, among other devices, are connected via a bus 1007 for communicating information. The bus 1007 can be configured as a single bus or as different buses used between the devices.

[0419] Furthermore, the base station 10 and the terminal 20 can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or a FPGA (Field Programmable Gate Array), and can also use this hardware to implement part or all of the functional blocks. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0420] Figure 16 An example of the structure of vehicle 2001 is shown. For example... Figure 16 As shown, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a gearshift 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. The various forms / implementations described in this disclosure can also be applied to communication devices mounted on the vehicle 2001, for example, to the communication module 2013.

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

[0422] The electronic control unit 2010 consists of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (I / O port) 2033. Signals from various sensors 2021 to 2029 of the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 can also be referred to as an ECU (Electronic Control Unit).

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

[0424] The Information Service Unit 2012 consists of various devices such as a car navigation system, audio system, speakers, television, and radio, which provide various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information obtained from external devices such as the communication module 2013 to provide various multimedia information and multimedia services to the occupants of the vehicle 2001.

[0425] The Driver Assistance System 2030 comprises various devices used to prevent accidents or reduce driver workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyroscope systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. Furthermore, the Driver Assistance System 2030 transmits and receives various information via the communication module 2013 to achieve driver assistance or autonomous driving functions.

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

[0427] The communication module 2013, controlled by the microprocessor 2031 of the electronic control unit 2010, is a communication device capable of communicating with external devices. For example, it can transmit and receive various types of information with external devices via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. External devices can be, for example, base stations, mobile stations, etc.

[0428] The communication module 2013 transmits the current signal from the current sensor input to the electronic control unit 2010 to an external device via wireless communication. Additionally, the communication module 2013 also transmits the following signals input to the electronic control unit 2010 via wireless communication to external devices: the front and rear wheel speed signals obtained by the speed sensor 2022; the front and rear wheel air pressure signals obtained by the air pressure sensor 2023; the vehicle speed signal obtained by the vehicle speed sensor 2024; the acceleration signal obtained by the acceleration sensor 2025; the accelerator pedal depressor signal obtained by the accelerator pedal sensor 2029; the brake pedal depressor signal obtained by the brake pedal sensor 2026; the gear shift lever operation signal obtained by the gear shift lever sensor 2027; and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0429] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) sent from external devices and displays it on the information service unit 2012 of the vehicle 2001. Furthermore, the communication module 2013 stores the various information received from external devices in a memory 2032 available to the microprocessor 2031. The microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gearshift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, and sensors 2021-2029 of the vehicle 2001 based on the information stored in the memory 2032.

[0430] (Supplement to the implementation method)

[0431] The embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments. Those skilled in the art should understand various modifications, alterations, substitutions, and replacements. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these values ​​are merely examples, and any appropriate values ​​may be used. The distinctions between items in the above description are not essential to the present invention. Items described in two or more items may be combined as needed, and items described in one item may be applied to items described in another item (as long as there is no contradiction). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical components. Multiple functional units may be operated by a single physical component, or a single functional unit may be operated by multiple physical components. Regarding the processing described in the embodiments, the order of processing may be interchanged unless there is a contradiction. For ease of explanation, a functional block diagram is used to illustrate the base station 10 and terminal 20, but such a device may also be implemented by hardware, software, or a combination thereof. The software operating according to the embodiments of the present invention via the processor of the base station 10 and the software operating according to the embodiments of the present invention via the processor of the terminal 20 may also 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 and other suitable storage media, respectively.

[0432] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Additionally, RRC signaling may be referred to as an RRC message, for example, it may also be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0433] The various forms / implementations described in this disclosure can also be applied to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6G (6th generation mobile communication system), xG (xth generation mobile communication system) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), NX (new radio access), FX (future generation radio access), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE The system may include at least one of 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), other suitable systems, and next-generation systems based on these systems that have been extended, modified, created, or specified. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

[0434] The processing procedures, timing, and flow of the various forms / implementations described in this specification may be rearranged in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order for the methods described in this disclosure, but are not limited to the specific order indicated.

[0435] In this specification, certain actions performed by base station 10 may sometimes also be performed by its upper node, depending on the circumstances. In a network consisting of one or more network nodes having base station 10, it is obvious that various actions performed to communicate with terminal 20 can be performed by at least one of base station 10 and other network nodes besides base station 10 (e.g., considering MME or S-GW, but not limited to these). The above example illustrates the case where there is one other network node besides base station 10, but other network nodes can also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0436] The information or signals described in this disclosure can be output from a higher (or lower) layer to a lower (or higher) layer. They can also be input or output via multiple network nodes.

[0437] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0438] The determination in this disclosure can be made by a value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value).

[0439] Software, whether called software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as referring to commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0440] In addition, software, commands, and information can also be sent and received via transmission media. For example, when software is sent from a webpage, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of transmission media.

[0441] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description as a whole can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0442] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may also be referred to as carrier frequency, cell, frequency carrier, etc.

[0443] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0444] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may be indicated using indexes.

[0445] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, therefore the various names assigned to these channels and information elements are non-limiting in any respect.

[0446] In this disclosure, the terms "base station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0447] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, its coverage area can be divided into several smaller areas, each of which can provide communication services through a base station subsystem (e.g., a small indoor base station RRH: Remote Radio Head). Terms such as "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base station and base station subsystem providing communication services within that coverage area.

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

[0449] For mobile stations, those skilled in the art sometimes also use the following terms: 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, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0450] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Additionally, at least one of the base station and mobile station can also be a device mounted on a mobile body, the mobile body itself, etc. This mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Furthermore, at least one of the base station and mobile station also includes devices that do not necessarily move during communication. For example, at least one of the base station and mobile station can be an IoT (Internet of Things) device such as a sensor.

[0451] Furthermore, the base station in this disclosure can also be replaced by a user terminal. For example, the communication between the base station and the user terminal can be replaced by communication between multiple terminals 20 (e.g., D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.), and various forms / implementations of this disclosure can also be applied. In this case, the terminal 20 can also be configured to have the functions of the base station 10 described above. In addition, terms such as "uplink" and "downlink" can be replaced with terms corresponding to inter-terminal communication (e.g., "side"). For example, uplink channel, downlink channel, etc., can also be replaced with side channel.

[0452] Similarly, the user terminal in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of the aforementioned user terminal.

[0453] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" or "determining" may include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" or "determining." Furthermore, "determining" or "determining" may include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" or "determining." Additionally, "determining" or "determining" may include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" or "determining." That is, "judgment" and "decision" can include matters that are considered as having been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0454] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including cases where there is one or more intermediate elements between the two elements that are “connected” or “coupled.” The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, it can be understood that two elements are “connected” or “coupled” to each other using at least one of one or more wires, cables, and printed electrical connections, and, as some non-limiting and non-inclusive examples, using electromagnetic energy with wavelengths in the wireless frequency domain, microwave region, and light (including both visible and invisible regions) to “connect” or “couple” to each other.

[0455] The reference signal can be simply called RS (Reference Signal), or, depending on the standard applied, pilot.

[0456] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least".

[0457] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, references to the first and second elements do not imply that only two elements can be taken, or that in any form the first element must precede the second element.

[0458] Alternatively, the "unit" in the structure of the above devices can be replaced with "section", "circuit", "equipment", etc.

[0459] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure does not refer to XOR.

[0460] A radio frame can consist of one or more frames in the time domain. Each frame in the time domain is called a subframe. A subframe can also consist of one or more time slots in the time domain. A subframe can also be a fixed time length (e.g., 1 ms) independent of the parameter set (numerology).

[0461] A parameter set can be communication parameters applied to at least one of the transmission and reception of a signal or channel. For example, a parameter set can represent 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, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0462] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0463] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0464] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can each be referred to by other corresponding names.

[0465] For example, a subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and a time slot or a mini-time slot can also be called a TTI. That is, at least one of a subframe and a TTI can be a subframe (1ms) in existing LTE, a period shorter than 1ms (e.g., 1-13 symbols), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0466] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each terminal 20) in units of TTI. However, the definition of TTI is not limited to this.

[0467] The Time Interval (TTI) can be a unit of time for transmitting channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit such as scheduling or link adaptation. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) that the transmission block, code block, codeword, etc., are mapped to can be shorter than the TTI.

[0468] Furthermore, when one time slot or one mini time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini time slot) can become the minimum time unit for scheduling. In addition, the number of time slots (mini time slots) constituting the minimum time unit of the schedule can be controlled.

[0469] A TTI with a duration of 1ms is also called a normal TTI (in LTE Rel. 8-12), a long TTI, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0470] Additionally, a long TTI (e.g., a normal TTI, a subframe, etc.) can be replaced with a TTI with a duration of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) can be replaced with a TTI with a duration of less than a long TTI but more than 1 ms.

[0471] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set, for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0472] Furthermore, the temporal domain of an RB can contain one or more symbols, which can be a time slot, a mini-time slot, a subframe, or the length of a TTI. A TTI, a subframe, etc., can each be composed of one or more resource blocks.

[0473] In addition, one or more RBs can also be called Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

[0475] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) can also represent a subset of contiguous common resource blocks (RBs) used for a certain parameter set in a certain carrier. Here, common RBs can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0476] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be configured for terminal 20 within one carrier.

[0477] At least one of the configured BWPs can be active, and it is not assumed that the terminal 20 will transmit or receive predetermined signals / channels outside of an active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0478] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained within a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, and the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in many ways.

[0479] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure also includes cases where the noun following these articles is in a plural form.

[0480] In this disclosure, the phrase "A and B are different" can mean "A and B are not the same." Additionally, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0481] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information (e.g., a notification of "It is X") is not limited to being explicit, but can also be implicit (e.g., without notification of the predetermined information).

[0482] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0483] Label Explanation

[0484] 10: Base station

[0485] 110: Sending Department

[0486] 120: Receiving Department

[0487] 130: Setting Department

[0488] 140: Control Department

[0489] 20: Terminal

[0490] 210: Sending Department

[0491] 220: Receiving Department

[0492] 230: Setting Department

[0493] 240: Control Department

[0494] 1001: Processor

[0495] 1002: Storage device

[0496] 1003: Auxiliary storage device

[0497] 1004: Communication device

[0498] 1005: Input device

[0499] 1006: Output device

[0500] 2001: Vehicles

[0501] 2002: Drive Unit

[0502] 2003: Steering Unit

[0503] 2004: Accelerator Pedal

[0504] 2005: Brake Pedal

[0505] 2006: Gear Shift

[0506] 2007: Front Wheel

[0507] 2008: Rear Wheel

[0508] 2009: Axle

[0509] 2010: Electronic Control Department

[0510] 2012: Information Services Department

[0511] 2013: Communication Module

[0512] 2021: Current Sensor

[0513] 2022: Speed ​​Sensor

[0514] 2023: Barometric Pressure Sensor

[0515] 2024: Vehicle Speed ​​Sensor

[0516] 2025: Accelerometer

[0517] 2026: Brake Pedal Sensor

[0518] 2027: Gearshift Sensor

[0519] 2028: Object Detection Sensor

[0520] 2029: Accelerator Pedal Sensor

[0521] 2030: Driver Assistance Systems Department

[0522] 2031: Microprocessors

[0523] 2032: Memory (ROM, RAM)

[0524] 2033: Communication port (IO port)

Claims

1. A terminal having: The receiving unit receives from the base station signaling that sets resources related to the on-demand transmission of SSBs and signaling that instructs the activation of sub-cells, wherein... SSB refers to SS / PBCH Block. as well as The control unit performs the process of activating the secondary cell using the SSB transmitted on demand.

2. The terminal according to claim 1, wherein, The control unit determines the time offset between the on-demand SSB and a certain cell based on the signaling of the resources related to the settings of the SSB.

3. The terminal according to claim 1, wherein, The control unit envisions that the signaling for setting resources related to on-demand SSB transmission is associated with the signaling for indicating the activation of the sub-cell.

4. The terminal according to claim 1, wherein, The control unit obtains the signaling indicating the activation of the secondary cell based on the DCI transmitted by the SSB that is notified on demand, wherein DCI refers to Downlink Control Information.

5. The terminal according to claim 1, wherein, The control unit obtains the characteristics of the on-demand SSB from the signaling indicating the activation of the secondary cell.

6. A communication method in which a terminal performs the following steps: The base station receives signaling that sets up resources related to the on-demand transmission of SSBs and signaling that instructs the activation of secondary cells, wherein... SSB refers to SS / PBCH Block. as well as The process of activating the secondary cell using the SSB sent on demand is performed.

Images