Terminals and communication methods

Abstract

To reduce the power consumption of base stations. [Solution] The terminal has a receiving unit that receives first control information relating to an intermittent transmission function in which a base station enables or disables a transmission unit and an intermittent reception function in which the base station enables or disables a reception unit; a control unit that assumes, based on the first control information, that the base station will perform the intermittent transmission function and the intermittent reception function; and a communication unit that performs transmission and reception with the base station based on the assumed intermittent transmission function and the intermittent reception function. The receiving unit receives second control information relating to at least one of spatial domain adaptation and power domain adaptation, and the control unit performs at least one of spatial domain adaptation and power domain adaptation based on the second control information.

Description

Technical Field

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

Background Art

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

[0003] Also, in Release 18 of 3GPP (registered trademark), in order to achieve environmental sustainability, carbon neutrality, SDGs (Sustainable Development Goals), reduction of operating costs, etc., network energy savings in the network has become more important, and methods for energy savings are being studied (for example, Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] Saving power consumption at base stations is becoming increasingly important in order to achieve carbon neutrality and the SDGs. However, there is a problem in that methods for saving power consumption at base stations have not been standardized.

[0006] This invention has been made in view of the above points, and aims to reduce the power consumption of base stations. [Means for solving the problem]

[0007] According to the disclosed technology, a terminal is provided having: a receiving unit that receives first control information relating to an intermittent transmission function in which a base station enables or disables a transmitting unit and an intermittent reception function in which the base station enables or disables a receiving unit; a control unit that assumes, based on the first control information, that the base station performs the intermittent transmission function and the intermittent reception function; and a communication unit that performs transmission and reception with the base station based on the assumed intermittent transmission function and the intermittent reception function, wherein the receiving unit receives second control information relating to at least one of spatial domain conformance and power domain conformance, and the control unit performs at least one of spatial domain conformance and power domain conformance based on the second control information. [Effects of the Invention]

[0008] According to the disclosed technology, a technology is provided that enables power savings for base stations. [Brief explanation of the drawing]

[0009] [Figure 1] This figure illustrates a wireless communication system according to an embodiment of the present invention. [Figure 2] This is a diagram illustrating CDRX in NR Release 15. [Figure 3] This is a diagram illustrating WUS in NR Release 16. [Figure 4] This figure illustrates the intermittent reception of a base station according to Embodiment 1 of the present invention. [Figure 5] This is a diagram for explaining each parameter according to Example 1 of the embodiment of the present invention. [Figure 6] This is a diagram for explaining the intermittent transmission of the base station according to Example 5 of the embodiment of the present invention. [Figure 7] This is a diagram for explaining each parameter according to Example 5 of the embodiment of the present invention. [Figure 8] This is a flowchart for explaining Example (1) of Example 9 of the embodiment of the present invention. [Figure 9] This is a flowchart for explaining Example (2) of Example 9 of the embodiment of the present invention. [Figure 10] This is a flowchart for explaining Example (3) of Example 9 of the embodiment of the present invention. [Figure 11] This is a diagram for explaining an example of the setting related to the CSI report. [Figure 12] This is a diagram for explaining Example (1) of the antenna OFF mode. [Figure 13] This is a diagram for explaining Example (2) of the antenna OFF mode. [Figure 14] This is a diagram for explaining Example (3) of the antenna OFF mode. [Figure 15] This is a diagram for explaining Example (1) of the setting related to multiple CSI reports. [Figure 16] This is a diagram for explaining Example (2) of the setting related to multiple CSI reports. [Figure 17] This is a diagram for explaining an example of the setting related to the trigger for multiple CSI reports according to the embodiment of the present invention. [Figure 18] This is a diagram for explaining Example (1) of the TCI format. [Figure 19] This is a diagram for explaining Example (2) of the TCI format. [Figure 20] This is a flowchart for explaining Example (1) of the TCI notification. [Figure 21] This is a flowchart for explaining Example (2) of the TCI notification. [Figure 22] This is a diagram for explaining the combined TCI state. [Figure 23] This is a diagram showing an example (1) of the antenna mapping mode. [Figure 24] This is a diagram showing an example (2) of the antenna mapping mode. [Figure 25] This is a diagram showing an example (3) of the antenna mapping mode. [Figure 26] This is a diagram showing an example of the ES state in an embodiment of the present invention. [Figure 27] This is a diagram for explaining Plan 1-1 of Examples 1-3 related to power adaptation in an embodiment of the present invention. [Figure 28] This is a diagram for explaining Plan 1-3 of Examples 1-3 related to power adaptation in an embodiment of the present invention. [Figure 29] This is a diagram for explaining Example 1-4 related to power adaptation in an embodiment of the present invention. [Figure 30] This is a diagram showing an example of the functional configuration of a base station according to an embodiment of the present invention. [Figure 31] This is a diagram showing an example of the functional configuration of a terminal according to an embodiment of the present invention. [Figure 32] This is a diagram showing an example of the hardware configuration of a base station or a terminal according to an embodiment of the present invention. [Figure 33] This is a diagram showing an example of the configuration of a vehicle according to an embodiment of the present invention.

Embodiments for Carrying Out the Invention

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

[0011] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. Such existing technologies include, but are not limited to, existing NR or LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.

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

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

[0014] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters, etc., may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from a base station or terminal are configured.

[0015] (System Configuration) Figure 1 is a diagram illustrating an embodiment of the wireless communication system according to the present invention. A wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Although Figure 1 shows one base station 10 and one terminal 20, this is an example, and there may be multiple base stations 10 and terminal 20.

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

[0017] The base station 10 transmits synchronization signals and system information to the terminal 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH and is also called broadcast information. The synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, the base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using CA (Carrier Aggregation). Furthermore, terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell: Primary SCG Cell) of other base stations 10 using DC (Dual Connectivity).

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

[0019] Next, we will describe the discussion status regarding base station power saving in NR Release 18. Base station and terminal techniques to improve network energy saving from both base station transmission and reception perspectives are being considered. For example, base stations are being explored on how to more efficiently achieve finer-grained, dynamic and / or semi-static adaptation of transmission and / or reception in one or more network energy saving techniques in the time, frequency, space, and power domains, using potential support / feedback and potential support information from terminals.

[0020] Next, we will explain discontinuous reception (DRX) or connected mode DRX (CDRX) in conventional terminals.

[0021] Figure 2 is a diagram illustrating CDRX in NR Release 15. In CDRX operation in NR Release 15, the terminal monitors the PDCCH during the DRX-on period.

[0022] Figure 3 is a diagram illustrating the WUS in NR Release 16. In NR Release 16, the PDCCH-based Wake Up Signal (WUS) can instruct one or more terminals whether they will monitor the PDCCH during the next DRX-on period.

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

[0024] WUS monitoring opportunities are set by an offset from the on period based on terminal functionality. If WUS indicates "inactive" (i.e., no data is being sent or received by the terminal), the terminal can skip monitoring during the on period and immediately enter sleep mode. Furthermore, a default terminal action can be set in case the PDCCH-based WUS is not detected due to, for example, a detection error.

[0025] DCI format 2_6 includes one bit of startup instruction information indicating "active" or "inactive".

[0026] (Previous problems) Next, let's discuss the conventional problems. Saving power consumption at base stations is becoming increasingly important in order to achieve carbon neutrality and the SDGs. However, a problem has been that methods for saving power consumption at base stations have not been standardized.

[0027] (Summary of this embodiment 1) Therefore, this embodiment describes an example of achieving a reduction in base station power consumption from a time domain perspective. Below, we will describe specific examples, from Example 1 to Example 4.

[0028] (Example 1) This embodiment describes the operation of the base station when it receives signals intermittently, and defines related concepts.

[0029] Figure 4 is a diagram illustrating the intermittent reception of a base station according to Embodiment 1 of the present invention. The period during which the base station 10 disables / enables the receiving unit is introduced as an intermittent reception (gNB CDRX) function by the base station (hereinafter referred to as base station intermittent reception).

[0030] The concept of intermittent reception at base station 10 is similar to that of intermittent reception at terminal 20. The receiving units and / or parameters to be disabled may be per port, panel, beam, or carrier (or cell).

[0031] Figure 5 is a diagram illustrating the parameters according to Embodiment 1 of the present invention. The base station CDRX may be defined by several parameters listed below. The units of the parameters may be symbols, slots, subframes, milliseconds, or seconds. The units may differ or be the same among the parameters. • drx-onDurationTimer: The duration at the start of the DRX cycle. • drx-SlotOffset: Delay before starting drx-onDurationTimer • drx-InactivityTimer: The period during which terminal 20 performs an uplink transmission after an uplink reception opportunity. • drx-LongCycleStartOffset: Defines when long DRX cycles and short DRX cycles start, using the long DRX cycle (i.e., drx-LongCycle) and drx-StartOffset. • drx-ShortCycle: Short DRX cycle • drx-ShortCycleTimer: The period during which base station 10 follows a short DRX cycle. • drx-RetransmissionTimerUL: Maximum period until permission for uplink retransmission is received. • drx-HARQ-RTT-TimerUL: Minimum period until uplink retransmission permission is expected

[0032] If intermittent base station reception is enabled, the base station 10 may receive the uplink channel transmitted from the terminal 20 when drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL is running.

[0033] If intermittent base station reception is enabled, terminal 20 may perform one of the following optional actions:

[0034] <Option 1> Terminal 20 may operate assuming intermittent reception from base stations. Specifically, terminal 20 identifies the status of intermittent reception from base stations using RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 assumes that it receives a DCI from base station 10 indicating the status of intermittent reception from base station 10. Details of the instructions using DCI will be described later in Example 3.

[0035] Terminal 20 may transmit an uplink channel while drx-onDurationTimer, drx-InactivityTimer, or drx-RetransmissionTimerUL is running, if intermittent reception from the base station is enabled.

[0036] <Option 2> Terminal 20 may ignore intermittent reception from the base station. Specifically, terminal 20 will perform uplink transmissions as scheduled or configured by base station 10, regardless of the status of intermittent reception from the base station.

[0037] Furthermore, if intermittent base station reception is enabled, base station 10 may perform a schedule or settings that take intermittent base station reception into consideration, or it may perform a schedule or settings regardless of intermittent base station reception. If a schedule or settings that take intermittent base station reception into consideration are performed, the function of intermittent base station reception will be realized even if terminal 20 ignores intermittent base station reception. Conversely, if a schedule or settings that take intermittent base station reception are not performed, and terminal 20 ignores intermittent base station reception, it will transmit unnecessary signals, resulting in wasted power consumption of terminal 20.

[0038] On the other hand, if intermittent base station reception is disabled, base station 10 may receive the uplink channel transmitted from terminal 20 regardless of the intermittent base station reception parameters. That is, base station 10 may keep the receiving unit turned on and continuously receive the uplink channel from terminal 20.

[0039] If intermittent base station reception is disabled, terminal 20 may perform one of the following optional actions:

[0040] <Option 1> Terminal 20 may operate assuming intermittent reception from base stations. Specifically, terminal 20 identifies the status of intermittent reception from base stations using RRC, MAC-CE, or DCI. In the case of DCI, terminal 20 assumes that it receives a DCI from base station 10 indicating the status of intermittent reception from base station 10. Details of the instructions using DCI will be described later in Example 3.

[0041] If intermittent base station reception is disabled, terminal 20 will perform uplink transmission as scheduled or configured by base station 10, regardless of the status of intermittent base station reception.

[0042] <Option 2> Terminal 20 may ignore intermittent reception from the base station. Specifically, terminal 20 will perform uplink transmissions as scheduled or configured by base station 10, regardless of the status of intermittent reception from the base station.

[0043] Furthermore, the base station 10 may receive terminal assistance information in order to determine the values ​​of the aforementioned parameters that define the wake-up / sleep period.

[0044] Terminal assistance information may also be the period of terminal traffic. Base station 10 may receive terminal assistance information at a higher layer. Base station 10 determines the parameter values ​​taking into account the terminal assistance information reported by terminal 20.

[0045] Terminal 20 may transmit terminal support information, such as the period of terminal traffic, to base station 10.

[0046] According to this embodiment, intermittent reception by the base station 10 can be achieved.

[0047] (Example 2) This embodiment provides an example of a method for triggering intermittent reception at base stations.

[0048] Enabling or disabling intermittent base station reception may be done using one of the following options:

[0049] <Option 1> The base station 10 may enable or disable intermittent base station reception when an RRC parameter indicating the enable / disable of intermittent base station reception is set by the terminal 20 or other network node (e.g., the core network or other base stations).

[0050] <Option 2> When base station 10 receives a MAC-CE command indicating the enablement or disablement of intermittent base station reception from terminal 20 or other network nodes (e.g., the core network or other base stations), it may enable or disable intermittent base station reception.

[0051] <Option 3> When base station 10 receives a UCI included in PUCCH or PUSCH from terminal 20, it may enable or disable intermittent base station reception based on the instructions for enabling / disabling intermittent base station reception included in the UCI.

