KR20240115573A - Method and apparatus for DTX (discontinuous transmission) operation of network in wireless communication system - Google Patents

Abstract

This specification proposes a terminal operation method and terminal device in a wireless communication system. That is, the terminal receives information related to discontinuous transmission (DTX) of the cell, and after the terminal receives information related to discontinuous transmission of the cell, monitoring of the physical downlink control channel (PDCCH) Suggests methods and devices that do not perform this.

Description

{Method and apparatus for DTX (discontinuous transmission) operation of network in wireless communication system}

This specification relates to the 3GPP 5G NR system.

As more and more communication devices require larger communication traffic as the times go by, the next-generation 5G system, which is an improved wireless broadband communication than the existing LTE system, is required. In this next-generation 5G system, called NewRAT, communication scenarios are divided into Enhanced Mobile BroadBand (eMBB)/Ultra-reliability and low-latency communication (URLLC)/Massive Machine-Type Communications (mMTC).

Here, eMBB is a next-generation mobile communication scenario with characteristics such as High Spectrum Efficiency, High User Experienced Data Rate, and High Peak Data Rate, and URLLC is a next-generation mobile communication scenario with characteristics such as Ultra Reliable, Ultra Low Latency, and Ultra High Availability. (e.g., V2X, Emergency Service, Remote Control), mMTC is a next-generation mobile communication scenario with Low Cost, Low Energy, Short Packet, and Massive Connectivity characteristics. (e.g., IoT).

Meanwhile, network energy savings are important for environmental sustainability and operational cost reduction. As communication technology develops, networks become more dense, and more antennas and larger bandwidths are used to handle advanced services and applications that require very high data transmission rates. According to the GSMA report, the energy cost of mobile networks accounts for up to 23% of the total operating cost. Most of the energy consumption comes from the wireless access network, especially the active antenna units. The power consumption of wireless access is separated into two parts. The dynamic part is consumed when data transmission/reception is in progress and the static part is consumed at all times to maintain the necessary operation of the wireless access device even when data transmission/reception is not in progress. As a potential technology for saving network energy, applying DTX (Discontinuous Transmission)/DRX (Discontinuous Reception) in the cell(s) connected to the base station can be considered. This allows the base station to have the opportunity to turn off data transmission/reception and/or reference signal transmission/reception by setting non-active/inactive time/duration. During the inactive time/duration, the base station may refrain from transmitting/receiving some periodic signals/channels such as common channels/signals or terminal specific signals/channels. The base station can either do no transmission/reception or maintain only limited transmission/reception. This can save network energy. However, if C-DRX is configured to reduce terminal power consumption for the terminal(s) in a connected state in the cell, it may not be aligned with the C-DRX configured in the terminal.

To save network energy, you can consider setting an inactive time/duration in which the base station does not transmit/receive data through cell-specific DTX/DRX, but this may cause a conflict with the DRX configured in the connected terminal, resulting in unexpected transmission. There are problems that may cause unnecessary power consumption of the terminal or deterioration of service quality due to failure.

Therefore, the purpose of the disclosure of this specification is to provide a specific method and device that can be used by aligning network/cell DTX/DRX and terminal DRX to solve the above-mentioned problems.

This specification proposes a terminal operation method and terminal device in a wireless communication system. That is, the terminal receives information related to discontinuous transmission (DTX) of the cell, and after the terminal receives information related to discontinuous transmission of the cell, monitoring of the physical downlink control channel (PDCCH) Suggests methods and devices that do not perform this.

This specification targets the 5G/5G-advanced system defined in 3GPP, but the technology/concept proposed in this specification can be applied to mobile communication systems other than 5G, such as LTE or 6G to be defined in the future.

According to the disclosure of this specification, terminal DRX operation according to cell DTX/DRX provision can be effectively processed.

Figure 1 illustrates the structure of a radio frame used in NR.
Figure 2 shows an example of a DRX cycle.
Figure 3 shows a block diagram of a processor on which the disclosure of the present specification is implemented.
Figure 4 shows a wireless communication device according to an embodiment of the present specification.
Figure 5 illustrates a block diagram of a communication device according to an embodiment of the present specification.

Although this specification describes embodiments using an LTE system, an LTE-A system, and an NR system, these embodiments may be applied to any communication system that falls within the above definition.

In addition, in this specification, the name of the base station may be used as a comprehensive term including remote radio head (RRH), eNB, transmission point (TP), reception point (RP), relay, etc.

The 3GPP-based communication standard includes downlink physical channels corresponding to resource elements carrying information originating from the upper layer, and downlink physical channels corresponding to resource elements used by the physical layer but not carrying information originating from the upper layer. Physical signals are defined. For example, a physical downlink shared channel (PDSCH), a physical broadcast channel (PBCH), a physical multicast channel (PMCH), and a physical control format indicator channel (physical control). format indicator channel (PCFICH), physical downlink control channel (PDCCH), and physical hybrid ARQ indicator channel (PHICH) are defined as downlink physical channels, and reference signals and synchronization signals are defined as downlink physical signals. A reference signal (RS), also referred to as a pilot, refers to a signal with a predefined special waveform known to both the gNB and the UE, for example, cell specific RS (cell specific RS), UE- UE-specific RS (UE-RS), positioning RS (PRS), and channel state information RS (CSI-RS) are defined as downlink reference signals. The 3GPP LTE/LTE-A standard corresponds to uplink physical channels corresponding to resource elements carrying information originating from upper layers, and resource elements used by the physical layer but not carrying information originating from upper layers. Uplink physical signals are defined. For example, a physical uplink shared channel (PUSCH), a physical uplink control channel (PUCCH), and a physical random access channel (PRACH) are used as uplink physical channels. A demodulation reference signal (DMRS) for uplink control/data signals and a sounding reference signal (SRS) used for uplink channel measurement are defined.

In this specification, PDCCH (Physical Downlink Control CHannel) / PCFICH (Physical Control Format Indicator CHannel) / PHICH ((Physical Hybrid automatic retransmit request Indicator CHannel) / PDSCH (Physical Downlink Shared CHannel) are respectively DCI (Downlink Control Information) / CFI ( Control Format Indicator)/Downlink ACK/NACK (ACKnowlegement/Negative ACK)/Refers to a set of time-frequency resources or a set of resource elements carrying downlink data. Also, PUCCH (Physical Uplink Control CHannel)/PUSCH (Physical). Uplink Shared CHannel)/PRACH (Physical Random Access CHannel) refers to a set of time-frequency resources or a set of resource elements that carry UCI (Uplink Control Information)/uplink data/random access signal, respectively.

Figure 1 illustrates the structure of a radio frame used in NR.

In NR, uplink and downlink transmission consists of frames. A wireless frame is 10ms long and is defined as two 5ms half-frames (HF). A half-frame is defined as five 1ms subframes (Subframe, SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on SCS (Subcarrier Spacing). Each slot contains 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP). Normally when CP is used, each slot contains 14 symbols. When extended CP is used, each slot contains 12 symbols. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or DFT-s-OFDM symbol).

Table 1 illustrates that when a normal CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

SCS(15* ^2u )
N- ^slot _symbol
N ^{frame, u} _slot
N ^{subframe, u} _slot
15 KHz (u = 0)
14
10
One
30 KHz (u = 1)
14
20
2
60 KHz (u = 2)
14
40
4
120 KHz (u =3)
14
80
8
240 KHz (u =4)
14
160
16

N ^slot _symb : Number of symbols in a slotN ^frame,u _slot : Number of slots in a frame

N ^subframe,u _slot : Number of slots in subframe

Table 2 illustrates that when an extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary depending on the SCS.

