Terminal and communication method

By implementing a control unit in the terminal to notify the base station of fallback from LP-WUS to PDCCH monitoring, the patent addresses recognition mismatches, thereby optimizing resource utilization in wireless communication systems.

WO2026235098A1PCT designated stage Publication Date: 2026-11-12NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/017171
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-30
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In wireless communication systems, when a terminal autonomously falls back from monitoring a low-power wake-up signal (LP-WUS) to a control channel (PDCCH), there is a mismatch in recognition between the terminal and the base station, leading to wastage of radio resources due to continued transmission of LP-WUS by the base station.

Method used

The terminal includes a control unit to perform fallback notification to the base station, using methods such as scheduling requests, MAC CE messages, RRC messages, or PRACH, to inform the base station about the fallback to PDCCH monitoring, ensuring synchronized recognition and avoiding unnecessary LP-WUS transmission.

Benefits of technology

This approach prevents radio resource wastage by aligning terminal and base station recognition, optimizing resource utilization through coordinated fallback notifications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026017171_12112026_PF_FP_ABST
    Figure JP2026017171_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This terminal comprises: a control unit that determines whether to perform fallback from a state in which a low-power signal is monitored to a state in which a control channel is monitored; and a transmission unit that transmits a fallback notification to a base station.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal and Communication Method

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

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project) Release 18 (Rel-18), LP-WUS (Low-Power Wake-Up Signal) was introduced. The LP-WUS is a mechanism that uses a wake-up receiver (WUR) capable of operating at all times with low power consumption to determine the presence or absence of paging with the minimum necessary reception function.

[0003] In 3GPP Rel-19, terminal operations when a terminal (UE) falls back from a state of monitoring the LP-WUS to a state of monitoring the PDCCH are under consideration.

[0004] 3GPP TS 38.300 V18.5.0 (2025-03)

[0005] Even after the terminal autonomously performs fallback and stops monitoring the LP-WUS, if the base station continues transmitting the LP-WUS, radio resources will be wasted. However, in the conventional art, when the terminal performs autonomous fallback, a mismatch in recognition between the terminal and the base station cannot be avoided, and the above-described waste of radio resources may occur.

[0006] The present invention has been made in view of the above points, and an object thereof is to provide a technique for avoiding a mismatch in recognition between a terminal and a base station when the terminal falls back from a state of monitoring the LP-WUS to a state of monitoring the PDCCH.

[0007] According to the present embodiment, a terminal includes a control unit that determines to perform fallback from a state of monitoring a low-power signal to a state of monitoring a control channel, and a transmission unit that transmits a fallback notification to a base station.

[0008] According to this embodiment, a technique is provided to avoid inconsistencies in recognition between the terminal and the base station when the terminal falls back from a state of monitoring LP-WUS to a state of monitoring PDCCH.

[0009] This figure shows an example of a wireless communication system in this embodiment. This figure illustrates an example of operation in the first embodiment. This figure illustrates an example of operation of Alt.2 in the first embodiment. This figure illustrates an example of operation of option 2 in the third embodiment. This figure shows an example of the functional configuration of a base station in this embodiment. This figure shows an example of the functional configuration of a terminal in this embodiment. This figure shows an example of the hardware configuration of a base station or terminal in this embodiment.

[0010] Hereinafter, this embodiment (including the first, second, and third embodiments described later) will be explained 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 embodiments described below.

[0011] In the operation of the wireless communication system of this embodiment, existing technologies may be used as appropriate. Such existing technologies include, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0012] Furthermore, in the embodiments 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 technologies, 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 this embodiment, 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 this embodiment, "configuring" wireless parameters means 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 the wireless communication system in this embodiment. The wireless communication system in this embodiment includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminal 20.

[0016] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. The physical resources of 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, in 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 measurement based on the reception results of said reference signals. Terminal 20 may be referred to as UE 20 and base station 10 as gNB 10.

[0019] (About LP-WUS) The Low-Power Wake Up Signal is called LP-WUS or simply WUS, and the Low-Power Wake Up Receiver is called LP-WUR, WUR, or LR. As a substitute for the main radio (MR) used in normal data communication, the LR, a simpler circuit that operates with lower power consumption than the MR, is activated to introduce a state called Ultra-Deep Sleep. The LR may have a function that triggers the power OFF of the MR or the power ON of the MR when the LR receives an LP-WUS signal. In this embodiment, the terminal 20 (specifically, for example, the receiving unit 220) has an MR and an LR.

[0020] The following is the agreement regarding the scope of application of LP-WUS / WUR in 3GPP Rel-19.

[0021] To specify an LP-WUS design that is applicable to both RRC IDLE / INACTIVE and RRC CONNECTED modes, an LP-WUS is specified based on OOK (OOK-1 and / or OOK-4) waveforms, with OFDM sequences overlaid on OOK symbols as needed. At a minimum, duty cycle monitoring of the LP-WUS must be supported. In IDLE / INACTIVE operation, the same information must be delivered regardless of the LP-WUS type, and OFDM sequences may carry the information.

