Methods, devices, and systems for saving energy in terminals.

Abstract

A method, device, and system for saving energy in terminals are provided. [Solution] This method includes the following: A terminal device receives first information from a network device. Here, the first information is used to determine the first CDRX cycle corresponding to the terminal device. The terminal device then determines when it enters its operational duration according to the first CDRX cycle and a first calculation rule. Here, the first calculation rule is used to control when the terminal device enters its operational duration so that it coincides with when the network device transmits a downlink frame for the first service according to its service cycle.

Description

Technical Field

[0001] This application relates to the field of communication technologies. In particular, it relates to a method, apparatus, and system for energy saving of a terminal.

[0002] This application claims priority to Chinese Patent Application No. 202111022590.4, titled "TERMINAL ENERGY SAVING METHOD, APPARATUS, AND SYSTEM", filed with the China National Intellectual Property Administration on September 1, 2021, the entire content of which is incorporated herein by reference.

Background Art

[0003] With the development of communication technologies, extended reality (XR) (for example, virtual reality (VR)) services have also emerged. In order to improve the user experience, the terminal device executing the XR service needs to be lightweight (for example, VR glasses), and the communication system executing the XR service needs to have high throughput and low latency. To achieve such requirements, the terminal device requires high power consumption for executing the XR service. Therefore, for the normal operation of the terminal device, the power consumption of the terminal device should be reduced as much as possible.

[0004] Currently, the connected discontinuous reception (CDRX) mechanism is an effective energy-saving technology. Terminal devices equipped with the CDRX mechanism are divided into a "wake state" and a "sleep state". A terminal device in the "wake state" can monitor the physical downlink control channel (PDCCH) to transmit service data. After the terminal device remains in the "wake state" for a specific period of time, it enters the "sleep state". Since the terminal device does not monitor the PDCCH in the "sleep state", it can achieve the objective of reducing power consumption. A terminal device in the "wake state" may also be referred to as a terminal device in the "activation duration", and a terminal device in the "sleep state" may also be referred to as a terminal device in the "deactivation duration". Currently, the duration that the terminal device remains in the "wake state" and the duration that the terminal device remains in the "sleep state" constitute the CDRX cycle. In other words, a CDRX cycle is the interval between the last time a terminal device enters the "wake state" and the next time it enters the "wake state". In the currently defined CDRX mechanism, all CDRX cycles are integers.

[0005] To reduce the power consumption of terminal devices, the CDRX mechanism may be configured for terminal devices running XR services. However, downlink frames in current XR services have periodic characteristics, and service cycles are all decimals. For example, if the service frame rate is 120 fps, the service cycle for one frame is 8.33 milliseconds (ms). If the service frame rate is 60 fps, the service cycle for one frame is 16.67 milliseconds. However, CDRX cycles are all integers (e.g., 6ms, 7ms, 8ms, or 10ms). Therefore, when the CDRX mechanism is configured for a terminal device running XR services, even if the CDRX cycle closest to the service cycle of the XR service is configured for the terminal device, for example, if the service cycle of the XR service is 8.33ms, the CDRX cycle will be configured as 8ms, and the CDRX cycle of the terminal device will not be able to match the service cycle of the XR service. In other words, the terminal device enters a "wake state," and the time at which it can transmit data does not match the time of the XR service data to be transmitted. When the terminal device's CDRX cycle does not match the service cycle of the XR service, the following situations occur: When the terminal device is in a "wake state," there are no service frames to be transmitted for the XR service, resulting in wasted power consumption of the terminal device. In addition, when there are service frames to be transmitted for the XR service, the terminal device is in a "sleep state" and cannot receive the service frames. As a result, the delay of the XR service does not meet the delay requirements for the XR service.

[0006] In summary, following existing technical solutions results in terminal equipment CDRX cycles not matching the service cycles of XR services, leading to problems such as wasted power consumption in terminal equipment or inability to meet XR service latency requirements. Therefore, how to align terminal equipment CDRX cycles with XR service cycles is an urgent issue that needs to be resolved. [Overview of the Initiative]

[0007] Embodiments of this application provide terminal energy saving methods, apparatus, and systems to solve the problem in existing technical solutions where the CDRX cycle of a terminal device does not coincide with the service cycle of an XR service.

[0008] To achieve the aforementioned objectives, the following technical solutions are used in embodiments of this application.

[0009] A terminal energy saving method is provided according to a first embodiment. The method includes: A terminal device receives first information from a network device, where the first information is used to determine a first CDRX cycle corresponding to the terminal device. The terminal device then determines, according to the first CDRX cycle and a first calculation rule, when it enters an operational duration, where the first calculation rule is used to control when the terminal device enters the operational duration, so that it coincides with when the network device transmits a downlink frame for a first service according to a service cycle. Based on this solution, a terminal device can determine a first CDRX cycle according to the first information, and when the terminal device enters an operational duration, determined by the terminal device according to the first CDRX cycle and the first calculation rule, coincides with when the network device transmits a downlink frame for a first service according to a service cycle, thereby avoiding wasted power consumption of the terminal device and satisfying the delay requirements for the first service.

[0010] In relation to the first embodiment, in a possible implementation, the first CDRX cycle corresponding to the terminal device is a first CDRX cycle configured by a network device for the terminal device, and the first CDRX cycle is the same as the service cycle. Based on this solution, the terminal device can configure a first CDRX cycle that is the same as the service cycle of the first service, according to the first information, so as to match the service cycle of the first service.

[0011] In relation to the first embodiment, in a possible implementation, the first calculation rule is:

number

number

[0012] In relation to the first embodiment, in a possible implementation, the first information includes the service cycle of the first service, or the value of the first CDRX cycle, or the frequency of the first CDRX cycle, or the first information includes a preset integer value, and the preset integer value is used by the terminal device to determine the first CDRX cycle according to a preset relationship. Based on this solution, multiple forms of the first information for determining the first CDRX cycle are provided for application to multiple possible situations.

[0013] In relation to the first embodiment, in a possible implementation, the first information is carried in a radio resource control RRC message. Based on this solution, the first CDRX cycle can be semi-statically configured in a terminal device through the first information in the RRC message.

[0014] In relation to the first embodiment, in a possible implementation, the first CDRX cycle corresponding to the terminal device is a first CDRX cycle obtained by adjusting the CDRX cycle configured for the terminal device according to the first information. Based on this solution, the terminal device can obtain a first CDRX cycle by adjusting the configured CDRX cycle according to the first information.

[0015] In relation to the first embodiment, in a possible implementation, the first calculation rule is: [(SFN×10)+subframe number]modulo(drx-Cycle + cycle-adjust) =drx-StartOffset, or [(SFN×10)+subframe number]modulo(drx-cycle + cycle-adjust) =(drx-StartOffset)modulo(drx-cycle+cycle-adjust) The following relationship is satisfied: Here, SFN represents the system frame number when the terminal device enters the operational duration, subframe number represents the subframe number in the system frame corresponding to the system frame number, drx-cycle represents the CDRX cycle configured for the terminal device by the network device, cycle-adjust represents the cycle offset value determined by the terminal device according to the first information, (drx-cycle + cycle-adjust) represents the first CDRX cycle corresponding to the terminal device, and drx-StartOffset represents the subframe offset before the terminal device enters the operational duration. Based on this solution, a calculation rule is provided for determining when the terminal device enters the operational duration in the case of non-memory adjustment of the CDRX cycle.

[0016] In relation to the first embodiment, in a possible implementation, the first calculation rule is: [(SFN×10)+subframe number]modulo(drx-cycleN) =drx-StartOffset, or [(SFN×10)+subframe number]modulo(drx-cycleN) =(drx-StartOffset)modulo(drx-cycleN) The following relationship is satisfied, where SFN represents the frame number when the terminal device enters the operating duration period, subframe number represents the subframe number within the system frame corresponding to the system frame number, drx-cycleN represents the first CDRX cycle corresponding to the terminal device, drx-StartOffset represents the subframe offset before the terminal device enters the operating duration period, and drx-cycleN satisfies the relationship drx-cycleN=drx-cycle(N-1)+cycle-adjust, where drx-cycle(N-1) represents the CDRX cycle configured before the terminal device enters the operating duration period, and when drx-cycle(N-1)=drx-cycle0, drx-cycle0 represents the CDRX cycle configured by the network device for the terminal device, and cycle-adjust represents the cycle offset value determined by the terminal device according to the first information. Based on this solution, calculation rules are provided for determining when a terminal device enters its operational duration in the case of memory adjustment for the CDRX cycle.

[0017] In relation to the first aspect, in possible implementations, the first information is carried in a MAC CE message, which is a control element for media access control. Based on this solution, the CDRX cycle of a terminal device can be dynamically adjusted through the first information in the MACCE message.

[0018] A terminal energy saving method is provided according to a second embodiment. The method includes: A terminal device receives second information from a network device, where the second information is used to determine one or more CDRX cycles in a plurality of CDRX cycles configured by the network device for the terminal device. The one or more CDRX cycles are used to control when the terminal device enters an operational duration, such that the time coincides with when the network device transmits a downlink frame for a first service according to a service cycle. The terminal device then determines the time when it enters the operational duration according to the one or more CDRX cycles. Based on this solution, the terminal device can determine one or more CDRX cycles according to the second information, and the time determined by the terminal device, according to one or more CDRX cycles, when the terminal device enters an operational duration, coincides with when the network device transmits a downlink frame for a first service according to a service cycle, thereby avoiding wasted power consumption of the terminal device and satisfying the delay requirements for the first service.

[0019] In relation to a second aspect, in a possible implementation, the one or more CDRX cycles are a plurality of periodic CDRX cycles, each corresponding to a CDRX cycle within the plurality of periodic CDRX cycles, and are used to control the time at which the terminal device enters the operational duration, such that the time at which the network device transmits the downlink frame of the first service according to the service cycle. Based on this solution, the terminal device can determine the plurality of periodic CDRX cycles according to the second information, each corresponding to a CDRX cycle within the plurality of periodic CDRX cycles, and the time at which the terminal device enters the operational duration coincides with the time at which the network device transmits the downlink frame of the first service according to the service cycle.

[0020] In relation to the second aspect, in a possible implementation, the second information includes identification information corresponding to each CDRX cycle within the plurality of periodic CDRX cycles, and a sequence of the identification information, and the sequence of the identification information corresponds to the periodic sequence of the plurality of periodic CDRX cycles. Based on this solution, second information for determining a plurality of periodic CDRX cycles is provided according to the identification information.

[0021] In relation to the second aspect, in a possible implementation, the second information is carried in a radio resource control (RRC) message, or the second information is carried in a media access control control element (MAC CE) message. Based on this solution, a plurality of periodic CDRX cycles can be semi-statically configured in a terminal device through the second information in the RRC message. Alternatively, a plurality of periodic CDRX cycles can be dynamically updated through the second information in the MAC CE message.

[0022] In relation to the second aspect, in a possible implementation, the one or more CDRX cycles are a first CDRX cycle, and the first CDRX cycle is used to control the time when the terminal device enters the operation duration to coincide with the time when the network device transmits the downlink frame of the first service according to the service cycle. Based on this solution, the terminal device can determine a first CDRX cycle for controlling the time when the terminal device enters the operation duration according to the second information so as to coincide with the time when the network device transmits the downlink frame of the first service according to the service cycle.

[0023] In relation to the second aspect, in another possible implementation, the second information includes identification information corresponding to the first CDRX cycle. Based on this solution, second information for determining the first CDRX cycle is provided according to the identification information.

[0024] In relation to the second aspect, in possible implementations, the second information is carried in an RRC message, or the second information is carried in a MAC CE message. Based on this solution, the first CDRX cycle can be configured semi-statically in the terminal device through the second information in the RRC message. Alternatively, the first CDRX cycle can be dynamically updated through the second information in the MACCE message.

[0025] In relation to the second aspect, in a possible implementation, the method further includes: the terminal device receives third information from the network device, where the third information is used by the network device to configure the plurality of CDRX cycles for the terminal device, and the plurality of CDRX cycles comprises one or more CDRX cycles. Based on this solution, the plurality of CDRX cycles can be configured for the terminal device through the third information.

[0026] In relation to the second aspect, in a possible implementation, the third information includes identification information corresponding to each CDRX cycle in a plurality of CDRX cycles, and configuration information for the CDRX cycle corresponding to the identification information. Based on this solution, each CDRX cycle in a plurality of CDRX cycles configured for a terminal device has corresponding identification information, and the corresponding CDRX cycle can be determined from a plurality of configured CDRX cycles according to the identification information.

[0027] In relation to the second aspect, in possible implementations, the third information is carried in an RRC message. Based on this solution, multiple CDRX cycles can be semi-statically configured in a terminal device through the third information in the RRC message.

[0028] A terminal energy saving method is provided according to a third embodiment. The method includes the following: A terminal device receives fourth information from a network device, where the fourth information indicates the time when the terminal device will next enter an operational duration after receiving a first downlink frame of a first service, and the time when the terminal device will next enter an operational duration coincides with the time when the network device transmits a second downlink frame of the first service, and the second downlink frame is a first downlink frame transmitted by the network device after the first downlink frame according to the service cycle. The terminal device then determines the time when it will next enter an operational duration after receiving the first downlink frame, according to the fourth information. Based on this solution, the network device can control the time when the terminal device enters an operational duration each time, according to the fourth information, so as to coincide with the time when the first downlink frame of the first service is transmitted.

[0029] In relation to the third aspect, in a possible implementation, the fourth information is carried in the last data packet included in the first downlink frame.

[0030] In relation to the third embodiment, in a possible implementation, the fourth information further indicates that the terminal device enters a non-operational duration after receiving the first downlink frame.

[0031] In relation to the third aspect, in a possible implementation, the fourth information is carried in a MAC CE message, which is a control element of media access control. Based on this solution, the fourth information in the MACCE message may be used to dynamically indicate when a terminal device enters an operational duration.

