WO2024092576A1

WO2024092576A1 - Timer starting method and apparatus

Info

Publication number: WO2024092576A1
Application number: PCT/CN2022/129357
Authority: WO
Inventors: 江小威
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-11-02
Filing date: 2022-11-02
Publication date: 2024-05-10
Also published as: WO2024092870A1

Abstract

Disclosed in embodiments of the present disclosure are a timer starting method and an apparatus, applicable to the technical field of communications. The method executed by an Internet of Things terminal device comprises: determining a start moment of a DRX inactivity timer according to transmission time information of a PDSCH, a PUSCH or a PDCCH, and a first duration; and starting the DRX inactivity timer at the start moment. Therefore, a start moment of a DRX inactivity timer and a start moment for monitoring a PDCCH are overlapped as much as possible, so that the Internet of Things terminal device can reliably monitor the PDCCH, and the reliability of an Internet of Things communication system is improved.

Description

A method and device for starting a timer

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a method and device for starting a timer.

Background technique

At present, the relevant communication protocols agree to configure only one hybrid automatic repeat request (HARQ) process for the Internet of Things (IoT) terminal device, or configure more than one HARQ process. In the case of only one HARQ process, the protocol agrees that the discontinuous reception inactivity timer (drx-inactivity timer) is started at the subframe where the last repetition of the physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) transmission is located. In the case of more than one HARQ process, if a new transmission is indicated by the physical downlink control channel (PDCCH), the drx-inactivity timer will also be started immediately.

However, for narrowband (NB) IOT terminal devices, the protocol also agrees that the terminal device will not monitor the narrowband PDCCH within 12 milliseconds (ms) after the narrowband PDSCH reception ends, that is, the drx-inactivity timer will not be started. This conflicts with the start timing of the drx-inactivity timer in the above agreement.

Summary of the invention

The embodiments of the present disclosure provide a method and device for starting a timer.

The first aspect of the present disclosure provides a method for starting a timer, which is executed by an Internet of Things terminal device, and includes:

Determine a start time of a discontinuous transmission DRX inactivity timer according to transmission time information of a physical downlink shared channel PDSCH, a physical uplink shared channel PUSCH, or a physical downlink control channel PDCCH and a first duration;

At the start time, the DRX inactivity timer is started.

In the present disclosure, the IoT terminal device determines the start time of the DRX inactivity timer according to the transmission time information of the PDSCH, PUSCH or PDCCH and the first duration, and then starts the DRX inactivity timer at the start time of the DRX inactivity timer. Thus, by maximally overlapping the start time of the DRX inactivity timer with the start time of monitoring the PDCCH, it is ensured that the IoT terminal device can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

A second aspect of the present disclosure provides a method for starting a timer, the method being executed by a network device, and the method comprising:

According to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH, the start time of the discontinuous transmission DRX inactivation timer in the Internet of Things terminal device is determined.

A third aspect of the present disclosure provides a communication device, the communication device comprising:

A processing module, configured to determine a start time of a discontinuous transmission DRX inactivation timer according to transmission time information of a physical downlink shared channel PDSCH, a physical uplink shared channel PUSCH, or a physical downlink control channel PDCCH and a first duration;

The processing module is further configured to start the DRX inactivity timer at the start time.

A fourth aspect of the present disclosure provides a communication device, the communication device comprising:

The processing module is used to determine the start time of the discontinuous transmission DRX inactivation timer in the Internet of Things terminal device according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH.

The fifth aspect embodiment of the present disclosure proposes a communication device, which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory so that the device executes the timer starting method described in the first aspect embodiment.

The sixth aspect embodiment of the present disclosure proposes a communication device, which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory so that the device executes the timer starting method described in the second aspect embodiment.

The seventh aspect embodiment of the present disclosure proposes a communication device, which includes a processor and an interface circuit, the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the timer starting method described in the first aspect embodiment above.

An eighth aspect embodiment of the present disclosure proposes a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the timer starting method described in the second aspect embodiment.

An embodiment of a ninth aspect of the present disclosure provides a communication system, the system comprising the communication device described in the third aspect and the communication device described in the fourth aspect, or the system comprising the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system comprising the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system comprising the communication device described in the ninth aspect and the communication device described in the tenth aspect.

The tenth aspect embodiment of the present disclosure proposes a computer-readable storage medium for storing instructions. When the instructions are executed, the timer starting method described in the first aspect embodiment is implemented.

An eleventh embodiment of the present disclosure proposes a computer-readable storage medium for storing instructions. When the instructions are executed, the timer starting method described in the second embodiment is implemented.

The twelfth aspect of the present disclosure proposes a computer program product, which, when executed on a computer, enables the computer to execute the frequency domain resource configuration allocation method described in the first aspect of the present disclosure.

A thirteenth aspect of the present disclosure provides a computer program product, which, when executed on a computer, enables the computer to execute the timer starting method described in the second aspect of the present disclosure.

In a fourteenth aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, for supporting the first AMF to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the terminal device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

