Terminal and communication method

Abstract

This terminal comprises: a control unit that monitors a low-power wake-up signal at a monitoring opportunity; and a reception unit that receives the monitored low-power wake-up signal. The control unit does not monitor the low-power wake-up signal during a prescribed period.

Description

Terminal and Communication Method

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

[0002] Technologies for further increasing the capacity of 3GPP (Registered Trademark) (3rd Generation Partnership Project) systems, further increasing the data transmission speed, and further reducing latency in the radio section are being studied (for example, Non-Patent Document 1 and Non-Patent Document 2). Furthermore, in 3GPP Rel-19, technologies for low-power wake-up signals (LP (Low Power)-WUS (Wake Up Signal) / LP-WUR (Wake Up Receiver)) for reducing power consumption in wireless communication systems are being discussed.

[0003] When the terminal enters a low-power state, it performs LP-WUS monitoring during an LP-WUS monitoring opportunity (also referred to as an LP-WUS opportunity) based on the LP-WUS setting information.

[0004] 3GPP TS 38.300 V18.2.0(2024-06)3GPP TS 38.401 V18.2.0(2024-06)

[0005] However, in the conventional 3GPP standards, there is no regulation on how the terminal should control LP-WUS monitoring when other operations of the terminal (for example, C-DRX operation) are executed during LP-WUS monitoring or when an LP-WUS monitoring opportunity collides with other signals. Therefore, there is a possibility that the terminal may not be able to appropriately execute LP-WUS monitoring or receive LP-WUS.

[0006] The terminal in the present embodiment includes a control unit that monitors a low-power wake-up signal during a monitoring opportunity, and a receiving unit that receives the monitored low-power wake-up signal, and the control unit does not monitor the low-power wake-up signal during a predetermined period.

[0007] According to this embodiment, the control of LP-WUS monitoring is clarified when other operations are performed on the terminal during LP-WUS monitoring, or when the LP-WUS monitoring opportunity conflicts with other signals, thereby enabling appropriate LP-WUS monitoring and LP-WUS reception by the terminal.

[0008] This is a diagram illustrating the wireless communication system in this embodiment. This is a diagram illustrating an example of the procedure for LP-WUS to trigger PDCCH monitoring. This is a diagram illustrating an example of the procedure for LP-WUS to trigger PDCCH monitoring. This is a diagram illustrating an example of the procedure for LP-WUS to trigger PDCCH monitoring. This is a diagram illustrating an example of the procedure for LP-WUS to trigger PDCCH monitoring. This is a diagram illustrating an example of the period during which LP-WUS monitoring is not performed in Example 1-1. This is a diagram illustrating an example of the operation of the terminal during the period during which LP-WUS monitoring is not performed in Example 1-2. This is a flowchart illustrating an example of the operation of the terminal in Example 2. This is a diagram illustrating an example of the functional configuration of the base station in this embodiment. This is a diagram illustrating an example of the functional configuration of the terminal in this embodiment. This is a diagram illustrating an example of the hardware configuration of the base station or terminal in this embodiment. This is a diagram illustrating an example of the configuration of the vehicle in this embodiment.

[0009] This embodiment will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention applies are not limited to those described below.

[0010] The wireless communication system of this embodiment operates using existing technology. Existing technology is, for example, wireless communication technology based on communication standards such as the 3GPP standard. Existing technology is, for example, NR (New Radio), but is not limited to existing NR. As used herein, the term "NR" has a broad meaning that includes NR (5G) and later systems (e.g., 6G), unless otherwise specified.

[0011] 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 LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. In NR, the above terms will be referred to as SS, PSS, SSS, PBCH, PRACH, etc., without any particular distinction from LTE.

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

[0013] In this embodiment, "configuring" wireless parameters means either pre-configuring predetermined values, or configuring wireless parameters notified by the base station 10 or terminal 20.

[0014] Figure 1 shows an example of the configuration of a 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 terminals 20.

[0015] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time 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. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, PSS and SSS. System information is transmitted, for example, via PBCH and is also called broadcast information. Synchronization signals and system information may be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both base station 10 and terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using Carrier Aggregation (CA). In addition, the terminal 20 may communicate via the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10 using Dual Connectivity (DC).

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