[0032] A communication device is provided according to a fourth embodiment. The communication device has a function to implement the method according to the first embodiment. This function may be implemented by using hardware or by running corresponding software on hardware. The hardware or software includes one or more modules corresponding to the function described above. For example, the communication device may include a transceiver module and a processing module. The transceiver module is configured to receive first information from a network device, the first information being used to determine a first CDRX cycle corresponding to the communication device. The processing module is configured to determine when the communication device enters an operational duration according to the first CDRX cycle and a first calculation rule, the first calculation rule being used to control when the communication device enters the operational duration so that it coincides with when the network device transmits a downlink frame for a first service according to a service cycle.

[0033] In relation to the fourth aspect, in a possible implementation, the first CDRX cycle corresponding to the communication device is a first CDRX cycle configured by network devices for the communication device, and the first CDRX cycle is the same as the service cycle.

[0034] In relation to the fourth aspect, in a possible implementation, the first calculation rule is:

number

number

[0035] In relation to a fourth aspect, in a possible implementation, the first information includes the service cycle of the first service, or the first information includes the value of the first CDRX cycle, or the first information includes the frequency of the first CDRX cycle, or the first information includes a preset integer value, and the preset integer value is used by the communication device to determine the first CDRX cycle according to a preset relationship.

[0036] In relation to the fourth aspect, in possible implementations, the first information is carried in a wireless resource control RRC message.

[0037] In relation to the fourth aspect, in a possible implementation, the first CDRX cycle corresponding to the communication device is the first CDRX cycle obtained by adjusting the CDRX cycle configured for the communication device in accordance with the first information.

[0038] In relation to the fourth aspect, in a possible implementation, the first calculation rule is: [(SFN×10)+subframe number]modulo(drx-Cycle + cycle-adjust) =drx-StartOffset, or [(SFN×10)+subframe number]modulo(drx-cycle + cycle-adjust) =(drx-StartOffset)modulo(drx-cycle + cycle-adjust) The following relationship is satisfied, where SFN represents the frame number when the communication device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number, drx-cycle represents the CDRX cycle configured by the network device for the communication device, cycle-adjust represents the cycle offset value determined by the communication device according to the first information, (drx-cycle + cycle-adjust) represents the first CDRX cycle corresponding to the communication device, and drx-StartOffset represents the subframe offset before the communication device enters its operational duration.

[0039] In relation to the fourth aspect, in a possible implementation, the first calculation rule is: [(SFN×10)+subframe number]modulo(drx-cycleN) =drx-StartOffset, or [(SFN×10)+subframe number]modulo(drx-cycleN) =(drx-StartOffset)modulo(drx-cycleN) The following relationship is satisfied, where SFN represents the frame number when the communication device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number, drx-cycleN represents the first CDRX cycle corresponding to the communication device, drx-StartOffset represents the subframe offset before the communication device enters its operational duration, and drx-cycleN satisfies the relationship drx-cycleN=drx-cycle(N-1)+cycle-adjust, where drx-cycle(N-1) represents the CDRX cycle configured before the communication device enters its operational duration, and when drx-cycle(N-1)=drx-cycle0, drx-cycle0 represents the CDRX cycle configured for the communication device by the network device, and cycle-adjust represents the cycle offset value determined by the communication device according to the first information.

[0040] In relation to the fourth aspect, in possible implementations, the first information is carried in a MAC CE message of the media access control element.

[0041] For the technical effects of the fourth embodiment, please refer to the technical effects of the first embodiment. Further details will not be explained here.

[0042] A communication device is provided according to a fifth aspect. The communication device has a function to perform a method according to a second aspect. This function may be implemented by using hardware or by running corresponding software on hardware. The hardware or software includes one or more modules corresponding to the function described above. For example, the communication device may include a transceiver module and a processing module. The transceiver module is configured to receive second information from a network device, the second information is used to determine one or more CDRX cycles in a plurality of CDRX cycles configured by the network device for the communication device, the one or more CDRX cycles are used to control when the communication device enters an operational duration, such that the network device transmits a downlink frame for a first service according to a service cycle. The processing module is configured to determine when the communication device enters the operational duration according to the one or more CDRX cycles.

[0043] In relation to a fifth aspect, in a possible implementation, the one or more CDRX cycles are a plurality of periodic CDRX cycles, which are used to control the time when the communication device corresponding to each CDRX cycle in the plurality of periodic CDRX cycles enters the operating duration, so that the time when the network device transmits the downlink frame of the first service in accordance with the service cycle.

[0044] In relation to the fifth aspect, in a possible implementation, the second information includes identification information and a sequence of identification information corresponding to each CDRX cycle in a plurality of periodic CDRX cycles, wherein the sequence of identification information corresponds to a periodic sequence of the plurality of periodic CDRX cycles.

[0045] In relation to the fifth aspect, in possible implementations, the second information is carried in a wireless resource control RRC message, or the second information is carried in a media access control MAC CE message.

[0046] In relation to a fifth aspect, in a possible implementation, the one or more CDRX cycles are a first CDRX cycle, and the first CDRX cycle is used to control the time when the communication device enters the operating duration, so that the time when the network device transmits the downlink frame of the first service in accordance with the service cycle.

[0047] In relation to the fifth aspect, in another possible implementation, the second information includes identification information corresponding to the first CDRX cycle.

[0048] In relation to the fifth aspect, in possible implementations, the second information is carried in an RRC message, or the second information is carried in a MAC CE message.

[0049] In relation to a fifth aspect, in a possible implementation, the transceiver module is further configured to receive third information from the network device, where the third information is used by the network device to constitute the plurality of CDRX cycles for the communication device, and the plurality of CDRX cycles comprises one or more CDRX cycles.

[0050] In relation to the fifth aspect, in a possible implementation, the third information includes identification information corresponding to each CDRX cycle in a plurality of CDRX cycles, and configuration information for the CDRX cycle corresponding to the identification information.

[0051] In relation to the fifth aspect, in possible implementations, the third information is carried in an RRC message.

[0052] For the technical effects of the fifth embodiment, please refer to the technical effects of the second embodiment. Further details will not be explained here.

[0053] A communication device is provided according to a sixth embodiment. This communication device has a function to carry out the method according to the third embodiment. This function may be implemented by using hardware or by running corresponding software on hardware. The hardware or software includes one or more modules corresponding to the function described above. For example, the communication device may include a transceiver module and a processing module. The transceiver module is configured to receive fourth information from a network device, where the fourth information indicates the time when the communication device will next enter an operational duration after receiving a first downlink frame of a first service, the time when the communication device will next enter an operational duration coincides with the time when the network device transmits a second downlink frame of the first service, and the second downlink frame is a first downlink frame transmitted by the network device after the first downlink frame, according to the service cycle. The processing module is configured to determine, according to the fourth information, the time when the communication device will next enter the operational duration after receiving the first downlink frame.

[0054] In relation to the sixth aspect, in a possible implementation, the fourth information is carried in the last data packet included in the first downlink frame.

[0055] In relation to the sixth aspect, in a possible implementation, the fourth information further indicates that the communication device enters a non-operational duration after receiving the first downlink frame.

[0056] In relation to the sixth aspect, in possible implementations, the fourth information is carried in a MAC CE message of the media access control element.

[0057] For the technical effects of the sixth aspect, please refer to the technical effects of the third aspect. Further details will not be explained here.

[0058] A communication device is provided according to the seventh embodiment, and the communication device includes a processor and memory. The memory is configured to store computer executable instructions. When the communication device is operating, the processor executes the computer executable instructions stored in memory, and as a result, the communication device performs a terminal energy saving method according to any one of the first, second, or third embodiments.

[0059] A communication device is provided according to the eighth aspect, and the communication device includes a processor. The processor is coupled to memory and, after reading an instruction in memory, is configured to perform a terminal energy saving method according to any one of the first, second, or third aspects in accordance with the instruction.

[0060] A communication device is provided according to the ninth aspect, the communication device comprising a processor, memory, and a transceiver. The memory is configured to store executable instructions, the processor is configured to execute the instructions stored in the memory, and the transceiver is configured to communicate between the communication device and another device in a communication network. When the communication device is operating, the processor executes the instructions and the transceiver communicates with another device in the communication network, and as a result, the communication device performs a terminal energy saving method according to any one of the first, second, or third aspects.

[0061] A computer-readable storage medium is provided according to a tenth aspect. The computer-readable storage medium stores instructions. When the instructions are executed on a computer, the computer is enabled to perform a terminal energy saving method according to any one of the first, second, or third aspects.

[0062] A computer program product including instructions is provided according to the eleventh aspect. When the instructions are executed on a computer, the computer is enabled to perform a terminal energy saving method according to any one of the first, second, or third aspects.

[0063] A communication device is provided according to the twelfth embodiment. The communication device includes a processor configured to support the communication device in order to perform a function related to any one of the first, second, or third embodiments. In a possible design, the communication device further includes memory. The memory is configured to store program instructions and data necessary for the communication device. The device may include a chip, or it may include a chip and another discrete device.

[0064] A communication system is provided according to the 13th embodiment. The communication system includes a terminal device and a network device that perform the method described in the first embodiment, or a terminal device and a network device that perform the method described in the second embodiment, or a terminal device and a network device that perform the method described in the third embodiment.

[0065] For technical effects resulting from any implementation in aspects 7 through 13, please refer to the technical effects resulting from different implementations in aspects 1, 2, or 3. Further details are not provided here. [Brief explanation of the drawing]

[0066] [Figure 1] Figure 1 is a schematic diagram relating to a CDRX cycle according to one embodiment of this application. [Figure 2]Figure 2 is a schematic diagram relating to the XR service cycle and CDRX cycle according to one embodiment of this application. [Figure 3] Figure 3 is a schematic diagram relating to the structure of a communication system according to one embodiment of this application. [Figure 4] Figure 4 is a schematic diagram relating to the structure of a network device and terminal device according to one embodiment of this application. [Figure 5] Figure 5 is a schematic diagram relating to another structure of a terminal device according to one embodiment of this application. [Figure 6] Figure 6 is a schematic diagram relating to the interaction of a first terminal energy saving method according to one embodiment of this application. [Figure 7] Figure 7 is a schematic diagram relating to MACCE according to one embodiment of this application. [Figure 8] Figure 8 is a schematic diagram relating to the interaction of a second terminal energy saving method according to one embodiment of this application. [Figure 9] Figure 9 is a schematic diagram relating to another MACCE according to one embodiment of this application. [Figure 10] Figure 10 is a schematic diagram relating to the interaction of a third terminal energy saving method according to one embodiment of this application. [Figure 11] Figure 11 is a schematic diagram relating to the interaction of a fourth terminal energy saving method according to one embodiment of this application. [Figure 12] Figure 12 is a schematic diagram relating to the interaction of a fifth terminal energy saving method according to one embodiment of this application. [Figure 13] Figure 13 is a schematic diagram relating to yet another MACCE according to one embodiment of this application. [Figure 14] Figure 14 is a schematic diagram relating to the structure of a communication device according to one embodiment of this application. [Figure 15] Figure 15 is a schematic diagram relating to the structure of another communication device according to one embodiment of this application. [Modes for carrying out the invention]

[0067] Before the embodiments of this application are described in detail, a brief introduction to the relevant technologies of this application is provided below to facilitate understanding of the technical solutions according to the embodiments of this application.

[0068] 1. CDRX Mechanism

[0069] The CDRX mechanism is an effective energy-saving technology. When CDRX is configured for a terminal device, the terminal device can enter a sleep period at a specific time. In this case, the terminal device is in a "sleep state" or "non-operational duration," and does not need to monitor the PDCCH. When it is necessary to monitor the PDCCH in order to receive downlink service data, the terminal device is woken from the "sleep state" and enters an "activated state," that is, an activation duration. In this way, the terminal device can achieve the objective of saving power.

[0070] A typical CDRX cycle is shown in Figure 1.

[0071] Operating Duration: After a terminal device is activated, it enters a fixed-length operating duration. This fixed-length operating duration may be referred to as the on-duration. If the terminal device receives a scheduled PDCCH during the on-duration, it remains in the awakened state and extends the operating duration. The length of the on-duration is determined by the network device for the terminal device.

[0072] Non-operational duration: This duration is the sleep time in the CDRX mechanism, i.e., the time during which the terminal device enters sleep mode without monitoring the PDCCH in order to conserve power.

[0073] CDRX cycle: This is a repeating cycle of on-duration, i.e., the time interval between the moment the terminal device last entered an operating duration and the next moment the terminal device enters an operating duration. The CDRX cycle includes operating and non-operating durations.

[0074] Currently, the CDRX cycle is a fixed value semi-statically configured in a terminal device by a network device through a radio resource control (RRC) message. The protocol specifies that all possible CDRX cycle values ​​are integers. In addition, when a network device configures a CDRX cycle for a terminal device, it can further indicate whether the configured CDRX cycle is long or short. For example, a short DRX field in an RRC message indicates that a configured CDRX cycle of 10 milliseconds is a short cycle.

[0075] Whether a CDRX cycle is long or short depends on the moment at which the terminal device enters its operational period. The following explains how the terminal device determines the moment at which it enters its operational period.

[0076] In the current CDRX mechanism, the terminal device determines the point at which it enters the operational duration period through the following equation.

[0077] If the CDRX cycle (drx-cycle) is a long DRX cycle: [(SFN×10)+subframe number]modulo(drx-cycle) =drx-StartOffset Equation (1)

[0078] If the CDRX cycle (drx-cycle) is a short cycle (shortDRXcycle): [(SFN×10)+subframe number]modulo(drx-cycle) =(drx-StartOffset)modulo(drx-cycle) Formula (2)

[0079] SFN represents the system frame number when the terminal device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number when the terminal device enters its operational duration, drx-cycle represents the CDRX cycle of the terminal device, and drx-StartOffset represents the subframe offset before the terminal device entered its operational duration.

[0080] In the parameters described above, the value of drx-cycle is a fixed integer configured by the network device, and the value of drx-StartOffset is also a fixed value configured by the network device for the terminal device. SFN can be any integer from 0 to 1023. The subframe number can be any integer from 0 to 9.