In a fifteenth aspect, the present disclosure provides a chip system, which includes at least one processor and an interface, and is used to support a terminal device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method. In a possible design, the chip system also includes a memory, and the memory is used to store computer programs and data necessary for the terminal device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

In a sixteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect.

In a seventeenth aspect, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect.

Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

FIG2 is a schematic flow chart of a method for starting a timer provided in an embodiment of the present disclosure;

FIG3 is a schematic flow chart of another method for starting a timer provided in an embodiment of the present disclosure;

FIG4 is a schematic flow chart of another method for starting a timer provided in an embodiment of the present disclosure;

FIG5 is a schematic flow chart of another method for starting a timer provided in an embodiment of the present disclosure;

FIG. 6 is a flow chart of another method for starting a timer provided in an embodiment of the present disclosure.

FIG7 is a schematic flow chart of another method for starting a timer provided in an embodiment of the present disclosure;

FIG8 is a schematic diagram of the structure of a communication device provided by an embodiment of the present disclosure;

FIG9 is a schematic diagram of the structure of another communication device provided in an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.

Detailed ways

For ease of understanding, the terms involved in the present disclosure are first introduced.

1. Physical downlink shared channel (PDSCH)

PDSCH is mainly used for transmission of downlink unicast data, and can also be used for transmission of paging messages and system messages.

2. Physical uplink shared channel (PUSCH)

The uplink physical channel corresponding to PDSCH is used to transmit uplink service data and can also be used to carry uplink control information (UCI).

3. Physical downlink control channel (PDCCH)

The PDCCH channel transmits downlink control information (DCI) related to PUSCH/PDSCH. The DCI information includes several related contents such as resource block (RB) allocation information, HARQ identifier, etc. Only when the terminal device correctly decodes the DCI information can it correctly process PDSCH data or PUSCH data.

4. Hybrid Automatic Repeat Request HARQ

HARQ is a new communication technology based on FEC (forward error correction) and ARQ (automatic retransmission) developed to better resist interference and fading, improve system throughput (effectiveness) and data transmission reliability.

5. HARQ feedback disabling

HARQ feedback disabling means that after receiving a HARQ signal, the receiver does not need to feed back a HARQ confirmation (ACK) message or a HARQ negative confirmation (NACK) message to the sender.

6. Narrow Band Internet of Things (NB-IoT)

NB-IoT is an emerging technology in the IoT field that supports cellular data connections of low-power devices in wide area networks, also known as low power wide area networks (LPWAN).

7. Enhanced machine type communication (eMTC)

eMTC, also known as LTE-machine to machine (LTE-M), is an Internet of Things technology based on the evolution of LTE.

8. Discontinuous reception (DRX)

The basic mechanism of DRX is to configure a DRX cycle for a terminal device in a radio resource control (RRC) connection state. The DRX cycle consists of an "On Duration" and an "Opportunity for DRX" period: during the "On Duration" period, the terminal device monitors and receives PDCCH; during the "Opportunity for DRX" period, the terminal device does not receive PDCCH to reduce power consumption.

9. Discontinuous reception inactivity timer (drx-inactivity timer)

If there is new uplink or downlink data to be transmitted during the On Duration period, the drx-InactivityTimer is started to indicate how long the terminal device needs to continue monitoring the PDCCH. As long as there is new data to be scheduled, the timer will be started (or restarted). The purpose of the drx-InactivityTimer is to reduce the data processing delay.

Please refer to FIG. 1, which is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. The number and form of devices shown in FIG. 1 are only used as examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. The communication system shown in FIG. 1 includes, for example, a network device 11 and an IoT terminal device 12.

It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long term evolution (LTE) system, fifth generation (5G) mobile communication system, 5G new radio (NR) system, or other future new mobile communication systems.

Optionally, the network device 11 in the communication system is an entity used to transmit or receive signals on the network side. For example, an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiments of the present disclosure may be composed of a central unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the protocol layer of a network device, such as a base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

The IoT terminal device 12 in the disclosed embodiment is an entity on the user side for receiving or transmitting signals. The IoT terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc. The IoT terminal device may be a car with communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

In this communication system, the Internet of Things terminal device 12 can implement the method shown in any embodiment of Figures 2 to 4 of the present disclosure, and the network device 11 can implement the method shown in any embodiment of Figures 5 to 7 of the present disclosure.

It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. A person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

It should be understood that, although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the term "in response to" as used herein may be interpreted as "at the time of" or "when" or "if". For the purpose of brevity and ease of understanding, the terms used herein when characterizing the size relationship are "greater than" or "less than", "higher than" or "lower than". However, for those skilled in the art, it can be understood that the term "greater than" also covers the meaning of "greater than or equal to", and "less than" also covers the meaning of "less than or equal to"; the term "higher than" covers the meaning of "higher than or equal to", and "lower than" also covers the meaning of "lower than or equal to".