[0052] A UCI containing instructions to enable / disable intermittent base station reception may be a newly defined UCI type that differs from conventional ones. Alternatively, such a UCI may be a conventional UCI type such as HARQ-ACK, CSI, or SR.

[0053] Terminal 20 may enable or disable intermittent base station reception by sending a PUCCH or PUSCH to base station 10 to perform an instruction for intermittent base station reception (i.e., activate / deactivate).

[0054] Terminal 20 may receive a DCI from base station 10 indicating the status of intermittent base station reception in order to identify whether the instructions via UCI have been successfully decoded by base station 10 and whether there is a common understanding between base station 10 and terminal 20 regarding the status of intermittent base station reception. Details of DCI will be described later in Example 3.

[0055] <Option 4> Base station 10 may enable or disable intermittent base station reception when certain conditions are met. For example, base station 10 may enable intermittent base station reception if it does not receive an uplink channel from terminal 20 for a certain period of time. This period of time may be a symbol, slot, subframe, millisecond, or second.

[0056] Terminal 20 may receive a DCI (Data Control Information) from base station 10 indicating the status of intermittent base station reception in order to obtain a common understanding of the status of intermittent base station reception between base station 10 and terminal 20. Details of the DCI will be described later in Example 3.

[0057] <Option 5> The base station 10 may enable or disable intermittent base station reception by a combination of the above options.

[0058] Furthermore, base station 10 may perform one of the following optional actions as a procedure for enabling / disabling intermittent base station reception.

[0059] <Option 1> The base station 10 may immediately enable or disable intermittent base station reception when any of the options that trigger the enabling / disabling of intermittent base station reception as described above are executed.

[0060] <Option 2> Base station 10 may receive instructions regarding the timing of enabling / disabling intermittent base station reception at a certain time interval or at a specified time after receiving the instruction. The unit of the time interval or specified time may be a symbol, slot, subframe, millisecond, second, etc. That is, base station 10 may enable / disable intermittent base station reception at the specified time when any of the options that trigger the enabling / disabling of intermittent base station reception described above are executed.

[0061] <Option 3> Base station 10 may enable / disable intermittent base station reception based on newly introduced timers. The enable / disable timers may be the same or different. The timer units may be symbols, slots, subframes, milliseconds, seconds, etc. Base station 10 or terminal 20 or other network nodes may set the timers using RRC or specify them using MAC-CE or UCI / DCI.

[0062] In other words, the timer runs when any of the options that trigger the activation / deactivation of intermittent base station reception, as described above, is executed. When the timer expires, base station 10 may activate or deactivate intermittent base station reception.

[0063] Let's explain the advantages of the timer. Even if intermittent base station reception is instructed to be enabled, actual uplink transmission from terminal 20 may occur after a certain delay due to processing by terminal 20, etc. Even in such cases, by introducing a timer, intermittent base station reception can be enabled after a certain period of time, thereby reducing the power consumption of base station 10.

[0064] Furthermore, even if intermittent base station reception is instructed to be disabled, actual uplink transmissions from terminal 20 may continue for a while after the instruction due to processing by terminal 20. In such cases, by introducing a timer, intermittent base station reception can be disabled after a certain period of time, thereby improving the performance of terminal 20.

[0065] According to this embodiment, it is possible to trigger intermittent reception at base stations and to enable / disable the system when it is triggered.

[0066] (Example 3) This embodiment describes an example in which a terminal receives instructions regarding intermittent reception from a base station via DCI.

[0067] If terminal 20 identifies the status of intermittent reception from the base station and this is commonly understood by both terminal 20 and base station 10, a mechanism should be considered to indicate the status of intermittent reception from base station 10 to terminal 20. For timely notification, DCI (Data Control Indicator) is a promising option.

[0068] Furthermore, one advantage of having a shared understanding is that when intermittent reception from the base station is enabled, terminal 20 can stop uplink transmission, thus saving power consumption.

[0069] A new RNTI may be introduced to indicate the status of intermittent base station reception. The new RNTI may be, for example, gNB CDRX-RNTI (GC-RNTI).

[0070] Furthermore, the introduction of DCI fields may be one of the following options:

[0071] <Option 1> A new DCI field may be introduced to indicate the status of intermittent base station reception. The introduced DCI field may have a bit size of 1 bit, with "1" indicating an enabled state and "0" indicating an disabled state, or vice versa.

[0072] <Option 2> It is not necessary to introduce a new DCI field; that is, the status of intermittent base station reception may be indicated by an existing field. 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", terminal 20 may identify that the status of intermittent base station reception is enabled.

[0073] Furthermore, for example, if the corresponding DCI format is scrambled with a newer 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 may identify that the status of intermittent base station reception is disabled.

[0074] Furthermore, the corresponding DCI format may be one of the following options:

[0075] <Option 1> It may also be a DCI specific to terminal 20.

[0076] <Option 1-1> Base station 10 may use a new DCI format different from the conventional one to indicate the status of intermittent base station reception.

[0077] <Option 1-2> The base station 10 may indicate the status of intermittent reception using conventional DCI formats 0_1, 0_2, 1_1, 1_2, or other DCI formats.

[0078] <Option 2> Terminal 20 may also have a group-wide DCI.

[0079] <Option 2-1> Base station 10 may indicate the status of intermittent base station reception using a new DCI format different from the conventional one. The aforementioned new DCI fields may be introduced in the new DCI format along with other new DCI fields for power saving technologies of base station 10. Base station 10 may scramble the new DCI format with the aforementioned new RNTI (such as GC-RNTI).

[0080] <Option 2-2> The base station 10 may indicate the status of intermittent base station reception using the conventional DCI format 2_6 or other group-common DCI format.

[0081] Assuming DCI format 2_6 is being used, the traditional DCI fields in the DCI format may be reinterpreted to indicate the status of intermittent base station reception. For example, "Wake-up indication" may be used for reinterpretation. An enabled state may be indicated by "1" and an disabled state by "0," or vice versa.

[0082] For differentiation purposes, base station 10 may scramble DCI format 2_6 with the aforementioned new RNTI (such as GC-RNTI) instead of PS-RNTI.

[0083] According to this embodiment, terminal 20 can identify the status of intermittent reception from the base station, which can be commonly understood by both terminal 20 and base station 10.

[0084] (Example 4) This embodiment describes an example in which base stations or terminals report capability information to each other regarding intermittent reception between base stations.

[0085] The following capability information may be introduced.

[0086] Base station capability information indicating the capabilities of base station 10 may be introduced. That is, base station 10 transmits base station capability information to terminal 20 or other network nodes. Terminal 20 or other network nodes that receive base station capability information may make assumptions about the capabilities of base station 10 based on the received base station capability information.

[0087] Base station capability information may include information indicating whether or not intermittent base station reception is supported. Furthermore, base station capability information indicating whether or not DCI indications, which show the status of intermittent base station reception, are supported may also be introduced.

[0088] Furthermore, the following terminal capability information may be introduced. For example, terminal capability information indicating whether or not intermittent base station reception is supported may be introduced. Also, terminal capability information indicating whether or not the status of intermittent base station reception is supported may be introduced.

[0089] If terminal 20 has the capability to support identification of the status of intermittent base station reception, it may identify whether the intermittent base station reception function is enabled or disabled. For example, terminal 20 may perform the operation of option 1 shown in Example 1. Alternatively, if terminal 20 does not have the capability to support identification of the status of intermittent base station reception, it may perform the operation of option 2 shown in Example 1.

[0090] Furthermore, terminal capability information indicating whether or not it supports DCI instructions that show the status of intermittent base station reception may be introduced. Additionally, terminal capability information indicating whether or not it supports a new terminal-specific / group-common DCI format may be introduced.

[0091] The dependency between base station capability information and terminal capability information may be any of the following options.

[0092] <Option 1> In order to apply intermittent base station reception, it may be required that both base station capability information and terminal capability information indicating support for intermittent base station reception be reported.

[0093] <Option 2> To apply intermittent base station reception, it may suffice for either base station capability information or terminal capability information indicating support for intermittent base station reception to be reported.

[0094] According to this embodiment, base stations and terminals can report capability information regarding intermittent reception between base stations to each other.

[0095] The terminal capabilities described in each of the above embodiments may be limited to cases where terminal 20 is a function-reduced terminal, or they may be applicable even when terminal 20 is not a function-reduced terminal.

[0096] (Summary of this embodiment 2) Furthermore, cell DTX / DRX is being considered to reduce power consumption at base station 10. For example, alignment between cell DTX / DRX and UE-DRX in RRC connected mode, and information exchange between nodes regarding cell DTX / DRX are being considered.

[0097] The mechanism for enabling or disabling the transmit / receive unit of the base station 10 is important for reducing power consumption at the base station 10. To reduce power consumption at the base station 10, the application of DL transmission and UL reception is being considered.

[0098] Cell DTX / DRX is useful for achieving DL transmission and UL reception adaptation. However, the operational details of cell DTX / DRX were not clear. Therefore, Examples 5 to 8 will be described below as specific embodiments relating to cell DTX / DRX.

[0099] (Example 5) Example 5 describes the definition of cell DTX / DRX. Cell DRX may be defined as in Examples 1-4 above. Whether or not to perform cell DRX is determined by upper-layer parameters, and further, the period, start slot, offset, and duration may be set. In addition, the applicability of cell DRX may be determined by quasi-static, dynamic, or flexible network conditions.

[0100] Cell DTX may be defined as described below. Whether or not to perform Cell DTX is determined by higher-layer parameters, which may also include a period, start slot, offset, and duration. Furthermore, the applicability of Cell DTX may be determined by quasi-static, dynamic, or flexible network conditions.

[0101] <Option 1> Figure 6 is a diagram illustrating the intermittent transmission of a base station according to Embodiment 5 of the present invention. As shown in Figure 6, the period during which the base station 10 disables or enables its own transmission unit may be introduced as a cell DTX.

[0102] The transmitting units and / or parameters to be disabled may be per port, per panel, per beam, per carrier, or per cell. The cell DTX may be defined by some or all of the parameters shown in 1)-6) below. The units of these parameters may be symbols, slots, subframes, milliseconds, or seconds, or other units. The units may be the same or different among these parameters.

[0103] 1) dtx-onDurationTimer: The period from the beginning of the DTX cycle. 2) dtx-SlotOffset: The delay period before starting dtx-onDurationTimer. 3) dtx-InactivityTimer: A period that starts after a DL transmission opportunity (an opportunity when base station 10 performs a DL transmission and terminal 20 receives the DL transmission). 4) dtx-LongCycleStartOffset: dtx-StartOffset defines the start of long DTX cycles (i.e., dtx-LongCycle) and long and short DTX cycles. 5) dtx-ShortCycle: Short DTX cycle. May be optional. 6) dtx-ShortCycleTimer: The period during which base station 10 performs a short DTX cycle. When DL reception occurs during a long DTX, a short DTX is initiated. This may be optional.

[0104] Figure 7 is a diagram illustrating the parameters related to Embodiment 5 of the present invention. As shown in Figure 7, the active time is from the beginning of dtx-LongCycle, after dtx-SlotOffset, for the duration of dtx-onDurationTimer. If DL reception occurs during dtx-LonCycle, the active time ends after dtx-InactivityTimer from the time of DL reception, and dtx-ShortCycle starts. If DL reception occurs during dtx-ShortCycleTimer, dtx-ShortCycle continues. If DL reception does not occur during dtx-ShortCycleTimer, dtx-LongCycle starts.

[0105] When cell DTX is enabled, base station 10 may transmit DL channels or DL ​​signals while dtx-onDurationTimer or dtx-InactivityTimer is operating. As for the operation of terminal 20, when cell DTX is enabled, terminal 20 may receive DL channels or DL ​​signals while dtx-onDurationTimer or dtx-InactivityTimer is operating. Terminal 20 may be assumed to receive DL channels or DL ​​signals when dtx-onDurationTimer or dtx-InactivityTimer is not operating.

[0106] When cell DTX is disabled, terminal 20 may expect to receive DL channels or DL ​​signals as notified or configured to base station 10.

[0107] The DL Channel or DL ​​signal may be any of the following: PDCCH, PDSCH, SPS-PDSCH, CSI-RS, PT-RS, or DM-RS.

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

[0109] (Example 6) Example 6 describes the configuration of the cell DTX / DRX. This configuration may be performed at the base station 10 or at the terminal 20.

[0110] <Option 1> Joint configuration may be performed. Cell DTX and Cell DRX may be configured jointly by common parameters. If common parameters (e.g., CellDTXDRX-Config) are configured, Cell DTX and DRX may be enabled. Terminal 20 may appropriately perform the operation of Embodiment 5.

[0111] The common parameters may include either or both of the information elements 1) and 2) shown below.

[0112] 1) Parameters common to DTX and DRX. Some parameters may be common to both DTX and DRX. For example, the parameter indicating the on-duration timer may be common to both DTX and DRX. For example, the parameter indicating the cycle may be common to both DTX and DRX.

[0113] 2) Parameters separated by DTX and DRX. Some parameters may be set individually for DTX and DRX. For example, the parameter indicating the slot offset may be set individually for DTX and DRX.

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