[0081] To avoid ambiguity, the operator modulo in equation (1) or equation (2) is explained here. a modulo b means the remainder obtained by dividing a by b. This is explained consistently here and will not be repeated below.

[0082] The terminal device determines the values ​​of SFN and subframe number that satisfy equation (1) or (2) above, based on the values ​​of drx-cycle and drx-StartOffset in the aforementioned parameters, as well as the SFN and subframe number currently associated with the terminal device. Then, according to the obtained values ​​of SFN and subframe number, the terminal device can determine the system frame number and subframe number in the system frame when it next enters its operational duration. For example, assuming drx-cycle=8 and drx-StartOffset=0, the terminal device determines, according to the system message broadcast by the network device, that the SFN currently associated with the terminal device is equal to 0, subframe number=0, and CDRX cycle is short cycle. The terminal device substitutes the values ​​of drx-cycle and drx-StartOffset into equation (2) and begins evaluating the SFN and subframe number from SFN=0 and subframe number=0 until it obtains values ​​of SFN and subframe number that satisfy equation (2). The terminal device determines that SFN=0 and subframe number=0 satisfy equation (2). Therefore, the point in time when the terminal device first enters its operational duration corresponds to the point in time when subframe number 0 is in the system frame having frame number 0. After the terminal device first enters its operational duration, the values ​​of SFN and subframe number that satisfy equation (2) are determined again, starting from the terminal device's current SFN and subframe number. It is found that equation (2) is satisfied when SFN=0 and subframe number=8. Therefore, after the terminal device first enters its operational duration, the point in time when it is determined that the terminal device will enter its operational duration again (the point in time when the terminal device enters its operational duration for the second time) corresponds to the point in time when subframe number 8 is in the system frame having frame number 0.By analogy, the point in time when it is determined that the terminal device will enter its next operational period after it has entered its second operational period (the point in time when the terminal device enters its third operational period) corresponds to subframe number 6 in the system frame having frame number 1.

[0083] Furthermore, after determining the system frame number and the subframe number within the system frame at which the terminal device enters its operational duration, the terminal device may further determine when it enters the operational duration within the subframe, according to a slot offset (drx-slot offset) configured by the network device for the terminal device. For example, starting from the beginning position of the subframe in the determined system frame, the terminal device enters an operational duration with an offset of drx-slot offset * 1 / 32 ms.

[0084] With the advancement of communication technology, XR services have also emerged and continue to develop. To improve the user experience, terminal devices running XR services need to be lightweight (e.g., VR glasses), and XR services themselves need to have high throughput and low latency. To meet these requirements, terminal devices require high power consumption to run XR services. Therefore, several topics point to how to reduce the power consumption of XR services as an important research direction.

[0085] To reduce the power consumption of terminal devices running XR services, a CDRX mechanism may be configured for terminal devices running XR services. However, downlink frames in current XR services have periodic characteristics, and service cycles are all decimal numbers. For example, if the service frame rate is 120 fps, the service cycle for one frame is 8.33 ms. If the service frame rate is 60 fps, the service cycle for one frame is 16.67 ms. Currently, all CDRX cycles that can be configured for terminal devices are integers. Therefore, when a CDRX mechanism is configured for a terminal device running XR services, even if the CDRX cycle configured for the terminal device is closest to the service cycle of the XR service, for example, if the service cycle of the XR service is 8.33 ms, an 8 ms CDRX cycle will be configured for the terminal device, and the CDRX cycle of the terminal device cannot match the service cycle of the XR service. In other words, the time at which data can be transmitted by the terminal device and the time at which the transmitted XR service data are transmitted do not coincide. For example, as shown in Figure 2, assuming the service cycle of the XR service is 8.33 ms, the network device sends downlink frames for the XR service every 8.33 ms. The configured CDRX cycle for the terminal device is 8 ms. Over time, the mismatch between the XR service cycle and the CDRX cycle gradually increases until the transmission time of the XR service downlink frames is completely offset from the operating duration of the terminal device. As can be seen from Figure 2, if the terminal device's CDRX cycle does not match the XR service cycle, the following situations occur: 1. When the terminal device is within its operating duration, there is no XR service data (service frames) to be transmitted, resulting in wasted power consumption of the terminal device. 2. When there is XR service data to be transmitted, the terminal device cannot receive the data when it is in a non-operating duration. The data can only be received when the terminal device enters the next operating duration.As a result, the delay of the XR service performed by the terminal device does not meet the delay requirements for the XR service. 3. The overall capacity and quality of the communication system deteriorates.

[0086] In summary, following existing technical solutions results in terminal equipment CDRX cycles not matching the service cycles of XR services, leading to problems such as wasted power consumption in terminal equipment or inability to meet the latency requirements of XR services. Therefore, how to align terminal equipment CDRX cycles with the service cycles of XR services is an urgent issue that needs to be resolved.

[0087] The following describes the technical solutions in embodiments of this application with reference to the accompanying drawings. In this description, unless otherwise specified, " / " indicates an "or" relationship between related objects. For example, A / B may indicate A or B. In this application, "and / or" describes only related relationships between related objects and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: A exists only, A and B exist together, or B exists only, where A and B may be singular or plural. In addition, in this description, unless otherwise specified, "a plurality of" means two or more. At least one of the following items (pieces), or similar expressions, refers to a singular item (piece) or any combination of these items, and includes any combination of multiple items (pieces). For example, at least one item (piece) among a, b, or c may represent a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c may be singular or plural. In addition, in order to clearly describe the technical solutions in the embodiments of this application, terms such as "first" and "second" are used in the embodiments of this application to distinguish the same or similar items that provide essentially the same function or purpose. Those skilled in the art will understand that terms such as "first" and "second" do not limit the quantity or order of execution, and that terms such as "first" and "second" do not indicate a clear distinction. Furthermore, in the embodiments of this application, terms such as "illustrative" and "for example" are used to present an example, instance, or illustration. Any embodiment or design scheme described as "example" or "for example" in the embodiments of this application should not be described as being preferable or having more advantages than another embodiment or design scheme.More precisely, terms like "exemplary" and "for example" are intended to present specific examples of related concepts to facilitate understanding.

[0088] In addition, the network architectures and service scenarios described in the embodiments of this application are intended to more clearly illustrate the technical solutions in the embodiments of this application and do not constitute a limitation to the technical solutions provided in the embodiments of this application. Those skilled in the art will know that, with the evolution of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0089] The terminal energy saving method provided in the embodiments of this application may be applied to a variety of communication systems. For example, the terminal energy saving method provided in the embodiments of this application may be applied to long-term evolution (LTE) systems, fifth-generation (5G) systems, or other similar new future-oriented systems. This is not particularly limited to the embodiments of this application. In addition, the term "system" may be used interchangeably with "network".

[0090] Figure 3 shows a communication system 30 according to one embodiment of the present application. The communication system 30 includes a network device 40 and terminal devices 50 connected to the network device 40. The terminal devices 50 are connected to the network device 40 wirelessly. Optionally, different terminal devices 50 may communicate with each other. The terminal devices 50 may be in a fixed location or may be mobile.

[0091] Figure 3 is merely a schematic diagram, and it should be noted that, although not shown, the communication system 30 may also include other network devices. For example, the communication system 30 may also include one or more of a core network device, a wireless relay device, and a wireless backhaul device, and this is not particularly limited herein. Network devices may be connected to the core network device wirelessly or wired. The core network device and network device 40 may be separate physical devices, or the functions of the core network device and the logical functions of network device 40 may be integrated on the same physical device, or some functions of the core network device and some functions of network device 40 may be integrated on a single physical device. This is not particularly limited in the embodiments of this application.

[0092] As one example, by using the interaction between the network device 40 and an arbitrary terminal device 50 shown in Figure 3, in a possible implementation, the network device 40 is configured to transmit first information to the terminal device 50. The terminal device 50 is configured to receive the first information from the network device 40, which is used by the terminal device 50 to determine a first CDRX cycle corresponding to the terminal device 50. The terminal device 50 is further configured to determine the moment at which the terminal device 50 enters an operational duration, according to the first CDRX cycle and a first calculation rule, where the first calculation rule is used to control the moment at which the terminal device 50 enters an operational duration, according to a service cycle, to coincide with the moment when the network device 40 transmits a downlink frame for a first service. Specific implementations of this solution will be described in detail in embodiments of the subsequent method. Details are not described here.

[0093] Alternatively, as one example, in another possible implementation, by using the interaction between the network device 40 and an arbitrary terminal device 50 shown in Figure 3, the network device 40 is configured to transmit second information to the terminal device 50. The terminal device 50 is configured to receive second information from the network device 40, which is used by the terminal device 50 to determine one or more CDRX cycles in a plurality of CDRX cycles configured by the network device 40 for the terminal device 50, and which one or more CDRX cycles are used to control when the terminal device 50 enters an operational duration so as to coincide with the time when the network device 40 transmits a downlink frame for a first service, according to a service cycle. The terminal device 50 is further configured to determine when the terminal device 50 enters an operational duration according to one or more CDRX cycles. Specific implementations and technical effects of this solution will be described in detail in embodiments of subsequent methods. Details are not described here.

[0094] Alternatively, as one example, in yet another possible implementation, by using the interaction between the network device 40 and an arbitrary terminal device 50 shown in Figure 3, the network device 40 is configured to transmit a fourth piece of information to the terminal device 50. The terminal device 50 is configured to receive the fourth piece of information from the network device 40, where the fourth piece of information indicates when the terminal device 50 will next enter an operational duration after receiving the first downlink frame of the first service, and this timing coincides with when the network device 40 transmits the second downlink frame of the first service, and the second downlink frame is the first downlink frame transmitted by the network device 40 after the first downlink frame, according to the service cycle. The terminal device 50 is further configured to determine, according to the fourth piece of information, when the terminal device 50 will next enter an operational duration after receiving the first downlink frame. The specific implementation and technical effects of this solution will be described in detail in embodiments of the subsequent method. Details are not described here.

[0095] Optionally, the network device 40 in this embodiment of the present application is a device that connects a terminal device 50 to a wireless network and may be a base station, an evolved node B (eNodeB), a transmission reception point (TRP), a next-generation node B (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless-fidelity (Wi-Fi®) system, or it may be a module or unit that completes some functions of a base station, for example, a central unit (CU) or a distributed unit (DU). The specific technology and specific device form used by the network device are not limited to the embodiments of the present application. In this application, unless otherwise specified, a network device refers to a wireless access network device.

[0096] Optionally, the terminal device 50 in the embodiments of this application may be a device such as a terminal or a chip that can be used in a terminal, configured to implement wireless communication functionality. The terminal may also be called user equipment (UE), mobile station, mobile terminal, etc. The terminal may be a mobile phone, tablet PC, computer with wireless transmission and reception capabilities, virtual reality terminal device, augmented reality terminal device, wireless terminal in industrial control, wireless terminal in autonomous driving, wireless terminal in remote surgery, wireless terminal in smart grids, wireless terminal in traffic safety, wireless terminal in smart cities, wireless terminal in smart homes, etc. The specific technologies and specific device forms used by the terminal device are not limited to the embodiments of this application.

[0097] Optionally, the network device 40 and terminal device 50 in this embodiment of the present application may be located on the ground, including indoors, outdoors, handheld, or vehicle-mounted, or on water, or in the air on an airplane, balloon, or satellite. The application scenarios for the network device 40 and terminal device 50 are not limited to the embodiments of the present application.

[0098] Optionally, communication between the network device 40 and the terminal device 50 in this embodiment of the present application may be performed using a licensed spectrum, or using an unlicensed spectrum, or using both a licensed spectrum and an unlicensed spectrum. Optionally, communication between the network device 40 and the terminal device 50 may be performed using a spectrum below 6 gigahertz (GHz), or using a spectrum above 6 GHz, or using both a spectrum below 6 GHz and a spectrum above 6 GHz. The spectrum resources used between the network device 40 and the terminal device 50 are not limited to this embodiment of the present application.

[0099] Optionally, the network device 40 and terminal device 50 in this embodiment of the present application may also be called communication devices, and may be general-purpose devices or dedicated devices, respectively. This is not particularly limited in this embodiment of the present application.

[0100] Optionally, Figure 4 is a schematic diagram relating to the structure of a network device 40 and a terminal device 50 according to one embodiment of this application.

[0101] The terminal device 50 includes at least one processor 501 and at least one transceiver 503. Optionally, the terminal device 50 may further include at least one memory 502, at least one output device 504, or at least one input device 505.

[0102] The processor 501, memory 502, and transceiver 503 are interconnected via a communication line. The communication line may include a path for transmitting information between the aforementioned components.

[0103] The processor 501 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any ordinary processor. In a specific implementation, in one embodiment, the processor 501 may include multiple CPUs, and the processor 501 may be a single-core processor or a multi-core processor. The processor as used herein may be one or more devices, circuits, and / or processing cores used for data processing.

[0104] Memory 502 may be a device having storage functionality. For example, memory may be read-only memory (ROM), another type of static storage device capable of storing static information and instructions, random access memory (RAM), or another type of dynamic storage device capable of storing information and instructions, or programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CDROM), or another optical disc storage, optical disc storage (including compact optical discs, laser discs, optical discs, digital multipurpose discs, Blu-ray® discs, etc.), magnetic recording disc storage media or other magnetic storage devices, or any other medium that can be configured to carry or store program code expected in the form of instructions or data structures and is accessible to a computer. However, this does not constitute a limitation. Memory 502 may exist independently and be connected to processor 501 via a communication line. Alternatively, memory 502 may be integrated with processor 501.

[0105] Memory 502 is configured to store computer executable instructions for executing the solution in this application, and the processor 501 controls the execution. Specifically, the processor 501 is configured to execute computer executable instructions stored in memory 502 in order to implement the terminal energy saving method in the embodiment of this application.

