DRX implementation method and device, terminal equipment and network equipment

Abstract

The embodiment of the invention provides a DRX implementation method and device, terminal equipment and network equipment, and the method comprises the steps that the terminal equipment obtains DRX configuration, and the DRX configuration is used for determining a plurality of DRX wake-up periods in a DRX period; wherein the DRX period is a long DRX period; or, the DRX period is a short DRX period.

Description

A DRX implementation method and device, terminal equipment, and network 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), a terminal device, and a network device. Background Art

[0002] To save energy on terminal devices, a discontinuous reception (DRX) mechanism is introduced. Network equipment configures a DRX configuration for the terminal device, which then uses the DRX configuration to monitor the physical downlink control channel (PDCCH).

[0003] However, although the current DRX mechanism can achieve energy saving for terminal devices, it also has some disadvantages. For example, the DRX wake-up period configured by the DRX configuration cannot be adapted to the service transmission cycle, resulting in the inability to guarantee service transmission.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a DRX implementation method and apparatus, terminal equipment, network 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 a DRX configuration, where the DRX configuration is used to determine a plurality of DRX wake-up periods within a DRX cycle; wherein,

[0008] The DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

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

[0010] The network device sends a DRX configuration to the terminal device, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

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

[0012] an acquiring unit, configured to acquire a DRX configuration, where the DRX configuration is used to determine a plurality of DRX wake-up periods within a DRX cycle;

[0013] The DRX cycle is a long DRX cycle; or the DRX cycle is a short DRX cycle.

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

[0015] A sending unit is used to send a DRX configuration to a terminal device, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

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

[0017] The network 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.

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

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

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

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

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

[0023] The above technical solution proposes an enhanced DRX implementation method. This method uses DRX configuration to configure multiple DRX wake-up periods within a DRX cycle, clarifying whether multiple DRX wake-up periods are used for long DRX cycles or multiple DRX wake-up periods are used for short DRX cycles. This enhanced DRX implementation method allows the multiple DRX wake-up periods configured in the DRX configuration to flexibly adapt to services with different transmission cycles, ensuring service transmission performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] 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:

[0025] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application;

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

[0027] FIG3-1 is a first schematic diagram of an aperiodic DRX wake-up period provided in an embodiment of the present application;

[0028] FIG3-2 is a second schematic diagram of an aperiodic DRX wake-up period provided in an embodiment of the present application;

[0029] FIG3-3 is a third schematic diagram of an aperiodic DRX wake-up period provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0051] URLLC / XR

[0052] In the future, the 3rd Generation Partnership Project (3 rdThe 3GPP (3rd Generation Partnership Project) system will provide increasingly broad and in-depth support for vertical industries. For example, Ultra-Reliable Low-Latency Communications (URLLC) supports the transmission of services such as factory automation, transport industry, and smart electrical power distribution over 5G systems. Extended Reality (XR) supports the transmission of services such as augmented reality (AR), virtual reality (VR), mixed reality (MR), and cloud gaming. These services generally have reliability and latency requirements, and resource scheduling for terminal devices must meet data transmission Quality of Service (QoS) requirements. For terminal devices, power consumption must also be addressed to avoid unnecessary power consumption. Furthermore, given the large number of terminal devices supporting these services, resource allocation must ensure network capacity.

[0053] Typically, URLLC / XR services must support a minimum latency of 0.5ms and 99.999% reliability. Services can be pseudo-periodic, meaning that service arrival times exhibit jitter. In other words, services arrive not at a specific time but at any time within a time range. Furthermore, service periods can be non-integer. Furthermore, the arrival times of different service flows within the same service can vary significantly.

[0054] DRX mechanism

[0055] Network equipment can configure DRX configuration for terminal devices through RRC dedicated signaling, so that the terminal device can monitor the PDCCH discontinuously to achieve the purpose of terminal device power saving. Each Media Access Control (MAC) entity has a DRX configuration. As an example, the parameters configured in the DRX configuration are:

[0056] -DRX state timer (drx-onDurationTimer): used to determine the period of time after the start of the DRX cycle (DRX cycle), which is called the DRX wake-up period or DRX duration (DRX On Duration) (also referred to as On Duration);

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

[0058] -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;

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

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

[0061] -DRX long cycle start offset (drx-LongCycleStartOffset): used to determine the DRX long cycle (drx-LongCycle) and DRX start 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);

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

[0063] -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;

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

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

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

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

[0068] 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:

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

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

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

[0072] 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:

[0073] 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);

[0074] 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;

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

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

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

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

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

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

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

[0082] 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 resource, 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 repetition of the PUSCH.

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

[0084] It can be seen from the above DRX mechanism that after completing uplink transmission or completing ACK / NACK feedback for downlink transmission, the terminal device will first start a DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL for uplink transmission and drx-HARQ-RTT-TimerDL for downlink transmission). The terminal device is in sleep state during the operation of the DRX HARQ RTT timer and does not monitor the PDCCH. The terminal device will start monitoring the uplink retransmission scheduling after the timer expires, or determine whether to start monitoring the downlink retransmission scheduling based on the feedback.

[0085] As shown in Figure 2, the DRX cycle consists of "On Duration" and "DRX Opportunity for DRX". During the On Duration time, the terminal device is in the DRX active time; if the terminal does not receive the PDCCH within the On Duration time, it will stop monitoring and switch to the DRX inactive time during the "Opportunity for DRX" time. The terminal device does not receive the PDCCH to reduce power consumption (that is, the terminal device is in a dormant period).

[0086] The start time of the DRX cycle (that is, the start time of the On Duration) can be determined using the following formula:

[0087] [(SFN*10)+subframe number]modulo(current DRX)=drx-StartOffset;

[0088] Among them, SFN represents the system frame number corresponding to the start time of the DRX cycle, subframe number represents the subframe number corresponding to the start time of the cycle, current DRX represents the current DRX cycle, which can be a DRX long cycle (drx-LongCycle) or a DRX short cycle (drx-ShortCycle), drx-StartOffset represents the DRX start offset (drx-StartOffset), and modulo represents the remainder operation.

[0089] While the current DRX mechanism can achieve energy savings for terminal devices, it also has some drawbacks. For example, the DRX wake-up period configured by the DRX configuration cannot be adapted to the service transmission cycle, resulting in service transmission being unguaranteed. In view of these drawbacks of the DRX mechanism, the following technical solutions are proposed in the embodiments of this application.

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

[0091] For some specific services, such as XR services, their service transmission cycle (referred to as service cycle for short) is non-integer ms. For example, the service frame rates of 60fps, 90fps, and 120fps correspond to service cycles of 1 / 60s (16.67ms), 1 / 90s (11.11ms), and 1 / 120s (8.33ms), respectively. In order to meet the latency requirements of specific services and ensure the energy-saving gain of terminal equipment, DRX configuration or DRX operation needs to meet the characteristics of non-integer ms cycle of specific services. Based on RRC semi-static configuration, there are three ways to achieve the adaptation of DRX wake-up period (also known as DRX on duration) to the service cycle:

[0092] Method 1: Configure multiple DRX cycles through RRC signaling. These multiple DRX cycles are combined into a DRX pattern. This DRX pattern is configured in a periodic manner. As an example, Figure 3-1 shows a DRX pattern composed of a 16ms DRX cycle, a 17ms DRX cycle, and a 17ms DRX cycle. The starting period of each DRX cycle is the DRX wake-up period (also known as the DRX on duration). The duration of the DRX wake-up period is determined based on the drx-onDurationTimer. The three DRX wake-up periods within the 50ms DRX pattern can adapt to three 16.67ms service cycles.

[0093] Method 2: Configure multiple DRX start offsets through RRC signaling. These multiple DRX start offsets are used to determine the start times of multiple DRX wake-up periods. As an example, Figure 3-2 shows DRX start offsets 1, 2, and 3. These three DRX start offsets determine the start times of three DRX wake-up periods. The duration of each DRX wake-up period is determined by the drx-onDurationTimer. Three DRX wake-up periods within a 50ms DRX cycle can accommodate three 16.67ms service cycles.

