Method and apparatus for DRX adaptation

Adaptive DRX operation based on terminal predictions optimizes power efficiency and resource utilization by aligning DRX active intervals with traffic patterns, addressing inefficiencies in conventional DRX control methods.

WO2026235458A1PCT designated stage Publication Date: 2026-11-12LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

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

AI Technical Summary

Technical Problem

Conventional DRX control methods in mobile communication systems fail to align active time with actual traffic occurrence, leading to unnecessary power consumption and inefficient resource utilization, particularly in environments with periodic and jittery traffic patterns.

Method used

Adaptive DRX operation is implemented by terminals based on predicted time points for UL data transmission or DL data arrival, allowing for autonomous adjustment of DRX timers and cycles to optimize power efficiency and resource utilization.

Benefits of technology

This approach reduces unnecessary PDCCH monitoring, minimizes power consumption, and enhances communication performance by aligning DRX active intervals with actual traffic patterns, even in irregular periodic environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096565_12112026_PF_FP_ABST
    Figure KR2026096565_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving a discontinuous reception (DRX) configuration including i) information about a DRX timer and ii) information about a DRX cycle; and transmitting preference information related to the DRX configuration. An active time includes a time during which the DRX timer is running. The DRX timer includes a first DRX timer that starts based on a beginning of the DRX cycle. The preference information is related to i) the DRX cycle and / or ii) adjustment of the DRX timer. The preference information is determined on the basis of a time point predicted by a terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for DRX adaptation

[0001] This specification relates to a method and apparatus for DRX adaptation.

[0002] Mobile communication systems were developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include data services as well as voice. Currently, due to the explosive increase in traffic leading to resource shortages and users demanding higher-speed services, more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems largely include the ability to accommodate explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, such as dual connectivity, massive multiple input multiple output (MMIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] Meanwhile, the terminal operating according to the DRX settings performs PDCCH monitoring only during the active time. For example, the active time includes the time when the DRX timer is running.

[0005] According to the existing DRX configuration described above, active time and inactive time are repeated according to a fixed DRX cycle to reduce the power consumption of the terminal. However, the existing method has limitations in that it does not sufficiently reflect the timing of actual traffic occurrence or temporal characteristics.

[0006] Specifically, the existing method assumes the following operation. DRX settings are primarily determined by the network, and terminals report limited assistance information, such as battery status or data reception status. Consequently, precise DRX control that takes into account the periodicity and jitter characteristics of UL or DL ​​traffic generated by individual terminals is difficult. This may lead to the following problems.

[0007] For example, if the active time is not aligned with the actual arrival or transmission time of the next packet, the terminal may perform PDCCH monitoring for longer than necessary, resulting in unnecessary power consumption. For instance, the occurrence of UL data during inactivity requires an immediate wake-up operation, which hinders the power savings expected from DRX. Furthermore, in traffic environments that are periodic and jittery, the negative effects resulting from the aforementioned problems may be exacerbated. As described above, conventional DRX control methods find it difficult to guarantee optimal operation in terms of power efficiency and resource utilization.

[0008] The purpose of this specification is to propose a method for solving the aforementioned problems.

[0009] The technical problems to be solved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0010] A method according to one embodiment of the present specification for solving the above-described problem comprises the steps of receiving a DRX setting including i) information about a DRX (Discontinuous Reception) timer and ii) information about a DRX cycle, and transmitting preference information related to the DRX setting. The active time includes the time during which the DRX timer is running. The DRX timer includes a first DRX timer that starts based on the beginning of the DRX cycle. The preference information relates to i) the DRX cycle and / or ii) the adjustment of the DRX timer. The preference information is characterized by being determined based on a time predicted by a terminal.

[0011] Therefore, even in a periodic traffic environment containing jitter, DRX operation can be improved in terms of power efficiency and resource utilization compared to existing DRX operation.

[0012] According to an embodiment of the present specification, by adaptively adjusting the DRX active interval based on a time point predicted by the terminal (e.g., UL data transmission time / DL data arrival time), the power consumption of the terminal due to unnecessary PDCCH monitoring can be effectively reduced.

[0013] In addition, the terminal can directly derive optimal DRX timer information or autonomously control the period to prevent frequent wake-up phenomena and increase the efficiency of DRX operation. Through this, power efficiency improvement and data transmission / reception delay minimization can be achieved simultaneously, thereby providing more stable and optimized communication performance even in an environment of irregular periodic traffic.

[0014] The effects obtainable in this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which this specification belongs from the description below.

[0015] Figure 1 is a diagram illustrating the overall functions from the perspective of an AI / ML model.

[0016] Figure 2 illustrates a general form of an AI / ML-related procedure performed between a network and a terminal.

[0017] Figure 3 is a diagram illustrating network-driven AI / ML management based on network decisions.

[0018] Figure 4 is a diagram illustrating terminal-driven AI / ML management based on network decisions.

[0019] Figure 5 is an example of an AI / ML management procedure based on terminal decisions.

[0020] Figure 6 is another example of an AI / ML management procedure based on terminal decisions.

[0021] Figure 7 is a diagram illustrating terminal operation according to DRX settings.

[0022] FIG. 8 is an example of DRX cycle adjustment according to one embodiment of the present specification.

[0023] FIG. 9 is another example of DRX cycle adjustment according to one embodiment of the present specification.

[0024] FIG. 10 is a flowchart illustrating a method according to one embodiment of the present specification.

[0025] FIG. 11 is a flowchart illustrating a method according to another embodiment of the present specification.

[0026] FIG. 12 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0027] In this specification, "A or B" may mean "only A," "only B," or "both A and B." Alternatively, in this specification, "A or B" may be interpreted as "A and / or B." For example, in this specification, "A, B or C" may mean "only A," "only B," "only C," or "any combination of A, B and C."

[0028] A slash ( / ) or a comma used in this specification may mean "and / or." For example, "A / B" may mean "A and / or B." Accordingly, "A / B" may mean "only A," "only B," or "both A and B." For example, "A, B, C" may mean "A, B or C."

[0029] In this specification, "at least one of A and B" may mean "only A," "only B," or "both A and B." Additionally, in this specification, the expressions "at least one of A or B" or "at least one of A and / or B" may be interpreted as synonymous with "at least one of A and B."

[0030] Additionally, in this specification, "at least one of A, B and C" may mean "only A," "only B," "only C," or "any combination of A, B and C." Also, "at least one of A, B or C" or "at least one of A, B and / or C" may mean "at least one of A, B and C."

[0031] Additionally, parentheses used in this specification may mean "for example." Specifically, when indicated as "control information (PDCCH)," "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)," "PDCCH" may be proposed as an example of "control information."

[0032] In the following explanation, 'when, if, in case of' can be replaced with 'based on'.

[0033] Technical features described individually within a single drawing in this specification may be implemented individually or simultaneously.

[0034] Hereinafter, preferred embodiments according to the present specification will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present specification and is not intended to represent the only embodiment in which the present specification may be practiced. The following detailed description includes specific details to provide a complete understanding of the present specification.

[0035] In this specification, a terminal is a user-side device (user equipment, UE) or a consumer-side device, and may also be referred to as a first node that receives / transmits signals from / to a base station / second node / IAB node / Transmission-Reception Point (TRP). A terminal may correspond to a physical node or a logical node. A terminal may correspond to a user-side endpoint or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a terminal may correspond to a served node. A terminal may be a fixed-location node or a non-fixed-location (or mobile) node.

[0036] In this specification, a Base Station (BS) is a device on the network side and may also be referred to as a second node / IAB node / x-NodeB (x-NodeB, where x may be an abbreviation related to Radio Access Technology (RAT)) / Transmission-Reception Point (TRP). A Base Station may correspond to a physical node or a logical node. A Base Station may correspond to an endpoint on the network side or an intermediate point between other endpoints. In communication between two points not limited to endpoints (including one-to-one / many-to-one / one-to-many / many-to-many communication), a Base Station may correspond to a serving node. A Base Station may be a node with a fixed location or a node with an indefinite location.

[0037] In this specification, higher layer parameters may be set for the terminal, pre-set, or pre-defined. For example, a base station may transmit higher layer parameters to the terminal. For example, the terminal may transmit parameters such as capability to the base station as higher layer parameters. For example, higher layer parameters may be transmitted via RRC (radio resource control) signaling or MAC (medium access control) signaling.

[0038] In this specification, information / state / parameters being "configured" or "pre-configured" may be interpreted as the information / state / parameters being provided / pre-provided to the terminal through pre-defined signaling (e.g., SIB, MAC, RRC) from the base station. In this specification, information / state / parameters being "defined" or "pre-defined" may be interpreted as being known or stored in advance by the base station and the terminal without signaling between the base station and the terminal.

[0039] < AI / ML for Wireless Communication >

[0040] With the advancement of computing technology, artificial intelligence (AI) and machine learning (ML) are being adopted across various industries and technological fields. In the field of wireless communication, various discussions are underway regarding the application of AI models trained on ML; notably, the 3GPP standardization process refers to this as AI / ML. In this specification, we use the term "AI / ML" following the terminology currently in use during the 3GPP standardization discussions; however, "AI / ML" may be referred to by various other terms depending on the progress of standardization and implementation in the future. For example, it may be referred to as a "transmission / reception mode" or a "signal / channel / operation / transmission / reception configuration" set for AI / ML, but is not limited thereto. The meanings of the terms currently used in the 3GPP standardization process are briefly summarized as follows.

[0041] - AI / ML Model: Refers to a data-driven algorithm that applies AI / ML technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.

[0042] - Data collection: This is the process of collecting data necessary for AI / ML model training, data analysis, and inference from network nodes, management entities, or terminals.

[0043] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.

[0044] - AI / ML Inference: This is the process of making predictions or deriving decisions based on collected data and AI models using trained AI models. Meanwhile, depending on whether the AI / ML model is configured on both the transmitting and receiving devices or on only one, it can be classified into (i) two-sided models and (ii) one-sided models. In the case of (i) two-sided models, cooperative inference is performed through paired AI / ML models. Cooperative inference refers to cooperation between the network and the UE, where one side performs part of the inference and the other performs the remainder. (ii) One-sided models are divided into UE-side models and network-side models. In the case of one-sided models, inference is performed entirely by the UE / network-side models.

[0045] 1. Life Cycle Management (LCM) for AI / ML models

[0046] For AI / ML models, LCM is a concept that encompasses all overall procedures for the model, such as data collection, model training, model deployment, model inference, model monitoring, and model updates.

[0047] Figure 1 is a diagram illustrating the overall functions from the perspective of an AI / ML model.

[0048] Referring to FIG. 1, a general AI / ML functional framework can be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).

[0049] The Data Collection function (10) is a function that provides input data to the Model Training function (20), Management function (30), and Inference function (40). The Data Collection function (10) performs data preparation and can provide input data processed through data preparation.

[0050] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).

[0051] The Model Training function (20) is a function that performs AI / ML model training, validation, and testing, and can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the Model Training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the Training Data (11) delivered from the Data Collection function (10).

[0052] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).

[0053] The Management function (30) is a function that monitors the operation of an AI / ML model or an AI / ML function.

[0054] Management Instruction (32) is information required as input to manage the Inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).

[0055] A Model Transfer / Delivery Request (33) can be used to request model(s) from Model Storage (50).

[0056] Performance Feedback / Retraining Request (31) refers to information required as input to Model Training function (20) (e.g., for the purpose of retraining or updating the model).

[0057] The inference function (40) is a function that provides output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). If necessary, the inference function (40) may also perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the inference data (13) provided by the data collection function (10).

[0058] Inference Output (41) is data used in the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.

[0059] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40).

[0060] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.

[0061] 2. General AI / ML related procedures between the network and the terminal

[0062] Figure 2 illustrates the general form of AI / ML-related procedures performed between a network and a terminal. While Figure 1 examined the LCM from the perspective of an AI / ML model, Figure 2 describes the general form of procedures performed between a terminal and a network from the perspective of signaling / protocols.

[0063] (1) AI / ML related setup procedure