[0017] In the following explanation, " / " means "and / or" unless otherwise specified, or unless the context makes it clear that it has a different meaning.

[0018] At 3GPP, a power-saving technology called "Low-Power Wake Up Signal and Receiver" is being discussed. The Low-Power Wake Up Signal is called LP-WUS or WUS, and the Low-Power Wake Up Receiver is called LP-WUR, WUR, or LR. As an alternative to the Main Radio (MR), which is the circuit used for normal data communication, a simplified circuit called LR operates with lower power consumption than the MR, introducing a state called Ultra-Deep Sleep. The LR may have a function that triggers either the power off of the MR or the power on of the MR when the LR receives an LP-WUS signal.

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

[0020] To specify an LP-WUS design that is common to both RRC IDLE / INACTIVE mode and RRC CONNECTED mode, an OFDM sequence is specified in which an OOK (OOK-1 and / or OOK-4) based LP-WUS is overlaid on OOK symbols, and at least LP-WUS duty cycle monitoring is supported. In the LP-WUS design, the same information must be delivered regardless of the LP-WUS type in IDLE / INACTIVE operation. The OFDM sequence may transmit the information.

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

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

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

[0024] In RRC CONNECTED mode, the procedure for enabling and disabling LP-WUS monitoring, and 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.

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

[0026] Furthermore, 3GPP Rel-19 is considering a procedure for triggering PDCCH monitoring using an LP-WUS in RRC CONNECTED mode. In this procedure, the LP-WUS is, for example, an LP-WUS in a C-DRX (Connected mode Discontinuous Reception) configuration. The following options are being discussed in this procedure:

[0027] In Option 1, as shown in Figure 2, the terminal performs LP-WUS monitoring according to the LP-WUS monitoring configuration before triggering the start of drx-onDurationTimer. Option 1 can be applied to DCP (DCI format 2_6 with CRC scrambled by PS-RNTI) functionality.

[0028] In Option 2, to trigger PDCCH monitoring, the terminal performs LP-WUS monitoring at least outside of the legacy C-DRX active time, according to the LP-WUS monitoring configuration. In Option 2, PDCCH monitoring may be performed regardless of drx-onDurationTimer.

[0029] In Option 2-1, as shown in Figure 3, PDCCH monitoring is additionally triggered during LP-WUS monitoring based on the legacy C-DRX cycle and drx-onDurationTimer. To adopt Option 2-1, it must be configured together with Option 1 to achieve power savings compared to legacy C-DRX.

[0030] In Option 2-2, as shown in Figure 4, PDCCH monitoring is not triggered by the legacy C-DRX cycle and drx-onDurationTimer during LP-WUS monitoring.

[0031] In Option 3, as shown in Figure 5, LP-WUS monitoring is performed at least during the legacy C-DRX active time, according to the LP-WUS monitoring configuration for triggering PDCCH monitoring.

[0032] The above combinations of options need to be considered. Currently, C-DRX-related timers other than drx-onDurationTimer have not been discussed. The above does not preclude the support of a fallback mechanism if one exists that triggers PDCCH monitoring.

[0033] The following points have been agreed upon in 3GPP regarding Option 2 for LP-WUS CONNECTED mode operation:

[0034] - To trigger PDCCH monitoring, perform LP-WUS monitoring at least outside of conventional C-DRX active hours, according to the LP-WUS monitoring settings.

[0035] - UE will be configured as Rel-18 using the conventional C-DRX settings.

[0036] - UE is expected to be configured in the LP-WUS monitoring settings (periodicity and offset may differ from those in the C-DRX settings).

[0037] - Restrictions are placed on LP-WUS settings related to C-DRX settings.

[0038] - LP-WUS triggers the start of a timer that allows the UE to monitor the PDCCH.

[0039] -UE PDCCH monitoring operations related to other conventional DRX timers (drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL) are unaffected.

[0040] - It is assumed that there will be no impact on RRM / RLM / BFD measurement requirements.

[0041] - For periodic CSI / L1-RSRP reporting, if the UE is not instructed to wake up, the periodic CSI / L1-RSRP is not reported, and the periodic CSI / L1-RSRP is reported periodically regardless of whether the UE is instructed to wake up or not.