[0094] Method 3: Two parameters are introduced: the time offset and the number of DRX cycles, n. After n DRX cycles, the DRX start offset of the DRX wake-up period is added to the configured offset. As an example, Figure 3-3 shows the case where n = 4 and offset = 6. The DRX cycle is 16 ms, and the service cycle is 1 / 60 ms. After four DRX cycles, the DRX start offset of the DRX wake-up period is added to 6 ms. Therefore, the start time of the fifth DRX cycle is 60 + 6 = 66 ms. The five DRX wake-up periods within these five DRX cycles can accommodate five 16.67 ms service cycles.

[0095] The technical solution of the embodiment of this application is mainly described with respect to the details and expansion solutions in the above-mentioned method 2.

[0096] It should be noted that the “DRX wake-up period” described in the embodiments of the present application may also be referred to as “DRX onduration” or “onduration” or “on” or “duration”.

[0097] It should be noted that the “DRX start offset” described in the embodiments of the present application may also be referred to as “drx-StartOffset” or “StartOffset”.

[0098] It should be noted that the “long DRX cycle” described in the embodiments of the present application may also be referred to as “drx-LongCycle”.

[0099] It should be noted that the “short DRX cycle” described in the embodiments of the present application may also be referred to as “drx-ShortCycle”.

[0100] It should be noted that the technical solutions in the embodiments of the present application can be applied to, but are not limited to, 5G, 6G and future communication systems.

[0101] FIG4 is a 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:

[0102] Step 401: The terminal device obtains a DRX configuration, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

[0103] Here, the DRX configuration is configured by a network device. In some implementations, the DRX configuration is configured by the network device via RRC signaling.

[0104] For a network device, the network device sends a DRX configuration to a terminal device, where the DRX configuration is used to determine a plurality of DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

[0105] In the embodiment of the present application, a long DRX cycle may be configured in the DRX configuration, and optionally, a short DRX cycle may also be configured. That is, in the DRX configuration, a long DRX cycle is a mandatory configuration, and a short DRX cycle is an optional configuration.

[0106] In an embodiment of the present application, the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle.

[0107] In some embodiments, the DRX configuration is used to configure multiple DRX start offsets, and the multiple DRX start offsets are used to determine the start time of the multiple DRX wake-up periods, and the duration of each DRX wake-up period in the multiple DRX wake-up periods is determined based on the duration of the first timer.

[0108] Here, the time corresponding to the DRX wake-up period is also the time corresponding to the running period of the first timer. It can be understood that the length of the DRX wake-up period is equal to the length of the first timer, and the start time of the DRX wake-up period is the start time of the first timer.

[0109] Here, the first timer may also be referred to as "drx-onDurationTimer".

[0110] In some embodiments, the DRX configuration includes a first parameter and a second parameter, the first parameter being used to configure a long DRX cycle and a first DRX start offset, and the second parameter being used to configure at least one DRX start offset; wherein the first DRX start offset and the at least one DRX start offset are used to determine multiple DRX wake-up periods within the DRX cycle; or, the at least one DRX start offset is used to determine multiple DRX wake-up periods within the DRX cycle. Here, the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

[0111] Here, the first parameter may be called "drx-LongCycleStartOffset", which is used to configure a long DRX cycle and a DRX start offset, which is called a "first DRX start offset". In some implementations, the first DRX start offset may also be called a default DRX start offset.

[0112] As a case, multiple DRX wake-up periods are configured on a long DRX cycle. For this case, the DRX configuration is used to determine multiple DRX wake-up periods within the long DRX cycle. The DRX configuration includes a first parameter and a second parameter. The first parameter is used to configure the long DRX cycle and the first DRX start offset, and the second parameter is used to configure at least one DRX start offset; wherein the first DRX start offset and the at least one DRX start offset are used to determine the start time of multiple DRX wake-up periods within the long DRX cycle.

[0113] As another case, multiple DRX wake-up periods are configured on a short DRX cycle. For this case, the DRX configuration is used to determine multiple DRX wake-up periods within the short DRX cycle. The DRX configuration includes a first parameter, a second parameter, and a third parameter. The first parameter is used to configure the long DRX cycle and the first DRX start offset, the second parameter is used to configure at least one DRX start offset, and the third parameter is used to configure the short DRX cycle; wherein the first DRX start offset and the at least one DRX start offset are used to determine the start time of multiple DRX wake-up periods within the short DRX cycle, or the at least one DRX start offset is used to determine the start time of multiple DRX wake-up periods within the short DRX cycle.

[0114] The start time of the DRX wake-up period can be determined using the following formula:

[0115] [(SFN*10)+subframe number]modulo(DRX cycle)=drx-StartOffset;

[0116] Among them, SFN represents the system frame number corresponding to the start time of the DRX wake-up period, subframe number represents the subframe number corresponding to the start time of the DRX wake-up period, DRX cycle represents the DRX cycle, which can be a DRX long cycle (drx-LongCycle) or a DRX short cycle (drx-ShortCycle), drx-StartOffset represents the DRX start offset, and modulo represents the remainder operation.

[0117] In one example, multiple DRX wake-up periods are configured on a long DRX cycle. Specifically, the parameter drx-LongCycleStartOffset (i.e., the first parameter) is configured in the DRX configuration (DRX-Config). This parameter configures the long DRX cycle and a DRX start offset (i.e., the first DRX start offset). This DRX start offset may also be referred to as the default DRX start offset. In addition, the DRX configuration (DRX-Config) further configures a DRX start offset list (i.e., the second parameter), which configures at least one DRX start offset. The DRX start offset of the long DRX cycle may include a DRX start offset configured by drx-LongCycleStartOffset and at least one DRX start offset configured by the DRX start offset list. For any DRX start offset of the long DRX cycle, the start time of the DRX wake-up period may be determined by the following formula:

[0118] [(SFN*10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0119] SFN represents the system frame number corresponding to the start time of the DRX wake-up period, subframe number represents the subframe number corresponding to the start time of the DRX wake-up period, drx-LongCycle represents the DRX long cycle, drx-StartOffset represents the DRX start offset, and modulo represents the remainder operation.

[0120] When multiple DRX wake-up periods are configured on a long DRX cycle, parameters related to the short DRX cycle, such as the DRX short cycle (drx-ShortCycle) and the DRX short cycle timer (drx-ShortCycleTimer), may not be configured in the DRX configuration (DRX-Config). Since the energy consumption of terminal devices is higher with a short DRX cycle compared to a long DRX cycle, not configuring parameters related to the short DRX cycle can save energy on the terminal device to a certain extent. On the other hand, since multiple DRX wake-up periods are configured on a long DRX cycle, service transmission requirements can be met even without a short DRX cycle.

[0121] In one example, multiple DRX wake-up periods are configured on a short DRX cycle. Specifically, the parameter drx-LongCycleStartOffset (i.e., the first parameter) is configured in the DRX configuration (DRX-Config). This parameter configures the long DRX cycle and a DRX start offset (i.e., the first DRX start offset). This DRX start offset can also be referred to as the default DRX start offset. In addition, the DRX configuration (DRX-Config) also configures a DRX start offset list (i.e., the second parameter), which configures at least one DRX start offset. At the same time, the DRX configuration (DRX-Config) also configures parameters related to the short DRX cycle, such as the DRX short cycle (drx-ShortCycle) and the DRX short cycle timer (drx-ShortCycleTimer). The DRX start offset of the short DRX cycle may include at least one DRX start offset configured by the DRX start offset list, or may also include the first DRX start offset configured by drx-LongCycleStartOffset and at least one DRX start offset configured by the DRX start offset list. For any DRX start offset of the short DRX cycle, the start time of the DRX wake-up period can be determined by the following formula:

[0122] [(SFN*10)+subframe number]modulo(drx-ShortCycle)=drx-StartOffset;

[0123] SFN represents the system frame number corresponding to the start time of the DRX wake-up period, subframe number represents the subframe number corresponding to the start time of the DRX wake-up period, drx-ShortCycle represents the DRX short cycle, drx-StartOffset represents the DRX start offset, and modulo represents the remainder operation.

[0124] When the terminal device enters the DRX short cycle, the DRX short cycle timer (drx-ShortCycleTimer) is started. When the DRX short cycle timer times out, the terminal device enters the DRX long cycle from the short DRX cycle.

[0125] Through the above solution, an enhanced DRX mechanism is implemented. Under the enhanced DRX mechanism, the technical solution of the embodiment of the present application also introduces the following solution.

[0126] Option 1

[0127] In some embodiments, the DRX wake-up period corresponding to the first part of the DRX start biases in the multiple DRX start biases is in a deactivated state when the first condition is met; and / or, the DRX wake-up period corresponding to the second part of the DRX start biases in the multiple DRX start biases is in an activated state when the first condition is met.

[0128] In some implementations, the first condition is that a second timer has expired.

[0129] In some embodiments, the start of the second timer is triggered based on at least one of the following:

[0130] DRX inactivity timer expires;

[0131] The terminal device receives a first command sent by the network device, where the first command is used to instruct to start the second timer.

[0132] Here, the first command may be an L2 command, such as a MAC CE.

[0133] In the above solution, the second timer is different from the DRX short cycle timer; or, the second timer is the DRX short cycle timer.

[0134] In the above solution, the first part of the DRX start offset and / or the second part of the DRX start offset are configured by a network device or agreed upon by a protocol.

[0135] In some embodiments, the first part of the DRX start bias includes all or part of the DRX start bias in at least one DRX start bias configured by the second parameter in the DRX configuration, and the second part of the DRX start bias includes the first DRX start bias configured by the first parameter in the DRX configuration.

[0136] It should be noted that when the DRX wake-up period is in the deactivated state, the terminal device no longer monitors the PDCCH and / or receives service data during the DRX wake-up period. When the DRX wake-up period is in the activated state, the terminal device monitors the PDCCH and / or receives service data during the DRX wake-up period.

[0137] In the above solution, by deactivating a portion of the DRX wake-up periods corresponding to the DRX start offsets, the purpose of energy saving of the terminal device can be achieved to a certain extent.

[0138] In one example, the second timer is Tx, and when the timer Tx times out, the terminal device may deactivate a portion of the DRX wake-up periods corresponding to the DRX start offsets, while keeping the DRX wake-up periods corresponding to other DRX start offsets in an activated state. Which DRX wake-up periods corresponding to the DRX start offsets are deactivated may be configured by the network device, or, by default, at least one DRX wake-up period corresponding to the DRX start offset configured by the second parameter is deactivated. For example, when the timer Tx times out, only the DRX wake-up period corresponding to the default DRX start offset may be activated, and the DRX wake-up periods corresponding to other DRX start offsets are deactivated. The timer Tx may be a separately configured timer or a timer drx-ShortCycleTimer. When the drx-InactivityTimer timer times out or the terminal device receives an L2 command (such as MAC CE) sent by the network device, the terminal device starts the timer Ta.

[0139] In some embodiments, the DRX wake-up periods corresponding to all or part of the multiple DRX start offsets are in an activated state when a second condition is met.

[0140] In some embodiments, by default, the DRX wake-up periods corresponding to all the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met; or, in a case where the network device configures an activated DRX start bias, the DRX wake-up periods corresponding to all or part of the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met, and the all or part of the DRX start biases are the activated DRX start biases configured by the network device.

[0141] Here, by default, the DRX wake-up periods corresponding to all DRX start biases in the multiple DRX start biases may be activated. In the case where the network device configures an activated DRX start bias (the network device may configure all or part of the DRX start bias to be activated), the terminal device determines which DRX wake-up periods corresponding to the DRX start biases to activate based on the configuration of the network device.

[0142] In the above solution, the demand for service data transmission can be met by activating the DRX wake-up period corresponding to the DRX start offset.

[0143] In some embodiments, the second condition includes at least one of the following:

[0144] The terminal device receives a second command sent by the network device, where the second command is used to indicate activation and / or deactivation of a DRX start offset;

[0145] The terminal device receives any scheduling command;

[0146] The terminal device receives any data;

[0147] The terminal device sends arbitrary data;

[0148] The terminal device receives a scheduling command for a designated service;

[0149] The terminal device receives data of a designated service;

[0150] The terminal device sends data of a designated service.

[0151] Here, the second command may be an L2 command, such as a MAC CE.

[0152] Here, the scheduling command is used to schedule the transmission of downlink data or to schedule the transmission of uplink data.

[0153] Here, the terminal device receives any data, including at least one of the following:

[0154] The terminal device receives any dynamically scheduled data;

[0155] The terminal device receives any data on the semi-persistent scheduling SPS resources.

[0156] Here, the terminal device sends any data, including at least one of the following:

[0157] The terminal device sends any dynamically scheduled data;

[0158] The terminal device sends arbitrary data on the configured authorized CG resources.

[0159] Here, the terminal device receives data of a designated service, including at least one of the following:

[0160] The terminal device receives data of a dynamically scheduled designated service;

[0161] The terminal device receives data of a designated service on the SPS resource.

[0162] Here, the terminal device sends data of a designated service, including at least one of the following:

[0163] The terminal device sends data of a dynamically scheduled designated service;

[0164] The terminal device sends data of the specified service on the CG resource.

[0165] Here, the designated service may be, for example, an XR service.

[0166] In some embodiments, the designated service has a corresponding relationship with one or more logical channel identifiers. For received data or sent data, the terminal device determines whether the data belongs to the designated service based on the logical channel where the data is located and the corresponding relationship.

[0167] Here, the terminal device may determine the logical channel where the data is located by any of the following methods:

[0168] Method 1) The network device sends a first RRC signaling to the terminal device, and the terminal device receives the first RRC signaling sent by the network device, where the first RRC signaling is used to configure a correspondence between a logical channel identifier and a CG resource or the first RRC signaling is used to configure a correspondence between a logical channel identifier and an SPS resource; the correspondence and the CG or SPS resource where the data is located are used to determine the logical channel where the data is located. The terminal device determines the logical channel where the data is located based on the CG resource or SPS resource where the data is located and the correspondence.

[0169] Here, the configured grant resource refers to the uplink periodic resource. The SPS resource refers to the downlink periodic resource. For uplink transmission, the terminal device determines the logical channel where the data is located based on the correspondence between the CG resource where the data is located, the logical channel identifier, and the CG resource. For downlink transmission, the terminal device determines the logical channel where the data is located based on the correspondence between the SPS resource where the data is located, the logical channel identifier, and the SPS resource.

[0170] The above method 1) is applicable to the cases of CG and SPS.

[0171] Method 2) The network device sends a scheduling command to the terminal device, and the terminal device receives the scheduling command sent by the network device, where the scheduling command is used to schedule the transmission of downlink data or to schedule the transmission of uplink data, and the scheduling command carries first indication information, where the first indication information is used to indicate the logical channel where the data scheduled for transmission by the scheduling command is located.

[0172] The above method 2) is applicable to the cases of uplink dynamic scheduling and downlink dynamic scheduling.

[0173] Method 3) The network device sends data to the terminal device, and the data carries the logical channel identifier corresponding to the data; the terminal device decodes the received data to obtain the logical channel identifier corresponding to the data, and determines the logical channel where the data is located based on the logical channel identifier corresponding to the data.

[0174] Here, the terminal device decodes the received data (ie, TB) through the MAC layer and can obtain the logical channel identifier corresponding to the data, and the logical channel identifier is used to indicate the logical channel where the data is located.

[0175] The above method 3) is applicable to downlink dynamic scheduling and SPS.

[0176] In some embodiments, the network device sends a second RRC signaling to the terminal device, and the terminal device receives the second RRC signaling sent by the network device, where the second RRC signaling is used to configure a correspondence between a logical channel identifier and a designated service; the correspondence and the logical channel identifier corresponding to the data are used to determine whether the data belongs to the designated service. The terminal device determines whether the data belongs to the designated service based on the logical channel where the data is located (the logical channel where the data is located can be determined by any of the above-mentioned methods 1) to 3)) and the correspondence configured by the second RRC signaling.