[0064] Referring to FIG. 2, an AI / ML-related configuration procedure may be performed between the network and the terminal (B05). The AI / ML-related configuration procedure may include information exchange through at least one upper-layer signaling between the terminal and the network, and / or prior preparation / subsequent operations at the terminal / network respectively before / after the upper-layer signaling.

[0065] Specifically, the configuration procedure related to AI / ML may include, but is not limited to, at least one of the following: (i) reporting the capability of the AI / ML-related terminal, (ii) data collection, (iii) model training, (iv) model delivery / transmission, (v) selection of AI / ML functions / models, and (vi) configuration of various operations performed based on the AI / ML model (e.g., AI / ML-based CSI / Positioning / Beam Management).

[0066] (i) The terminal can inform the network of its capabilities, such as models and functions related to AI / ML, that it supports through UE Capability reporting. The network can provide AI / ML-related settings to the terminal based on the terminal's capabilities related to AI / ML reported by the terminal.

[0067] (ii) AI / ML-related configuration procedures may include data collection related to the training / inference of AI / ML models and / or the provision of configuration information regarding data collection. The configuration information regarding data collection may relate to how to configure the method / operation of data collection.

[0068] (iii) AI / ML-related configuration procedures may include training AI / ML models online or offline and / or providing configuration information for AI / ML model training. The configuration information for AI / ML model training may relate to how to configure the method / behavior, etc., of training the AI / ML model.

[0069] (iv) AI / ML-related configuration procedures may include transmitting / transmitting configuration information for a model. The configuration information for a model may include parameters that constitute the AI / ML model and / or an identifier (ID) for the AI / ML model.

[0070] The provided AI / ML model may be a model trained by the network or a model that requires self-training at the terminal. Even when a model trained by the network is provided, the terminal may perform fine-tuning or retraining as necessary. Meanwhile, if a model trained by the network is provided, the terminal may provide data for training to the network.

[0071] (v) The configuration procedure related to AI / ML may include the configuration of how to select AI / ML Functionality / models and / or the selection process for AI / ML Functionality / models. In UE-side AI / ML models or two-sided AI / ML models, the selection of the UE part may be performed through instructions / signaling from the network or the terminal may select it itself. The selection of AI / ML Functionality / models may be performed when multiple AI / ML Functionality / models are configured / provided.

[0072] (vi) The configuration procedure related to AI / ML may include configuration information for various inference operations performed based on AI / ML models, e.g., AI / ML-based CSI measurement / reporting, AI / ML-based positioning, and / or AI / ML-based beam management.

[0073] (2) Operation based on inference by AI / ML models

[0074] Referring again to FIG. 2, the network and / or terminal can perform inference of the AI / ML model through the trained AI / ML model and perform various operations based on the inference of the AI / ML model (B10). If the AI / ML model is a one-sided model, the inference of the AI / ML model can be performed at either the network or the terminal where the AI / ML model is configured. If the AI / ML model is a two-sided model, each part of the inference of the AI / ML model can be performed at the network and the terminal, and depending on the implementation, such inference can be performed cooperatively between the network and the terminal.

[0075] (i) Actions performed based on the inference of an AI / ML model may include AI / ML-based CSI measurement / reporting. AI / ML-based CSI measurement / reporting is intended to improve CSI feedback and may be related to overhead reduction / CSI compression, accuracy improvement, and / or CSI prediction.

[0076] (ii) Actions performed based on the inference of an AI / ML model may include AI / ML-based beam management. AI / ML-based beam management may be related to beam prediction in the time domain, reduction of overhead / latency in the spatial domain, and / or improvement of beam selection accuracy.

[0077] (iii) Actions performed based on the inference of an AI / ML model may include AI / ML-based positioning. AI / ML-based positioning may be relevant to improving positioning accuracy in various scenarios, for example, in non-line-of-sight environments.

[0078] (3) Procedures for AI / ML management

[0079] The network and / or terminal can perform procedures for the management of AI / ML Functionality / model or the settings therefor (B15).

[0080] The network and / or terminal may perform monitoring of AI / ML Functionality / model during the AI / ML model inference or operation based thereon (B10) for the management procedure (B15).

[0081] The management procedure may include, for example, at least one of activation / deactivation, switching, model update, and / or fallback operation for AI / ML Functionality / model. For the signaling of the management procedure, various 3GPP signaling schemes, such as RRC, MAC-CE, DCI, etc., may be used.

[0082] As an example of model switching, multiple model groups are configured, and switching between them can be performed based on models having a common model structure or partially common substructures, and models within the same group may be associated with different input / output formats or processing.

[0083] Model updating involves modifying the parameters used by the model to suit channel conditions that change over time, and fine-tuning is an example of model updating.

[0084] Fallback: In a wireless communication system using an AI / ML model, this may refer to the operation of not using the AI / ML model or operating in a pre-configured / defined default mode when the reliability of the AI / ML model decreases due to internal or external environmental factors.

[0085] For example, the decision on whether to perform a management procedure can be made by the network. For instance, the network may decide to perform the management procedure upon network initiation, or the network may decide to perform the management procedure upon terminal initiation and request.

[0086] As another example, the decision on whether to perform a management procedure can be made by the terminal. For instance, the terminal's decision on the management procedure may be triggered when an event condition set by the network is satisfied, performed by reporting the terminal's decision to the network, or performed autonomously by the terminal.

[0087] 7.2 Protocol Aspects

[0088] In this section, considering the use case and RAN1 input, aspects related to life cycle management signaling procedures, model identification, data collection, model transfer / delivery, UE capability reporting, and applicability-related reporting are reviewed.

[0089] 7.2.1 Common Framework

[0090] 7.2.1.1 Signaling procedures for model and function life cycle management

[0091] Based on the functional framework, this section exemplifies signaling procedures for different scenarios for model-ID-based management and / or functionality-based management. Such procedures may be considered for at least UE-side models. These procedures may include scenarios where management decisions are made by the network or by the UE. In the case of network-side decisions, they may be network-initiated or UE-initiated and requested by the network. On the other hand, in the case of UE-side decisions, they may be event-triggered as configured by the network and the UE's decision may be reported to the network, or UE-autonomous, and the UE's decision may or may not be reported to the network.

[0092] Note: Mapping these scenarios to specific use cases can be left to RAN1.

[0093] Note: The scenarios discussed below do not imply support for all potential functionality and / or model management instructions (e.g., (de)activation, selection, switching, fallback, etc.) for all use cases.

[0094] Note: In FIGS. 3 through 6, the Management Request, Management Instruction, and Management Decision Report may include detailed information regarding the selection, (de)activation, transition, or fallback of a model or function.

[0095] Figure 3 is a diagram illustrating network-driven AI / ML management based on network decisions.

[0096] Specifically, Fig. 3 illustrates a case where an LCM decision is taken and initiated by a network (Network decision, network-initiated AI / ML management).

[0097] Management instructions can be the result of model / functionality performance monitoring in the network.

[0098] Management instructions may include information regarding the model or functionality.

[0099] Figure 4 is a diagram illustrating terminal-driven AI / ML management based on network decisions.

[0100] Specifically, Fig. 4 illustrates a case where the LCM decision is taken by the network but the request is initiated by the UE (Network decision, UE-initiated AI / ML management).

[0101] A management request can be the result of model / functionality monitoring in the UE.

[0102] In response to a management request, the network can send a management instruction to the UE.

[0103] A Management Request may include information regarding a model or functionality.

[0104] The network can accept or reject management requests from the UE.

[0105] A Management Request may include information related to model / functionality performance metrics.

[0106] Management instructions may include information regarding the model or functionality.

[0107] Figure 5 is an example of an AI / ML management procedure based on terminal decisions.

[0108] Specifically, FIG. 5 illustrates a case (UE decision, event-triggered as configured by the network) in which an LCM decision is taken by the UE according to a prior network configuration.

[0109] For management in the UE (e.g., event-triggered AI / ML management), use case-specific events / conditions can be configured by the network.

[0110] The UE can transmit a Management Decision Report to the network after management within the UE.

[0111] A Management Decision Report may include information regarding a model or functionality.

[0112] Figure 6 is another example of an AI / ML management procedure based on terminal decisions.

[0113] Specifically, Fig. 6 illustrates a case where an LCM decision can be taken autonomously by the UE (UE autonomous, decision reported to the network).

[0114] The UE can be configured to send the Management Decision Report to the network when performing a model / functionality Management Decision.

[0115] It is UE-autonomous, and UE decisions may not be reported to the network.

[0116] In cases where LCM decisions can be made autonomously by the UE and are not reported to the network, AI / ML management is transparent from a network perspective.

[0117] 7.2.1.2 Model identification and meta information

[0118] According to the functional framework, the model ID can be used within functions and for different data, information, and instruction flows to identify AI / ML models. For example, the model ID can ultimately be associated with model selection, (de)activation, or switching, or linked to "Model Transfer / Delivery" information.

[0119] RAN2 assumes that model IDs can be globally unique, for example, which allows for appropriate model validation and model testing procedures.

[0120] Note: Methods to guarantee model ID uniqueness are outside the RAN2 scope.

[0121] Note: Details of model training, validation, and testing are outside the scope of RAN2.

[0122] Additionally, some meta-information about the models may be necessary to manage or control AI / ML models.

[0123] Note: Details regarding the relationship between model IDs and meta information for model control and management purposes may be covered in the normative phase.

[0124] 7.2.1.3 Data collection

[0125] Data collection plays a crucial role in enabling various use cases. Therefore, it is important to define the optimal approach for collecting data to support UE-side and network-side model inference, monitoring, and training.

[0126] The analysis and selection of data collection frameworks should focus on the RRC CONNECTED state for both data generation and reporting.

[0127] 7.2.1.3.1 Considerations for Network-side Data Collection

[0128] A set of general data collection principles is expected to be considered for network-side model training. This includes the following:

[0129] - The UE must support data logging,

[0130] - UEs will report collected data in periodic, event-based, and on-demand manner,

[0131] UE memory, processing power, energy consumption, and signaling overhead must be considered.

[0132] Note: The above principles may be modified according to RAN1 requirements.

[0133] In addition, the following points are considered in relation to the use cases of this study.

[0134] For CSI and beam management use cases, training of network-side models can consider both gNB-centric and OAM-centric data collection mechanisms. gNB-centric data collection means that the gNB can be configured to allow the UE to initiate or terminate data collection procedures. The potential impact of L3 signaling for reporting collected data must be evaluated.

[0135] Meanwhile, OAM-centric data collection means that the OAM provides the configuration necessary for the UE to initiate / terminate data collection procedures (via gNB). To achieve this, an MDT framework may be considered. The potential impact of MDT on the RRC_CONNECTED state must be evaluated.

[0136] For the positioning use case, when considering LMF-side inference, it is assumed that the LPP protocol should be applied to data collected by the UE and terminated at the LMF, and the NRPPa protocol should be applied to data collected by the gNB and terminated at the LMF. Additionally, for LMF-side performance monitoring, it is assumed that the LPP protocol should be applied to data collected by the UE and terminated at the LMF, and the NRPPa protocol should be applied to data collected by the gNB and terminated at the LMF.

[0137] Note: For gNB- and OAM-centric data collection, it may be necessary to consult with RAN3 and SA5 regarding whether and how OAM should be involved.

[0138] Note: In the case of potential impacts due to positioning use cases, it may be necessary to consult with RAN3 regarding whether NRPPa should be involved and how it should be involved.

[0139] 7.2.1.3.2 Data collection for UE-side model training

[0140] The following proposals were discussed in RAN2:

[0141] 1. The UE collects training data and directly transfers it to an Over-The-Top (OTT) server;

[0142] 1a) OTT (Transparent)

[0143] 1b) OTT (non-transparent)

[0144] 2. The UE collects training data and transfers it to the Core Network. The Core Network transfers the training data to the OTT server.

[0145] 3. The UE collects training data and transfers it to the OAM. The OAM transfers the necessary data to the OTT server.

[0146] RAN2 did not study or analyze these proposals and did not agree on the requirements or recommendations.