[0106] Alternatively, and optionally, in this embodiment of the present application, the processor 501 may also perform functions related to processing in the terminal energy saving method provided in subsequent embodiments of the present application, and the transceiver 503 may be responsible for communicating with other devices or communication networks. The embodiments of the present application do not impose any specific limitations thereon.

[0107] Optionally, the computer executable instructions in this embodiment of the present application may also be referred to as application program code or computer program code. This is not particularly limited to this embodiment of the present application.

[0108] The transceiver 503 can be configured to communicate with another device or a communication network, such as Ethernet®, a radio access network (RAN), or a wireless local area network (WLAN), by using any device such as a transceiver. The access network transceiver 503 includes a transmitter (Tx) and a receiver (Rx).

[0109] The output device 504 communicates with the processor 501 and can display information in multiple ways. For example, the output device 504 may be a liquid crystal display (LCD), a light-emitting diode (LED) display, a cathode ray tube (CRT) display, a projector, etc.

[0110] The input device 505 communicates with the processor 501 and can receive input from the user in multiple ways. For example, the input device 505 may be a mouse, keyboard, touchscreen device, or sensor device.

[0111] The network device 40 includes at least one processor 401, at least one transceiver 403, and at least one network interface 404. Optionally, the network device 40 may further include at least one memory 402. The processor 401, memory 402, transceiver 403, and network interface 404 are connected via a communication line. The network interface 404 is configured to connect to a core network device via a link (e.g., S1 interface) or to a network interface of another network device via a wired or wireless link (e.g., X2 interface) (not shown in Figure 3). This is not particularly limited in this embodiment of the present application. In addition, for a description of the processor 401, memory 402, and transceiver 403, see the description of the processor 501, memory 502, and transceiver 503 in the terminal device 50. Details are again not described here.

[0112] Referring to the schematic diagram of the structure of the terminal device 50 shown in Figure 4, for example, Figure 5 shows a specific structural configuration of the terminal device 50 according to one embodiment of this application.

[0113] In some embodiments, the functions of the processor 501 in Figure 4 can be implemented by the processor 110 in Figure 5.

[0114] In some embodiments, the functionality of the transceiver 503 in Figure 4 may be implemented by antennas 1 and 2, a mobile communication module 150, a wireless communication module 160, etc., in Figure 5. The mobile communication module 150 may include wireless communication technology solutions for application to the terminal device 50, including LTE, NR, future communications, etc. The wireless communication module 160 may include wireless communication technology solutions for application to the terminal device 50, including, for example, WLAN (e.g., Wi-Fi network), BT (Bluetooth®, BT), global navigation satellite system (GNSS), frequency modulation (FM), near-field communication (NFC), and infrared (IR). In some embodiments, antenna 1 of the terminal device 50 is coupled to the mobile communication module 150, and antenna 2 is coupled to the wireless communication module 160, so that the terminal device 50 can communicate with networks and other devices by using wireless communication technology.

[0115] In some embodiments, the functionality of memory 502 in Figure 4 can be implemented by internal memory 121 in Figure 5, external memory connected by using external memory interface 120, and so on.

[0116] In some embodiments, the function of the output device 504 in Figure 4 can be implemented by the display 194 in Figure 5.

[0117] In some embodiments, the functions of the input device 505 in Figure 4 may be implemented by a mouse, keyboard, touchscreen device, or the sensor module 180 in Figure 5.

[0118] In some embodiments, as shown in Figure 4, the terminal device 50 may further include one or more of the following: an audio module 170, a camera 193, a key 190, a SIM card interface 195, a USB interface 130, a charging management module 140, a power management module 141, and a battery 142.

[0119] It will be understood that the structure shown in Figure 5 does not constitute a specific limitation on the terminal device 50. For example, in some other embodiments of this application, the terminal device 50 may include more or fewer components than those shown in the figure, or some components may be combined, some components may be separated, or components may be arranged differently. The components shown in the figure may be implemented by hardware, software, or a combination of software and hardware.

[0120] Referring to Figures 1 to 5, a terminal energy saving method provided in embodiments of this application is described below by using an interaction between a network device 40 and an arbitrary terminal device 50, as shown in Figure 3 as one example.

[0121] In this embodiment of the present application, it should be noted that the terminal device may indicate the point in time when the terminal device enters the operational duration in the form of a subframe number. Specifically, as can be seen from the above description that the terminal device determines the point in time when the terminal device enters the operational duration according to formula (1) or (2), the determination of an SFN and subframe number that satisfies formula (1) or (2) by the terminal device may be understood as determining [(SFN × 10) + subframe number] that satisfies formula (1) or (2). Therefore, the terminal device can express the determined [(SFN × 10) + subframe number] in the form of a subframe number. For example, the terminal device determines that formula (1) is satisfied when SFN = 1 and subframe number = 9. The terminal device determines that the subframe number when the terminal device enters the operational duration is 19, according to SFN × 10 + subframe number = 19. The length of one subframe is 1 ms. In accordance with the range of SFN and subframe number values ​​described above, in this embodiment of the present application, the value of the subframe number when the terminal device enters the operational duration is any integer from 0 to 10239.

[0122] It should be noted that in this embodiment of the present application, matching between two can be understood as the two being equal, or the distance between the two being within a specific threshold. The specific threshold is less than or equal to the length of the on-duration configured by the network device for the terminal device. In other words, the timing at which the terminal device enters its on-duration can be understood as the timing at which the network device transmits a downlink frame for the first service according to the service cycle, meaning that each time the network device delivers a downlink frame for the first service, the terminal device can receive the downlink frame during its on-duration. Thus, the terminal device does not waste power, and the downlink frame for the first service does not wait before it can be received until the terminal device next enters its on-duration, thereby satisfying the delay requirement for the first service.

[0123] To briefly explain how a terminal device determines when it enters its operational duration, it should be noted that in this embodiment of the present application, the slot offset (drx-slot offset) configured by the network device for the terminal device is 0. This has been described uniformly in this specification and will not be repeated below.

[0124] A terminal energy saving method provided in one embodiment of this application is described below. As shown in Figure 6, the terminal energy saving method provided in this embodiment of this application includes the following steps S601 and S602.

[0125] S601: The network device transmits first information to the terminal device. In response, the terminal device receives first information from the network device. Here, the first information is used by the terminal device to determine the first CDRX cycle corresponding to the terminal device.

[0126] S602: The terminal device determines when it enters its operational duration according to the first CDRX cycle and the first calculation rule. Here, the first calculation rule is used to control when the terminal device enters its operational duration so that it coincides with when the network device transmits a downlink frame for the first service according to the service cycle.

[0127] Steps S601 and S602 in two specific embodiments will be described below.

[0128] Embodiment 1: In this solution, after a terminal device receives first information from a network device, it can be determined, according to the first information, that the first CDRX cycle corresponding to the terminal device is the first CDRX cycle configured by the network device for the terminal device. Here, the first CDRX cycle is the same as the service cycle of the first service. In other words, the network device can, through the first information, configure a first CDRX cycle for the terminal device that is the same as the service cycle of the first service. After configuring the first CDRX cycle according to the first information, it can be understood that the terminal device continues to execute the CDRX mechanism using the configured first CDRX cycle until it is instructed to change the first CDRX cycle according to information from the network device. Based on this solution, the terminal device can, according to the first information, configure a first CDRX cycle that is the same as the service cycle of the first service, so as to match the service cycle of the first service.

[0129] Optionally, the service cycle of the first service may be a decimal value. Correspondingly, the first CDRX cycle, configured according to the first information, is the same decimal value as the service cycle. For example, the first service is an XR service, and its service cycle is 8.33 ms. The network device transmits the first information to the terminal device according to the service cycle of the first service, and configures the terminal device's first CDRX cycle to 8.33 ms.

[0130] Optionally, in Embodiment 1 of this application, the first information may be carried by an RRC message. In other words, the network device semi-statically constitutes a first CDRX cycle in the terminal device through the RRC message.

[0131] In Embodiment 1 of this application, the network device can configure a first CDRX cycle for a terminal device through first information in any form of the following forms of first information.

[0132] The first piece of information indicates the service cycle of the first service, or the first piece of information indicates the first CDRX cycle. Here, the first CDRX cycle indicated by the first piece of information is the same as the service cycle of the first service.

[0133] In the case where the first information indicates the service cycle of the first service, specifically, the first information is used to configure the terminal device's first CDRX cycle to be the same as the service cycle of the first service indicated by the first information. After receiving the first information, the terminal device determines the service cycle of the first service according to the first information and configures the determined service cycle of the first service as the first CDRX cycle.

[0134] In the example where the first information indicates the first CDRX cycle, specifically, the first information is used to configure the first CDRX cycle of the terminal device to be the same as the CDRX cycle indicated by the first information, and the first CDRX cycle indicated by the first information is the same as the service cycle of the first service.

[0135] Optionally, the first information includes the value of the first CDRX cycle. For example, if the service cycle of the first service is 8.33 ms, and the first information transmitted by the network device includes the value of the first CDRX cycle, 8.33. After receiving the first information, the terminal device configures the first CDRX cycle to 8.33 ms according to the first information and the default unit of the first CDRX cycle (ms).

[0136] Alternatively, and optionally, the first information includes the frequency of the first CDRX cycle. For example, the service cycle of the first service is 8.33 ms, and the first information transmitted by the network device includes the value of the frequency of the first CDRX cycle, which is 120. After receiving the first information, the terminal device calculates the first CDRX cycle as (1000 / 120) ms according to a default relationship between the first CDRX cycle and the frequency of the first CDRX cycle. The frequency of the first CDRX cycle is the amount of CDRX cycles per second, and the default unit of the first CDRX cycle is ms. That is, the first CDRX cycle is approximately equal to 8.33 ms. Based on the calculation result, the terminal device configures the first CDRX cycle to 8.33 ms.

[0137] Alternatively, and optionally, the first information includes a pre-configured integer value. After receiving the first information, the terminal device can determine the first CDRX cycle according to the pre-configured integer value and the pre-configured relationship. For example, the pre-configured integer value included in the first information is the integer value INTEGER, and the value of INTEGER is 833. The relationship between INTEGER and the first CDRX cycle is predetermined as firstCDRX cycle = INTEGER, and the unit is 0.01 ms. The terminal device configures the first CDRX cycle to 8.33 ms according to the first information and the predetermined relationship between INTEGER and the first CDRX cycle. In another example, the pre-configured integer value included in the first information is the enumeration value ENUMERATED, and the value of ENUMERATED is 120. The relationship between ENUMERATED and the first CDRX cycle is predetermined as firstCDRX cycle = 1 / ENUMERATED, and the unit is ms. The terminal device configures the first CDRX cycle to 8.33 ms according to the first information and the default relationship between ENUMERATED and the first CDRX cycle.

[0138] Once a pre-configured relationship is determined, the network device can determine a pre-configured integer value according to the pre-configured relationship and the service cycle of the first service, and then transmit first information containing the pre-configured integer value to the terminal device. As a result, the terminal device can determine the same first CDRX cycle as the service cycle of the first service, according to the pre-configured relationship and the pre-configured integer value.

[0139] Furthermore, in this solution, the terminal device can determine when it enters its operational duration based on the first CDRX cycle determined according to the first information and the first calculation rule. The first calculation rule is used to control when the terminal device enters its operational duration so that it coincides with the time when the network device transmits the downlink frame for the first service according to the service cycle.

[0140] In possible implementations, the first computation rule in this solution satisfies the following relationship:

[0141]

number

[0142]

number

[0143] Here, SFN represents the system frame number when the terminal device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number when the terminal device enters its operational duration, drx-cycle represents the first CDRX cycle, and drx-StartOffset represents the subframe offset before the terminal device entered its operational duration.

[0144] For the values ​​of drx-StartOffset, SFN, and subframe number in the aforementioned parameters, please refer to the descriptions of the corresponding parameters in equation (1) or (2) above. Further details will not be explained here.

[0145] To avoid ambiguity, the operators used in equation (3) or equation (4) are explained here.

number

[0146] In Embodiment 1 of this application, when the first CDRX cycle is a long cycle, the first calculation rule satisfies equation (3), and when the first CDRX cycle is a short cycle, the first calculation rule satisfies equation (4). For how the terminal device determines when it enters its operational duration according to the first calculation rule and the first CDRX cycle, see the preceding explanation of equation (1) or equation (2). Further details are not described here.

[0147] In one embodiment, if equation (1) or equation (2) is used to calculate a CDRX cycle that currently has a decimal value to determine when a terminal device enters an operational duration, the calculated subframe number when entering the operational duration is a decimal value. As a result, the terminal device cannot determine the corresponding time when entering the operational duration according to the decimal subframe number. In contrast, in Embodiment 1 of this application, if the first CDRX cycle is a decimal value, the terminal device can determine an integer subframe number when entering the operational duration according to equation (3) or equation (4), and as a result, the operational duration can enter at the time corresponding to the determined subframe number. In another embodiment, if the first CDRX cycle is an integer value, the time when the terminal device determines and enters the operational duration according to equation (3) or equation (4) is the same as the time when the terminal device determines and enters the operational duration according to equation (1) or equation (2). As can be understood, equation (3) or equation (4) provided in Embodiment 1 of this application are compatible with integer CDRX cycles and decimal CDRX cycles.

[0148] For ease of understanding, the following is an illustrative description of how Embodiment 1 of this application ensures that the time when a terminal device enters an operational duration coincides with the time when a network device transmits a downlink frame for the first service, according to the service cycle. Assuming that the service cycle for the first service is 8.33 ms, the first CDRX cycle, configured according to the first information, is also 8.33 ms, and the length of the on-duration configured by the network device for the terminal device is 2 ms. If the first downlink frame for the first service is transmitted at 0 ms, and the subframe number when the terminal device first enters an operational duration is also 0 (corresponding to 0 ms), then the transmission times of each downlink frame for the first service, and the subframe numbers each time the terminal device enters an operational duration, starting from 0 ms, are shown in Table 1 below. [Table 1] Table 1