The present disclosure mainly aims at the problem that the start timing of the drx-inactivity timer in NB-IOT agreed in the relevant protocol conflicts with the monitoring timing of the PDCCH, which may cause the start timing of the drx-inactivity timer to be advanced, indirectly resulting in a shortened time for the IoT terminal device to monitor the narrowband PDCCH. A method for determining the start time of the drx-inactivity timer according to the transmission time information of the PDSCH, PUSCH or PDCCH and the first duration is provided, thereby ensuring that the start timing of the drx-inactivity timer can meet the requirement that the IoT terminal device can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

The following describes in detail the method for starting a timer provided in the embodiments of the present disclosure in conjunction with the flow charts.

Please refer to FIG. 2, which is a flow chart of a method for starting a timer provided in an embodiment of the present disclosure. The method provided in this embodiment can be executed by an IoT terminal device. As shown in FIG. 2, the method can include but is not limited to the following steps:

Step 201: Determine a start time of a DRX inactivity timer according to transmission time information of a PDSCH, a PUSCH, or a PDCCH and a first duration.

Step 202: At the start time, start the DRX inactivity timer.

Among them, the transmission time information can be used to indicate the time domain position of the subframe occupied by the last repetition among multiple repetitions of PDSCH transmission. Or, it can be used to indicate the time domain position of the subframe occupied by the last repetition among multiple repetitions of PUSCH transmission; or, it can be used to indicate the time domain position occupied by PDCCH transmission. For example, the transmission time information is the start time or end time of the subframe occupied by the last repetition among multiple repetitions of PDSCH/PUSCH transmission, or the start time or end time of the time domain resources occupied by PDCCH transmission, etc., which is not limited in the present disclosure.

In addition, the first duration may be a duration determined by the IoT terminal device according to a protocol agreement, or may be a duration indicated by the network device to the IoT terminal device, and this disclosure does not limit this.

Optionally, when the IoT terminal device is configured with a downlink (DL) HARQ process and HARQ feedback is disabled, the start time of the DRX inactivation timer is determined to be the moment after the first time duration has passed after the subframe occupied by the last of multiple repetitions of the PDSCH transmission is received.

That is, the start time of the DRX inactivation timer = the subframe occupied by the last repetition of multiple repetitions of PDSCH transmission + T, where T is the first duration, such as 1ms, 4ms, 5ms, 10ms, 12ms, 13ms, etc.

Optionally, when the IoT terminal device is configured with an uplink (UL) HARQ process and the UL HARQ is in the first mode, the start time of the DRX inactivation timer is determined to be the moment after the first duration has passed after the subframe occupied by the last of multiple repetitions of sending the PUSCH transmission.

The first mode may be mode B. In mode B, the network device does not schedule retransmission based on the decoding result of the PUSCH data, that is, the network device can schedule retransmission without waiting for receiving the PUSCH. Therefore, in the present disclosure, the DRX inactivity timer may be started after the first time period has passed after the PUSCH is sent to monitor the PDCCH.

That is, the start time of the DRX inactivity timer = the subframe occupied by the last repetition of multiple repetitions of PUSCH transmission + T, where T is the first duration, such as 1ms, 4ms, 5ms, 10ms, 12ms, 13ms, etc.

Optionally, in the case where the network device configures a scheduling offset value for the terminal device, the first duration may also be determined according to the scheduling offset value, wherein the scheduling offset value is a frame timing value used by the network device when the downlink and uplink are not aligned.

For example, the first duration = scheduling offset value + a, where the value of a can be 1, 2, 3, etc., and this is not limited in the present disclosure.

Alternatively, when the IoT terminal device is configured with multiple DL HARQ processes, the start time of the DRX inactivation timer is determined to be the moment after the first period of time has passed after the new DL transmission indicated by the PDCCH is received; or, when the IoT terminal device is configured with multiple UL HARQ processes, the start time of the DRX inactivation timer is determined to be the moment after the first period of time has passed after the new UL transmission indicated by the PDCCH is received.

That is to say, if the NB-IOT terminal device or eMTC terminal device is configured with multiple DL HARQ processes, then after receiving the new DL/UL transmission indicated by the PDCCH, it can delay for the first time and then start the DRX inactivity timer to monitor the new PDCCH.

Please refer to FIG. 3, which is a flow chart of another method for starting a timer provided in an embodiment of the present disclosure. The method provided in this embodiment can be executed by an IoT terminal device. As shown in FIG. 3, the method can include but is not limited to the following steps:

Step 301, determining a first duration according to a first parameter value.

Among them, the first parameter value is a value used to determine the start time of the DRX inactivation timer in the auxiliary IoT terminal device, which can be any value that ensures that the IoT terminal device can reliably monitor the PDCCH after the start time of the DRX inactivation timer is delayed by the first duration determined based on it. The first parameter can be a fixed value, such as 12ms; or it can be a range of values, such as the first parameter value is any value in {1,2,3,4...,13}, which is not limited in the present disclosure.