[0115] <Option 2> Separate configurations may be performed. Cell DTX and cell DRX may be configured individually by separate parameters. If parameters for DTX (e.g., CellDTX-Config) are set, cell DTX may be enabled. If parameters for DRX (e.g., CellDRX-Config) are set, cell DRX may be enabled. Parameters for DTX may include the parameters described in Example 5. Parameters for DRX may include the parameters described in Example 1.

[0116] Option 2 provides greater configuration flexibility when enabling either cell DTX or cell DRX.

[0117] (Example 7) Example 7 describes how to enable or disable cell DTX / DRX. When cell DTX and cell DRX are configured together (Option 1 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows.

[0118] <Option 1> Cell DTX and Cell DRX may be enabled or disabled by RRC signaling. Cell DTX and Cell DRX may be enabled or disabled if RRC parameters are set. For example, the RRC parameters may be the common parameters in Example 6 (e.g., CellDTXDRX-Config).

[0119] <Option 2> Cell DTX and Cell DRX may be enabled or disabled by MAC-CE. When terminal 20 receives MAC-CE, Cell DTX and Cell DRX may be enabled or disabled.

[0120] <Option 3> The DCI may enable or disable cell DTX and cell DRX. Terminal 20 may be dynamically notified by the DCI that cell DTX and cell DRX have been enabled or disabled. Such notification by the DCI may be performed as shown in 1)-4) below.

[0121] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

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

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

[0124] 4) The DCI fields may be a set of existing fields and / or new fields. For example, if they are a set of existing fields, some fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt.1) and Alt.2) below.

[0125] Alt.1) When scrambling is performed by an existing RNTI such as CS-RNTI, and for example HPN is set to all "0", RV to all "00", and TDRA to all "1", terminal 20 may dynamically enable cell DTX and cell DRX. Alternatively, for example HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and TDRA to all "1", terminal 20 may dynamically disable cell DTX and cell DRX.

[0126] Alt.2) When scrambling with a new RNTI, and for example, HPN is set to all "0" and RV is set to all "00", terminal 20 may dynamically enable cell DTX and cell DRX. Also, for example, when HPN is set to all "0", RV is set to all "00", MCS is set to all "1" and FDRA is set to all "1", terminal 20 may dynamically disable cell DTX and cell DRX.

[0127] For example, if there is a new DCI field, the cell DTX and cell DRX may be enabled or disabled by the new DCI field. The new DCI field may be called the "Cell DTX DRX identifier". For example, if the Cell DTX DRX identifier is set to "1", terminal 20 may dynamically enable the cell DTX and cell DRX. Also, for example, if the Cell DTX DRX identifier is set to "0", terminal 20 may dynamically disable the cell DTX and cell DRX. Note that the DCI including the new DCI field may be scrambled with either an existing RNTI or a new RNTI.

[0128] Furthermore, if cell DTX and cell DRX are configured individually (Option 2 in Example 6), cell DTX and cell DRX may be enabled or disabled as follows.

[0129] <Option 1> Cell DTX or Cell DRX may be enabled or disabled by RRC signaling. If RRC parameters are set, Cell DTX or Cell DRX may be enabled or disabled. For example, the RRC parameters may be the separated parameters in Example 6 (e.g., CellDTX-Config, CellDRX-Config).

[0130] <Option 2> The cell DTX or cell DRX may be enabled or disabled by MAC-CE. When terminal 20 receives MAC-CE, the cell DTX or cell DRX may be enabled or disabled.

[0131] <Option 3> Terminal 20 may be dynamically notified by DCI that cell DTX or cell DRX has been enabled or disabled. Such notification by DCI may be performed as shown in 1)-4) below.

[0132] 1) The DCI format may be a UE-specific DCI format or a group-common DCI format.

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

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

[0135] 4) The DCI fields may be sets of existing fields and / or new fields. For example, different sets of DCI fields may be used to enable or disable cell DTX or cell DRX, respectively, so that each set indicates either cell DTX or cell DRX. For example, if they are sets of existing fields, several fields may be used to enable or disable cell DTX and cell DRX, as shown in Alt.1) and Alt.2) below.

[0136] Alt.1) When scrambling is performed by an existing RNTI such as CS-RNTI, and for example HPN is set to all "0", RV to all "00", and PRI to all "1", terminal 20 may dynamically enable cell DTX. Also, for example HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and PRI to all "1", terminal 20 may dynamically disable cell DTX. Also, for example HPN is set to all "0", RV to all "00", and TDRA to all "1", terminal 20 may dynamically enable cell DRX. Also, for example HPN is set to all "0", RV to all "00", MCS to all "1", FDRA to all "1", and TDRA to all "1", terminal 20 may dynamically disable cell DRX.

[0137] The PRI and TDRA fields may also be used to indicate whether the DCI to be enabled or disabled is CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX.

[0138] Furthermore, the same fields used as described above, such as PRI and TDRA (e.g., TDRA), may be used to indicate whether CG-PUSCH / SPS-PDSCH or cell DTX / cell DRX is targeted. When different DCI formats are used, the DCI format may indicate whether cell DTX or cell DRX is targeted. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0139] Alt.2) When scrambling with a new RNTI, for example, if HPN is all set to "0", RV is all set to "00", and PRI is all set to "1", terminal 20 may dynamically enable cell DTX. For example, if HPN is all set to "0", RV is all set to "00", MCS is all set to "1", FDRA is all set to "1", and PRI is all set to "1", terminal 20 may dynamically disable cell DTX. For example, if HPN is all set to "0" and RV is all set to "00", terminal 20 may dynamically enable cell DRX. For example, if HPN is all set to "0", RV is all set to "00", MCS is all set to "1", and FDRA is all set to "1", terminal 20 may dynamically disable cell DRX.

[0140] For example, while PRI is used as described above, additional fields are not required to indicate whether to target cell DTX or cell DRX. When different DCI formats are used, the DCI format may indicate whether to target cell DTX or cell DRX. For example, DCI format 0_0 may enable or disable cell DRX, and DCI format 1_0 may enable or disable cell DTX.

[0141] For example, if it is a new DCI field, the new DCI field may enable or disable cell DTX or cell DRX. The new DCI field may be called a "Cell DTX identifier" or a "Cell DRX identifier".

[0142] When cell DTX and cell DRX are notified separately in separate fields, for example, if the cell DTX identifier is set to "1", terminal 20 may dynamically enable cell DTX. Also, for example, if the cell DTX identifier is set to "0", terminal 20 may dynamically disable cell DTX. For example, if the cell DRX identifier is set to "1", terminal 20 may dynamically enable cell DRX. Also, for example, if the cell DRX identifier is set to "0", terminal 20 may dynamically disable cell DRX.

[0143] Furthermore, the new DCI field may be called the "Cell DTX DRX identifier". When Cell DTX and Cell DRX are notified together in a common field, for example, if the Cell DTX DRX identifier is set to "01", terminal 20 may dynamically enable Cell DTX or dynamically disable Cell DRX. For example, if the Cell DTX DRX identifier is set to "10", terminal 20 may dynamically enable Cell DRX or dynamically disable Cell DTX. For example, if the Cell DTX DRX identifier is set to "11", terminal 20 may dynamically enable Cell DTX and Cell DRX. For example, if the Cell DTX DRX identifier is set to "00", terminal 20 may dynamically enable Cell DTX and Cell DRX. The bit mapping of Cell DTX and Cell DRX described above may be reversed.

[0144] Furthermore, the DCI including the new DCI field may be scrambled with either the existing RNTI or the new RNTI.

[0145] The timing for applying the activation or deactivation of cell DTX or cell DRX as notified by MAC-CE or DCI, as described above, may be either 1) or 2) as shown below.

[0146] 1) Terminal 20 may be immediately enabled or disabled. When MAC-CE or DCI notifies the activation or deactivation of cell DTX or cell DRX, cell DTX or cell DRX may be immediately enabled or disabled.

[0147] 2) Terminal 20 may be enabled or disabled at the notified time. The timing of enabling or disabling cell DTX or cell DRX may be notified via RRC signaling, MAC-CE, or DCI as an interval or time from the time the enabling or disabling is notified. The unit of time may be a symbol, slot, subframe, millisecond, or second. When the enabling or disabling of cell DTX or cell DRX is notified via MAC-CE or DCI, cell DTX or cell DRX may be enabled or disabled at the previously notified time.

[0148] (Example 8) Example 8 describes the related operation between cell DTX / DRX and UE DRX. If the time positions of cell DTX and UE DRX are not aligned, terminal 20 may wake up to receive a DL channel or DL ​​signal when DL transmission is not being performed for cell DTX.

[0149] Therefore, it may be operated as shown in Options 1-5 below.

[0150] <Option 1> If UE DRX is configured (for example, DRX-Config), terminal 20 does not need to assume that cell DTX is configured.

[0151] <Option 2> If cell DTX is configured, terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) is configured. Note that the parameters of cell DTX may be the parameters described in Example 6.

[0152] <Option 3> If UE DRX is configured (for example, DRX-Config), terminal 20 does not need to assume that cell DTX will be configured in a time position that does not match that of UE DRX. If cell DTX and UE DRX are configured in time positions, cell DTX and UE DRX may be configured jointly.

[0153] <Option 4> If cell DTX is configured, terminal 20 does not need to assume that UE DRX (e.g., DRX-Config) is configured if its time position does not match that of cell DTX. If the time positions of cell DTX and UE DRX are aligned, cell DTX and UE DRX may be configured jointly.

[0154] <Option 5> Terminal 20 may be configured with both cell DTX and UE DRX regardless of whether the time positions of cell DTX and UE DRX are aligned or not. Furthermore, if cell DTX is configured in addition to UE DRX, the parameters of cell DTX may take precedence. Terminal 20 may ignore the parameters of UE DRX. Terminal 20 may operate as in Example 5. Also, if cell DTX is configured in addition to UE DRX, the parameters of both may be applied. Terminal 20 may wake up during the active times of both cell DTX and cell DRX.

[0155] The above statement, "The time positions of the cell DTX and UE DRX are aligned," may be defined as in Option 1 or Option 2 shown below.

[0156] <Option 1> If the long cycle is the same for cell DTX and UE DRX, then we can define that the time positions of cell DTX and UE DRX are aligned.

[0157] <Option 1-1> Furthermore, if the long cycles are the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the long cycle. In other words, if the long cycle of cell DTX (e.g., dtx-LongCycle) and the long cycle of UE DRX (e.g., drx-LongCycle) are the same, the time positions may be defined as being aligned.

[0158] <Option 1-2> If the long cycle is the same for cell DTX and UE DRX, then the time positions of cell DTX and UE DRX may be defined as being aligned, depending on the active time within the long cycle. If the on-period timers and slot offsets (e.g., dtx-LongCycle, drx-LongCycle, dtx-onDurationTimer, drx-onDurationTimer, dtx-SlotOffset, drx-SlotOffset) in the long cycle are the same for cell DTX and UE DRX, then the time positions of cell DTX and UE DRX may be defined as being aligned. Furthermore, other parameters (e.g., dtx-InactivityTimer, drx-InactivityTimer, etc.) may be additionally considered to determine whether this definition is satisfied.

[0159] <Option 2> In addition to long cycles, if the short cycle is the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned. Option 2 may be applied if the conditions of Option 1-1 or Option 1-2 are met.

[0160] <Option 2-1> Furthermore, if the short cycles are the same for cell DTX and UE DRX, the time positions of cell DTX and UE DRX may be defined as being aligned regardless of the active time within the short cycle. In other words, if the short cycle of cell DTX (e.g., dtx-ShortCycle) and the short cycle of UE DRX (e.g., drx-ShortCycle) are the same, the time positions may be defined as being aligned.

[0161] <Option 2-2> If the short cycle is the same for cell DTX and UE DRX, then it may be further defined that the time positions of cell DTX and UE DRX are aligned, depending on the active time within the short cycle. If the short cycle timers and short cycles (e.g., dtx-ShortCycleTimer, drx-ShortCycleTimer, dtx-ShortCycle, drx-ShortCycle) are the same for cell DTX and UE DRX, then it may be defined that the time positions of cell DTX and UE DRX are aligned.

[0162] (Summary of this embodiment 3) Here, it is assumed that multiple cell DTX / DRX are effective in accommodating traffic of different QoS types. However, the operational details of multiple cell DTX / DRX were not clear. Therefore, Example 9 will be described below as a specific example involving multiple cell DTX / DRX.

[0163] (Example 9) The settings for each cell DTX / DRX may differ from those of the cell DTX / DRX in the embodiment described above. For example, if multiple cell DTX / DRX are defined by parameters, the dtx-onDurationTimer may differ in the settings for each cell DTX / DRX. Other parameters may also differ in the settings for each cell DTX / DRX.

[0164] The settings for each cell DTX / DRX may include at least the following 1) and 2).

[0165] 1) A configuration index that specifies the index for the settings of cell DTX and / or cell DRX.

[0166] 2) Priority levels corresponding to different traffic types. For example, eMBB (enhanced Mobile Broadband) may have a priority level of 0, URLLC (Ultra-Reliable and Low Latency Communications) may have a priority level of 1, and traffic types with higher priority levels may be given priority.