[0177] Here, the solution of "the terminal device determining whether the data belongs to the data of the designated service" can be combined with the solution related to "the second condition".

[0178] In one example, when the terminal device receives an L2 command (such as a MAC CE) sent by the network device, it activates all DRX wake-up periods in the DRX cycle or activates all or part of the DRX wake-up periods indicated by the network device.

[0179] In one example, when the terminal device receives any new transmission scheduling command or receives any dynamically scheduled data or receives any data on SPS resources or sends any data based on dynamic scheduling or sends any data on CG resources, it activates all DRX wake-up periods within the DRX cycle or activates all or part of the DRX wake-up periods indicated by the network device.

[0180] In one example, when a terminal device receives a new transmission scheduling command for an XR service, or receives data for a dynamically scheduled XR service, or receives data for an XR service on an SPS resource, or sends data for an XR service based on dynamic scheduling, or sends data for an XR service on a CG resource, all DRX wake-up periods within the DRX cycle are activated, or all or part of the DRX wake-up periods indicated by the network device are activated. Here, the XR service has a corresponding relationship with one or more logical channels. The terminal device can determine whether the data belongs to the XR service based on the logical channel where the data is located and the corresponding relationship. The terminal device can determine the logical channel where the data is located by any one of the above methods 1) to 3).

[0181] In the above scheme, for a DRX wake-up period in a deactivated state, the terminal device does not start the first timer when the start time corresponding to the DRX wake-up period is reached; and / or, for a DRX wake-up period in an activated state, the terminal device starts the first timer when the start time corresponding to the DRX wake-up period is reached. Here, the first timer may also be referred to as "drx-onDurationTimer".

[0182] Option 2

[0183] In some embodiments, the network device sends a first DCI to the terminal device, and the terminal device receives the first DCI, where the first DCI carries second indication information, and the second indication information is used to indicate whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX cycle level or the DRX wake-up period level.

[0184] In some embodiments, the first DCI is a wake-up signal (Wake Up Single, WUS), and the first DCI is scrambled by a Power Save-Radio Network Temporary Identity (PS-RNTI).

[0185] In some implementations, the first DCI may also be referred to as DCP (DCI with CRC scrambled by PS-RNTI).

[0186] In the embodiment of the present application, the second indication information may indicate whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level, or may indicate whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX wake-up period level.

[0187] Option A) The second indication information indicates whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX cycle level. In this case, one DRX cycle corresponds to one first DCI. Specific implementations may be as follows:

[0188] Mode a-1) The value of the second indication information is a first value, used to indicate that multiple DRX wake-up periods within the DRX cycle are in an activated state; or, the value of the second indication information is a second value, used to indicate that multiple DRX wake-up periods within the DRX cycle are in a deactivated state.

[0189] In one example, a terminal device obtains a DCP configuration, where the DCP configuration is used to configure an offset of a time domain position corresponding to the DCP relative to a time domain position (e.g., a start time) of the first DRX wake-up period in a DRX cycle. The terminal device can determine the time domain position corresponding to the DCP based on the offset and the time domain position of the first DRX wake-up period in the DRX cycle, and then monitor and receive the DCP at the time domain position. The DCP includes second indication information (which may be referred to as wake-up indication information) for indicating whether multiple DRX wake-up periods in this DRX cycle are in an activated state or a deactivated state, that is, an indication of a DCP corresponding to multiple DRX wake-up periods in this DRX cycle.

[0190] Mode a-2) The second indication information is a first bit map, each bit in the first bit map corresponds to a DRX wake-up period within the DRX cycle; the value of the bit is a first value, used to indicate that the DRX wake-up period corresponding to the bit is in an activated state; or, the value of the bit is a second value, used to indicate that the DRX wake-up period corresponding to the bit is in a deactivated state.

[0191] In one example, a terminal device obtains a DCP configuration, and the DCP configuration is used to configure an offset of a time domain position corresponding to the DCP relative to a time domain position (e.g., a start time) of the first DRX wake-up period in a DRX cycle. The terminal device can determine the time domain position corresponding to the DCP based on the offset and the time domain position of the first DRX wake-up period in the DRX cycle, and then monitor and receive the DCP at the time domain position. The DCP includes second indication information (which may be referred to as wake-up indication information) for indicating whether each DRX wake-up period in this DRX cycle is in an activated state or a deactivated state. The second indication information may be a bitmap, where each bit corresponds to a DRX wake-up period in the DRX cycle, and the bits in the bitmap correspond one-to-one to the DRX wake-up periods in the DRX cycle from near to far, from low bits to high bits (or from high bits to low bits), respectively, wherein the value of the bit is used to indicate whether the corresponding DRX wake-up period is in an activated state or a deactivated state.

[0192] Option B) The second indication information indicates whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX wake-up period level. In this case, one DRX wake-up period corresponds to one first DCI. Specific implementations may be as follows:

[0193] Mode b-1) The value of the second indication information is the first value, which is used to indicate that the DRX wake-up period is in an activated state; or the value of the second indication information is the second value, which is used to indicate that the DRX wake-up period is in a deactivated state.

[0194] In one example, a terminal device obtains a DCP configuration, which is used to configure time domain locations corresponding to multiple DCPs. The terminal device then monitors and receives the DCPs at the corresponding time domain locations. A DRX cycle has multiple DRX wake-up periods, each of which corresponds to a DCP, indicating whether the corresponding DRX wake-up period is in an activated or deactivated state.

[0195] In the above scheme, for a DRX wake-up period in a deactivated state, the terminal device does not start the first timer when the start time corresponding to the DRX wake-up period is reached; and / or, for a DRX wake-up period in an activated state, the terminal device starts the first timer when the start time corresponding to the DRX wake-up period is reached. Here, the first timer may also be referred to as "drx-onDurationTimer".

[0196] Option 3

[0197] In some embodiments, the network device sends first configuration information to the terminal device, where the first configuration information is used to determine a first time period, where the first time period is used to determine a measurement-related time and / or a cell type, where the cell type includes a known cell and / or an unknown cell; and the first time period is different from the DRX cycle. The terminal device uses the first time period to determine a measurement-related time and / or a cell type, where the cell type includes a known cell and / or an unknown cell; and the first time period is different from the DRX cycle.

[0198] Here, the configuration of the first time period may include the following options:

[0199] Option 1) The first time period is configured by the network device, that is, the first configuration information is used to configure the first time period.

[0200] Option 2) The first time period is determined based on the DRX cycle and a first factor. The first factor is configured by the network device; or, the first factor is determined based on the number of the multiple DRX wake-up periods. For example: the first time period = first factor * DRX cycle. That is, the first configuration information is used to configure the first factor, and the DRX cycle and the first factor are used to determine the first time period; or, the first configuration information is the DRX configuration, and the number of the multiple DRX wake-up periods configured by the DRX configuration is used to determine the first factor, and the DRX cycle and the first factor are used to determine the first time period.

[0201] Option 3) The first time period is determined based on the DRX cycle and a first offset. The first offset is configured by the network device. For example, the first time period = the DRX cycle - the first offset. That is, the first configuration information is used to configure the first offset, and the DRX cycle and the first offset are used to determine the first time period.

[0202] In one example, for some measurement operations and cell type definitions, information about the DRX cycle needs to be applied.

[0203] Taking measurement as an example, the following measurements need to be applied to the DRX cycle:

[0204] The time period for PSS / SSS detection, the time period for time index detection, the measurement period for intra / inter-frequency measurements, and the SFTD measurement requirement are all related to the DRX cycle. Table 1 below shows the relationship between the measurement period for intra-frequency measurements and the DRX cycle:

[0205]

[0206] Table 1

[0207] The definitions of known cells and unknown cells are related to the DRX cycle. Table 2 below shows the relationship between the definitions of known cells and unknown cells and the DRX cycle.

[0208]

[0209] Table 2