Optionally, the first duration may be the same as the first parameter value, or the first duration may have a fixed relationship with the first parameter value, such as the first duration is 1.5 times, 2 times, etc. of the first parameter value, which is not limited in the present disclosure.

Optionally, the IoT terminal device may determine the first parameter value according to a protocol agreement; or, determine the first parameter value according to an instruction of a network device.

For example, the IoT terminal device can receive the first parameter value sent by the network device through a broadcast message or a radio resource control (RRC) message, etc., and the present disclosure does not limit this.

Step 302: Determine the start time of the DRX inactivity timer according to the transmission time information of the PDSCH, PUSCH, or PDCCH and the first duration.

Step 303: Start the DRX inactivity timer at the start time.

The specific implementation of the above steps 302-303 can refer to the detailed description of any embodiment in the present disclosure, which will not be repeated here.

In the present disclosure, the IoT terminal device first determines the first duration according to the first parameter value, and then determines that the start time of the DRX inactive timer is located at the moment after the subframe occupied by the last repetition in multiple repetitions of PDSCH/PUSCH transmission and the first duration has passed, or at the moment after the new transmission indicated by PDCCH is received and the first duration has passed. Therefore, by maximally overlapping the start time of the DRX inactive timer with the start time of monitoring the PDCCH, it is ensured that the IoT terminal device can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

Please refer to FIG. 4, which is a flow chart of another method for starting a timer provided in an embodiment of the present disclosure. The method provided in this embodiment can be executed by an IoT terminal device. As shown in FIG. 4, the method can include but is not limited to the following steps:

Step 401: Receive a scheduling offset value sent by a network device.

The scheduling offset value is a frame timing value used by the network device when the downlink and uplink are not aligned.

Optionally, the IoT terminal device can receive the scheduling offset value sent by the network device through a radio resource control (RRC) message, which is not limited in the present disclosure.

Step 402: determine the first duration according to the scheduling offset value and the second parameter value.

Among them, the second parameter value is a value used to determine the start time of the DRX inactive timer in the auxiliary IoT terminal device together with the scheduling offset value, which can be any value that makes the start time of the DRX inactive timer, after delaying the first duration determined based on it and the scheduling offset value, ensure that the IoT terminal device can reliably monitor the PDCCH. The second parameter can be a fixed value, such as 3; or it can be a range of values, such as the second parameter value is any value in {1,2,3,4...}, which is not limited in this disclosure.

Optionally, the first duration = scheduling offset value + second parameter value.

In some possible implementation forms, if the value of the scheduling offset value + the second parameter value is a non-integer, the first duration can also be the value of the "scheduling offset value + the second parameter value" rounded up or down. In order to avoid the timing of starting the DRX inactive timer earlier than the timing of the IoT terminal device starting to monitor the PDCCH, in the present disclosure, the value of the "scheduling offset value + the second parameter value" rounded up can be determined as the first duration. For example, if the scheduling offset value + the second parameter value = 3.5, then the first duration can be determined as 4.

Step 403: Determine the start time of the DRX inactivity timer according to the PUSCH transmission time information and the first duration.

Step 404: At the start time, start the DRX inactivity timer.

The specific implementation of the above steps 403-404 can refer to the detailed description of any embodiment in the present disclosure, which will not be repeated here.

It should be noted that since the scheduling offset value is the frame timing value determined by the network device after receiving the uplink data, the IoT terminal device can determine the start time of the DRX inactivation timer after PUSCH transmission based on the first duration determined by the scheduling offset value.

That is to say, if the IoT terminal device has received the scheduling offset value, then after the frame transmission of the last repetition in multiple repetitions of PUSCH transmission, the DRX inactivation timer can be started after a first delay to monitor the PDCCH.

In the present disclosure, when receiving the scheduling offset value, the IoT terminal device first determines the first duration according to the second parameter value and the scheduling offset value, and then determines that the start time of the DRX inactive timer is located at the time after the last repetition occupied subframe in the multiple repetitions of PUSCH transmission and after the first duration. Therefore, by maximally overlapping the start time of the DRX inactive timer with the start time of monitoring the PDCCH, it is ensured that the IoT terminal device can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

Please refer to Figure 5, which is a flow chart of another method for starting a timer provided by an embodiment of the present disclosure, and the method is executed by a network device. As shown in Figure 5, the method may include but is not limited to the following steps:

Step 501, determine the start time of the DRX inactivation timer in the Internet of Things terminal device according to the transmission time information of the PDSCH, PUSCH, or PDCCH and the first duration.

Among them, the transmission time information can be used to indicate the time domain position of the subframe occupied by the last repetition among multiple repetitions of PDSCH transmission. Or, it can be used to indicate the time domain position of the subframe occupied by the last repetition among multiple repetitions of PUSCH transmission; or, it can be used to indicate the time domain position occupied by PDCCH transmission. For example, the transmission time information is the start time or end time of the subframe occupied by the last repetition among multiple repetitions of PDSCH/PUSCH transmission, or the start time or end time of the time domain resources occupied by PDCCH transmission, etc., and the present disclosure does not limit this.