SCS (15* ^2u ) N- ^slot _symbol N ^{frame, u} _slot N ^subframe,u _slot 60KHz (u=2) 12 40 4

In an NR system, OFDM(A) numerology (eg, SCS, CP length, etc.) may be set differently between multiple cells merged into one UE. Accordingly, the (absolute time) interval of time resources (e.g., SF, slot, or TTI) (for convenience, collectively referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between merged cells. Figure 2 shows an example of a DRX cycle.

Referring to Figure 2, the terminal uses DRX to save power. Once DRX is set, the UE does not need to continuously perform PDCCH monitoring. That is, PDCCH reception is attempted only within the set time interval, and PDCCH reception is not attempted within the remaining time interval. The section in which the UE performs PDCCH monitoring is called on-duration, and the on-duration section is defined once per DRX cycle.

Meanwhile, DRX has the following characteristics.

- on-duration: This is the duration in which the terminal waits to receive the PDCCH after waking up. If the terminal successfully decodes the PDCCH, the terminal remains awake and starts the inactivity timer (inactivity-timer).

- Deactivation timer: This is the time period in which the terminal waits for successful PDCCH decoding from the last successful PDCCH decoding, and in case of failure, the terminal goes back to sleep. The UE must restart the inactivity timer after successfully decoding the PDCCH only for the first transmission (i.e., not for retransmission).

- Retransmission timer: This is the time period until retransmission is expected.

- Cycle: Specifies a periodic repetition of on-duration followed by a possible deactivation cycle.

- Active time: This is the total period during which the terminal monitors the PDCCH.

Below, we describe the 5GS/NR-based network/cell/BWP DTX/DRX operation method. However, this is for convenience of explanation and the present invention can be applied to any system/wireless access technology (e.g. LTE, 6G). The embodiment described in the present invention includes the contents of information elements and operations specified in the NR/5GS standard (e.g. TS 38.321 as a MAC standard, TS 38.331 as an NR RRC standard, etc.). Even if the definition of the corresponding information element and the related terminal operation content are not included in this specification, the corresponding content specified in the standard specification, which is a known technology, may be included in the present invention.

Any function described below is defined as an individual terminal capability (UE radio capability or UE Core network capability) and can be transmitted by the terminal to the base station/core network entity (e.g. AMF/SMF) through corresponding signaling. . Alternatively, arbitrary functions may be combined/combined, defined as the terminal capability, and transmitted by the terminal to the base station/core network entity through corresponding signaling.

The base station may transmit/instruct information indicating permission/support/pre-configuration of the function/function combination for any function or combination of functions described below to the terminal through an RRC message. For example, this may be given to the terminal before or after the configuration/application of the function/function combination, or at the same time as the instruction for the configuration/application of the function/function combination. The RRC message can be broadcast through system information. Alternatively, it may be indicated to the terminal through a dedicated RRC message (e.g. RRC reconfiguration).

The functions described below can be performed individually and independently. It is obvious that the functions described below can be implemented in any combination/combination and that this is also included within the scope of the present invention. For example, more than one function may be applied simultaneously.

Operation to skip/not perform/stop PDCCH monitoring during cell DTX/DRX offduration/non-active time

For convenience of explanation, the following describes how to operate when using Cell DTX with terminal DRX. This is for convenience of explanation, and it is obvious that the operation method when using Cell DRX or Cell DTX/Cell DRX together with terminal DRX is also included in the scope of the present invention.

In the prior art, when the terminal (MAC entity) is in the RRC connection state, if DRX (UE DRX) is configured (for all activated serving cells), the terminal (MAC entity) uses the DRX operation. The PDCCH can be monitored discontinuously. Otherwise, the terminal (MAC entity) must continuously monitor the PDCCH (or according to the specifications specified in TS 38.213).

If cell DTX is configured/indicated, the UE can monitor the PDCCH (discontinuously) by taking this into account.

For example, PDCCH monitoring can be skipped/not performed/stopped/interrupted during the DTX offduration/non-active time of the cell. For example, when the cell DTX offduration/non-active time starts, if the terminal DRX is configured in the terminal, the active time operation according to the terminal DRX configuration can be skipped/not performed/stopped/suspended/suspended/ignored.

As another example, the PDCCH can be monitored using DRX operation during the DTX onduration/active time of the cell.

For another example, a timer for indicating cell DTX offduration/non-active time at the start of one cell DTX cycle/period in the corresponding cell may be instructed/configured in the terminal. For convenience of explanation, this is referred to as CellDTX-Offduration Timer. This is for convenience of explanation and may be replaced with any other name. Information to indicate a delay before the start of the corresponding cell DTX-offduration timer may be instructed/configured in the terminal. For convenience of explanation, this is referred to as Cell DTX-Operation Slot Offset. Information to indicate the subframe in which the corresponding cell DTX cycle/period (or cell DTX offduration/non-active time accordingly) starts may be instructed/configured in the terminal. For convenience of explanation, this is referred to as Cell DTX-Offduration Start Offset.

If cell DTX cycles/cycle are used for one cell DTX configuration, and [(SFN × 10) + subframe number] modulo (cell DTX cycle/cycle) = (cell DTX offduration start offset) modulo (cell DTX cycle /cycle), the terminal (MAC entity) starts/restarts the cell DTX-offduration timer for the corresponding cell DTX configuration after the cell DTX offduration slot offset from the start of the subframe.

For another example, the base station can deactivate cell DTX through arbitrary L1/L2 signaling (e.g. UE-specific PDCCH, group-common PDCCH, cell-specific PDCCH, MAC CE). When the corresponding L1/L2 signaling is received, the terminal (MAC entity) can enter Cell DTX offduration/non-active time. Start/restart the cell DTX-offduration timer for the corresponding cell DTX configuration. The corresponding L1 signaling may be indicated with a UE-specific DCI/DCI_format, group-specific, or cell-specific DCI/DCI_format. The MAC CE may be indicated with a scrambled DCI with a UE-specific RNTI (e.g. C-RNTI). The MAC CE may be indicated with a DCI scrambled with a group-specific RNTI or a cell-specific RNTI. The L1/L2 signaling may include one or more of the following: index information for distinguishing the DTX configuration, information for indicating activation/deactivation, and index information of the cell for which activation/deactivation is indicated.

For another example, a timer may be instructed/configured in the terminal to indicate the cell DTX onduration/active time at the start of one cell DTX cycle/period in the corresponding cell. For convenience of explanation, this is referred to as CellDTX-Onduration Timer. This is for convenience of explanation and may be replaced with any other name. Information to indicate a delay before the start of the corresponding cell DTX-onduration timer may be instructed/configured in the terminal. For convenience of explanation, this is referred to as Cell DTX-Onduration Slot Offset. Information to indicate the subframe in which the corresponding cell DTX cycle/period (or cell DTX onduration/active time accordingly) starts may be instructed/configured in the terminal. For convenience of explanation, this is referred to as Cell DTX-Onduration Start Offset.

If cell DTX cycles/cycle are used for one cell DTX configuration, and [(SFN × 10) + subframe number] modulo (cell DTX cycle/cycle) = (cell DTX onduration start offset) modulo (cell DTX cycle /cycle), the terminal (MAC entity) starts/restarts the cell DTX-onduration timer for the corresponding cell DTX configuration after the cell DTX onduration slot offset from the start of the subframe.

For another example, the base station can activate cell DTX through arbitrary L1/L2 signaling (e.g. UE-specific PDCCH, group-common PDCCH, cell-specific PDCCH, MAC CE). When the corresponding L1/L2 signaling is received, the terminal (MAC entity) can enter CellDTX onduration/active time. Stop the cell DTX-offduration timer for the corresponding cell DTX configuration.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal sets the DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. Even if is running, PDCCH monitoring can be skipped/not performed/stopped/interrupted (in the corresponding cell or in the corresponding serving cell). The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal sets the DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. Even if is running (in the corresponding cell or in the corresponding serving cell), it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is not running, the terminal sets the DRX onduration timer/DRX inactivity according to the terminal DRX configuration. If a timer is running, it can be included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal sets the DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. If is running, the corresponding DRX Onduration Timer/DRX InActivity Timer can be stopped (in the corresponding cell or in the corresponding serving cell). The DRX Onduration Timer/DRX Inactivity Timer can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer starts/restarts, the terminal has a DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. If it is running, you can stop/abort/suspend the corresponding DRX Onduration Timer/DRX InActivity Timer (in the corresponding cell or in the corresponding serving cell). The DRX Onduration Timer/DRX Inactivity Timer can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer stops/expires, the terminal (in the corresponding cell or in the serving cell) according to the terminal DRX configuration You can start/restart/resume the DRX Onduration Timer/DRX Inactivity Timer.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal is configured (in the corresponding cell or serving cell) to the terminal DRX configuration. Even if the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, PDCCH monitoring can be skipped/not performed/stopped/aborted. . The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal is configured (in the corresponding cell or serving cell) to the terminal DRX configuration. Even if the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is not running, the terminal sets the downlink DRX retransmission timer (drx-) according to the terminal DRX configuration. If the uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, it can be included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal is configured (in the corresponding cell or serving cell) to the terminal DRX configuration. If the corresponding downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, the corresponding downlink DRX retransmission timer (drx-RetransmissionTimerDL)/ The uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be stopped. The downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer starts/restarts, the terminal (in the corresponding cell or in the corresponding serving cell) is configured/instructed to configure the terminal DRX. If the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, the corresponding downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink You can stop/interrupt/suspend the link DRX retransmission timer (drx-RetransmissionTimerUL)/side link DRX retransmission timer (drx-RetransmissionTimerSL). The downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer stops/expires, the terminal (in the corresponding cell or in the serving cell) according to the terminal DRX configuration You can start/restart/resume the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL).

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal resolves random access contention (in the corresponding cell or in the serving cell). Even if the timer (ra-ContentionResolutionTimer)/Message B Response Window (msgB-ResponseWindow) is running, PDCCH monitoring can be skipped/not performed/stopped/interrupted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal resolves random access contention (in the corresponding cell or in the serving cell). Even if the timer (ra-ContentionResolutionTimer)/MessageB Response Window (msgB-ResponseWindow) is running, it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is not running, the terminal sends the corresponding random access contention resolution timer (ra-ContentionResolutionTimer)/message If the B response window (msgB-ResponseWindow) is running, it can be included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal resolves random access contention (in the corresponding cell or in the serving cell). If the timer (ra-ContentionResolutionTimer)/Message B Response Window (msgB-ResponseWindow) is running, stop/suspend/suspend the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B Response Window (msgB-ResponseWindow), PDCCH monitoring skip/not performed/stop/abort/suspend, random access Temporary terminal identifier (TEMPORARY_C-RNTI) which is the value received in the response message Discard/maintain, random access procedure is considered to have failed/stop/suspend/abort More than one action can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer starts/restarts, the terminal (in the corresponding cell or in the corresponding serving cell) is configured/instructed to configure the terminal DRX. If the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) is running, the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) is stopped. /Stop/Suspend, PDCCH monitoring Skip/Not performed/Stop/Abort/Suspend, Temporary terminal identifier (TEMPORARY_C-RNTI) which is the value received in the random access response message Discard/Maintain, One or more of the random access procedures considered to have failed The action can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer stops/expires, the terminal (in the corresponding cell or in the serving cell) according to the terminal DRX configuration You can start/restart/resume the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow).

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal receives a scheduling request (in the corresponding cell or serving cell) on the PUCCH. When sent to and pending, PDCCH monitoring can be skipped/not performed/stopped/interrupted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal receives a scheduling request (in the corresponding cell or serving cell) on the PUCCH. When it is sent to and is pending, it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is not running, the terminal sends a scheduling request (in the corresponding cell or in the serving cell) to PUCCH It can be included in the active time when it is sent to the top and is pending. It is possible to prevent other serving cells other than the cell from being included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal receives a scheduling request (in the corresponding cell or serving cell) on the PUCCH. When sent to and pending, PDCCH monitoring is skipped/not performed/stopped/suspended, random access procedure initiated (on special cell), pending scheduling request stopped/suspended/suspended, pending scheduling request canceled, scheduling request prohibited. Start a timer (sr-ProhibitTimer), increase the scheduling request counter (SR_COUNTER) by 1, and stop one of the random access procedures in progress due to a pending SR (for one or more of BSR, SL-BSR, BFR, consistent LBT failre recovery). The above operations can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer starts/restarts, the terminal (in the corresponding cell or serving cell) sends a scheduling request on the PUCCH. When sent and pending, skip/not perform/stop/suspend PDCCH monitoring, start random access procedure (on special cell), stop/suspend/suspend pending scheduling request, cancel pending scheduling request, inhibit scheduling request timer Start (sr-ProhibitTimer), increase scheduling request counter (SR_COUNTER) by 1, stop one or more random access procedures in progress due to pending SR (for one or more of BSR, SL-BSR, BFR, consistent LBT failre recovery) The action can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer stops/expires, the terminal (in the corresponding cell or in the serving cell) according to the terminal DRX configuration One or more operations can be performed among starting/restarting/resuming a pending scheduling request, starting the scheduling request prohibit timer (sr-ProhibitTimer), or increasing the scheduling request counter (SR_COUNTER) by 1. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) MAC When the PDCCH indicating new transmission addressed to the C-RNTI of the corresponding MAC entity is not received after successful reception of a random access preamble that was not selected among the contention-based random access preambles by the entity, PDCCH monitoring is skipped/ It may not be performed/stopped/interrupted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) MAC Even when the PDCCH indicating new transmission addressed to the C-RNTI of the corresponding MAC entity is not received after successful reception of a random access preamble that was not selected among the contention-based random access preambles by the entity, it is not included in the active time. can do. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-offduration timer is not running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) After successful reception of a random access preamble that is not selected among the contention-based random access preamble by the MAC entity, if the PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received, it can be included in the active time. there is.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-offduration timer is started/restarted, the terminal (MAC entity) (in the corresponding cell or in the corresponding serving cell) MAC entity If the PDCCH indicating new transmission addressed to the C-RNTI of the corresponding MAC entity is not received after successful reception of a random access preamble that is not selected among the contention-based random access preambles, PDCCH monitoring is skipped/not performed. /stop/can be aborted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