[0210] After the introduction of the additional DRX mechanism, multiple DRX wake-up periods can occur within a DRX cycle. Since multiple DRX wake-up periods can occur within a DRX cycle, the aforementioned measurement-related time (such as TSSB_measurement_period_intra in Table 1) and / or cell type (such as known cell and unknown cell in Table 2) can no longer be determined using the DRX cycle. Instead, the DRX cycle must be adjusted. For ease of description, the DRX cycle is adjusted to a first time period, and the measurement-related time and / or cell type are determined using the first time period (i.e., DRX cycle / DRX cycle in Tables 1 and 2 is replaced with the first time period).

[0211] In an example, the network device configures a time period (ie, a first time period), and uses the time period to replace the DRX cycle in Table 1 and Table 2 to define measurement-related time and known cells and unknown cells.

[0212] In one example, a factor N (i.e., a first factor) is defined, and the DRX cycle / DRX cycle in Tables 1 and 2 is replaced by N*DRX cycle to define the measurement-related time and the known and unknown cells. For example, the factor N can be directly configured by the network device or determined based on the number of DRX start offsets configured by the network device. For example, if the network device is configured with three DRX start offsets, the factor N = 1 / 3.

[0213] In an example, an offset (ie, a first offset) is defined, and the DRX cycle / DRX cycle in Table 1 and Table 2 is replaced by (DRX cycle-offset) to define the measurement-related time and the known cells and unknown cells.

[0214] The technical solution of the embodiment of the present application is that multiple DRX start offsets can be configured within a DRX cycle, so that a DRX cycle can have multiple DRX wake-up periods. Based on the enhanced DRX solution, a solution for activating and / or deactivating the DRX wake-up period is further provided. Based on the enhanced DRX solution, a DCP / WUS implementation solution is further provided for further energy saving of terminal devices under the enhanced DRX solution. Based on the enhanced DRX solution, a solution for determining the measurement-related time and / or cell type is further provided. This makes the entire DRX mechanism more complete.

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

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

[0217] FIG5 is a 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 FIG5 , the DRX implementation apparatus includes:

[0218] The acquisition unit 501 is configured to acquire a DRX configuration, where the DRX configuration is used to determine a plurality of DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or the DRX cycle is a short DRX cycle.

[0219] In some embodiments, the DRX configuration is used to configure multiple DRX start offsets, and the multiple DRX start offsets are used to determine the start time of the multiple DRX wake-up periods, and the duration of each DRX wake-up period in the multiple DRX wake-up periods is determined based on the duration of the first timer.

[0220] In some embodiments, the DRX configuration includes a first parameter and a second parameter, the first parameter being used to configure a long DRX cycle and a first DRX start offset, and the second parameter being used to configure at least one DRX start offset;

[0221] The first DRX start offset and the at least one DRX start offset are used to determine the start time of multiple DRX wake-up periods within the DRX cycle; or, the at least one DRX start offset is used to determine the start time of multiple DRX wake-up periods within the DRX cycle.

[0222] In some embodiments, the DRX wake-up period corresponding to the first part of the DRX start biases in the multiple DRX start biases is in a deactivated state when the first condition is met; and / or, the DRX wake-up period corresponding to the second part of the DRX start biases in the multiple DRX start biases is in an activated state when the first condition is met.

[0223] In some implementations, the first condition is that a second timer has expired.

[0224] In some embodiments, the start of the second timer is triggered based on at least one of the following:

[0225] DRX inactivity timer expires;

[0226] The terminal device receives a first command sent by the network device, where the first command is used to instruct to start the second timer.

[0227] In some implementations, the second timer is different from the DRX short cycle timer; or, the second timer is the DRX short cycle timer.

[0228] In some implementations, the first part of the DRX start offset and / or the second part of the DRX start offset are configured by a network device or agreed upon by a protocol.

[0229] In some embodiments, the first part of the DRX start offset includes all or part of the DRX start offset in at least one DRX start offset configured by the second parameter in the DRX configuration, and the second part of the DRX start offset includes the first DRX start offset configured by the first parameter in the DRX configuration.

[0230] In some embodiments, the DRX wake-up periods corresponding to all or part of the multiple DRX start offsets are in an activated state when a second condition is met.

[0231] In some embodiments, by default, the DRX wake-up periods corresponding to all the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met; or, in a case where the network device configures an activated DRX start bias, the DRX wake-up periods corresponding to all or part of the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met, and the all or part of the DRX start biases are the activated DRX start biases configured by the network device.

[0232] In some embodiments, the second condition includes at least one of the following:

[0233] The terminal device receives a second command sent by the network device, where the second command is used to indicate activation and / or deactivation of a DRX start offset;

[0234] The terminal device receives any scheduling command;

[0235] The terminal device receives any data;

[0236] The terminal device sends arbitrary data;

[0237] The terminal device receives a scheduling command for a designated service;

[0238] The terminal device receives data of a designated service;

[0239] The terminal device sends data of a designated service.

[0240] In some implementations, the scheduling command is used to schedule transmission of downlink data or to schedule transmission of uplink data.

[0241] In some embodiments, the terminal device receives any data including at least one of the following:

[0242] The terminal device receives any dynamically scheduled data;

[0243] The terminal device receives any data on the semi-persistent scheduling SPS resources.

[0244] In some embodiments, the terminal device sends arbitrary data, including at least one of the following:

[0245] The terminal device sends any dynamically scheduled data;

[0246] The terminal device sends arbitrary data on the configured authorized CG resources.

[0247] In some implementations, the terminal device receives data of a designated service, including at least one of the following:

[0248] The terminal device receives data of a dynamically scheduled designated service;

[0249] The terminal device receives data of a designated service on the SPS resource.

[0250] In some implementations, the terminal device sending data of a designated service includes at least one of the following:

[0251] The terminal device sends data of a dynamically scheduled designated service;

[0252] The terminal device sends data of the specified service on the CG resource.

[0253] In some embodiments, the device also includes: a determination unit 502; the designated service has a corresponding relationship with one or more logical channel identifiers, and the determination unit 502 is used to determine whether the received data or sent data belongs to the designated service based on the logical channel where the data is located and the corresponding relationship.

[0254] In some embodiments, the apparatus further includes: a receiving unit 503, configured to receive a first RRC signaling sent by a network device, where the first RRC signaling is used to configure a correspondence between a logical channel identifier and a CG resource or the first RRC signaling is used to configure a correspondence between a logical channel identifier and an SPS resource;

[0255] The determination unit 502 is used to determine the logical channel where the data is located based on the CG resource or SPS resource where the data is located and the corresponding relationship.

[0256] In some embodiments, the receiving unit 503 is used to receive a scheduling command sent by a network device, where the scheduling command is used to schedule the transmission of downlink data or to schedule the transmission of uplink data. The scheduling command carries first indication information, where the first indication information is used to indicate the logical channel where the data scheduled for transmission by the scheduling command is located.

[0257] In some embodiments, the apparatus further comprises: a processing unit, configured to decode the received data to obtain a logical channel identifier corresponding to the data;

[0258] The determining unit 502 is configured to determine the logical channel where the data is located based on the logical channel identifier corresponding to the data.

[0259] In some implementations, the receiving unit 503 is configured to receive a second RRC signaling sent by a network device, where the second RRC signaling is used to configure a correspondence between a logical channel identifier and a designated service;

[0260] The determining unit 502 is configured to determine whether the data belongs to the designated service based on the correspondence between the logical channel where the data is located and the second RRC signaling configuration.

[0261] In some embodiments, the receiving unit 503 is used to receive a first DCI, where the first DCI carries second indication information, and the second indication information is used to indicate whether the DRX wake-up period is in an activated state or a deactivated state according to a DRX cycle level or a DRX wake-up period level.

[0262] In some embodiments, the first DCI is a WUS, and the first DCI is scrambled by a PS-RNTI.

[0263] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level,

[0264] The value of the second indication information is a first value, used to indicate that multiple DRX wake-up periods in the DRX cycle are in an activated state; or