In addition, the first duration may be a duration determined by the network device according to a protocol agreement, and the present disclosure does not limit this.

Among them, the first mode can be mode B. Because in mode B, the network device does not perform retransmission scheduling based on the decoding result of the PUSCH data, that is, the network device does not need to wait for receiving the PUSCH to schedule retransmission. Therefore, in the present disclosure, the network device can determine that the DRX inactive timer in the IoT terminal device can be started after the first time period has passed after the PUSCH is sent. The network device can send PDCCH to the IoT terminal device at the start time of the DRX inactive timer or after it is started, thereby ensuring that the IoT terminal device can reliably monitor the PDCCH.

That is to say, if the NB-IOT terminal device or eMTC terminal device is configured with multiple DL HARQ processes, then after receiving the new DL/UL transmission indicated by the PDCCH, it can delay for the first period of time and then start the DRX inactivity timer. The network device can send PDCCH to the IoT terminal device at the start time of the DRX inactivity timer or after it is started, thereby ensuring that the IoT terminal device can reliably monitor the PDCCH.

It should be noted that in the present disclosure, after the network device determines the start time of the DRX inactive timer in the IoT terminal device, it can send the PDCCH based on the time. For example, the PDCCH starts to be sent at the start time of the DRX inactive timer, or after the start time of the DRX inactive timer. This ensures that when the networked terminal device performs PDCCH based on the DRX inactive timer, it can reliably monitor the PDCCH.

In the present disclosure, the network device determines the start time of the DRX inactive timer in the IoT terminal device according to the transmission time information of the PDSCH, PUSCH or PDCCH and the first duration, and then transmits the PDCCH. This ensures that the IoT terminal device that starts monitoring the PDCCH based on the DRX inactive timer can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

Please refer to Figure 6, which is a flow chart of another method for starting a timer provided in an embodiment of the present disclosure, and the method is executed by a network device. As shown in Figure 6, the method may include but is not limited to the following steps:

Step 601, determining a first duration according to a first parameter value.

Among them, the first parameter value is a value used to determine the start time of the DRX inactive timer in the auxiliary IoT terminal device, which can be any value that ensures that the IoT terminal device can reliably monitor the PDCCH after the start time of the DRX inactive timer in the IoT terminal device is delayed by the first duration determined based on it. The first parameter can be a fixed value, such as 12ms; or it can be a range of values, such as the first parameter value is any value in {1,2,3,4...,13}, which is not limited in the present disclosure.

Optionally, the network device and the IoT terminal device may determine the first parameter value according to a protocol agreement, respectively. Alternatively, the network device may send the determined first parameter value to the IoT terminal device.

For example, the network device may send the first parameter value to the IoT terminal device via a broadcast message or a radio resource control (RRC) message, etc., and the present disclosure does not limit this.

Step 602, determining the start time of the DRX inactivation timer in the IoT terminal device according to the transmission time information of the PDSCH, PUSCH, or PDCCH and the first duration.

Step 603: Send PDCCH to the IoT terminal device according to the start time of the DRX inactivation timer in the IoT terminal device.

Optionally, the network device may start sending PDCCH to the IoT terminal device at the start time of the DRX inactivity timer in the IoT terminal device; or, the network device may start sending PDCCH to the IoT terminal device at a certain time after the start time of the DRX inactivity timer in the IoT terminal device, such as at the 1ms, 2ms, etc. after the start time of the DRX inactivity timer. This is not limited in the present disclosure.

The specific implementation process of the

above steps

602 and 603 can refer to the detailed description of any embodiment of the present disclosure, and will not be repeated here.

In the present disclosure, the network device first determines the first duration according to the first parameter value, and then determines the start time of the DRX inactive timer in the IoT terminal device according to the transmission time information of the PDSCH, PUSCH or PDCCH and the first duration, and then transmits the PDCCH. This ensures that the IoT terminal device that starts monitoring the PDCCH based on the DRX inactive timer can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

Please refer to Figure 7, which is an interactive schematic diagram of a timer start method provided by an embodiment of the present disclosure. As shown in Figure 7, the method provided by this embodiment can be executed by a network device. As shown in Figure 7, the method can include but is not limited to the following steps:

Step 701, determining a first duration according to a scheduling offset value and a second parameter value, wherein the scheduling offset value is a frame timing value used by a network device when a downlink and an uplink are not aligned.

Among them, the second parameter value is a value used to determine the start time of the DRX inactive timer in the auxiliary IoT terminal device together with the scheduling offset value, which can be any value that makes the start time of the DRX inactive timer, after delaying the first duration determined based on it and the scheduling offset value, ensure that the IoT terminal device can reliably monitor the PDCCH. The second parameter can be a fixed value, such as 3; or it can be a range of values, such as the second parameter value is any value in {1,2,3,4...}, which is not limited in the present disclosure.