Here, (in the corresponding cell or in the serving cell) may indicate a case where any parameter described in relation (e.g. DRX timer, random access contention resolution timer, etc.) operates in connection with the cell or the serving cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the DRX onduration timer/DRX inactivity according to the terminal DRX configuration. When the timer is running (in the corresponding cell or in the corresponding serving cell), PDCCH monitoring can be skipped/not performed/stopped/interrupted. If the cell DTX-onduration timer is running, the terminal monitors the PDCCH (in the corresponding cell or in the serving cell) when the DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration is running. You can.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the DRX onduration timer/DRX inactivity according to the terminal DRX configuration. When a timer is running (either in that cell or in that serving cell) it may not be included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, DRX Onduration Timer/DRX Inactivity Timer is applied specifically to that configuration/group/terminal in one DRX configuration/DRX group. Therefore, regardless of cell DTX-Onduration Timer execution, the terminal can be included in the active time (in the corresponding cell or in the serving cell) when the DRX Onduration Timer/DRX InActivity Timer according to the terminal DRX configuration is running. However, PDCCH monitoring can be skipped/not performed/stopped/interrupted in that cell (in that cell or in that serving cell). If the cell DTX-onduration timer of each serving cell is running in the remaining serving cells other than the cell, the PDCCH can be monitored in each serving cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is running, the terminal is configured to configure the terminal DRX (in the corresponding cell or in the serving cell). If the corresponding DRX Onduration Timer/DRX Inactivity Timer is running, it can be included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the DRX onduration timer/DRX inactivity according to the terminal DRX configuration. If the timer is running, the corresponding DRX Onduration Timer/DRX InActivity Timer can be stopped (in the corresponding cell or in the corresponding serving cell). The corresponding DRX Onduration Timer/DRX InActivity Timer can be maintained in the remaining serving cells other than the corresponding cell (if the cell DTX-onduration timer of each serving cell is running).

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts, the terminal has a DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. If it is not running, you can start/restart/resume the corresponding DRX Onduration Timer/DRX InActivity Timer (in the corresponding cell or in the corresponding serving cell).

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts, the terminal has a DRX onduration timer/DRX inactivity timer according to the terminal DRX configuration. If running, you can start/restart/resume/maintain the corresponding DRX Onduration Timer/DRX Inactivity Timer (in the corresponding cell or in the corresponding serving cell). The DRX Onduration Timer/DRX Inactivity Timer can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer stops/expires, the terminal (in the corresponding cell or in the serving cell) according to the terminal DRX configuration You can stop/interrupt/suspend the DRX Onduration Timer/DRX Inactivity Timer. The DRX Onduration Timer/DRX Inactivity Timer can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). Even if the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, PDCCH monitoring can be skipped/not performed/stopped/interrupted. there is. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). Even if the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is running, the terminal sets the downlink DRX retransmission timer (drx-RetransmissionTimerDL) according to the terminal DRX configuration. )/Uplink DRX Retransmission Timer (drx-RetransmissionTimerUL)/Sidelink DRX Retransmission Timer (drx-RetransmissionTimerSL) can be included in the active time if they are running.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). If the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) is running, the corresponding downlink DRX retransmission timer (drx-RetransmissionTimerDL) You can stop/interrupt/suspend the /Uplink DRX Retransmission Timer (drx-RetransmissionTimerUL)/Sidelink DRX Retransmission Timer (drx-RetransmissionTimerSL). The downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer stops/interrupts/suspends/expires, the terminal (in the corresponding cell or in the serving cell) If the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) according to the DRX configuration is running, the corresponding downlink DRX retransmission timer (drx- You can stop/interrupt/suspend the uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL). The downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be maintained in the remaining serving cells other than the cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts/resumes, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). You can start/restart/resume the downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) according to. The downlink DRX retransmission timer (drx-RetransmissionTimerDL)/uplink DRX retransmission timer (drx-RetransmissionTimerUL)/sidelink DRX retransmission timer (drx-RetransmissionTimerSL) can be maintained in the remaining serving cells other than the cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or in the serving cell) random access contention Even if the resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) is running, PDCCH monitoring can be skipped/not performed/stopped/interrupted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or in the serving cell) random access contention Even if the resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) is running, it can be prevented from being included in the active time. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when Cell DTX and Terminal DRX are configured/instructed in the terminal, when Cell DTX-Onduration Timer is running, the terminal uses the corresponding random access contention resolution timer (ra-ContentionResolutionTimer)/Message B. If the response window (msgB-ResponseWindow) is running, it can be included in the active time.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or in the serving cell) random access contention If the resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) is running, stop/suspend/suspend the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow). , PDCCH monitoring skip/not performed/stop/abort/suspend, temporary terminal identifier (TEMPORARY_C-RNTI) which is the value received in the random access response message, Discard/maintain, random access procedure considered to have failed/stopped/suspended/aborted. One or more actions can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer stops/interrupts/suspends/expires, the terminal (in the corresponding cell or in the serving cell) If the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB-ResponseWindow) according to the DRX configuration is running, the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B response window (msgB- ResponseWindow) stop/suspend/suspend, PDCCH monitoring skip/not performed/stop/suspend, random access temporary terminal identifier (TEMPORARY_C-RNTI) which is the value received in the response message, discard/maintain, random access procedure fails/ You can perform one or more of the actions considered as stop/suspend/interrupted. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts/resumes, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). You can start/restart/resume the random access contention resolution timer (ra-ContentionResolutionTimer)/Message B Response Window (msgB-ResponseWindow) according to .

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or serving cell) sends a scheduling request to PUCCH PDCCH monitoring can be skipped/not performed/stopped/interrupted when it is sent to the network and pending. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or serving cell) sends a scheduling request to PUCCH You can prevent it from being included in the active time when it is sent to the top and pending. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is running, the terminal (in the corresponding cell or serving cell) receives a scheduling request on the PUCCH. It can be included in active time when it is sent to and is pending.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (in the corresponding cell or serving cell) sends a scheduling request to PUCCH When sent and pending, PDCCH monitoring is skipped/not performed/stopped/suspended, random access procedure initiated (on special cell), pending scheduling request stopped/suspended/suspended, pending scheduling request canceled, scheduling request Starting prohibit timer (sr-ProhibitTimer), increasing scheduling request counter (SR_COUNTER) by 1, stopping random access procedure in progress due to pending SR (for one or more of BSR, SL-BSR, BFR, consistent LBT failre recovery) More than one action can be performed. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer stops/interrupts/suspends/expires, the terminal requests scheduling (in the corresponding cell or in the serving cell). When sent on this PUCCH and pending, skip/not perform/stop/suspend PDCCH monitoring, initiate random access procedure (on special cell), stop/abort/suspend pending scheduling request, cancel pending scheduling request, Starts scheduling request prohibit timer (sr-ProhibitTimer), increases scheduling request counter (SR_COUNTER) by 1, random access procedure in progress due to pending SR (for one or more of BSR, SL-BSR, BFR, consistent LBT failre recovery) One or more actions can be performed during a stop. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts/resumes, the terminal configures the terminal DRX (in the corresponding cell or in the serving cell). One or more operations may be performed among starting/restarting/resuming a pending scheduling request, starting the scheduling request prohibit timer (sr-ProhibitTimer), and increasing the scheduling request counter (SR_COUNTER) by 1. It may operate differently in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) Skip PDCCH monitoring when the PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of a random access preamble that is not selected among the contention-based random access preambles by the MAC entity. /Not performed/Stop/Can be aborted. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is not running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) Even when the PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of a random access preamble that was not selected among the contention-based random access preambles by the MAC entity, it is not included in the active time. You can avoid it. It may be included in the active time in the remaining serving cells other than the corresponding cell.

