Terminal and communication method
The terminal's control unit and receiving unit clarify LP-WUS operation in CA/DC scenarios, addressing undefined configurations and associations, enabling efficient PDCCH monitoring and power optimization in wireless communication systems.
Patent Information
- Application Number
- PCT/JP2024/028596
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-08
- Publication Date
- 2026-02-12
AI Technical Summary
The operation of Low-Power Wake-Up Signal (LP-WUS) in Carrier Aggregation (CA)/Dual Connectivity (DC) for RRC_CONNECTED UEs in wireless communication systems is not clearly defined, leading to potential improper performance of LP-WUS in systems with CA/DC application.
The terminal includes a control unit for setting up LP-WUS monitoring from a base station in a connected state across multiple cells, and a receiving unit to receive the LP-WUS in specific cells, clarifying the LP-WUS design in CA/DC scenarios, including configurations for BWPs, CCs, and associations with serving cells and DRX groups.
Enables appropriate operation of LP-WUS in CA/DC environments, optimizing power consumption and ensuring efficient PDCCH monitoring by defining LP-WUS configurations and associations with serving cells and DRX groups.
Smart Images

Figure JP2024028596_12022026_PF_FP_ABST
Abstract
Description
Terminal and communication method
[0001] The present invention relates to a terminal and a communication method in a wireless communication system.
[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is studying technologies for achieving further increases in system capacity, further increases in data transmission speed, and further reductions in latency in wireless sections (e.g., Non-Patent Documents 1 and 2). Furthermore, 3GPP Rel-19 is discussing low-power wake-up signal (LP (Low Power)-WUS (Wake Up Signal) / LP-WUR (Wake Up Receiver)) technology for reducing power consumption in wireless communication systems.
[0003] Here, in 3GPP Release 19 (R19), a procedure for triggering PDCCH (Physical Downlink Control Channel) monitoring using LP-WUS in RRC (Radio Resource Control)_CONNECTED mode is being considered.
[0004] 3GPP TS 38.300 V18.2.0(2024-06)3GPP TS 38.401 V18.2.0(2024-06)
[0005] However, in the past, the operation of LP-WUS in Carrier Aggregation (CA) / Dual Connectivity (DC) for RRC_CONNECTED UE has not been clarified, so there is a risk that the operation of LP-WUS cannot be properly performed in a wireless communication system to which CA / DC is applied.
[0006] The terminal in this embodiment includes a control unit that sets up monitoring of a low power wake-up signal from a base station for the terminal in a connected state that communicates using multiple cells, and a receiving unit that receives the low power wake-up signal in a specific cell among the multiple cells that is used to transmit the low power wake-up signal.
[0007] According to this embodiment, a terminal that communicates using a plurality of cells can appropriately perform operations related to low-power signals.
[0008] 1 is a diagram for explaining a wireless communication system in this embodiment. FIG. 1 is a diagram illustrating an example of a configuration of a wireless communication system in this embodiment. FIG. 2 is a diagram illustrating an example of a procedure in which an LP-WUS triggers PDCCH monitoring. FIG. 3 is a diagram illustrating an example of a procedure in which an LP-WUS triggers PDCCH monitoring. FIG. 4 is a diagram illustrating an example of a procedure in which an LP-WUS triggers PDCCH monitoring. FIG. 5 is a diagram illustrating an example of an operation of a terminal in Example 1. FIG. 6 is a diagram illustrating an example of an operation of a terminal in Example 2. FIG. 7 is a diagram illustrating an example of a method in which an LP-WUS triggers PDCCH monitoring in Example 2. FIG. 8 is a diagram illustrating an example of a method in which an LP-WUS triggers PDCCH monitoring in Example 2. FIG. 9 is a diagram illustrating an example of a method in which an LP-WUS triggers PDCCH monitoring in Example 2. FIG. 10 is a diagram illustrating an example of a method in which an LP-WUS triggers PDCCH monitoring in Example 2. FIG. 11 is a diagram illustrating an example of a method in which an LP-WUS triggers PDCCH monitoring in Example 2. FIG. 12 is a diagram illustrating an example of an operation of a terminal in Example 3. FIG. 13 is a diagram illustrating an example of a description in a standard of the operation of LP-WUS monitoring in Example 3. FIG. 14 is a diagram illustrating an example of the functional configuration of a base station in this embodiment. FIG. 15 is a diagram illustrating an example of the functional configuration of a terminal in this embodiment. 1 is a diagram illustrating an example of a hardware configuration of a base station or a terminal according to the present embodiment.
[0009] The present embodiment will be described below with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0010] In the operation of the wireless communication system of this embodiment, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems after LTE-Advanced (e.g., NR), unless otherwise specified.
[0011] In the present embodiment 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) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned terms in NR are referred to as SS, PSS, SSS, PBCH, PRACH, etc. without any particular distinction from LTE.
[0012] In addition, in this embodiment, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).
[0013] Furthermore, in this embodiment, "configuring" radio parameters etc. may mean that predetermined values are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.
[0014] Fig. 1 is a diagram showing an example of the configuration of a wireless communication system according to this embodiment. As shown in Fig. 1, the wireless communication system according to this embodiment includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.
[0015] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. Physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal may be, for example, a PSS or an SSS. The system information is transmitted, for example, via the PBCH and is also referred to as broadcast information. The synchronization signal and system information may also be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in a downlink (DL) and receives control signals or data from the terminal 20 in an uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).
[0016] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module. As shown in Fig. 1, the 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. The terminal 20 also receives various reference signals transmitted from the base station 10 and measures propagation path quality based on the reception results of the reference signals.
[0017] FIG. 2 is a diagram showing an example of the configuration of a wireless communication system according to this embodiment.
[0018] As shown in FIG. 2, the terminal 20 communicates with a base station 10A provided by the NR system and a base station 10B provided by the NR system (hereinafter, when the base stations 10A and 10B are not distinguished, they may be referred to as "base station 10"). Furthermore, the terminal 20 supports NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is the master node (hereinafter also referred to as "MN") and the base station 10B is the secondary node (hereinafter also referred to as "SN"). The terminal 20 can simultaneously use multiple component carriers provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.
[0019] As shown in FIG. 2, the terminal 20 may communicate with a base station 10A provided by the LTE system and a base station 10B provided by the NR system. Furthermore, the terminal 20 may support LTE-NR dual connectivity, i.e., EN-DC, in which the base station 10A is the MN and the base station 10B is the SN. The terminal 20 can simultaneously use multiple component carriers provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.
[0020] As shown in FIG. 2, the terminal 20 may communicate with a base station 10A provided by the NR system and a base station 10B provided by the LTE system. Furthermore, the terminal 20 may support NR-LTE dual connectivity, i.e., NE-DC (NR-E-UTRA Dual Connectivity), in which the base station 10A is the MN and the base station 10B is the SN. The terminal 20 can simultaneously use multiple component carriers provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.
[0021] As shown in FIG. 2, the terminal 20 may communicate with a base station 10A provided by the NR system and a base station 10B provided by the NR system. Furthermore, the terminal 20 may support NR-NR dual connectivity, i.e., NR-DC, in which the base station 10A is the MN and the base station 10B is the SN. The terminal 20 can simultaneously use multiple component carriers provided by the base station 10A, which is the master node, and the base station 10B, which is the secondary node, to perform simultaneous transmission or reception with the base station 10A, which is the master node, and the base station 10B, which is the secondary node.
[0022] The terminal 20 in this embodiment may perform communication using one serving cell, or may perform communication using multiple serving cells (for example, CA or DC).
[0023] A C-DRX configuration in CA in this embodiment will be described. A maximum of two DRX groups may be configured for the serving cell of one terminal 20. Note that the maximum number of DRX groups is not limited to two and may be any number.
[0024] In CA scenarios, DCP (DCI format 2_6 with CRC scrambled by PS-RNTI) is configured only on the PCell. The serving cell of the MAC entity is configured by RRC into two DRX groups, each with separate DRX parameters (e.g., one DRX group for FR1 and another DRX group for FR2).
[0025] If RRC does not configure a secondary DRX group, there is only one DRX group and all serving cells belong to that one DRX group. If two DRX groups are configured, each serving cell is uniquely assigned to one of the two groups.
[0026] The DRX parameters that are individually set for each DRX group are, for example, drx-onDurationTimer and drx-InactivityTimer.
[0027] The DRX parameters that are common to all DRX groups are drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-NonIntegerLongCycleStartOffset, drx-ShortCycle (optional), drx-NonIntegerShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.
[0028] In the following description, unless otherwise specified or unless a different meaning is clear from the context, " / " means "and / or."
[0029] In 3GPP (registered trademark), a power consumption reduction 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. A state called Ultra-Deep Sleep is introduced by operating the LR, a simplified circuit that operates with lower power consumption than the Main Radio (MR), which is a circuit used for normal data communication. The LR may have a function that triggers the power OFF of the MR or triggers the power ON of the MR when the LR receives an LP-WUS signal.
[0030] The agreement on the scope of application of LP-WUS / WUR in 3GPP Rel-19 is shown below.
[0031] To specify a LP-WUS design that is commonly applicable to both RRC IDLE / INACTIVE and RRC CONNECTED modes, an OFDM sequence overlaid on OOK symbols (OOK-1 and / or OOK-4) based LP-WUS is specified, supporting at least LP-WUS duty cycle monitoring. The LP-WUS design must ensure that the same information is delivered in IDLE / INACTIVE operation regardless of the LP-WUS type. The OFDM sequence may carry information.
[0032] In case of RRC IDLE / INACTIVE mode: - Specify the LP-WUS procedures and configurations to indicate paging monitoring triggered by the LP-WUS, including at least the configuration, subgrouping and entry / exit conditions for LP-WUS monitoring.
[0033] - For synchronization and / or serving cell RRM, the LP-WUR is assigned an LP-SS with a periodicity of Y [ms]. 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.
[0034] -Specify, including the necessary conditions, further relaxing the RRM of the terminal 20 MR with measurements of both the serving cell and the neighbor cell and offloading the RRM measurement of the terminal 20 serving cell from the MR to the LP-WUR.
[0035] In RRC CONNECTED mode, it specifies the procedure to enable UE MR PDCCH monitoring triggered by LP-WUS, including the procedure to enable and disable LP-WUS monitoring. In CONNECTED mode, UE MR ultra-deep sleep is not considered, and UE RRM / RLM / BFD / CSI measurements are performed by MR.
[0036] The target coverage of LP-WUS and LP-SS is the PUSCH coverage of message 3. Optimization of LP-WUS signal design for idle / inactive mode takes priority over optimization for connected mode.
[0037] Furthermore, 3GPP Rel-19 is considering a procedure for triggering PDCCH monitoring by LP-WUS in RRC CONNECTED mode. The LP-WUS in this procedure is, for example, an LP-WUS configured in C-DRX (Connected mode Discontinuous Reception). In this procedure, the following options are discussed:
[0038] In option 1, the terminal performs LP-WUS monitoring according to the LP-WUS monitoring configuration before triggering the start of the drx-onDurationTimer, as shown in Figure 3. Option 1 may be applied to the DCP (DCI format 2_6 with CRC scrambled by PS-RNTI) function.
[0039] In option 2, to trigger PDCCH monitoring, the terminal performs LP-WUS monitoring at least outside 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.
[0040] In Option 2-1, PDCCH monitoring is additionally triggered during LP-WUS monitoring based on the legacy C-DRX cycle and drx-onDurationTimer, as shown in Figure 4. To adopt Option 2-1, it must be configured together with Option 1 to achieve power savings compared to legacy C-DRX.
[0041] In option 2-2, as shown in FIG. 5, PDCCH monitoring is not triggered by the legacy C-DRX cycle and drx-onDurationTimer during LP-WUS monitoring.
[0042] In option 3, LP-WUS monitoring at least within the legacy C-DRX active time is performed according to the LP-WUS monitoring configuration for triggering PDCCH monitoring, as shown in FIG. 6 .
[0043] Combinations of the above options should be considered. Currently, no C-DRX related timers other than drx-onDurationTimer are discussed. The above does not preclude the support of fallback mechanisms that trigger PDCCH monitoring, if any.
[0044] For Option 1, the timing of LP-WUS monitoring is at a configured time offset before the start of drx-onDurationTimer. For Option 1, it may be assumed that the solutions / operations introduced in the DCP mechanism are used as a baseline. It may be assumed that legacy DCP and Option 1 are not configured for the terminal at the same time. LP-WUS related configuration in the RRC CONNECTED state is provided via a dedicated RRC message.
[0045] Furthermore, in R19 it has been agreed to apply the following options to LP-WUS information for triggering PDCCH monitoring in RRC_CONNECTED UE:
[0046] Option A: A bitmap where each bit corresponds to one or more UEs Option B: A codepoint value corresponding to one or part of a UE ID (e.g. C-RNTI) Option C: A codepoint value corresponding to one or more UEs Option D: A number of codepoint values each corresponding to one or more UEs Option E: A number of bit blocks each corresponding to one or more UEs Combinations of the above options are not excluded.
[0047] However, conventionally, the operation related to LP-WUS in CA / DC for RRC_CONNECTED UE has not been clarified. For example, regarding the configuration of LP-WUS in CA / DC, one or more BWPs or CCs capable of transmitting LP-WUS, a serving cell that monitors the LP-WUS, and a BWP that monitors the LP-WUS have not been clarified. Furthermore, the operation of LP-WUS monitoring taking into account multiple cells and multiple DRX groups and how the LP-WUS and the serving cell should be associated have not been clarified. Therefore, there is a risk that the operation related to LP-WUS in CA / DC cannot be performed appropriately.
[0048] According to this embodiment, the operation relating to the LP-WUS in the CA / DC, which has not been defined in the past, is clarified, and the operation relating to the LP-WUS in the CA / DC can be executed appropriately. This embodiment will be described below.
[0049] In this embodiment, the LP-WUS (low power wake-up signal) is an example of a low power signal. For example, a legacy (conventional) NR signal / channel is an example of a signal that does not include a low power signal or a signal that is different from a low power signal.
[0050] 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 terminal in a connected state.
[0051] The terminal in this embodiment may be a terminal in which C-DRX is configured. However, the terminal in this embodiment is not limited to a terminal in which C-DRX is configured. C-DRX is configured in the terminal based on C-DRX parameters transmitted from the base station. The terminal operates in accordance with the C-DRX parameters configured by the base station.
[0052] In the following description, the notation [A / B / C / D] means at least one of A, B, C, or D, and means that any combination such as A and B or A, B and C is possible.
[0053] The examples in this embodiment may be implemented independently of each other, or any combination of a plurality of examples may be implemented.
[0054] In this embodiment, when "X" (e.g., function or information) is configured in a terminal (or a base station), it indicates that the terminal is configured with "X".
[0055] In this embodiment, the various pieces of information set in the terminal may be included in parameters (e.g., upper layer (RRC) parameters) transmitted from the base station. The terminal may set the various pieces of information in the terminal based on the parameters transmitted from the base station. As another example, the various pieces of information may be set in the terminal in advance based on a standard (e.g., technical specifications of the 3GPP standard) for the terminal.
[0056] (First Embodiment) Conventionally, with regard to the configuration of an LP-WUS in CA / DC, it has not been clarified how to configure one or more BWPs or CCs capable of transmitting an LP-WUS, a serving cell that monitors the LP-WUS, and a BWP that monitors the LP-WUS. According to the first embodiment, the LP-WUS design in CA / DC, which has not been specified in the past, is clarified.
[0057] 7, when LP-WUS monitoring is set in the terminal 20 in the CONNECTED mode (step S101) and multiple serving cells are set for the terminal 20 (step S102), the terminal 20 receives (or monitors) the LP-WUS transmitted from a predetermined cell or in a predetermined BWP from the base station 10 (step S103). The configuration in which multiple serving cells are set for the terminal 20 is a CA or DC configuration.
[0058] (Example 1-1) According to Example 1-1, in a cell configured to transmit LP-WUS, one or more of the following Alt.1-1 to Alt.1-3 may be applied.
[0059] Alt.1-1: The LP-WUS may be transmitted only in the PCell, PSCell, SCell, or SpCell. For example, when a transmission cell for the LP-WUS is configured for the terminal 20, the terminal 20 may monitor only the LP-WUS transmitted within the bandwidth of [PCell / PSCell / SCell / SpCell] or [PCell / PSCell / SCell / SpCell].
[0060] Alt.1-2: LP-WUS may be transmitted in [PCell / PSCell / SCell / SpCell].
[0061] Alt.1-3: LP-WUS may be transmitted in a [cell / band] specific to the LP-WUS.
[0062] The LP-WUS specific cell is not, for example, a PCell, SpCell or activated SCell of the terminal 20.
[0063] The terminal 20 may monitor the LP-WUS in the cell / band.
[0064] (Embodiment 1-2) According to embodiment 1-2, in a BWP configured to transmit an LP-WUS, one or more of Alt.2-1 to Alt.2-3 may be applied.
[0065] Alt. 2-1: LP-WUS is transmitted only in the initial DL BWP, the default DL BWP, or other activated DL BWP. The default DL BWP is configured in the terminal 20 by an RRC transmitted from the base station 10. The LP-WUS-specific DL BWP is configured to include the LP-WUS transmission.
[0066] Alt.2-2: LP-WUS may be sent in [initial DL BWP / default DL BWP / other activated DL BWP].
[0067] Alt. 2-3: The LP-WUS may be transmitted in a LP-WUS specific DL [Bandwidth / BWP]. The LP-WUS specific DL BWP may be one of the DL BWPs configured for the terminal 20, whether activated or not.
[0068] (Embodiment 1-3) According to embodiment 1-3, the number of LP-WUSs monitored by the terminal 20 may be one or more of Alt.3-1 to Alt.3-4.
[0069] Alternative 3-1: The terminal 20 monitors the LP-WUS at one or more timings within the bandwidth and BWP. Alternative 3-1 may be applied to the above-mentioned embodiment 1-2.
[0070] Alternative 3-2: The terminal 20 may monitor the LP-WUS in a part or multiple parts of the bandwidth within the BWP. Alternative 3-2 may be applied to the above-mentioned embodiment 1-2.
[0071] Alternative 3-3: The terminal 20 may monitor the LP-WUS in one or more BWPs of the serving cell. Alternative 3-3 may be applied to the above-mentioned embodiment 1-1.
[0072] Alt. 3-4: When the terminal 20 is configured with multiple serving cells, the terminal 20 may monitor the LP-WUS in one or more serving cells.
[0073] The serving cell may be an intra-band CA, an inter-band CA, or an inter-FR CA / DC cell.
[0074] When the terminal 20 monitors the LP-WUS in one serving cell, the monitoring cell may be a PCell.
[0075] When the terminal 20 monitors the LP-WUS in multiple serving cells, one of the monitored cells may be a PCell, and the other monitored cells may be serving cells of the [same / different] [band / FR / DRX group] compared to the PCell.
[0076] (Example 1-4) According to Example 1-4, one or more of the following Alt. 4-1 to Alt. 4-6 may be applied to LP-WUS monitoring.
[0077] Alt. 4-1: LP-WUS monitoring and secondary DRX group in [idle / inactive / connected] mode cannot be jointly (simultaneously) supported / configured for one terminal 20.
[0078] Alt. 4-2: LP-WUS monitoring and secondary DRX group in [idle / inactive / connected] mode may be jointly (simultaneously) supported / configured for one terminal 20.
[0079] Alt. 4-3: LP-WUS monitoring and DCI format 2_6 monitoring in [idle / inactive / connected] mode cannot be jointly (simultaneously) supported / configured for one terminal 20.
[0080] For example, terminal 20 is not expected to monitor LP-WUS and DCI format 2_6 transmitted in the same [cell / BWP]. In terminal 20, it is not permitted that LP-WUS is transmitted from cell #1 and DCI format 2_6 is transmitted from cell #1.
[0081] Terminal 20 does not assume that LP-WUS and DCI format 2_6 are configured to trigger PDCCH monitoring in the same [cell / BWP]. In terminal 20, LP-WUS is not allowed to trigger PDCCH monitoring in cell #1, and DCI format 2_6 is not allowed to trigger PDCCH monitoring in cell #1.
[0082] Alt. 4-4: LP-WUS monitoring and DCI format 2_6 monitoring in [idle / inactive / connected] mode may be jointly (simultaneously) supported / configured for one terminal 20.
[0083] For example, the terminal 20 may monitor LP-WUS and DCI format 2_6 transmitted in the same or different [cell / BWP].
[0084] For example, the terminal 20 may assume that the LP-WUS and DCI format 2_6 are configured to trigger PDCCH monitoring in the same or different [cell / BWP].
[0085] Alt. 4-5: LP-WUS monitoring and C-DRX in [idle / inactive / connected] mode must be configured jointly (simultaneously) for one terminal 20.
[0086] For example, the terminal 20 does not assume that LP-WUS monitoring in the CONNECTED mode is set for the terminal 20, but C-DRX is not set.
[0087] For example, when LP-WUS monitoring is set for the terminal 20 in the CONNECTED mode, the terminal 20 assumes that C-DRX is set for the terminal 20.
[0088] Alt. 4-6: LP-WUS monitoring and C-DRX in [idle / inactive / connected] mode may be configured individually for one terminal 20.
[0089] In this way, according to the first embodiment, the LP-WUS design in CA / DC, which has not been defined in the past, is clarified. Furthermore, according to the first embodiment, regarding the setting of the LP-WUS in CA / DC, one or more BWPs or CCs capable of transmitting the LP-WUS, a serving cell that monitors the LP-WUS, and a BWP that monitors the LP-WUS are defined.
[0090] (Embodiment 2) Conventionally, it is not clear how LP-WUS monitoring should be performed considering multiple cells and multiple DRX groups, and how the LP-WUS should be associated with the serving cell.
[0091] According to the second embodiment, an association between an LP-WUS and a serving cell of a CA / DC, which has not been defined conventionally, is defined. According to the second embodiment, as shown in Fig. 8, when LP-WUS monitoring is configured in the terminal 20 in the CONNECTED mode (step S201) and multiple serving cells are configured for the terminal 20 (step S202), the terminal 20 assumes a predetermined operation based on whether DRX / secondary DRX is configured for the terminal 20 (step S203). The terminal 20 operates based on the assumed predetermined operation. An example of the predetermined operation based on whether DRX / secondary DRX is configured in step S203 is shown below.
[0092] When LP-WUS monitoring is configured for the terminal 20 in CONNECTED mode and multiple serving cells are configured, at least one of Alt.1-1 to Alt.1-4 below may be applied.
[0093] Alt.1-1: The terminal 20 may assume that DRX is configured in the terminal 20.
[0094] Alt. 1-2: The terminal 20 may assume that DRX is configured or that DRX is not configured in the terminal 20.
[0095] Alt. 1-3: When CRX is configured, the terminal 20 may assume that [one DRX group is configured / no secondary DRX group is configured] for the terminal 20.
[0096] Alt.1-4: If DRX is configured, a secondary DRX group may be configured in the terminal 20.
[0097] When LP-WUS monitoring in CONNECTED mode is configured in the terminal 20 and multiple serving cells are configured in the terminal 20, at least one of the following (1) to (4) may be applied.
[0098] (1) If DRX is not configured in the terminal 20, one or more of the following Alt. 2-1 to Alt. 2-3 may be applied.
[0099] Alt. 2-1: One LP-WUS configured in the terminal 20 may trigger PDCCH monitoring of one serving cell.
[0100] Alt. 2-2: One LP-WUS configured in the terminal 20 may trigger PDCCH monitoring of multiple serving cells.
[0101] In Alt. 2-1 and 2-2, one or more LP-WUS may be set for the terminal 20 as in the first embodiment.
[0102] Alt. 2-3: One LP-WUS configured in the terminal 20 may trigger PDCCH monitoring of all serving cells.
[0103] (2) If DRX is configured in the terminal 20 but secondary DRX is not configured, Alt. 2-4 may be applied.
[0104] Alternative 2-4: One LP-WUS configured in the terminal 20 may trigger PDCCH monitoring in all serving cells of a DRX group. As shown in Fig. 9, one LP-WUS transmitted in cell #1 (PCell) triggers PDCCH monitoring in all serving cells (cells #1-#3) included in one DRX group.
[0105] (3) When secondary DRX is configured in the terminal 20, one or more of the following Alt. 2-5 and Alt. 2-6 may be applied.
[0106] Alt.2-5: As shown in Fig. 10-12, one LP-WUS configured in the terminal 20 may trigger PDCCH monitoring of all serving cells of one DRX group. In Fig. 10-12, the periods indicated by the drx-onDurationTimer for each of the multiple DRX groups (DRX groups #1, #2) are different. However, the periods indicated by the drx-onDurationTimer for each of the multiple DRX groups may be the same.
[0107] Figure 10 shows an example in which multiple LP-WUSs transmitted in the same serving cell each trigger PDCCH monitoring of serving cells included in each DRX group. In the example of Figure 10, LP-WUS #1 transmitted in cell #1 triggers PDCCH monitoring in cells #1 and #2 included in DRX group #1. LP-WUS #2 transmitted in cell #1 triggers PDCCH monitoring in cell #3 included in DRX group #2.
[0108] Figure 11 shows an example in which one LP-WUS transmitted in one serving cell triggers PDCCH monitoring of serving cells in two different DRX groups. In the example of Figure 11, one LP-WUS triggers PDCCH monitoring in cells #1 and #2 in DRX group #1, and PDCCH monitoring in cell #3 in DRX group #2.
[0109] Fig. 12 shows an example in which an LP-WUS transmitted in each of multiple serving cells triggers PDCCH monitoring of the serving cells included in each DRX group. In the example of Fig. 12, an LP-WUS #1 transmitted in cell #1 triggers PDCCH monitoring in cells #1 and #2 included in DRX group #1. An LP-WUS #2 transmitted in cell #3 triggers PDCCH monitoring in cell #3 included in DRX group #2.
[0110] In Alt. 2-5, two LP-WUSs may be configured in the terminal 20. Each LP-WUS may be associated with one DRX group on a one-to-one basis.
[0111] In Alt. 2-5, the terminal 20 does not need to assume that one LP-WUS is associated with one DRX group and that no LP-WUS is associated with other DRX groups.
[0112] Alt. 2-6: As shown in Fig. 13, one LP-WUS configured in the terminal 20 may trigger PDCCH monitoring of all serving cells of two DRX groups. One LP-WUS may be configured as in Example 1 and associated one-to-one.
[0113] Fig. 13 shows an example in which one LP-WUS triggers PDCCH monitoring of serving cells included in all of multiple DRX groups. In Fig. 13, the periods indicated by the drx-onDurationTimer for each of the multiple DRX groups (DRX groups #1 and #2) are different. However, the periods indicated by the drx-onDurationTimer for each of the multiple DRX groups may be the same.
[0114] In the example of FIG. 13, an LP-WUS transmitted in cell #1 triggers PDCCH monitoring in cells #1 and #2 included in DRX group #1 and cell #3 included in DRX group #2.
[0115] (4) In the above (1)-(3) (including each Alt.), if the LP-WUS detected by the terminal 20 indicates wake-up / PDCCH monitoring, the terminal 20 may turn on the MR (Main Radio) (main radio) (turn on / wake-up / exit sleep mode) and monitor the PDCCH of the serving cell associated with the LP-WUS. In other cases, the terminal 20 may not monitor the PDCCH of the serving cell associated with the LP-WUS.
[0116] Third Embodiment According to a third embodiment, the operation of a terminal for LP-WUS and PDCCH monitoring in CA / DC is defined.
[0117] (Example 3-1) According to Example 3-1, the terminal 20 does not assume that it will detect multiple LP-WUSs with different wake-up instructions to the terminal 20 during the LP-WUS monitoring opportunities associated with the following Alt.1-1 or Alt.1-2.
[0118] Alt.1-1: LP-WUS monitoring occasions may be associated with the same DRX cycle. For example, this association may be applied to the PDCCH monitoring trigger procedure shown in Figures 3-5. The DRX cycle may be a long DRX cycle or a short DRX cycle.
[0119] Alternative 1-2: LP-WUS monitoring occasions may be associated with the same duty cycle. For example, this association may apply to the PDCCH monitoring trigger procedure shown in Figure 6. Within a DRX cycle, e.g., within a legacy C-DRX active time, there may be multiple duty cycles for LP-WUS monitoring.
[0120] (Example 3-2) According to Example 3-2, in LP-WUS monitoring during the active time of DRX, the following Alt.2-1 to Alt.2-3 may be applied.
[0121] Alt.2-1: If DRX is configured in the terminal 20 but secondary DRX is not configured and one LP-WUS triggers PDCCH monitoring of all serving cells in the DRX group (for example, when Alt.2-4 of Example 2 is applied), the terminal 20 does not perform LP-WUS monitoring during the active time of DRX.
[0122] Alt. 2-2: If secondary DRX is configured in terminal 20 and one LP-WUS triggers PDCCH monitoring of all serving cells of two DRX groups (e.g., when Alt. 2-6 of Example 2 is applied), terminal 20 does not perform LP-WUS monitoring during the active time of either DRX group.
[0123] Alt.2-3: If secondary DRX is configured in terminal 20 and one LP-WUS triggers PDCCH monitoring of all serving cells of one DRX group (e.g., when Alt.2-5 of Example 2 applies), terminal 20 does not perform LP-WUS monitoring during the active time of the associated DRX group.
[0124] (Embodiment 3-3) According to embodiment 3-3, an operation when the terminal 20 does not have an LP-WUS monitoring opportunity is defined.
[0125] If LP-WUS monitoring is configured in the terminal 20 and there is no LP-WUS monitoring opportunity in the terminal 20 [outside the active time of the next DRX cycle / before the drx-onDurationTimer of the next DRX cycle / before the next duty cycle within the DRX cycle shown in Alt.1-2 of Example 3-1], the terminal 20 may perform one or more of the operations Alt.3-1 to Alt.3-4.
[0126] Alt. 3-1: As shown in FIG. 14, the terminal 20 follows the actions when it receives an indication to wake up the PDCCH monitoring of the associated DRX cycle.
[0127] Alt.3-2: The terminal 20 follows the behavior when it does not receive an indication to wake up the PDCCH monitoring for the associated DRX cycle.
[0128] Alt.3-3: The terminal 20 turns on MR [on / wakes up / exits sleep mode] and monitors the PDCCH of the serving cell associated with the LP-WUS of the associated DRX cycle.
[0129] Alt. 3-4: The terminal 20 does not monitor the PDCCH of the serving cell associated with the LP-WUS of the associated DRX cycle.
[0130] 15 shows examples of descriptions of Alt.1-1, Alt.2-1, and Alt.3-1 of the above-described third embodiment in a standard (e.g., a 3GPP technical specification). For example, the 3GPP technical specification may be TS 38.213. [CR example of Alt.1-1] In the case of LP-WUS monitoring associated with the same long DRX cycle, it is not assumed that the terminal 20 will detect multiple LP-WUSs with different values of the wake-up indication bit of the terminal 20.
[0131] [CR Example of Alt.2-1] The terminal 20 does not monitor the LP-WUS during the DRX active time. [CR Example of Alt.3-1] If the terminal 20 is configured for LP-WUS monitoring and there is no LP-WUS monitoring opportunity for the terminal 20 before the drx-onDurationTimer of the next DRX cycle, the terminal 20 may monitor the PDCCH of the serving cell associated with the LP-WUS of the associated DRX cycle.
[0132] Regarding Alternative 1-1 of Example 3, it may be specified that in an LP-WUS monitoring occasion associated with the same long DRX cycle, the UE is not expected to detect multiple LP-WUSs with different values of the wake-up indication bit for the UE. In other words, the UE is not expected to receive multiple LP-WUSs with different wake-up indications within the same DRX cycle.
[0133] Regarding Alt. 2-1 of Example 3, it may be specified that the UE does not monitor the LP-WUS during the active time of DRX.
[0134] Regarding Alternative 3-1 of Example 3, it may be specified that if LP-WUS monitoring is configured for the UE and there is no LP-WUS monitoring opportunity before the drx-onDurationTimer of the next DRX cycle, the UE shall monitor the PDCCH for the serving cell associated with the LP-WUS in the relevant DRX cycle. In other words, even if no LP-WUS is received by the start of the active time of the next DRX cycle, the UE shall continue to monitor the PDCCH for the cell associated with the LP-WUS in that DRX cycle.
[0135] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.
[0136] <Base Station> Fig. 16 is a diagram showing an example of the functional configuration of the base station 10 in this embodiment. As shown in Fig. 16, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 16 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations according to this embodiment.
[0137] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitter 110 also transmits setting information, instructions, notifications, etc. related to a low-power wake-up signal to the terminal 20. The transmitter 110 also transmits notifications related to switching of monitoring operations to the terminal. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.
[0138] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to measurements of low-power signals.
[0139] As described in the embodiments, the control unit 140 controls settings, instructions, and notifications related to low-power wake-up signals, etc. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.
[0140] <Terminal> Fig. 17 is a diagram showing an example of the functional configuration of the terminal 20 in this embodiment. As shown in Fig. 17, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 17 is merely an example. As long as the operations according to this embodiment can be executed, the names of the functional divisions and functional units may be any. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.
[0141] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitter 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiver 220 wirelessly receives various signals and acquires higher-layer signals from the received physical layer signals. The receiver 220 also has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. The receiver 220 also receives paging notification information and configuration information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiver 220 receives a low-power wake-up signal from the base station 10. The configuration unit 230 stores various configuration information received from the base station 10 by the receiver 220. The configuration unit 230 also stores pre-configured configuration information. The configuration information includes, for example, information related to measurements of the low-power signal.
[0142] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to the low-power wake-up signal. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.
[0143] (Hardware Configuration) The block diagrams (FIGS. 16 and 17) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.
[0144] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0145] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 18 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above 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.
[0146] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0147] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.
[0148] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.
[0149] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 16 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 17 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.
[0150] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.
[0151] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.
[0152] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.
[0153] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0154] 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 may be configured using different buses between each device.
[0155] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.
[0156] Fig. 19 shows an example configuration of a vehicle 2001. As shown in Fig. 19, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0157] The drive unit 2002 is configured, for example, by 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 operated by the user.
[0158] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0159] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0160] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.
[0161] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0162] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.
[0163] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
[0164] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0165] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices 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 to 2029, etc. provided in the vehicle 2001.
[0166] (Configuration related to this embodiment) (Item 1) A terminal comprising: a control unit that sets monitoring of a low power wake-up signal from a base station for the terminal in a connected state that communicates using multiple cells; and a receiving unit that receives the low power wake-up signal in a specific cell among the multiple cells that is used to transmit the low power wake-up signal.
[0167] (Item 2) The terminal according to item 1, wherein the predetermined cell is a PCell (Primary Cell), a PSCell (Primary Secondary Cell), a SCell (Secondary Cell), or a SpCell (Special Cell), and the low power wake-up signal is transmitted only by the PCell, the PSCell, the SCell, or the SpCell.
[0168] (Clause 3) The terminal according to clause 1, wherein the plurality of cells belong to a plurality of DRX (Discontinuous Reception) groups, and the low power wake-up signal triggers PDCCH (Physical Downlink Control Channel) monitoring in all cells included in the plurality of DRX groups.
[0169] (Clause 4) The terminal according to clause 1, wherein the plurality of cells belong to a plurality of DRX groups, the period indicated by drx-onDurationTimer differs for each of the plurality of DRX groups, and the low power wake-up signal triggers PDCCH monitoring in all cells included in each of the plurality of DRX groups, for each of the plurality of DRX groups.
[0170] (Clause 5) The terminal according to clause 1, wherein the plurality of cells belong to a plurality of DRX groups, and a plurality of wake-up signals for low power are each associated one-to-one with the plurality of DRX groups, and each of the plurality of wake-up signals for low power triggers PDCCH monitoring in all cells included in the associated DRX group among the plurality of DRX groups.
[0171] (Clause 6) A communication method executed by a terminal, comprising: a step of configuring the terminal, which is in a connected state and communicates using a plurality of cells, to monitor for a low power wake-up signal from a base station; and a step of receiving the low power wake-up signal in a predetermined cell among the plurality of cells that is used to transmit the low power wake-up signal.
[0172] Any of the above configurations allows a terminal communicating using multiple cells to appropriately perform operations related to low-power signals. Furthermore, the above configurations clarify the LP-WUS design in CA / DC, which was previously unspecified. Furthermore, clauses 1, 2, and 6 clarify the LP-WUS configuration in CA / DC, including one or more BWPs or CCs capable of transmitting the LP-WUS, the serving cell that monitors the LP-WUS, and the BWP that monitors the LP-WUS. Clauses 3 to 5 clarify the LP-WUS monitoring operation and the association between the LP-WUS and the serving cell, taking into account multiple cells and multiple DRX groups.
[0173] (Supplementary Notes on the Embodiments) Although the present embodiment has been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor 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 each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.
[0174] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling and Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB) and System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0175] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.
[0176] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.
[0177] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).
[0178] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.
[0179] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.
[0180] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values (e.g., comparison with a predetermined value).
[0181] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0182] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0183] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0184] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0185] As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0186] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.
[0187] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0188] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.
[0189] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of a base station and / or base station subsystem that provides communication services within that coverage.
[0190] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.
[0191] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0192] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.
[0193] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication 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.
[0194] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0195] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.
[0196] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0197] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.
[0198] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.
[0199] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."
[0200] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.
[0201] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.
[0202] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.
[0203] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0204] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, etc.
[0205] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.
[0206] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.
[0207] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0208] 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. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.
[0209] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.
[0210] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0211] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0212] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0213] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.
[0214] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.
[0215] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0216] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0217] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0218] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0219] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.
[0220] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."
[0221] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.
[0222] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0223] In the present 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 "coupled" may also be interpreted in the same way as "different."
[0224] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).
[0225] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.
[0226] 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 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)
Claims
1. A terminal comprising: a control unit that sets monitoring of a low power wake-up signal from a base station for the terminal in a connected state that communicates using multiple cells; and a receiving unit that receives the low power wake-up signal in a specific cell among the multiple cells that is used to transmit the low power wake-up signal.
2. The terminal according to claim 1, wherein the predetermined cell is a PCell (Primary Cell), a PSCell (Primary Secondary Cell), a SCell (Secondary Cell), or a SpCell (Special Cell), and the low power wake-up signal is transmitted only by any one of the PCell, the PSCell, the SCell, or the SpCell.
3. The terminal according to claim 1, wherein the plurality of cells belong to a plurality of DRX (Discontinuous Reception) groups, and the low power wake-up signal triggers PDCCH (Physical Downlink Control Channel) monitoring in all cells included in the plurality of DRX groups.
4. The terminal according to claim 1, wherein the plurality of cells belong to a plurality of DRX groups, the period indicated by drx-onDurationTimer differs for each of the plurality of DRX groups, and the low power wake-up signal triggers PDCCH monitoring in all cells included in each of the plurality of DRX groups, for each of the plurality of DRX groups.
5. The terminal according to claim 1, wherein the plurality of cells belong to a plurality of DRX groups, a plurality of wake-up signals for low power are respectively associated one-to-one with the plurality of DRX groups, and each of the plurality of wake-up signals for low power triggers PDCCH monitoring in all cells included in the associated DRX group among the plurality of DRX groups.
6. A communication method executed by a terminal, comprising: a step of setting up monitoring of a low power wake-up signal from a base station for the terminal in a connected state that communicates using a plurality of cells; and a step of receiving the low power wake-up signal in a predetermined cell among the plurality of cells that is used to transmit the low power wake-up signal.