[0147] 7.2.1.4 Model transfer / delivery

[0148] It is not clear from the results of this study whether there is a need to consider standardized solutions for transferring / delivering AI / ML model(s). Nevertheless, the following solutions are considered to support AI / ML model transfer / delivery:

[0149] - Solution 1a: gNB can transfer / deliver AI / ML model(s) to UE via RRC signaling.

[0150] - Solution 2a: The Core Network (except LMF) can transfer / deliver AI / ML model(s) to the UE via NAS signaling.

[0151] - Solution 3a: LMF can transfer / deliver AI / ML model(s) to the UE via LPP signaling.

[0152] - Solution 1b: gNB can transfer / deliver AI / ML model(s) to UE via UP data.

[0153] - Solution 2b: Core Network (except LMF) can transfer / deliver AI / ML model(s) to the UE via User Plane (UP) data.

[0154] - Solution 3b: LMF can transfer / deliver AI / ML model(s) to the UE via UP data.

[0155] - Solution 4a: OTT server can transfer / deliver AI / ML model(s) to UE (eg, transparent to 3GPP).

[0156] - Solution 4b: OAM can transfer / deliver AI / ML model(s) to UE.

[0157] Note: The relationship between model transfer / delivery solutions and use cases can be derived from the contents described in Sections 7.3.2, 7.3.3, and 7.3.4.

[0158] To evaluate various model transmission and delivery solutions, the following areas are considered.

[0159] -A1:Large, no upper limit model / model parameter size,

[0160] -A2:Model transfer / delivery continuity (i.e. resume transmission of model (segments) across gNBs),

[0161] -A3:Network controllability on model transfer / delivery (e.g., management decision at gNB),

[0162] -A4:Model transfer / delivery QoS (for DRB) (including latency, etc.) and priority (for SRB).

[0163] For each model transfer / delivery solution, each of the above areas is analyzed with a focus on the current status and gaps and potential impact on RAN specification.

[0164] Reactive and proactive approaches for initiating model transfer / delivery can be considered during the normative phase. In the case of the reactive approach, the AI / ML model is transferred / delivered (i.e. downloaded) to the UE when necessary. This typically occurs due to changes in scenarios, configurations, sites, etc. On the other hand, in the case of the proactive model transfer / delivery approach, the AI / ML model is downloaded to the UE in advance, and the model switch is typically performed due to changes in scenarios, configurations, sites, etc.

[0165] 7.2.1.5 UE capability reporting

[0166] The Legacy UE capability framework functions as a baseline for reporting AI / ML-enabled Features / FGs supported by the UE. Therefore, for CSI and beam management use cases, this information is displayed in the UE AS capability (e.g., UECapabilityEnquiry / UECapabilityInformation) in the RRC. On the other hand, for positioning use cases, this is displayed by the positioning capability defined in the LPP.

[0167] Further discussions regarding UE capability details (e.g., level of detail in Features / FGs, content and structure of related UE capabilities, etc.) may be conducted during the Normative phase.

[0168] 7.2.1.6 Applicability-related information reporting

[0169] AI / ML models for specific use cases may be adapted and applicable to particular scenarios, locations, configurations, deployments, and other factors. In this regard, it is acknowledged that AI / ML models may undergo updates, such as model changes, as an inherent part of their development. Therefore, to ensure efficient network control and management, particularly in relation to UE-side matters, UEs may have the ability to indicate to the network relevant information regarding the AI / ML models and AI / ML functionalities they support. This enables the network to make decisions, for example, regarding the (de)activation or switching of AI / ML functionalities and AI / ML models.

[0170] The aforementioned information can, in principle, be understood as "applicability-related information," where the UE can report to the network, for example, conditions under which a model / functionality is applicable / suitable, or whether the model(s) / functionality(es) are (non)applicable under the current context. However, existing UE capability reporting frameworks cannot be used for this purpose.

[0171] Note: Whether it is necessary to enable UEs to report applicability-related information and how to do so can be further discussed and defined in the normative phase. Mechanisms such as UE Assistance Information can eventually be used as examples.

[0172] Two UE reporting types are identified to convey this additional information:

[0173] - "reactive" reporting, and

[0174] - "proactive" reporting.

[0175] Reactive reporting is a method in which a UE provides information to the network when it receives an action from the network.

[0176] On the other hand, proactive reporting refers to a method in which a UE provides information even without necessarily receiving action from the network. For example, a UE can proactively notify the RAN of updates or changes to the models or features it supports.

[0177] Note: Whether signaling from the network is required for active UE reporting can be discussed during the Normative phase.

[0178] Note: Whether the network needs to report information regarding the applicability of AI / ML models and / or AI / ML functions to the UE may be discussed during the standardization phase.

[0179] 7.2.2 CSI feedback enhancement

[0180] The following objectives were identified for the two-sided CSI compression use case. First, to ensure that the UE and network parts of the models are configured and applied according to their applicable scenarios and configurations. Second, to ensure that the models are properly matched so that the CSI generation part used in the UE corresponds to the CSI reconstruction part used in the gNB. Third, simultaneous (de)activation and switching of the two-sided models are required to allow for seamless operation.

[0181] Regarding the last point mentioned above, in the case of two-sided model CSI compression use cases, the selection, (de)activation, switching, and fallback of AI / ML models or AI / ML functionalities can be initiated by either the UE or the gNB. In this regard, it is important to distinguish various cases and understand the applicability of UE-side models versus network-side models.

[0182] For data collection, model transfer / delivery, and function-to-entity mapping analysis, various scenarios unfold in both two-sided CSI compression use cases and UE-side CSI prediction use cases when the data-generating entity and the endpoint entity are different. For example:

[0183] Model Training:

[0184] Two-sided CSI compression use case: Training data can be generated in the UE or gNB depending on specific requirements, and the endpoints of the training data may include the gNB, OAM, OTT (Over-The-Top) server, or UE.

[0185] Note: RAN2 identified cases where the core network (CN) can be used for model training. However, as this is outside the scope of this working group (WG), no separate research was conducted.

[0186] UE-side CSI prediction use case: Training data can be generated in the UE, and endpoints of the training data may include the UE or a UE-side OTT server.

[0187] Note: RAN2 identified cases where OAM or core networks could be used for UE-side model training. However, as this is outside the scope of this working group, no separate study was conducted.

[0188] Note: RAN2 identified cases where gNB could be used for UE-side model training. However, no conclusion was reached as this depends on the progress of RAN1.

[0189] Inference

[0190] Two-sided CSI Compression Use Case:

[0191] For inference of the network portion of the two-sided model, the UE can generate the necessary input data, and the endpoints of this input data are located within the gNB where the inference process is performed.

[0192] For the inference of the UE portion of the two-sided model, the input data is available within the UE where the inference process is performed.

[0193] UE-side CSI prediction use case:

[0194] For UE-side model inference, input data is available within the UE where the inference process is performed.

[0195] Management

[0196] Two-sided CSI compression use case: Model / function control (e.g., selection, (de)enable, transition, fallback, etc.) is performed by the gNB.

[0197] Note: RAN2 identified cases where control is performed by the UE. However, no conclusion was reached as this depends on the progress of RAN1.

[0198] UE-side CSI prediction use case:

[0199] If monitoring resides within the UE, model / function control can be performed by the UE.

[0200] If monitoring resides within the gNB or UE, model / function control can be performed by the gNB.

[0201] Monitoring:

[0202] The UE monitors the performance of its UE-side models.

[0203] For network-side monitoring of the UE-side model, the UE can generate calculated performance metrics or data required for calculating performance metrics if necessary, and their endpoint is the gNB.

[0204] 7.2.3 Beam management

[0205] In the case of beam management, the selection, (de)enable, transition, and fallback of models or functions can also be initiated by the UE or gNB. To this end, it is important to distinguish various cases and understand the applicability of UE-side and network-side models.

[0206] For data collection, model transmission / delivery, and feature-object mapping analysis, various scenarios unfold when the data-generating object and the endpoint object are different. For example:

[0207] Model Training:

[0208] UE-side model: Training data can be generated in the UE, and endpoints of the training data may include the UE or a UE-side OTT server.

[0209] Note: RAN2 identified cases where OAM or the core network could be used for UE-side model training. However, this was not studied as it is outside the scope of this working group.

[0210] Note: RAN2 identified cases where gNB could be used for UE-side model training. However, no conclusion was reached as this depends on the progress of RAN1.

[0211] gNB-side model: Training data can be generated in the gNB or UE, and endpoints of the training data can include the gNB or OAM.

[0212] Note: RAN2 identified cases where OTT servers and core networks could be used for gNB-side model training. However, this was not studied as it is outside the scope of this working group.

[0213] Inference

[0214] UE-side model inference: Input data is available within the UE where the inference process is performed.

[0215] Network-side model inference: The UE can generate the necessary input data, and the endpoint of this input data is located within the gNB where the inference process is performed.

[0216] Management

[0217] UE-side model: If monitoring resides within the UE, model / function control can be performed by the UE.

[0218] UE-side model: If monitoring resides in the gNB or within the UE, model / function control can be performed by the gNB.

[0219] Monitoring:

[0220] The UE monitors its own UE-side model performance.

[0221] For network-side monitoring of the UE-side model, the UE can generate performance metrics or data, etc., if necessary, and the endpoint is the gNB.

[0222] Network-side model: Monitoring resides within the gNB.

[0223] 7.2.4 Positioning accuracy enhancements

[0224] In the case of positioning (location estimation) use cases, the selection, (de)activation, transition, and fallback of a model or function can be initiated by the UE, gNB, or LMF. To this end, it is important to distinguish various cases and understand the applicability of UE-side and network-side models.

[0225] For data collection, model transmission / delivery, and feature-object mapping analysis, various scenarios unfold when the data-generating object and the endpoint object are different. For example:

[0226] Model Training:

[0227] UE-side model: Training data can be generated in the UE, and endpoints may include the UE or a UE-side OTT server.

[0228] Note: RAN2 identified cases where OAM or a core network is used, but these are outside the scope of the study.

[0229] Note: RAN2 has identified cases where LMF can be used for UE-side model training, but the conclusion is undetermined depending on the progress of RAN1.

[0230] gNB-side model: Training data can be generated from the gNB, and endpoints can include the gNB or OAM.

[0231] Note: RAN2 has identified cases where LMF can be used for training gNB-side models, but the conclusion is undetermined depending on the situation in RAN1.

[0232] LMF-side model: LMF becomes the endpoint of the training data.

[0233] Inference

[0234] UE-side model inference: Input data is available internally within the UE.

[0235] gNB-side model inference: Input data is available within the gNB. In this case, the UE can also generate the necessary input data, and the endpoint of this data is the gNB.

[0236] LMF-side model inference: The UE or gNB can generate the necessary input data, and the endpoint is the LMF.

[0237] Management

[0238] UE-side model: If monitoring is within the UE, the UE can perform control.

[0239] gNB-side model: Model / function control is performed by the gNB.

[0240] LMF-related control: If monitoring resides within the LMF or UE, control can be performed by the LMF.

[0241] Monitoring:

[0242] The UE monitors its own UE-side model performance.

[0243] In the case of gNB-side monitoring, calculated performance indicators or data can be generated by at least the gNB.

[0244] In the case of LMF-side monitoring, the gNB or UE can generate the necessary performance metrics or data, and the endpoint is the LMF.

[0245] 5.7 Discontinuous Reception (DRX)

[0246] A MAC entity may be configured by the RRC for a DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, AI-RNTI, SL-RNTI, SL-CS-RNTI, SL-PRS-RNTI, SL-PRS-CS-RNTI, SL Semi-Persistent Scheduling V-RNTI, and cellDTRX-RNTI. When using the DRX activity, the MAC entity must also monitor the PDCCH in accordance with the requirements found in other clauses of this specification. If DRX is configured in the RRC_CONNECTED state, the MAC entity may monitor PDCCH discontinuously for all active Serving Cells using the DRX behavior specified in this section; otherwise, the MAC entity must monitor PDCCH as specified in TS 38.213 [6].