For another example, when cell DTX and terminal DRX are configured/instructed in the terminal, if the cell DTX-onduration timer is running, the terminal (MAC entity) (in the corresponding cell or in the serving cell) MAC If a PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of a random access preamble that was not selected among the contention-based random access preambles by the entity, it can be included in the active time. .

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer stops/interrupts/suspends/expires, the terminal (MAC entity) (in the corresponding cell or corresponding serving cell) ) If the PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of the random access preamble that was not selected among the contention-based random access preamble by the MAC entity, PDCCH monitoring is performed. You can skip/not perform/stop/abort. The PDCCH can be monitored in the remaining serving cells other than the corresponding cell.

For another example, if cell DTX and terminal DRX are configured/instructed in the terminal, when the cell DTX-onduration timer starts/restarts/resumes, the terminal (MAC entity) (in the corresponding cell or in the serving cell) If the PDCCH indicating new transmission addressed to the C-RNTI of the MAC entity is not received after successful reception of a random access preamble that was not selected among the contention-based random access preambles by the MAC entity, the PDCCH can be monitored. there is.

Here, (in the corresponding cell or in the serving cell) may indicate a case where any parameter described in relation (e.g. DRX timer, random access contention resolution timer, etc.) operates in connection with the cell or the serving cell.

How to handle when cell DTX offduration/onduration is different for each cell