[0042] - When monitoring LP-WUS, UE PDCCH monitoring is not triggered by the conventional C-DRX cycle and drx-onDurationTimer.

[0043] Further, the following points are being discussed.

[0044] - For Option 1, whether to perform LP-WUS monitoring according to the LP-WUS monitoring setting before the drx-onDurationTimer to trigger the start of the drx-onDurationTimer.

[0045] - For Option 2, whether to perform LP-WUS monitoring at least outside the conventional C-DRX active time according to the LP-WUS monitoring setting to trigger PDCCH monitoring.

[0046] DCP is defined in 3GPP as follows.

[0047] As an exception to DCP monitoring, the UE can be set to monitor DCP only at the opportunity at the configured offset before on-duration when connected mode DRX is configured. Multiple monitoring opportunities can be configured before on-duration. The UE does not monitor DCP when it is monitoring the response to the active time, measurement gap, BWP switching, or CFRA preamble transmission for beam failure recovery. In that case, the UE monitors the PDCCH during the next on-duration. If DCP is not configured for the active BWP, the UE follows the normal DRX operation.

[0048] Regarding DCP, when the UE reports the MinTimeGap or MinTimeGapFR2-2 value, which is the X slot before the start of the slot in which the UE starts the drx-onDurationTimer for the active DL BWP, the UE is not required to monitor the PDCCH to detect DCI format 2_6 during the X slot. Here, X corresponds to the MinTimeGap or MinTimeGapFR2-2 value of the SCS of the active DL BWP in Table 10.3-1.

[0049] Furthermore, the validity / invalidity of the DCP monitoring opportunity is set.

[0050] If the DCP monitoring opportunity conflicts with other procedures that have a higher priority than PDCCH monitoring, the DCP monitoring opportunity is considered invalid. If all the set monitoring opportunities are invalid, the UE follows the conventional operation. If no DCP is detected in the valid monitoring opportunity, whether the UE wakes up is set by RRC.

[0051] ps-WakeUp (Power Saving-WakeUp) is a power-saving function that enables the UE to receive specific DCI even outside the active time of DRX. ps-WakeUp instructs the UE to wake up when DCI format 2-6 is not detected outside the active time. If this field does not exist, the UE does not wake up even if DCI format 2-6 is not detected outside the active time.

[0052] If ps-Wakeup with the value "true" is set and no DCP indication associated with the current DRX cycle has been received from the lower layer, the drx-onDurationTimer is started drx-SlotOffset after the start of the subframe.

[0053] Based on the above, since LP-WUS reception may reuse some of the MR's antenna / RF chain, the above exceptions regarding DCP should also be considered for LP-WUS. However, the period during which LP-WUS monitoring will not be performed is not clearly defined.

[0054] Furthermore, it is unclear what types of other signals / channels or procedures LP-WUS monitoring opportunities overlap (conflict) with, and also how terminals behave during overlapping LP-WUS monitoring opportunities.

[0055] Therefore, according to this embodiment, the method for controlling LP-WUS monitoring when other operations of the terminal are performed during LP-WUS monitoring, or when the LP-WUS monitoring opportunity conflicts with other signals, is clarified, thereby enabling appropriate LP-WUS monitoring and LP-WUS reception.

[0056] In this embodiment, LP-WUS (Low Power Wake-up Signal) is an example of a low-power signal. For example, legacy (conventional) NR signals / channels are an example of signals that do not include low-power signals or signals that are different from low-power signals.

[0057] The terminal in this embodiment may be a terminal in RRC_CONNECTED mode. However, the terminal in this embodiment is not limited to a terminal in RRC_CONNECTED mode. A terminal in RRC_CONNECTED mode may also be referred to as a connected terminal.

[0058] The terminal in this embodiment may be a terminal with C-DRX configured. However, the terminal in this embodiment is not limited to a terminal with C-DRX configured. C-DRX is configured on the terminal based on the C-DRX parameters transmitted from the base station. The terminal operates according to the C-DRX parameters configured from the base station.