[0022] In RRC IDLE / INACTIVE mode, this specifies the LP-WUS procedure and configuration for paging monitoring triggered by LP-WUS. This procedure and configuration includes at least the settings, subgrouping, and entry / exit conditions for LP-WUS monitoring.

[0023] - For synchronization and / or serving cell RRM, specify an LP-SS with a periodicity of Y[ms] for the LP-WUR. The LP-SS is based on OOK-1 and / or OOK-4 waveforms, with or without an OFDM sequence overlay. For LP-WURs that can receive existing PSS / SSS, the existing PSS / SSS can be used instead of the LP-SS for synchronization and RRM.

[0024] - Specify, including any necessary conditions, that the RRM of the UE MR be further relaxed in measurements of both the serving cell and the neighbor cell, and that the RRM measurement of the UE serving cell be offloaded from the MR to the LP-WUR.

[0025] In RRC CONNECTED mode, the procedure for enabling and disabling LP-WUS monitoring, as well as the procedure for enabling UE MR PDCCH monitoring triggered by LP-WUS, is specified. In CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / RLM / BFD / CSI measurements are performed by MR.

[0026] The target coverage for LP-WUS and LP-SS will be the same as the coverage of PUSCH in message3. Optimization of the LP-WUS signal design for idle / inactive mode takes precedence over optimization for connected mode.

[0027] The following describes LP-WUS for connected mode Option 1-1 / 1-2 and recent agreements regarding LP-WUS for connected mode.

[0028] (Regarding LP-WUS for connected mode Option 1-1 / 1-2) <Option 1-1> In Option 1-1 of LP-WUS CONNECTED mode operation, the following operation is expected.

[0029] Terminal 20 performs LP-WUS monitoring according to the LP-WUS monitoring settings prior to drx-onDurationTimer in order to trigger the start of drx-onDurationTimer.

[0030] Terminal 20 is configured with the same legacy C-DRX as Rel-18.

[0031] Terminal behavior related to CDRX active time triggered by legacy DRX timers will not be affected unless included in this proposal.

[0032] No impact on RRM / RLM / BFD measurement requirements is anticipated.

[0033] For periodic CSI / L1-RSRP reporting, terminal 20 may be configured with one of the following (same as Rel-16 DCP): Periodic CSI / L1-RSRP will not be reported during the time specified by the configured drx-onDurationTimer unless terminal 20 is instructed to wake up.

[0034] Periodic CSI / L1-RSRP is reported periodically during the time specified by the configured drx-onDurationTimer, regardless of whether terminal 20 is instructed to wake up. Periodic CSI / L1-RSRP is reported during the CDRX active time, as in the legacy specification.

[0035] <Option 1-2> For Option 1-2 of LP-WUS CONNECTED mode operation, the following operation is expected.

[0036] Terminal 20 performs LP-WUS monitoring at least outside of the legacy C-DRX active hours, according to the LP-WUS monitoring settings, to trigger PDCCH monitoring.

[0037] The terminal 20 is configured with legacy C-DRX as in Rel-18.

[0038] It is assumed that the terminal 20 is configured with LP-WUS monitoring (the period and offset may be different from those of C-DRX).

[0039] The LP-WUS triggers the start of a timer for the terminal 20 to monitor the PDCCH.

[0040] The UE PDCCH monitoring behavior related to other legacy DRX timers is not affected. The other legacy DRX timers include drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, and the like.

[0041] No impact on RRM / RLM / BFD measurement requirements is assumed. For periodic CSI / L1-RSRP reporting, the terminal 20 may be configured with one of the following (same as Rel-16 DCP and option 1-1).

[0042] • Periodic CSI / L1-RSRP is not reported when the terminal 20 is not instructed to wake up.

[0043] • Periodic CSI / L1-RSRP is reported periodically regardless of whether the terminal 20 is instructed to wake up or not.

[0044] The PDCCH monitoring of the terminal 20 is not triggered by the legacy C-DRX cycle and drx-onDurationTimer when monitoring the LP-WUS.

[0045] Further, in option 1-2, a new timer triggered by the LP-WUS is introduced. When this new timer is running, the terminal 20 is in the C-DRX active time. When the terminal 20 is not in the C-DRX active time, the terminal 20 returns to LP-WUS monitoring.

[0046] When terminal 20 is in the C-DRX active time, UE PDCCH monitoring behavior related to other legacy DRX timers (excluding drx-onDurationTimer) is unaffected.

[0047] (Regarding recent agreements and proposals) <Agreements in RAN1#116> In RRC CONNECTED mode, the following operations are expected to occur.