[0247] Note 1: Void

[0248] RRC controls DRX operation by setting the following parameters:

[0249] drx-onDurationTimer: duration at the beginning of the DRX cycle;

[0250] drx-SlotOffset: delay before starting drx-onDurationTimer;

[0251] drx-InactivityTimer: Duration after a PDCCH indicates a new uplink (UL), downlink (DL), or sidelink (SL) transmission for a MAC entity during a PDCCH occasion;

[0252] drx-RetransmissionTimerDL (per DL HARQ process excluding broadcast processes): maximum duration until downlink retransmission (DL retransmission) is received;

[0253] drx-RetransmissionTimerUL (UL HARQ per process): maximum duration until a grant for uplink retransmission (UL retransmission) is received;

[0254] drx-LongCycleStartOffset: drx-StartOffset defining the subframe where the Long DRX cycle and Long and Short DRX cycles start;

[0255] drx-NonIntegerLongCycleStartOffset (optional): drx-StartOffset that defines the Long DRX cycle and / or the subframe where the Long and Short DRX cycles start, when the length of the Long DRX cycle and / or Short DRX cycle is not an integer;

[0256] drx-ShortCycle (optional): Short DRX cycle;

[0257] drx-NonIntegerShortCycle (optional): Short DRX cycle with a non-integer length;

[0258] drx-ShortCycleTimer (optional): Duration during which the UE must follow the Short DRX cycle;

[0259] drx-HARQ-RTT-TimerDL (per DL HARQ process excluding broadcast processes): minimum duration before a DL assignment for HARQ retransmission is expected by a MAC entity;

[0260] drx-HARQ-RTT-TimerUL (per UL HARQ process): minimum duration before a UL HARQ retransmission grant is expected by a MAC entity;

[0261] drx-RetransmissionTimerSL (per sidelink process): maximum duration until a grant for sidelink retransmission (SL retransmission) is received;

[0262] drx-HARQ-RTT-TimerSL (per sidelink process): minimum duration before a sidelink retransmission grant (SL retransmission grant) is expected;

[0263] drx-LastTransmissionUL (optional): Configuration to start drx-HARQ-RTT-TimerUL after the last transmission in the bundle;

[0264] ps-Wakeup (optional): Configuration to start the associated drx-onDurationTimer when the DCP is monitored but not detected;

[0265] ps-TransmitOtherPeriodicCSI (optional): Configuration to report a non-L1-RSRP periodic CSI (periodic CSI) on PUCCH for the duration indicated by drx-onDurationTimer when DCP is configured but the associated drx-onDurationTimer has not started;

[0266] ps-TransmitPeriodicL1-RSRP (optional): A configuration for transmitting periodic CSIs that are L1-RSRP on PUCCH for the duration indicated by drx-onDurationTimer, where DCP is configured but the associated drx-onDurationTimer has not started;

[0267] downlinkHARQ-FeedbackDisabled (optional): Configuration to disable HARQ feedback per DL HARQ process;

[0268] uplinkHARQ-Mode (optional): Configuration for setting HARQmodeA or HARQmodeB per UL HARQ process;

[0269] disableCG-RetransmissionMonitoring (optional): Configuration to disable the initiation of drx-HARQ-RTT-TimerUL for UL transmissions via a configured uplink grant;

[0270] drx-TimeReferenceSFN (optional): Configuration to indicate how the UE initializes DRX_SFN_COUNTER.

[0271] If drx-NonIntegerLongCycleStartOffset is set, the following UE variables are used for DRX operation:

[0272] DRX_SFN_COUNTER: A counter that increments when SFN changes to 0. The maximum value of this counter is at least 65535.

[0273] The Serving Cells of a MAC entity can be configured by RRC into two DRX groups with separate DRX parameters. If RRC does not configure a secondary DRX group, only one DRX group exists, and all Serving Cells belong to that DRX group. If two DRX groups are configured, each Serving Cell is uniquely assigned to one of the two groups. The DRX parameters configured separately for each DRX group are drx-onDurationTimer and drx-InactivityTimer. The DRX parameters common to the 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.

[0274] If a DRX is configured, the Active Time for a serving cell within the DRX group includes the following periods:

[0275] The time during which drx-onDurationTimer or drx-InactivityTimer configured for the relevant DRX group is running; or

[0276] The time when drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running in any serving cell within the DRX group; or

[0277] The time during which ra-ContentionResolutionTimer (as described in Section 5.1.5) or msgB-ResponseWindow (as described in Section 5.1.4a) is running; or

[0278] The time during which a scheduling request is transmitted on PUCCH and is pending (as described in Section 5.4.4 or 5.22.1.5). If this serving cell is part of a non-terrestrial network, the active time begins by adding the UE-gNB RTT after the transmission of the scheduling request when SR_COUNTER is 0 for all SR configurations with pending SRs; or

[0279] A time during which a PDCCH indicating a new transmission addressed to the MAC entity's C-RNTI is not received following the successful reception of a Random Access Response for a Random Access Preamble that was not selected by the MAC entity among contention-based Random Access Preambles (as described in Sections 5.1.4 and 5.1.4a); or

[0280] Time when a RACH-less LTM cell switch is in progress; or

[0281] Time when a RACH-less handover is in progress on a terrestrial network.

[0282] The following MAC timers are used for DRX operation in non-terrestrial networks:

[0283] HARQ-RTT-TimerDL-NTN (per DL HARQ process with HARQ feedback enabled): Minimum duration before a DL assignment for HARQ retransmission is expected by a MAC object;

[0284] HARQ-RTT-TimerUL-NTN (per UL HARQ process configured with HARQModeA): The minimum duration before a UL HARQ retransmission grant is expected by a MAC object.

[0285] If DRX is not configured and a multicast DRX is configured for G-RNTI or G-CS-RNTI, the MAC object must perform the following:

[0286] 1> Monitor PDCCH as specified in TS 38.213 [6];

[0287] 1> When a MAC PDU is received in a downlink assignment set for unicast; or

[0288] 1> When PDCCH indicates a downlink unicast transmission:

[0289] 2> Stop drx-RetransmissionTimerDL-PTM for the relevant HARQ process.

[0290] If DRX is configured, the MAC object must perform the following:

[0291] 1> When a MAC PDU is received in a downlink allocation set for unicast:

[0292] 2> If this serving cell is set to downlinkHARQ-FeedbackDisabled:

[0293] 3> If the relevant HARQ process is set to have HARQ feedback enabled:

[0294] 4> Set HARQ-RTT-TimerDL-NTN for the corresponding HARQ process to the value of drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value;

[0295] 4> Start HARQ-RTT-TimerDL-NTN for the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.

[0296] 2> If not:

[0297] 3> Start drx-HARQ-RTT-TimerDL for the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying the DL HARQ feedback.

[0298] 2> Stop drx-RetransmissionTimerDL for the relevant HARQ process;

[0299] 2> Stop drx-RetransmissionTimerDL-PTM for the relevant HARQ process.

[0300] 1> If a MAC PDU is transmitted in a configured uplink grant and an LBT failure indication is not received from lower layers:

[0301] 2> If this serving cell is set to uplinkHARQ-Mode:

[0302] 3> If the corresponding HARQ process is set to HARQModeA:

[0303] 4> Set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process to the value of drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value;

[0304] 4> If drx-LastTransmissionUL is set:

[0305] 5> Start HARQ-RTT-TimerUL-NTN for the corresponding HARQ process at the first symbol after the end of the last transmission (in the bundle) of the corresponding PUSCH transmission.

[0306] 4> If not:

[0307] 5> Start HARQ-RTT-TimerUL-NTN for the corresponding HARQ process at the first symbol after the end of the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0308] 2> If not:

[0309] 3> If disableCG-RetransmissionMonitoring is not set for the configured uplink acknowledgment:

[0310] 4> If drx-LastTransmissionUL is set:

[0311] 5> Start drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol after the end of the last transfer of the corresponding PUSCH transfer (within the bundle).

[0312] 4> If not:

[0313] 5> Start drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol after the end of the first transfer (within the bundle) of the corresponding PUSCH transfer.

[0314] 2> Stop the corresponding HARQ process with drx-RetransmissionTimerUL on the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0315] 1> When a MAC PDU is transmitted in a configured sidelink grant:

[0316] 2> If the PUCCH resource is configured:

[0317] 3> Start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the corresponding PUCCH transmission carrying the sidelink (SL) HARQ feedback has finished; or

[0318] 3> When PUCCH is not transmitted, start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the corresponding PUCCH resource for sidelink (SL) HARQ feedback has finished;

[0319] 3> Stop drx-RetransmissionTimerSL for the relevant HARQ process.

[0320] 2> Otherwise (else):

[0321] 3> Start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission is finished;

[0322] 3> Stop drx-RetransmissionTimerSL for the relevant HARQ process.

[0323] 1> When drx-HARQ-RTT-TimerDL expires:

[0324] 2> If the data for the corresponding HARQ process is not successfully decoded:

[0325] 3> Start drx-RetransmissionTimerDL for the corresponding HARQ process at the first symbol after drx-HARQ-RTT-TimerDL expires.

[0326] 1> When HARQ-RTT-TimerDL-NTN expires:

[0327] 2> If the data for the corresponding HARQ process was not successfully decoded:

[0328] 3> Start drx-RetransmissionTimerDL for the corresponding HARQ process at the first symbol after HARQ-RTT-TimerDL-NTN expires.

[0329] 1> When drx-HARQ-RTT-TimerUL expires:

[0330] 2> Start drx-RetransmissionTimerUL for the corresponding HARQ process at the first symbol after drx-HARQ-RTT-TimerUL expires.

[0331] 1> When HARQ-RTT-TimerUL-NTN expires:

[0332] 2> Start drx-RetransmissionTimerUL for the corresponding HARQ process at the first symbol after HARQ-RTT-TimerUL-NTN expires.

[0333] 1> When drx-HARQ-RTT-TimerSL expires:

[0334] 2> When HARQ NACK feedback for the relevant HARQ process is transmitted on the PUCCH; or

[0335] 2> If HARQ NACK feedback for the relevant HARQ process has been generated but has not been transmitted on PUCCH; or

[0336] 2> If the PUCCH resource is not configured for Sidelink (SL) grant:

[0337] 3> Start drx-RetransmissionTimerSL for the corresponding HARQ process at the first symbol after drx-HARQ-RTT-TimerSL expires.

[0338] Note: UE handles the behavior of drx-RetransmissionTimerSL in the same way as when sl-PUCCH-Config is not configured by RRC but the PUCCH resource is not scheduled.

[0339] 1> When a DRX Command MAC CE indicated by a PDCCH addressed to C-RNTI or CS-RNTI, or a DRX Command MAC CE by a downlink assignment set for unicast transmission, or a Long DRX Command MAC CE is received:

[0340] 2> Stop drx-onDurationTimer for each DRX group;

[0341] 2> Stop drx-InactivityTimer for each DRX group.

[0342] 1> When drx-InactivityTimer for a DRX group expires:

[0343] 2> If Short DRX cycle is set:

[0344] 3> Start or restart drx-ShortCycleTimer for this DRX group at the first symbol after drx-InactivityTimer expires;

[0345] 3> Use a short DRX cycle for this DRX group.

[0346] 2> If not:

[0347] 3> Use a Long DRX cycle for this DRX group.

[0348] 1> When a DRX command MAC CE directed by a PDCCH addressed to C-RNTI or CS-RNTI, or a DRX command MAC CE by a downlink assignment set for unicast transmission is received:

[0349] 2> If a short DRX cycle is set:

[0350] 3> Start or restart drx-ShortCycleTimer for each DRX group at the first symbol after the DRX command MAC CE reception is finished;

[0351] 3> Use a short DRX cycle for each DRX group.

[0352] 2> If not:

[0353] 3> Use a long DRX cycle for each DRX group.

[0354] 1> When drx-ShortCycleTimer for a DRX group expires:

[0355] 2> Use a long DRX cycle for this DRX group.