[0059] In the following explanation, the notation [A / B / C / D] means at least one of A, B, C, or D, and any combination such as A and B or A, B and C is possible.

[0060] Each embodiment in this embodiment may be performed independently, or any combination of multiple embodiments may be performed.

[0061] (Example 1-1) According to Example 1-1, the period during which terminal 20, which is configured for LP-WUS monitoring, does not monitor LP-WUS is defined according to the operation of terminal 20 and the network.

[0062] LP-WUS monitoring is configured for terminal 20. Terminal 20 receives LP-WUS configuration information from base station 10 and performs LP-WUS monitoring based on the received LP-WUS configuration information. The LP-WUS configuration information includes information indicating the LP-WUS transmission schedule (e.g., LP-WUS transmission period and offset) and LP-WUS monitoring opportunities (LP-WUS opportunities). The LP-WUS configuration information may also be, for example, RRC parameters.

[0063] As shown in Figure 6, terminal 20, which is configured for LP-WUS monitoring, does not monitor LP-WUS during the LP-WUS monitoring exception period when LP-WUS monitoring is available.

[0064] The periods of exception for LP-WUS monitoring may be, for example, one or more combinations of the following 1-1) to 1-7):

[0065] 1-1) Active time of C-DRX operation The C-DRX operation with LP-WUS monitoring may follow any or any possible combination of the above options 1 (Figure 2), 2, 2-1 (Figure 3), 2-2 (Figure 4), or 3 (Figure 5).

[0066] 1-2) C-DRX drx-onDurationTimer The drx-onDurationTimer is one of the C-DRX settings and is a timer that controls the period during which terminal 20 remains in an active state. If C-DRX is set on terminal 20, terminal 20 will remain in an active state for the duration of the drx-onDurationTimer within the DRX cycle, and then transition to a sleep state.

[0067] 1-3) A timer (Option 2 above) on which terminal 20 monitors the PDCCH. 1-4) The duration of the time gap before the start of a slot / symbol on which terminal 20 starts "drx-onDurationTimer" or "Timer on which terminal monitors the PDCCH" (Option 2 above). The time gap may be X [seconds / milliseconds / wireless frame / SFN / subframe / slot / symbol].

[0068] If a higher-level parameter (e.g., LpwusMinTimeGap) is specified, the duration of the time gap must be taken into consideration. Otherwise, the duration of the time gap does not need to be considered.

[0069] The length of the time gap may be set for each terminal and / or for each terminal's BWP, or it may be determined based on at least one of the following: subcarrier interval, terminal wake-up delay, LP-WUS processing time, ramp-up MR transition time, or MR time / frequency synchronization.

[0070] 1-5) Measurement gap period 1-6) Bandwidth Part (BWP) switching period 1-7) Period during which terminal 20 monitors the response to CFRA preamble transmission for beam fault recovery The LP-WUS monitoring exception period may continue for a predetermined offset period after the end of the periods 1)-7) above. That is, the LP-WUS monitoring exception period may be the period 1)-7) above plus a predetermined offset period.

[0071] Thus, according to Example 1-1, it is possible to define a period during which LP-WUS monitoring is not performed, depending on the operation of the terminal 20 and the network.

[0072] (Example 1-2) According to Example 1-2, the operation of terminal 20 during a period when terminal 20 configured for LP-WUS monitoring does not monitor LP-WUS (for example, the period of exception for LP-WUS monitoring in Example 1-1) is defined.

[0073] As shown in Figure 7, during the period when terminal 20 does not monitor LP-WUS (the period of exceptions to LP-WUS monitoring), terminal 20 may monitor PDCCH during the on-duration, drx-onDurationTimer, the timer that terminal 20 monitors PDCCH, or the LP-WUS monitoring period, or any combination of these periods.

[0074] On-duration is the period during which terminal 20 remains active within one DRX cycle when C-DRX is being used.

[0075] For example, in the example of Embodiment 1-1, the start of the LP-WUS monitoring exception period may be triggered by on-duration, drx-onDurationTimer, the timer when terminal 20 monitors the PDCCH, or the start of the LP-WUS monitoring cycle. In Embodiment 1-2, the period during which PDCCH monitoring is performed within the LP-WUS monitoring exception period may be the first on-duration, drx-onDurationTimer, the timer when terminal 20 monitors the PDCCH, or the next timer / cycle of the LP-WUS monitoring cycle that triggers the start of the LP-WUS monitoring exception period.