[0048] PDCCH monitoring triggered by LP-WUS is enabled / disabled by gNB RRC signaling.

[0049] The base station 10 is notified that terminal 20 will perform LP-WUS monitoring.

[0050] If LP-WUS monitoring is enabled, the following options will be further considered.

[0051] Option 1: No additional instructions / conditions are introduced for activating / deactivating LP-WUS monitoring.

[0052] Option 2: Activation / deactivation of LP-WUS monitoring via gNB L1 / L2 signaling with or without UE support is introduced.

[0053] Option 3: Activation / deactivation of LP-WUS monitoring based on conditions such as timers is introduced.

[0054] Option 4: Implicit instructions / conditions are introduced, such as activation / deactivation of LP-WUS monitoring based on UL transmission.

[0055] <Conclusion in RAN1#120> When LP-WUS monitoring is enabled in RRC CONNECTED mode, SR, PRACH, and CG-PUSCH are supported to trigger MR PDCCH monitoring in accordance with legacy UE behavior. This applies at least to option 1-1 as described above.

[0056] <Conclusion from RAN1#120b> When LP-WUS monitoring options 1-2 are enabled for RRC CONNECTED mode, SR, PRACH, and CG-PUSCH are supported to trigger PDCCH monitoring in accordance with legacy UE behavior.

[0057] <Proposal 4-1b in RAN1#120bis> When LP-WUS monitoring option 1-1 is enabled for RRC CONNECTED mode, terminal 20 can fall back to PDCCH monitoring when terminal 20 is monitoring LP-WUS. However, whether and how conditions are considered for the fallback is still under consideration. In the case of LP-WUS operation option 1-1, terminal 20 falls back to legacy C-DRX behavior.

[0058] (Regarding the issue) The ability of terminal 20 to autonomously fall back from the LP-WUS monitoring state to the PDCCH monitoring state may be beneficial when the latest channel quality cannot be tracked by semi-static enable / disable.

[0059] If terminal 20 performs an autonomous fallback (i.e., terminal 20 stops monitoring LP-WUS), it is necessary for base station 10 and terminal 20 to be aware of this. This is because base station 10 would be wasting radio resources if it were to transmit LP-WUS that is not monitored by terminal 20.

[0060] In view of the above, in this embodiment, the terminal 20 notifies the base station 10 whether or not to perform autonomous fallback. The technology according to this embodiment will be described below. In this embodiment, LP-WUS is an example of a low-power signal. PDCCH is an example of a control channel.

[0061] (Outline of Embodiments) In this embodiment, the terminal 20 notifies the base station 10 to fall back to PDCCH monitoring during LP-WUS monitoring. More specific examples of operation are the first, second, and third embodiments described below. In each embodiment, "notification" may be replaced with "instruction," "display," etc.

[0062] First Embodiment: Various approaches to fallback notification, which are described below as Alt. 1 to 4.

[0063] Alt. 1: Terminal 20 sends a scheduling request (SR) as a fallback notification.

[0064] Alt. 2: Terminal 20 sends a MAC CE message as a fallback notification.

[0065] Alt. 3: Terminal 20 sends an RRC message as a fallback notification.

[0066] Alt. 4: Terminal 20 sends PRACH as a fallback notification.

[0067] Second embodiment: An embodiment relating to the operation of terminal 20 when base station 10 does not receive a fallback notification transmitted from terminal 20.

[0068] Third Embodiment: An embodiment relating to the time point at which it is no longer necessary to monitor LP-WUS after terminal 20 has sent a fallback notification.

[0069] The embodiments will be described in detail below. In the following description, " / " represents "or". For example, "A / B" means "A or B".

[0070] (First Embodiment) In the first embodiment, if terminal 20 is configured to perform LP-WUS monitoring, and terminal 20 wants to fall back to PDCCH monitoring (i.e., does not monitor LP-WUS), terminal 20 sends a fallback notification to base station 10. Note that "terminal 20 wants to fall back to PDCCH monitoring (i.e., has already fallen back)" includes "terminal 20 deciding to fall back from a state of monitoring LP-WUS to a state of monitoring PDCCH".

[0071] Furthermore, for terminal 20 configured for LP-WUS monitoring, after terminal 20 sends a fallback notification to base station 10, or after terminal 20 sends a fallback notification and receives a response from base station 10 to the fallback notification, terminal 20 is [not required / expected / does not expect] to monitor LP-WUS.

[0072] An example of operation in the first embodiment will be described with reference to Figure 2.

[0073] In step S101, terminal 20 monitors the LP-WUS transmitted from base station 10.

[0074] In S102, terminal 20 decides to fall back to PDCCH monitoring. In S103, terminal 20 sends a fallback notification to base station 10. In S104, terminal 20 decides not to perform LP-WUS monitoring. Base station 10, having received the fallback notification, also decides that terminal 20 will not perform LP-WUS monitoring.