[0356] 1> When a long DRX command MAC CE is received:

[0357] 2> Stop drx-ShortCycleTimer for each DRX group;

[0358] 2> Use a long DRX cycle for each DRX group.

[0359] 1> If drx-NonIntegerLongCycleStartOffset is set:

[0360] 2> Increment DRX_SFN_COUNTER by 1 at the first symbol of the slot where SFN changes to 0;

[0361] 2> If DRX is (re)configured by RRC:

[0362] 3> If drx-TimeReferenceSFN is included in the RRC (re)configuration received during the first half of the hyper frame (i.e., SFN is between 0 and 511):

[0363] 4> Set DRX_SFN_COUNTER to 1.

[0364] 3> If not:

[0365] 4> Set DRX_SFN_COUNTER to 0.

[0366] 1> If Short DRX cycle is used for the DRX group and drx-NonIntegerShortCycle is not set, and [(SFN Х 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle); or

[0367] 1> For the DRX group, Short DRX cycle is used and drx-NonIntegerShortCycle is set, and floor([(DRX_SFN_COUNTER Х 10240) + (SFN Х 10) + subframe number - drx-StartOffset] modulo (drx-NonIntegerShortCycle)) = 0:

[0368] 2> Start drx-onDurationTimer for the corresponding DRX group after drx-SlotOffset from the start of the subframe.

[0369] 1> If Long DRX cycle is used for the DRX group and drx-NonIntegerLongCycleStartOffset is not set, and [(SFN Х 10) + subframe number] modulo (drx-LongCycle) = drx-StartOffset; or

[0370] 1> For the DRX group, Long DRX cycle is used and drx-NonIntegerLongCycleStartOffset is set, and floor([(DRX_SFN_COUNTER Х 10240) + (SFN Х 10) + subframe number] modulo (drx-NonIntegerLongCycle)) = drx-StartOffset:

[0371] 2> If DCP monitoring is configured for an active DL BWP as specified in Section 10.3 of TS 38.213 [6]:

[0372] 3> If a DCP indication associated with the current DRX cycle received from a lower layer instructs to start drx-onDurationTimer; or

[0373] 3> If all DCP applications in the time domain associated with the current DRX cycle occurred within Active Time, considering the acknowledgment / assignment / DRX command MAC CE / Long DRX command MAC CE received and the transmitted scheduling request up to 4ms prior to the start of the last DCP application; or

[0374] 3> If ps-Wakeup is set to true and the DCP indication associated with the current DRX cycle is not received from the lower layer:

[0375] 4> Start drx-onDurationTimer after drx-SlotOffset from the start of the subframe.

[0376] 2> If not:

[0377] 3> Start drx-onDurationTimer for the corresponding DRX group after drx-SlotOffset from the start of the subframe.

[0378] Note 2: If SFNs are not aligned between carriers within a cell group, the DRX duration is calculated using the SFNs of SpCells.

[0379] 1> If the DRX group is within Active Time:

[0380] 2> Monitor PDCCH in the Serving Cells within the DRX group as specified in TS 38.213 [6];

[0381] 2> If PDCCH indicates downlink transmission (DL transmission); or

[0382] 2> Where PDCCH represents one-shot HARQ feedback as specified in Section 9.1.4 of TS 38.213 [6]; or

[0383] 2> When PDCCH represents a retransmission of HARQ feedback as specified in Section 9.1.5 of TS 38.213 [6]:

[0384] 3> If the corresponding serving cell is configured to downlinkHARQ-FeedbackDisabled:

[0385] 4> If at least one of the corresponding HARQ process(s) is set to the HARQ feedback enabled state:

[0386] 5> For the corresponding HARQ process(s), set HARQ-RTT-TimerDL-NTN to the value of drx-HARQ-RTT-TimerDL plus the most recent available UE-gNB RTT value;

[0387] 5> If the UE is configured with one-shot HARQ feedback:

[0388] 6> At the first symbol after the end of the corresponding transmission carrying the downlink (DL) HARQ feedback, the HARQ feedback is activated and the HARQ-RTT-TimerDL-NTN for the reported corresponding HARQ process(s) is started or restarted.

[0389] 5> Otherwise (else):

[0390] 6> Start HARQ-RTT-TimerDL-NTN for the corresponding HARQ process at the first symbol after the end of the corresponding transmission carrying downlink (DL) HARQ feedback.

[0391] 3> If not:

[0392] 4> At the first symbol after the end of the corresponding transmission carrying downlink (DL) HARQ feedback, start or restart drx-HARQ-RTT-TimerDL for the corresponding HARQ process(s) for which HARQ feedback was reported.

[0393] Note 3: As specified in TS 38.213 [6], if HARQ feedback is postponed by PDSCH-to-HARQ_feedback timing indicating an inapplicable k1 value, the corresponding transmission opportunity to send downlink (DL) HARQ feedback is indicated in the subsequent PDCCH requesting HARQ-ACK feedback.

[0394] 3> Stop drx-RetransmissionTimerDL for the corresponding HARQ process(s) for which HARQ feedback was reported;

[0395] 3> Stop drx-RetransmissionTimerDL-PTM for the corresponding HARQ process;

[0396] 3> When PDSCH-to-HARQ_feedback timing indicates an inapplicable k1 value as specified in TS 38.213 [6]:

[0397] 4> Start drx-RetransmissionTimerDL at the first symbol after the (last) PDSCH transfer (termination) for the corresponding HARQ process.

[0398] 2> When PDCCH indicates uplink transmission (UL transmission):

[0399] 3> If the corresponding serving cell is set to uplinkHARQ-Mode:

[0400] 4> If the corresponding HARQ process is set to HARQModeA:

[0401] 5> Set HARQ-RTT-TimerUL-NTN for the corresponding HARQ process to the value of drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value;

[0402] 5> If drx-LastTransmissionUL is set:

[0403] 6> Start HARQ-RTT-TimerUL-NTN for the corresponding HARQ process at the first symbol after the end of the last transmission (in the bundle) of the corresponding PUSCH transmission.

[0404] 5> If not:

[0405] 6> Start HARQ-RTT-TimerUL-NTN for the corresponding HARQ process at the first symbol after the end of the first transmission (within the bundle) of the PUSCH transmission.

[0406] 3> If not:

[0407] 4> If drx-LastTransmissionUL is set:

[0408] 5> Start drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol after the end of the last transfer (within the bundle) of the corresponding PUSCH transfer.

[0409] 4> If not:

[0410] 5> Start drx-HARQ-RTT-TimerUL for the corresponding HARQ process at the first symbol after the end of the first transfer (within the bundle) of the corresponding PUSCH transfer.

[0411] 3> Stop drx-RetransmissionTimerUL for the corresponding HARQ process.

[0412] 2> When PDCCH indicates sidelink transmission (SL transmission):

[0413] 3> If the PUCCH resource is set:

[0414] 4> Start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the end of the corresponding PUCCH transmission carrying the sidelink (SL) HARQ feedback; or

[0415] 4> When PUCCH is not transmitted, start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the termination of the corresponding PUCCH resource for sidelink (SL) HARQ feedback;

[0416] 4> Stop drx-RetransmissionTimerSL for the relevant HARQ process.

[0417] 3> If not:

[0418] 4> Start drx-HARQ-RTT-TimerSL for the corresponding HARQ process at the first symbol after the PDCCH occasion ends;

[0419] 4> Stop drx-RetransmissionTimerSL for the relevant HARQ process.

[0420] 2> If PDCCH indicates a new transmission (downlink, uplink, or sidelink) in the serving cell within this DRX group:

[0421] 3> Start or restart drx-InactivityTimer for the corresponding DRX group at the first symbol after PDCCH reception ends.

[0422] Note 3a: A PDCCH representing SPS activation, configured grant type 2, or a configured sidelink grant of configured grant type 2 is considered to represent a new transmission.

[0423] Note 3b: As described in Section 10.1 of TS 38.213 [6], if a PDCCH reception contains two PDCCH candidates from the corresponding search spaces, start or restart the drx-InactivityTimer for the corresponding DRX group at the first symbol after the PDCCH candidate that ends later in time ends.

[0424] 2> When the HARQ process receives downlink feedback information and an acknowledgment is indicated:

[0425] 3> Stop drx-RetransmissionTimerUL for the corresponding HARQ process.

[0426] 1> Where DCP monitoring is configured for an active DL BWP as specified in Section 10.3 of TS 38.213 [6]; and

[0427] 1> If the current symbol n occurs within the duration of the drx-onDurationTimer; and 1> If the drx-onDurationTimer associated with the current DRX cycle has not started as specified in this section:

[0428] 2> When evaluating all DRX Active Time conditions specified in this section, if the MAC entity is not in Active Time considering the acknowledgment / assignment / DRX command MAC CE / Long DRX command MAC CE and transmitted scheduling requests received up to 4ms prior to symbol n; and

[0429] 2> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any active BWP of the serving cell(s), or if, when evaluating all DRX active time conditions specified in Section 5.7b, considering the multicast allocation / DRX command MAC CE for MBS multicast received up to 4ms prior to symbol n, all multicast DRXs will not be in active time and all multicast sessions are set as multicast DRXs:

[0430] 3> Does not transmit periodic SRS and semi-persistent SRS as defined in TS 38.214 [7];

[0431] 3> Does not report semi-continuous CSI set on PUSCH;

[0432] 3> Does not report semi-persistent CSI on PUCCH;

[0433] 3> If ps-TransmitPeriodicL1-RSRP is not configured with a true value:

[0434] 4> Does not report periodic CSI as L1-RSRP on PUCCH.

[0435] 3> If ps-TransmitOtherPeriodicCSI is not configured with a true value:

[0436] 4> Does not report periodic CSI other than L1-RSRP on PUCCH.

[0437] 1> Otherwise (else):

[0438] 2> In the current symbol n, when evaluating all DRX active time conditions specified in this section, if the DRX group would not be in active time by considering the acknowledgments / assignments scheduled to the serving cell(s) within the DRX group up to 4ms prior to symbol n, the received DRX command MAC CE / Long DRX command MAC CE, and the transmitted scheduling requests; and

[0439] 2> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any active BWP of the serving cell(s), or if, when evaluating all DRX active time conditions specified in Section 5.7b at the current symbol n, considering the multicast allocation / DRX command MAC CE for MBS multicast received up to 4ms prior to symbol n, all multicast DRXs corresponding to that DRX group will not be in active time and all multicast sessions corresponding to that DRX group are set as multicast DRXs:

[0440] 3> The DRX group does not transmit periodic SRS and semi-continuous SRS as defined in TS 38.214 [7];

[0441] 3> The DRX group does not report CSI on PUCCH and semi-continuous CSI set on PUSCH.

[0442] 2> When CSI masking is set up by upper layers:

[0443] 3> At the current symbol n, when evaluating all DRX active time conditions specified in this section, if the DRX group's drx-onDurationTimer is not running considering the accepted / assigned and received DRX command MAC CE / Long DRX command MAC CE scheduled in the serving cell(s) within the DRX group up to 4ms prior to symbol n; and

[0444] 3> if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if cfr-ConfigMulticast is not configured for any active BWP of the serving cell(s), or if, when evaluating all DRX active time conditions specified in Section 5.7b at the current symbol n, considering the DRX command MAC CE for MBS multicast received up to 4ms prior to symbol n, the drx-onDurationTimerPTM(s) of all multicast DRXs corresponding to that DRX group will not be running and all multicast sessions corresponding to that DRX group are configured as multicast DRXs:

[0445] 4> The DRX group does not report CSI on PUCCH.

[0446] Note 4: If a UE multiplexes a CSI set on a PUCCH with other overlapping UCI(s) in accordance with the procedure specified in Section 9.2.5 of TS 38.213 [6], and this CSI multiplexed with other UCI(s) is to be reported through the PUCCH resource outside of the DRX active time of the DRX group on which the PUCCH is set, or outside of the on-duration period of the DRX group on which the PUCCH is set if CSI masking is set by a higher layer, it is up to the UE implementation whether to report this CSI multiplexed with other UCI(s).

[0447] The MAC object must ensure that no rounding error occurs when performing a modulus operation with drx-NonIntegerShortCycle or drx-NonIntegerLongCycle as the divisor.

[0448] Regardless of whether the MAC object is monitoring the PDCCH in the serving cell of the DRX group, the MAC object transmits HARQ feedback, aperiodic CSI on the PUSCH, and aperiodic SRS as defined in TS 38.214 [7] when the transmission is expected.

[0449] MAC objects do not need to monitor the PDCCH if it is not a complete PDCCH occupancy (e.g., if the active time starts or ends in the middle of the PDCCH occupancy).

[0450] If drx-LastTransmissionUL is set, drx-HARQ-RTT-TimerUL or HARQ-RTT-TimerUL-NTN starts after the bundle's last PUSCH transmission location, regardless of whether that last PUSCH transmission location was used for an actual PUSCH transmission.

[0451] Figure 7 is a diagram illustrating terminal operation according to DRX settings.

[0452] The DRX mechanism implemented in 5G and LTE networks is designed to optimize battery usage by allowing the UE to intermittently enter a "sleep" state where it does not need to monitor the PDCCH. This configuration is established via the network's RRC signaling, enabling the UE to periodically wake up to check for potential downlink data and remain active for a specified period. The length of this active period can be adjusted based on scheduling decisions and the UE's decoding success. To effectively manage the active period, the UE uses various timers (e.g., drx-InactivityTimer, drx-RetransmissionTimer), which are started or restarted by PDCCH scheduling or the transmission and reception of MAC PDUs. The DRX mechanism is sophisticatedly designed to ensure reliable reception of the scheduled PDCCH, and the active time is extended by starting or restarting the timers.

[0453] However, even if the DRX mechanism is configured, the UE must respond when UL data is generated, regardless of the active time determined by the DRX operation. When UL data is generated, the UE immediately wakes up and performs UL operations, which include transmitting BSR. If the BSR transmission fails, the UE initiates SR, and if this also fails, it performs the RACH procedure to establish a connection for transmitting UL data.

[0454] The additional "wake-up" operation for UL data transmission during such DRX active time can undermine the power saving effects intended by the DRX mechanism. In particular, the requirement for the UE to wake up separately for UL data transmission increases power consumption, which can offset the efficiency improvements sought through the DRX configuration. Therefore, while the DRX mechanism aims to optimize battery life by allowing the UE to enter a power-saving state, the simultaneous requirement to process UL data can create a conflict that reduces the overall power saving effect.

[0455] There are several potential disadvantages to the existing operation based on current standards due to the interaction between the DRX mechanism and the uplink operation.

[0456] Power consumption increases because the UE must wake up from the "sleep" state to transmit UL data. This runs counter to the basic purpose of DRX, which is to increase battery efficiency by minimizing the active period.

[0457] Even if the UE performs UL operations during the DRX inactive time, resource allocation for PDCCH monitoring is still required in sleep mode. This results in inefficiency where the UE uses network resources for monitoring without actually transmitting data, and consequently undermines the power-saving benefits of the DRX mechanism.

[0458] To improve power efficiency and optimize resource allocation during DRX operation associated with UL operation, a method is proposed in which the UE predicts the expected arrival time of the next packet of jittery periodic traffic when transmitting UL data and adjusts the DRX cycle accordingly. The ability to adjust DRX parameters based on network conditions and traffic patterns is important for optimizing the balance between power efficiency and data integrity.

[0459] Step 1. The UE's MAC entity may be configured by RRC with a DRX functionality that controls the UE's PDCCH monitoring activity.

[0460] In Step 1, the UE receives an initial DRX configuration from the NW via RRC signaling. This configuration defines parameters that govern the UE's power-saving and active states and is important as it directly affects the UE's power consumption and data processing capabilities. Upon receiving the DRX configuration, the UE stores it for future reference and utilizes it to effectively manage power consumption while maintaining responsiveness to received data.

[0461] The DRX settings may include the following DRX operation-related timer information.

[0462] drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerSL, drx-HARQ-RTT-TimerSL, drx-LastTransmissionUL, ps-Wakeup, ps-TransmitPeriodicL1-RSRP, downlinkHARQ-FeedbackDisabled, uplinkHARQ-Mode

[0463] During active time, the UE monitors the PDCCH. The active time of serving cells within a DRX group includes a period that satisfies any of the following conditions.

[0464] - If drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is active

[0465] - If drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running in any Serving Cell within the DRX group

[0466] - If ra-ContentionResolutionTimer or msgB-ResponseWindow is active

[0467] - When a Scheduling Request has been transmitted and is pending on the PUCCH. If the Serving Cell is part of a non-terrestrial network, and in all SR configurations, the Active Time starts from the point calculated by adding the UE-gNB RTT after the transmission of the Scheduling Request performed when the SR_COUNTER for the pending SR is 0.

[0468] - If, even after successfully receiving a Random Access Response for a Random Access Preamble that the MAC entity did not select among the contention-based Random Access Preambles, a PDCCH instructing a new transmission targeting the MAC entity's C-RNTI has not yet been received

[0469] Step 2. The UE predicts the expected arrival and / or transmission time for the next packet of periodic traffic.

[0470] In this step, the UE predicts the expected arrival time and / or transmission time of the next periodic traffic packet. Traffic that may occur during the configured DRX operation includes both UL traffic and DL traffic. Here, it is assumed that both UL and DL traffic have jitter and are periodic. Examples of UL traffic may include XR traffic, and examples of DL traffic may include AR traffic and tethering scenarios.

[0471] The UE can collect data on DL and UL data during DRX operation. Based on the collected data, the UE generates a prediction module for DL ​​and / or UL data. Specifically, the UE can perform predictions on DL data and / or UL data. For DL ​​data prediction, the UE predicts the expected arrival time of the next periodic traffic packet. For UL data prediction, the UE predicts the expected transmission time of the next periodic traffic packet.

[0472] To improve prediction performance, the UE may include the following specialized modules.

[0473] 1. Expected DL data Arrival Time Prediction Module: This module uses AIML techniques to predict the arrival time of the next periodic traffic packet by considering jitter characteristics. This enables the UE to make informed decisions based on past traffic patterns. Components of the expected arrival time information may include time, jitter characteristics, periodicity, and other related factors.

[0474] 2. UL Data Transmission Time Prediction Module: This module also uses AIML techniques to predict the transmission time of the next periodic traffic packet by considering jitter characteristics. This enables the UE to make informed decisions based on historical traffic patterns. Components of the predicted transmission time information may include time, jitter characteristics, periodicity, and other related factors.

[0475] When the Expected DL data Arrival Time Prediction Module and / or UL Data Transmission Management Module calculate the predicted arrival time of the next periodic DL traffic packet and / or the transmission time of the next periodic UL traffic packet, the UE can derive information related to the preferred DRX timer setting in Step 3. This prediction function not only optimizes the UE's power consumption but also improves responsiveness to incoming and outgoing data traffic for efficient communication in a dynamic network environment.

[0476] Step 3. UE-informed preferred DRX timer-related information based on the time prediction module

[0477] In this step, the UE predicts the expected arrival time and / or transmission time of the next periodic traffic packet. If this predicted time does not match the upcoming drx-onDurationTimer interval, the UE may instruct the NW with its preferred DRX timer information. The UE first checks whether the predicted arrival time of the next packet matches the start point of the next drx-onDurationTimer (or the onDuration within the next DRX cycle). If a discrepancy is detected, the UE may instruct the NW with its preferred DRX timer information.

[0478] The key factor in determining preferred DRX timer information is minimizing unnecessary PDCCH monitoring. To this end, the following factors can be considered.

[0479] - Expected DL data Output of Arrival Time Prediction Module

[0480] - Output of UL Data Transmission Time Prediction Module

[0481] - Weights assigned to each module output:

[0482] If a higher weight is assigned to the UL Data Transmission Time Prediction Module, the start time of the DRX cycle is adjusted to match the transmission time of the next periodic UL traffic packet. As a result, the NW and UE manage DL traffic together according to the newly adjusted DRX cycle. In this case, power savings can be maximized if the periodicity of UL traffic and DL traffic is synchronized.

[0483] Conversely, if a greater weight is given to the Expected DL data Arrival Time Prediction Module, the start time of the DRX cycle is adjusted to match the arrival time of the next periodic DL traffic packet. Even in this case, the NW and UE process DL traffic according to the newly adjusted DRX cycle, and the UE may also consider UL data transmission delay for additional power saving.

[0484] - Power state of UE: If the UE is in a low-power state, it may direct preferred information to minimize wake-up operations during DRX.

[0485] All operations related to DRX timer adjustment can be performed through the DRX Operation Preference Module. This module plays a key role in optimizing UE power consumption by modifying the activation and deactivation timing of DRX cycles using predicted arrival times. By aligning DRX cycles with expected traffic patterns, the UE can significantly reduce unnecessary wake-ups and ultimately conserve battery life.

[0486] The expected output of the DRX Operation Preference Module may include at least one of the following 1) to 3).