It can be configured as cell DTX offduration/non-active time in one cell and cell DTX onduration/active time in another cell. (vice versa) For convenience of explanation, this will be explained using the case where a terminal is configured with a CA with two serving cells (PCell, SCell). This is for convenience of explanation, and it is obvious that the case of two or more serving cells is also included in the scope of the present invention.

If the DTX onduration/non-active time and DTX onduration/active time of the two cells (PCell/SCell) are configured to be the same, when CA is configured in the terminal and SCell is activated, the terminal operates in each cell (according to base station scheduling). Data can be transmitted/received through the cell during the DTX onduration/active time where data transmission/reception is possible.

In each cell, SSB/CSI-RS can be transmitted/indicated at the cell DTX onduration/active time. If the measurement gap is configured as cell DTX offduration/non-active time, the terminal may not be able to perform measurements on the SCell using a different band/frequency. Therefore, the measurement gap can be configured to be performed at the cell DTX onduration/active time. If dual connectivity is used to merge cells between base stations, the serving/neighbor base station can request/response/transmit/confirm cell DTX configuration information to the neighbor/serving base station for appropriate terminal configuration. An Xn message can be defined for this.

If the DTX onduration/inactive time of one cell (e.g. PCell) is the DTX onduration/active time of another cell (e.g. SCell), and the DTX onduration/active time of the PCell is the DTX onduration/inactive time of the SCell If configured by time, when the CA is configured in the terminal and the SCell is activated, the terminal can transmit/receive data through the corresponding cell at the time when data can be transmitted and received through each cell (according to base station scheduling).

If one terminal DRX is configured in the corresponding terminal (or one DRX group is configured, or the corresponding DRX group is not configured with a secondary DRX group linked to a specific cell (e.g. the corresponding SCell)), the terminal monitors the PDCCH Among the parameters that make up the active time, the DRX Onduration Timer and DRX Inactivity Timer perform the corresponding timer operation regardless of cell. On the other hand, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL or drx-RetransmissionTimerSL distinguishes between cells because timer operation is performed for each corresponding DL/UL/SL HARQ process. Cells are distinguished even when ra-ContentionResolutionTimer/msgB-ResponseWindow or a scheduling request is sent and pending on PUCCH.

As an example to distinguish this, any operation (e.g. start, restart, resume, stop, suspend, expiration) related to the execution of the cell DTX onduration timer/active time or the cell DTX offduration timer/non-active time is one DRX group. It can be operated independently (regardless of the operation) of the DRX Onduration Timer/DRX Inactivity Timer.

As another example to distinguish this, any operation (e.g. start, restart, resume, stop, suspend, expiration) related to the execution of the cell DTX onduration timer/active time or the cell DTX offduration timer/non-active time is one DRX group. It can be operated in conjunction with the drx-RetransmissionTimerDL/drx-RetransmissionTimerUL/drx-RetransmissionTimerSL operations.

Added DRX-HARQ-RTT timer operation

When the terminal DRX is configured, the DRX-HARQ-RTT timer can be configured for each of the downlink, uplink, and sidelink. drx-HARQ-RTT-TimerDL indicates the minimum duration before allocating one DL for HARQ retransmission expected by the terminal (MAC entity). drx-HARQ-RTT-TimerUL indicates the minimum duration before one UL HARQ retransmission grant expected by the terminal (MAC entity). And drx-HARQ-RTT-TimerSL represents the minimum duration before one SL HARQ retransmission grant expected by the terminal (MAC entity).

For Cell DTX Onduration Timer Execution/Active Time, drx-HARQ-RTT-TimerDL indicates that the PDCCH will direct downlink transmission when a MAC PDU is received within the configured downlink assignment for unicast. It may be started in one or more of the following cases: when the PDCCH indicates retransmission of HARQ feedback.

In the case of cell DTX offduration timer execution/non-active time, drx-HARQ-RTT-TimerDL may not receive (or configure not to receive) MAC PDUs within the configured downlink assignment for unicast. /can be configured). Alternatively, the PDCCH may be set/configured to not instruct downlink transmission or retransmission of HARQ feedback. Therefore, it does not affect drx-HARQ-RTT-TimerDL startup operation.

If a MAC PDU is set/configured to be received within the configured downlink assignment at the cell DTX offduration timer execution/non-active time, the terminal (MAC entity) is responsible for receiving the corresponding transmission carrying the downlink HARQ feedback. After finishing, you can start drx-HARQ-RTT-TimerDL for the corresponding HARQ process within the first symbol.

In the case of cell DTX onduration timer execution/active time, if the data of the corresponding HARQ process has not been successfully decoded when drx-HARQ-RTT-TimerDL expires, drx-RetransmissionTimerDL for the corresponding HARQ process can be started.

In the case of cell DTX offduration timer execution/non-active time, even if the data of the corresponding HARQ process has not been successfully decoded when drx-HARQ-RTT-TimerDL expires, the corresponding data cannot be received, so it is necessary to monitor the corresponding PDCCH There is no Therefore, you can perform one or more of the following actions:

For example, in the case of cell DTX onduration timer execution/non-active time, when drx-HARQ-RTT-TimerDL expires, if the data of the corresponding HARQ process was not successfully decoded, the next/successive cell DTX onduration timer starts. When /restart/resume/ is executed, drx-RetransmissionTimerDL for the corresponding HARQ process can be started. or after drx-HARQ-RTT-TimerDL expires, after the cell DTX slot offset from the start/start of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/executes, for the corresponding HARQ process You can start drx-RetransmissionTimerDL.

For Cell DTX Onduration Timer Execution/Active Time, drx-HARQ-RTT-TimerUL is set when a MAC PDU is transmitted within a configured uplink grant (and when no LBT failure is received from the lower layer). , When the PDCCH indicates uplink transmission, it may be started in one or more of the following cases.

In the case of cell DTX offduration timer execution/non-active time, drx-HARQ-RTT-TimerUL can be set/configured so that MAC PDU is not transmitted within the configured uplink grant. Alternatively, the PDCCH may be set/configured not to indicate uplink transmission. Therefore, it does not affect drx-HARQ-RTT-TimerUL startup operation.

If the MAC PDU is set/configured to be transmitted within the configured uplink grant during the cell DTX offduration timer execution/non-active time (when no LBT failure is received from the lower layer), the terminal (MAC entity) Can start drx-HARQ-RTT-TimerUL for the corresponding HARQ process within the first symbol after the end of the first transmission of the corresponding PUSCH transmission.

In the case of cell DTX onduration timer execution/active time, when drx-HARQ-RTT-TimerUL expires, drx-RetransmissionTimerUL for the corresponding HARQ process can be started within the first symbol after the drx-HARQ-RTT-TimerUL expires.

In the case of cell DTX offduration timer execution/non-active time, if drx-HARQ-RTT-TimerUL expires, the corresponding data cannot be transmitted even after the expiration of the drx-HARQ-RTT-TimerUL, so there is no need to monitor the corresponding PDCCH. Therefore, you can perform one or more of the following actions:

For example, in the case of cell DTX onduration timer execution/non-active time, when drx-HARQ-RTT-TimerUL expires, when the next/successive cell DTX onduration timer is started/restarted/resumed/executed, the corresponding HARQ process You can start drx-RetransmissionTimerUL. Or, if drx-HARQ-RTT-TimerUL expires, from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/runs after expiration of the drx-HARQ-RTT-TimerUL. After the cell DTX slot offset, drx-RetransmissionTimerUL for the corresponding HARQ process can be started. Or, if drx-HARQ-RTT-TimerUL expires, from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/runs after expiration of the drx-HARQ-RTT-TimerUL. After the cell DTX slot offset, drx-RetransmissionTimerUL for the corresponding HARQ process can be started within the first symbol.

In the case of cell DTX onduration timer execution/active time, drx-HARQ-RTT-TimerSL is one or more of the following: when a MAC PDU is transmitted within a configured sidelink grant, or when the PDCCH indicates sidelink transmission. It can be started in some cases.

In the case of cell DTX offduration timer execution/non-active time, drx-HARQ-RTT-TimerSL can be set/configured so that MAC PDUs are not transmitted within the configured sidelink grant (configured uplink grant). Alternatively, the PDCCH may be set/configured not to indicate sidelink transmission. Therefore, it can be ensured that drx-HARQ-RTT-TimerSL startup operation is not affected.

If the MAC PDU is set/configured to be transmitted within a configured sidelink grant at the Cell DTX Offduration Timer Execution/NonActive Time, or sidelink data regardless of the Cell DTX Offduration Timer Execution/NonActive Time Since transmission and reception can be provided, if a MAC PDU is transmitted within the configured sidelink grant in the cell DTX offduration timer execution/non-active time, the terminal (MAC entity) is the first after the end of the corresponding PSSCH transmission. You can start drx-HARQ-RTT-TimerSL for the corresponding HARQ process from the symbol. For example, when the PUCCH resource is not configured, the corresponding drx-HARQ-RTT-TimerSL can be started. For another example, if the PUCCH resource is configured, the sidelink HARQ feedback is sent after the corresponding cell DTX slot offset from the beginning/start of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/executes. drx-HARQ-RTT-TimerSL for the corresponding HARQ process can be started within the first symbol after the end of the corresponding PUCCH transmission. drx-RetransmissionTimerSL for the corresponding HARQ process can be stopped.

For another example, if a PUCCH resource is configured, the PUCCH will not be transmitted after the corresponding cell DTX slot offset from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/runs. When the sidelink HARQ feedback, drx-HARQ-RTT-TimerSL for the corresponding HARQ process can be started within the first symbol after the end of the corresponding PUCCH resource. drx-RetransmissionTimerSL for the corresponding HARQ process can be stopped.

In the case of cell DTX onduration timer execution/active time, when drx-HARQ-RTT-TimerSL expires, drx-RetransmissionTimerUL for the corresponding HARQ process can be started within the first symbol after the drx-HARQ-RTT-TimerSL expires.

In the case of cell DTX offduration timer execution/non-active time, when drx-HARQ-RTT-TimerSL expires, HARQ feedback can be transmitted for the corresponding HARQ process if PUCCH resources are configured even after the drx-HARQ-RTT-TimerSL expires. Therefore, there is no need to monitor the PDCCH. Therefore, you can perform one or more of the following actions:

For example, in the case of a cell DTX onduration timer execution/non-active time, when drx-HARQ-RTT-TimerSL expires, the next/successive cell DTX onduration timer is started/restarted/resumed/executed for the corresponding HARQ process. You can start drx-RetransmissionTimerSL. Or, if drx-HARQ-RTT-TimerSL expires, from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/runs after the drx-HARQ-RTT-TimerSL expires. After the cell DTX slot offset, drx-RetransmissionTimerSL for the corresponding HARQ process can be started. Or, if drx-HARQ-RTT-TimerSL expires, from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/runs after the drx-HARQ-RTT-TimerSL expires. After the cell DTX slot offset, drx-RetransmissionTimerSL for the corresponding HARQ process can be started within the first symbol. Or, in one or more cases: HARQ NACK feedback for the corresponding HARQ process is transmitted on PUCCH, HARQ NACK feedback for the corresponding HARQ process is not transmitted on PUCCH, and PUCCH resources are not configured for sidelink grant drx-HARQ-RTT -drx-RetransmissionTimerSL for the corresponding HARQ process within the first symbol after the corresponding cell DTX slot offset from the beginning/beginning of the subframe in which the next/successive cell DTX onduration timer starts/restarts/resumes/executes after TimerSL expiration. You can start.

Below, the cell/carrier/base station DTX/DRX configuration signaling/notification/instruction method and detailed information are described.

To save network energy and/or reduce terminal power consumption, the base station/CU/DU may provide cell DTX/DRX functions. During cell DTX/DRX, the base station may not transmit/receive any data in that cell. Alternatively, only limited transmission/reception can be maintained. For convenience of explanation, depending on the cell DTX/DRX, the base station turns off random/specific data transmission/reception and/or random/specific reference signal transmission/reception to discontinuously transmit data/reference signals/signals/channels. /Denotation of reception as cell DTX/DRX. In addition, depending on the cell DTX/DRX, the base station turns off random/specific data transmission/reception and/or random/specific reference signal transmission/reception in a cell DTX/DRX non-active (non-active) time/period/duration/interval. -active) Expressed as time/cycle/duration/interval. This is for convenience of explanation and can be expressed as DTX/DRX inactive time/cycle/duration/interval and DTX/DRX off time/cycle/duration/interval. For convenience of explanation, the DTX/DRX functions at the cell level are explained. However, this is for convenience of explanation, and it is obvious that DTX/DRX functions of different granularity that can be provided separately from DTX/DRX are also included in the scope of the present invention. For example, BWP level DTX/DRX functions, cell group level DTX/DRX functions, and base station level DTX/DRX functions are also included in the scope of the present invention.

The base station can notify/instruct the terminal of the cell DTX/DRX configuration through RRC signaling (e.g. System information, RRC reconfiguration message, RRC resume message, RRC setup message, paging message). And/or it can be activated/deactivated through arbitrary L1/L2 signaling (e.g. UE-specific PDCCH, group-common PDCCH, MAC CE).

For example, the base station may broadcast cell DTX/DRX configuration through corresponding system information. The base station can indicate addition/modification of cell DTX/DRX configuration using a Short Message transmitted on PDCCH using P-RNTI with or without an associated paging message. As an example, bit 1 (systemInfoModification) can be used in the Short Message field in DCI format 1_0 to instruct the connected terminal to receive and apply the corresponding configuration. As another example, in the Short Message field within DCI format 1_0, a bit that can indicate the addition/modification of the cell DTX/DRX configuration, which is distinct from bit 1 (systemInfoModification), is defined to instruct the connected terminal to receive and apply the corresponding configuration. You can. For another example, for a terminal supporting the cell DTX/DRX function, depending on the state of the terminal, an RRC reconfiguration message is sent for a terminal in the RRC connected state, an RRC resume message is sent when an RRC inactive terminal transitions to the connected state, and an RRC idle terminal is sent. When transitioning to the connected state, this can be indicated through the RRC setup message.

Cell DTX/DRX configuration can be configured/instructed by dividing into cell DTX mode and cell DRX mode. For example, the cell DTX configuration for downlink transmission/reception of the base station/UE and the cell DRX configuration for uplink transmission of the terminal may be configured independently. Alternatively, the cell DTX mode and cell DRX mode can be configured/directed in combination/connection. Cell DTX/DRX configuration includes one or more of the following parameters: DTX/DRX cycle/period, start slot/offset, onduration/active time, onduration/active time timer, offduration/nonactive time, and nonactive/offduration timer. can do. When cell DTX/DRX are configured by combining/connecting, one or more parameters included in the cell DTX configuration and cell DRX configuration may be set to the same value.

