DRX (Discontinuous Reception) implementation method and device and terminal equipment

Abstract

Provided in an embodiment of the present application are a DRX implementation method and apparatus, and a terminal device, the method comprising: a terminal device obtaining one or more DRX configurations, the DRX configurations having at least one of the following characteristics: at least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink; the DRX configuration is related to a service type.

Description

DRX implementation method, device, and terminal equipment Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a method and apparatus for implementing discontinuous reception (DRX), and a terminal device. Background Art

[0002] To save energy in terminal devices, the Discontinuous Reception (DRX) mechanism was introduced. Network equipment configures DRX for terminal devices, which then monitor the Physical Downlink Control Channel (PDCCH) and, based on the monitored PDCCH, receive the Physical Downlink Shared Channel (PDSCH) or transmit the Physical Uplink Shared Channel (PUSCH).

[0003] Current DRX configurations are configured per UE (per UE). Terminals use the same DRX configuration for all transmission scenarios. This lacks flexibility and doesn't achieve optimal energy savings. Furthermore, the current DRX states are relatively simple, which also fails to achieve optimal energy savings.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a DRX implementation method and apparatus, terminal equipment, chip, computer-readable storage medium, computer program product, and computer program.

[0006] The DRX implementation method provided in the embodiment of the present application includes:

[0007] The terminal device obtains one or more DRX configurations, where the DRX configurations have at least one of the following characteristics:

[0008] At least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink;

[0009] The DRX configuration is related to the service type and / or service transmission direction.

[0010] The DRX implementation method provided in the embodiment of the present application includes:

[0011] The terminal device determines the DRX state it is in from at least two DRX states, and different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

[0012] The DRX implementation device provided in the embodiment of the present application is applied to a terminal device, and the device includes:

[0013] An acquiring unit is configured to acquire one or more DRX configurations, where the DRX configuration has at least one of the following characteristics:

[0014] At least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink;

[0015] The DRX configuration is related to the service type.

[0016] The DRX implementation device provided in the embodiment of the present application is applied to a terminal device, and the device includes:

[0017] The determining unit is configured to determine the DRX state from at least two DRX states, where different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

[0018] The terminal device provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned DRX implementation method.

[0019] The chip provided in the embodiment of the present application is used to implement the above-mentioned DRX implementation method.

[0020] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned DRX implementation method.

[0021] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned DRX implementation method.

[0022] The computer program product provided in the embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned DRX implementation method.

[0023] The computer program provided in the embodiment of the present application, when running on a computer, enables the computer to execute the above-mentioned DRX implementation method.

[0024] Through the above technical solution, the DRX mechanism is enhanced. On the one hand, at least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink, which increases the flexibility of the DRX mechanism and helps to further improve the energy-saving space of the terminal device. On the other hand, the DRX configuration is related to the service type and / or service transmission direction, which increases the flexibility of the DRX mechanism and helps to further improve the energy-saving space of the terminal device. On the other hand, a variety of DRX states are defined, and different DRX states correspond to different DRX behaviors and / or energy-saving levels. In this way, by controlling the conversion of the terminal device between various DRX states, it is beneficial to balance the data transmission performance and energy-saving level of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0026] FIG1 is a schematic diagram of an application scenario;

[0027] FIG2 is a schematic diagram of a DRX cycle;

[0028] FIG3 is a flowchart of a DRX implementation method according to an embodiment of the present application;

[0029] FIG4 is a flow chart of a DRX implementation method according to an embodiment of the present application.

[0030] FIG5-1 is a first schematic diagram of transitions between DRX states provided in an embodiment of the present application;

[0031] FIG5-2 is a second schematic diagram of transitions between DRX states provided in an embodiment of the present application;

[0032] FIG5-3 is a third schematic diagram of transitions between DRX states provided in an embodiment of the present application;

[0033] FIG6 is a schematic diagram of the first structure of a DRX implementation apparatus provided in an embodiment of the present application;

[0034] FIG7 is a second schematic diagram of the structure of the DRX implementation device provided in an embodiment of the present application;

[0035] FIG8 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0036] FIG9 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0037] FIG10 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0039] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0040] As shown in Figure 1, a communication system 100 may include a terminal device 110 and a network device 120. The network device 120 may communicate with the terminal device 110 via an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0041] It should be understood that the embodiments of the present application are only illustrative of the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems.

[0042] In the communication system 100 shown in Figure 1, the network device 120 may be an access network device that communicates with the terminal device 110. The access network device may provide communication coverage for a specific geographical area and may communicate with the terminal device 110 (eg, UE) located within the coverage area.

[0043] The network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0044] The terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0045] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolution network, etc.

[0046] The terminal device 110 can be used for device-to-device (D2D) communication.

[0047] The wireless communication system 100 may further include a core network device 130 for communicating with the base station. The core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions that can be implemented by SMF and PGW-C. During the network evolution process, the above-mentioned core network device may also be called other names, or a new network entity may be formed by dividing the functions of the core network, which is not limited in the embodiments of the present application.

[0048] The functional units in the communication system 100 may also establish connections and implement communication via next generation (NG) network interfaces.

[0049] For example, the terminal device establishes an air interface connection with the access network device through the NR interface for transmitting user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (referred to as N1); the access network device, such as the next generation wireless access base station (gNB), can establish a user plane data connection with the UPF through the NG interface 3 (referred to as N3); the access network device can establish a control plane signaling connection with the AMF through the NG interface 2 (referred to as N2); the UPF can establish a control plane signaling connection with the SMF through the NG interface 4 (referred to as N4); the UPF can exchange user plane data with the data network through the NG interface 6 (referred to as N6); the AMF can establish a control plane signaling connection with the SMF through the NG interface 11 (referred to as N11); the SMF can establish a control plane signaling connection with the PCF through the NG interface 7 (referred to as N7).

[0050] Figure 1 exemplarily shows a base station, a core network device and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminal devices within its coverage area, which is not limited in this embodiment of the present application.

[0051] It should be noted that Figure 1 is merely an example of a system applicable to this application. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the associated objects are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; or it can mean that A and B have an association relationship. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between two objects, or that there is an association relationship between the two objects, or a relationship between an indicator and the indicated, a configuration and the configured, and so on. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit its specific implementation method. For example, predefined can refer to a definition in a protocol. It should also be understood that in the embodiments of the present application, the “protocol” can refer to a standard protocol in the field of communications, such as an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0052] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0053] In LTE, the DRX mechanism is introduced to save energy on terminal devices. All services on a terminal device use a single DRX configuration, for example, real-time and non-real-time services use a single DRX configuration. As shown in Figure 2, which provides a basic schematic diagram of the DRX mechanism, the DRX cycle consists of an "On Duration" and a "DRX opportunity." The "On Duration" can also be called an activation period, and the "Opportunity for DRX" can also be called a silent period. During the "On Duration," the terminal device monitors the PDCCH and, based on the monitored PDCCH, receives or transmits data on its scheduled shared channel resources. Alternatively, the terminal device directly receives or transmits data on pre-allocated shared channel resources. During the "Opportunity for DRX," the terminal device does not need to monitor the PDCCH, nor does it receive any downlink data or transmit any uplink data, and is in a power-saving state.

[0054] In LTE, in addition to meeting high throughput requirements, it also requires excellent energy conservation. To this end, two DRX cycles—short DRX and long DRX—are introduced to meet the requirements of both voice and internet services. Switching between the long and short DRX cycles can be achieved using timers or commands, such as Media Access Control (MAC) Control Elements (CEs). Regarding the DRX starting point (i.e. the starting point of On Duration), it is taken into consideration that ① the DRX starting points of the terminal equipment cannot be too concentrated, otherwise it will lead to an unbalanced scheduling load and waste of resources; ② the DRX cycle and the BCCH / MBMS resource position cannot conflict, otherwise it will lead to scheduling restrictions; ③ the DRX starting point must be configured before the semi-continuous scheduling resources, otherwise it may cause a mismatch between the two; it is decided to notify the terminal device of a DRX starting point offset (DRX Start Offset) through RRC signaling, and the following formula is used to determine the DRX starting point: [(SFN*10)+subframe number]modulo(current DRX)=DRX Start Offset, where SFN represents the system frame number corresponding to the DRX starting point, and subframe number represents the subframe number corresponding to the DRX starting point.

[0055] In LTE, the DRX inactivity timer is introduced. This timer can be used to appropriately extend the active period, increasing the scheduling opportunities for terminal devices. Each time a terminal device receives control signaling to schedule new data transmission, the DRX inactivity timer is started. Thereafter, each time the terminal device receives control signaling to schedule new data transmission, the DRX inactivity timer is restarted. The period during which the DRX inactivity timer is running is considered active, thereby extending the active period, increasing the scheduling opportunities for the terminal device and shortening data transmission latency. The introduction of the DRX inactivity timer can, on the one hand, ensure service performance, but on the other hand, it will also increase the power consumption of the terminal device. However, ensuring service performance is more important. For downlink systems using asynchronous Hybrid Automatic Repeat Request (HARQ), it is difficult for the terminal device to determine how long it should remain active while waiting for retransmission scheduling. The DRX inactivity timer can limit this waiting time, thereby saving power.