[0265] The value of the second indication information is a second value, which is used to indicate that multiple DRX wake-up periods in a DRX cycle are in a deactivated state.

[0266] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level,

[0267] The second indication information is a first bitmap, where each bit in the first bitmap corresponds to a DRX wake-up period in the DRX cycle;

[0268] The value of the bit is a first value, which is used to indicate that the DRX wake-up period corresponding to the bit is in an active state; or

[0269] The value of the bit is a second value, which is used to indicate that the DRX wake-up period corresponding to the bit is in a deactivated state.

[0270] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX wake-up period level,

[0271] The value of the second indication information is a first value, used to indicate that the DRX wake-up period is in an activated state; or

[0272] The value of the second indication information is a second value, which is used to indicate that the DRX wake-up period is in a deactivated state.

[0273] In some embodiments, the processing unit is configured to, for a DRX wake-up period in a deactivated state, not start the first timer when the start time corresponding to the DRX wake-up period is reached; and / or, for a DRX wake-up period in an activated state, start the first timer when the start time corresponding to the DRX wake-up period is reached.

[0274] In some embodiments, the determining unit 502 is configured to use a first time period to determine a measurement-related time and / or determine a cell type, where the cell type includes a known cell and / or an unknown cell; and the first time period is different from the DRX cycle.

[0275] In some implementations, the first time period is configured by the network device.

[0276] In some embodiments, the first time period is determined based on the DRX cycle and a first factor.

[0277] In some implementations, the first factor is configured by a network device; or, the first factor is determined based on the number of the multiple DRX wake-up periods.

[0278] In some embodiments, the first time period is determined based on the DRX cycle and a first offset.

[0279] In some embodiments, the first bias is configured by a network device.

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

[0281] FIG6 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 network device. As shown in FIG6 , the DRX implementation apparatus includes:

[0282] The sending unit 601 is used to send a DRX configuration to the terminal device, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

[0283] In some embodiments, the DRX configuration is used to configure multiple DRX start offsets, and the multiple DRX start offsets are used to determine the start time of the multiple DRX wake-up periods, and the duration of each DRX wake-up period in the multiple DRX wake-up periods is determined based on the duration of the first timer.

[0284] In some embodiments, the DRX configuration includes a first parameter and a second parameter, the first parameter being used to determine a long DRX cycle and a first DRX start offset, and the second parameter being used to determine at least one DRX start offset;

[0285] The first DRX start offset and the at least one DRX start offset are used to determine the start time of multiple DRX wake-up periods within the DRX cycle; or, the at least one DRX start offset is used to determine the start time of multiple DRX wake-up periods within the DRX cycle.

[0286] In some embodiments, the DRX wake-up period corresponding to the first part of the DRX start biases in the multiple DRX start biases is in a deactivated state when the first condition is met; and / or, the DRX wake-up period corresponding to the second part of the DRX start biases in the multiple DRX start biases is in an activated state when the first condition is met.

[0287] In some implementations, the first condition is that a second timer has expired.

[0288] In some embodiments, the start of the second timer is triggered based on at least one of the following:

[0289] DRX inactivity timer expires;

[0290] The terminal device receives a first command sent by the network device, where the first command is used to instruct to start the second timer.

[0291] In some implementations, the second timer is different from the DRX short cycle timer; or, the second timer is the DRX short cycle timer.

[0292] In some implementations, the first part of the DRX start offset and / or the second part of the DRX start offset are configured by a network device or agreed upon by a protocol.

[0293] In some embodiments, the first part of the DRX start offset includes all or part of the DRX start offset in at least one DRX start offset configured by the second parameter in the DRX configuration, and the second part of the DRX start offset includes the first DRX start offset configured by the first parameter in the DRX configuration.

[0294] In some embodiments, the DRX wake-up periods corresponding to all or part of the multiple DRX start offsets are in an activated state when a second condition is met.

[0295] In some embodiments, by default, the DRX wake-up periods corresponding to all the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met; or, in a case where the network device configures an activated DRX start bias, the DRX wake-up periods corresponding to all or part of the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met, and the all or part of the DRX start biases are the activated DRX start biases configured by the network device.

[0296] In some embodiments, the second condition includes at least one of the following:

[0297] The terminal device receives a second command sent by the network device, where the second command is used to indicate activation and / or deactivation of a DRX start offset;

[0298] The terminal device receives any scheduling command;

[0299] The terminal device receives any data;

[0300] The terminal device sends arbitrary data;

[0301] The terminal device receives a scheduling command for a designated service;

[0302] The terminal device receives data of a designated service;

[0303] The terminal device sends data of a designated service.

[0304] In some embodiments, the sending unit 601 is used to send a first RRC signaling to the terminal device, where the first RRC signaling is used to configure the correspondence between the logical channel identifier and the CG resource or the first RRC signaling is used to configure the correspondence between the logical channel identifier and the SPS resource; the correspondence and the CG or SPS resource where the data is located are used to determine the logical channel where the data is located.

[0305] In some embodiments, the sending unit 601 is used to send a scheduling command, which is used to schedule the transmission of downlink data or to schedule the transmission of uplink data. The scheduling command carries first indication information, which is used to indicate the logical channel where the data scheduled for transmission by the scheduling command is located.

[0306] In some implementations, the sending unit 601 is configured to send data to the terminal device, where the data carries a logical channel identifier corresponding to the data.

[0307] In some embodiments, the sending unit 601 is used to send a second RRC signaling to the terminal device, and the second RRC signaling is used to configure the correspondence between the logical channel identifier and the specified service; the correspondence and the logical channel identifier corresponding to the data are used to determine whether the data belongs to the data of the specified service.

[0308] In some embodiments, the sending unit 601 is used to send a first DCI to the terminal device, where the first DCI carries second indication information, and the second indication information is used to indicate whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX cycle level or the DRX wake-up period level.

[0309] In some embodiments, the first DCI is a WUS, and the first DCI is scrambled by a PS-RNTI.

[0310] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level,

[0311] The value of the second indication information is a first value, used to indicate that multiple DRX wake-up periods in the DRX cycle are in an activated state; or

[0312] The value of the second indication information is a second value, which is used to indicate that multiple DRX wake-up periods in a DRX cycle are in a deactivated state.

[0313] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level,

[0314] The second indication information is a first bitmap, where each bit in the first bitmap corresponds to a DRX wake-up period in the DRX cycle;

[0315] The value of the bit is a first value, which is used to indicate that the DRX wake-up period corresponding to the bit is in an active state; or

[0316] The value of the bit is a second value, which is used to indicate that the DRX wake-up period corresponding to the bit is in a deactivated state.

[0317] In some implementations, for a case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX wake-up period level,

[0318] The value of the second indication information is a first value, used to indicate that the DRX wake-up period is in an activated state; or

[0319] The value of the second indication information is a second value, which is used to indicate that the DRX wake-up period is in a deactivated state.

[0320] In some embodiments, the sending unit 601 is used to send first configuration information to the terminal device, the first configuration information is used to determine a first time period, the first time period is used to determine the measurement-related time and / or determine the cell type, the cell type includes a known known cell and / or an unknown unknown cell; the first time period is different from the DRX cycle.

[0321] In some implementations, the first configuration information is used to configure the first time period.

[0322] In some embodiments, the first configuration information is used to configure a first factor, and the DRX cycle and the first factor are used to determine the first time period; or, the first configuration information is the DRX configuration, and the number of the multiple DRX wake-up periods configured by the DRX configuration is used to determine the first factor, and the DRX cycle and the first factor are used to determine the first time period.

[0323] In some implementations, the first configuration information is used to configure a first offset, and the DRX cycle and the first offset are used to determine the first time period.

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

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

[0326] Optionally, as shown in Figure 7, the communication device 700 may further include a memory 720. The processor 710 may call and execute a computer program from the memory 720 to implement the method in the embodiment of the present application.

[0327] The memory 720 may be a separate device independent of the processor 710 , or may be integrated into the processor 710 .

[0328] Optionally, as shown in FIG7 , the communication device 700 may further include a transceiver 730 , and the processor 710 may control the transceiver 730 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