One or more (plural) DTX/DRX configurations may be indicated/configured in the terminal. Index information to distinguish the corresponding DTX/DRX configuration may be included. The base station sends L3 (RRC message)/L2 (MAC CE)/L1 (DCI) signaling to add/modify/change/activate/deactivate the corresponding DTX/DRX configuration. Index to distinguish the corresponding DTX/DRX configuration, corresponding cell The indication may include one or more of the indexes (e.g. serving cell index or SCell index) for distinguishing cells to which DTX/DRX is applied. The terminal may instruct the base station to confirm the above-described L3 (RRC message)/L2 (MAC CE)/L1 (DCI) signaling. L3 (RRC message)/L2 (MAC CE)/L1 (UCI) signaling to indicate the confirmation is an index to distinguish the DTX/DRX configuration of the cell, and an index to distinguish the cell to which DTX/DRX is applied. The instructions may include one or more of the following:

For example, the base station transmits group/cell common L1/L2 signaling (e.g. group-common PDCCH, cell-common PDCCH, PDCCH/PDSCH scrambled by group common or cell common RNTI, group common or cell common RNTI). Activation/deactivation of cell DTX/DRX can be indicated through MAC CE indicated by the PDSCH scrambled by. The terminal(s) connected to the corresponding cell can instruct the base station to confirm receipt of the signaling. Through this, the base station can effectively perform retransmission for the terminal(s) that did not receive the corresponding signaling. Confirmation signaling for the corresponding signaling may be indicated to the base station through one of PUCCH/UCI/HARQ feedback/MAC-CE. The timing for the corresponding confirmation signaling may be dynamically indicated through DCI or provided semi-statically within the RRC configuration. When L1/L2 signaling indicating activation/deactivation of cell DTX/DRX is not received, the base station sends group/cell common L1/L2 signaling or UE-specific L1/L2 signaling (e.g. UE-specific PDCCH, C- The corresponding L1/L2 signaling information can be retransmitted through MAC CE indicated by the PDSCH scrambled by the RNTI.

Depending on the operator's decision/selection/setting, a terminal that supports the cell DTX/DRX function can distinguish the cell DTX/DRX mode and flexibly transmit/receive data discontinuously.

For example, one or more cell DTX/DRX modes may be defined. The network provides information (e.g. index) to distinguish/identify the cell DTX/DRX mode, information to distinguish channels/signals/scheduling associated with the cell DTX/DRX, and channels/signals/scheduling associated with the cell DTX/DRX. One or more pieces of scheduling configuration information can be instructed to the terminal. The corresponding cell DTX/DRX mode may include one or more of the following:

- DTX/DRX mode 1: During the cell DTX/DRX non-active time/duration/period, the base station transmits data traffic (e.g. user plane data (DTCH, MTCH), control plane data (DCCH, MCCH), DL-SCH, UL -SCH, one or more of PDCCH, PDSCH for data traffic scheduling, PUCCH, and PUSCH for data traffic transmission confirmation) and all transmission and reception for reference signals (turn off all transmission and reception for data traffic and reference signal) during Cell DTX / DRX non-active time/durations/periods)

- DTX/DRX mode 2: During Cell DTX/DRX non-active time/duration/period, the base station does not transmit/receive only data traffic (turn off its transmission / reception only for data traffic during Cell DTX / DRX non-active) time/durations/periods, i.e. gNB will still transmit / receive reference signals)

- DTX/DRX mode 3: The base station does not dynamically transmit/receive during Cell DTX/DRX non-active time/durations/. periods, i.e. gNB is expected to still perform transmission/reception in periodic resources, including SPS, CG-PUSCH, SR, RACH, and SRS)

- DTX/DRX Mode 4: During cell DTX/DRX non-active time/duration/period, the base station transmits only random/specific reference signals (e.g. CSI-RS for measurement)

- DTX mode 1: During the cell DTX non-active period, the base station does not transmit any data traffic and reference signals.

- DTX mode 2: The base station does not transmit only for data traffic during Cell DTX non-active periods (turn off its transmission only for data traffic during Cell DTX non-active periods, i.e. gNB will still transmit / receive reference signals)

- DTX mode 3: The base station does not dynamically transmit during Cell DTX non-active periods (to turn off its dynamic transmission during Cell DTX non-active periods, i.e. gNB is expected to still perform transmission/reception in periodic resources, including SPS , CG-PUSCH, SR, RACH, and SRS)

- DTX Mode 4: During the cell DTX non-active period, the base station transmits only random/specific reference signals (e.g. CSI-RS for measurement)

The terminal can operate by distinguishing/considering the corresponding DTX/DRX mode based on the indicated/received information. For example, when cell DTX/DRX mode 1 is configured, the terminal stops/skips one or more operations among PDCCH monitoring, CSI measurement, beam management, and RRM measurement in the corresponding cell during the corresponding DTX offduration/non-active time. /Cannot be performed. Or, when cell DTX/DRX mode 1 is configured, the terminal suspends/skips/cancel/release/discard/configuration/instruction/received uplink grant (e.g. configured grant)/RACH during the corresponding DTX offduration/non-active time. Ignored/Not sent/Considering the resource as invalid/Considering the occurrence as invalid. When the DTX/DRX configuration is indicated, the UE configures the CG-PUSCH, SR, RACH, and SRS, CSI-RS, and measurement configurations of the corresponding cell when they overlap with the DTX/DRX offduration/non-active time of the relevant cell. Override/Suspend/Skip/Cancel/Release/Discard/Ignore/Not Transmit/Applicable to CG-PUSCH, SR, RACH, and SRS, CSI-RS, and operation according to measurement configuration during DTX/DRX offduration/non-active time You can consider the resource as invalid/the occurrence as invalid. The terminal may consider the DTX/DRX offduration/non-active time of the corresponding cell first.

For another example, when cell DTX/DRX mode 2/3/4 is configured, the terminal may stop/skip/not perform PDCCH monitoring. The UE can perform CG-PUSCH, SR, RACH, and SRS transmission. When the DTX/DRX configuration is indicated, the UE configures CG-PUSCH, SR, RACH, and SRS, CSI-RS, and measurement configuration overlaps with the DTX/DRX offduration/non-active time of the relevant cell. , SR, RACH, and SRS, CSI-RS, operations according to the measurement configuration can be performed with priority. The DTX/DRX offduration/non-active time of the cell can be overridden/ignored in the operation orchestration according to the corresponding CG-PUSCH, SR, RACH, and SRS, CSI-RS, measurement configuration.

For another example, cell DTX/DRX configuration is a physical channel (e.g. PDCCH, dynamic grant PDSCH, configured grant PDSCH, PBCH, PUCCH, dynamic grant PUSCH, configured grant PUSCH, PRACH)/transmission channel (e.g. BCH, DL-SCH, PCH, UL-SCH, RACH)/logical channel (e.g. BCCH, PCCH, CCCH, DCCH, DTCH) and/ Alternatively, it may include one or more information among information for indicating a signal (e.g. SSB, DMRS, SRS, PT-RS, etc.) and configuration information for the corresponding channel and/or signal.

For another example, cell DTX/DRX configuration is a physical channel (e.g. PDCCH, dynamic grant PDSCH, configured) where transmission/reception is restricted/prohibited/unavailable/unsupported during the cell DTX/DRX offduration/non-active time. grant PDSCH, PBCH, PUCCH, dynamic grant PUSCH, configured grant PUSCH, PRACH)/logical channels (e.g. BCCH, PCCH, CCCH, DCCH, DTCH) and/or signals (e.g. SSB, DMRS, SRS, PT-RS, etc. ) may include one or more of information for indicating, and configuration information for the corresponding channel and/or signal.