In some possible implementation forms, if the value of the scheduling offset value + the second parameter value is a non-integer, the first duration may also be a value after rounding up or down the "scheduling offset value + the second parameter value". In order to avoid the timing of starting the DRX inactivity timer earlier than the timing of the network device sending the PDCCH, in the present disclosure, the value of the "scheduling offset value + the second parameter value" rounded up may be determined as the first duration. For example, if the scheduling offset value + the second parameter value = 3.5, the first duration may be determined as 4.

Optionally, the network device may determine the second parameter value according to a protocol agreement with the IoT terminal device, or the network device may send the second parameter value to the IoT terminal device, which is not limited in the present disclosure.

Optionally, the network device may send a scheduling offset value to the IoT terminal device, so that the IoT terminal device may determine the first duration based on the scheduling offset value and the second parameter value.

In some possible embodiments, the IoT terminal device may receive a scheduling offset value sent by a network device via a radio resource control (RRC) message, which is not limited in the present disclosure.

Step 702: Determine the start time of the DRX inactivation timer in the IoT terminal device according to the transmission time information of the PUSCH and the first duration.

Step 703: Send PDCCH to the IoT terminal device according to the start time of the DRX inactivation timer in the IoT terminal device.

The specific implementation of the above steps 702-703 can refer to the detailed description of any embodiment in the present disclosure, which will not be repeated here.

It should be noted that since the scheduling offset value is the frame timing value determined by the network device after receiving the uplink data, the network device can determine the start time of the DRX inactivation timer in the IoT terminal device after PUSCH transmission based on the first duration determined by the scheduling offset value.

That is to say, if the network device has sent a scheduling offset value to the IoT terminal device, it can be determined that the IoT terminal device will start the DRX inactive timer after a first delay after the transmission of the frame in which the last repetition of multiple repetitions of PUSCH transmission is located, to monitor the PDCCH. The network device can then start sending PDCCH to the IoT terminal device at the start time of the DRX inactive timer, or at a certain time after the start time.

In the present disclosure, the network device first determines the first duration according to the scheduling offset value and the second parameter value, and then determines the start time of the DRX inactive timer in the IoT terminal device according to the transmission time information of the PUSCH and the first duration, and then transmits the PDCCH. This ensures that the IoT terminal device that starts monitoring the PDCCH based on the DRX inactive timer can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

Please refer to Figure 8, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure. The communication device 800 shown in Figure 8 may include a transceiver module 801 and a processing module 802. The transceiver module 801 may include a sending module and/or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module 801 may implement a sending function and/or a receiving function.

It can be understood that the communication device 800 can be an Internet of Things terminal device, or it can also be a device in the Internet of Things terminal device, or it can also be a device that can be used in conjunction with the Internet of Things terminal device.

When the communication device 800 is on the IoT terminal device side, wherein:

The processing module 802 is used to determine the start time of the discontinuous transmission DRX inactivation timer according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH;

The processing module 802 is further configured to start the DRX inactivity timer at the start time.

Optionally, the processing module 802 is further configured to:

In a case where the IoT terminal device is configured with a downlink DL hybrid automatic repeat request HARQ process and HARQ feedback is disabled, determining the start time of the DRX inactivity timer as a time after the subframe occupied by the last repetition of multiple repetitions of the PDSCH transmission is received and then the first duration has passed; or

When the IoT terminal device is configured with an uplink UL HARQ process and the UL HARQ is in the first mode, the start time of the DRX inactivation timer is determined to be the time after the first duration has passed after the subframe occupied by the last of multiple repetitions of sending the PUSCH transmission.

Optionally, the processing module 802 is further configured to:

In the case where the IoT terminal device is configured with multiple DL HARQ processes, the start time of the DRX inactivation timer is determined to be the time after the first time period has passed after the DL new transmission indicated by the PDCCH is received; or,

In the case where the IoT terminal device is configured with multiple UL HARQ processes, the start time of the DRX inactivation timer is determined to be the time after the first time duration has passed after the new UL transmission indicated by the PDCCH is received.

Optionally, the processing module 802 is further configured to:

determining the first duration according to a first parameter value; or,

The first duration is determined according to a scheduling offset value and a second parameter value, wherein the scheduling offset value is a frame timing value used by a network device when a downlink and an uplink are not aligned.

Optionally, the transceiver module 801 is used to receive the scheduling offset value sent by the network device.

Optionally, the processing module 802 is further configured to:

Determine the first parameter value or the second parameter value according to the protocol; or,

The first parameter value or the second parameter value is determined according to an instruction of the network device.

In the present disclosure, the IoT terminal device determines the start time of the DRX inactive timer according to the transmission time information of the PDSCH, PUSCH, or PDCCH and the time of the first duration, and then restarts the DRX inactive timer at the restart time. Thus, by overlapping the start time of the DRX inactive timer with the start time of monitoring the PDCCH as much as possible, it is ensured that the IoT terminal device can reliably monitor the PDCCH, thereby improving the reliability of the IoT communication system.