[0330] Optionally, the communication device 700 may specifically be a network device in an embodiment of the present application, and the communication device 700 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.

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

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

[0333] Optionally, as shown in FIG8 , the chip 800 may further include a memory 820 , wherein 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.

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

[0335] Optionally, the chip 800 may further include an input interface 830. The processor 810 may control the input interface 830 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0336] Optionally, the chip 800 may further include an output interface 840. The processor 810 may control the output interface 840 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

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

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

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

[0340] FIG9 is a schematic block diagram of a communication system 900 provided in an embodiment of the present application. As shown in FIG9 , the communication system 900 includes a terminal device 910 and a network device 920 .

[0341] Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 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.

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

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

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

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

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

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

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

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

[0350] Optionally, the computer program product can be applied to the 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 terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

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

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

[0353] Optionally, the computer program can be applied to the 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 terminal device in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

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

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

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

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

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

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

[0360] 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 a DRX configuration, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

2. The method according to claim 1, wherein The DRX configuration is used to configure multiple DRX start offsets, the multiple DRX start offsets are used to determine the start time of the multiple DRX wake-up periods, and the duration of each DRX wake-up period in the multiple DRX wake-up periods is determined based on the duration of the first timer.

3. The method according to claim 2, wherein: The DRX configuration includes a first parameter and a second parameter, the first parameter being used to configure a long DRX cycle and a first DRX start offset, and the second parameter being used to configure at least one DRX start offset; The first DRX start offset and the at least one DRX start offset are used to determine start times of multiple DRX wake-up periods within the DRX cycle; Alternatively, the at least one DRX start offset is used to determine the start time of multiple DRX wake-up periods in the DRX cycle.

4. The method according to claim 2 or 3, wherein: The DRX wake-up periods corresponding to the first part of the DRX start offsets among the multiple DRX start offsets are in a deactivated state when the first condition is satisfied; and / or, The DRX wake-up periods corresponding to the second part of the DRX start offsets in the multiple DRX start offsets are in an activated state when the first condition is met.

5. The method according to claim 4, wherein The first condition is that the second timer times out.

6. The method according to claim 5, wherein: The start of the second timer is triggered based on at least one of the following: DRX inactivity timer expires; The terminal device receives a first command sent by the network device, where the first command is used to instruct to start the second timer.

7. The method according to claim 5 or 6, wherein: The second timer is different from the DRX short cycle timer; or, The second timer is a DRX short cycle timer.

8. The method according to any one of claims 4 to 7, wherein The first part of the DRX start offset and / or the second part of the DRX start offset are configured by a network device or agreed upon by a protocol.

9. The method according to any one of claims 4 to 8, wherein The first part of the DRX start offset includes all or part of the at least one DRX start offset configured by the second parameter in the DRX configuration, and the second part of the DRX start offset includes the first DRX start offset configured by the first parameter in the DRX configuration.

10. The method according to any one of claims 2 to 9, wherein The DRX wake-up periods corresponding to all or part of the multiple DRX start offsets are in an activated state when a second condition is met.

11. The method according to claim 10, wherein: By default, the DRX wake-up periods corresponding to all the DRX start offsets in the multiple DRX start offsets are in an activated state when the second condition is met; or, In the case where the network device configures an activated DRX start bias, the DRX wake-up periods corresponding to all or part of the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met, and the all or part of the DRX start biases are the activated DRX start biases configured by the network device.

12. The method according to claim 10 or 11, wherein: The second condition includes at least one of the following: The terminal device receives a second command sent by the network device, where the second command is used to indicate activation and / or deactivation of a DRX start offset; The terminal device receives any scheduling command; The terminal device receives any data; The terminal device sends arbitrary data; The terminal device receives a scheduling command for a designated service; The terminal device receives data of a designated service; The terminal device sends data of a designated service.

13. The method according to claim 12, wherein: The scheduling command is used to schedule transmission of downlink data or to schedule transmission of uplink data.

14. The method according to claim 12 or 13, wherein: The terminal device receives any data, including at least one of the following: The terminal device receives any dynamically scheduled data; The terminal device receives any data on the semi-persistent scheduling SPS resources.

15. The method according to any one of claims 12 to 14, wherein The terminal device sends any data, including at least one of the following: The terminal device sends any dynamically scheduled data; The terminal device sends arbitrary data on the configured authorized CG resources.

16. The method according to any one of claims 12 to 15, wherein The terminal device receives data of a designated service, including at least one of the following: The terminal device receives data of a dynamically scheduled designated service; The terminal device receives data of a designated service on the SPS resource.

17. The method according to any one of claims 12 to 16, wherein The terminal device sends data of a designated service, including at least one of the following: The terminal device sends data of a dynamically scheduled designated service; The terminal device sends data of the specified service on the CG resource.

18. The method according to any one of claims 12 to 17, wherein The designated service has a corresponding relationship with one or more logical channel identifiers, and the method further includes: For received data or sent data, the terminal device determines whether the data belongs to the designated service based on the logical channel where the data is located and the corresponding relationship.

19. The method according to claim 18, wherein The method further comprises: The terminal device receives a first radio resource control RRC signaling sent by a network device, where the first RRC signaling is used to configure a correspondence between a logical channel identifier and a CG resource or the first RRC signaling is used to configure a correspondence between a logical channel identifier and an SPS resource; The terminal device determines the logical channel where the data is located based on the CG resource or SPS resource where the data is located and the corresponding relationship.

20. The method according to claim 18, wherein The method further comprises: The terminal device receives a scheduling command sent by a network device, where the scheduling command is used to schedule the transmission of downlink data or to schedule the transmission of uplink data. The scheduling command carries first indication information, where the first indication information is used to indicate the logical channel where the data scheduled for transmission by the scheduling command is located.

21. The method according to claim 18, wherein The method further comprises: The terminal device decodes the received data to obtain a logical channel identifier corresponding to the data, and determines the logical channel where the data is located based on the logical channel identifier corresponding to the data.

22. The method according to any one of claims 18 to 21, wherein The terminal device determines whether the data belongs to the designated service based on the logical channel where the data is located and the corresponding relationship, including: The terminal device receives a second RRC signaling sent by the network device, where the second RRC signaling is used to configure a correspondence between a logical channel identifier and a designated service; The terminal device determines whether the data belongs to the designated service based on the correspondence between the logical channel where the data is located and the second RRC signaling configuration.

23. The method according to any one of claims 1 to 22, wherein The method further comprises: The terminal device receives first downlink control information DCI, the first DCI carries second indication information, and the second indication information is used to indicate whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX cycle level or the DRX wake-up period level.

24. The method according to claim 23, wherein The first DCI is a wake-up signal WUS, and the first DCI is scrambled by a power saving-radio network temporary identifier PS-RNTI.

25. The method according to claim 23 or 24, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level, The value of the second indication information is a first value, used to indicate that multiple DRX wake-up periods in the DRX cycle are in an activated state; or The value of the second indication information is a second value, which is used to indicate that multiple DRX wake-up periods in a DRX cycle are in a deactivated state.

26. The method according to claim 23 or 24, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level, The second indication information is a first bitmap, where each bit in the first bitmap corresponds to a DRX wake-up period in the DRX cycle; The value of the bit is a first value, which is used to indicate that the DRX wake-up period corresponding to the bit is in an active state; or The value of the bit is a second value, which is used to indicate that the DRX wake-up period corresponding to the bit is in a deactivated state.

27. The method according to claim 23 or 24, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX wake-up period level, The value of the second indication information is a first value, used to indicate that the DRX wake-up period is in an activated state; or The value of the second indication information is a second value, which is used to indicate that the DRX wake-up period is in a deactivated state.

28. The method according to any one of claims 2 to 27, wherein The method further comprises: For a DRX wake-up period in a deactivated state, the terminal device does not start the first timer when the start time corresponding to the DRX wake-up period is reached; and / or, For a DRX wake-up period in an activated state, the terminal device starts a first timer when the start time corresponding to the DRX wake-up period is reached.