[0487] 1) Start time of the next DRX cycle

[0488] 2) Decision on whether to apply the Long DRX cycle or the Short DRX cycle, and related configuration information

[0489] 3) The duration for which the adjusted DRX cycle will remain valid and operational. This is intended to ensure optimal performance and resource utilization efficiency during that period.

[0490] Preferred DRX timer-related information must be piggybacked during the transmission of UL data via the last PUSCH just before the DRX cycle is interrupted.

[0491] The following embodiments may be considered as a method for the UE to transmit preferred DRX timer information to the NW.

[0492] Method 1: NW-approved Adjustment of DRX cycle

[0493] Method 1-1) The UE transmits preferred DRX timer related information by piggybacking it to UL traffic.

[0494] Method 1-2) Upon receiving information regarding UL traffic and preferred DRX timers, the NW instructs the UE to adjust the DRX cycle accordingly.

[0495] Method 1-3) The UE applies the adjusted DRX cycle according to the instructions of the NW.

[0496] Method 2: UE-independent Adjustment of DRX cycle

[0497] Method 2-1) The UE transmits preferred DRX timer related information by piggybacking it to UL traffic.

[0498] Method 2-2) If the UE does not receive a retransmission grant from the NW, it applies a DRX cycle adjusted based on information related to the preferred DRX timer without additional network instructions.

[0499] Method 2-3) When the UE receives a retransmission grant from the network, it piggybacks the preferred DRX timer information along with the UL data (PUSCH) to be retransmitted and sends it to the NW.

[0500] Method 2-3-1) Depending on the situation, the UE follows the procedure of Method 2-2) or Method 2-3).

[0501] For example, if only the DL data arrival time is predicted, the UE can indicate preferred DRX timer information based on the predicted DL data arrival time. If the predicted DL arrival time falls within a specific window, the UE can adjust UL transmission to align with the DRX cycle. This allows the UE to remain ready to receive DL data without unnecessary delays while simultaneously transmitting UL data at the most optimal time.

[0502] For example, if only the UL data arrival time is predicted, the UE may direct preferred DRX timer information based on the predicted UL data arrival time. Based on this information, the network may adjust the DL data arrival time and reset new DRX-related information for the DL data. In this case, the UE may transmit preferred DRX information to the network only when it is expected that the predicted UL traffic will not occur within a specific time window based on the predicted DL data arrival time and / or DRX settings.

[0503] For example, if both DL and UL data arrival times are predicted, the UE can indicate preferred DRX timer information based on the predicted DL / UL data arrival times. In this case, the UE can adjust the DRX timer based on the predicted DL / UL data arrival times. Additionally, the UE can adjust the DL / UL transmission timing. Examples of DL / UL transmission timing adjustments are as follows.

[0504] (i) The UE can adjust the uplink (UL) data transmission time based on the predicted downlink (DL) data arrival time: in this case, the UE uses the predicted downlink (DL) data arrival time to schedule its uplink (UL) transmission.