[0149] In Table 1, the time when the first service downlink frame is transmitted is the time when the network device transmits the first service downlink frame to the terminal device each time, according to the first service's service cycle, and the unit is ms. The subframe number when the terminal device enters the operational duration is the subframe number determined by the terminal device that satisfies [(SFN × 10) + subframe number] in equation (3) or equation (4). The interval refers to the period between the time the terminal device last entered the operational duration (subframe number) and the time the terminal device next enters the operational duration (subframe number), and the unit is ms.

[0150] In Table 1, the subframe number when the terminal device enters the operational duration is determined by the terminal device according to the first CDRX cycle, which is 8.33 ms, and formula (3) or formula (4). As can be seen from the table above, after using the method provided in Embodiment 1 of this application, the difference between the time the terminal device enters the operational duration each time and the time the corresponding downlink frame of the first service is transmitted is within 1 ms and shorter than the length of the on-duration, which is 2 ms. It will be understood that each time the terminal device enters the operational duration, the terminal device is able to receive the corresponding downlink frame of the first service. By using the method in Embodiment 1 of this application, it can be seen that the time the terminal device enters the operational duration each time coincides with the time the downlink frame of the first service is transmitted. The terminal device can satisfy the delay requirements of the first service without wasting power consumption.

[0151] Embodiment 2: In this solution, after a terminal device receives first information from a network device, it may be determined, according to the first information, that the first CDRX cycle corresponding to the terminal device is the first CDRX cycle obtained by the terminal device by adjusting the CDRX cycle configured for the terminal device according to the first information. In other words, before the terminal device receives the first information, the network device configures the CDRX cycle for the terminal device. After receiving the first information, the terminal device adjusts the configured CDRX cycle according to the first information in order to obtain the first CDRX cycle.

[0152] Optionally, a CDRX cycle configured before the terminal device receives the first information may be a CDRX cycle semi-statically configured in the terminal device by the network device via an RRC message.

[0153] Optionally, in Embodiment 2 of this application, the first information may be carried in media access control layer (MAC Layer) control element (CE) messages. In other words, a network device can dynamically adjust the CDRX cycle of a terminal device through MACCE messages.

[0154] It should be noted that the MAC CE in this embodiment of the present application may be a newly defined MAC CE, and a newly defined MAC CE may be understood as a MAC CE having a newly defined logical channel identify (LCID). Alternatively, the MAC CE in this embodiment of the present application may be a MAC CE that reuses an existing LCID and defines new control rules for the data body. This is described uniformly in this specification and will not be repeated below.

[0155] Optionally, in Embodiment 2 of this application, the first information may be carried in the last data packet included in the downlink frame of the first service. After receiving the first information during the operating duration, the terminal device determines, according to the first information, when to enter the next operating duration.

[0156] Optionally, in Embodiment 2 of this application, if the first information is carried in the last data packet included in the downlink frame of the first service, the first information may further indicate that the terminal device enters a non-operational duration after receiving the downlink frame. In other words, the terminal device enters a non-operational duration after receiving the first information.

[0157] In Embodiment 2 of this application, the first information may include a period adjustment value configured by a network device. The terminal device then adjusts the configured CDRX period according to the received period adjustment value. Furthermore, the terminal device may determine a cycle offset value according to the cycle adjustment value included in the first information. Then, it may adjust the configured CDRX cycle according to the cycle offset value.

[0158] For example, the following describes how the first information is carried in a MAC CE message in Embodiment 2 of this application.

[0159] For example, as shown in Figure 7, a MACCE with a data body length of 8 bits is defined. The LCID of the MAC CE indicates that the MAC CE is used to adjust the configured CDRX cycle. The value of the data body of the MAC CE is N, and the value of N represents the period adjustment value. The value of N ranges from 0 to 255. The network device sends the MAC CE to the terminal device. After receiving the MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE is used to adjust the configured CDRX cycle, and then determines the cycle offset value according to the value of N and a pre-set rule. For example, if the value of N is 200, the terminal device determines that the cycle offset value is 73, according to cycle offset value = (N - 127). Positive and negative values ​​of the cycle offset value can also indicate the offset direction of the CDRX cycle. For example, a positive cycle offset value means that the CDRX cycle is offset backward in the time domain, and a negative cycle offset value means that the CDRX cycle is offset forward in the time domain. In Embodiment 2 of this application, the unit of the cycle offset value may be slot, symbol, or ms.

[0160] The following describes how a terminal device adjusts its configured CDRX cycles according to the first information in order to obtain the first CDRX cycle. In possible implementations, the value of the CDRX cycle configured for the terminal device remains unchanged before receiving the first information, and each time the terminal device receives the first information, an adjustment is made based on the configured CDRX cycle to determine the first CDRX cycle. This method may be called a non-memory method. For example, the CDRX cycle configured for the terminal device before receiving the first information is 8ms. After receiving the first information for the first time, the terminal device adjusts its configured CDRX cycles to 8ms in order to obtain the first CDRX cycle. After receiving the first information for the second time, the terminal device still adjusts its configured CDRX cycles to 8ms in order to obtain the first CDRX cycle.

[0161] In possible implementations, the first computation rule in this implementation satisfies the following relationship:

[0162] [(SFN×10)+subframe number]modulo(drx-Cycle + cycle-adjust) =drx-StartOffset formula (5), or,

[0163] [(SFN×10)+subframe number]modulo(drx-cycle + cycle-adjust) =(drx-StartOffset)modulo(drx-cycle + cycle-adjust) Equation (6)

[0164] SFN represents the system frame number when the terminal device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number when the terminal device enters its operational duration, drx-cycle represents the CDRX cycle configured for the terminal device by the network device, cycle-adjust represents the cycle offset value determined by the terminal device according to the first information, (drx-cycle + cycle-adjust) represents the first CDRX cycle corresponding to the terminal device (in other words, the first CDRX cycle obtained by adjusting the configured CDRX cycle), and drx-StartOffset represents the subframe offset before the terminal device entered its operational duration.

[0165] For the values ​​of drx-StartOffset, SFN, and subframe number in the aforementioned parameters, please refer to the descriptions of the corresponding parameters in equation (1) or equation (2) above. Further details will not be explained here.

[0166] In Embodiment 2 of this application, when the first CDRX cycle is a long cycle, the first calculation rule satisfies equation (5), and when the first CDRX cycle is a short cycle, the first calculation rule satisfies equation (6). For how the terminal device determines when it enters the operational duration according to the first calculation rule and the first CDRX cycle, see the above explanation of equation (1) or equation (2). Further details are not provided here.

[0167] In another possible implementation, the CDRX cycle configured for a terminal device is updated using each received first piece of information. In this implementation, after receiving the first piece of information, the terminal device adjusts the previously configured CDRX cycle for the terminal device to obtain the first CDRX cycle, and then configures the first CDRX cycle in the terminal device as the updated, configured CDRX cycle. This method may be called a memory method. For example, the CDRX cycle configured for a terminal device before receiving the first piece of information is 8ms. After receiving the first piece of information for the first time, the terminal device adjusts the configured CDRX cycle of 8ms to obtain the first CDRX cycle of 8.33ms, and then configures the first CDRX cycle in the terminal device. After receiving the first piece of information for the second time, the terminal device adjusts the configured CDRX cycle of 8.33ms to obtain the first CDRX cycle.

[0168] In possible implementations, the first computation rule in this implementation satisfies the following relationship:

[0169] [(SFN×10)+subframe number]modulo(drx-cycleN) =drx-StartOffset formula (7), or,

[0170] [(SFN×10)+subframe number]modulo(drx-cycleN) =(drx-StartOffset)modulo(drx-cycleN) Formula (8)

[0171] SFN represents the system frame number when the terminal device enters its operational duration, the subframe number represents the subframe number within the system frame corresponding to the system frame number when the terminal device enters its operational duration, drx-cycleN represents the first CDRX cycle corresponding to the terminal device (in other words, the first CDRX cycle obtained by adjusting the configured CDRX cycle), and drx-StartOffset represents the subframe offset before the terminal device entered its operational duration.

[0172] In the parameters mentioned above, drx-cycleN satisfies the following relationship: drx-cycleN=drx-Cycle(N-1) + cycle-adjust Equation (9), where:

[0173] drx-cycle(N-1) represents the CDRX cycle configured before the terminal device enters its operating period, and when drx-cycle(N-1) = drx-cycle0, drx-cycle0 represents the CDRX cycle configured for the terminal device by the network device (in other words, the CDRX cycle configured for the terminal device by the network device before the terminal device first receives the first information), and cycle-adjust represents the cycle offset value determined by the terminal device according to the first information.

[0174] For the values ​​of drx-StartOffset, SFN, and subframe number in the aforementioned parameters, please refer to the descriptions of the corresponding parameters in equation (1) or equation (2) above. Further details will not be explained here.

[0175] In Embodiment 2 of this application, when the first CDRX cycle is a long cycle, the first calculation rule satisfies equation (7), and when the first CDRX cycle is a short cycle, the first calculation rule satisfies equation (8). For how the terminal device determines when it enters the operational duration according to the first calculation rule and the first CDRX cycle, see the above explanation of equation (1) or equation (2). Further details are not provided here.

[0176] In steps S601 and S602 described above, the operation of the terminal device may be performed by the processor 501 in the terminal device 50 shown in Figure 4 by calling application program code stored in memory 502 to instruct the terminal device to execute. In steps S601 and S602 described above, the operation of the network device may be performed by the processor 401 in the network device 40 shown in Figure 4 by calling application program code stored in memory 402 to instruct the network device to execute. This is not limited to this embodiment.

[0177] Another terminal energy saving method provided in an embodiment of this application is described below. As shown in Figure 8, the terminal energy saving method provided in this embodiment of this application includes the following steps S801 and S802.

[0178] S801: The network device transmits second information to the terminal device. In response, the terminal device receives second information from the network device. Here, the second information is used by the terminal device to determine one or more CDRX cycles in a plurality of CDRX cycles configured by the network device for the terminal device, and one or more CDRX cycles are used to control when the terminal device enters its operational duration so that it coincides with the time when the network device transmits a downlink frame for the first service according to the service cycle.

[0179] S802: The terminal device determines when it enters its operational duration according to one or more CDRX cycles.

[0180] From step S801 described above, it can be seen that the second information is used to determine one or more CDRX cycles from a plurality of CDRX cycles configured by the network device for the terminal device. Thus, before the terminal device receives the second information, the network device has configured a plurality of CDRX cycles for the terminal device. The plurality of configured CDRX cycles may be called a configured CDRX cycle pool. Optionally, before the terminal device receives the second information, the terminal device may further receive third information from the network device. Here, the third information is used by the network device to configure a plurality of CDRX cycles for the terminal device, and the plurality of configured CDRX cycles include one or more CDRX cycles determined by the terminal device according to the second information.

[0181] Specifically, the third information transmitted by the network device includes identification information corresponding to each CDRX cycle within a plurality of configured CDRX cycles, and configuration information for the CDRX cycle corresponding to the identification information. The terminal device can determine the configuration information for each CDRX cycle within a plurality of CDRX cycles that need to be configured according to the CDRX cycle's identification information and corresponding configuration information, and then configure each CDRX cycle in the terminal device.

[0182] Optionally, in this embodiment of the present application, the third information may be carried in an RRC message. In other words, the network device semi-statically configures a CDRX cycle pool containing a plurality of CDRX cycles in the terminal device via an RRC message.

[0183] The following is an example of third information provided in this embodiment of the present application.

number

[0184] The CDRX-Id represents the identification information of a CDRX cycle, and the "cdrx specific configuration" represents the configuration information of the CDRX cycle corresponding to the CDRX-Id, for example, the value of the CDRX cycle.

[0185] Optionally, the network device may also carry information within the message carrying the third information indicating the type of downlink control information (DCI) received by the terminal device during the operational duration. After receiving the information, the terminal device receives only the type of DCI indicated by the information during the operational duration and does not receive any other types of DCI. For example, the information may be "dci-monitor ENUMERATED{downlink,uplink,both} / / ". Based on this solution, the terminal device can blindly detect only the type of DCI it corresponds to during the operational duration, thereby reducing the amount of blind DCI detection and the power consumption of the terminal device.

[0186] After the network device has configured multiple CDRX cycles for the terminal device, steps S801 and S802 are described below in two specific embodiments.

[0187] Embodiment 3: In this solution, after receiving second information from a network device, the terminal device can determine a plurality of periodic CDRX cycles according to the second information, and each CDRX cycle within the plurality of periodic CDRX cycles corresponds to the point in time when the terminal device enters its operational duration, which coincides with the point in time when the network device transmits the downlink frame for the first service, according to the service cycle.

[0188] Specifically, in Embodiment 3 of this application, the second information includes identification information corresponding to each CDRX cycle in a plurality of periodic CDRX cycles, and a sequence of identification information. The sequence of identification information corresponds to the periodic sequence of the plurality of periodic CDRX cycles. The terminal device can use the CDRX cycle corresponding to the identification information contained in the second information as a CDRX cycle among the plurality of periodic CDRX cycles in the previously configured plurality of CDRX cycles, and can determine the periodic sequence of the corresponding plurality of periodic CDRX cycles according to the sequence of identification information.

[0189] Optionally, in Embodiment 3 of this application, the second information may be conveyed in an RRC message, or the second information may be conveyed in a MAC CE message.

[0190] Optionally, in Embodiment 3 of this application, the second information may be carried in the last data packet included in the downlink frame of the first service. After receiving the second information during the operating duration, the terminal device determines, according to the second information, when to enter the next operating duration.

[0191] Optionally, in Embodiment 3 of this application, if the second information is carried in the last data packet included in the downlink frame of the first service, the second information may further indicate that the terminal device enters a non-operational period after receiving the downlink frame. In other words, the terminal device enters a non-operational period after receiving the second information.

[0192] For example, the following is second information conveyed in the RRC message provided in Embodiment 3 of this application.