[0075] Below, we will explain Alt. 1 to 4 as more specific examples of operation.

[0076] <Alt.1> Terminal 20 sends a scheduling request (SR) to base station 10 as a fallback notification. Alt.1 includes Alt.1a to Alt.1c as follows.

[0077] Alt.1a: An existing SR message is used as a fallback notice. In this case, any SR is considered a fallback notice by base station 10, even if it is a normal SR requesting a UL grant.

[0078] Alt.1b: An extended SR message is used as a fallback notification. For example, this SR message contains two bits, which can be used to indicate whether or not terminal 20 will fall back. A specific example of the two-bit value is as follows.

[0079] "00": No UL grant requested, no fallback. "01": UL grant requested. "10": Fallback to PDCCH monitoring requested, no UL grant requested. "11": UL grant and fallback to PDCCH monitoring requested. Alt.1c: Use a dedicated SR configuration (such as a PUCCH resource) for fallback notifications, different from the legacy SR configuration.

[0080] The above is an explanation of Alt.1a to Alt.1c.

[0081] In Alt.1, terminal 20 may or may not expect to receive a PDCCH having a UL grant triggered by SR as a response to the fallback notification.

[0082] When terminal 20 receives a PDCCH with a UL grant triggered by an SR or a PDCCH with a UL grant after an SR has been transmitted, terminal 20 determines that base station 10 has received a fallback notification.

[0083] If terminal 20 does not receive a PDCCH with a UL grant triggered by an SR or a PDCCH with a UL grant after an SR transmission within the time window, terminal 20 determines that base station 10 has not received a fallback notification. This time window may be a legacy monitoring window after an SR transmission or a newly defined window for fallback notifications.

[0084] <Alt.2> In Alt.2, terminal 20 sends a MAC CE message to base station 10 as a fallback notification. Specifically, it is as follows:

[0085] A new MAC CE may be defined to include fallback information, or an existing MAC CE may be extended to include fallback information.

[0086] For example, the MAC CE of a BSR (Buffer State Report) could be extended to include fallback notifications. Alternatively, for example, a 1-bit fallback notification could be included in existing / new MAC CEs.

[0087] If terminal 20 is configured for LP-WUS monitoring, terminal 20 will not be requested / expected / expected to monitor LP-WUS if it sends a fallback notification MAC CE and receives a response from base station 10 to the MAC CE fallback notification (i.e., the NDI of the HPN for MAC CE is reset), or if the fallback notification bit exists, or if the fallback notification bit is set to true or false.

[0088] After a fallback notification is sent by MAC CE in a PUSCH with a HARQ ID, terminal 20 determines that base station 10 has successfully received the fallback notification if the following conditions apply, and otherwise determines that base station 10 has not received the fallback notification.

[0089] Case 1-1: Terminal 20 monitors (or receives) a PDCCH that schedules a new PUSCH transmission with the same HARQ ID.

[0090] Case 1-2: Terminal 20 does not monitor / detect / receive a PDCCH scheduling a retransmission of a PUSCH with the same HARQ ID before the drx-RetransmissionTimerUL timer expires. When Terminal 20 transmits a PUSCH, the timer drx-RetransmissionTimerUL is started to monitor its retransmission. If the timer expires and no retransmission scheduling is received, it means that base station 10 has successfully received the PUSCH.

[0091] An example of operation in Alt.2 will be explained with reference to Figure 3.

[0092] In S201, terminal 20 transmits an SR to base station 10 using PUCCH. In S202, terminal 20 receives a PDCCH with a UL grant from base station 10. In S203, terminal 20 transmits a PUSCH with a fallback notification via MAC CE to inform base station 10 that it will not monitor LP-WUS. In S204, terminal 20 determines whether base station 10 has received the notification, for example, by whether or not there is a response from base station 10.

[0093] Furthermore, when using PUSCH for fallback notifications, information indicating that it is a fallback notification (e.g., a specific bit value) may be included in data other than MAC CE. In other words, when terminal 20 sends data using PUSCH, it may include a fallback notification in that data.

[0094] <Alt.3> Next, Alt.3 will be explained. In Alt.3, terminal 20 sends an RRC message to base station 10 as a fallback notification. Specifically, it is as follows.

[0095] Include fallback information in new IEs or extended versions of existing IEs. For example, a 1-bit fallback notification can be included in RRC IEs.