When the communication device 800 is on the network device side, wherein:

The processing module 802 is used to determine the start time of the discontinuous transmission DRX inactivation timer in the Internet of Things terminal device according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH.

Optionally, the processing module 802 is further configured to:

In a case where the IoT terminal device is configured with a downlink DL hybrid automatic repeat request HARQ process and HARQ feedback is disabled, determining the start time of the DRX inactivity timer as a time after the IoT terminal device receives a subframe occupied by the last repetition of multiple repetitions of the PDSCH transmission and then the first duration has passed; or,

When the IoT terminal device is configured with an uplink UL HARQ process and the UL HARQ is in the first mode, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device sends the subframe occupied by the last of multiple repetitions of the PUSCH transmission and then the first duration has passed.

Optionally, the processing module 802 is further configured to:

In the case where the IoT terminal device is configured with multiple DL HARQ processes, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device receives the new DL transmission indicated by the PDCCH and then the first time duration has passed; or,

In the case where the IoT terminal device is configured with multiple UL HARQ processes, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device receives the new UL transmission indicated by the PDCCH and then the first time duration has passed.

Optionally, the processing module 802 is further configured to:

determining the first duration according to a first parameter value; or,

Optionally, the transceiver module 801 is used to send the scheduling offset value to the Internet of Things terminal device.

Optionally, the processing module 802 is further configured to:

Determine the first parameter value or the second parameter value according to the protocol; and/or,

The transceiver module 801 is further configured to send the first parameter value or the second parameter value to the IoT terminal device.

Please refer to Figure 9, which is a schematic diagram of the structure of another communication device provided in an embodiment of the present disclosure. The communication device 900 can be an IoT terminal device, or a chip, a chip system, or a processor that supports the IoT terminal device to implement the above method; or, the communication device 900 can be a network device, or a chip, a chip system, or a processor that supports the network device to implement the above method. The device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.

The communication device 900 may include one or more processors 901. The processor 901 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and the communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

Optionally, the communication device 900 may further include one or more memories 902, on which a computer program 904 may be stored, and the processor 901 executes the computer program 904 so that the communication device 900 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 902. The communication device 900 and the memory 902 may be provided separately or integrated together.

Optionally, the communication device 900 may further include a transceiver 905 and an antenna 906. The transceiver 905 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 1205 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

Optionally, the communication device 900 may further include one or more interface circuits 907. The interface circuit 907 is used to receive code instructions and transmit them to the processor 901. The processor 901 runs the code instructions to enable the communication device 900 to execute the method described in the above method embodiment.

The transceiver 905 in the communication device 900 may be used to execute the transceiver steps in the above figures, and the processor 901 may be used to execute the processing steps in the above figures.

In one implementation, the processor 9201 may include a transceiver for implementing receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

In one implementation, the processor 901 may store a computer program 903, which runs on the processor 901 and enables the communication device 900 to perform the method described in the above method embodiment. The computer program 903 may be fixed in the processor 901, in which case the processor 901 may be implemented by hardware.

In one implementation, the communication device 900 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver may also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

The communication device described in the above embodiments may be a network device or an intelligent relay, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 9. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

(1) Independent integrated circuit IC, or chip, or chip system or subsystem;