[0056] In the downlink, to balance power conservation and data transmission performance for terminal devices, two timers are introduced: the HARQ Round Trip Timer (HARQ RTT Timer) and the HARQ Retransmission Timer (HARQ Retransmission Timer). Both timers are defined for the HARQ process, and each HARQ process uses an independent timer. With the adoption of asynchronous HARQ in the uplink, the HARQ RTT Timer and HARQ Retransmission Timer for the uplink process are introduced.

[0057] LTE DRX design is primarily described from the perspective of the downlink direction, where the terminal device monitors the PDCCH or receives the PDSCH on pre-allocated downlink shared channel resources. The impact of uplink transmission on DRX and the interoperability between DRX and other features are as follows:

[0058] 1) DRX and handover measurements

[0059] To ensure the success rate of handovers and the robustness of terminal device mobility, measurement reporting is not restricted by the DRX state. This means that measurement reporting can occur during the DRX silent period. For example, during the silent period, the terminal device uses the Random Access Channel (RACH) to report measurements. After the report is completed, the terminal device is allowed to continuously monitor the PDCCH, thereby receiving handover commands and avoiding radio link failures. During the measurement gap, the terminal device performs inter-frequency measurements and does not monitor the PDCCH.

[0060] 2) DRX and CQI / SRS for uplink transmission

[0061] Based on a comparison of implementation complexity, Physical Uplink Control Channel (PUCCH) resource utilization, scheduling performance, and terminal device power consumption, the decision was made to bundle Channel Quality Indicator (CQI) reporting with DRX, allowing reporting only during the DRX active period. Sounding Reference Signal (SRS) transmission, similar to CQI reporting, is only permitted during the active period.

[0062] 3) DRX and uplink data transmission

[0063] To ensure uplink data transmission performance, it has been decided to allow initiation during any DRX period. While in the DRX sleep period (i.e., silent period), the terminal device is allowed to send a Scheduling Request (SR) using the most recent RACH, thereby initiating uplink data transmission. After receiving the Random Access Response (RAR), the terminal device leaves the sleep period (i.e., silent period) and continuously monitors the PDCCH. If a new data transmission is scheduled, the DRX inactivity timer is restarted, and subsequent behavior is determined by the DRX inactivity timer. For Semi-Persistent Scheduling (SPS), the terminal device can transmit and receive only during the DRX active period.

[0064] In NR, the DRX design mechanism is similar to that of LTE. That is, all services share a common DRX configuration (i.e., a common set of DRX parameters). Because NR uses asynchronous HARQ for both uplink and downlink, independent HARQ RTT timers and HARQ Retransmission timers are configured for the downlink and uplink directions. These two timers are per HARQ process. NR also supports URLLC services. To meet the transmission latency requirements of these services, semi-persistent scheduling (SPS) and configuration grants (CG) are allowed to transmit and receive data even when DRX is inactive.

[0065] NR supports both FR1 and FR2, and can be configured with dual DRX for both FR1 and FR2. Some parameters in dual DRX are shared. Typically, the first DRX is configured with all DRX parameters, while the second DRX is configured with only the independent drx-onDurationTimer and drx-InactivityTimer. Other parameters share the configuration of the first DRX.

[0066] To save energy on the terminal device, the terminal device can report its preferred DRX parameters via the UE Assistance Information message to assist the network device in configuring appropriate DRX parameters, thereby achieving the goal of saving energy on the terminal device. Examples of the preferred DRX parameters of the terminal device include: preferred DRX-Inactivity Timer, preferred DRX-LongCycle, preferred DRX-ShortCycle, and preferred DRX-ShortCycleTimer.

[0067] In the MBS topic, a DRX configuration independent of the unicast service is configured for the MBS service. Furthermore, each MBS service can be configured with its own DRX configuration (each DRX configuration corresponds to a G-RNTI), and they are independent of each other.

[0068] In NR, a DRX configuration includes the following DRX parameters:

[0069] -DRX-onDurationTimer: used to determine the period of time after the start of the DRX cycle;

[0070] -DRX slot offset (drx-SlotOffset): used to determine the delay before starting the DRX state timer;

[0071] -DRX Inactivity Timer: used to determine the period of time after a PDCCH occasion in which a PDCCH is detected and indicates a new uplink or downlink transmission;

[0072] - Downlink DRX retransmission timer (drx-RetransmissionTimerDL): used to determine the maximum time before receiving a downlink retransmission;

[0073] - Uplink DRX retransmission timer (drx-RetransmissionTimerUL): used to determine the maximum time before receiving an uplink retransmission grant;

[0074] -DRX long cycle start offset (drx-LongCycleStartOffset): used to determine the DRX long cycle and the DRX start time offset (drx-StartOffset). drx-StartOffset is used to determine the start time of the DRX long cycle and DRX short cycle (e.g., the subframe corresponding to the start time);

[0075] -DRX short cycle (drx-ShortCycle): This is an optional configuration used to determine the DRX short cycle;

[0076] -DRX Short Cycle Timer (drx-ShortCycleTimer): This is an optional configuration used to determine the duration of the DRX short cycle. Its value refers to the multiple of the DRX short cycle;

[0077] - Downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL): the minimum duration expected by the MAC entity before a downlink allocation for HARQ retransmission;

[0078] - Uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL): The minimum duration before an uplink grant for HARQ retransmission expected by the MAC entity.

[0079] In the above solution, the unit of the DRX parameter is millisecond (ms), which is applicable to services whose DRX cycle is an integer multiple of the ms cycle.

[0080] In the above solution, the downlink DRX retransmission timer, the uplink DRX retransmission timer, the downlink DRX HARQ RTT timer, and the uplink DRX HARQ RTT timer are related to HARQ.

[0081] If the terminal device is configured with DRX, the terminal device needs to monitor the PDCCH during the DRX active time. The DRX active time includes the following situations:

[0082] 1) The running period of any one of the five timers, drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and ra-ContentionResolutionTimer, belongs to the DRX activation time.

[0083] 2) After the terminal device sends a scheduling request (SR) on the physical uplink control channel (PUCCH), the period when the SR is in a pending state belongs to the DRX activation time.

[0084] 3) In the contention-based random access process, the period during which the terminal device has not received an initial transmission indicated by the C-RNTI-scrambled PDCCH after successfully receiving the random access response belongs to the DRX activation time.

[0085] The terminal device determines the start time of drx-onDurationTimer based on whether the current DRX cycle is a short DRX cycle or a long DRX cycle. The specific regulations are as follows:

[0086] 1.1> If the DRX short cycle is used, the SFN and subframe number of the start time of drx-onDurationTimer satisfy the following equation: [(SFN × 10) + subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle);

[0087] 1.2> If DRX long cycle is used, then the SFN and subframe number of the start time of drx-onDurationTimer satisfy the following: [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0088] 2> Start drx-onDurationTimer at the moment when the start time of the subframe determined by the above formula is offset by drx-SlotOffset time slots.

[0089] The conditions for the terminal device to start or restart drx-InactivityTimer are:

[0090] If the terminal device receives a PDCCH indicating an initial downlink or uplink transmission, the terminal device starts or restarts the drx-InactivityTimer.

[0091] The conditions for the terminal device to start and stop drx-RetransmissionTimerDL are:

[0092] When the terminal device receives a PDCCH indicating a downlink transmission, or when the terminal device receives a MAC PDU on the configured downlink grant resources, the terminal device stops the drx-RetransmissionTimerDL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process after completing the transmission of the HARQ process feedback for this downlink transmission.

[0093] If the drx-HARQ-RTT-TimerDL corresponding to a HARQ process of the terminal device times out and the decoding of the downlink data transmitted using this HARQ process is unsuccessful, the terminal device starts the drx-RetransmissionTimerDL corresponding to this HARQ process.

[0094] The conditions for the terminal device to start and stop drx-RetransmissionTimerUL are:

[0095] When the terminal device receives a PDCCH indicating an uplink transmission, or when the terminal device sends a MAC PDU on the configured uplink grant resources, the terminal device stops the drx-RetransmissionTimerUL corresponding to the HARQ process. The terminal device starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process after completing the first PUSCH transmission.

[0096] If the drx-HARQ-RTT-TimerUL corresponding to a HARQ process of the terminal device times out, the terminal device starts the drx-RetransmissionTimerUL corresponding to this HARQ process.

[0097] At present, the DRX configuration configured by the network equipment for the terminal equipment is configured according to the UE granularity (per UE). The terminal equipment will use the same set of DRX configurations for any transmission situation, that is, no matter what service, no matter what bearer data is transmitted and what data is in the bearer, the terminal equipment will use a set of DRX configurations. For DRX parameters related to HARQ, the same DRX parameters are also used. The current DRX configuration method has poor flexibility and does not achieve the optimal energy-saving effect. In addition, the current DRX state is also relatively simple and cannot achieve the optimal energy-saving effect. To this end, the following technical solutions of the embodiments of the present application are proposed.

[0098] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0099] FIG3 is a flowchart of a DRX implementation method according to an embodiment of the present application. As shown in FIG3 , the DRX implementation method includes the following steps:

[0100] Step 301: The terminal device obtains one or more DRX configurations, and the DRX configuration has at least one of the following characteristics: at least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink; the DRX configuration is related to the service type and / or service transmission direction.

[0101] Here, one or more DRX configurations may also be described as one or more sets of DRX configurations, each set of DRX configurations including multiple DRX parameters. As an example, a set of DRX configurations includes at least one of the following DRX parameters: a DRX state timer (drx-onDurationTimer); a DRX slot offset (drx-SlotOffset); a DRX inactivity timer (drx-InactivityTimer); a downlink DRX retransmission timer (drx-RetransmissionTimerDL); an uplink DRX retransmission timer (drx-RetransmissionTimerUL); a DRX long cycle start offset (drx-LongCycleStartOffset); a DRX short cycle (drx-ShortCycle); a DRX short cycle timer (drx-ShortCycleTimer); a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL); and an uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL).

[0102] In some embodiments, the terminal device obtains a DRX configuration, wherein at least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink.

[0103] In some embodiments, the terminal device obtains one or more DRX configurations, wherein the DRX configurations are configured according to service type and / or service transmission direction, that is, the DRX configurations are related to the service type and / or service transmission direction. Furthermore, in some embodiments, at least one DRX parameter in each of the DRX configurations is independently configured and / or independently operated for uplink and downlink.

[0104] Option 1

[0105] In some embodiments, the DRX configuration includes an inactivity timer, which is independently configured and / or independently operated for uplink and downlink. The inactivity timer applied to the downlink is a first inactivity timer, and the inactivity timer applied to the uplink is a second inactivity timer.

[0106] Here, the inactivity timer may also be referred to as a DRX inactivity timer (drx-InactivityTimer). The DRX inactivity timer is independently configured and / or independently operated for uplink and downlink.

[0107] In some implementations, the DRX inactivity timer is uniformly configured for both the uplink and downlink and operates independently for both. The DRX inactivity timer applied to the downlink (i.e., the first inactivity timer) and the DRX inactivity timer applied to the uplink (i.e., the second inactivity timer) are uniformly configured and thus may have a unified name, i.e., the DRX inactivity timer. The DRX inactivity timer applied to the downlink and the DRX inactivity timer applied to the uplink are independently controlled and thus operate independently. The independent operation may be reflected in at least one of the following aspects: whether the timer is started, when the timer is started, or the timer length.

[0108] In some implementations, the DRX inactivity timer is independently configured for the uplink and downlink and operates independently for the uplink and downlink. The DRX inactivity timer applied to the downlink (i.e., the first inactivity timer) and the DRX inactivity timer applied to the uplink (i.e., the second inactivity timer) are independently configured and thus may have different names. The inactivity timer applied to the downlink may also be referred to as the downlink DRX inactivity timer (drx-InactivityTimerDL), and the inactivity timer applied to the uplink may also be referred to as the uplink DRX inactivity timer (drx-InactivityTimerUL). The DRX inactivity timer applied to the downlink and the DRX inactivity timer applied to the uplink are independently controlled and thus operate independently. The independent operation may be reflected in at least one of the following aspects: whether the timer is started, the timer start time, and the timer length.

[0109] The condition for the terminal device to start or restart the first inactivity timer is: if the terminal device receives a PDCCH indicating a downlink initial transmission (or a new transmission scheduling of PDSCH), the terminal device will decide whether to start or restart the first inactivity timer or default to starting or restarting the first inactivity timer.

[0110] The condition for the terminal device to start or restart the second inactivity timer is: if the terminal device receives a PDCCH indicating an uplink initial transmission (or a new transmission scheduling of PUSCH), the terminal device will decide whether to start or restart the second inactivity timer or start or restart the second inactivity timer by default.

[0111] In some implementations, for new transmission scheduling of the first PDSCH, the terminal device determines information related to starting the first inactivity timer, where the information related to starting the first inactivity timer includes at least one of the following:

[0112] first information, where the first information is used to determine whether to start the first inactivity timer;

[0113] second information, where the second information is used to determine a length of the first inactivity timer;

[0114] The third information is used to determine a start time of the first inactivity timer.

[0115] Here, if the first PDSCH is the last PDSCH transmitted by the network device, the first information indicates that the first inactivity timer is not started; if the first PDSCH is not the last PDSCH transmitted by the network device, the first information indicates that the first inactivity timer is started or the start-related information does not include the first information so that the terminal device considers that the first inactivity timer is started by default. For downlink transmission, the network device itself can clearly determine whether the PDSCH transmitted this time is the last PDSCH, thereby indicating whether to start the first inactivity timer through the first information.

[0116] Here, the third information is used to indicate a first time interval, where the first time interval is the time interval between the reception time of the first PDCCH and the start time of the first inactivity timer, and the first PDCCH is used to schedule a new transmission of the first PDSCH. Alternatively, the start-related information does not include the third information, so that the terminal device believes that the first inactivity timer is started after receiving the first PDCCH.

[0117] Here, the first time interval is equal to K0 time slots; or, the first time interval is not equal to K0 time slots; the K0 time slots refer to the time interval between the first PDCCH and the first PDSCH, and K0 is a positive integer.

[0118] In some implementations, the information related to starting the first inactivity timer is indicated by at least one of the following signaling: downlink control information (DCI), radio resource control (RRC) signaling, and MAC CE.

[0119] In some embodiments, for new transmission scheduling of the first PUSCH, the terminal device determines information related to starting the second inactivity timer, where the information related to starting the second inactivity timer includes at least one of the following:

[0120] fourth information, where the fourth information is used to determine whether to start the second inactivity timer;

[0121] fifth information, where the fifth information is used to determine a length of the second inactivity timer;

[0122] Sixth information, where the sixth information is used to determine a start time of the second inactivity timer.

[0123] Here, if the first PUSCH is the last PUSCH transmitted by the terminal device, the fourth information indicates that the second inactivity timer is not started; if the first PUSCH is not the last PUSCH transmitted by the terminal device, the fourth information indicates that the second inactivity timer is started or the startup related information does not include the fourth information so that the terminal device considers that the second inactivity timer is started by default. For uplink transmission, the terminal device can report its own BSR (indicating how much uplink data needs to be transmitted) to the network device. The network device can determine whether the PUSCH transmitted by the terminal device this time is the last PUSCH based on the BSR of the terminal device, thereby indicating whether to start the second inactivity timer through the fourth information.

[0124] Here, the sixth information is used to indicate a second time interval, where the second time interval is the time interval between the reception time of the second PDCCH and the start time of the second inactivity timer, and the second PDCCH is used to schedule the new transmission of the first PUSCH. Alternatively, the start-related information does not include the sixth information, so that the terminal device believes that the second inactivity timer is started after receiving the second PDCCH.

[0125] Here, the second time interval is equal to K2 time slots; or, the second time interval is not equal to K2 time slots; the K2 time slots refer to the time interval between the second PDCCH and the first PUSCH, and K2 is a positive integer.

[0126] In some implementations, the information related to starting the second inactivity timer is indicated through at least one of the following signaling: DCI, RRC signaling, and MAC CE.

[0127] The above solution is described below with reference to specific application examples.

[0128] Application Example 1

[0129] For downlink, the downlink reception objects of the terminal device include: PDCCH, PDSCH, SPS, synchronization signal block (SSB) and channel state information-reference signal (CSI-RS), etc. Here, SPS can be understood as semi-static PDSCH.

[0130] For uplink transmissions, the terminal device transmits information including PUSCH, CG, SRS, and PUCCH. Here, CG can be understood as a semi-static PUSCH. PUCCH can carry information such as SR, CSI, and HARQ feedback. PUSCH transmission is related to PDCCH reception (PDCCH schedules PUSCH transmission). The terminal device determines how to transmit PUSCH based on the received PDCCH.

[0131] The DRX configuration is mainly used to control the terminal device to monitor PDCCH, which can schedule PDSCH transmission or PUSCH transmission. For the downlink, after the terminal device receives the PDCCH for scheduling new PDSCH transmission, it usually starts the inactive timer, which can extend the activation period and increase the downlink scheduling opportunity. For the uplink, after the terminal device receives the PDCCH for scheduling new PUSCH transmission, it usually starts the inactive timer, which can extend the activation period and increase the uplink scheduling opportunity. However, turning on the inactive timer will increase the energy consumption of the terminal device, and not turning on the inactive timer will result in the service performance cannot be guaranteed. How to further save the energy consumption of the terminal device while ensuring the service performance requires a new solution. The following is such a new solution:

[0132] For the downlink, the network device is clear about whether there will be a new PDSCH transmission scheduling next, so the network device can instruct the terminal device whether to start the inactivity timer. Specifically, if the network device does not have a new PDSCH transmission scheduling next, the terminal device is instructed not to start the inactivity timer. If the network device has a new PDSCH transmission scheduling next, the terminal device is instructed to start the inactivity timer.