[0167] Additionally, the number of cell DTX / DRX settings that are activated simultaneously may be configurable.

[0168] <Option 1> Figure 8 is a flowchart illustrating Example (1) of Embodiment 9 of the present invention. In step S11, multiple cell DTX / DRX are set to UE. In the following step S12, all settings of the multiple cell DTX / DRX become effective simultaneously at a certain point.

[0169] Multiple cell DTX / DRX settings may be configured as a list via RRC signaling. For example, the information element CellDTXConfigList may contain multiple cell DTX / DRX settings with different parameters. To enable all multiple cell DTX / DRX settings, the above-described example 7 may be applied.

[0170] <Option 2> Figure 9 is a flowchart illustrating Example (2) of Embodiment 9 of the present invention. In step S21, multiple cell DTX / DRX are set to UE. In the following step S22, some of the settings for multiple cell DTX / DRX become effective simultaneously at a certain point.

[0171] Multiple cell DTX / DRX settings may be configured as a list via RRC signaling. For example, the information element CellDTXConfigList may contain multiple cell DTX / DRX settings with different parameters.

[0172] The cell DTX / DRX configuration to be enabled by MAC-CE and / or DCI may be notified from a list of multiple cell DTX / DRX configurations. Hereafter, cell DTX / DRX configurations will also be referred to simply as configurations.

[0173] When both MAC-CE and DCI are used, X of the N settings may be notified by MAC-CE and activated by DCI, where X is less than N, and N is the total number of settings in the list. To activate the settings, the above-described example 7 may be applied.

[0174] When both MAC-CE and DCI are used, MAC-CE may notify X of N settings, and DCI may enable Y settings, where Y is less than X, X is less than N, and N is the total number of settings in the list. To enable settings, the DCI field may be used to notify which settings are to be enabled. A bitmap may be used in which each bit corresponds to a setting index. The MSB or LSB may correspond to the lowest or highest index of the setting. If a bit in the bitmap is 1, the corresponding setting may be enabled. If a bit in the bitmap is 0, the corresponding setting may be disabled.

[0175] If MAC-CE or DCI is used, X of N settings may be notified by MAC-CE or DCI, where X is less than N and N is the total number of settings in the list. To enable a setting, the MAC-CE or DCI field may be used to indicate which setting is to be enabled. A bitmap may be used in which each bit corresponds to a setting index. The MSB or LSB may correspond to the lowest or highest index of the setting. If a bit in the bitmap is 1, the corresponding setting may be enabled. If a bit in the bitmap is 0, the corresponding setting may be disabled.

[0176] <Option 3> Figure 10 is a flowchart illustrating Example (3) of Embodiment 9 of the present invention. In step S31, multiple cell DTX / DRX are set to UE. In the following step S32, only the setting of a single cell DTX / DRX becomes effective at some point.

[0177] Cell DTX / DRX settings, enabled by MAC-CE and / or DCI, may be notified. Hereafter, cell DTX / DRX settings will also be simply referred to as settings.

[0178] When both MAC-CE and DCI are used, X of the N settings may be notified by MAC-CE, and one of the X settings may be activated by DCI. X is less than N, where N is the total number of settings in the list. To activate the settings, the above-described example 7 may be applied.

[0179] When both MAC-CE and DCI are used, one of the N settings to be enabled may be notified by MAC-CE or DCI, where N is the total number of settings in the list.

[0180] To enable or disable the settings for cell DTX / DRX, several fields may be used. Existing fields (e.g., HPN) or new fields may be used to indicate which settings to enable or disable.

[0181] To jointly configure cells DTX and DRX, if an existing set of DCI fields is used to enable or disable them, it may be configured as shown in 1) or 2) below.

[0182] 1) DCI may be scrambled with an existing RNTI (e.g., CS-RNTI). Furthermore, if, for example, RV is "00" and TDRA is all "1", the UE may dynamically enable cell DTX / DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DTX / DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be enabled.

[0183] For example, if RV is "00", MCS is all "1", FDRA is all "1", and TDRA is all "1", the UE may dynamically disable the cell DTX / DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DTX / DRX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be disabled. The TDRA field may be used additionally to distinguish whether DCI is enabling / disabling CG-PUSCH / SPS-PDSCH or cell DTX / DRX.

[0184] 2) The DCI may be scrambled with a new RNTI. Furthermore, if, for example, RV is "00", the UE may dynamically enable the cell DTX / DRX. The value notified by the HPN field or new field included in the DCI format may indicate that the cell DTX / DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be enabled.

[0185] For example, if RV is "00", MCS is all "1", and FDRA is all "1", the UE may dynamically disable the cell DTX / DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DTX / DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be disabled.

[0186] To combine and configure cells DTX and DRX, the new DCI field may be used to enable or disable it, as shown below.

[0187] The new DCI field may be called a Cell DTX DRX identifier. The new DCI field may be scrambled with an existing RNTI or with a new RNTI.

[0188] For example, if the new DCI field is "1", the UE may dynamically enable the cell DTX / DRX. The value notified by the HPN field or new field included in the DCI format may indicate that the cell DTX / DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be enabled.

[0189] For example, if the new DCI field is "0", the UE may dynamically disable the cell DTX / DRX. The value notified by the HPN field or new field included in the DCI format may indicate that the cell DTX / DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXDRXConfigIndex) should be disabled.

[0190] To configure cells DTX and DRX separately, if an existing set of DCI fields is used to enable or disable them, it may be configured as shown in 1) or 2) below.

[0191] 1) DCI may be scrambled with an existing RNTI (e.g., CS-RNTI). Furthermore, if, for example, RV is "00" and PRI is all "1", the UE may dynamically enable the cell DTX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DTX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be enabled.

[0192] For example, if RV is "00", MCS is all "1", FDRA is all "1", and PRI is all "1", the UE may dynamically disable the cell DTX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DTX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be disabled.

[0193] For example, if RV is "00" and TDRA is all "1", the UE may dynamically enable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be enabled.

[0194] For example, if RV is "00", MCS is all "1", FDRA is all "1", and TDRA is all "1", the UE may dynamically disable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DRX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be disabled.

[0195] Additionally, the PRI and TDRA fields may be used to distinguish whether DCI enables or disables CG-PUSCH / SPS-PDSCH or cell DTX / DRX.

[0196] In the above example, the PRI and TDRA fields are used to distinguish between CG-PUSCH / SPS-PDSCH and cell DTX / DRX, but the same field (e.g., TDRA) may be used to distinguish between CG-PUSCH / SPS-PDSCH and cell DTX / DRX. Using different DCI formats may also indicate whether cell DTX or cell DRX is being specified. For example, DCI format 0_0 may enable / disable cell DRX, and DCI format 1_0 may enable / disable cell DTX.

[0197] 2) DCI may be scrambled with new RNTI. Furthermore, for example, if RV is "00" and PRI is all "1", the UE may dynamically enable the cell DTX. The value notified by the HPN field or new field included in the DCI format may indicate that the cell DTX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be enabled.

[0198] For example, if RV is "00", MCS is all "1", FDRA is all "1", and PRI is all "1", the UE may dynamically disable the cell DTX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DTX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be disabled.

[0199] For example, if RV is "00", the UE may dynamically enable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be enabled.

[0200] For example, if RV is "00", MCS is all "1", and FDRA is all "1", the UE may dynamically disable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DRX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be disabled.

[0201] In the example above, PRI is used to distinguish between cell DTX and DRX, but the DCI field does not necessarily have to be used to distinguish between cell DTX and DRX. Using different DCI formats may indicate whether a cell is DTX or DRX. For example, DCI format 0_0 may enable / disable cell DRX, and DCI format 1_0 may enable / disable cell DTX.

[0202] To configure cells DTX and DRX separately, the new DCI field may be used to enable or disable them as shown in 1) or 2) below.

[0203] 1) The following describes the case where cell DTX and cell DRX are separated and notified using separate DCI fields. The new field for cell DTX may be called the cell DTX identifier, and the new field for cell DRX may be called the cell DRX identifier.

[0204] For example, if the cell DTX identifier is "1", the UE may dynamically enable the cell DTX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DTX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be enabled.

[0205] For example, if the cell DTX identifier is "0", the UE may dynamically disable the cell DTX. A value notified by the HPN field or a new field included in the DCI format may indicate that the setting of the cell DTX corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDTXConfigIndex) should be disabled.

[0206] For example, if the cell DRX identifier is "1", the UE may dynamically enable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be enabled.

[0207] For example, if the cell DRX identifier is "0", the UE may dynamically disable the cell DRX. A value notified by the HPN field or a new field included in the DCI format may indicate that the cell DRX setting corresponding to the notified value among the values ​​set by the RRC parameter (e.g., CellDRXConfigIndex) should be disabled.

[0208] 2) The following describes the case where a common DCI field is used to notify cell DTX and cell DRX. The new field for cell DTX and cell DRX may be called the Cell DTX DRX Identifier. The Cell DTX DRX Identifier may consist of 2 bits.

[0209] For example, if the cell DTXDRX identifier is "01", the UE may dynamically enable cell DTX and dynamically disable cell DRX.

[0210] For example, if the cell DTXDRX identifier is "10", the UE may dynamically disable cell DTX and dynamically enable cell DRX.

[0211] For example, if the cell DTXDRX identifier is "11", the UE may dynamically enable cell DTX and then dynamically enable cell DRX.

[0212] For example, if the cell DTXDRX identifier is "00", the UE may dynamically disable cell DTX and dynamically disable cell DRX.

[0213] The bit mapping above can be reversed, with 0s and 1s being reversed.

[0214] Furthermore, a value notified by the HPN field or a new field included in the DCI format may indicate that the settings for Cell DTX and Cell DRX corresponding to the notified value among the values ​​set by the RRC parameters (e.g., CellDTXConfigIndex and CellDRXConfigIndex) should be activated.

[0215] The new DCI field may be scrambled with an existing RNTI, or it may be scrambled with a new RNTI.

[0216] (Summary of this embodiment 4) It was unclear whether cell DTX / DRX and spatial and / or power domain conformances were supported in combination. If joint operation was supported, it was unclear whether cell DTX / DRX and spatial and / or power domain conformances would be notified in combination, or how they would be notified in combination.

[0217] <Option 1> Cell DTX / DRX and spatial domain fitting and / or power domain fitting do not necessarily have to be operated in combination. For example, the following 1)-4) may be supported. Note that cell DTX / DRX may be cell DTX / DRX in multiple cells.

[0218] 1) Only DTX / DRX cells are supported. 2) Only power domain compliance is supported. 3) Only spatial domain fitting is supported. 4) A combination of spatial domain and power domain adaptation is supported.

[0219] <Option 2> Cell DTX / DRX and spatial domain fitting and / or power domain fitting may be operated in combination. For example, the following 1)-7) may be supported. Note that cell DTX / DRX may be cell DTX / DRX in multiple cells.

[0220] 1) Only DTX / DRX cells are supported. 2) Only power domain compliance is supported. 3) Only spatial domain fitting is supported. 4) A combination of spatial domain and power domain adaptation is supported. 5) Combinations of cell DTX / DRX and spatial domain matching are supported. 6) Cell DTX / DRX and power domain compatibility combinations are supported. 7) Cell DTX / DRX, combinations of spatial domain adaptation and power domain adaptation are supported.

[0221] Notifications relating to cell DTX / DRX and notifications relating to spatial and / or power domain compliance may be performed separately. For example, notifications may be performed as shown in 1)-3) below. Note that cell DTX / DRX may be cell DTX / DRX across multiple cells.

[0222] 1) Notifications regarding cell DTX / DRX and notifications regarding spatial domain conformance will be issued. 2) Notifications regarding cell DTX / DRX and notifications regarding power domain compliance will be issued, respectively. 3) Notifications regarding cell DTX / DRX, notifications regarding spatial domain compliance, and notifications regarding power domain compliance will be issued, respectively.

[0223] Furthermore, notifications regarding compliance in the spatial domain and notifications regarding compliance in the power domain may be carried out as described later. Notifications regarding cell DTX / DRX may be carried out as in the embodiment described above.

[0224] Notifications relating to cell DTX / DRX and notifications relating to spatial and / or power domain compliance may be executed in combination. For example, notifications may be executed as shown in 1)-3) below. Note that cell DTX / DRX may be cell DTX / DRX for multiple cells.

[0225] 1) Notifications related to cell DTX / DRX and notifications related to spatial area conformance are combined and executed. 2) The notification concerning cell DTX / DRX and the notification concerning power area compliance are combined. 3) Notifications relating to cell DTX / DRX, notifications relating to spatial domain compliance, and notifications relating to power domain compliance are combined and executed.

[0226] Figure 11 is a diagram illustrating an example of settings related to CSI reporting.

[0227] Figure 12 is a diagram illustrating an example (1) of the antenna OFF mode.

[0228] Figure 13 is a diagram illustrating example (2) of the antenna OFF mode.

[0229] Figure 14 is a diagram illustrating an example (3) of the antenna OFF mode.