[0096] If terminal 20 is configured for LP-WUS monitoring, terminal 20 sends a fallback notification RRC message, and [if it receives a response from base station 10 to the RRC fallback notification (i.e., if the HPN's NDI for the RRC message is reset), or if the fallback notification bit is present, or if the fallback notification bit is set to true or false], terminal 20 [is not requested / expected / does not expect] to monitor LP-WUS.

[0097] After sending a fallback notification via PUSCH with a HARQ ID by RRC, terminal 20 determines that base station 10 has successfully received the fallback notification if the following conditions apply; otherwise, terminal 20 determines that base station 10 has not received the fallback notification.

[0098] Case 2-1: Same as Case 1-1 in Alt.2 above.

[0099] Case 2-2: Same as Case 1-2 in Alt.2 above.

[0100] Case 2-3: When terminal 20 receives an RRC message from base station 10 indicating that base station 10 has correctly received the fallback notification.

[0101] <Alt.4> Next, we will explain Alt.4. In Alt.4, terminal 20 sends [PRACH / Random Access Msg1] as a fallback notification. This transmission is similar to Msg1 based on On-Demand OSI. Specifically, it is as follows:

[0102] A [PRACH preamble / PRACH opportunity], or a set of [PRACH preambles / PRACH opportunities], may be reserved for fallback notifications.

[0103] In the case of terminal 20 configured for LP-WUS monitoring, after terminal 20 sends a fallback notification PRACH to base station 10, or after terminal 20 sends a PRACH and receives a response from base station 10 to the PRACH, terminal 20 is not required / expected / does not expect to monitor LP-WUS.

[0104] Terminal 20 may or may not expect to receive a RAR (Random Access Response) as a response to the fallback notification.

[0105] If terminal 20 receives an RAR in the RAR window as a response to a fallback notification, terminal 20 will assume that base station 10 has received a fallback notification.

[0106] If terminal 20 does not receive a RAR in response to a fallback notification within the RAR window, terminal 20 determines that base station 10 did not receive a fallback notification. The RAR window length may reuse legacy parameters (reusing the RAR window length of Msg1 based on on-demand OSI) or may be newly defined.

[0107] <Common to Alt.1-4> Terminal 20 may be able to send a fallback notification in any of the following cells / BWPs.

[0108] - For each cell group, only Pcells or only PSCells.

[0109] Any serving cell.

[0110] - Initial / default BWP only.

[0111] - Any active BWP.

[0112] <Effects of the First Embodiment> According to the first embodiment, the terminal 20 sends a fallback notification to the base station 10, so the base station 10 can understand that the terminal 20 is performing a fallback.

[0113] (Second Embodiment) Next, a second embodiment will be described. In the second embodiment, the operation of the terminal 20 when the base station 10 does not receive a fallback notification will be described.

[0114] If terminal 20 does not receive a PDCCH with an UL grant (for example, base station 10 does not receive an SR), terminal 20 performs one of the following options 1 to 4. That is, if terminal 20 determines that base station 10 has not received a fallback notification, terminal 20 performs one of the following options 1 to 4.

[0115] Option 1: Terminal 20 resends the fallback notification. The total number of fallback notification transmissions and retransmissions shall not exceed a predefined / configured number. If the total number exceeds the predefined / configured number, terminal 20 may perform other optional actions.

[0116] Option 2: Terminal 20 remains in LP-WUS monitoring mode. That is, terminal 20 does not fall back to PDCCH monitoring.

[0117] Option 3: Terminal 20 will fall back to PDCCH monitoring. That is, terminal 20 will not perform LP-WUS monitoring and will fall back to PDCCH monitoring. Specifically, PDCCH monitoring will be performed using one of the following three methods.

[0118] - Perform PDCCH monitoring without a C-DRX timer. In other words, always perform PDCCH monitoring.

[0119] - Perform PDCCH monitoring based on the C-DRX timer.

[0120] - Perform PDCCH monitoring based on a new timer (for example, the new timer in Option 1-2 of the explanation of the agreements mentioned above).

[0121] Option 4: Terminal 20 performs random access. For example, in the cases of Alt1 to Alt3 of the first embodiment, if base station 10 does not receive a fallback notification, terminal 20 attempts to perform random access for RRC reconfiguration to notify of the fallback. In performing random access, terminal 20 sends a random access preamble to base station 10.

[0122] <Effects of the Second Embodiment> According to the second embodiment, when the base station 10 determines that it has not received a fallback notification from the terminal 20, the terminal 20 can continue to operate appropriately.

[0123] (Third Embodiment) Next, a third embodiment will be described. In the third embodiment, the time point at which terminal 20 no longer needs to monitor LP-WUS after sending a fallback notification will be described.

[0124] After sending a fallback notification, terminal 20 no longer needs to monitor LP-WUS, or terminal 20 assumes that base station 10 will not send LP-WUS to terminal 20, or terminal 20 starts monitoring PDCCH.

[0125] The following options 1 and 2 are available for determining the "point in time" mentioned above. Here, we will refer to this "point in time" as the point in time when LP-WUS monitoring is not required.

[0126] <Option 1> In Option 1, the terminal 20 and base station 10 do not need a response from base station 10 to a fallback notification when determining the time point at which LP-WUS monitoring is unnecessary. More specifically, Option 1 has the following options.

[0127] Option 1-1: Terminal 20 and base station 10 determine that the point in time when LP-WUS monitoring is not required is the time position at the end of the last symbol including SR. Option 1-1 is suitable for Alt.1 of the first embodiment.

[0128] Option 1-1a: Terminal 20 and base station 10 determine that LP-WUS monitoring is not required at the time position of the end of n1 symbol after the last symbol containing the SR.

[0129] Option 1-1b: When the terminal 20 and base station 10 transmit an SR or the last symbol of an SR in slot m, they determine that the point at which LP-WUS monitoring is not required is the time position at the end of slot m+s1.

[0130] Option 1-2: Terminal 20 and base station 10 determine that the point in time when LP-WUS monitoring is not required is the time position at the end of the last symbol of PUSCH with MAC CE / RRC fallback notification. Option 1-2 is suitable for Alt. 2 / 3 of the first embodiment.

[0131] Option 1-2a: Terminal 20 and base station 10 determine that LP-WUS monitoring is unnecessary at the time position of the end of n2 symbol after the last symbol of above PUSCH.

[0132] Option 1-2b: When the PUSCH or the last symbol of the PUSCH is transmitted in slot m, the terminal 20 and the base station 10 determine that the time when LP-WUS monitoring is not required is the time position at the end of slot m+s2.

[0133] Option 1-3: The terminal 20 and base station 10 determine that the point at which LP-WUS monitoring is not required is the time position at the end of the last symbol of PRACH for fallback notification. Option 1-3 is suitable for Alt.4 of the first embodiment.

[0134] Option 1-3a: Terminal 20 and base station 10 determine that LP-WUS monitoring is unnecessary at the time position of the end of n3 symbol after the last symbol of above PRACH.

[0135] Option 1-3b: The terminal 20 and the base station 10 determine that the point at which LP-WUS monitoring is not required is the time position at the end of slot m+s3, if the above PRACH or the last symbol of the above PRACH is in slot m.

[0136] <Option 2> In Option 2, the terminal 20 and base station 10 need a response from base station 10 to the fallback notification in order to determine the time point at which LP-WUS monitoring is not required. After receiving the response, terminal 20 determines that LP-WUS monitoring is not required at the time point and falls back to PDCCH monitoring.

[0137] Referring to Figure 4, the operation of Option 2 will be explained. In S301, terminal 20 sends a fallback notification to base station 10. In S302, terminal 20 receives a response sent from base station 10. In S303, terminal 20 determines that LP-WUS monitoring is unnecessary at the time when it is not required and falls back to PDCCH monitoring. Base station 10 may also determine when LP-WUS monitoring is unnecessary using the same judgment as terminal 20. More specific options in Option 2 will be explained below.

[0138] Option 2-1: Terminal 20 and base station 10 determine that the point in time when LP-WUS monitoring is not required is the time position of the end of the last symbol of the PDCCH having an UL grant triggered by SR. Option 2-1 is suitable for Alt.1 of the first embodiment.

[0139] Option 2-1a: Terminal 20 and base station 10 determine that LP-WUS monitoring is not required at the time position of the end of n1 symbol after the last symbol of the above PDCCH.

[0140] Option 2-1b: The terminal 20 and the base station 10 determine that the point at which LP-WUS monitoring is not required is the time position at the end of slot m+s1, when the PDCCH or the last symbol of the PDCCH is in slot m.

[0141] Option 2-2: Terminal 20 and base station 10 determine the time point at the end of the PDCCH's last symbol having a new PUSCH transmission scheduling with the same HARQ ID as the PUSCH (drx-RetransmissionTimerUL timer for the PUSCH that sends the fallback notification) when Terminal 20 sends a fallback notification, as the time point at the end of the PDCCH's fallback notification. Option 2-2 is suitable for Alt.2 / 3 of the first embodiment.

[0142] Option 2-2a: Terminal 20 and base station 10 determine the time point at which n2 symbol ends after [the last symbol of the above PDCCH / the end of the above drx-RetransmissionTimerUL timer] is a time when LP-WUS monitoring is not required.

[0143] Option 2-2b: Terminal 20 and base station 10 determine that the time position at the end of slot m+s2 is a time when LP-WUS monitoring is not required if [the above PDCCH or the last symbol of the above PDCCH / the end of the above drx-RetransmissionTimerUL timer] is in slot m.

[0144] Option 2-3: Terminal 20 and base station 10 determine the time point at the end of the last symbol of the PDSCH of the RAR for the PRACH of the fallback notification as the point at which LP-WUS monitoring is not required. Option 2-3 is suitable for Alt.4 of the first embodiment.

[0145] Option 2-3a: Terminal 20 and base station 10 determine the time point at the end of n3 symbol after the end of the last symbol of the above PDSCH as a time when LP-WUS monitoring is not required.

[0146] Option 2-3b: Terminal 20 and base station 10 determine that LP-WUS monitoring is not required at the time position of the end of slot m+s3 if the PDSCH or the last symbol of the PDSCH is in slot m.

[0147] Option 2-4: Terminal 20 and base station 10 determine that the time point at the end of the last symbol of PUCCH / PUSCH, which has a HARQ ACK for the RRC message from base station 10 as a response to the fallback notification, is a time point where LP-WUS monitoring is not required. Option 2-4 is suitable for Alt.3 of the first embodiment.

[0148] Option 2-4a: Terminal 20 and base station 10 determine that the time point at the end of n4 symbol after the last symbol of above PUCCH / PUSCH is a time when LP-WUS monitoring is not required.

[0149] Option 2-4b: Terminal 20 and base station 10 determine that if the PUCCH / PUSCH or the last symbol of the PUCCH / PUSCH is in slot m, the time position at the end of slot m+s4 is a time when LP-WUS monitoring is not required.

[0150] The parameters such as n1 used in the third embodiment are defined, for example, as follows.

[0151] ni / si / m are non-negative integers, where i = 1, 2, 3, ...

[0152] - ni / si may or may not take into account the wake-up delay of MR.

[0153] For example, si = 3N subframe,μ slot +d, where d is the wake-up delay. subframe,μ slot This is defined in the existing specifications and is the number of slots contained within one subframe in μ (SCS). subframe,μ slot This is based on the SCS of one of the following Alts, for example.

[0154] Alt.a: Terminal 20 is an active BWP SCS that sends the above SR / PRACH / PUSCH.

[0155] Alt.b: SCS of an active BWP where terminal 20 receives PDCCH / PDSCH.

[0156] Alt.c: The smaller SCS / larger SCS of Alt.a and Alt.b.

[0157] <Effects of the Third Embodiment> According to the third embodiment, terminal 20 (and base station 10) can clearly determine the time point at which terminal 20 no longer needs to monitor LP-WUS after sending a fallback notification.

[0158] (Matters common to the first to third embodiments)

[0159] In this embodiment, terminal 20 may report its UE capability to the network (e.g., base station 10). The capability information may include, for example, at least one of the following:

[0160] - Capabilities relating to each embodiment described above (information indicating that each embodiment is supported) - Capabilities relating to each option in each embodiment or combination of options - Capabilities relating to each Alt. in each embodiment or combination of Alts Terminal 20 may report the above capability information in frequency units. The frequency units may include at least one of UE units, FR1, FR2, FR2-1, FR2-2, FR3, subcarrier spacing (SCS) units, band, BC, FC, or FSPC units.

[0161] Terminal 20 may report the above capability information on a cell-by-cell basis. A cell-by-cell basis may include at least one of the following units: UE unit, cell-by-cell basis, or TDD and FDD.

[0162] In this embodiment, the terminal 20 may receive the following types of information from the network (for example, the base station 10).

[0163] - Information via upper-layer signaling (e.g., RRC messages / LPP messages) - MAC CE A MAC CE may be a MAC CE with a new LCID in the subheader, or an existing MAC CE may be an extended MAC CE (e.g., a MAC CE with a new octet introduced).

[0164] - DCI: The DCI field may be an existing DCI field or a newly introduced DCI field. The DCI may be an existing RNTI or a newly introduced RNTI with a scrambled CRC. The DCI format may be an existing DCI format or a newly introduced DCI format. A combination of these may be applied in the DCI.

[0165] In this embodiment, the terminal 20 may receive information from the network periodically, semi-persistently (triggered by instructions from the terminal 20 or base station 10), or aperiodically (triggered by instructions from the terminal 20 or base station 10).

[0166] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include functions to implement all of the embodiments described above. However, the base station 10 and terminal 20 may each have only some of the functions of all embodiments.

[0167] <Base Station 10> Figure 5 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Figure 5, 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 5 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations in this embodiment. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as the communication unit.

[0168] 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 from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, LP-WUS, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.

[0169] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to the operation described in each embodiment.

[0170] The control unit 140 performs control in setting, instructing, and notifying about the operations described in the embodiment. 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.

[0171] <Terminal 20> Figure 6 is a diagram showing an example of the functional configuration of terminal 20 in this embodiment. As shown in Figure 6, 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 6 is just one example. Any functional classification and functional unit names are acceptable as long as they can perform the operations in this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0172] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information for the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, LP-WUS, etc. transmitted from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information on the operation described in the embodiment.

[0173] As described in each embodiment, the control unit 240 performs control in setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0174] (Hardware Configuration) The block diagrams (Figures 5 and 6) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. 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, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.

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