[0133] For the uplink, 1) the network device can determine whether there will be new PUSCH transmission scheduling based on the BSR of the terminal device, so the network device can instruct the terminal device whether to start the inactivity timer. Specifically, if the BSR is equal to 0 or the delay is tolerable, the terminal device is instructed not to start the inactivity timer, otherwise the terminal device is instructed to start the inactivity timer. Alternatively, 2) the terminal device can know whether there is new data that needs to be scheduled for transmission based on the data to be transmitted, and determine whether to start the inactivity timer. Specifically, if the BSR is equal to 0 or the delay is tolerable, the terminal device is not to start the inactivity timer, otherwise the terminal device starts the inactivity timer.

[0134] Furthermore, the downlink inactivity timer and the uplink inactivity timer are independent, or in other words, independently configured for the downlink and uplink. This can be reflected in at least one of the following aspects: different timer lengths, different timer start times, or different timer start times. For example, in XR services, downlink traffic is busy while uplink traffic is sparse. Therefore, the downlink inactivity timer is longer, while the uplink inactivity timer is shorter.

[0135] In addition, the inactivity timer is started after receiving the PDSCH or sending the PUSCH. The later the inactivity timer is started, the more power saving space it can bring. How to define the start time of the inactivity timer requires a new solution. The following is a new solution:

[0136] For downlink, after receiving the PDCCH, the terminal device receives the PDSCH scheduled by the PDCCH after K0 time slots (the scheduling of the PDSCH is new transmission scheduling), and the value of K0 is indicated by the PDCCH. The terminal device may not monitor the PDCCH during the time period of K0 time slots, thereby achieving the purpose of saving power. This is especially applicable to terminal devices with low complexity and high energy-saving requirements. In view of this, the terminal device may start the inactivity timer at an interval of K0 time slots after receiving the PDCCH. Alternatively, the network device configures or indicates a time interval (for example, through PDCCH to indicate a time interval), which is used to indicate how long the terminal device should wait to start the inactivity timer after receiving the PDCCH. The network device must ensure that no other PDSCHs are scheduled within this time interval, that is, there will be no new transmission scheduling of other PDSCHs within this time interval.

[0137] For the uplink, after receiving the PDCCH, the terminal device sends the PUSCH scheduled by the PDCCH after K2 time slots (the scheduling of the PUSCH is new transmission scheduling), and the value of K2 is indicated by the PDCCH. The terminal device can not monitor the PDCCH during the time period of K2 time slots, so as to achieve the purpose of power saving. This is especially applicable to terminal devices with low complexity and high energy-saving requirements. In view of this, the terminal device can start the inactivity timer at an interval of K2 time slots after receiving the PDCCH. Alternatively, the network device configures or indicates a time interval (for example, through PDCCH to indicate a time interval), which is used to indicate how long the terminal device should wait to start the inactivity timer after receiving the PDCCH. The network device must ensure that no other PUSCHs are scheduled within this time interval, that is, there will be no new transmission scheduling of other PUSCHs within this time interval.

[0138] In new transmission scheduling, whether the inactivity timer is started, the start time of the inactivity timer, and the duration of the inactivity timer can all be dynamically indicated via DCI, or configured and indicated via RRC and MAC CE. This allows network equipment to dynamically determine whether to start the inactivity timer, the start time of the inactivity timer, and the duration of the inactivity timer based on the different service data being transmitted or the current situation of the service to be transmitted, thereby achieving the purpose of power saving for terminal devices. In addition, the inactivity timer can be configured independently for downlink and uplink, which increases DRX flexibility and further improves the power saving space of terminal devices.

[0139] Option 2

[0140] In some embodiments, the DRX configuration includes an RTT timer and / or a retransmission timer, and the RTT timer and / or the retransmission timer are independently configured and / or independently operated for uplink and downlink, the RTT timer applied to the downlink is a first RTT timer, the retransmission timer applied to the downlink is a first retransmission timer, the RTT timer applied to the uplink is a second RTT timer, and the retransmission timer applied to the uplink is a second retransmission timer.

[0141] Here, the RTT timer may also be referred to as a DRX HARQ RTT timer (drx-HARQ-RTT-Timer). The DRX HARQ RTT timer is independently configured and / or operates independently for uplink and downlink. The retransmission timer may also be referred to as a DRX retransmission timer (drx-RetransmissionTimer). The DRX retransmission timer is independently configured and / or operates independently for uplink and downlink.

[0142] In some embodiments, a DRX HARQ RTT timer and / or a DRX retransmission timer are uniformly configured for uplink and downlink and operate independently for uplink and downlink. The DRX HARQ RTT timer and / or DRX retransmission timer applied to the downlink (i.e., the first RTT timer and / or the first retransmission timer) and the DRX HARQ RTT timer and / or DRX retransmission timer applied to the uplink (i.e., the second RTT timer and / or the second retransmission timer) are uniformly configured and thus may have a unified name, i.e., DRX HARQ RTT timer and / or DRX retransmission timer. The DRX HARQ RTT timer and / or DRX retransmission timer applied to the downlink and the DRX HARQ RTT timer and / or DRX retransmission timer applied to the uplink are independently controlled and thus operate independently.

[0143] In some embodiments, the DRX HARQ RTT timer and / or the DRX retransmission timer are configured independently for uplink and downlink, and run independently for uplink and downlink. The DRX HARQ RTT timer and / or DRX retransmission timer applied to the downlink (i.e., the first RTT timer and / or the first retransmission timer) and the DRX HARQ RTT timer and / or DRX retransmission timer applied to the uplink (i.e., the second RTT timer and / or the second retransmission timer) are independently configured and therefore may have different names. The DRX HARQ RTT timer applied to the downlink may also be referred to as a downlink DRX HARQ RTT timer (drx-HARQ-RTT-TimerDL), the DRX retransmission timer applied to the downlink may also be referred to as a downlink DRX retransmission timer (drx-RetransmissionTimerDL), the DRX HARQ RTT timer applied to the uplink may also be referred to as an uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL), and the DRX retransmission timer applied to the uplink may also be referred to as an uplink DRX retransmission timer (drx-RetransmissionTimerUL. The DRX HARQ RTT timer and / or DRX retransmission timer applied to the downlink and the DRX retransmission timer applied to the uplink The HARQ RTT timer and / or the DRX retransmission timer are independently controlled and thus operate independently.

[0144] Here, the second RTT timer and / or the second retransmission timer are timers used by the uplink HARQ process. Here, the second RTT timer may also be referred to as an uplink DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL), and the second retransmission timer may also be referred to as an uplink DRX retransmission timer (drx-RetransmissionTimerUL). Their functions may refer to the description of the aforementioned related solutions.

[0145] For the retransmission scheduling of the first PDSCH, the terminal device determines whether to start the first RTT timer and / or the first retransmission timer.

[0146] In some embodiments, the terminal device determines whether to start the first RTT timer and / or the first retransmission timer based on a first DCI sent by a network device, where the first DCI is used to schedule retransmission of the first PDSCH, and the first DCI carries first indication information, where the first indication information is used to indicate at least one of the following:

[0147] Whether this retransmission is the last one;

[0148] Whether to start the first RTT timer and / or the first retransmission timer for this retransmission.

[0149] Here, if the first indication information indicates that this retransmission is the last retransmission or this retransmission does not start the first RTT timer and / or the first retransmission timer, then the terminal device does not start the first RTT timer and / or the first retransmission timer after receiving the first DCI. If the first indication information indicates that this retransmission is not the last retransmission or this retransmission starts the first RTT timer and / or the first retransmission timer, then the terminal device starts the first RTT timer and / or the first retransmission timer at the corresponding time after receiving the first DCI. Here, the start time of the first RTT timer and the first retransmission timer can refer to the aforementioned related scheme. For downlink transmission, the network device can clearly determine whether this retransmission is the last retransmission, thereby indicating whether this retransmission is the last retransmission and / or whether this retransmission starts the first RTT timer and / or the first retransmission timer through the first indication information.

[0150] For the retransmission scheduling of the first PUSCH, the terminal device determines whether to start the second RTT timer and / or the second retransmission timer.

[0151] In some embodiments, the terminal device determines whether to start the second RTT timer and / or the second retransmission timer based on a second DCI sent by the network device, where the second DCI is used to schedule retransmission of the first PUSCH, and the second DCI carries second indication information, where the second indication information is used to indicate at least one of the following:

[0152] Whether this retransmission is the last one;

[0153] Whether the second RTT timer and / or the second retransmission timer is started for this retransmission;

[0154] or,

[0155] The terminal device determines whether to start the second RTT timer and / or the second retransmission timer based on whether the current retransmission is the last retransmission.

[0156] Here, if the second indication information indicates that this retransmission is the last retransmission or this retransmission does not start the second RTT timer and / or the second retransmission timer, then the terminal device does not start the second RTT timer and / or the second retransmission timer after receiving the second DCI. If the second indication information indicates that this retransmission is not the last retransmission or this retransmission starts the second RTT timer and / or the second retransmission timer, then the terminal device starts the second RTT timer and / or the second retransmission timer at the corresponding time after receiving the second DCI. Here, the start time of the second RTT timer and the second retransmission timer can refer to the aforementioned related scheme. For uplink transmission, the network device can clarify whether this retransmission scheduling is the last retransmission scheduling through the retransmission scheduling situation of the terminal device, thereby indicating whether this retransmission is the last retransmission and / or whether this retransmission starts the second RTT timer and / or the second retransmission timer in the second indication information. Alternatively, the terminal device itself can determine whether this retransmission is the last retransmission. If it is the last retransmission, it determines not to start the second RTT timer and / or the second retransmission timer. If it is not the last retransmission, it determines to start the second RTT timer and / or the second retransmission timer.