[0076] As another example of Embodiment 1-2, during the LP-WUS monitoring exception period, the terminal 20 may follow legacy DRX operation or normal DRX operation during the on-duration, drx-onDurationTimer, the timer on which the terminal 20 monitors the PDCCH, or the LP-WUS monitoring period, or any combination of these periods.

[0077] For example, if LP-WUS monitoring is not configured in [Carrier / PCell / SpCell (Special Cell) / SCell / Cell / Active BWP / DRX Group], terminal 20 may follow the normal DRX operation of [Carrier / PCell / SpCell (Special Cell) / SCell / Cell / Active BWP / DRX Group].

[0078] Thus, according to Examples 1-2, the operation of terminal 20 during periods when LP-WUS monitoring is not performed can be defined.

[0079] As described above, according to Example 1, it is possible to clearly define the control of LP-WUS monitoring when other operations are performed on the terminal during LP-WUS monitoring, which was not specified in the conventional 3GPP standard.

[0080] (Example 2) Example 2 clarifies how it is determined whether an LP-WUS monitoring opportunity is valid or invalid, and defines the operation of terminal 20 in an LP-WUS monitoring opportunity that is valid or invalid.

[0081] As shown in Figure 8, in step S11, terminal 20 determines whether the LP-WUS monitoring opportunity is enabled or disabled.

[0082] For example, an LP-WUS monitoring opportunity may be deemed invalid in at least one of the following cases 2-1) to 2-4). Symbols in 2-1) to 2-4) may be replaced with slots, or symbols and slots may be replaced with each other. "Overlap" in 2-1) to 2-4) means that two resources overlap in the time domain, and "overlap" may be referred to as "collision".

[0083] 2-1) If the symbols of the LP-WUS monitoring opportunity completely or partially overlap with the uplink symbols and / or flexible symbols of the TDD. 2-2) If the LP-WUS monitoring opportunity overlaps with other low-power signals, the other low-power signals may be, for example, LP-SS or LP-WUS in IDLE mode, or LP-WUS for a terminal (UE) in other CONNECTED mode.

[0084] 2-3) When an LP-WUS monitoring opportunity overlaps with an MR signal or channel, the MR signal or channel may be at least one of the following, for example: SS, SSB, CSI-RS, CSI-IM, TRS (Tracking Reference Signal), DMRS (Demodulation Reference Signal), PTRS (Phase Tracking Reference Signal), position RS, PDCCH, or PDSCH.

[0085] 2-4) If the LP-WUS monitoring opportunity does not overlap with the rate matching pattern, terminal 20 may determine that the LP-WUS monitoring opportunity is valid if it is not at least one of the above 2-1) to 2-4).

[0086] In step S11, terminal 20 may determine that the LP-WUS monitoring opportunity is invalid if all or some of the LP-WUS monitoring opportunities in the cycle are invalid.

[0087] In step S11 of Figure 8, if it is determined that the LP-WUS monitoring opportunity is valid, in step S12, terminal 20 monitors the LP-WUS during the LP-WUS monitoring opportunity.

[0088] If it is determined in step S11 that the LP-WUS monitoring opportunity is invalid, the terminal performs a predetermined action in step S13.

[0089] The specified actions are, for example, one or more of the following 3-1) to 3-5).

[0090] 3-1) Terminal 20 is assumed to be an LP-WUS indicating the wake-up of PDCCH monitoring. Terminal 20 performs operations based on this assumption.

[0091] 3-2) Terminal 20 monitors PDCCH during the following [on-duration / drx-onDurationTimer / timer for terminal 20 to monitor PDCCH / LP-WUS monitoring period].

[0092] 3-3) Terminal 20 assumes that LP-WUS is not indicating PDCCH monitoring wake-up. Terminal 20 operates based on this assumption.

[0093] 3-4) Terminal 20 follows normal DRX operation and / or legacy DRX operation.