(2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

(3) ASIC, such as modem;

(4) Modules that can be embedded in other devices;

(5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

(6)Others

For the case where the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 10. The chip shown in Figure 10 includes a processor 1001 and an interface 1002. The number of processors 1001 can be one or more, and the number of interfaces 1002 can be multiple.

Regarding the case where the chip is used to implement the functions of the terminal device in the embodiment of the present disclosure.

Optionally, the chip further includes a memory 1003, and the memory 1003 is used to store necessary computer programs and data.

Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present disclosure.

The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

Those skilled in the art can understand that the various numerical numbers such as first and second involved in the present disclosure are only used for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, but also indicate the order of precedence.

At least one in the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

The corresponding relationships shown in the tables in the present disclosure may be coverage ranges or predefined. The values of the information in each table are merely examples, and the coverage range may be other values, which are not limited by the present disclosure. When covering the corresponding relationship between the coverage range information and each parameter, it is not necessarily required to cover all the corresponding relationships illustrated in each table. For example, in the table in the present disclosure, the corresponding relationships shown in some rows may not cover the range. For another example, appropriate deformation adjustments may be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles in the above tables may also use other names that can be understood by the communication device, and the values or representations of the parameters may also be other values or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-covered, solidified, or pre-fired.

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

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

The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

A method for starting a timer, characterized in that it is executed by an Internet of Things terminal device, and the method includes:

Determine a start time of a discontinuous transmission DRX inactivity timer according to transmission time information of a physical downlink shared channel PDSCH, a physical uplink shared channel PUSCH, or a physical downlink control channel PDCCH and a first duration;

At the start time, the DRX inactivity timer is started.
The method according to claim 1, characterized in that the step of determining the start time of the discontinuous transmission DRX inactivity timer according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH comprises:

In a case where the IoT terminal device is configured with a downlink DL hybrid automatic repeat request HARQ process and HARQ feedback is disabled, determining the start time of the DRX inactivity timer as a time after the subframe occupied by the last repetition of multiple repetitions of the PDSCH transmission is received and then the first duration has passed; or

When the IoT terminal device is configured with an uplink UL HARQ process and the UL HARQ is in the first mode, the start time of the DRX inactivation timer is determined to be the time after the first duration has passed after the subframe occupied by the last of multiple repetitions of sending the PUSCH transmission.
The method according to claim 1, characterized in that the step of determining the start time of the discontinuous transmission DRX inactivity timer according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH comprises:

In the case where the IoT terminal device is configured with multiple DL HARQ processes, the start time of the DRX inactivation timer is determined to be the time after the first time period has passed after the DL new transmission indicated by the PDCCH is received; or,

In the case where the IoT terminal device is configured with multiple UL HARQ processes, the start time of the DRX inactivation timer is determined to be the time after the first time duration has passed after the new UL transmission indicated by the PDCCH is received.
The method according to any one of claims 1 to 3, further comprising:

determining the first duration according to a first parameter value; or,

The first duration is determined according to a scheduling offset value and a second parameter value, wherein the scheduling offset value is a frame timing value used by a network device when a downlink and an uplink are not aligned.
The method according to claim 4, further comprising:

The scheduling offset value sent by the network device is received.
The method according to claim 4, further comprising:

Determine the first parameter value or the second parameter value according to the protocol; or,

The first parameter value or the second parameter value is determined according to an instruction of the network device.
A method for starting a timer, characterized in that it is executed by a network device, and the method comprises:

According to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH, the start time of the discontinuous transmission DRX inactivation timer in the Internet of Things terminal device is determined.
The method according to claim 7, characterized in that the step of determining the start time of the discontinuous transmission DRX inactivity timer in the IoT terminal device according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH comprises:

In a case where the IoT terminal device is configured with a downlink DL hybrid automatic repeat request HARQ process and HARQ feedback is disabled, determining the start time of the DRX inactivity timer as a time after the IoT terminal device receives a subframe occupied by the last repetition of multiple repetitions of the PDSCH transmission and then the first duration has passed; or,

When the IoT terminal device is configured with an uplink UL HARQ process and the UL HARQ is in the first mode, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device sends the subframe occupied by the last of multiple repetitions of the PUSCH transmission and then the first duration has passed.
The method according to claim 7, characterized in that the step of determining the start time of the discontinuous transmission DRX inactivity timer in the IoT terminal device according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH comprises:

In the case where the IoT terminal device is configured with multiple DL HARQ processes, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device receives the new DL transmission indicated by the PDCCH and then the first time duration has passed; or,

In the case where the IoT terminal device is configured with multiple UL HARQ processes, the start time of the DRX inactivation timer is determined as the time after the IoT terminal device receives the new UL transmission indicated by the PDCCH and then the first time duration has passed.
The method according to any one of claims 7 to 9, further comprising:

determining the first duration according to a first parameter value; or,

The first duration is determined according to a scheduling offset value and a second parameter value, wherein the scheduling offset value is a frame timing value used by a network device when a downlink and an uplink are not aligned.
The method according to claim 10, further comprising:

Send the scheduling offset value to the Internet of Things terminal device.
The method according to claim 10, further comprising:

Determine the first parameter value or the second parameter value according to the protocol; and/or,

Send the first parameter value or the second parameter value to the Internet of Things terminal device.
A communication device, comprising:

A processing module, configured to determine a start time of a discontinuous transmission DRX inactivation timer according to transmission time information of a physical downlink shared channel PDSCH, a physical uplink shared channel PUSCH, or a physical downlink control channel PDCCH and a first duration;

The processing module is further configured to start the DRX inactivity timer at the start time.
A communication device, comprising:

The processing module is used to determine the start time of the discontinuous transmission DRX inactivation timer in the Internet of Things terminal device according to the transmission time information and the first duration of the physical downlink shared channel PDSCH, the physical uplink shared channel PUSCH, or the physical downlink control channel PDCCH.
A communication device, characterized in that the device comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program stored in the memory so that the device performs the method as described in any one of claims 1 to 6, or performs the method as described in any one of claims 7 to 12.
A communication device, characterized in that it comprises: a processor and an interface circuit;

The interface circuit is used to receive code instructions and transmit them to the processor;

The processor is configured to run the code instructions to execute the method according to any one of claims 1 to 6, or to execute the method according to any one of claims 7 to 12.
A communication system, characterized in that the communication system includes an Internet of Things terminal device and a network device;

The Internet of Things terminal device is used to execute the method described in any one of claims 1-6, and the network device is used to execute the method described in any one of claims 7-12.
A computer-readable storage medium for storing instructions, which, when executed, enables the method according to any one of claims 1 to 6 to be implemented, or enables the method according to any one of claims 7 to 12 to be implemented.