[0157] The above solution is described below with reference to specific application examples.

[0158] Application Example 2

[0159] For the downlink, after the PDSCH reaches the maximum number of retransmissions, the terminal device does not know that the PDSCH has reached the maximum number of retransmissions. If it is the last retransmission, the terminal device does not need to start the downlink RTT timer and / or the downlink retransmission timer. The network device can indicate through DCI whether this retransmission is the last retransmission. If the DCI indicates that this retransmission is the last retransmission, the terminal device does not start the downlink RTT timer and / or the downlink retransmission timer. Alternatively, the network device can directly indicate through DCI whether to start the downlink RTT timer and / or the downlink retransmission timer.

[0160] For the uplink, after the PUSCH reaches the maximum number of retransmissions, the terminal device knows that the PDSCH has reached the maximum number of retransmissions. If it is the last retransmission, the terminal device does not need to start the uplink RTT timer and / or the uplink retransmission timer. Alternatively, the network device knows that the PDSCH has reached the maximum number of retransmissions based on the retransmission scheduling of the PUSCH. If it is the last retransmission, the network device can indicate through the DCI whether this retransmission is the last retransmission. If the DCI indicates that this retransmission is the last retransmission, the terminal device does not start the uplink RTT timer and / or the uplink retransmission timer. Alternatively, the network device can directly indicate through the DCI whether to start the uplink RTT timer and / or the uplink retransmission timer.

[0161] Through the above scheme, the network device dynamically indicates whether the current retransmission is the last retransmission, or directly indicates whether to start the RTT timer and / or retransmission timer. The terminal device can not start the RTT timer and / or retransmission timer in the case of the last retransmission, thereby achieving the purpose of saving power for the terminal device.

[0162] Option 3

[0163] In some embodiments, the one or more DRX configurations include a first DRX configuration and / or a second DRX configuration, the first DRX configuration is related to a first type of service, and the second DRX configuration is related to a second type of service.

[0164] In some embodiments, the first DRX configuration and / or the first type of service is associated with a first logical channel list; and / or the second DRX configuration and / or the second type of service is associated with a second logical channel list.

[0165] In some embodiments, each logical channel in the first logical channel group is associated with a DRX index of the first DRX configuration; and / or each logical channel in the second logical channel group is associated with a DRX index of the second DRX configuration.

[0166] In some embodiments, the terminal device receives a third DCI sent by a network device, where the third DCI carries third indication information, and the third indication information is used to indicate a DRX index and / or logical channel list to be used.

[0167] In some embodiments, the terminal device receives first configuration information sent by a network device, where the first configuration information includes an association between a logical channel or a logical channel list and a DRX index.

[0168] In some embodiments, the one or more DRX configurations include a third DRX configuration and / or a fourth DRX configuration, the third DRX configuration is related to downlink services, and the fourth DRX configuration is related to uplink services.

[0169] The above solution is described below with reference to specific application examples.

[0170] Application Example 3

[0171] With the diversification of services in the future, different types of services (such as real-time and non-real-time services) will have different requirements for DRX operations. Therefore, different DRX configurations can be configured based on different service types (or service attributes). In actual applications, the number of DRX configurations should not be too large, otherwise the terminal device will need to maintain multiple DRX cycles simultaneously, which increases implementation complexity. Furthermore, if the DRX cycle length and starting point are not configured appropriately, the terminal device may be active most of the time, which is not conducive to power conservation. To this end, network equipment is configured with a limited number of DRX configurations, each with a corresponding DRX index. Each DRX configuration is associated with a service type. Since different types of services require C-RNTI scheduling and scrambling, different types of services can be grouped into logical channels at L2, that is, different service types are associated with different logical channel lists. Therefore, there is a correspondence between service type, logical channel list, and DRX configuration. Scheduling the logical channel list enables the corresponding DRX configuration to be invoked. Each logical channel within a logical channel list is associated with the same DRX index. Furthermore, only data from logical channels associated with the same DRX index can be multiplexed in a single MAC PDU at the MAC layer.

[0172] For downlink data scheduling, the network device can dynamically specify the affected DRX index through DCI, and the terminal device packages the data on the logical channel associated with the DRX index according to the DCI. Optionally, the network device can pre-configure the association between the logical channel list and the DRX index through RRC signaling.

[0173] For uplink data scheduling, the network device can dynamically specify the affected DRX index and / or logical channel list through DCI, and the terminal device can group the data on the logical channel associated with the DRX index or group the data on the logical channel list according to the DCI. Optionally, the network device can pre-configure the association between the logical channel list and the DRX index through RRC signaling.

[0174] Application Example 4

[0175] For the downlink, the network equipment is very clear about the downlink business situation and can adjust the DRX operation in a timely manner. However, the network equipment does not understand the uplink business situation. If the terminal device needs to indicate the uplink business situation, the delay will be relatively large and the DRX operation will not be adjusted in a timely manner. Furthermore, the characteristics of downlink and uplink services may also be different. For example, the downlink business is busy, while the uplink business is rare or almost non-existent. In view of this, independent DRX configurations can be configured for uplink and downlink services, thereby achieving greater energy saving gains for terminal devices. When the DRX configuration is configured independently for downlink and uplink services, the activation period of the DRX configuration for downlink services and the DRX configuration for uplink services overlaps to the greatest extent possible, which can achieve the maximum power saving gain.

[0176] As a case, the DRX configuration of the uplink service and the DRX configuration of the downlink service can be configured completely independently.

[0177] As another case, a complete DRX configuration may be configured for downlink services, while only a partial DRX configuration may be configured for uplink services, and the other DRX configurations may share the downlink services. Alternatively, a complete DRX configuration may be configured for uplink services, while only a partial DRX configuration may be configured for downlink services, and the other DRX configurations may share the uplink services.

[0178] Through the above solution, different DRX configurations are adopted according to different service types and / or service transmission directions, so as to achieve the purpose of power saving for terminal equipment.

[0179] FIG4 is a second flow chart of a DRX implementation method provided in an embodiment of the present application. As shown in FIG4 , the DRX implementation method includes the following steps:

[0180] Step 401: The terminal device determines the DRX state it is in from at least two DRX states, where different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

[0181] In some embodiments, the at least two DRX states include at least two of the following DRX states: a first DRX state, a second DRX state, a third DRX state, and a fourth DRX state; the energy saving level of the first DRX state is higher than that of the second DRX state, the energy saving level of the second DRX state is higher than that of the third DRX state, and the energy saving level of the third DRX state is higher than that of the fourth DRX state.

[0182] Here, the period corresponding to the first DRX state may also be referred to as a deep silent period, the period corresponding to the second DRX state may also be referred to as a silent period, the period corresponding to the third DRX state may also be referred to as a dormant period, and the period corresponding to the fourth DRX state may also be referred to as an active period. This application does not limit the names of these periods.

[0183] In some implementations, the DRX behaviors of the at least two DRX states are respectively as follows:

[0184] The DRX behavior of the first DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and shutting down radio frequency devices;

[0185] The DRX behavior of the second DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and turning on radio frequency devices;

[0186] The DRX behavior of the third DRX state includes at least one of the following: monitoring the first type of signal, not sending or receiving data, and turning on the radio frequency device;

[0187] The DRX behavior of the fourth DRX state includes at least one of the following: monitoring signals, sending and receiving data, and turning on radio frequency devices.

[0188] Here, the first type of signal is, for example, a low power consumption signal.

[0189] In some embodiments, the fourth DRX state includes a first activation state and a second activation state, and the energy saving level of the first activation state is higher than that of the second activation state.

[0190] Here, the period corresponding to the first activation state may also be referred to as a shallow activation period, and the period corresponding to the second activation state may also be referred to as a full activation period.

[0191] In some embodiments, the DRX behaviors of the first activation state and the second activation state are respectively as follows:

[0192] The monitoring signal in the DRX behavior of the first activation state refers to: monitoring the PDCCH on a designated cell and / or a designated search space;

[0193] The monitoring signal in the DRX behavior of the second activation state refers to monitoring the PDCCH in all search spaces of all activated serving cells.

[0194] Here, the designated cell is a primary cell (PCell); or, the designated cell is a cell configured by a network device.

[0195] Here, the designated search space is a search space configured by the network device.

[0196] In the embodiment of the present application, the at least two DRX states can be converted. Specifically, the conversion between the at least two DRX states is triggered based on at least one of the following: a timer, a command from a network device, or an event.

[0197] In some embodiments, the transition from the first DRX state to the second DRX state is triggered based on a command based on a network device; and / or, the transition from the first DRX state to the third DRX state is triggered based on a command based on a network device; and / or, the transition from the first DRX state to the fourth DRX state is triggered based on a command based on a network device.

[0198] In some embodiments, the transition from the second DRX state to the first DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the second DRX state to the third DRX state is triggered based on a command from a network device; and / or, the transition from the second DRX state to the fourth DRX state is triggered based on at least one of: a timer, an event.