[0505] (ii) The UE may coordinate DL / UL data transmission based on the earlier of the predicted DL / UL data times: The UE may use the earlier of the predicted downlink (DL) or uplink (UL) data arrival times as a reference for coordinating its transmission.

[0506] (iii) The UE may coordinate DL / UL data transmission based on the later of the predicted DL / UL data times. In this case, the UE considers the later arrival time of the downlink (DL) or uplink (UL) data as the key timing reference. This may be useful if the UE wants to ensure that transmission does not start too early and that resources are not prematurely allocated.

[0507] (iv) The UE may adjust DL / UL data transmission based on the longer duration of the expected DL / UL data. This includes adjusting the transmission schedule based on data transmissions expected to be longer. This may also mean that the UE ensures sufficient time is available to complete the transmission depending on which side requires more time, downlink (DL) or uplink (UL), potentially improving data flow efficiency and preventing premature cutoffs.

[0508] Step 4. Adjusting the DRX cycle based on the DRX Operation Preference Module

[0509] Based on the preference information set in Step 3, actual DRX cycle adjustment is performed in this step. The preference information derived from the UE's DRX Operation Preference Module is critical to DRX cycle adjustment. This will be explained below with reference to Figures 8 and 9.

[0510] FIG. 8 is an example of DRX cycle adjustment according to one embodiment of the present specification.

[0511] Specifically, FIG. 8 illustrates an operation to change / adjust the time interval by the DRX on-duration timer according to the following method 1 to an on-duration (8B) located at a point in time earlier than the existing on-duration (8A).

[0512] Method 1: If the predicted expected arrival time and / or transmission time of the next packet (e.g., the expected arrival time of the next packet of jittery periodic traffic) is earlier than the time interval (8A) according to the upcoming DRX on-duration timer, the UE preemptively advances the start time of the DRX on-duration timer. The time interval according to the start time of the adjusted DRX on-duration timer is indicated by 8B.

[0513] FIG. 9 is another example of DRX cycle adjustment according to one embodiment of the present specification.

[0514] Specifically, FIG. 9 illustrates an operation to change / adjust the time interval by the DRX on-duration timer according to the following method 2 to an on-duration (9B) located at a time delayed from the existing on-duration (9A).

[0515] Method 2: If the predicted expected arrival time and / or transmission time of the next packet (e.g., the expected arrival time of the next packet of jittery periodic traffic) occurs immediately after the end of the time interval (9A) by the next DRX on-duration timer (within a defined offset), the UE delays the start time of the DRX on-duration timer by that offset. The time interval corresponding to the start time of the adjusted DRX on-duration timer is indicated by 9B.

[0516] For example, the DRX on-duration timer starts based on the beginning of the DRX cycle; therefore, in this specification, the adjustment of the start point of the DRX on-duration timer may be interpreted or substituted for the adjustment of the start point of the DRX cycle. As a specific example, the DRX cycle may start based on the conditions according to "5.7 Discontinuous Reception (DRX)" described above. This will be explained in detail below.

[0517] Specifically, the starting point of the DRX period can be determined based on the System Frame Number (SFN) and the subframe number. For example, the terminal can determine whether the DRX period starts in the corresponding subframe based on whether the time index defined by SFN ≡ 10 + subframe number satisfies conditions related to the DRX period and the start offset.

[0518] [1] For example, if a short DRX period is used and a non-integer short DRX period is not set, the terminal can determine the subframe satisfying the following conditions as the starting point of the short DRX period.

[0519] [(SFN Х 10) + subframe number] modulo drx-ShortCycle = drx-StartOffset modulo drx-ShortCycle

[0520] Specifically, if the time index corresponding to the current subframe corresponds to the same position as drx-StartOffset based on drx-ShortCycle, the terminal can determine that the subframe is the starting point of the short DRX cycle. In this case, the terminal can start drx-onDurationTimer after drx-SlotOffset from the starting point of the subframe.

[0521] [2] As another example, when a short DRX period is used and a non-integer short DRX period is set, the terminal can determine the starting point of the short DRX period by considering the DRX_SFN_COUNTER, SFN, and subframe number together. In this case, the terminal can determine the starting point of the non-integer short DRX period as a subframe that satisfies the following conditions.

[0522] floor([(DRX_SFN_COUNTER Х 10240) + (SFN Х 10) + subframe number - drx-StartOffset] modulo drx-NonIntegerShortCycle) = 0

[0523] Specifically, when a non-integer short DRX period is set, instead of simply considering only the subframe index within a single SFN period, an extended time index can be constructed using DRX_SFN_COUNTER, and the starting point of the DRX period can be determined based on whether the extended time index satisfies the period condition corresponding to the non-integer short DRX period. In this case, the terminal can start drx-onDurationTimer after drx-SlotOffset from the starting point of the corresponding subframe.

[0524] [3] As another example, when a long DRX period is used and a non-integer long DRX period is not set, the terminal can determine the subframe satisfying the following conditions as the starting point of the long DRX period.

[0525] [(SFN Х 10) + subframe number] modulo drx-LongCycle = drx-StartOffset

[0526] Specifically, if the time index corresponding to the current subframe corresponds to drx-StartOffset based on drx-LongCycle, the terminal can determine that the subframe is the starting point of the long DRX cycle. In this case as well, the terminal can start drx-onDurationTimer after drx-SlotOffset from the starting point of the subframe.

[0527] [4] As another example, when a long DRX period is used and a non-integer long DRX period is set, the terminal can determine the starting point of the non-integer long DRX period based on DRX_SFN_COUNTER, SFN, and subframe number. In this case, the terminal can determine the subframe satisfying the following conditions as the starting point of the non-integer long DRX period.

[0528] floor([(DRX_SFN_COUNTER Х 10240) + (SFN Х 10) + subframe number] modulo drx-NonIntegerLongCycle) = drx-StartOffset

[0529] Specifically, when a non-integer long DRX period is set, the starting point of the DRX period can be determined based on whether the extended time index satisfies the period condition and start offset condition corresponding to the non-integer long DRX period. In this case, the terminal can start drx-onDurationTimer after drx-SlotOffset from the starting point of the corresponding subframe.

[0530] As described above, in the existing NR DRX operation, the conditions for determining the start point of the DRX period may be defined differently depending on whether a short DRX period or a long DRX period is used, and whether a non-integer DRX period is set. The terminal determines the start of the DRX period in a subframe where these conditions are satisfied, and can start the drx-onDurationTimer after the drx-SlotOffset from the start point of the said subframe. Accordingly, in the DRX operation, the start point of the drx-onDurationTimer can be determined based on the DRX period, start offset, SFN, subframe number, and, if necessary, DRX_SFN_COUNTER.

[0531] The examples described above are examples of starting points of a DRX cycle to which the embodiments of this specification may be applied. The embodiments of this specification may also be applied even when the starting point of a DRX cycle is defined separately from the subframe-based examples.

[0532] When the DRX cycle is adjusted, the UE continues to monitor the PDCCH during the active time of the modified DRX cycle. This active time includes not only on-duration but also other time intervals that may be considered active due to data activity, such as when drx-InactivityTimer or drx-RetransmissionTimer is valid.

[0533] DRX cycle adjustments may be applied during the following periods.

[0534] 1) Temporarily applied: In this case, the adjustment is maintained for a specific period.

[0535] - After a certain period, the UE's DRX settings revert to the original DRX settings.

[0536] - After a certain period, the UE's DRX settings revert to the pre-configured DRX settings.

[0537] 2) It remains in effect until further instructions are given.

[0538] 3) It remains in effect until the next DRX cycle adjustment is made.

[0539] If the predicted result for the UE's next packet arrival time and / or transmission time differs from the actual result, a fallback mechanism based on at least one of the following 1) to 3) may be considered.

[0540] 1) Apply original DRX settings

[0541] 2) Apply pre-configured DRX settings

[0542] 3) Apply DRX cycle adjustments regardless of the accuracy of the prediction results.

[0543] To transmit the data unit of the present disclosure to UL-SCH, the UE must have available uplink resources. To receive the data unit of the present disclosure to DL-SCH, the UE must have available downlink resources. Resource allocation includes time domain resource allocation and frequency domain resource allocation. In the present disclosure, uplink resource allocation is also referred to as an uplink grant, and downlink resource allocation is also referred to as a downlink assignment. An uplink grant may be dynamically received by the UE via PDCCH, received via Random Access Response, or set semi-permanently by RRC. A downlink assignment may be dynamically received by the UE via PDCCH or set semi-permanently by RRC signaling from a base station.

[0544] According to the present disclosure, by predicting the UL transmission timing of jitter traffic and adjusting the DRX cycle accordingly, the proposed method enables highly efficient data transmission and reception for the UE. This preemptive adjustment not only optimizes the timing of the DRX cycle but also significantly improves power saving effects, thereby extending the operating life of the UE battery. As a result, the system achieves a balance between maintaining connectivity and minimizing energy consumption, and improves overall performance in a data communication environment characterized by variable traffic patterns.

[0545] Modules related to operations according to the embodiments described above may be interpreted or replaced by models. Additionally, for the convenience of explanation, the operation has been described by dividing it into multiple modules (e.g., Expected DL data Arrival Time Prediction Module, UL Data Transmission Time Prediction Module, DRX Operation Preference Module), but the operation based on the embodiments described above may be performed based on a single module or a single model. The model described above may refer to an AI / ML (Artificial Intelligence / Machine Learning) model. An AI / ML model may refer to a data-driven algorithm that applies AI / ML techniques to generate a set of outputs based on a set of inputs. The AI / ML model may be a UE-side model. In other words, the AI / ML model may be an AI / ML model in which inference is performed on the UE.

[0546] Below, we examine examples of terminal / base station operations based on the embodiments described above.

[0547] Case 1) DL only prediction

[0548] Step of receiving DRX settings for DRX operation;

[0549] Step of determining the predicted DL data arrival time;

[0550] A step of instructing the network with preferred DRX-related information based on the above-mentioned predicted DL data arrival time;

[0551] A step of adjusting the UL transmission timing to align with a DRX cycle configured based on the above-mentioned predicted DL data arrival time; and

[0552] A step of monitoring PDCCH during the active period of the above DRX cycle.

[0553] Case 2) UL only prediction

[0554] Step of receiving DRX settings for DRX operation;

[0555] Step of determining the predicted UL data arrival time;

[0556] A step of notifying the network of preferred DRX-related information based on the above-mentioned predicted UL data arrival time;

[0557] The above-mentioned notification step is performed only when it is expected that the predicted UL traffic will not occur within a time window determined based on the predicted DL data arrival time and / or DRX settings; and

[0558] A step of monitoring PDCCH during the active period of the above DRX cycle.

[0559] Case 3) DL / UL prediction

[0560] Step of receiving DRX settings for DRX operation;

[0561] Step of determining the predicted DL and UL data arrival times;

[0562] A step of instructing the network with preferred DRX-related information based on the predicted arrival times of the DL and UL data;

[0563] Step of adjusting DL and / or UL transmission timing based on one of the following:

[0564] (i) Predicted DL data arrival time, or

[0565] (ii) the earlier of the predicted DL and UL data arrival times, or

[0566] (iii) the later of the predicted DL and UL data arrival times, or

[0567] (iv) the longer of the predicted DL or UL data transmission duration; and

[0568] A step of monitoring PDCCH during the active period of the above DRX cycle.

[0569] In terms of implementation, the operations of the base station / terminal according to the embodiments described above can be processed by the device of FIG. 12 (e.g., the processor (110, 210) of FIG. 12).

[0570] In addition, the operations of the base station / terminal according to the above-described embodiment may be stored in memory (e.g., 140, 240 of FIG. 12) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 12).

[0571] The embodiments described above will be explained in detail below with reference to FIGS. 10 and FIGS. 11 in terms of the operation of the terminal and base station. The methods described below are distinguished only for convenience of explanation, and it is understood that a part of one method may be substituted with a part of another method or combined with one another and applied.

[0572] FIG. 10 is a flowchart illustrating a method according to one embodiment of the present specification.