[0230] Figure 15 is a diagram illustrating an example of settings related to multiple CSI reporting (1).

[0231] Figure 16 is a diagram illustrating an example of settings related to multiple CSI reporting (2).

[0232] Figure 17 is a diagram illustrating an example of settings related to a trigger for multiple CSI reporting according to an embodiment of the present invention.

[0233] Here, in order to achieve power saving in the network, it is being considered to efficiently adapt the spatial domain elements in CSI (Channel State Information) reporting and beam management. Furthermore, it is being considered to efficiently adapt the power offset value between PDSCH and CSI-RS in the procedures related to CSI reporting.

[0234] Figure 11 is a diagram illustrating an example of settings related to CSI reporting. Terminal 20 may be configured from base station 10 with the following information 1) and 2) for CSI measurement.

[0235] 1) Reporting setting. The corresponding information element may be CSI-ReportConfig (see Non-Patent Document 3). The reporting setting is information that instructs terminal 20 on how to perform reporting.

[0236] 2) Resource setting. The corresponding information element may be CSI-ResourceConfig. The resource setting is information that notifies terminal 20 of the CSI-RS / SSB resource set to be used for CSI / L1-RSRP measurement.

[0237] For example, as shown in Figure 2, periodic CSI reports, semi-persistent CSI reports, and aperiodic CSI reports can be configured. A CSI-ReportConfig specifies a CSI-ResourceConfig on a one-to-one basis. A CSI-ReportConfig includes a CodebookConfig, which includes nrOfAntennaPorts, typeI-SinglePanel-ri-Restriction, and ri-Restriction.

[0238] As shown in FIG. 11, CSI-ResourceConfig specifies a CSI resource set in a 1-to-S manner. The CSI resource set is, for example, NZP-CSI-RS-ResourceSet, CSI-SSB-ResourceSet, or CSI-IM_ResourceSet. All CSI-RS resources included in one CSI resource set are set with the same number of ports. Note that only one CSI resource set may be set as CMR (Channel measurement resource).

[0239] As shown in FIG. 11, the CSI resource set specifies CSI resources in a 1-to-1 list. The CSI resources are, for example, NZP-CSI-RS-Resource, SSB-Index, or CSI-IM-Resource. CSI-RS-ResourceMapping including the power offset and the number of ports between PDSCH and CSI-RS is included in, for example, NZP-CSI-RS-Resource

[0240] As described above, the number of ports of the CSI-RS for CSI reporting is explicitly notified by NZP-CSI-RS-Resource and CodebookConfig included in CSI-ReportConfig. The power offset between PDSCH and CSI-RS is notified by powerControlOffset included in NZP-CSI-RS-Resource.

[0241] Next, the antenna OFF mode will be described. The mapping between the TxRU (Transceiver Unit) and the antenna and the antenna OFF mode are defined (see Non-Patent Document 4). The sub-array antenna corresponds to a plurality of antennas to which one TxRU is connected. In the sub-array antenna, the antennas connected to different TxRUs are separated. In the full-connection array, all TxRUs are connected to all antennas.

[0242] FIG. 12 is a diagram for explaining an example (1) of the antenna OFF mode. FIG. 12 is an example of mode 1-1 in a subarray. As shown in FIG. 12, some antennas in each subarray are turned OFF. The number of ports does not change, and the beamforming gain decreases.

[0243] FIG. 13 is a diagram for explaining an example (2) of the antenna OFF mode. FIG. 13 is an example of mode 1-2 in a subarray. As shown in FIG. 13, all antennas in the subarray are turned OFF. The number of ports decreases, and the beamforming gain does not change.

[0244] FIG. 14 is a diagram for explaining an example (3) of the antenna OFF mode. FIG. 14 is an example of the fully connected array mode 2. As shown in FIG. 14, some of the antennas are turned OFF. The number of ports does not change, and the beamforming gain decreases.

[0245] Here, for antenna adaptation in the spatial domain and power adaptation in the power domain, it is assumed that a plurality of CSIs based on different antennas and different power assumptions are reported to the base station 10 so that the base station 10 makes a decision regarding the adaptation.

[0246] FIG. 15 is a diagram for explaining an example (1) of the setting related to the plurality of CSI reports. As shown in FIG. 15, a plurality of CSIs that measure a plurality of states of antenna OFF or power reduction in mode 1-1 of the subarray antenna are reported.

[0247] FIG. 16 is a diagram for explaining an example (2) of the setting related to the plurality of CSI reports. As shown in FIG. 16, a plurality of CSIs that measure a plurality of states of the reduced ports due to antenna OFF in mode 1-2 of the subarray antenna are reported.

[0248] In the conventional CSI setting and reporting that perform one setting and one report, there are problems 1)-3) shown below, for example, when performing a plurality of CSI reports.

[0249] 1) If base station 10 creates multiple CSI reporting settings where most of the information is duplicated, the complexity of setting creation at base station 10 increases, and the notification payload increases.

[0250] 2) Multiple measurement procedures for multiple CSI reporting increase the complexity of terminal 20.

[0251] 3) If multiple CSI reports are performed independently, the CSI feedback payload increases.

[0252] Therefore, in order to report multiple CSIs that assume different spaces and / or power levels, the procedure for reporting multiple CSIs may be enhanced as shown in operation 1) below.

[0253] Operation 1) Trigger multiple CSI reports. For example, determine which spatial and / or power assumptions to measure and report.

[0254] The following describes operation 1).

[0255] Multiple CSI reports may be triggered to correspond to different spatial and / or power assumptions. For multiple CSI reports, base station 10 may include multiple spatial and power assumptions in a single CSI report setting.

[0256] The assumptions relating to space may include some or all of the following 1)-3).

[0257] 1) Number of active ports or coefficient, or number of active TxRUs or coefficient. Suitable for antenna OFF mode 1-2. For example, if the coefficient is 0.25, the number of active ports will be 0.25 × (total number of configured ports).

[0258] 2) Active or valid port index. Suitable for Antenna OFF mode 1-2. For example, when all 8 ports have port indices {0, 1, 2, 3} being valid, port indices {4, 5, 6, 7} are invalid or OFF.

[0259] 3) Mapping mode between ports or TxRUs and antennas. For example, the number of active antennas per port or TxRU, or the active coefficient with respect to the number of antennas per port or TxRU. Suitable for Antenna OFF mode 1-1 and mode 2. For example, when the coefficient is 0.25, the number of active antennas per port or TxRU is 0.25 × (the number of antennas set per port or TxRU).

[0260] Assumptions regarding power may include some or all of the following 1)-3).

[0261] 1) Power of RE (Resource Element) of PDSCH and / or CSI-RS or PSD (Power spectrum density) level.

[0262] 2) Power or PSD offset between PDSCH and RE of CSI-RS.

[0263] 3) Additional offset with respect to the existing offset of power or PSD between PDSCH and RE of CSI-RS. For example, the additional offset to powerControlOffset included in NZP-CSI-Resource.

[0264] Assumptions regarding space and power may be notified separately or jointly. One assumption may correspond to one CSI report. Tables 1 and 2 show examples where assumptions regarding space and power are notified jointly.

[0265]

Table 1

[0266] [Table 2]

[0267] As shown in Table 1, a single assumed index may be associated with the index of the active port and the additional power offset, and this information may be communicated to terminal 20.

[0268] As shown in Table 2, a single assumed index may be associated with the number of ports, the coefficient of active antennas per port, and the additional power offset, and notified to terminal 20.

[0269] Assumptions relating to space and / or power may be notified in the following ways: 1)-3)

[0270] 1) Notification may be made by RRC (Radio Resource Control) signaling only, MAC-CE (Medium Access Control - Control Element) only, or DCI (Downlink Control Information) only. Figure 17 is a diagram illustrating an example of settings for triggers for multiple CSI reporting according to an embodiment of the present invention. For example, the assumed index in the table at the top of Figure 17 may be notified to terminal 20 by RRC signaling, and terminal 20 may perform measurements and CSI reporting based on the number of ports and additional power offset corresponding to the assumed index. Note that the DCI may be a UE-specific DCI or a UE group DCI.

[0271] 2) Candidates may be set by RRC signaling, and assumed indexes may be selected by MAC-CE and / or DCI. For example, the table at the top of Figure 17 may be set by RRC signaling, and the assumed indexes or bitmaps of the assumed indexes in that table may be notified by MAC-CE and / or DCI. For example, if the bitmap "1011" is notified, three CSIs corresponding to assumed indexes {0,2,3} may be reported. For example, if index #2 is notified, a CSI corresponding to assumed index 2 may be reported.

[0272] Furthermore, for example, the table at the top of Figure 17 may be set by RRC signaling, and MAC-CE and / or DCI may specify candidate assumptions for a particular space and / or power. For example, if MAC-CE and / or DCI notify that the number of ports is 4, the table may report the CSI assumption for the space and / or power corresponding to the number of ports 4. That is, the CSI corresponding to assumption index 2 may be reported. For example, if MAC-CE and / or DCI notify that the number of ports is 4, the table may report the CSI assumption for the space and / or power corresponding to the number of ports of 4 or less. That is, the CSI corresponding to assumption indices 2 and 3 may be reported.

[0273] 3) RRC signaling, or RRC signaling and MAC-CE, may set up candidates and candidate combinations, and MAC-CE or DCI may notify the combination index. For example, RRC signaling may set up the upper and lower tables in Figure 17, and MAC-CE and / or DCI may specify the combination index for the lower table. Alternatively, for example, RRC signaling may set up the upper table in Figure 17, MAC-CE may set up the lower table in Figure 17, and DCI may specify the combination index for the lower table. As described above, one or more assumption indexes are included in the reported assumptions and are specified in the reported combination index.

[0274] Furthermore, if a CSI report is configured as described above, and the RS resource (e.g., CSI-RS resource) or configuration (e.g., codebook) does not support the CSI report, terminal 20 may drop or ignore the CSI report, or it may not update the CSI report and instead report, for example, the most recently configured CSI measurement.

[0275] Furthermore, the above-described multiple CSI reports may have the following operational attributes in the time domain. For example, the above-described multiple CSI reports may apply to only periodic, quasi-persistent, and aperiodic events. For example, the above-described multiple CSI reports may apply to all of periodic, quasi-persistent, and aperiodic events. For example, the above-described multiple CSI reports may apply to periodic, quasi-persistent, and aperiodic events.

[0276] Furthermore, the following UE capabilities may be reported from terminal 20 to base station 10.

[0277] UE capability indicating whether or not multiple CSI reports are supported. UE capability indicating the maximum number of CSI reports that can be configured by a single CSI reporting setting (e.g., CSI-ReportConfig). UE capability indicating the maximum number of CSI reporting settings (e.g., CSI-ReportConfig) for enhancing multiple CSI reporting. UE capability indicating supported spatial and / or power assumptions. For example, spatial and / or power assumptions may include a reduced number of antenna ports, a reduced number of ports, a reduced power level, spatial and temporal transition times, etc.

[0278] Furthermore, a notification instructing whether or not to enable multiple CSI reporting may be sent from the base station 10 to the terminal 20 via RRC signaling, MAC-CE, or DCI.

[0279] Through the above operation 1), the base station 10 can efficiently trigger CSI reports corresponding to multiple spatial and / or power-related assumptions to the terminal 20.

[0280] Table 3 shows an example where notifications related to cell DTX / DRX, notifications related to spatial domain compliance, and notifications related to power domain compliance are combined and executed.

[0281] [Table 3]

[0282] As shown in Table 3, notifications (enabled or disabled) related to cell DTX / DRX may be set up as a table by RRC signaling, and row indexes may be notified by DCI, allowing the UE to determine the number of active ports, power offset, TCI status of DL and UL, cell DTX status and cell DRX status.

[0283] Figure 18 is a diagram illustrating an example of the TCI format (1).

[0284] Figure 19 is a diagram illustrating an example of the TCI format (2).

[0285] Figure 20 is a flowchart illustrating an example of a TCI notification (1).

[0286] Figure 21 is a flowchart illustrating example (2) of a TCI notification.

[0287] Figure 22 is a diagram illustrating the coupled TCI state.

[0288] Figure 23 shows an example of the antenna mapping mode (1).

[0289] Figure 24 shows an example of antenna mapping mode (2).

[0290] Figure 25 shows an example of the antenna mapping mode (3).

[0291] Figure 26 shows an example of the ES state in an embodiment of the present invention.

[0292] Technologies are being considered to improve network energy saving (hereinafter also referred to as "NW-ES"), i.e., network energy saving, from both the transmission and reception perspectives of base station 10. For transmission and / or reception, efficient operation is required that adapts to time, frequency, space, power domain, etc., dynamically and / or semistatically, and at a finer granularity, using feedback and assistance information from the UE. Information exchange and coordination may also be performed via the network interface.

[0293] Two antenna ports are considered to be QCL (Quasi Co-Location) if the properties of the channel carrying symbols at one antenna port can be estimated from the properties of the channel carrying symbols at the other antenna port. Large-scale properties, such as delay spread, Doppler spread, and SINR (Signal-to-interference-plus-noise ratio) / average gain, allow the UE to optimize the filter coefficients for channel estimation. QCL settings can reduce the number of reference signals or channels that the UE is required to measure.