[0199] In some embodiments, the transition from the third DRX state to the first DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the third DRX state to the second DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the third DRX state to the fourth DRX state is triggered based on at least one of: a timer, a command from a network device, an event.

[0200] In some embodiments, the transition from the fourth DRX state to the second DRX state is triggered based on at least one of the following: a timer, an event; and / or, the transition from the fourth DRX state to the third DRX state is triggered based on at least one of the following: a timer, a command from a network device, an event.

[0201] In some embodiments, the transition between the first activation state and the second activation state is triggered based on at least one of the following: a timer, a command from a network device, and an event.

[0202] In some embodiments, the terminal device includes a first communication module and a second communication module, the working energy consumption of the first communication module is lower than that of the second communication module; the command of the network device is received by the first communication module and notified to the second communication module, and the DRX state refers to the DRX state of the second communication module.

[0203] Here, the first communication module is, for example, a wake-up receiver (WUR), and the second communication module is, for example, a main receiver.

[0204] The above solution is described below with reference to specific application examples.

[0205] Application Example 5

[0206] The DRX state consists of an active period and a silent period. During the active period, the terminal device monitors the PDCCH and further receives or transmits data on the shared channel resources scheduled by it based on the monitored PDCCH. Alternatively, the terminal device directly receives or transmits data on the pre-allocated shared channel resources. During the silent period, the terminal does not need to monitor the PDCCH, does not receive any downlink data, and does not transmit any uplink data, and is in a power-saving state.

[0207] Terminal devices can have different power-saving states defined at different levels. These states correspond to different energy-saving levels, resulting in different energy-saving gains for the terminal device. This also includes different DRX behaviors within the terminal device, such as whether it monitors the PDCCH, whether it transmits and receives data, and whether it shuts down the RF components. Furthermore, due to the emergence of auxiliary terminal power-saving signals such as WUS and WUR, the energy consumed by the terminal device when receiving WUS-type PDCCHs and data-scheduled PDCCHs varies. Therefore, to better balance data transmission performance and terminal device energy efficiency, different DRX states are defined, and these states can be converted between each other.

[0208] Table 1 below shows the energy consumption of the terminal device during state transition. State transition refers to transitioning from the current state to a non-sleep state or from a non-sleep state to the current state.

[0209]

[0210] Table 1

[0211] Table 2 below shows the energy consumption model of the terminal device under FR1.

[0212]

[0213] Table 2

[0214] The following defines four DRX states: deep silence period (corresponding to deep silence state), silence period (corresponding to silence state), sleep period (corresponding to sleep state), and active period (corresponding to active state). The transitions between these four states can be implemented based on timers, network device commands, event triggers, etc. All DRX states can be controlled based on network devices. This is because the delay from different DRX states to the active state is different, and the network device can control and adjust the DRX state according to the service conditions. The following describes the DRX behavior of these four DRX states:

[0215] 1) Deep Silence: No signals (such as PDCCH) are monitored, no data (such as PDSCH and PUSCH) is sent or received, and RF components are turned off (for example, active RF components such as power amplifiers, up / down converters, etc.). The Deep Silence period can be understood as a completely energy-saving state.

[0216] 2) Silent period: No signals (such as PDCCH) are monitored, no data (such as PDSCH and PUSCH) is sent or received, and the radio frequency devices are not turned off. The energy consumption during the silent period is higher than that during the deep silent period.

[0217] 3) Sleep period (optional): Monitors low-power signals (such as the wake-up signal (WUS)), does not send or receive any data (such as PDSCH and PUSCH), and does not shut down the radio frequency components. The energy consumption during the sleep period is higher than the silent period.

[0218] 4) Active phase: All signals (such as PDCCH) are monitored, data transmission and reception (such as PDSCH and PUSCH) are performed, and radio frequency devices are turned on. The energy consumption during the active phase is higher than that during the dormant phase.

[0219] Furthermore, the activation period can also be divided into two states: shallow activation period and full activation period. Among them, the PDCCH that needs to be monitored in shallow activation comes from partially activated service cells and / or partial search spaces, and the PDCCH on other service cells and / or other search spaces is not monitored, wherein the partially activated service cells can be PCells or cells indicated by the network device, and the partial search spaces can be search spaces indicated by the network device. The PDCCH that needs to be monitored in the full activation period comes from all activated service cells and / or all search spaces. It should be noted that a service cell can have one or more search spaces, and the PDCCH occasions on the search space are used to monitor PDCCH. The density of PDCCH occasions on different search spaces is different. For search spaces with sparse PDCCH occasions, the energy consumption of monitoring PDCCH on them is relatively high. For search spaces with dense PDCCH occasions, the energy consumption of monitoring PDCCH on them is relatively low.

[0220] Figure 5-1 illustrates a schematic diagram of the transitions between the three DRX states: deep silence period, silence period and activation period. As shown in Figure 5-1, the transition from the deep silence period to the silence period is triggered based on the command of the network device (the command is received through WUR), the transition from the deep silence period to the activation period is triggered based on the command of the network device (the command is received through WUR), the transition from the silence period to the deep silence period is triggered based on the command of the network device (the command is received through WUR) and / or the timer, and the transition between the silence period and the activation period is triggered based on the timer and / or event.

[0221] Figure 5-2 illustrates a schematic diagram of the transitions between the four DRX states: deep silence period, silence period, sleep period and activation period. As shown in Figure 5-2, the transition from the deep silence period to the silence period is triggered based on the command of the network device (the command is received through WUR), the transition from the deep silence period to the sleep period is triggered based on the command of the network device (the command is received through WUR), the transition from the deep silence period to the activation period is triggered based on the command of the network device (the command is received through WUR), the transition from the silence period to the deep silence period is triggered based on the command of the network device (the command is received through WUR), UR receives the command) and / or a timer, the transition from the silent period to the sleep period is triggered based on the command of the network device (the command is received through WUR), the transition from the sleep period to the deep silent period is triggered based on the command of the network device (the command is received through WUR) and / or a timer, the transition from the sleep period to the deep silent period is triggered based on the command of the network device (the command is received through WUR) and / or a timer, the transition between the sleep period and the active period is triggered based on a timer and / or an event and / or a command of the network device (the command is received through WUR).

[0222] Figure 5-3 illustrates a schematic diagram of the transition between the shallow activation period and the full activation period, two DRX states. As shown in Figure 5-3, the transition between the shallow activation period and the full activation period is triggered based on a timer and / or event and / or a command from a network device (the command is received through WUR).

[0223] It should be noted that the DRX state in the above solution refers to the state of the main receiver in the terminal device. The terminal device may also have a WUR, which monitors the commands of the network device and triggers the conversion of the DRX state of the main receiver based on the monitored commands.

[0224] The above technical solution defines a rich set of DRX states with different energy-saving levels. Network equipment can control the transition between DRX states to achieve different energy-saving effects, further improving the energy-saving space of terminal equipment, while also meeting the data transmission performance of terminal equipment.

[0225] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0226] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0227] FIG6 is a schematic diagram of the first structure of a DRX implementation apparatus provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG6 , the DRX implementation apparatus includes:

[0228] The acquiring unit 601 is configured to acquire one or more DRX configurations, where the DRX configurations have at least one of the following characteristics:

[0229] At least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink;

[0230] The DRX configuration is related to the service type.

[0231] In some embodiments, the DRX configuration includes an inactivity timer, which is independently configured and / or independently operated for uplink and downlink. The inactivity timer applied to the downlink is a first inactivity timer, and the inactivity timer applied to the uplink is a second inactivity timer.

[0232] In some embodiments, the apparatus further includes: a determining unit 602, configured to determine, for new transmission scheduling of the first PDSCH, information related to starting the first inactivity timer, where the information related to starting the first inactivity timer includes at least one of the following:

[0233] first information, where the first information is used to determine whether to start the first inactivity timer;

[0234] second information, where the second information is used to determine a length of the first inactivity timer;

[0235] The third information is used to determine a start time of the first inactivity timer.

[0236] In some embodiments, the third information is used to indicate a first time interval, where the first time interval is the time interval between the reception time of the first physical downlink control channel PDCCH and the start time of the first inactivity timer, and the first PDCCH is used to schedule new transmission of the first PDSCH.

[0237] In some embodiments, the first time interval is equal to K0 time slots; or, the first time interval is not equal to K0 time slots; the K0 time slots refers to the time interval between the first PDCCH and the first PDSCH, and K0 is a positive integer.

[0238] In some implementations, the information related to starting the first inactivity timer is indicated by at least one of the following signaling: DCI, RRC signaling, and MAC CE.

[0239] In some embodiments, the apparatus further includes: a determining unit 602, configured to determine, for new transmission scheduling of the first PUSCH, information related to starting the second inactivity timer, where the information related to starting the second inactivity timer includes at least one of the following:

[0240] fourth information, where the fourth information is used to determine whether to start the second inactivity timer;

[0241] fifth information, where the fifth information is used to determine a length of the second inactivity timer;

[0242] Sixth information, where the sixth information is used to determine a start time of the second inactivity timer.