[0193] CDRX-PATTERN::=SEQUENCE{SIZE(1...maxNrofCdrxs)OF CDRX-Id}.

[0194] The CDRX-Id represents the identification information of a CDRX cycle. After receiving an RRC message, the terminal device determines the corresponding CDRX cycle in the configured CDRX cycle pool based on the CDRX-Id in the message, and then determines the cyclic sequence of the corresponding CDRX cycle based on the sequence of CDRX-Ids. For example, the CDRX-Ids in the RRC message are 1 and 2. After the terminal device receives the RRC message, in the configured CDRX cycle pool, the CDRX cycle with identifier 1 and the CDRX cycle with identifier 2 are determined as multiple cyclic CDRX cycles according to the sequence {1,2}.

[0195] For example, the following describes how the second information is transported within the MAC CE message in Embodiment 3 of this application.

[0196] As shown in Figure 9, a MAC CE with an 8-bit data body length is defined. The LCID of the MAC CE indicates that the MAC CE is used to determine multiple periodic CDRX cycles. Each 2-bit NxNy (N1N2, N3N4, N5N6, or N7N8) in the MAC CE represents the identification information of one CDRX cycle. NxNy=00 represents an invalid configuration, NxNy=01 represents a CDRX cycle with identifier 1, and so on. NxNy=10 represents a CDRX cycle with identifier 2, NxNy=11 represents a CDRX cycle with identifier 3. After receiving the MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE is used to determine multiple periodic CDRX cycles, and then determines the multiple periodic CDRX cycles according to the value of each NxNy and the pre-configured rules. For example, a network device issues a MAC CE with the bit value 01111000. After receiving MAC CE, the terminal device determines, within the configured CDRX cycle pool, a CDRX cycle having identifiers 1, 3, or 2 as multiple periodic CDRX cycles according to the sequence {1, 3, 2}.

[0197] In this solution, after determining multiple periodic CDRX cycles, the terminal device can determine when it enters its operational duration according to equation (1) or equation (2), which follows the corresponding CDRX cycle and the periodic sequence of the multiple periodic CDRX cycles. For the specific determination process, please refer to the explanation of equation (1) or equation (2) above. Further details are not provided here.

[0198] For ease of understanding, the following is an illustrative description of how a terminal device in Embodiment 3 of this application implements the following: each CDRX cycle within a plurality of periodic CDRX cycles corresponds to a point in time when the terminal device enters its operational duration, and the point in time when the network device transmits the downlink frame for the first service, according to the service cycle.

[0199] The service cycle for the first service is 8.33ms, the first downlink frame for the first service is transmitted at 0ms, the subframe number when the terminal device first enters the operational duration is also 0 (corresponding to 0ms), and it is assumed that the terminal device receives second information after first entering the operational duration. The second information indicates that there are multiple periodic CDRX cycles {1,1,2}, where 1 or 2 is the identifier of the CDRX cycle. According to the second information, the terminal device determines that among the multiple configured CDRX cycles, the CDRX cycle with identifier 1 is 8ms, and the CDRX cycle with identifier 2 is 9ms. Therefore, the terminal device determines the time to enter the operational duration each time according to the periodic sequence of CDRX cycles {8ms,8ms,9ms}. The transmission time of each downlink frame for the first service and the subframe number each time the terminal device enters the operational duration are shown in Table 2 below. [Table 2] Table 2

[0200] For the timing of the transmission of the first service's downlink frame, the subframe number when the terminal device enters its operational period, and the interval in Table 2, please refer to the explanation above in Table 1. Further details will not be explained here.

[0201] In Table 2, the subframe number when the terminal device enters the operational duration is determined by the terminal device according to multiple periodic CDRX cycles of {8ms, 8ms, 9ms} and equation (1) or equation (2). As can be seen from the table above, after the method provided in Embodiment 2 of this application is used, the difference between the time the terminal device enters the operational duration and the time the corresponding downlink frame of the first service is transmitted is within 1 ms each time. It will be understood that each time the terminal device enters the operational duration, the terminal device can receive the corresponding downlink frame of the first service. Thus, by using the method in Embodiment 2 of this application, the time the terminal device enters the operational duration coincides with the time the downlink frame of the first service is transmitted each time. The terminal device can satisfy the delay requirements of the first service without wasting power consumption.

[0202] Embodiment 4: In this solution, after receiving second information from a network device, the terminal device can determine a first CDRX cycle according to the second information, and the first CDRX cycle is used to control when the terminal device enters its operational duration so as to coincide with the time when the network device transmits a downlink frame for the first service according to the service cycle.

[0203] Specifically, in Embodiment 4 of this application, the second information includes identification information corresponding to the first CDRX cycle. The terminal device can use the CDRX cycle corresponding to the identification information as the first CDRX cycle in a CDRX cycle pool configured according to the identification information contained in the second information.

[0204] Optionally, in Embodiment 4 of this application, the second information may be conveyed in an RRC message, or the second information may be conveyed in a MAC CE message.

[0205] Optionally, in Embodiment 4 of this application, the second information may be carried in the last data packet included in the downlink frame of the first service. After receiving the second information during the operating duration, the terminal device determines, according to the second information, when to enter the next operating duration.

[0206] Optionally, in Embodiment 4 of this application, if the second information is carried in the last data packet included in the downlink frame of the first service, the second information may further indicate that the terminal device enters a non-operational duration after receiving the downlink frame. In other words, the terminal device enters a non-operational duration after receiving the second information.

[0207] For example, the following is second information conveyed in the RRC message provided in Embodiment 4 of this application.

[0208] CDRX-PATTERN::=SEQUENCE{SIZE(1...maxNrofCdrxs)OF CDRX-Id}.

[0209] The CDRX-Id represents the identification information of a CDRX cycle. After receiving an RRC message, the terminal device determines the corresponding CDRX cycle in the configured CDRX cycle pool as the first CDRX cycle based on the CDRX-Id in the message. For example, if the CDRX-Id in the RRC message is 1, then in the configured CDRX cycle pool, the CDRX cycle with identifier 1 is determined to be the first CDRX cycle.

[0210] For example, the following describes how the second information is conveyed in the MAC CE message in Embodiment 4 of this application.

[0211] As shown in Figure 9, a MAC CE with a data body length of 8 bits is defined. The LCID of the MAC CE indicates that the MAC CE is used to determine the first CDRX cycle. Each bit of the MAC CE represents identification information for the CDRX cycle. For example, the first bit N1 represents the CDRX cycle with identifier 1, the second bit N2 represents the CDRX cycle with identifier 2, and so on. The eighth bit N8 represents the CDRX cycle with identifier 8. The value of a bit in the MAC CE can indicate whether the CDRX cycle represented by the bit is the first CDRX cycle or not. For example, a bit value of 0 indicates that the CDRX cycle represented by that bit is not the first CDRX cycle. A bit value of 1 indicates that the CDRX cycle represented by that bit is the first CDRX cycle. After receiving a MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE will be used to determine the first CDRX cycle, and then determines the first CDRX cycle in the configured CDRX cycle pool according to the value of each bit in the MAC CE and the pre-configured rules. For example, a network device issues a MAC CE with a bit value of 01000000. After receiving the MAC CE, the terminal device determines that the CDRX with identifier 2 is the first CDRX cycle in the configured CDRX cycle pool.

[0212] In this solution, after determining the first CDRX cycle, the terminal device can determine the time at which it enters its operational duration according to the first CDRX cycle and equation (1) or equation (2). For the specific determination process, please refer to the explanation of equation (1) or equation (2) above. Further details are not provided here.

[0213] For ease of understanding, the following is an illustrative description of how a terminal device in Embodiment 4 of this application implements the fact that the time when the terminal device enters its operational duration is determined according to the first CDRX cycle and coincides with the time when the network device transmits the downlink frame for the first service, according to the service cycle.

[0214] The service cycle for the first service is 8.33ms, the first downlink frame for the first service is transmitted at 0ms, and the subframe number when the terminal device first enters the operational duration is also assumed to be 0 (corresponding to 0ms). The terminal device first receives the second information after entering the operational duration for the first time. The second information contains identifier 1. According to the second information, the terminal device determines that the CDRX cycle with identifier 1 in the configured CDRX cycle pool is 8ms, and determines when to enter the operational duration for the second time, according to the first CDRX cycle being 8ms. The terminal device receives the second information for the second time after entering the operational duration for the second time. The second information contains identifier 1. According to the second information, the terminal device determines that the CDRX cycle with identifier 1 in the configured CDRX cycle pool is 8ms, and determines when to enter the operational duration for the third time, according to the first CDRX cycle being 8ms. The terminal device receives the second information for the third time after entering the operational duration for the third time. The second piece of information includes identifier 2. According to the second piece of information, the terminal device determines that the CDRX cycle with identifier 2 in the configured CDRX cycle pool is 9ms, and, according to the first CDRX cycle being 9ms, determines when to enter the operational duration for the fourth time. By analogy, the network device can continuously transmit the second piece of information to the terminal device to adjust when the terminal device enters the operational duration. For example, the transmission time of each downlink frame of the first service, and the subframe number each time the terminal device enters the operational duration, may be as shown in Table 2 above. As can be understood, based on this solution, the network device can continuously adjust the terminal device's CDRX cycle by transmitting the second piece of information, so that when the terminal device enters the operational duration, it coincides with the time when the network device transmits the downlink frame of the first service according to the service cycle, thereby avoiding wasted power consumption of the terminal device and satisfying the delay requirements of the first service.

[0215] In steps S801 and S802 described above, the operation of the terminal device may be performed by the processor 501 in the terminal device 50 shown in Figure 4 by calling application program code stored in memory 502 to instruct the terminal device to execute. In steps S801 and S802 described above, the operation of the network device may be performed by the processor 401 in the network device 40 shown in Figure 4 by calling application program code stored in memory 402 to instruct the network device to execute. This is not limited to this embodiment.

[0216] Another terminal energy saving method provided in embodiments of this application is described below. As shown in Figure 10, the terminal energy saving method provided in this embodiment of this application includes the following steps S1001 and S1002.

[0217] S1001: The network device transmits the fourth piece of information to the terminal device. In response, the terminal device receives the fourth piece of information from the network device. Here, the fourth piece of information indicates the point in time when the terminal device will next enter an operational duration after receiving the first downlink frame of the first service, the point in time when the terminal device will next enter an operational duration coincides with the point in time when the network device transmits the second downlink frame of the first service, and the second downlink frame is the first downlink frame transmitted by the network device according to the service cycle following the first downlink frame.

[0218] S1002: The terminal device determines, according to the fourth piece of information, when it will enter the next operating duration period after receiving the first downlink frame.

[0219] In this embodiment of the present application, the terminal device receives a first downlink frame during the operating duration, and determines the time indicated by the fourth information as the time when the terminal device enters the next operating duration after receiving the first downlink frame.

[0220] Based on the method provided in this embodiment of the present application, the network device can indicate, through a fourth piece of information transmitted each time, when a terminal device enters an operational duration, and can control the timing of when the terminal device enters an operational duration each time so as to coincide with when the network device transmits a downlink frame for the first service, according to the service cycle of the first service.

[0221] Optionally, in this embodiment of the present application, the fourth information may be carried in the last data packet included in the first downlink frame.

[0222] Optionally, in this embodiment of the present application, the fourth information may further indicate that the terminal device enters a deactivation period after receiving the first downlink frame. In other words, according to the fourth information, the terminal device enters a non-operational duration after receiving the first downlink frame, and then enters an operational duration again at the time indicated by the fourth information. Furthermore, if the fourth information is carried in the last data packet included in the first downlink frame and further indicates that the terminal device enters a deactivation period after receiving the first downlink frame, the terminal device enters a non-operational duration immediately after receiving the fourth information, and then enters an operational duration again at the time indicated by the fourth information.

[0223] Optionally, in this embodiment of the present application, the fourth information may be carried in a MAC CE message. In other words, the network device can dynamically adjust the timing at which a terminal device enters its operational duration each time through the MAC CE information.

[0224] For example, the following describes how the fourth information is carried in the MAC CE message in this embodiment of the present application.

[0225] As shown in Figure 7, a MAC CE with a data body length of 8 bits is defined. The LCID of the MAC CE indicates the point in time when the terminal device enters its operational duration. The value of the data body of the MAC CE is N. The value of N represents the point in time when the terminal device enters its operational duration. The value of N ranges from 0 to 255. After receiving the MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE is used to indicate the point in time when the terminal device enters its operational duration, and then determines the point in time when the terminal device enters its operational duration according to the value of N and a pre-configured rule. The unit of the point in time when the terminal device enters its operational duration, represented by the value of N, may be a slot, milliseconds, or a symbol. For example, a network device carries the MAC CE in the last data packet included in the downlink frame of the first service and then sends the MAC CE to the terminal device. After receiving the MAC CE, the terminal device enters its non-operational duration and determines that the value of N in the MAC CE is 10. The terminal device will enter its operational period again after 10 slots.

[0226] In steps S1001 and S1002 described above, the operation of the terminal device may be performed by the processor 501 in the terminal device 50 shown in Figure 4 by calling application program code stored in memory 502 to instruct the terminal device to execute. In steps S1001 and S1002 described above, the operation of the network device may be performed by the processor 401 in the network device 40 shown in Figure 4 by calling application program code stored in memory 402 to instruct the network device to execute. This is not limited to this embodiment.

[0227] Another terminal energy saving method provided in embodiments of this application is provided below. As shown in Figure 11, the terminal energy saving method provided in this embodiment of this application includes the following steps S1101 and S1102.

[0228] S1101: The network device transmits fifth information to the terminal device. In response, the terminal device receives fifth information from the network device. Here, the fifth information is used by the terminal device to determine one of several CDRX cycles configured by the network device for the terminal device. The fifth information is then further used by the terminal device to adjust the determined CDRX cycle in order to obtain the first CDRX cycle.

[0229] S1102: The terminal device determines when it enters its operational duration according to the first CDRX cycle and the first calculation rule. Here, the first CDRX cycle and the first calculation rule are used to control when the terminal device enters its operational duration so that it coincides with when the network device transmits a downlink frame for the first service according to the service cycle.