[0294] Table 4 shows examples of QCL types. As shown in Table 1, four QCL types are defined: QCL type A, QCL type B, QCL type C, and QCL type D. QCL types are defined to communicate information related to large-scale properties and beams.

[0295] [Table 4]

[0296] The Transmission Configuration Indication (TCI) indicates that the Channel State Information Reference Signal (CSI-RS) or the DMRS of a PDSCH / PDCCH can reference the large-scale properties of one or two reference signals (SSB index or NZP (non-zero power)-CSI-RS).

[0297] Figure 18 is a diagram illustrating an example of the TCI format (1). As shown in Figure 3, it is possible to set up two QCL sources with PDCCH DMRS, PDSCH DMRS, and CSI-RS for TRS (Tracking RS) / BM (Beam management) / CSI as QCL targets. The QCL sources are SSB and CSI-RS for TRS / BM / CSI.

[0298] Figure 19 is a diagram illustrating an example of the TCI format (2). As shown in Figure 4, the information elements of the TCI state are defined (see Non-Patent Literature 3). The TCI state may include two QCL pieces of information. Each QCL piece of information may include the serving cell index, BWP-ID, reference signal, and QCL type.

[0299] Figure 20 is a flowchart illustrating an example of TCI notification (1). Figure 20 shows a TCI notification for PDCCH. In step S101, the RRC sets K (up to 64) TCI states for each CORESET. In the following step S102, for each CORESET, if K>1, the MAC-CE enables 1 TCI, and if K=1, the TCI set by the RRC is used. In the following step S103, the CORESET is dynamically switched for PDCCH transmission. In the following step S104, the UE blind decodes all CORESETs for the PDCCH.

[0300] The UE will activate the device 3ms after the slot that sent the HARQ-ACK information corresponding to the PDSCH carrying the activation command.

[0301] Figure 21 is a flowchart illustrating example (2) of TCI notification. Figure 21 shows TCI notification for PDSCH. In step S201, RRC sets M (up to 128) TCI states. In the following step S202, MAC-CE activates up to 8 TCI states. In the following step S203, it is determined whether the gap between DCI and PDSCH is less than the threshold (Threshold-Sched-Offset). If it is less than the threshold (YES in S203), proceed to step S204; if it is greater than or equal to the threshold (NO in S203), proceed to step S205. In step S204, the TCI state of CORESET with the lowest ID of PDCCH is used.

[0302] In step S205, it is determined whether tci-PresentInDCI (see Non-Patent Literature 3) is set. If it is not set (YES in S205), proceed to step S206; if it is set (NO in S206), proceed to step S207. In step S206, the TCI status of the scheduled PDCCH is used. In step S207, DCI notifies the 1TCI ​​status.

[0303] The TCI notification for the reference signal is set by the RRC. The CSI-RS references QCL information from the SSB or other CSI-RS.

[0304] Release 17 features a completely redesigned beam notification mechanism, known as the Release 17 Unified TCI Framework.

[0305] Figure 22 is a diagram illustrating the combined TCI state. The TCI state is indicated by a TCI state field of up to 3 bits contained in DCI format 1_1 (with DL assignment) or DCI format 1_2 (without DL assignment). As shown in Figure 22, with respect to TCI state indication, the combined TCI state and the isolated TCI state can be switched by RRC. As shown in Figure 22, one TCI code point may be associated with one combined TCI state or with one DL-TCI and one / UL-TCI.

[0306] Here, when dynamic network energy saving, which adapts the antenna and transmit power, is applied to the base station 10, it affects the QCL relationship.

[0307] Figure 23 shows an example of antenna mapping mode (1). Figure 23 is an example of sub-array mode, where 1 TxRU (Tx radio unit) is mapped to multiple antennas. That is, antennas for different TxRUs are separated. As shown in Figure 23, turning off some of the antennas in each sub-array increases the beamwidth.

[0308] Figure 24 shows an example of antenna mapping mode (2). Figure 24 is an example of sub-array mode, where 1 TxRU is mapped to multiple antennas. That is, antennas for different TxRUs are isolated. As shown in Figure 24, turning off antennas for each sub-array reduces the number of ports.

[0309] Figure 25 shows an example of antenna mapping mode (3). Figure 25 is an example of full-connection mode, where all TxRUs are connected to all antennas. As shown in Figure 25, turning off some antennas increases the beamwidth.

[0310] When the RS beamwidth changes, the transmit and receive paths change, resulting in changes to delay and beamforming gain. Therefore, QCL type A, QCL type C, and QCL type D are affected.

[0311] A change in the number of RS ports affects all large-scale properties by measuring ports that have already been turned off. Therefore, QCL Type A, QCL Type B, and QCL Type C are affected.

[0312] Regarding power compatibility, a change in RS power alters the average gain and thus the received power. Therefore, QCL type D is affected.

[0313] Table 5 summarizes the QCL types affected by the above.

[0314] [Table 5]

[0315] Therefore, in order to apply network energy saving to base station 10, the following operations 1) to 4) related to QCL / TCI enhancement may be performed.

[0316] Action 1) The Energy Saving State (ES state) may be defined and notified as follows:

[0317] The ES state may include any or more of the following conditions 1)-4).

[0318] 1) Spatial information regarding the number of ports, the number of TxRUs, or the number of antennas. Mapping mode between TxRUs and antennas, and antenna OFF mode. The antenna OFF mode may be one of the modes shown in Figures 23, 24, or 25.

[0319] 2) Power information relating to the transmitted power and / or PSD (Power spectral density). This power information may include the transmitted power and / or PSD itself, the offset of the transmitted power and / or PSD to a reference level, or the maximum transmitted power and / or PSD.

[0320] 3) Information relating to the suitability of time, frequency, space, or power domains for energy saving.

[0321] 4) Figure 26 shows an example of an ES state in an embodiment of the present invention. The information element ES-State shown in Figure 26 includes spatial port information or the number of ports and the PSD offset of the power domain.

[0322] Any or more of the following 1)-3) may be communicated as ES status via RRC signaling, MAC-CE, group, or UE-specific DCI.

[0323] 1) The ES status may be explicitly notified in separate fields. For example, the ES status may be notified in a 2-bit field and the TCI notification in a 3-bit field. These two fields may be included in the same or different MAC-CE or DCI notification or format.

[0324] 2) The ES status may be explicitly notified by combining it with other network energy saving information. For example, the ES status and TCI notification may be notified in a 3-bit field that is jointly coded. Table 6 shows an example where the DL and UL TCIs are combined. Table 7 shows an example where the DL and UL TCIs are separated.

[0325] [Table 6]

[0326] [Table 7]

[0327] 3) The ES state may be implicitly notified. For example, base station 10 may notify spatial, power, and other energy-saving information, and the UE may estimate the ES state based on that energy-saving information.

[0328] If the ES status can be notified by a group or UE-specific DCI, it may be possible to configure whether or not a field indicating the ES status is included in that DCI via RRC signaling.

[0329] Table 8 shows an example where notifications related to cell DTX / DRX, notifications related to spatial domain compliance, and notifications related to power domain compliance are combined and executed.

[0330] [Table 8]

[0331] As shown in Table 8, notifications (enabled or disabled) related to cell DTX / DRX may be set up as a table by RRC signaling, and the row index may be notified by DCI, allowing the UE to determine the number of active ports, power offset, cell DTX status, and cell DRX status.

[0332] (Example 1-1 related to power compliance) Regarding dynamic power instruction for SSB, base station 10 may perform one of the following three actions:

[0333] <Plan 1> The base station 10 may instruct the terminal 20 to use an offset value for SSS-EPRE based on a parameter that indicates the absolute value of SSS-EPRE by the upper layer (for example, "ss-PBCH-BlockPower-adjust"). The terminal 20 derives the adjusted EPRE for SSS as follows:

[0334] SSS EPRE[dBm]="ss-PBCH-BlockPower"[dBm]+"ss-PBCH-BlockPower-adjust"[dB]

[0335] Here, "ss-PBCH-BlockPower-adjust" includes candidate EPRE adjustment values ​​in dB (e.g., 1 bit {-3,0}, 2 bits {-9,-6,-3,0}, or {-6,-3,0,3}).

[0336] Terminal 20 may recognize that the EPRE adjustment value is 0 dB if "ss-PBCH-BlockPower-adjust" does not exist, is not specified, or is not enabled. In other words, in that case, terminal 20 does not need to adjust the EPRE.

[0337] <Plan 2> The base station 10 may instruct the terminal 20 to use a new parameter (for example, "ss-PBCH-BlockPower-r18") to specify the absolute value of EPRE. The terminal 20 derives the adjusted EPRE of the SSS as follows:

[0338] SSS's EPRE[dBm]="ss-PBCH-BlockPower-r18"="dBm]

[0339] The value of the parameter "ss-PBCH-BlockPower-r18" is a candidate for the EPRE of the SSS in dBm units, and is an integer value in the range of (-60...50), for example.

[0340] Terminal 20 may derive the EPRE of the SSS using the default value or "ss-PBCH-BlockPower" instead if "ss-PBCH-BlockPower-r18" does not exist, is not specified, or is not enabled.

[0341] <Plan 3> The base station 10 may instruct the terminal 20 to provide an adjusted value for EPRE based on a previously adjusted EPRE (e.g., "ss-PBCH-BlockPower-adjust2"). The terminal 20 derives the adjusted EPRE for SSS as follows:

[0342] EPRE[dBm] of SSS(i+1) = EPRE[dBm] of SSS(i) + "s - PBCH - BlockPower - adjust2" dB

[0343] Here, the EPRE of SSS(i) refers to the EPRE adjusted immediately before derivation. Also, the EPRE of SSS(i+1) refers to the EPRE adjusted at the time of derivation.

[0344] Note that if i=0, no previous adjustments have been made, so the EPRE adjusted immediately before the derivation is as follows.

[0345] SSS(0) EPRE="ss-PBCH-BlockPower="dBm"

[0346] Here, "ss-PBCH-BlockPower-adjust2" contains candidate EPRE adjustment values ​​in dB (e.g., 1 bit {-3,3}, 2 bits {-3,-1,0,3}, or {-6,-3,0,6}).

[0347] Terminal 20 may recognize that the EPRE adjustment value is 0 dB if "ss-PBCH-BlockPower-adjust2" does not exist, is not specified, or is not enabled. In other words, in that case, terminal 20 does not need to adjust the EPRE.

[0348] (Examples 1-2 related to power compliance) With respect to the dynamic power indication of CSI-RS or PDSCH, the base station 10 may perform one of the following three actions:

[0349] <Plan 1> The base station 10 may instruct the terminal 20 to provide an offset value (e.g., "OffsetAdjust") to "powerControlOffsetSS" or "powerControlOffset".

[0350] The ratio of EPRE in NZP-CSI-RS to EPRE in SSS is equal to "powerControlOffsetSS[dB]+"OffsetAdjust[dB]". Also, the ratio of EPRE in PDSCH to EPRE in NZP-CSI-RS is equal to "powerControlOffset[dB]+"OffsetAdjust[dB]".

[0351] Here, "OffsetAdjust" contains candidate EPRE adjustment values ​​in dB (e.g., 1 bit {-3,3}, 2 bits {-9,-6,-3,0} or {-6,-3,0,3}).

[0352] Terminal 20 may recognize that the EPRE adjustment value is 0dB if "OffsetAdjust" does not exist, is not specified, or is not enabled. In other words, in that case, terminal 20 does not need to adjust the EPRE.

[0353] <Plan 2> The base station 10 may instruct the terminal 20 to provide an absolute value for EPRE using a new parameter (e.g., "ss-PBCH-BlockPower-r18"). Specifically, the base station 10 may instruct the terminal 20 to provide a new value (e.g., "powerControlOffsetSS-r18" or "powerControlOffset-r18") which is the ratio of the EPRE of the CSI-RS to the EPRE of the SSS, or the ratio of the EPRE of the PDSCH to the EPRE of the NZP-CSI-RS, to replace "powerControlOffsetSS" or "powerControlOffset".

[0354] The ratio of EPRE in CSI-RS to EPRE in SSS is equal to "powerControlOffsetSS-r18" if "powerControlOffsetSS-r18" is specified, and equal to "powerControlOffsetSS" otherwise.

[0355] The ratio of the EPRE of PDSCH to the EPRE of NZP-CSI-RS is equal to "powerControlOffset-r18" if "powerControlOffset-r18" is specified, and equal to "powerControlOffset" otherwise.

[0356] <Plan 3> The base station 10 may instruct the terminal 20 to set an EPRE adjustment value (e.g., "OffsetAdjust2") based on a previously adjusted EPRE. The terminal 20 derives the ratio of the CSI-RS EPRE to the SSS EPRE or the ratio of the PDSCH EPRE to the NZP-CSI-RS EPRE as follows:

[0357] PowerRatio(i+1)[dBm]=PowerRatio(i)[dBm]+"OffsetAdjust2"[dB]