[0176] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.

[0177] 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 memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.

[0178] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit, call processing unit, etc., may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.

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

[0180] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).

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

[0182] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., card, stick, key drive), a floppy® disk, a magnetic strip, or a combination of at least two of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.

[0183] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or at least a combination of these. For example, a transmit / receive antenna, amplifier section, transmit / receive section, or transmission path interface may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

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

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

[0186] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, 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.

[0187] <Additional Notes> (Additional Note 1) A terminal comprising a control unit that decides to fall back from a state of monitoring low-power signals to a state of monitoring control channels, and a transmission unit that transmits a fallback notification to a base station. (Additional Note 2) The terminal according to Additional Note 1, wherein the transmission unit transmits a scheduling request, MAC CE (Medium Access Control Control Element), RRC (Radio Resource Control) message, or PRACH (Physical Random Access Channel) to the base station as the fallback notification. (Additional Note 3) The terminal according to Additional Note 1, wherein, when the control unit determines that the base station has not received the fallback notification, the transmission unit retransmits the fallback notification to the base station, the control unit maintains the state of monitoring low-power signals, or the transmission unit performs random access. (Additional Note 4) The terminal according to Additional Note 1, wherein, after the transmission unit has transmitted the fallback notification to the base station, the control unit determines that it is not necessary to monitor low-power signals at the time of a specific symbol related to the transmission of the fallback notification. (Appendix 5) The terminal according to Appendix 1, wherein after the transmitting unit has transmitted the fallback notification to the base station, the control unit determines that it is not necessary to monitor the low-power signal at the time of a specific symbol related to the reception of a response from the base station to the fallback notification. (Appendix 6) A communication method performed by a terminal, comprising the steps of deciding to fall back from a state of monitoring a low-power signal to a state of monitoring a control channel, and transmitting a fallback notification to a base station.