[0094] 3-5) Terminal 20 is configured by upper-layer parameters and / or RRC parameters (e.g., lpwus-WakeUp) to determine whether to wake up for PDCCH monitoring. For example, terminal 20 may wake up for PDCCH monitoring if lpwus-WakeUp is configured or the value of lpwus-WakeUp is "true", and "all LP-WUS monitoring opportunities are invalid", "no LP-WUS has been detected", and / or "no LP-WUS indication associated with the current LP-WUS monitoring opportunity cycle has been received from the lower layer".

[0095] Thus, according to Embodiment 2, it is possible to clearly identify signals / channels or procedures in which LP-WUS monitoring opportunities overlap (collide), and to clearly identify the operation of terminal 20 when overlapping (colliding).

[0096] (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 the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0097] <Base Station> Figure 9 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Figure 9, 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 9 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to this embodiment.

[0098] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. 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, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.

[0099] The setting unit 130 stores pre-set setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to measurements in low-power signals.

[0100] As described in the embodiment, the control unit 140 performs control related to setting, instructing, and notifying about low-power wake-up signals and the like. 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.

[0101] <Terminal> Figure 10 shows an example of the functional configuration of the terminal 20 in this embodiment. As shown in Figure 10, 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 10 is just one example. Any functional classification and name of functional unit is acceptable as long as it can perform the operations according to this embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0102] 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 related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires 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, etc. transmitted from the base station 10. The receiving unit 220 also receives paging notification information, setting information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiving unit 220 receives the low-power wake-up signal 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 related to measurements in low-power signals.

[0103] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying of low-power wake-up signals. 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.

[0104] (Hardware Configuration) The block diagrams (Figures 9 and 10) 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 one device or the multiple devices with software.

[0105] 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. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0106] 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 11 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.

[0107] In the following explanation, the term "device" can be read as "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.

[0108] 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 data reading and writing in the storage device 1002 and auxiliary storage device 1003.

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

[0110] 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 the 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 9 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 10 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 also be transmitted from the network via a telecommunications line.

[0111] 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 the present disclosure.

[0112] 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 disk, a digital multipurpose disk, a Blu-ray® disk), 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.

[0113] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

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

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

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

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

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

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

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

[0121] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service 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. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0122] 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), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0123] 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 the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0124] 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 with 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.

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

[0126] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0127] (Configuration relating to this embodiment) (Section 1) A terminal comprising: a control unit that monitors a low-power wake-up signal on a monitoring occasion; and a receiving unit that receives the monitored low-power wake-up signal, wherein the control unit does not monitor the low-power wake-up signal for a predetermined period of time.

[0128] (Clause 2) The terminal as described in paragraph 1, wherein the predetermined period is at least one of the following: the active time of the C-DRX (Connected mode Discontinuous Reception), the period indicated by the drx-onDurationTimer, the period of the timer by which the terminal monitors the PDCCH (Physical Downlink Control Channel), the time gap period before the start of the slot or symbol by which the terminal starts the drx-onDurationTimer or the timer by which the terminal monitors the PDCCH, the measurement gap period, the Bandwidth Part (BWP) switching period, or the period by which the terminal monitors the response to the transmission of the CFRA (Contention Free Random Access) preamble for beam fault recovery.

[0129] (Clause 3) The terminal as described in paragraph 1, wherein the control unit monitors the PDCCH during at least one of the following periods within the predetermined period: on-duration, drx-onDurationTimer, timer during which the terminal 20 monitors the PDCCH, or LP-WUS monitoring period.

[0130] (Clause 4) The terminal according to paragraph 1, wherein the control unit determines that the monitoring opportunity is invalid in at least one of the following cases: when the monitoring opportunity overlaps with an uplink symbol or flexible symbol of a TDD (Time Division Duplex); when the monitoring opportunity collides with a low-power signal different from the low-power wake-up signal; when the monitoring opportunity collides with a signal or channel of MR (Main Radio); or when the monitoring opportunity collides with a rate matching pattern.

[0131] (Clause 5) When the control unit determines that the monitoring opportunity is invalid, it assumes that the low-power wake-up signal indicates a wake-up for PDCCH monitoring, or monitors PDCCH during the on-duration, drx-onDurationTimer, timer during which the terminal monitors PDCCH, or LP-WUS monitoring cycle, as described in Clause 4.