[0358] Here, PowerRatio(i) refers to the ratio of the EPRE of the CSI-RS to the EPRE of the SSS, or the ratio of the EPRE of the PDSCH to the EPRE of the NZP-CSI-RS, as adjusted immediately before derivation. PowerRatio(i+1) refers to the ratio of the EPRE of the CSI-RS to the EPRE of the SSS, or the ratio of the EPRE of the PDSCH to the EPRE of the NZP-CSI-RS, as adjusted at the time of derivation.

[0359] In the case of i=0, since no previous adjustments have been made, the ratio of EPRE for CSI-RS to EPRE for SSS, or the ratio of EPRE for PDSCH to EPRE for NZP-CSI-RS, as adjusted immediately before derivation, is as follows.

[0360] PowerRatio(0)="powerControlOffsetSS" or "powerControlOffset"

[0361] Here, "OffsetAdjust2" contains candidate EPRE adjustment values ​​in dB (e.g., 1 bit {-3,3}, 2 bits {-3,-1,0,3}, or {-6,-3,0,6}).

[0362] Terminal 20 may recognize that the EPRE adjustment value is 0dB if "OffsetAdjust2" does not exist, is not specified, or is not enabled. In other words, in that case, terminal 20 does not need to adjust the EPRE.

[0363] Furthermore, if the above adjustments are applied to CSI-RS, terminal 20 may assume that one of the following limitations will be applied, taking into account the time characteristics of CSI-RS.

[0364] <Plan 1> Terminal 20 may assume that the above adjustments apply only to aperiodic CSI-RS or only to semi-persistent CSI-RS.

[0365] <Plan 2> Terminal 20 may assume that the above adjustments apply to both aperiodic CSI-RS and semi-permanent CSI-RS.

[0366] <Plan 3> Terminal 20 may assume that the above-described adjustments apply to aperiodic CSI-RS, semi-permanent CSI-RS, and periodic CSI-RS.

[0367] (Examples 1-3 related to power compliance) This section describes the activation time and validity period of the downlink power indicator.

[0368] When terminal 20 receives a downlink power instruction at slot / symbol / time n, it may assume that a signal will be transmitted from base station 10 using the adjusted downlink power during one of the following proposed activation times.

[0369] <Plan 1-1> When terminal 20 receives a downlink power instruction at slot / symbol / time n, it may assume that signals will be transmitted using the downlink power adjusted by base station 10 from slot / symbol / time n+m until a new downlink power instruction is received.

[0370] Figure 27 is a diagram illustrating Example 1-1 of Embodiment 1-3 relating to power adaptation of an embodiment of the present invention. The time until the downlink power instruction is activated (activation time) is m slots / symbols / hours from slot / symbol / time n to slot / symbol / time n+m. The activation time includes the power transition period (power transition period Toffset).

[0371] <Plan 1-2> When terminal 20 receives a downlink power instruction at slot / symbol / time n, it may assume that a signal is transmitted from base station 10 using the adjusted downlink power from slot / symbol / time n+m to slot / symbol / time n+m+l-1 or n+l-1, after which the downlink power returns to its pre-adjustment level.

[0372] <Plan 1-3> When terminal 20 receives a downlink power instruction at slot / symbol / time n, it may assume that a signal is transmitted from base station 10 using the adjusted downlink power for the PDSCH and / or triggering RS resource in the scheduled slot, and that the downlink power then returns to its pre-adjustment level.

[0373] Figure 28 is a diagram illustrating Example 1-3 of the Power Adaptation Embodiment of the present invention. The time until the downlink power instruction is activated (activation time) is m slot length / symbol length / hour, from slot / symbol / time n to slot / symbol / time n+m. The effective period of the power instruction is 1 slot length.

[0374] The parameters m or l mentioned above are set as follows:

[0375] <Plan 2-1> m or l is a fixed value. For example, m may be 0, in which case terminal 20 may assume that the downlink transmit power has already been adjusted at the slot / symbol / time (e.g., milliseconds) in which the instruction was received.

[0376] Alternatively, for example, m=4, in which case terminal 20 may assume that the downlink transmit power is adjusted 4 slot length / symbol length / time (e.g., milliseconds) after receiving the instruction.

[0377] Alternatively, for example, l=2, in which case terminal 20 may assume that the downlink signal is transmitted using adjusted downlink power in 2 slot length / symbol length / time (e.g., milliseconds).

[0378] <Plan 2-2> Terminal 20 may assume that m or l is set according to one or more of the following elements: The criterion element may be one or more of the following elements: neurology / subcarrier interval, symbol or slot period, power transition period of base station 10 (Examples 1-4), base station capability, reported terminal capability, power adjustment amount, power adjustment direction (i.e., power increased or decreased).

[0379] <Plan 2-3> Terminal 20 may assume that m or l is indicated in RRC / MAC-CE / DCI / SIB.

[0380] (Examples 1-4 related to power compliance) When base station 10 transmits with downlink power adjusted by slot length / symbol length / time n+m, terminal 20 may assume that there is a power transition period Toffset immediately before slot length / symbol length / time n+m.

[0381] Figure 29 is a diagram illustrating Examples 1-4 relating to power adaptation of an embodiment of the present invention. The duration of the power transition period Toffset may be determined by one of the following options.

[0382] <Plan 1-1> Toffset can be a fixed value.

[0383] <Plan 1-2> Terminal 20 may assume that Toffset is set according to one or more of the following elements: The criterion element may be one or more of the following elements: neurology / subcarrier interval, symbol or slot duration, base station capability, reported terminal capability, power adjustment amount, or power adjustment direction (i.e., whether power was increased or decreased).

[0384] <Plan 1-3> Terminal 20 may assume that Toffset is specified in RRC / MAC-CE / DCI / SIB.

[0385] Terminal 20 may assume one of the following options during the power transition period Toffset:

[0386] <Plan 2-1> Terminal 20 may assume that there are no downlink RS (including SSB) transmissions, and / or no PDCCH transmissions, and / or no PDSCH transmissions.

[0387] <Plan 2-2> Terminal 20 may assume that there is no uplink transmission.

[0388] <Plan 2-3> Terminal 20 may assume that there are no downlink or uplink transmissions.

[0389] (Examples 1-5 related to power compliance) In this embodiment, the signal design for downlink transmission power instructions will be described. Terminal 20 may assume that the downlink transmission power instructions include one or more of the following: • SSB power adjustment (Example 1-1) • Power adjustment of CSI-RS (Examples 1-2) • Power adjustment of PDSCH (Examples 1-2) • Activation time (m) and validity period (l) (Examples 1-3) • Power transition period (Toffset) (Examples 1-4)

[0390] Furthermore, in addition to downlink power instructions, terminal 20 may assume that its signaling includes one or more pieces of information from the following spatial domains for energy conservation at base station 10. • Valid port numbers for CSI-RS • Valid codebook settings • Valid CSI-RS resource set • Valid CSI-RS report settings or group of report settings

[0391] Terminal 20 may assume that the downlink transmit power instruction is transmitted in one of the following ways:

[0392] <Plan 1-1> Terminal 20 may assume that candidate values ​​are set by RRC, and that MAC-CE and / or DCI indicate the index of the value selected from the candidate values.

[0393] <Plan 1-2> Terminal 20 may be assumed to be directed solely by MAC-CE.

[0394] <Plan 1-3> Terminal 20 may be assumed to be directed solely by DCI (either terminal-specific or terminal group DCI).

[0395] Furthermore, terminal 20 may assume that, if DCI is used in the above instructions, it will be instructed as one of the following options:

[0396] <Plan 2-1> Terminal 20 may be assumed to be multiplexed into the conventional DCI bitfield of the conventional DCI format.

[0397] <Plan 2-2> Terminal 20 may be assumed to be indicated by a new DCI bitfield in the conventional DCI format. For example, it may be a new bitfield for "DL power indicator" in DCI format 1_0 / 1_1 / 1_2. In this case, since the actual downlink transmission time is the activation time, terminal 20 may assume that the "Effective time" field is omitted.

[0398] As an example, the new bitfield for "DL power indicator" in DCI format 2_6 may also be used. Terminal 20 may assume that one or more elements from power adjustment / activation time / power transition period are added to each block of DCI format 2_6, as follows: DCI Format 2_6: Block number 1, Block number 2, ..., Block number N

[0399] <Plan 2-3> Terminal 20 may be assumed to be indicated in a new DCI format with a new RNTI defined for downlink power indication. For example, terminal 20 may be assumed to be indicated in DCI format 2_x with a new RNTI (ES_RNTI) for notifying a group of terminals 20. Here, terminal 20 may be assumed to have the DCI bit size of the power indication field set by an RRC parameter or specified in the specification.

[0400] According to Example 1 of power compatibility (any of Examples 1-1 to 1-5), the terminal 20 can be assumed to receive instructions for downlink transmission power from the base station 10. This allows the base station 10 to appropriately adjust its transmission power and save energy.

[0401] The following describes an example of notifying terminals of changes to the base station's CSI-RS port number and related reporting settings. Examples 1 and 2 are described below as specific implementations.

[0402] (Example 1 of changing the port number) In this embodiment, we describe an example in which the base station 10 notifies the terminal 20 of the information of antenna ports supported by CSI-RS, and the terminal 20 reports only the CSIs that correspond to the CSI-RS port numbers.

[0403] The base station 10 may provide CSI-RS with explicit or implicit information (hereinafter referred to as "port information") indicating the antenna ports supported for CSI reporting.

[0404] <Option 1-1> The port information may be any of the following options.

[0405] <Plan 1> The port information may also be a CSI-RS port number. For example, any of the port numbers in the following suggestions may be selected from all or some of the permitted antenna ports in CSI-RS.

[0406] <Plan 1-1> The port number may indicate the maximum number of supported antenna ports for the CSI-RS.

[0407] <Plan 1-2> The port number may indicate a combination of supported CSI-RS antenna port numbers. For example, if terminal 20 is configured to report 2-port CSI-RS, 4-port CSI-RS, and 8-port CSI-RS CSIs, and the supported port numbers are reduced to 4, the indicated port information will include {2,4}, which is the combination of supported CSI-RS antenna port numbers.

[0408] <Plan 2> Port information may also be a valid codebook configuration. A valid codebook configuration may be, for example, a "CodebookConfig(s)" corresponding to a supported number of CSI-RS ports.

[0409] <Plan 3> Port information may also be a valid CSI-RS resource set. A valid CSI-RS resource set may be, for example, an "NZP-CSI-RS-ResourceSetId(s)" for channel measurement using a supported number of CSI-RS ports.

[0410] <Plan 4> Port information may also be a valid CSI-RS reporting configuration. A valid CSI-RS reporting configuration may be, for example, a "CSI-ReportConfigId" corresponding to a supported number of CSI-RS ports.

[0411] <Option 1-2> Port information may be presented in one of the following ways:

[0412] <Plan 1> Terminal 20 may receive a configuration of candidate statuses for port information by RRC, or it may receive an indication of a selected status by MAC-CE and / or DCI.

[0413] For example, you could include "CSI-RS-portStateList" as a new information element in "CSI-MeasConfig" for RRC.

[0414] <Plan 2> Terminal 20 may receive port information instructions only from MAC-CE.

[0415] <Plan 3> Terminal 20 may receive port information instructions solely through DCI.

[0416] When using DCI to indicate the port information as described above, the port information may be indicated as one of the following values:

[0417] <Plan 1> Port information may be multiplexed with the conventional DCI bitfield of the conventional DCI format. For example, port information may be multiplexed with the "CSI request" bitfield.

[0418] <Plan 1-1> Traditional fields for port indication may be reinterpreted. For example, the values ​​of new RNTI or other traditional DCI fields may be used to distinguish between their original meaning and port indication. For example, a traditional DCI field may be a "CSI request" bit field. Also, in the case of a DCI format scrambled with traditional RNTI, the value of that field may be interpreted as a CSI request. Furthermore, in the case of a DCI format scrambled with new RNTI, the value of that field may be interpreted as a port indication.

[0419] <Plan 1-2> Conventional fields may be extended to a larger number of bits in order to transmit port information along with the original meaning of the field. For example, the "CSI request" field may be extended to N bits. The first N1 bits of the "CSI request" field may be for port indication and the last N2 bits for the CSI request, where N = N1 + N2.

[0420] <Plan 2> Port information may also be a new DCI bitfield in the traditional DCI format.

[0421] <Plan 3> Port information may be in a new DCI format with a new RNTI defined for port indication.

[0422] In the cases of the aforementioned proposals 2 and 3, the DCI bit size may be indicated by an RRC parameter. For example, "portStateTrigerSize" may be included in "CSI-MeasConfig" as a new information element in the RRC.

[0423] <Options 1-3> The port instruction (by option 1-1 or option 1-2) may be used in any of the following cases:

[0424] <Plan 1> Port instructions may be used only for periodic / semi-permanent / irregular CSI reporting.

[0425] <Plan 2> Port instructions may be used for periodic, semi-permanent, and irregular CSI reporting.

[0426] <Plan 3> Port instructions may be used for both periodic and semi-permanent CSI reporting.