29. The method according to any one of claims 1 to 28, wherein The method further comprises: The terminal device uses a first time period to determine measurement-related time and / or determine a cell type, where the cell type includes a known cell and / or an unknown cell; the first time period is different from the DRX cycle.

30. The method according to claim 29, wherein The first time period is configured by the network device.

31. The method according to claim 29, wherein The first time period is determined based on the DRX cycle and a first factor.

32. The method according to claim 31, wherein The first factor is configured by the network device; or The first factor is determined based on the number of the plurality of DRX wake-up periods.

33. The method of claim 29, wherein: The first time period is determined based on the DRX cycle and a first offset.

34. The method according to claim 33, wherein The first bias is configured for the network device.

35. A DRX implementation method, the method comprising: The network device sends a DRX configuration to the terminal device, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

36. The method according to claim 35, wherein The DRX configuration is used to configure multiple DRX start offsets, the multiple DRX start offsets are used to determine the start time of the multiple DRX wake-up periods, and the duration of each DRX wake-up period in the multiple DRX wake-up periods is determined based on the duration of the first timer.

37. The method according to claim 36, wherein The DRX configuration includes a first parameter and a second parameter, the first parameter being used to determine a long DRX cycle and a first DRX start offset, and the second parameter being used to determine at least one DRX start offset; The first DRX start offset and the at least one DRX start offset are used to determine start times of multiple DRX wake-up periods within the DRX cycle; Alternatively, the at least one DRX start offset is used to determine the start time of multiple DRX wake-up periods in the DRX cycle.

38. The method according to claim 36 or 37, wherein The DRX wake-up periods corresponding to the first part of the DRX start offsets among the multiple DRX start offsets are in a deactivated state when the first condition is satisfied; and / or, The DRX wake-up periods corresponding to the second part of the DRX start offsets in the multiple DRX start offsets are in an activated state when the first condition is met.

39. The method according to claim 38, wherein The first condition is that the second timer times out.

40. The method of claim 39, wherein The start of the second timer is triggered based on at least one of the following: DRX inactivity timer expires; The terminal device receives a first command sent by the network device, where the first command is used to instruct to start the second timer.

41. The method according to claim 39 or 40, wherein The second timer is different from the DRX short cycle timer; or, The second timer is a DRX short cycle timer.

42. The method according to any one of claims 38 to 41, wherein The first part of the DRX start offset and / or the second part of the DRX start offset are configured by a network device or agreed upon by a protocol.

43. The method according to any one of claims 38 to 42, wherein The first part of the DRX start offset includes all or part of the at least one DRX start offset configured by the second parameter in the DRX configuration, and the second part of the DRX start offset includes the first DRX start offset configured by the first parameter in the DRX configuration.

44. The method according to any one of claims 36 to 43, wherein The DRX wake-up periods corresponding to all or part of the multiple DRX start offsets are in an activated state when a second condition is met.

45. The method of claim 44, wherein: By default, the DRX wake-up periods corresponding to all the DRX start offsets in the multiple DRX start offsets are in an activated state when the second condition is met; or, In the case where the network device configures an activated DRX start bias, the DRX wake-up periods corresponding to all or part of the DRX start biases in the multiple DRX start biases are in an activated state when the second condition is met, and the all or part of the DRX start biases are the activated DRX start biases configured by the network device.

46. ​​The method according to claim 44 or 45, wherein The second condition includes at least one of the following: The terminal device receives a second command sent by the network device, where the second command is used to indicate activation and / or deactivation of a DRX start offset; The terminal device receives any scheduling command; The terminal device receives any data; The terminal device sends arbitrary data; The terminal device receives a scheduling command for a designated service; The terminal device receives data of a designated service; The terminal device sends data of a designated service.

47. The method according to any one of claims 35 to 46, wherein The method further comprises: The network device sends a first RRC signaling to the terminal device, where the first RRC signaling is used to configure the correspondence between the logical channel identifier and the CG resource or the first RRC signaling is used to configure the correspondence between the logical channel identifier and the SPS resource; the correspondence and the CG or SPS resource where the data is located are used to determine the logical channel where the data is located.

48. The method according to any one of claims 35 to 47, wherein The method further comprises: The network device sends a scheduling command to the terminal device, where the scheduling command is used to schedule the transmission of downlink data or to schedule the transmission of uplink data. The scheduling command carries first indication information, where the first indication information is used to indicate the logical channel where the data scheduled for transmission by the scheduling command is located.

49. The method according to any one of claims 35 to 47, wherein The method further comprises: The network device sends data to the terminal device, where the data carries a logical channel identifier corresponding to the data.

50. The method according to any one of claims 35 to 48, wherein The method further comprises: The network device sends a second RRC signaling to the terminal device, where the second RRC signaling is used to configure the correspondence between the logical channel identifier and the designated service; the correspondence and the logical channel identifier corresponding to the data are used to determine whether the data belongs to the designated service.

51. The method according to any one of claims 35 to 50, wherein The method further comprises: The network device sends a first DCI to the terminal device, where the first DCI carries second indication information, and the second indication information is used to indicate whether the DRX wake-up period is in an activated state or a deactivated state according to the DRX cycle level or the DRX wake-up period level.

52. The method of claim 51, wherein The first DCI is WUS, and the first DCI is scrambled by PS-RNTI.

53. The method according to claim 51 or 52, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level, The value of the second indication information is a first value, used to indicate that multiple DRX wake-up periods in the DRX cycle are in an activated state; or The value of the second indication information is a second value, which is used to indicate that multiple DRX wake-up periods in a DRX cycle are in a deactivated state.

54. The method according to claim 51 or 52, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX cycle level, The second indication information is a first bitmap, where each bit in the first bitmap corresponds to a DRX wake-up period in the DRX cycle; The value of the bit is a first value, which is used to indicate that the DRX wake-up period corresponding to the bit is in an active state; or The value of the bit is a second value, which is used to indicate that the DRX wake-up period corresponding to the bit is in a deactivated state.

55. The method according to claim 51 or 52, wherein For the case where the second indication information indicates whether the DRX wake-up period is in an activated state or in a deactivated state according to the DRX wake-up period level, The value of the second indication information is a first value, used to indicate that the DRX wake-up period is in an activated state; or The value of the second indication information is a second value, which is used to indicate that the DRX wake-up period is in a deactivated state.

56. The method according to any one of claims 35 to 55, wherein The method further comprises: The network device sends first configuration information to the terminal device, where the first configuration information is used to determine a first time period, where the first time period is used to determine measurement-related time and / or determine a cell type, where the cell type includes a known cell and / or an unknown cell; and the first time period is different from the DRX cycle.

57. The method of claim 56, wherein The first configuration information is used to configure the first time period.

58. The method of claim 56, wherein The first configuration information is used to configure a first factor, and the DRX cycle and the first factor are used to determine the first time period; or, The first configuration information is the DRX configuration, the number of the multiple DRX wake-up periods configured by the DRX configuration is used to determine a first factor, and the DRX cycle and the first factor are used to determine the first time period.

59. The method of claim 56, wherein The first configuration information is used to configure a first offset, and the DRX cycle and the first offset are used to determine the first time period.

60. A DRX implementation device, applied to a terminal device, comprising: An acquisition unit is used to acquire a DRX configuration, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

61. A DRX implementation device, applied to a network device, comprising: A sending unit is used to send a DRX configuration to a terminal device, where the DRX configuration is used to determine multiple DRX wake-up periods within a DRX cycle; wherein the DRX cycle is a long DRX cycle; or, the DRX cycle is a short DRX cycle.

62. 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 so that the terminal device executes the method according to any one of claims 1 to 34.

63. A network 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 so as to enable the network device to perform the method as claimed in any one of claims 35 to 59.

64. 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 34, or the method according to any one of claims 35 to 59.

65. 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 34, or the method according to any one of claims 35 to 59.

66. 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 34, or any one of claims 35 to 59.

67. A computer program, the computer program causing a computer to perform the method of any one of claims 1 to 34, or any one of claims 35 to 59.

Images