[0132] (Clause 6) A communication method performed by a terminal, comprising: a control unit that monitors a low-power wake-up signal on a monitoring occasion; and a receiving unit that receives the monitored low-power wake-up signal, wherein the control unit does not monitor the low-power wake-up signal for a predetermined period of time.

[0133] Any of the above configurations can clarify the periods during which LP-WUS monitoring is not performed and the behavior of the terminal during those periods. According to paragraphs 1-2 and 6 above, the periods of exceptions during which LP-WUS monitoring is not performed can be defined depending on the behavior of the terminal and the network. According to paragraph 3 above, the behavior of the terminal during the periods of exceptions during which LP-WUS monitoring is not performed can be clarified. According to paragraphs 4-5 above, the signals / channels or procedures in which LP-WUS monitoring opportunities overlap (collide) can be clarified, and the behavior of the terminal during overlap (collision) can be clarified.

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

[0135] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, 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.

[0136] Each aspect / embodiment described in this disclosure may be applied to at least one of systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

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

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

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

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

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

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

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

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

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

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

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

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

[0149] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "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.

[0150] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple 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.

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

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

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

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

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

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

[0157] 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, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or 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."

[0158] The terms “connected,” “coupled,” and any variations 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.

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

[0160] 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."

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

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

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

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

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

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

[0167] 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 a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

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

[0169] 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 minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), 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, minislot, etc., instead of a subframe.

[0170] Here, TTI refers to, for example, the smallest time unit 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.

[0171] 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. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

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

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

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

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

[0176] 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. One TTI, one subframe, etc., may each consist of one or more resource blocks.

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

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

[0179] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a particular neurology 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. The PRBs may be defined and numbered within a given BWP.

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

[0181] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit 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".

[0182] 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 the TTI can be varied in various ways.

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

[0184] 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."

[0185] Each aspect / embodiment described in this disclosure 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).

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

[0187] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a control unit that monitors a low-power wake-up signal during a monitoring opportunity; and a receiving unit that receives the monitored low-power wake-up signal, wherein the control unit does not monitor the low-power wake-up signal for a predetermined period of time.

2. The terminal according to claim 1, wherein the predetermined period is at least one of the following: the active time of C-DRX (Connected mode Discontinuous Reception), the period indicated by drx-onDurationTimer, the period of the timer by which the terminal monitors PDCCH (Physical Downlink Control Channel), the time gap period before the start of a slot or symbol by which the terminal starts drx-onDurationTimer or the timer by which the terminal monitors PDCCH, the measurement gap period, the Bandwidth Part (BWP) switching period, or the period by which the terminal monitors the response to the transmission of a Contention Free Random Access (CFRA) preamble for beam fault recovery.

3. The terminal according to claim 1, wherein the control unit monitors the PDCCH during at least one of the following periods within the predetermined period: on-duration, drx-onDurationTimer, timer for the terminal 20 to monitor the PDCCH, or LP-WUS monitoring period.

4. The terminal according to claim 1, wherein the control unit determines that the monitoring opportunity is invalid in at least one of the following cases: when the monitoring opportunity overlaps with an uplink symbol or flexible symbol of a TDD (Time Division Duplex); when the monitoring opportunity collides with a low-power signal different from the low-power wake-up signal; when the monitoring opportunity collides with a signal or channel of MR (Main Radio); or when the monitoring opportunity collides with a rate matching pattern.

5. The terminal according to claim 4, wherein when the control unit determines that the monitoring opportunity is invalid, it assumes that the low-power wake-up signal indicates a wake-up for PDCCH monitoring, or monitors PDCCH during the on-duration, drx-onDurationTimer, timer during which the terminal monitors PDCCH, or LP-WUS monitoring cycle.

6. A communication method performed by a terminal, comprising: a control unit that monitors a low-power wake-up signal on a monitoring occasion; and a receiving unit that receives the monitored low-power wake-up signal, wherein the control unit does not monitor the low-power wake-up signal for a predetermined period of time.

Images