For another example, cell DTX/DRX configuration is a physical channel (e.g. PDCCH, dynamic grant PDSCH, configured grant PDSCH, PBCH) that is allowed/possible/available/supported for transmission/reception in the corresponding cell DTX/DRX onduration/active time. , PUCCH, dynamic grant PUSCH, configured grant PUSCH, PRACH)/indicating logical channels (e.g. BCCH, PCCH, CCCH, DCCH, DTCH) and/or signals (e.g. SSB, DMRS, SRS, PT-RS, etc.) It may include one or more of the following information, configuration information for the corresponding channel and/or signal.

For another example, cell DTX/DRX configuration is a physical channel (e.g. PDCCH, dynamic grant PDSCH, configured grant) on which transmission/reception is restricted/prohibited/unavailable/unsupported in the corresponding cell DTX/DRX onduration/active time. PDSCH, PBCH, PUCCH, dynamic grant PUSCH, configured grant PUSCH, PRACH)/logical channels (e.g. BCCH, PCCH, CCCH, DCCH, DTCH) and/or signals (e.g. SSB, DMRS, SRS, PT-RS, etc.) It may include one or more of information for indicating and configuration information for the corresponding channel and/or signal.

For another example, only one cell DTX/DRX mode may be defined and used. The network can allow terminals that support the corresponding function to operate in accordance with the corresponding function without the need to indicate the cell DTX/DRX mode to the terminal.

<General devices to which this specification can be applied>

Hereinafter, a device to which this specification can be applied will be described.

Figure 3 shows a block diagram of a processor on which the disclosure of the present specification is implemented.

As can be seen with reference to FIG. 3, the processor 1020 on which the disclosure of the present disclosure is implemented includes a plurality of circuitry to implement the proposed functions, procedures and/or methods described herein. can do. For example, the processor 1020 may include a first circuit 1020-1, a second circuit 1020-2, and a third circuit 1020-3.

Additionally, although not shown, the processor 1020 may include more circuits. Each circuit may include a plurality of transistors.

The processor 1020 may be called an application-specific integrated circuit (ASIC) or an application processor (AP), and includes at least one of a digital signal processor (DSP), a central processing unit (CPU), and a graphics processing unit (GPU). can do.

Figure 4 shows a wireless communication device according to an embodiment of the present specification.

Referring to FIG. 4, a wireless communication system may include a first device 100a and a second device 100b.

The first device 100a includes a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, and a drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, pin It may be a tech device (or financial device), security device, climate/environment device, device related to 5G service, or other device related to the 4th Industrial Revolution field.

The second device 100b is a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, a connected car, and a drone (Unmanned Aerial Vehicle, UAV), AI (Artificial Intelligence) module, robot, AR (Augmented Reality) device, VR (Virtual Reality) device, MR (Mixed Reality) device, hologram device, public safety device, MTC device, IoT device, medical device, pin It may be a tech device (or financial device), security device, climate/environment device, device related to 5G service, or other device related to the 4th Industrial Revolution field.

The first device 100a may include at least one processor such as the processor 1020a, at least one memory such as the memory 1010a, and at least one transceiver such as the transceiver 1031a. The processor 1020a may perform the functions, procedures, and/or methods described above. The processor 1020a may perform one or more protocols. For example, the processor 1020a may perform one or more layers of a wireless interface protocol. The memory 1010a is connected to the processor 1020a and can store various types of information and/or instructions. The transceiver 1031a is connected to the processor 1020a and can be controlled to transmit and receive wireless signals.

The second device 100b may include at least one processor such as the processor 1020b, at least one memory device such as the memory 1010b, and at least one transceiver such as the transceiver 1031b. The processor 1020b may perform the functions, procedures, and/or methods described above. The processor 1020b may implement one or more protocols. For example, the processor 1020b may implement one or more layers of a wireless interface protocol. The memory 1010b is connected to the processor 1020b and can store various types of information and/or commands. The transceiver 1031b is connected to the processor 1020b and can be controlled to transmit and receive wireless signals.

The memory 1010a and/or the memory 1010b may be connected to each other inside or outside the processor 1020a and/or the processor 1020b, and may be connected to other processors through various technologies such as wired or wireless connection. It may also be connected to .

The first device 100a and/or the second device 100b may have one or more antennas. For example, antenna 1036a and/or antenna 1036b may be configured to transmit and receive wireless signals.

Figure 5 illustrates a block diagram of a communication device according to an embodiment of the present specification.

In particular, Figure 5 is a diagram illustrating the terminal of Figure 4 in more detail.

The terminal includes a memory 1010, a processor 1020, a transceiver 1031, a power management module 1091, a battery 1092, a display 1041, an input unit 1053, a speaker 1042, and a microphone 1052, Includes a subscriber identification module (SIM) card and one or more antennas.

Processor 1020 may be configured to implement the suggested functions, procedures and/or methods described herein. Layers of the air interface protocol may be implemented in processor 1020. Processor 1020 may include an application-specific integrated circuit (ASIC), other chipset, logic circuit, and/or data processing device. The processor 1020 may be an application processor (AP). The processor 1020 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of processors 1020 include SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL® It may be an ATOMTM series processor manufactured by or a corresponding next-generation processor.

The power management module 1091 manages power for the processor 1020 and/or the transceiver 1031. Battery 1092 supplies power to power management module 1091. The display 1041 outputs the results processed by the processor 1020. Input unit 1053 receives input to be used by processor 1020. The input unit 1053 may be displayed on the display 1041. A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) and its associated keys, which are used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers. You can also store contact information on many SIM cards.

The memory 1010 is operably coupled to the processor 1020 and stores various information for operating the processor 610. Memory 1010 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. When an embodiment is implemented as software, the techniques described herein may be implemented as modules (eg, procedures, functions, etc.) that perform the functions described herein. Modules may be stored in memory 1010 and executed by processor 1020. The memory 1010 may be implemented inside the processor 1020. Alternatively, the memory 1010 may be implemented external to the processor 1020 and may be communicatively connected to the processor 1020 through various means known in the art.

The transceiver 1031 is operably coupled to the processor 1020 and transmits and/or receives wireless signals. The transceiver unit 1031 includes a transmitter and a receiver. The transceiver 1031 may include a baseband circuit for processing radio frequency signals. The transceiver controls one or more antennas to transmit and/or receive wireless signals. The processor 1020 transmits command information to the transceiver 1031 to initiate communication, for example, to transmit a wireless signal constituting voice communication data. The antenna functions to transmit and receive wireless signals. When receiving a wireless signal, the transceiver 1031 may transfer the signal and convert the signal to baseband for processing by the processor 1020. The processed signal may be converted into audible or readable information output through the speaker 1042.

The speaker 1042 outputs sound-related results processed by the processor 1020. Microphone 1052 receives sound-related input to be used by processor 1020.

The user inputs command information such as a phone number, for example, by pressing (or touching) a button on the input unit 1053 or by voice activation using the microphone 1052.

The processor 1020 receives this command information and processes it to perform appropriate functions, such as calling a phone number. Operational data can be extracted from the SIM card or memory 1010.

Additionally, the processor 1020 may display command information or driving information on the display 1041 for the user's recognition and convenience.

The examples of the present disclosure posted in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. In addition to the examples posted here, it is obvious to those skilled in the art that other modifications based on the technical idea of the invention can be implemented.

Claims (2)

In a terminal operation method in a wireless communication system,
Receiving information associated with discontinuous transmission (DTX) of the cell; and
A method comprising not performing monitoring of a physical downlink control channel (PDCCH) after receiving information associated with discontinuous transmission of the cell. According to clause 1,
Not performing monitoring of the physical downlink control channel is characterized in that discontinuous transmission of the cell is during off-duration and/or non-active time.