[0427] <Plan 4> Port instructions may be used for both semi-permanent and intermittent CSI reporting.

[0428] <Plan 5> Port instructions may be used for both regular and irregular CSI reporting.

[0429] <Options 1-4> Terminal 20 may, in each of the following cases, perform the actions shown below after receiving port instructions in accordance with options 1-1 and 1-2.

[0430] Terminal 20, in the case of periodic CSI reporting, receives port instructions according to options 1-1 and 1-2, and in the case of CSI reporting by measuring the port number in slot (n) with an unsupported CSI-RS according to the latest port instruction in slot (n), disables the reporting setting from slot (n+X1).

[0431] Furthermore, in the case of periodic CSI reporting, terminal 20 receives port instructions according to options 1-1 and 1-2, and then, in the case of CSI reporting by measuring the port number in slot (n) with a supported CSI-RS according to the latest port instruction in slot (n), it enables the reporting setting from slot (n+X2).

[0432] X1 and X2 may be the same or different. Terminal 20 will not report a CSI if it has an invalid reporting setting. Terminal 20 will report a CSI if it has a valid reporting setting.

[0433] Terminal 20, in the case of semi-persistent CSI reporting, after receiving port instructions according to options 1-1 and 1-2, deactivates the reporting in slot (n+X3) if the CSI-RS port for the already activated semi-persistent CSI reporting is not supported according to the port instructions in slot (n).

[0434] Furthermore, in the case of semi-persistent CSI reporting, terminal 20 recognizes that semi-persistent CSI reporting is not activated if, after receiving port instructions according to options 1-1 and 1-2, the CSI-RS port for the newly activated semi-persistent CSI reporting is not supported according to the latest port instructions.

[0435] In the case of an irregular CSI report, terminal 20 will not report an irregular CSI after slot (n+X4) if, after receiving port instructions according to options 1-1 and 1-2, the CSI-RS port for an already triggered irregular CSI report is not supported according to the port instructions in slot (n).

[0436] Furthermore, in the case of an irregular CSI report, terminal 20 will not report an irregular CSI if, after receiving port instructions according to options 1-1 and 1-2, the CSI-RS port for the newly triggered irregular CSI report is not supported according to the latest port instructions.

[0437] The values ​​of X1, X2, X3, or X4 may be set considering terminal capabilities or port indications (by DCI or MAC-CE).

[0438] In this embodiment, the base station 10 notifies the terminal 20 of the information on the antenna ports supported by CSI-RS, and the terminal 20 reports only the CSIs that correspond to the CSI-RS port numbers. Therefore, the antenna ports supported by the base station 10 can be appropriately limited in the CSI-RS measurement, thereby reducing power consumption.

[0439] (Example 2 of changing the port number) For semi-permanent or irregular CSI reporting, the conventional activation / deactivation / trigger mechanism already supports the selection of settings suitable for reporting by the terminal. However, for periodic CSI reporting, new signaling and configuration are required for instruction.

[0440] Therefore, this embodiment shows an example of defining periodic CSI reporting groups. The base station 10 may semi-statically or dynamically instruct the terminal 20 to select periodic CSI reporting groups for reporting by the terminal.

[0441] <Option 2-1> The RRC may define a regular list of CSI groups.

[0442] A list of periodic CSI groups may be defined as "CSI-PeriodicGroupList" in "CSI-MeasConfig".

[0443] The "CSI-PeriodicGroupList" list may contain one or more "PeriodicCSIGroups." Each "PeriodicCSIGroup" may also contain one or more "CSI-ReportConfigs." In other words, periodic CSI groups may include port information.

[0444] <Option 2-2> The base station 10 may instruct the terminal 20 to provide an index for a periodic CSI group selected for reporting by the terminal, by one of the following means. Based on the notified index, the terminal 20 identifies the selected periodic CSI group and provides periodic CSI reporting using a reference signal for the port number corresponding to the identified CSI group.

[0445] <Plan 1> The base station 10 may, via MAC-CE, instruct the terminal 20 to provide the index of the selected periodic CSI group.

[0446] <Plan 2> The base station 10 may, via DCI, instruct the terminal 20 to use the index of the selected periodic CSI group.

[0447] <Plan 3> The base station 10 may, via MAC-CE and DCI, instruct the terminal 20 to use the index of the selected periodic CSI group.

[0448] When DCI is used to instruct the index of selected periodic CSI groups, the information provided (hereinafter referred to as CSI group information) may be one of the following:

[0449] <Plan 1> CSI group information may be multiplexed with the conventional DCI bitfield of the conventional DCI format. For example, CSI group information may be multiplexed with the "CSI request" bitfield.

[0450] <Plan 2> CSI group information may also be a new DCI bitfield in the conventional DCI format.

[0451] <Plan 3> The CSI group information may be in a new DCI format with a new RNTI defined for the purpose of instructing periodic CSI group indexes.

[0452] This example shows that "PeriodicCSIGroup#2" corresponds to a 4-TRX CSI group, and "PeriodicCSIGroup#3" corresponds to an 8-TRX CSI group.

[0453] In this case, the base station 10 may instruct terminal 20 to use "PeriodicCSIGroup#2" as the index for the periodic CSI group in slot (n) in order to switch to a 4TRX CSI group. Alternatively, the base station 10 may instruct terminal 20 to use "PeriodicCSIGroup#3" as the index for the periodic CSI group in a certain slot in order to switch to an 8TRX CSI group.

[0454] In this embodiment, the base station 10 instructs the terminal 20 to perform periodic CSI reporting. This allows the base station 10 to appropriately limit the antenna ports it supports during periodic CSI reporting, thereby reducing power consumption.

[0455] In the embodiment described above, CSI-RS may be replaced with SSB or other reference signals in the initial access (for example, a positioning reference signal (PRS)), etc.

[0456] The choice of which of the above embodiments to use may be determined by a higher-layer parameter, reported from the terminal 20 to the base station 10 as UE capability, specified by the specification, or reported from the terminal 20 to the base station 10 as UE capability and also determined by a higher-layer parameter. A base station WUS (Wake up signal) may be used for cell DTX in addition to cell DRX. Disabling cell DTX / DRX, which disables all enabled cell DTX / DRX settings, may be introduced.

[0457] Furthermore, UE capabilities may be defined to indicate whether or not cell DTX and cell DRX are supported. UE capabilities may be defined to indicate whether or not dynamic activation or deactivation of cell DTX and cell DRX is supported. UE capabilities may be defined to indicate whether or not cell DTX and cell DRX with UE DRX or CDRX are supported. UE capabilities may be defined to indicate the maximum number of cell DTX / DRX configurations. UE capabilities may be defined to indicate the maximum number of cell DTX / DRX configurations that can be activated simultaneously. UE capabilities may be defined to indicate whether or not combined operation of cell DTX / DRX and spatial and / or power domain conformance is supported. UE capabilities may be defined to indicate whether or not combined notification of cell DTX / DRX and spatial and / or power domain conformance is supported.

[0458] Note that cell DTX / DRX may be replaced by multiple cell DTX / DRX. Among the multiple cells, the first cell and the second cell may have the same or common settings, or, for example, a list of settings may be provided and the settings may be configured individually.

[0459] Note that cell DTX / DRX may be replaced with cell DTX and / or cell DRX. Enable / Disable may be replaced with enable and / or disable.

[0460] The above-described embodiment provides a technology that enables saving power consumption at base stations.

[0461] (Device configuration) Next, we will describe an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above. The base station 10 and terminal 20 include functions to perform the embodiments described above. However, the base station 10 and terminal 20 may each be equipped with only one of the proposed functions from the embodiments.

[0462] <Base station 10> Figure 30 shows an example of the functional configuration of a base station. As shown in Figure 30, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 30 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 110 and the receiving unit 120 may be called the communication unit.

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

[0464] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device and reads it from the storage device as needed. The control unit 140 performs control of the entire base station 10, including control related to signal transmission and reception. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively.

[0465] <Terminal 20> Figure 31 shows an example of the functional configuration of a terminal. As shown in Figure 31, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 31 is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be called the communication unit.

[0466] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The transmitting unit 210 also transmits a HARQ-ACK, and the receiving unit 220 receives the configuration information and the like as described in the embodiment.

[0467] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-set setting information. The control unit 240 controls the entire terminal 20, including control related to signal transmission and reception. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220. The transmission unit 210 and the reception unit 220 may also be called the transmitter and receiver, respectively.

[0468] The terminal or base station of this embodiment may be configured as one of the terminals or base stations described in the following sections. Furthermore, the following communication methods may be implemented.

[0469] <Configuration of this embodiment> (Section 1) A receiving unit that receives first control information relating to an intermittent transmission function in which the base station enables or disables a transmission unit and an intermittent reception function in which the base station enables or disables a reception unit, A control unit that assumes the base station will perform the intermittent transmission function and the intermittent reception function based on the first control information, It has a communication unit that performs transmission and reception with the base station based on the assumed intermittent transmission function and the intermittent reception function, The receiving unit receives control information relating to spatial domain conformance and second control information relating to at least one of power domain conformance. The control unit is a terminal that performs at least one of spatial domain adaptation and power domain adaptation based on the second control information. (Section 2) The receiving unit is the terminal described in paragraph 1, which receives the first control information and the second control information separately. (Section 3) The receiving unit is the terminal described in paragraph 1, which receives the first control information and the second control information in combination. (Section 4) The first control information includes the terminal described in paragraph 1, which includes information indicating whether the intermittent transmission function is enabled or disabled and information indicating whether the intermittent reception function is enabled or disabled. (Section 5) The second control information is the terminal described in paragraph 1, including the number of active ports and the power offset. (Section 6) A procedure for receiving first control information relating to an intermittent transmission function in which a base station enables or disables a transmission unit and an intermittent reception function in which the base station enables or disables a reception unit, A procedure for assuming that the base station performs the intermittent transmission function and the intermittent reception function based on the first control information, A procedure for performing transmission and reception with the base station based on the assumed intermittent transmission function and intermittent reception function, A procedure for receiving control information relating to spatial domain conformance and second control information relating to at least one of power domain conformance, A communication method in which a terminal performs a procedure to perform at least one of spatial domain adaptation and power domain adaptation based on the second control information.

[0470] Any of the above configurations provides a technology that enables saving power consumption at the base station. According to paragraph 2, the cell DTX / DRX and spatial and power compatibility can be configured separately. According to paragraph 3, the cell DTX / DRX and spatial and power compatibility can be configured together. According to paragraphs 4 and 5, the cell DTX / DRX and spatial and power compatibility can be configured.

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

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

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

[0474] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

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

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

[0477] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 30 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 31 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

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

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

[0480] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

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

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

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

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

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

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

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

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

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

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

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

[0492] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0493] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle 2001. The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., installed in the vehicle 2001.

[0494] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

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

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

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

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

[0500] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0501] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

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

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

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

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

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

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

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

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

[0512] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0513] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

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

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

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

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

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

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

[0522] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0523] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0524] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

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

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

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

[0528] For example, one subframe may be called a Transmission Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

[0529] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal 20 to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal 20) in TTI units. However, the definition of TTI is not limited to this.

[0530] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0531] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0532] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0533] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

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

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

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

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

[0539] A BWP may include a BWP for UL (Ultraviolet Link) and a BWP for DL ​​(Download Link). One or more BWPs may be set for a terminal 20 within a single carrier.

[0540] At least one of the configured BWPs may be active, and terminal 20 does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0541] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

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

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

[0545] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols]

[0546] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Front Wheel 2008 Rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A receiving unit that receives first control information relating to an intermittent transmission function in which the base station enables or disables a transmission unit and an intermittent reception function in which the base station enables or disables a reception unit, A control unit that assumes the base station will perform the intermittent transmission function and the intermittent reception function based on the first control information, It has a communication unit that performs transmission and reception with the base station based on the assumed intermittent transmission function and the intermittent reception function, The receiving unit receives control information relating to spatial domain conformance and second control information relating to at least one of power domain conformance. The control unit is a terminal that performs at least one of spatial domain adaptation and power domain adaptation based on the second control information.

2. The terminal according to claim 1, wherein the receiving unit receives the first control information and the second control information separately.

3. The terminal according to claim 1, wherein the receiving unit receives the first control information and the second control information in combination.

4. The terminal according to claim 1, wherein the first control information includes information indicating whether the intermittent transmission function is enabled or disabled and information indicating whether the intermittent reception function is enabled or disabled.

5. The terminal according to claim 1, wherein the second control information includes the number of active ports and a power offset.

6. A procedure for receiving first control information relating to an intermittent transmission function in which a base station enables or disables a transmission unit and an intermittent reception function in which the base station enables or disables a reception unit, A procedure assuming that the base station performs the intermittent transmission function and the intermittent reception function based on the first control information, A procedure for performing transmission and reception with the base station based on the assumed intermittent transmission function and intermittent reception function, A procedure for receiving control information relating to spatial domain conformance and second control information relating to at least one of power domain conformance, A communication method in which a terminal performs a procedure to perform at least one of spatial domain adaptation and power domain adaptation based on the second control information.

Images