[0230] For specific implementations in this embodiment of the present application in which a network device constitutes multiple CDRX cycles for a terminal device, see the preceding description in Information 3. Further details are not described here.

[0231] Specifically, in this embodiment of the present application, the fifth information includes identification information for one CDRX cycle. According to the identification information included in the fifth information, the terminal device can determine which CDRX cycle corresponds to the identification information among a plurality of previously configured CDRX cycles.

[0232] In this embodiment of the present application, the fifth information further includes a cycle adjustment value configured by a network device, and the terminal device adjusts the aforementioned determined CDRX cycle according to the received cycle adjustment value. Furthermore, the terminal device may determine a period offset value according to the period adjustment value included in the first information, and then adjust the aforementioned determined CDRX cycle according to the period offset value.

[0233] Optionally, in this embodiment of the present application, the fifth information may be carried in the last data packet included in the downlink frame of the first service. After receiving the fifth information during the operational duration, the terminal device determines, according to the fifth information, when it will next enter the operational duration.

[0234] Optionally, in this embodiment of the present application, if the fifth information is carried in the last data packet included in the downlink frame of the first service, the fifth information may further indicate that the terminal device enters a non-operational duration after receiving the downlink frame. In other words, the terminal device enters a non-operational duration after receiving the fifth information.

[0235] Optionally, in this embodiment of the present application, the fifth piece of information may be carried in a MAC CE message.

[0236] For example, the following describes how the fifth information is carried within a MAC CE message in this embodiment of the present application.

[0237] As shown in Figure 9, a MAC CE with a data body length of 8 bits is defined. The LCID of the MAC CE indicates that the MAC CE is used to determine one CDRX cycle and to adjust the determined CDRX cycle. The first two bits of the MAC CE, N1N2, represent the identification information of the CDRX cycle. For example, an N1N2 value of 00 indicates that the identifier of the CDRX cycle is 1, an N1N2 value of 01 indicates that the identifier of the CDRX cycle is 2, and so on. An N1N2 value of 11 indicates that the identifier of the CDRX cycle is 4. The last six bits of the MAC CE, N3 through N8, have the value of N, which ranges from 0 to 63. The value of N represents the period adjustment value.

[0238] After receiving the MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE will be used to determine and adjust the CDRX cycle, and then determines the CDRX cycle and cycle offset value from the configured CDRX cycle pool according to the values ​​of N1N2, the value of N, and a pre-configured rule. For example, a network device sends a MAC CE to the terminal device. After receiving the MAC CE, the terminal device determines that the value of N1N2 in the MAC CE is 00, and determines the CDRX cycle with identifier 1 in the configured CDRX cycle pool. The terminal device further determines that the value of N in the MAC CE is 61, and then determines that the cycle offset value is 30 according to cycle offset value = (N-31). The terminal device then adjusts the CDRX cycle with identifier 1 according to the cycle offset value. Positive and negative values ​​of the cycle offset value can also indicate the offset direction of the CDRX cycle. For example, a positive cycle offset value means that the CDRX cycle is offset backward in the time domain, and a negative cycle offset value means that the CDRX cycle is offset forward in the time domain. In this embodiment of the present application, the unit of the cycle offset value may be slots, symbols, or milliseconds.

[0239] In this embodiment of the present application, for how the terminal device adjusts the determined CDRX cycle according to the fifth information in order to obtain the first CDRX cycle, refer to the above description of the non-memory method in Embodiment 2 of the present application. Further details are not described here.

[0240] With respect to step S1102, in this embodiment of the present application, the first calculation rule satisfies the following relationship:

[0241] [(SFN×10)+subframe number]modulo(drx-Cycle + cycle-adjust) =drx-StartOffset formula (10), or,

[0242] [(SFN×10)+subframe number]modulo(drx-cycle + cycle-adjust) =(drx-StartOffset)modulo(drx-cycle + cycle-adjust) Equation (11)

[0243] SFN represents the system frame number when the terminal device enters its operational duration, the subframe number represents the subframe number within the system frame corresponding to the system frame number when the terminal device enters its operational duration, drx-cycle represents the CDRX cycle determined by the terminal device according to the fifth information from among multiple configured CDRX cycles, cycle-adjust represents the cycle offset value determined by the terminal device according to the fifth information, (drx-cycle + cycle-adjust) represents the first CDRX cycle (in other words, the first CDRX cycle obtained by adjusting the determined CDRX cycle), and drx-StartOffset represents the subframe offset before the terminal device enters its operational duration.

[0244] For the values ​​of drx-StartOffset, SFN, and subframe number in the aforementioned parameters, please refer to the descriptions of the corresponding parameters in equation (1) or equation (2) above. Further details will not be explained here.

[0245] For details of how the terminal device determines when it enters the operational duration according to the first CDRX cycle and formula (10) or formula (11) in this embodiment of the present application, see the preceding description of Embodiment 2 of the present application. Further details are not described here.

[0246] Based on this solution, the network device can transmit fifth information to enable the terminal device to select a CDRX cycle from multiple CDRX cycles configured for coordination. The time determined by the terminal device according to the coordinated CDRX cycle, and at which the terminal device enters its operational duration, coincides with the time when the network device transmits the downlink frame for the first service according to the service cycle, thereby avoiding wasted power consumption by the terminal device and satisfying the delay requirements for the first service.

[0247] In steps S1101 and S1102 described above, the operation of the terminal device may be performed by the processor 501 in the terminal device 50 shown in Figure 4 by calling application program code stored in memory 502 to instruct the terminal device to execute. In steps S1101 and S1102 described above, the operation of the network device may be performed by the processor 401 in the network device 40 shown in Figure 4 by calling application program code stored in memory 402 to instruct the network device to execute. This is not limited to this embodiment.

[0248] Another terminal energy saving method provided in embodiments of this application is described below. As shown in Figure 12, the terminal energy saving method provided in this embodiment of this application includes the following steps S1201 and S1202.

[0249] S1201: The network device transmits sixth information to the terminal device. In response, the terminal device receives sixth information from the network device. Here, the sixth information is used by the terminal device to determine multiple CDRX cycles within multiple CDRX cycles configured by the network device, and the sixth information is further used to adjust each CDRX cycle within the multiple determined CDRX cycles in order to obtain multiple periodic CDRX cycles.

[0250] S1202: The terminal device determines the point at which it enters its operational duration according to a plurality of periodic CDRX cycles. Here, the point at which the terminal device enters its operational duration, corresponding to each CDRX cycle within the plurality of periodic CDRX cycles, coincides with the point at which the network device transmits the downlink frame for the first service according to the service cycle.

[0251] For specific implementations in this embodiment of the present application in which a network device constitutes multiple CDRX cycles for a terminal device, see the preceding description in Information 3. Further details are not described here.

[0252] Specifically, in this embodiment of the present application, the sixth information includes identification information for a plurality of CDRX cycles and a sequence of identification information. The terminal device may use the CDRX cycles corresponding to the identification information in a configured CDRX cycle pool, according to the CDRX cycle identification information contained in the sixth information, as CDRX cycles among the plurality of CDRX cycles that need to be adjusted.

[0253] In this embodiment of the present application, the sixth information further includes a cycle adjustment value corresponding to the identification information. After receiving the sixth information, the terminal device adjusts the corresponding CDRX cycle among a plurality of CDRX cycles determined according to the identification information according to the cycle adjustment value. Furthermore, the terminal device may determine a cycle offset value according to the cycle adjustment value included in the sixth information, and then adjust the corresponding CDRX cycle among a plurality of CDRX cycles determined according to the identification information according to the cycle offset value. After adjusting each CDRX cycle in the plurality of CDRX cycles determined according to the identification information, the terminal device obtains a plurality of periodic CDRX cycles, and then determines the periodic sequence of the corresponding plurality of periodic CDRX cycles according to the sequence of the identification information.

[0254] Optionally, in this embodiment of the present application, the sixth information may be carried in the last data packet included in the downlink frame of the first service. After receiving the sixth information during the operational duration, the terminal device determines, according to the sixth information, when it will next enter the operational duration.

[0255] Optionally, in this embodiment of the present application, if the sixth information is carried in the last data packet included in the downlink frame of the first service, the sixth information may further indicate that the terminal device enters a non-operational duration after receiving the downlink frame. In other words, the terminal device enters a non-operational duration after receiving the sixth information.

[0256] Optionally, in this embodiment of the present application, the sixth piece of information may be carried in a MAC CE message.

[0257] For example, the following describes how the sixth information is carried within a MAC CE message in this embodiment of the present application.

[0258] As shown in FIG. 13, a MAC CE with a data body length of 2 bytes (8 bits per byte) is defined. The LCID of the MAC CE indicates that the MAC CE is used to adjust a plurality of determined CDRX cycles so as to determine a plurality of CDRX cycles and obtain a plurality of periodic CDRX cycles. The 8 bits included in the previous byte of the MAC CE are N1 to N8, and the 8 bits included in the next byte are M1 to M8. From N1 to N8, the value of N1N2 represents the identification information of the CDRX cycle. For example, a value of N1N2 of 00 indicates that the identifier of the CDRX cycle is 1, a value of N1N2 of 01 indicates that the identifier of the CDRX cycle is 2, and so on. A value of N1N2 of 11 indicates that the identifier of the CDRX cycle is 4. From N3 to N8, it has a value of N, and the value of N ranges from 0 to 63. N is a cycle adjustment value corresponding to the identification information represented by N1N2. Among M1 to M8, the value of M1M2 represents the identification information of the CDRX cycle. For example, a value of M1M2 of 00 indicates that the identifier of the CDRX cycle is 1, and so on. A value of M1M2 of 11 indicates that the identifier of the CDRX cycle is 4. From M3 to M8, it has a value of M, and the value of M ranges from 0 to 63. M is a cycle adjustment value corresponding to the identification information represented by M1M2.

[0259] After receiving the MAC CE, the terminal device determines, according to the LCID of the MAC CE, that the MAC CE is used to determine multiple CDRX cycles and to coordinate multiple determined CDRX cycles to obtain multiple periodic CDRX cycles. Then, according to the values ​​of N1N2, M1M2, N and M, and a pre-configured rule, it determines multiple CDRX cycles from the configured CDRX cycle pool and the corresponding cycle offset values. For example, if N1N2 is 00, the terminal device determines a CDRX cycle with identifier 1 from the configured CDRX cycle pool, the value of N is 61, and the terminal device determines that the cycle offset value corresponding to the CDRX cycle with identifier 1 is 30, according to the cycle offset value = (N-31). If M1M2 is 01, the terminal device determines a CDRX cycle with identifier 2 from the configured CDRX cycle pool, the value of M is 41, and the terminal device determines that the cycle offset value corresponding to the CDRX cycle with identifier 2 is 10, according to the cycle offset value = (M-31). The terminal device then adjusts the CDRX cycles having identifier 1 and identifier 2, respectively, according to the corresponding cycle offset values. Positive and negative values ​​of the cycle offset values ​​can also indicate the offset direction of the CDRX cycle. For example, a positive cycle offset value means that the CDRX cycle is offset backward in the time domain, and a negative cycle offset value means that the CDRX cycle is offset forward in the time domain. In this embodiment of the present application, the unit of the cycle offset value may be slots, symbols, or ms.

[0260] After adjusting the CDRX cycles indicated by N1N2 and M1M2, the terminal device acquires a plurality of periodic CDRX cycles and determines the periodic sequence of the corresponding plurality of CDRX cycles according to the sequence of N1N2 and M1M2.

[0261] In this embodiment of the present application, for how the terminal device adjusts each CDRX cycle within the plurality of determined CDRX cycles according to the sixth information in order to obtain a plurality of periodic CDRX cycles, refer to the foregoing description of the non-memory method in Embodiment 2 of the present application. Details are not described again here.

[0262] Regarding step S1202, in this embodiment of the present application, for how the terminal device determines the time point when it enters the operation duration according to the plurality of periodic CDRX cycles, refer to the foregoing description of Embodiment 3. Details are not described again here.

[0263] Based on this solution, the network device can send the sixth information to enable the terminal device to select a plurality of CDRX cycles from the plurality of configured CDRX cycles for adjustment and determine the plurality of adjusted CDRX cycles as the plurality of periodic CDRX cycles. The time point determined by the terminal device according to the plurality of periodic CDRX cycles and when the terminal device enters the operation duration coincides with the time point when the network device sends the downlink frame of the first service according to the service cycle, thereby avoiding waste of power consumption of the terminal device and meeting the delay requirement of the first service.

[0264] In the foregoing steps S1201 and S1202, the operation of the terminal device can be executed by the processor 501 in the terminal device 50 shown in FIG. 4 by calling the application program code stored in the memory 502 to instruct the terminal device to execute. In the foregoing steps S1201 and S1202, the operation of the network device can be executed by the processor 401 in the network device 40 shown in FIG. 4 by calling the application program code stored in the memory 402 to instruct the network device to execute. This is not limited in this embodiment.

[0265] In the embodiments described above, it will be understood that methods and / or steps performed by a terminal device may also be performed by components (e.g., chips or circuits) that can be used in the terminal device, and methods and / or steps performed by a network device may also be performed by components (e.g., chips or circuits) that can be used in the network device.

[0266] The above describes the solutions provided in embodiments of this application, primarily in terms of interaction between various devices. Correspondingly, one embodiment of this application further provides a communication device, which is configured to implement the various methods described above. The communication device may be a terminal device in embodiments of the methods described above, a device including the aforementioned terminal device, or a component that can be used in a terminal device. Alternatively, the communication device may be a network device in embodiments of the methods described above, a device including the aforementioned network device, or a component that can be used in a network device. To implement the functions described above, it will be understood that the communication device includes corresponding hardware structures and / or software modules for performing the functions. Those skilled in the art will readily recognize that the units, algorithms, and steps in the examples described with reference to the embodiments disclosed herein can be implemented in the form of hardware or a combination of hardware and computer software in this application. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the functions described for each specific application, but such implementations should not be considered to exceed the scope of this application.