[0243] In some embodiments, the sixth information is used to indicate a second time interval, where the second time interval is the time interval between the reception time of the second PDCCH and the start time of the second inactivity timer, and the second PDCCH is used to schedule a new transmission of the first PUSCH.

[0244] In some embodiments, the second time interval is equal to K2 time slots; or, the second time interval is not equal to K2 time slots; the K2 time slots refer to the time interval between the second PDCCH and the first PUSCH, and K2 is a positive integer.

[0245] In some implementations, the information related to starting the second inactivity timer is indicated through at least one of the following signaling: DCI, RRC signaling, and MAC CE.

[0246] In some embodiments, the DRX configuration includes an RTT timer and / or a retransmission timer, and the RTT timer and / or the retransmission timer are independently configured and / or independently operated for uplink and downlink, the RTT timer applied to the downlink is a first RTT timer, the retransmission timer applied to the downlink is a first retransmission timer, the RTT timer applied to the uplink is a second RTT timer, and the retransmission timer applied to the uplink is a second retransmission timer.

[0247] In some implementations, the determining unit 602 is configured to determine whether to start the first RTT timer and / or the first retransmission timer for the retransmission scheduling of the first PDSCH.

[0248] In some embodiments, the determining unit 602 is configured to determine whether to start the first RTT timer and / or the first retransmission timer based on a first DCI sent by a network device, where the first DCI is used to schedule retransmission of the first PDSCH, and the first DCI carries first indication information, where the first indication information is used to indicate at least one of the following:

[0249] Whether this retransmission is the last one;

[0250] Whether to start the first RTT timer and / or the first retransmission timer for this retransmission.

[0251] In some implementations, the determining unit 602 is configured to determine whether to start the second RTT timer and / or the second retransmission timer for the retransmission scheduling of the first PUSCH.

[0252] In some embodiments, the determining unit 602 is configured to determine whether to start the second RTT timer and / or the second retransmission timer based on a second DCI sent by the network device, where the second DCI is used to schedule retransmission of the first PUSCH, and the second DCI carries second indication information, where the second indication information is used to indicate at least one of the following:

[0253] Whether this retransmission is the last one;

[0254] Whether the second RTT timer and / or the second retransmission timer is started for this retransmission;

[0255] or,

[0256] The terminal device determines whether to start the second RTT timer and / or the second retransmission timer based on whether the current retransmission is the last retransmission.

[0257] In some embodiments, the one or more DRX configurations include a first DRX configuration and / or a second DRX configuration, the first DRX configuration is related to a first type of service, and the second DRX configuration is related to a second type of service.

[0258] In some embodiments, the first DRX configuration and / or the first type of service is associated with a first logical channel list; and / or the second DRX configuration and / or the second type of service is associated with a second logical channel list.

[0259] In some embodiments, each logical channel in the first logical channel group is associated with a DRX index of the first DRX configuration; and / or each logical channel in the second logical channel group is associated with a DRX index of the second DRX configuration.

[0260] In some embodiments, the apparatus further includes: a receiving unit 603, configured to receive a third DCI sent by a network device, wherein the third DCI carries third indication information, and the third indication information is used to indicate a DRX index and / or logical channel list to be used.

[0261] In some implementations, the receiving unit 603 is configured to receive first configuration information sent by a network device, where the first configuration information includes an association between a logical channel or a logical channel list and a DRX index.

[0262] Those skilled in the art should understand that the relevant description of the above-mentioned DRX implementation device in the embodiment of the present application can be understood with reference to the relevant description of the DRX implementation method in the embodiment of the present application.

[0263] FIG7 is a second schematic diagram of the structure of a DRX implementation apparatus provided in an embodiment of the present application, which is applied to a terminal device. As shown in FIG7 , the DRX implementation apparatus includes:

[0264] The determining unit 701 is configured to determine a DRX state from at least two DRX states, where different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

[0265] In some embodiments, the at least two DRX states include at least two of the following DRX states: a first DRX state, a second DRX state, a third DRX state, and a fourth DRX state;

[0266] The energy saving level of the first DRX state is higher than that of the second DRX state, the energy saving level of the second DRX state is higher than that of the third DRX state, and the energy saving level of the third DRX state is higher than that of the fourth DRX state.

[0267] In some embodiments, the DRX behavior of the first DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and turning off radio frequency devices; the DRX behavior of the second DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and turning on radio frequency devices; the DRX behavior of the third DRX state includes at least one of the following: monitoring first-category signals, not sending or receiving data, and turning on radio frequency devices; the DRX behavior of the fourth DRX state includes at least one of the following: monitoring signals, sending or receiving data, and turning on radio frequency devices.

[0268] In some embodiments, the fourth DRX state includes a first activation state and a second activation state, and the energy saving level of the first activation state is higher than that of the second activation state.

[0269] In some embodiments, the monitoring signal in the DRX behavior of the first activation state refers to: monitoring the PDCCH on the specified cell and / or specified search space; the monitoring signal in the DRX behavior of the second activation state refers to: monitoring the PDCCH on all search spaces of all activated service cells.

[0270] In some implementations, the designated cell is a PCell; or, the designated cell is a cell configured by a network device.

[0271] In some implementations, the designated search space is a search space configured by the network device.

[0272] In some embodiments, the transition between the first activation state and the second activation state is triggered based on at least one of the following: a timer, a command from a network device, and an event.

[0273] In some implementations, the transition between the at least two DRX states is triggered based on at least one of the following: a timer, a command from a network device, or an event.

[0274] In some embodiments, the transition from the first DRX state to the second DRX state is triggered based on a command based on a network device; and / or, the transition from the first DRX state to the third DRX state is triggered based on a command based on a network device; and / or, the transition from the first DRX state to the fourth DRX state is triggered based on a command based on a network device.

[0275] In some embodiments, the transition from the second DRX state to the first DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the second DRX state to the third DRX state is triggered based on a command from a network device; and / or, the transition from the second DRX state to the fourth DRX state is triggered based on at least one of: a timer, an event.

[0276] In some embodiments, the transition from the third DRX state to the first DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the third DRX state to the second DRX state is triggered based on at least one of: a timer, a command from a network device; and / or, the transition from the third DRX state to the fourth DRX state is triggered based on at least one of: a timer, a command from a network device, an event.

[0277] In some embodiments, the transition from the fourth DRX state to the second DRX state is triggered based on at least one of the following: a timer, an event; and / or, the transition from the fourth DRX state to the third DRX state is triggered based on at least one of the following: a timer, a command from a network device, an event.

[0278] In some embodiments, the terminal device includes a first communication module and a second communication module, the working energy consumption of the first communication module is lower than that of the second communication module; the command of the network device is received by the first communication module and notified to the second communication module, and the DRX state refers to the DRX state of the second communication module.

[0279] Those skilled in the art should understand that the relevant description of the above-mentioned DRX implementation device in the embodiment of the present application can be understood with reference to the relevant description of the DRX implementation method in the embodiment of the present application.

[0280] Figure 8 is a schematic diagram of a communication device 800 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 800 shown in Figure 8 includes a processor 810, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0281] Optionally, as shown in Figure 8, the communication device 800 may further include a memory 820. The processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0282] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0283] Optionally, as shown in FIG8 , the communication device 800 may further include a transceiver 830 , and the processor 810 may control the transceiver 830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0284] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0285] Optionally, the communication device 800 may specifically be a network device in an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the network device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0286] Optionally, the communication device 800 may specifically be a mobile terminal / terminal device in an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the mobile terminal / terminal device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0287] Figure 9 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 900 shown in Figure 9 includes a processor 910, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0288] Optionally, as shown in FIG9 , the chip 900 may further include a memory 920 , wherein the processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0289] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0290] Optionally, the chip 900 may further include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0291] Optionally, the chip 900 may further include an output interface 940. The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0292] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0293] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0294] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0295] FIG10 is a schematic block diagram of a communication system 1000 provided in an embodiment of the present application. As shown in FIG10 , the communication system 1000 includes a terminal device 1010 and a network device 1020 .

[0296] Among them, the terminal device 1010 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1020 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not repeated here.

[0297] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0298] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0299] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0300] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0301] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0302] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0303] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0304] Optionally, the computer program product can be applied to the network device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0305] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0306] The embodiment of the present application also provides a computer program.

[0307] Optionally, the computer program can be applied to the network device in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the network device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0308] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0309] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0310] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0311] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0312] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0313] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0314] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0315] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for implementing discontinuous reception (DRX), the method comprising: The terminal device obtains one or more DRX configurations, where the DRX configurations have at least one of the following characteristics: At least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink; The DRX configuration is related to the service type and / or service transmission direction.

2. The method according to claim 1, wherein The DRX configuration includes an inactivity timer, which is independently configured and / or independently operated for uplink and downlink. The inactivity timer applied to downlink is a first inactivity timer, and the inactivity timer applied to uplink is a second inactivity timer.

3. The method according to claim 2, wherein: The method further comprises: For new transmission scheduling of the first physical downlink shared channel PDSCH, the terminal device determines the start-related information of the first inactivity timer, where the start-related information of the first inactivity timer includes at least one of the following: first information, where the first information is used to determine whether to start the first inactivity timer; second information, where the second information is used to determine a length of the first inactivity timer; The third information is used to determine a start time of the first inactivity timer.