[0188] In any of the above configurations, when the terminal falls back from monitoring LP-WUS to monitoring PDCCH, a mismatch in recognition between the terminal and the base station can be avoided. According to Appendix 2, various signals can be used as fallback notifications. According to Appendix 3, even if the base station 10 determines that it has not received a fallback notification, it can continue to operate appropriately. According to Appendix 4, the terminal can clearly determine the point at which it no longer needs to monitor low-power signals.

[0189] (Supplement to Embodiments) Although these embodiments have been described above, the disclosed invention is not limited to these 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. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0190] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.

[0191] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", "Radio Access Network (RAN)", and "Network" may be used interchangeably.

[0192] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.

[0193] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE 20)", "Device", "module", and "Terminal" may be used interchangeably.

[0194] The terminal may be called 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other appropriate term.

[0195] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0196] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be interpreted as a sidelink channel.

[0197] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

[0198] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0199] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.

[0200] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0201] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).

[0202] Furthermore, in this disclosure, the action of "the terminal receiving information from the base station" is accompanied by the actions of "the base station transmitting the information to the terminal," "the base station generating the information," or both. Similarly, the action of "the terminal transmitting information to the base station" is accompanied by the action of "the base station receiving the information from the terminal." In addition, actions such as "the terminal is configured to..." or "configure the terminal to..." may include the actions of "the base station transmitting configuration information regarding the terminal's settings" and "the terminal configuring a predetermined action based on the configuration information."