[0267] In embodiments of this application, the communication device may be divided into functional modules based on embodiments of the method described above. For example, the division into functional modules may be based on corresponding functions, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. It should be noted that in embodiments of this application, the module division is just one example and is merely a logical functional division. In actual implementations, other division methods may be used.

[0268] Figure 14 is a schematic diagram relating to the structure of the communication device 140. The communication device 140 includes a transceiver module 1401 and a processing module 1402. The transceiver module 1401 may also be called a transceiver unit for implementing transmission and reception functions. For example, the transceiver module may be a transceiver circuit, a transceiver machine, a transceiver, or a communication interface.

[0269] For example, the communication device 140 is a terminal device in the embodiment of the method described above.

[0270] In possible implementations, the transceiver module 1401 is configured to receive first information from a network device, which is used to determine the first CDRX cycle corresponding to the communication device. The processing module 1402 is configured to determine when the communication device enters its operational duration, according to the first CDRX cycle and a first calculation rule, which is used to control when the communication device enters its operational duration, so that it coincides with the time when the network device transmits a downlink frame for the first service according to its service cycle.

[0271] Optionally, the first CDRX cycle corresponding to a communication device is the first CDRX cycle configured by network devices for the communication device, and the first CDRX cycle is the same as the service cycle.

[0272] Optionally, the first calculation rule satisfies the following relationship:

number

number

[0273] Optionally, the first information includes the service cycle of the first service, or the value of the first CDRX cycle, or the frequency of the first CDRX cycle, or the first information includes a preset integer value, and the preset integer value is used by the communication device to determine the first CDRX cycle according to a preset relationship.

[0274] Optionally, the first piece of information is carried in a radio resource control (RRC) message.

[0275] Optionally, the first CDRX cycle corresponding to the communication device is the first CDRX cycle obtained by adjusting the CDRX cycle configured for the communication device according to the first information.

[0276] Optionally, the first calculation rule satisfies the following relationship: [(SFN × 10) + subframe number] modulo (drx-Cycle + cycle-adjust) = drx-StartOffset, or [(SFN × 10) + subframe number] modulo (drx-cycle + cycle-adjust) = (drx-StartOffset) modulo (drx-cycle + cycle-adjust) Here, SFN represents the frame number when the communication device enters the operation duration, subframe number represents the subframe number within the system frame corresponding to the system frame number, drx-cycle represents the CDRX cycle configured by the network device for the communication device, cycle-adjust represents the cycle offset value determined by the communication device according to the first information, (drx-cycle + cycle-adjust) represents the first CDRX cycle corresponding to the communication device, and drx-StartOffset represents the subframe offset before the communication device enters the operation duration.

[0277] Optionally, the first calculation rule satisfies the following relationship. [(SFN × 10) + subframe number] modulo (drx-cycleN) = drx-StartOffset, or [(SFN × 10) + subframe number] modulo (drx-cycleN) = (drx-StartOffset) modulo (drx-cycleN) Here, SFN represents the frame number when the communication device enters its operational duration, subframe number represents the subframe number within the system frame corresponding to the system frame number, drx-cycleN represents the first CDRX cycle corresponding to the communication device, and drx-StartOffset represents the subframe offset before the communication device enters its operational duration. Here, drx-cycleN satisfies the following relationship: drx-cycleN=drx-cycle(N-1) + cycle-adjust Here, drx-cycle(N-1) represents the CDRX cycle configured before the communication device enters its operating period, and when drx-cycle(N-1) = drx-cycle0, drx-cycle0 represents the CDRX cycle configured for the communication device by the network device. Furthermore, cycle-adjust represents the cycle offset value determined by the communication device according to the first piece of information.

[0278] Optionally, the first information is carried in a MAC CE message, which is a control element for media access control.

[0279] In another possible implementation, the transceiver module 1401 is configured to receive second information from a network device. Here, the second information is used to determine one or more CDRX cycles out of a plurality of CDRX cycles configured by the network device for the communication device, and the one or more CDRX cycles are used to control when the communication device enters its operational duration, so that it coincides with when the network device transmits a downlink frame for the first service according to its service cycle. The processing module 1402 is configured to determine when the communication device enters its operational duration according to one or more CDRX cycles.

[0280] Optionally, one or more CDRX cycles are multiple periodic CDRX cycles, and the multiple periodic CDRX cycles are used to control when the communication device corresponding to each CDRX cycle within the multiple periodic CDRX cycles enters its operational duration, so as to coincide with the time when a network device transmits a downlink frame for the first service according to the service cycle.

[0281] Optionally, the second information includes identification information and a sequence of identification information corresponding to each CDRX cycle within a plurality of periodic CDRX cycles, and the sequence of identification information corresponds to the periodic sequence of the plurality of periodic CDRX cycles.

[0282] Optionally, the second information is carried in a wireless resource control RRC message, or in a media access control MAC CE message.

[0283] Optionally, one or more CDRX cycles are first CDRX cycles, and these first CDRX cycles are used to control when the communication device enters its operational duration, so that it coincides with when the network device transmits a first service downlink frame according to the service cycle.

[0284] Optionally, the second piece of information includes identification information corresponding to the first CDRX cycle.

[0285] Optionally, the second information is carried in an RRC message, or in a MAC CE message.

[0286] Optionally, the transceiver module 1401 is also configured to receive third information from a network device, where the third information is used by the network device to configure multiple CDRX cycles for the communication device, and each multiple CDRX cycle comprises one or more CDRX cycles.

[0287] Optionally, the third piece of information may include identification information corresponding to each CDRX cycle within a plurality of CDRX cycles, and configuration information for the CDRX cycles corresponding to the identification information.

[0288] Optionally, the third piece of information is transmitted via an RRC message.

[0289] In yet another possible implementation, the transceiver module 1401 is configured to receive a fourth piece of information from the network device, where the fourth piece of information indicates the point in time when the communication device will next enter an operational duration after receiving the first downlink frame of the first service. The point in time when the communication device will next enter an operational duration coincides with the point in time when the network device transmits the second downlink frame of the first service, and the second downlink frame is the first downlink frame transmitted by the network device after the first downlink frame, according to the service cycle. The processing module 1402 is configured to determine, according to the fourth piece of information, the point in time when the communication device will next enter an operational duration after receiving the first downlink frame.

[0290] Optionally, the fourth piece of information is carried in the last data packet included in the first downlink frame.

[0291] Optionally, the fourth piece of information further indicates that the communication device enters a non-operational duration after receiving the first downlink frame.

[0292] Optionally, the fourth piece of information is carried via a MAC CE message, which is a control element for media access control.

[0293] All relevant details of the steps in the embodiments of this method may be referenced in the functional description of the corresponding functional module. Further details are not described here.

[0294] In this embodiment, the communication device 140 has a functional module realized through integration. Here, “module” may be a specific ASIC, circuit, processor and memory, integrated logic circuit, and / or another component capable of providing the aforementioned functions, which runs one or more software or firmware programs.

[0295] In a simple embodiment, those skilled in the art will understand that the communication device 140 may be in the form of the terminal device 50 shown in Figure 4.

[0296] For example, the processor 501 in the terminal device 50 shown in Figure 4 can invoke computer-executable instructions stored in memory 502, and as a result, the terminal device 50 performs the terminal energy saving method in the embodiment of the method described above. Specifically, the functions / implementation processes of the transceiver module 1401 and processing module 1402 in Figure 14 can be implemented by the processor 501 in the terminal device 50 shown in Figure 4 by invoking computer-executable instructions stored in memory 502. Alternatively, the functions / implementation processes of the processing module 1402 in Figure 14 may be implemented by the processor 501 in the terminal device 50 shown in Figure 4 by invoking computer-executable instructions stored in memory 502, and the functions / implementation processes of the transceiver module 1401 in Figure 14 may be implemented by the transceiver 503 in the terminal device 50 shown in Figure 4. The communication device 140 provided in this embodiment can perform the terminal energy saving method described above. Therefore, for the technical effects that can be achieved by the communication device, refer to the embodiment of the method described above. Details will not be described again here.

[0297] Figure 15 is a schematic diagram relating to the structure of another communication device 150. As shown in Figure 15, the communication device 150 includes a processor 1501, a memory 1502, and a transceiver 1503. The memory 1503 is configured to store computer executable instructions, the processor 1501 is configured to execute the instructions stored in the memory 1503, and the transceiver 1503 is configured to communicate with other devices in the communication network. The communication device 150 may be a terminal device in the embodiment of the method described above.

[0298] In a simple embodiment, those skilled in the art will understand that the communication device 140 may use the form of the communication device 150 shown in Figure 15. For example, the function / implementation process of the processing module 1402 in Figure 14 may be implemented by the processor 1501 in the communication device 150 shown in Figure 15 by calling computer executable instructions stored in memory 1502, and the function / implementation process of the transceiver module 1401 in Figure 14 may be implemented by the transceiver 1503 in the communication device 150 shown in Figure 15. The communication device 150 provided in this embodiment can perform the terminal energy saving method described above. Accordingly, for the technical effects that can be achieved by the communication device, refer to the embodiments of the method described above. Details are again not described here.

[0299] It should be noted that one or more of the aforementioned modules or units may be implemented using software, hardware, or a combination thereof. When any one of the aforementioned modules or units is implemented using software, the software exists in the form of computer program instructions and is stored in memory. The processor may be configured to execute program instructions to carry out the aforementioned method procedures. The processor may be integrated into a System-on-a-chip (SoC) or ASIC, or it may be a separate semiconductor chip. The processor includes a core for executing software instructions to perform operations or processing, and may further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a programmable logic device (PLD), or logic circuits that implement dedicated logic operations.

[0300] When the aforementioned module or unit is implemented using hardware, the hardware may be one or any combination of digital signals, microprocessors, digital signal processing unit (DSP) chips, microcontroller units (MCUs), artificial intelligence processors, ASICs, SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices, and the hardware may or may not be software-dependent in order to perform the aforementioned method procedure.

[0301] Optionally, one embodiment of the present application further provides a chip system comprising at least one processor and an interface, wherein the at least one processor is coupled to memory via an interface and is enabled to execute a method according to any one of the above-described method embodiments when the at least one processor executes a computer program or instruction in memory. In possible implementations, the communication device further includes memory. Optionally, the chip system may include a chip, or a chip and another discrete device. This is not particularly limited in this embodiment of the present application.

[0302] All or part of the embodiments described above may be implemented by software, hardware, firmware, or any combination thereof. When a software program is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded into a computer and executed, all or part of a process or function according to one embodiment of this application is generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted by wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) means from one website, computer, server, or data center to another website, computer, server, or data center. Computer-readable storage media may be any available medium accessible by a computer, or a data storage device such as a server or data center that integrates one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), semiconductor media (e.g., solid-state drives (SSDs)), etc.

[0303] While this application is described with reference to embodiments, a person skilled in the art can understand and implement other variations of the disclosed embodiments by looking at the accompanying drawings, the disclosed content and the accompanying claims in the process of implementing this application for which protection is claimed. In the claims, “comprising” does not exclude other components or other steps, and “a” or “one” does not exclude multiple cases. A single processor or another unit may implement some of the functions enumerated in the claims. Although some means are described in different dependent claims, this does not mean that these means cannot be combined to obtain a greater effect.

[0304] This application is described with reference to its specific features and all embodiments, but it is evident that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and the accompanying drawings are merely illustrative descriptions of this application as defined by the accompanying claims and are to be considered any or all of the modifications, variations, combinations, or equivalents that cover the scope of this application. It is evident to those skilled in the art that various modifications and variations can be made to this application without departing from the spirit and scope of this application. This application is intended to cover these modifications and variations of this application, provided that they fall within the scope of protection defined by the subsequent claims and their equivalent art.

Claims

1. A terminal energy saving method, wherein the method is This is a step of receiving first information from a network device. The first information is used to determine the first CDRX cycle corresponding to the terminal device. The first CDRX cycle is a decimal value, the same as the service cycle of the first service. Steps and The step is for the terminal device to determine a first subframe number of an integer value that enters the operating duration, in accordance with the first CDRX cycle and the first calculation rule. The aforementioned first subframe number is located within the system frame, The first calculation rule is used to control the first subframe number that the terminal device enters the operating duration period so that it coincides with the time when the network device transmits the downlink frame of the first service according to the service cycle, Methods that include...

2. The first CDRX cycle corresponding to the terminal device is a first CDRX cycle configured by network devices for the terminal device. The method according to claim 1.

3. The first calculation rule is: [Math 1] or [Math 2] The relationship is satisfied, and here, SFN represents the system frame number when the terminal device enters its operating period. The subframe number represents the subframe number in the system frame corresponding to the aforementioned system frame number. drx-cycle represents the first CDRX cycle, drx-StartOffset represents the subframe offset before the terminal device enters the operating duration period. The method according to claim 2.

4. The first information includes the service cycle of the first service, or The first information includes the value of the first CDRX cycle, or The first information includes the frequency of the first CDRX cycle, or The first information includes a pre-set integer value, and the pre-set integer value is used by the terminal device to determine the first CDRX cycle according to a pre-set relationship. The method according to claim 2 or 3.

5. The first information is carried in a wireless resource control RRC message. The method according to claim 2.

6. A communication device including a processor, memory, and transceiver, The memory is configured to store computer instructions, The processor is configured to execute computer instructions stored in the memory, The transceiver is configured to communicate between the communication device and another device in the communication network. When the aforementioned communication device is activated, The processor executes the computer instructions, The transceiver communicates with another device in the communication network, The communication device implements the method described in any one of claims 1 to 3. Communication device.

7. A computer-readable storage medium that stores instructions, When the aforementioned instruction is executed on the computer, The computer is made to carry out the method according to any one of claims 1 to 3. A computer-readable storage medium.

8. Network devices and communication devices as described in claim 6, Communication system.

Images