4. The method according to claim 3, wherein: The third information is used to indicate a first time interval, where the first time interval is the time interval between the reception time of the first physical downlink control channel PDCCH and the start time of the first inactivity timer, and the first PDCCH is used to schedule a new transmission of the first PDSCH.

5. The method according to claim 4, wherein The first time interval is equal to K0 time slots; or, The first time interval is not equal to K0 time slots; The K0 time slots refer to the time interval between the first PDCCH and the first PDSCH, and K0 is a positive integer.

6. The method according to any one of claims 3 to 5, wherein The information related to starting the first inactivity timer is indicated by at least one of the following signaling: downlink control information DCI, radio resource control RRC signaling, and media access control MAC control element CE.

7. The method according to claim 2, wherein: The method further comprises: For new transmission scheduling of the first physical uplink shared channel PUSCH, the terminal device determines the start-related information of the second inactivity timer, where the start-related information of the second inactivity timer includes at least one of the following: fourth information, where the fourth information is used to determine whether to start the second inactivity timer; fifth information, where the fifth information is used to determine a length of the second inactivity timer; Sixth information, where the sixth information is used to determine a start time of the second inactivity timer.

8. The method according to claim 7, wherein: The sixth information is used to indicate a second time interval, where the second time interval is the time interval between the reception time of the second PDCCH and the start time of the second inactivity timer, and the second PDCCH is used to schedule a new transmission of the first PUSCH.

9. The method according to claim 8, wherein The second time interval is equal to K2 time slots; or, The second time interval is not equal to K2 time slots; The K2 time slots refer to the time interval between the second PDCCH and the first PUSCH, and K2 is a positive integer.

10. The method according to any one of claims 7 to 9, wherein The information related to starting the second inactivity timer is indicated through at least one of the following signaling: DCI, RRC signaling, and MAC CE.

11. The method according to any one of claims 1 to 10, wherein The DRX configuration includes an RTT timer and / or a retransmission timer, and the RTT timer and / or the retransmission timer are independently configured and / or independently operated for uplink and downlink. The RTT timer applied to the downlink is a first RTT timer, the retransmission timer applied to the downlink is a first retransmission timer, the RTT timer applied to the uplink is a second RTT timer, and the retransmission timer applied to the uplink is a second retransmission timer.

12. The method according to claim 11, wherein The method further comprises: For the retransmission scheduling of the first PDSCH, the terminal device determines whether to start the first RTT timer and / or the first retransmission timer.

13. The method according to claim 12, wherein: The terminal device determines whether to start the first RTT timer and / or the first retransmission timer, including: The terminal device determines, based on first DCI sent by the network device, whether to start the first RTT timer and / or the first retransmission timer, where the first DCI is used to schedule retransmission of the first PDSCH, and the first DCI carries first indication information, where the first indication information is used to indicate at least one of the following: Whether this retransmission is the last one; Whether to start the first RTT timer and / or the first retransmission timer for this retransmission.

14. The method according to claim 11, wherein The method further comprises: For the retransmission scheduling of the first PUSCH, the terminal device determines whether to start the second RTT timer and / or the second retransmission timer.

15. The method according to claim 14, wherein The terminal device determines whether to start the second RTT timer and / or the second retransmission timer, including: The terminal device determines, based on a second DCI sent by the network device, whether to start the second RTT timer and / or the second retransmission timer, where the second DCI is used to schedule retransmission of the first PUSCH, and the second DCI carries second indication information, where the second indication information is used to indicate at least one of the following: Whether this retransmission is the last one; Whether the second RTT timer and / or the second retransmission timer is started for this retransmission; or, The terminal device determines whether to start the second RTT timer and / or the second retransmission timer based on whether the current retransmission is the last retransmission.

16. The method according to any one of claims 1 to 15, wherein The one or more DRX configurations include a first DRX configuration and / or a second DRX configuration, the first DRX configuration is related to a first type of service, and the second DRX configuration is related to a second type of service.

17. The method according to claim 16, wherein The first DRX configuration and / or the first type of service are associated with a first logical channel list; and / or, The second DRX configuration and / or the second type of service are associated with a second logical channel list.

18. The method according to claim 17, wherein Each logical channel in the first logical channel group is associated with a DRX index of the first DRX configuration; and / or, Each logical channel in the second logical channel group is associated with a DRX index of the second DRX configuration.

19. The method according to any one of claims 16 to 18, wherein The method further comprises: The terminal device receives a third DCI sent by a network device, where the third DCI carries third indication information, and the third indication information is used to indicate the DRX index and / or logical channel list to be used.

20. The method according to any one of claims 16 to 19, wherein The method further comprises: The terminal device receives first configuration information sent by the network device, where the first configuration information includes an association between a logical channel or a logical channel list and a DRX index.

21. A DRX implementation method, the method comprising: The terminal device determines the DRX state it is in from at least two DRX states, and different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

22. The method according to claim 21, wherein The at least two DRX states include at least two of the following DRX states: a first DRX state, a second DRX state, a third DRX state, and a fourth DRX state; The energy saving level of the first DRX state is higher than that of the second DRX state, the energy saving level of the second DRX state is higher than that of the third DRX state, and the energy saving level of the third DRX state is higher than that of the fourth DRX state.

23. The method according to claim 22, wherein The DRX behavior of the first DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and shutting down radio frequency devices; The DRX behavior of the second DRX state includes at least one of the following: not monitoring signals, not sending or receiving data, and turning on radio frequency devices; The DRX behavior of the third DRX state includes at least one of the following: monitoring the first type of signal, not sending or receiving data, and turning on the radio frequency device; The DRX behavior of the fourth DRX state includes at least one of the following: monitoring signals, sending and receiving data, and turning on radio frequency devices.

24. The method according to claim 22 or 23, wherein The fourth DRX state includes a first activation state and a second activation state, and the energy saving level of the first activation state is higher than that of the second activation state.

25. The method according to claim 24, wherein The monitoring signal in the DRX behavior of the first activation state refers to: monitoring the PDCCH on a designated cell and / or a designated search space; The monitoring signal in the DRX behavior of the second activation state refers to monitoring the PDCCH in all search spaces of all activated serving cells.

26. The method according to claim 25, wherein The designated cell is a primary cell PCell; or The designated cell is a cell configured by the network device.

27. The method according to claim 25 or 26, wherein The specified search space is a search space configured by the network device.

28. The method according to any one of claims 24 to 27, wherein The transition between the first activation state and the second activation state is triggered based on at least one of the following: a timer, a command of a network device, and an event.

29. The method according to any one of claims 22 to 28, wherein The transition between the at least two DRX states is triggered based on at least one of the following: a timer, a command from a network device, or an event.

30. The method according to any one of claims 22 to 29, wherein The transition from the first DRX state to the second DRX state is triggered based on a command from a network device; and / or, The transition from the first DRX state to the third DRX state is triggered based on a command from a network device; and / or, The transition from the first DRX state to the fourth DRX state is triggered based on a command from a network device.

31. The method according to any one of claims 22 to 30, wherein The transition from the second DRX state to the first DRX state is triggered based on at least one of the following: a timer, a command of a network device; and / or, The transition from the second DRX state to the third DRX state is triggered based on a command of a network device; and / or, The transition from the second DRX state to the fourth DRX state is triggered based on at least one of the following: a timer, an event.

32. The method according to any one of claims 22 to 31, wherein The transition from the third DRX state to the first DRX state is triggered based on at least one of the following: a timer, a command of a network device; and / or, The transition from the third DRX state to the second DRX state is triggered based on at least one of the following: a timer, a command from a network device; and / or, The transition from the third DRX state to the fourth DRX state is triggered based on at least one of the following: a timer, a command from a network device, and an event.

33. The method according to any one of claims 22 to 32, wherein The transition from the fourth DRX state to the second DRX state is triggered based on at least one of the following: a timer, an event; and / or, The transition from the fourth DRX state to the third DRX state is triggered based on at least one of the following: a timer, a command from a network device, and an event.

34. The method according to any one of claims 28 to 33, wherein The terminal device includes a first communication module and a second communication module, and the working energy consumption of the first communication module is lower than that of the second communication module; The command of the network device is received by the first communication module and notified to the second communication module, and the DRX state refers to the DRX state of the second communication module.

35. A DRX implementation device, applied to a terminal device, comprising: An acquiring unit is configured to acquire one or more DRX configurations, where the DRX configuration has at least one of the following characteristics: At least one DRX parameter in the DRX configuration is independently configured and / or independently operated for uplink and downlink; The DRX configuration is related to the service type.

36. A DRX implementation apparatus, applied to a terminal device, comprising: The determining unit is configured to determine the DRX state from at least two DRX states, where different DRX states in the at least two DRX states correspond to different DRX behaviors and / or energy saving levels.

37. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to perform the method according to any one of claims 1 to 20, or the method according to any one of claims 21 to 34.

38. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 20, or the method according to any one of claims 21 to 34.

39. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 20, or the method according to any one of claims 21 to 34.

40. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 20, or any one of claims 21 to 34.

41. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 20, or any one of claims 21 to 34.

Images