[0573] Referring to FIG. 10, a method according to one embodiment of the present specification includes a step of receiving a DRX setting (S1010) and a step of transmitting preference information related to the DRX setting (S1020).

[0574] In S1010, the terminal receives a DRX (Discontinuous Reception) setting from the base station that includes i) information about the DRX timer and ii) information about the DRX cycle.

[0575] For example, the active time may include the time during which the DRX timer is running. The DRX timer may include a first DRX timer that starts based on the beginning of the DRX cycle.

[0576] For example, the above DRX settings may include parameters for controlling the DRX operation in the above-described 5.7 Discontinuous Reception (DRX).

[0577] As a specific example, the above DRX setting may include at least one of the parameters listed below.

[0578] drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle, drx-ShortCycleTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, drx-RetransmissionTimerSL, drx-HARQ-RTT-TimerSL, drx-LastTransmissionUL, ps-Wakeup, ps-TransmitPeriodicL1-RSRP, downlinkHARQ-FeedbackDisabled, uplinkHARQ-Mode

[0579] As a specific example, the DRX timer may include at least one of i) drx-onDurationTimer, ii) drx-InactivityTimer, iii) drx-RetransmissionTimerDL, iv) drx-RetransmissionTimerUL, and / or v) drx-RetransmissionTimerSL. The first DRX timer may be drx-onDurationTimer.

[0580] In S1020, the terminal transmits preference information related to the DRX setting to the base station.

[0581] According to one embodiment, the preference information may be related to i) the DRX period and / or ii) the adjustment of the DRX timer. The preference information may be determined based on a time predicted by the terminal. This embodiment may be based on Step 3 described above.

[0582] According to one embodiment, the time point may include at least one of i) an expected transmission time related to uplink data and / or ii) an expected arrival time related to downlink data.

[0583] According to one embodiment, the time point may be based on the output of an AI (Artificial Intelligence) / ML (Machine Learning) model. The AI / ML model may be generated or updated based on data collected during the DRX operation of the terminal. The output may be generated based on i) historical traffic patterns and ii) jitter characteristics related to periodic traffic.

[0584] For example, the above AI / ML model may include at least one AI / ML model based on the modules described above.

[0585] As a specific example, the above AI / ML model may include a single AI / ML model based on i) an Expected DL data Arrival Time Prediction Module, ii) a UL Data Transmission Time Prediction Module, and iii) a DRX Operation Preference Module. In this case, the single AI / ML model may generate an output corresponding to each module according to the input.

[0586] As a specific example, the above AI / ML model may be a plurality of AI / ML models based on i) an Expected DL data Arrival Time Prediction Module, ii) a UL Data Transmission Time Prediction Module, and iii) a DRX Operation Preference Module. In this case, each AI / ML model can generate an output corresponding to each module.

[0587] According to one embodiment, the preference information may be transmitted based on the last uplink shared channel before the DRX cycle (e.g., the nth DRX cycle) is interrupted. Through this, the terminal may operate according to the adjusted DRX cycle / adjusted DRX timer before the next DRX cycle (e.g., the n+1th DRX cycle) begins.

[0588] According to one embodiment, the preference information may be transmitted based on the fact that the time point is not within the active time.

[0589] According to one embodiment, based on the preference information, at least one of i) the starting point of the DRX cycle, ii) a setting to be applied to the DRX cycle among a long DRX cycle setting and a short DRX cycle setting, iii) the duration of the DRX cycle and / or iv) the starting point of the DRX timer may be determined.

[0590] According to one embodiment, the adjustment based on the preference information may be performed by the terminal based on instructions from the base station or autonomously by the terminal. Specifically, the DRX cycle and / or the first DRX timer may be adjusted based on instructions from the base station or autonomously adjusted by the terminal. This embodiment may be based on Method 1: NW-approved Adjustment of DRX cycle or Method 2: UE-independent Adjustment of DRX cycle.

[0591] For example, based on the fact that the above time point is earlier than the time interval based on the first DRX timer, the start time of the first DRX timer may be adjusted to an earlier time point based on the preference information. This embodiment may be based on method 1 of Step 4 (see FIG. 8).

[0592] For example, based on the fact that the above time point is later than the time interval based on the first DRX timer, the start time of the first DRX timer may be adjusted to a delayed time point based on the preference information. This embodiment may be based on method 2 of Step 4 (see FIG. 9).

[0593] For example, the first DRX timer starts based on the beginning of the DRX cycle, and the adjustment of the start point of the first DRX timer can be interpreted / substituted as the adjustment of the beginning of the DRX cycle.

[0594] The starting point of the above DRX cycle may mean i) a starting point determined in the same way as the existing method or ii) a starting point determined differently from the existing method. As a specific example of the existing method, the starting point of the above DRX cycle may be determined based on the System Frame Number (SFN) and the subframe number. More specifically, based on the fact that the SFN and the subframe number satisfy a defined condition (e.g., one of the conditions [1] to [4] defined based on the modulo operation described above), the starting point of the above DRX cycle may be determined as the starting point of the subframe based on the corresponding subframe number.

[0595] Operations based on the above-described S1010 to S1020 can be implemented by the device of FIG. 12. For example, referring to FIG. 12, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S1010 to S1020.

[0596] The embodiments described above will be explained in detail below in terms of base station operation.

[0597] S1110 to S1120 described below correspond to operations based on S1010 to S1020 described in FIG. 10. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below can be replaced by the description / embodiment of FIG. 10 corresponding to the operation.

[0598] FIG. 11 is a flowchart illustrating a method according to another embodiment of the present specification.

[0599] Referring to FIG. 11, a method according to another embodiment of the present specification includes a DRX setting transmission step (S1110) and a preference information reception step (S1120) related to the DRX setting.

[0600] In S1110, the base station transmits a Discontinuous Reception (DRX) setting to the terminal, which includes i) information about the DRX timer and ii) information about the DRX cycle.

[0601] For example, the active time may include the time during which the DRX timer is running. The DRX timer may include a first DRX timer that starts based on the beginning of the DRX cycle.

[0602] In S1120, the base station receives preference information related to the DRX setting from the terminal.

[0603] According to one embodiment, the preference information may be related to i) the DRX period and / or ii) the adjustment of the DRX timer. The preference information may be determined based on a time predicted by the terminal.

[0604] Operations based on the above-described S1110 to S1120 can be implemented by the device of FIG. 12. For example, referring to FIG. 12, a base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S1110 to S1120.

[0605] Hereinafter, an apparatus to which the embodiments of the present specification can be applied (an apparatus implementing the method / operation according to the embodiments of the present specification) will be described with reference to FIG. 12.

[0606] FIG. 12 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0607] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).

[0608] The processor (110) performs baseband-related signal processing and may include an upper layer processing unit (111) and a physical layer processing unit (115). The upper layer processing unit (111) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (115) may process operations of the PHY layer. For example, if the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, if the first device (100) is a first terminal device in terminal-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

[0609] The antenna section (120) may include one or more physical antennas, and if it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110) and software, operating systems, applications, etc. related to the operation of the first device (100), and may include components such as a buffer.

[0610] The processor (110) of the first device (100) may be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0611] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).

[0612] The processor (210) performs baseband-related signal processing and may include an upper layer processing unit (211) and a physical layer processing unit (215). The upper layer processing unit (211) may process operations of the MAC layer, RRC layer, or higher upper layers. The physical layer processing unit (215) may process operations of the PHY layer. For example, if the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, if the second device (200) is a second terminal device in terminal-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

[0613] The antenna section (220) may include one or more physical antennas, and may support MIMO transmission and reception if it includes multiple antennas. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210) and software, operating systems, applications, etc. related to the operation of the second device (200), and may include components such as a buffer.

[0614] The processor (210) of the second device (200) may be configured to implement the operation of the terminal in base station-terminal communication (or the operation of the second terminal device in terminal-terminal communication) in the embodiments described in this disclosure.

[0615] In the operation of the first device (100) and the second device (200), the details described in the examples of the present disclosure regarding the base station and terminal (or the first terminal and the second terminal in terminal-to-terminal communication) in base station-to-terminal communication may be applied in the same way, and redundant descriptions are omitted.

[0616] Here, the wireless communication technology implemented in the device of the present disclosure may include LTE, NR, and 6G, as well as Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above.

[0617] Additionally or alternatively, the wireless communication technology implemented in the device of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above.

[0618] Additionally or generally, the wireless communication technology implemented in the device of the present disclosure may include at least one of ZigBee, Bluetooth, and a Low Power Wide Area Network (LPWAN) for low-power communication, but is not limited to the names mentioned above. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

Claims

1. Regarding the method, A step of receiving a DRX (Discontinuous Reception) setting from a base station by a terminal, including i) information about a DRX timer and ii) information about a DRX cycle, The active time includes the time during which the DRX timer is running, and The above DRX timer includes a first DRX timer that starts based on the beginning of the DRX cycle; and The method includes the step of transmitting preference information related to the DRX setting to the base station by the terminal; The above preference information relates to i) the adjustment of the DRX cycle and / or ii) the adjustment of the DRX timer, and A method characterized in that the above preference information is determined based on a time point predicted by the terminal.

2. In Paragraph 1, A method characterized in that the above time includes at least one of i) an expected transmission time related to uplink data and / or ii) an expected arrival time related to downlink data.

3. In Paragraph 1, A method characterized in that the above point in time is based on the output of an AI (Artificial Intelligence) / ML (Machine Learning) model, and the AI / ML model is generated or updated based on data collected during the DRX operation of the terminal.

4. In Paragraph 3, A method characterized in that the above output is generated based on i) historical traffic patterns and ii) jitter characteristics associated with periodic traffic.

5. In Paragraph 1, A method characterized in that the above preference information is transmitted based on the last uplink shared channel before the above DRX cycle is interrupted.

6. In Paragraph 1, A method characterized by transmitting the above preference information based on the fact that the above point in time is not within the above active time.

7. In Paragraph 1, A method characterized by determining, based on the above preference information, at least one of i) the starting point of the DRX cycle, ii) a setting to be applied to the DRX cycle among a long DRX cycle setting and a short DRX cycle setting, iii) the duration of the DRX cycle and / or iv) the starting point of the DRX timer.

8. In Paragraph 1, A method characterized in that the above DRX period and / or the above first DRX timer are adjusted based on instructions from the base station or are adjusted autonomously by the terminal.

9. In Paragraph 8, A method characterized by adjusting the start time of the first DRX timer to an earlier time based on the preference information, based on the fact that the above time point is earlier than the time interval based on the first DRX timer.

10. In Paragraph 8, A method characterized by adjusting the start time of the first DRX timer to a delayed time based on the preference information, based on the fact that the above time point is later than the time interval based on the first DRX timer.

11. In the terminal, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A terminal characterized by the above instructions enabling the terminal to perform all steps of the method according to any one of claims 1 to 10, based on execution by the one or more processors.

12. A device comprising one or more memories and one or more processors connected to the one or more memories, An apparatus characterized in that the above one or more memories store instructions that cause the apparatus to perform all steps of the method according to any one of claims 1 to 10, based on execution by the above one or more processors.

13. In a non-transitory computer-readable storage medium for storing instructions, A non-transitory computer-readable storage medium characterized by instructions executable by one or more processors such that the terminal performs all steps of the method according to any one of claims 1 to 10.

14. Regarding the method, A step of transmitting a Discontinuous Reception (DRX) setting, comprising i) information about a DRX timer and ii) information about a DRX cycle, by a base station to a terminal, The active time includes the time during which the DRX timer is running, and The above DRX timer includes a first DRX timer that starts based on the beginning of the DRX cycle; and The method includes the step of receiving preference information related to the DRX setting from the terminal by the base station; The above preference information relates to i) the adjustment of the DRX cycle and / or ii) the adjustment of the DRX timer, and A method characterized in that the above preference information is determined based on a time point predicted by the terminal.

15. Regarding base stations, One or more transmitters / receivers; One or more processors; and It includes one or more memories connected to the above one or more processors and storing instructions, A base station characterized by the above instructions, based on execution by one or more processors, having the base station perform all steps of the method according to claim 14.