[0203] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during execution.

[0204] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.

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

[0206] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0207] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.

[0208] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0209] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.

[0210] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0211] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.

[0212] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.

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

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

[0215] This patent application claims priority based on Japanese Patent Application No. 2025-078583, filed on 9 May 2025, and the entire contents of Japanese Patent Application No. 2025-078583 are incorporated herein by reference.

[0216] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A terminal comprising a control unit that decides to fall back from a state of monitoring low-power signals to a state of monitoring control channels, and a transmission unit that transmits a fallback notification to a base station.

2. The terminal according to claim 1, wherein the transmitting unit transmits a scheduling request, a MAC CE (Medium Access Control Control Element), an RRC (Radio Resource Control) message, or a PRACH (Physical Random Access Channel) to the base station as the fallback notification.

3. The terminal according to claim 1, wherein, when the control unit determines that the base station has not received the fallback notification, the transmitting unit resends the fallback notification to the base station, the control unit maintains a state of monitoring the low-power signal, or the transmitting unit performs random access.

4. The terminal according to claim 1, wherein after the transmitting unit has transmitted the fallback notification to the base station, the control unit determines that it is not necessary to monitor the low-power signal at the time point of a specific symbol related to the transmission of the fallback notification.

5. The terminal according to claim 1, wherein after the transmitting unit has transmitted the fallback notification to the base station, the control unit determines that it is not necessary to monitor the low-power signal at the time point of a specific symbol related to the reception of the response from the base station to the fallback notification.

6. A communication method performed by a terminal, comprising the steps of deciding to fall back from a state of monitoring low-power signals to a state of monitoring control channels, and transmitting a fallback notification to a base station.