Communication method, apparatus and device

Abstract

A communication method, an apparatus, and a device are provided. In the method, a terminal device transmits uplink data corresponding to M HARQ processes and receives first indication information, the first indication information indicating whether to start DRX uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes. The terminal device starts the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer, and receives second indication information when the DRX uplink retransmission timer runs, the second indication information indicating retransmission of the uplink data corresponding to the N HARQ processes. The terminal device can timely determine whether to start the DRX uplink retransmission timer based on the first indication information. When uplink data corresponding to the HARQ processes needs to be retransmitted, the DRX uplink retransmission timer may be started, or when no uplink data needs to be retransmitted, the DRX uplink timer may not be started, thereby reducing power consumption of the terminal device.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202211727912.X, entitled "DISCONTINUOUS RECEPTION DRX CONFIGURATION METHOD AND APPARATUS, AND DEVICE," filed with the State Intellectual Property Office of China on December 30, 2022, which is incorporated herein by reference in its entirety.

[0002] [Technical field] This application relates to the field of wireless communications, and in particular to communication methods, apparatus and devices. [Background technology]

[0003] In recent years, with the continuous development of the fifth-generation (5G) communication system, data transmission latency has been continuously reduced and transmission capacity has been increasingly increased. 5G communication systems have been gradually introduced into several multimedia services with high requirements for real-time performance and data capacity, such as video transmission, cloud gaming (CG), and extended reality (XR). XR includes virtual reality (VR) and augmented reality (AR).

[0004] As communication transmission rates rapidly increase, real-time video transmission services are gradually becoming one of the core services in current networks. With the continuous advancement and improvement of XR technology, related industries are also developing vigorously. As a type of XR, VR has entered various fields closely related to people's production and life, such as education, entertainment, military, medical care, environmental protection, transportation, and public health. Compared with traditional video services, VR has multiple viewing angles, strong interaction, and other advantages, providing users with a new visual experience. In addition to smartphones, people may also use terminal devices such as head-mounted displays (HMDs) or smart glasses (such as VR glasses and AR glasses) to enhance their XR experience.

[0005] However, for uplink data, the network device does not feed back acknowledgement / negative acknowledgement (ACK / NACK) to the terminal device, so the terminal device cannot determine whether to start a discontinuous reception (DRX) uplink retransmission timer to perform retransmission. Summary of the Invention

[0006] This application provides a communication method, apparatus and device for solving the problem that a terminal device cannot timely determine whether to start a DRX uplink retransmission timer.

[0007] According to a first aspect, an embodiment of the present application provides a communication method, which may be executed by a terminal device, may be executed by a component of the terminal device (e.g., a processor, a chip, or a chip system), or may be realized by a logical node, a logical module, or software capable of realizing all or part of the functions of the terminal device. The method includes: transmitting uplink data corresponding to M hybrid automatic repeat request (HARQ) processes, where M is an integer greater than or equal to 1; receiving first indication information, where the first indication information indicates whether to start discontinuous reception (DRX) uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; starting the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer; and receiving second indication information, where the second indication information indicates retransmission of the uplink data corresponding to the N HARQ processes.

[0008] In the DRX configuration method provided in the above embodiments of this application, the network device notifies the terminal device in a timely manner whether to start the DRX uplink retransmission timer by using the first indication information. Therefore, the terminal device can timely determine whether to start the DRX uplink retransmission timer based on the first indication information. When there is uplink data corresponding to the HARQ process that needs to be retransmitted, the terminal device starts the DRX uplink retransmission timer. When there is no uplink data corresponding to the HARQ process that needs to be retransmitted, the terminal device does not need to start the DRX uplink retransmission timer, thereby reducing the power consumption of the terminal device.

[0009] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process. In this implementation, the first indication information may indicate whether to start a DRX uplink retransmission timer corresponding to one HARQ process. The network device may use M pieces of first indication information to indicate whether to start DRX uplink retransmission timers corresponding to the M HARQ processes, respectively, so that the terminal device can timely determine the DRX uplink retransmission timers corresponding to the HARQ processes to be started.

[0010] In a possible implementation, the first indication information indicates whether to start DRX uplink retransmission timers corresponding to multiple HARQ processes. In this implementation, the first indication information may indicate whether to start DRX uplink retransmission timers corresponding to multiple HARQ processes. For example, the first indication information may indicate whether to start DRX uplink retransmission timers corresponding to M HARQ processes, which facilitates reducing signaling overhead.

[0011] In a possible implementation, multiple HARQ processes correspond to one DRX uplink retransmission timer. The terminal device may provide one DRX uplink retransmission timer for multiple HARQ processes to simplify the operation of the terminal device and facilitate reducing the power consumption of the terminal device.

[0012] In a possible implementation, the multiple HARQ processes correspond to multiple DRX uplink retransmission timers, respectively. The terminal device may provide a corresponding DRX uplink retransmission timer for each HARQ process, and monitor the second indication information corresponding to each HARQ process during the operation of each timer, so that the terminal device determines the HARQ process corresponding to the second indication information.

[0013] In a possible implementation manner, the first indication information includes information indicating N. The first indication information includes information indicating N, so that the terminal device can quickly determine the number of HARQ processes for which process retransmission needs to be performed. Furthermore, when the timing length of the DRX uplink retransmission timer is related to the value of N, the terminal device can also quickly determine the timing length of the DRX uplink retransmission timer based on the value of N.

[0014] In a possible implementation, the timing length of the DRX uplink retransmission timer is related to N. In this implementation, a larger value of N indicates a longer timing length of the DRX uplink retransmission timer, i.e., a longer maximum time length for which the terminal device can monitor the second indication information, which helps the network device to perform scheduling and also helps the terminal device to completely receive the second indication information sent by the network device.

[0015] In a possible implementation manner, receiving the first indication information includes receiving the first indication information from a first time point, where the first time point is one of the following: a time point a first length of time after the end of the transmission of uplink data, where the first length of time is a downlink feedback information DFI delay time length; or the first length of time is configured by the network device, for example, the network adds a new parameter in control signaling to configure the first length of time, or configures a new timer, the timing length of the new timer is the first length of time; or an expiration time of an uplink HARQ round trip time timer. After transmitting the uplink data, the terminal device may wait for a certain period of time, and then start to monitor the first indication information, waiting for the network device to receive and analyze the uplink data. During the waiting time, the terminal device does not need to monitor the first indication information sent by the network device, which reduces the power consumption of the terminal device.

[0016] In a possible implementation manner, after receiving the second indication information, the method further includes: stopping operating a DRX uplink retransmission timer. After receiving the second indication information, the terminal device stops operating the DRX uplink retransmission timer, i.e., no longer monitors the second indication information sent by the network device, and reduces the power consumption of the terminal device.

[0017] In a possible implementation, the method further includes skipping starting a DRX uplink retransmission timer when the first indication indicates to skip starting the DRX uplink retransmission timer. When the first indication indicates to skip starting the DRX uplink retransmission timer, this indicates that there is no HARQ process that needs to be retransmitted. In this case, the network device skips starting the DRX uplink retransmission timer and skips monitoring the second indication, thereby reducing power consumption of the terminal device.

[0018] In a possible implementation, the first indication information is carried in the wake-up signal WUS, or the first indication information is carried in the low-power WUS, or the first indication information is included in the DFI.

[0019] According to a second aspect, an embodiment of the present application provides a communication method, which may be executed by a network device, or may be executed by a component (e.g., a processor, a chip, or a chip system) of the network device, or may be realized by a logical node, a logical module, or software capable of realizing all or part of the functions of the network device. The method includes: receiving uplink data corresponding to M hybrid automatic repeat request (HARQ) processes, where M is an integer greater than or equal to 1; transmitting first indication information, where the first indication information indicates whether to start discontinuous reception (DRX) uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; starting the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer; and transmitting second indication information when the DRX uplink retransmission timer is running, where the second indication information indicates retransmission of the uplink data corresponding to the N HARQ processes.

[0020] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

[0021] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to multiple HARQ processes.

[0022] In a possible implementation, multiple HARQ processes correspond to one DRX uplink retransmission timer.

[0023] In a possible implementation, multiple HARQ processes correspond to multiple DRX uplink retransmission timers, respectively.

[0024] In a possible implementation, the first indication information includes information indicating N.

[0025] In a possible implementation, the duration of the DRX uplink retransmission timer is related to N.

[0026] In a possible implementation, the step of transmitting the first indication information includes the step of transmitting the first indication information from a first time point, where the first time point is one of the following: a time point that is a first length of time after the end of the transmission of uplink data, where the first length of time is a downlink feedback information DFI delay time length; or an expiration time of an uplink HARQ round trip time timer.

[0027] In a possible implementation, the first indication information is carried in the wake-up signal WUS, or the first indication information is carried in the low-power WUS, or the first indication information is included in the DFI.

[0028] According to a third aspect, an embodiment of the present application provides a communication device. The communication device includes a module / unit for performing the method according to the first aspect or any one of the possible implementation manners of the first aspect. The device may be a terminal device, or a component of the terminal device (e.g., a processor, a chip, or a chip system), or a logical node, a logical module, or software capable of realizing all or part of the functions of the terminal device. These modules / units may be realized by hardware, or by hardware executing corresponding software.

[0029] For example, the communication device may include a processing module and an interface module. Specifically, the interface module is configured to transmit uplink data corresponding to M HARQ processes, where M is an integer greater than or equal to 1. The interface module is further configured to receive first indication information, where the first indication information indicates whether to start DRX uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M. The processing module is configured to start the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer, and when the DRX uplink retransmission timer runs, the interface module is further configured to receive second indication information, where the second indication information indicates retransmission of the uplink data corresponding to the N HARQ processes.

[0030] According to a fourth aspect, an embodiment of the present application provides a communication device. The communication device includes a module / unit for performing the method according to the second aspect or any one of the possible implementation manners of the second aspect. The device may be a network device, or a component of the network device (e.g., a processor, a chip, or a chip system), or a logical node, a logical module, or software capable of implementing all or part of the functions of the network device. These modules / units may be implemented by hardware, or by hardware executing corresponding software.

[0031] For example, the communication device may include a processing module and an interface module. Specifically, the interface module is configured to receive uplink data corresponding to M HARQ processes, where M is an integer greater than or equal to 1. The interface module is further configured to send first indication information, where the first indication information indicates whether to start DRX uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M. If the first indication information indicates to start the DRX uplink retransmission timer, the processing module is configured to start the DRX uplink retransmission timer, and the interface module is further configured to send second indication information when the DRX uplink retransmission timer runs, where the second indication information indicates retransmission of the uplink data corresponding to the N HARQ processes.

[0032] According to a fifth aspect, an embodiment of the present application provides a communications apparatus, the apparatus including a processor, the processor coupled to a memory, the memory configured to store a program or instructions, which, when executed by the processor, enable the communications device to perform a method according to the first aspect or any one of the possible implementation manners of the first aspect. The apparatus may be a terminal device, or a component of a terminal device (e.g., a processor, a chip or a chip system), or a logical node, logical module or software capable of realizing all or part of the functionality of the terminal device.

[0033] According to a sixth aspect, an embodiment of the present application provides a communications apparatus, the apparatus including a processor, the processor coupled to a memory, the memory configured to store a program or instructions that, when executed by the processor, enable the communications device to perform a method according to the second aspect or any one of the possible implementations of the second aspect. The apparatus may be a network device, or a component of a network device (e.g., a processor, a chip, or a chip system), or a logical node, logical module, or software capable of implementing all or part of the functionality of the network device.

[0034] According to a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium storing instructions, which, when run on a computer, enable the computer to perform a method according to any one of the first aspect and the implementation manner of the first aspect, or a method according to any one of the second aspect and the implementation manner of the second aspect.

[0035] According to an eighth aspect, an embodiment of the present application provides a computer program product including instructions, which, when run on a computer, enable the computer to perform a method according to any one of the first aspect and the implementation manner of the first aspect, or a method according to any one of the second aspect and the implementation manner of the second aspect.

[0036] According to a ninth aspect, an embodiment of the present application provides a chip including a processor. The processor is coupled to a memory. The memory is configured to store instructions. When the instructions are executed by the processor, the chip is enabled to implement a method according to any one of the first aspect, the second aspect, a possible implementation of the first aspect, or a possible implementation of the second aspect.

[0037] According to a tenth aspect, an embodiment of the present application provides a communication system including an apparatus according to the third aspect and an apparatus according to the fourth aspect.

[0038] According to an eleventh aspect, an embodiment of the present application provides a communication system including an apparatus according to the fifth aspect and an apparatus according to the sixth aspect.

[0039] For the technical effects that can be achieved by any one of the implementation methods of any one of the second to eleventh aspects, please refer to the description of the technical effects that can be achieved by the corresponding implementation solution in the first aspect. The repeated parts will not be described in this specification. [Brief explanation of the drawings]

[0040] [Figure 1] FIG. 10 is a diagram illustrating the transmission rate of an image frame. [Figure 2] FIG. 1 is a diagram of a DRX cycle. [Figure 3] FIG. 1 is a diagram of a short DRX cycle and a long DRX cycle. [Figure 4] FIG. 10 is a diagram of a DRX downlink retransmission. [Figure 5] FIG. 1 is a diagram illustrating monitoring of a WUS by a terminal device. [Figure 6] FIG. 1 is a diagram of a system architecture according to an embodiment of the present application. [Figure 7] 2 is a schematic flowchart of a DRX configuration method according to an embodiment of the present application; [Figure 8(a)] FIG. 2 is a diagram of one type of first indication information according to an embodiment of the present application. [Figure 8(b)] FIG. 2 is a diagram of one type of first indication information according to an embodiment of the present application. [Figure 9] FIG. 10 is a diagram of another type of first indication information according to an embodiment of the present application. [Figure 10] FIG. 10 is a diagram of yet another type of first indication information according to an embodiment of the present application. [Figure 11(a)] FIG. 10 is a diagram of a period for monitoring first indication information according to an embodiment of the present application. [Figure 11(b)]FIG. 10 is a diagram of a period for monitoring first indication information according to an embodiment of the present application. [Figure 11(c)] FIG. 10 is a diagram of a period for monitoring first indication information according to an embodiment of the present application. [Figure 11(d)] FIG. 10 is a diagram of a period for monitoring first indication information according to an embodiment of the present application. [Figure 12] FIG. 2 is a diagram of the timing length of a DRX uplink retransmission timer according to an embodiment of the present application. [Figure 13] 1 is a diagram of the structure of a communication device according to an embodiment of the present application; [Figure 14] FIG. 1 is a diagram of the structure of another communication device according to an embodiment of the present application; [Figure 15] FIG. 10 is a diagram of the structure of yet another communication device according to an embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0041] The service model of XR transmission services and video transmission services is typically such that uplink and downlink data are transmitted periodically based on a frame rate. As shown in FIG. 1, ideally, one frame of image is transmitted every 16.67 milliseconds for a video with a frame rate of 60 frames per second (FPS). Furthermore, the data volume of XR transmission services and video services is typically large. For example, the size of a 4K video frame is approximately 30 KB to 100 KB. Furthermore, the sizes of different video frames typically vary. Because different video frames have different compression rates and different frame types, the sizes of different video frames also vary significantly.

[0042] Different XR services have different uplink and downlink service models. Display changes in VR scene content are triggered by changes in the orientation or position of the terminal device. Therefore, uplink data transmission for VR services is primarily for position and orientation information, which typically involves a small amount of data, typically only tens of kilobits per second (kbps). Downlink transmission is primarily for rendered video streams, which involve a large amount of data, potentially reaching tens to hundreds of megabits per second (Mbps). Unlike VR, display changes in AR scene content are triggered by changes in the gaze focus target and changes in the spatial relationship (action) between the position and the gaze point. Uplink transmission includes visual information (including depth information, etc.) necessary for perception. Therefore, uplink data transmission for AR services is primarily for clear and stable images or video streams, which involve a large amount of data. Alternatively, uplink data transmission may be for environmental feature information. Based on industry research and evaluation, a network uplink rate of approximately 2 Mbit / s is required for an initial experience of an interactive AR service, while a network uplink rate of 10 Mbit / s to 20 Mbit / s is required for an advanced experience. Compared with cloud VR, cloud AR has higher requirements for uplink transmission rate, making uplink transmission more difficult.

[0043] For XR and video transmission services, the generation and arrival of uplink and downlink data packets are not continuous. Therefore, the terminal device monitors the downlink control signaling of the network device in different slots to perform uplink and downlink data transmission, which increases the power consumption of the terminal device. When no data is transmitted, the terminal device may stop receiving the physical downlink control channel (PDCCH) (in this case, the terminal device stops PDCCH blind detection) to reduce power consumption and thereby increase battery life. Discontinuous reception (DRX) technology can achieve power saving. The basic mechanism of DRX is to configure a DRX cycle for the terminal device. As shown in Figure 2, during the active period, the terminal device monitors the PDCCH as usual. During the sleep period, the terminal device may enter a sleep state and not receive the PDCCH, thereby reducing power consumption. It should be noted that a terminal device in a sleep state does not only receive the PDCCH, but may also receive data from other physical channels, such as a physical downlink shared channel (PDSCH) or an acknowledgement (ACK). For example, in semi-persistent scheduling (SPS), a terminal device in a sleep state may receive the PDSCH in periodically configured downlink subframes.

[0044] During the selection of the DRX cycle, a balance between battery saving and data latency needs to be considered. A long DRX cycle facilitates extending the battery life of a terminal device. However, a short DRX cycle facilitates a faster response when there is a new data transmission. To meet the requirements of a terminal device regarding power consumption and data latency, two DRX cycles, namely a short DRX cycle and a long DRX cycle, may be configured for one terminal device, as shown in FIG. 3. However, the terminal can use only one of the configurations at any one time.

[0045] The DRX cycle of a terminal device is typically configured by a network device. For example, the network device may perform DRX configuration by using radio resource control (RRC) signaling. For a long DRX cycle, the parameter drx-LongCycle indicates the cycle value of the long DRX cycle, and the parameter drx-StartOffset indicates the offset of the long DRX cycle. The two parameters jointly determine the start subframe of the long DRX cycle. For a short DRX cycle, the parameter drx-ShortCycle indicates the cycle value of the short DRX cycle, and the parameter drx-ShortCycleTimer is for configuring the number of short DRX cycles. The parameter drx-OnDurationTimer is for configuring the length of the On Duration period in the DRX cycle. The parameter drx-SlotOffset is for configuring the delay for starting the DRX OnDuration timer. Specifically, within a DRC cycle, the DRX OnDuration timer starts after the slot offset indicated by drx-SlotOffset from the On Duration subframe, where drx-SlotOffset is the offset within the subframe and is less than 1 ms.

[0046] Furthermore, the DRX configuration information further includes a parameter drx-RetransmissionTimerDL and a parameter drx-HARQ-RTT-TimerDL. The parameter drx-RetransmissionTimerDL is a DRX downlink retransmission timer, and the parameter drx-HARQ-RTT-TimerDL indicates a DRX downlink hybrid automatic repeat request (HARQ) round-trip time (RTT) timer. The two parameters are used for downlink data retransmission. After the transmission of the PDCCH and PDSCH is completed, the terminal device feeds back an ACK / NACK. If the terminal device feeds back a NACK, the DRX downlink HARQ round-trip time timer starts after the ACK / NACK is fed back, and the timing period of the DRX downlink HARQ round-trip time timer is for the network device to wait for receiving and analyzing the NACK. When the DRX downlink HARQ round trip time timer expires, the terminal device starts a DRX downlink retransmission timer and wakes up to monitor the PDCCH for retransmitting downlink data, as shown in Figure 4. When the transmission of the HARQ process to be retransmitted is completed, the terminal device stops operating the DRX downlink retransmission timer.

[0047] Similarly, the DRX configuration information further includes a parameter drx-RetransmissionTimerUL and a parameter drx-HARQ-RTT-TimerUL. The parameter drx-RetransmissionTimerUL indicates a DRX uplink retransmission timer, and the parameter drx-HARQ-RTT-TimerUL indicates a DRX uplink HARQ round trip time timer. The two parameters are used for uplink data retransmission. Unlike downlink transmission, after completing PUSCH transmission, the terminal device immediately starts the DRX uplink HARQ round trip time timer without waiting for feedback from the network device. In other words, the terminal device starts the DRX uplink HARQ round trip time timer regardless of whether the network device correctly receives the PUSCH. When the DRX uplink HARQ round trip time timer expires, the terminal device starts the DRX uplink retransmission timer, and wakes up to monitor the PDCCH for retransmitting uplink data. When receiving downlink control information (DCI) indicating a HARQ process that needs to be retransmitted, the terminal device stops timing of the DRX uplink retransmission timer. Specifically, the terminal device does not need to perform monitoring during the entire configured uplink retransmission (retransmissionUL) period, but may disable the DRX uplink retransmission timer in advance after receiving the DCI indicating retransmission.

[0048] A PDCCH-based wake-up signal (WUS) can further improve energy saving. The WUS is usually associated with a long DRX cycle and indicates whether to skip monitoring the PDCCH during the On Duration period of the next long DRX cycle. The WUS may be carried in DCI format (format 2_6), and the WUS configuration information may include a parameter ps-Offset-r16 indicating the start monitoring time of DCI format 2_6, which starts in the period before the On Duration of the long DRX cycle. The terminal device stops monitoring DCI format 2_6 at a minimum offset before the On Duration of the long DRX cycle. The minimum offset is related to the capability and subcarrier of the terminal device. DCI format 2_6 is a common DCI and may include DCI information for multiple terminal devices, with information for different terminal devices located at different positions in DCI format 2_6. Therefore, parameters sizeDCI-2-6-r16 and ps-PositionDCI-2-6-r16 indicate the length of DCI format 2_6 and the position of DCI information corresponding to a terminal device in DCI format 2_6, respectively. Parameter ps-WakeUp-r16 indicates the default behavior of a terminal device, specifically, whether the terminal device monitors the PDCCH normally when the terminal device is configured to monitor DCI format 2_6 but does not receive corresponding WUS information.

[0049] In DCI format 2_6, the DCI information corresponding to a terminal device may include one bit for indicating whether the terminal device skips monitoring the PDCCH during the On Duration period in the next long DRX cycle. When the bit value is 1, the terminal device monitors the PDCCH normally during the On Duration period in the next long DRX cycle. When the bit value is 0, the terminal device skips monitoring the PDCCH during the On Duration period in the next long DRX cycle.

[0050] A diagram of the WUS effect may be as shown in Figure 5. Generally, a terminal device monitors DCI format 2_6 only during sleep in DRX and does not monitor DCI format 2_6 during On Duration. Furthermore, a terminal device does not monitor more than one DCI format 2_6 within one long DRX cycle.

[0051] When multiple PUSCH transmission opportunities are configured within one XR service cycle to transmit XR frame data, the terminal device starts a DRX uplink retransmission timer of the HARQ process corresponding to the PUSCH every time the PUSCH is transmitted, and monitors the PDCCH during the count period of the DRX uplink retransmission timer. However, frequently starting the timer increases the power consumption of the terminal device.

[0052] To solve the above problem, an embodiment of this application provides a DRX configuration method for solving the problem that a terminal device frequently starts a DRX uplink retransmission timer because the terminal device cannot determine in a timely manner whether to start the DRX uplink retransmission timer.

[0053] The DRX configuration method provided in the embodiments of this application may be applied to a system architecture shown in Fig. 6. As shown in Fig. 6, a communication system 10 may include a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (e.g., 110a and 110b, collectively referred to as 110 in Fig. 6) and at least one terminal (e.g., 120a to 120j, collectively referred to as 120 in Fig. 6). The RAN 100 may also include other RAN nodes, such as a wireless relay device and / or a wireless backhaul device (not shown in Fig. 6). The terminal 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 may be different physical devices, or may be the same physical device that integrates the logical functions of the core network and the radio access network.

[0054] The RAN 100 may be a cellular system associated with the 3rd generation partnership project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). Alternatively, the RAN 100 may be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system. Alternatively, the RAN 100 may be a communication system that integrates two or more of the above systems.

[0055] The RAN node 110 may also be referred to as an access network device, RAN entity, access node, etc., and forms part of a communication system to enable terminals to achieve wireless access. The RAN nodes 110 in the communication system 10 may be the same type of node or different types of nodes. In some scenarios, the roles of the RAN node 110 and the terminal 120 are relative. For example, the network element 120i in FIG. 6 may be a helicopter or an unmanned aerial vehicle and may be configured as a mobile base station. For the terminal 120j accessing the RAN 100 by using the network element 120i, the network element 120i is a base station. However, for the base station 110a, the network element 120i is a terminal. The RAN node 110 and the terminal 120 are sometimes referred to as communication devices. For example, the network elements 110a and 110b in FIG. 6 may be understood as communication devices having base station functionality, and the network elements 120a to 120j may be understood as communication devices having terminal functionality.

[0056] In possible scenarios, the RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a 6th generation (6G) mobile communication system, a base station in a future mobile communication system, an access node in a Wi-Fi system, etc. The RAN node may also be a macro base station (e.g., 110a in FIG. 6), a micro base station or an indoor base station (e.g., 110b in FIG. 6), a relay node or a donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node may alternatively be a server, a wearable device, a vehicle, an in-vehicle device, etc. For example, an access network device in a vehicle-to-everything (V2X) technology may be a road side unit (RSU). All or part of the functionality of the RAN node in this application may also be realized by using software functions running on hardware, or by using virtualization functions instantiated on a platform (e.g., a cloud platform). Alternatively, the RAN node in this application may be a logical node, a logical module, or software capable of realizing all or part of the functionality of the RAN node.

[0057] In another possible scenario, multiple RAN nodes cooperate to help terminals achieve radio access, with different RAN nodes separately implementing some functions of a base station. For example, a RAN node may be a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), a radio unit (RU), etc. The CU and DU may be located separately or may be included in the same network element, such as a baseband unit (BBU). The RU may be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0058] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an ORAN system, the CU may also be called an O-CU (open CU), the DU may also be called an O-DU, the CU-CP may also be called an O-CU-CP, the CU-UP may also be called an O-CU-UP, and the RU may also be called an O-RU. For ease of explanation, the CU, CU-CP, CU-UP, DU, and RU are used as examples for explanation in this application. Any one of the CU (or CU-CP or CU-UP), DU, and RU in this application may be realized by using a software module, a hardware module, or a combination thereof.

[0059] A RAN node may also be expressed differently, such as a network device, which will be used for descriptive purposes in this application unless otherwise specified.

[0060] A terminal may also be referred to as a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals may be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, and smart city. A terminal may be a mobile phone, a tablet computer, a computer with wireless transceiver functionality, a wearable device, a vehicle, an unmanned aerial vehicle, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc. The device type of the terminal is not limited in the embodiments of this application.

[0061] It can be understood that in the methods provided in the following embodiments of this application, an example in which a network device and a terminal device function as execution entities of an interaction diagram is used to describe the method. However, the execution entities of the interaction diagram are not limited in this application. For example, the network device in the methods provided in the following embodiments of this application may be a chip, a chip system, or a processor that supports the network device when implementing the method, or may be a logical node, a logical module, or software that can realize all or part of the functions of the network device. Alternatively, the terminal device in the methods provided in the following embodiments of this application may be a chip, a chip system, or a processor that supports the terminal device when implementing the method, or may be a logical node, a logical module, or software that can realize all or part of the functions of the terminal device.

[0062] 7 is a schematic flowchart of a DRX configuration method according to an embodiment of this application. As shown in the drawing, the method may include the following steps:

[0063] Step 701: A terminal device transmits uplink data corresponding to M HARQ processes.

[0064] M is an integer of 1 or greater.

[0065] To support parallel processing of multiple data packets, NR supports multiple HARQ processes. One HARQ process may correspond to one data packet (MAC PDU) or one PUSCH, and MAC PDUs or PUSCHs corresponding to multiple processes may be processed in parallel. Regardless of whether a MAC PDU or PUSCH corresponding to one HARQ process is successfully transmitted, the transmission of MAC PDUs or PUSCHs corresponding to other HARQ processes is not affected. To ensure that HARQ processes do not affect each other, both the HARQ round trip time timer and the HARQ retransmission timer are for each HARQ process. In other words, a network device configures a corresponding HARQ round trip time timer and a corresponding HARQ retransmission timer for each HARQ process. Currently, in NR, there are a maximum of 16 HARQ processes for uplink transmission and a maximum of 16 HARQ processes for downlink transmission.

[0066] Correspondingly, in step 701, the network device (ie, the RAN node mentioned above) receives uplink data corresponding to M HARQ processes.

[0067] The uplink data transmitted by the terminal device may be a configured grant (CG) PUSCH, specifically, the terminal device may transmit the PUSCH on pre-configured resources that can be used to transmit the PUSCH, or the terminal device may transmit the PUSCH on resources of a PUSCH that is dynamically or semi-persistently scheduled by the network device.

[0068] Step 702: The network device sends first indication information to the terminal device, where the first indication information indicates whether to start DRX uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes.

[0069] N is a positive integer less than or equal to M.

[0070] The network device transmits corresponding first indication information depending on whether the uplink data corresponding to the M HARQ processes are correctly received. Specifically, if the network device correctly receives all the uplink data corresponding to the M HARQ processes, the first indication information transmitted by the network device may instruct the terminal device not to start a DRX uplink retransmission timer. If not all the uplink data corresponding to the M HARQ processes are correctly received by the network device, the first indication information transmitted by the network device may instruct the terminal device to start a DRX uplink retransmission timer corresponding to the N HARQ processes, in other words, may indicate to the terminal device that the uplink data corresponding to the N HARQ processes are not correctly received and need to be retransmitted.

[0071] Correspondingly, in step 702, the terminal device receives the first indication information sent by the network device. After sending the uplink data, the terminal device does not need to immediately start monitoring the PDCCH sent by the network device, i.e., does not monitor the first indication information sent by the PDCCH. Because the network device requires a certain period to receive and analyze the uplink data, if the terminal device immediately monitors the PDCCH after sending the uplink data, power consumption will also be incurred.

[0072] Step 703: When the first indication information indicates to start a DRX uplink retransmission timer, the terminal device starts a DRX uplink retransmission timer, and receives second indication information during the operation of the DRX uplink retransmission timer, where the second indication information indicates retransmission of uplink data corresponding to the N HARQ processes.

[0073] In a possible implementation, the length of the DRX uplink retransmission timer started by the terminal device is related to the value of N. The length of the DRX uplink retransmission timer is positively correlated with the value of N. Specifically, a larger value of N indicates a longer length of the DRX uplink retransmission timer. In a specific embodiment, the terminal device may pre-configure a reference length of the DRX uplink retransmission timer. The reference length is the length of the DRX uplink retransmission timer required to retransmit uplink data corresponding to one HARQ process. When the first indication information instructs the terminal device to start DRX uplink retransmission timers corresponding to N HARQ processes, the length of the DRX uplink retransmission timer started by the terminal device is the N reference length. For example, in the scenario shown in FIG. 12, the first indication information indicates that uplink data corresponding to two HARQ processes has not been correctly received, and the terminal device needs to start the DRX uplink retransmission timer, and the length of the DRX uplink retransmission timer is the two reference length.

[0074] The second indication information may be a DCI, and the DCI may include identifiers of HARQ processes that need to be retransmitted and / or retransmission resource indication information. The HARQ process identifiers indicate uplink data that correspond to the HARQ processes and need to be retransmitted by the terminal device. The resource indication information instructs the terminal device to retransmit uplink data corresponding to the HARQ processes on corresponding resources. Optionally, when the first indication information indicates to start DRX uplink retransmission timers corresponding to the N HARQ processes, the network device may send N pieces of second indication information to the terminal device, and the second indication information indicates identifiers of HARQ processes that need to be retransmitted and / or retransmission resource indication information. Alternatively, when the first indication information indicates to start DRX uplink retransmission timers corresponding to the N HARQ processes, the network device may send one piece of second indication information to the terminal device, and the second indication information includes identifiers of the N HARQ processes that need to be retransmitted and / or retransmission resource indication information. After receiving the second indication information, the terminal device may retransmit the uplink data corresponding to the HARQ process indicated by the HARQ process identifier on the retransmission resource indicated by the second indication information to complete the retransmission, thereby enabling the network device to re-receive the uplink data that was not correctly received, thereby realizing service interaction and meeting the user's service requirements.

[0075] The above method procedure may further include step 704. The terminal device skips starting a DRX uplink retransmission timer when the first indication information indicates to skip starting a DRX uplink retransmission timer.

[0076] In step 702, the first indication information sent by the network device may be in multiple forms to indicate to the terminal device whether to start a DRX uplink retransmission timer.

[0077] Format 1: The first indication information sent by the network device may include one bit. The value of the bit indicates whether the uplink data corresponding to the HARQ process is correctly received. If the uplink data corresponding to the HARQ process is not correctly received, this indicates that a retransmission needs to be performed, and the terminal device needs to start a DRX uplink retransmission timer. If the uplink data corresponding to the HARQ process is correctly received, this indicates that a retransmission does not need to be performed, in other words, the terminal device does not need to start a DRX uplink retransmission timer.

[0078] For example, when the bit value is 0, this indicates that all uplink data corresponding to the HARQ process has been correctly received, and the terminal device does not need to start the DRX uplink retransmission timer; alternatively, when the bit value is 1, this indicates that uplink data corresponding to at least one HARQ process has not been correctly received, and the terminal device needs to start the DRX uplink retransmission timer. In FIG. 8(a), an example in which the terminal device transmits one CG PUSCH (corresponding to one HARQ process) within one cycle (e.g., within the duration of one DRX cycle) is used for explanation. In FIG. 8(b), the terminal device may transmit multiple CG PUSCHs within one cycle. If one CG PUSCH is not correctly received and the value of the bit corresponding to the first indication information transmitted by the network device is 1, the terminal device starts the DRX uplink retransmission timer. The network device may specifically indicate the HARQ process that needs to be retransmitted by using the second indication information.

[0079] Format 2: The network device may send M pieces of first indication information, where the first indication information indicates whether uplink data corresponding to the corresponding HARQ process is correctly received. If the first indication information indicates that the uplink data is correctly received, this indicates that retransmission does not need to be performed, in other words, the terminal device does not need to start a DRX uplink retransmission timer. If the first indication information indicates that the uplink data is not correctly received, this indicates that retransmission needs to be performed, in other words, the terminal device needs to start a DRX uplink retransmission timer.

[0080] For example, the terminal device sets different DRX uplink retransmission timers for different HARQ processes, and the i-th first indication information transmitted by the network device indicates whether the uplink data corresponding to the i-th HARQ process has been correctly received. The i-th first indication information may include a 1-bit. If the bit value is 0, this indicates that the network device has correctly received the uplink data corresponding to the i-th HARQ process. In this case, the i-th HARQ process does not need to be retransmitted, and the terminal device does not need to start the DRX uplink retransmission timer corresponding to the i-th HARQ process. If the bit value is 1, this indicates that the network device has not correctly received the uplink data corresponding to the i-th HARQ process. In this case, the i-th HARQ process needs to be retransmitted, and the terminal device starts the DRX uplink retransmission timer corresponding to the i-th HARQ process.

[0081] In another example, the terminal device sets a common DRX uplink retransmission timer for M HARQ processes. The i-th first indication information transmitted by the network device indicates whether uplink data corresponding to the i-th HARQ process has been correctly received. The first indication information may include one bit. If the bit has a value of 0, this indicates that the network device has correctly received the uplink data corresponding to the i-th HARQ process. If the bit has a value of 1, this indicates that the network device has not correctly received the uplink data corresponding to the i-th HARQ process. For the terminal device, if all of the M received first indication information indicate that the uplink data has been correctly received, no HARQ process needs to be retransmitted, and the terminal device does not need to start the DRX uplink retransmission timer. If at least one of the M received first indication information indicates that the uplink data has not been correctly received, this indicates that there is an HARQ process that needs to be retransmitted, and the terminal device needs to start the DRX uplink retransmission timer.

[0082] Format 3: The first indication information sent by the network device may indicate whether to start a DRX uplink retransmission timer corresponding to multiple HARQ processes.

[0083] Optionally, the first indication information transmitted by the network device may include a bitmap. One HARQ process corresponds to one bit in the bitmap. The value of the bit indicates whether uplink data corresponding to the corresponding HARQ process has been correctly received, so as to indicate whether the terminal device needs to start a DRX uplink retransmission timer. Compared with transmitting M pieces of first indication information, this scheme facilitates reducing signaling overhead.

[0084] For example, the terminal device sets different DRX uplink retransmission timers for different HARQ processes. The i-th bit of the bitmap corresponds to the i-th HARQ process. If the value of the i-th bit is 0, this indicates that the network device has correctly received the uplink data corresponding to the i-th HARQ process. In this case, the i-th HARQ process does not need to be retransmitted, and the terminal device does not need to start the DRX uplink retransmission timer corresponding to the i-th HARQ process. If the value of the i-th bit is 1, this indicates that the network device has not correctly received the uplink data corresponding to the i-th HARQ process.

[0085] Currently, there may be 16 HARQ processes in uplink transmission, and the bitmap may include 16 bits. Alternatively, if a future communication system allows more uplink HARQ processes, the bitmap may include more bits. Alternatively, the number of bits included in the bitmap may be equal to M. For example, if there are four HARQ processes, the bitmap may include four bits, which correspond to the first, second, third, and fourth HARQ processes, respectively. If the network device has not received uplink data corresponding to the third HARQ process, the first indication information sent by the network device may be 0010, and the value of the third bit is 1, indicating that the uplink data corresponding to the third HARQ process has not been correctly received, and the terminal device should start the DRX uplink retransmission timer corresponding to the third HARQ process.

[0086] In another example, the terminal device sets a common DRX uplink retransmission timer for M HARQ processes. The i-th bit of the bitmap corresponds to the i-th HARQ process. If the bitmap indicates that all uplink data corresponding to the M HARQ processes has been correctly received, no HARQ process needs to be retransmitted, and the terminal device does not need to start the DRX uplink retransmission timer. If at least one bit in the bitmap indicates that uplink data corresponding to an HARQ process has not been correctly received, this indicates that there is an HARQ process that needs to be retransmitted, and the terminal device needs to start the DRX uplink retransmission timer. As shown in FIG. 9, the uplink data corresponding to the second HARQ process has not been correctly received. Therefore, the value of the second bit in the bitmap is 1, indicating that the terminal device needs to start the DRX uplink retransmission timer.

[0087] Format 4: The first indication information sent by the network device may further indicate information about N, that is, the first indication information may indicate the value of N.

[0088] For example, if there are 16 HARQ processes in the uplink transmission, the 4 bits may indicate the number of HARQ processes among the 16 HARQ processes corresponding to the incorrectly received uplink data. If the network device does not correctly receive uplink data corresponding to two HARQ processes among the 16 HARQ processes, the first indication information sent by the network device may be 0010 (converted to 2 in decimal), indicating that the uplink data corresponding to the two HARQ processes is not correctly received, and the terminal device needs to start the DRX uplink retransmission timer, as shown in FIG. 10.

[0089] Optionally, regardless of which format is used for the first indication information to instruct the terminal device whether to start the DRX uplink retransmission timer, the first indication information may be carried in a WUS, or may be carried in a low power-wake-up signal (LP-WUS), or may be carried in a DFI and sent to the terminal device.

[0090] The start time at which the terminal device monitors the first indication information, i.e., the start time at which the network device sends the first indication information, may be determined in any one of the following manners.

[0091] Scheme 1: After transmitting uplink data corresponding to the HARQ process, the terminal device may start a DRX uplink HARQ round trip time timer. After the DRX uplink HARQ round trip time timer ends or expires, the terminal device may start monitoring the first indication information sent by the network device. In other words, the time length T1 in FIG. 11(a) or 11(b) is the time length of the DRX uplink HARQ round trip time timer. The time period of the DRX uplink HARQ round trip time timer is used to wait for the network device to receive and analyze the uplink data. During the time period of the DRX uplink HARQ round trip time timer, the terminal device does not need to monitor the PDCCH sent by the network device, which reduces the power consumption of the terminal device.

[0092] When the network device transmits one common first indication information for the M HARQ processes, the terminal device may start a DRX uplink HARQ round trip time timer after transmitting uplink data corresponding to the last HARQ process. When the network device transmits one first indication information for each HARQ process, the terminal device may start a DRX uplink HARQ round trip time timer corresponding to the HARQ process after transmitting uplink data corresponding to one HARQ process.

[0093] Scheme 2: After transmitting uplink data corresponding to the HARQ process, the terminal device starts to monitor the first indication information transmitted by the network device after a first time period. The first time period, i.e., the time period T1 shown in Figure 11(a) or 11(b), is used for the network device to wait for receiving and analyzing the uplink data. During the first time period, the terminal device does not need to monitor the PDCCH transmitted by the network device, which reduces the power consumption of the terminal device.

[0094] The first time length may be a downlink feedback indicator (DFI) delay time length (cg-minDFI-Delay). The cg-minDFI-Delay is an existing field in current communication systems and indicates the minimum duration (in symbols) from the end symbol of the PUSCH to the start symbol of the PDCCH. The PDCCH includes the first indication information.

[0095] Alternatively, the first length of time may be indicated by defining a new field. For example, a new field HARQ-feedback-delay (HARQ-feedback-delay) may be configured in RRC signaling to indicate the length of the first length of time, and the first length of time indicated by the field may indicate not only the first length of time corresponding to a dynamically or semi-persistently scheduled PUSCH but also the first length of time corresponding to a CG PUSCH.

[0096] When the network device transmits one common first indication information for the M HARQ processes, the terminal device may start to monitor the first indication information transmitted by the network device after a first length of time after transmitting uplink data corresponding to the last HARQ process. When the network device transmits one first indication information for each HARQ process, the terminal device may start to monitor the first indication information corresponding to the HARQ process and transmitted by the network device after a first length of time after transmitting uplink data corresponding to one HARQ process.

[0097] Method 3: The start time at which the terminal device monitors the first indication information may alternatively be a point in time that is a second length of time before the terminal device starts the DRX uplink retransmission timer.

[0098] As shown in Figure 11(c) or 11(d), if the terminal device needs to start the DRX uplink retransmission timer after transmitting the PUSCH, the terminal device needs to start the DRX uplink retransmission timer at time t2. In this case, the terminal device may start monitoring the first indication information at time t1 = t2 - T1, where T1 represents the second time length. Optionally, the second time length may be pre-configured in the protocol or configured by the network device. Alternatively, the second time length may be the time length of the DRX uplink HARQ round trip period timer or the time length indicated by cg-minDFI-Delay.

[0099] If the terminal device configures a common DRX uplink retransmission timer for the M HARQ processes, the second length of time may be subtracted from the time at which the common DRX uplink retransmission timer is started, and the terminal device may start to monitor the first indication information at the corresponding time. If the terminal device configures different DRX uplink retransmission timers for different HARQ processes, the second length of time is subtracted from the time at which the DRX uplink retransmission timer is started, and the terminal device starts to monitor the first indication information corresponding to the HARQ process at the corresponding time.

[0100] The above describes a method for determining the start time for the terminal device to monitor the first indication information. The following describes a method for determining the end time for the terminal device to monitor the first indication information.

[0101] In a possible implementation, the terminal device may determine an end time for monitoring the first indication information based on a third length of time. Specifically, the time reached after the third length of time has elapsed since the start time for monitoring the first indication information is the time at which the terminal device stops monitoring the first indication information. For example, T2 in FIG. 11(b) or FIG. 11(b) represents the third length of time. The third length of time may be preconfigured in the terminal device or may be configured by the network device. In this case, the network device needs to transmit the first indication information to the terminal device after the start time begins and before the third length of time is reached. The terminal device monitors the first indication information when the third length of time is reached after the start time begins. After the third length of time is reached, the terminal device no longer monitors the first indication information. If the terminal device receives the first indication information transmitted by the network device before the third length of time is reached, the terminal device no longer needs to continue monitoring the first indication information and determine whether to start the DRX uplink retransmission timer based on the first indication information.

[0102] In another possible implementation manner, the terminal device may alternatively determine the end time of monitoring the first indication information based on a minimum offset. The minimum offset indicates that the terminal device stops monitoring the first indication information at the minimum offset before starting the DRX uplink retransmission timer. If the terminal device receives the first indication information at a time smaller than the minimum offset before the DRX uplink retransmission timer starts, the terminal device may not start the DRX uplink retransmission timer in a timely manner, resulting in a failure to receive the second indication information. Therefore, the network device needs to transmit the first indication information to the terminal device before the minimum offset before the terminal device starts the DRX uplink retransmission timer, and the terminal device stops monitoring the first indication information at the minimum offset before the terminal device starts the DRX uplink retransmission timer. For example, T2 in FIG. 11(a) or 11(d) represents the minimum offset. If the terminal device receives the first indication information sent by the network device before the minimum offset point before the terminal device starts the DRX uplink retransmission timer, the terminal device no longer needs to continue monitoring the first indication information and determine whether to start the DRX uplink retransmission timer based on the first indication information.

[0103] When the terminal device determines to start the DRX uplink retransmission timer based on the received first indication information, the terminal device monitors second indication information transmitted by the network device during operation of the DRX uplink retransmission timer. As described above, the terminal device may set a corresponding DRX uplink retransmission timer for each HARQ process. In this case, the terminal device monitors second indication information transmitted by the network device for the HARQ process corresponding to the DRX uplink retransmission timer during timing of the DRX uplink retransmission timer. Alternatively, the terminal device may set a common DRX uplink retransmission timer for M HARQ processes. In this case, the terminal device monitors second indication information transmitted by the network device during timing of the common DRX uplink retransmission timer. The second indication information may include N pieces of second indication information, and the second indication information may indicate retransmission of uplink data corresponding to the corresponding HARQ process, or one piece of second indication information may indicate retransmission of uplink data corresponding to the N HARQ processes.

[0104] When the terminal device sets a corresponding DRX uplink retransmission timer for each HARQ process, the terminal device monitors second indication information sent by the network device for the HARQ process during the operation of the DRX uplink retransmission timer. If the terminal device receives the second indication information for the HARQ process during the operation process of the DRX uplink retransmission timer, the terminal device may immediately stop the DRX uplink retransmission timer for the HARQ process regardless of whether the DRX uplink retransmission timer expires.

[0105] When the terminal device sets a common DRX uplink retransmission timer for M HARQ processes and the network device transmits N pieces of second indication information for the N HARQ processes, the terminal device monitors the N pieces of second indication information transmitted by the network device during operation of the common DRX uplink retransmission timer. When the terminal device receives the N pieces of second indication information during the operation process of the common DRX uplink retransmission timer, the terminal device may immediately stop the DRX uplink retransmission timer regardless of whether the DRX uplink retransmission timer has expired.

[0106] When the terminal device sets a common DRX uplink retransmission timer for M HARQ processes and the network device transmits one second indication information for N HARQ processes, the terminal device monitors the one second indication information transmitted by the network device during operation of the common DRX uplink retransmission timer. When the terminal device receives the one second indication information during the operation process of the common DRX uplink retransmission timer, the terminal device may immediately stop the DRX uplink retransmission timer regardless of whether the DRX uplink retransmission timer has expired.

[0107] In the DRX configuration method provided in the above embodiments of this application, the network device notifies the terminal device in a timely manner whether to start the DRX uplink retransmission timer by using the first indication information. Therefore, the terminal device can timely determine whether to start the DRX uplink retransmission timer based on the first indication information. When there is uplink data corresponding to the HARQ process that needs to be retransmitted, the terminal device starts the DRX uplink retransmission timer. When there is no uplink data corresponding to the HARQ process that needs to be retransmitted, the terminal device does not need to start the DRX uplink retransmission timer, thereby reducing the power consumption of the terminal device.

[0108] Based on the same technical concept, an embodiment of this application further provides a communication device, including a module / unit for implementing the terminal device in the above method embodiment. The device may be a terminal device, or a component of the terminal device (e.g., a processor, a chip, or a chip system), or a logical node, logical module, or software that can implement all or part of the functions of the terminal device. These modules / units may be implemented by hardware, or may be implemented by hardware executing corresponding software.

[0109] 13, a communication device may include an interface module 1301 and a processing module 1302. The interface module 1301 is configured to receive and transmit messages, and the processing module 1302 is configured to implement message processing by the communication device. In this embodiment of the present application, it should be understood that the processing module 1302 may be implemented by a processor or a processor-related circuit component (also referred to as a processing circuit). The interface module 1301 may be implemented by a transceiver or a transceiver-related circuit component.

[0110] Specifically, the interface module 1301 is configured to transmit uplink data corresponding to M HARQ processes, where M is an integer greater than or equal to 1. The interface module 1301 is further configured to receive first indication information, where the first indication information indicates whether to start DRX uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M. The processing module 1302 is configured to start the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer, and when the DRX uplink retransmission timer runs, the interface module 1301 is further configured to receive second indication information, where the second indication information indicates retransmission of uplink data corresponding to the N HARQ processes.

[0111] In addition, the above modules may be further configured to support other processes executed by the terminal device in the embodiments shown in Figures 7 to 12. For beneficial effects, please refer to the above description. Details will not be described again in this specification.

[0112] Based on the same technical concept, an embodiment of this application further provides a communication device, including a module / unit for implementing the network device in the above method embodiment. The device may be a network device, or a component of a network device (e.g., a processor, a chip, or a chip system), or a logical node, logical module, or software that can implement all or part of the functions of the network device. These modules / units may be implemented by hardware, or may be implemented by hardware executing corresponding software.

[0113] 14, a communication device may include an interface module 1401 and a processing module 1402. The interface module 1401 is configured to receive and transmit messages, and the processing module 1402 is configured to implement message processing by the communication device. In this embodiment of the present application, it should be understood that the processing module 1402 may be implemented by a processor or a processor-related circuit component (also referred to as a processing circuit). The interface module 1401 may be implemented by a transceiver or a transceiver-related circuit component.

[0114] Specifically, the interface module 1401 is configured to receive uplink data corresponding to M HARQ processes, where M is an integer greater than or equal to 1. The interface module 1401 is further configured to send first indication information, where the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M. If the first indication information indicates to start the DRX uplink retransmission timer, the processing module 1402 is configured to start the DRX uplink retransmission timer, and the interface module 1401 is further configured to send second indication information when the DRX uplink retransmission timer runs, where the second indication information indicates retransmission of the uplink data corresponding to the N HARQ processes.

[0115] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

[0116] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to multiple HARQ processes.

[0117] In a possible implementation, multiple HARQ processes correspond to one DRX uplink retransmission timer.

[0118] In a possible implementation, multiple HARQ processes correspond to multiple DRX uplink retransmission timers, respectively.

[0119] In a possible implementation, the first indication information includes information indicating N.

[0120] In a possible implementation, the duration of the DRX uplink retransmission timer is related to N.

[0121] In a possible implementation manner, when sending the first indication information, the interface module 1401 is specifically configured to send the first indication information from a first time point, where the first time point is one of the following: a time point that is a first time length after the end of the transmission of uplink data, where the first time length is a downlink feedback information DFI delay time length, or an expiration time of an uplink HARQ round trip time timer.

[0122] In a possible implementation, the first indication information is carried in the wake-up signal WUS, or the first indication information is carried in the low-power WUS, or the first indication information is included in the DFI.

[0123] In addition, the above modules may be further configured to support other processes executed by the terminal device in the embodiments shown in Figures 7 to 12. For beneficial effects, please refer to the above description. Details will not be described again in this specification.

[0124] Based on the same technical concept, an embodiment of this application further provides a communication device, which includes a processor 1501 shown in Figure 15, and the processor 1501 is coupled to a memory 1502. In addition, the communication device may further include a communication interface 1503 and a communication bus 1504.

[0125] The processor 1501 may be a general-purpose processor, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, one or more integrated circuits configured to control program execution of the solutions in this application, etc. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of this application may be performed directly by a hardware processor or may be performed by using a combination of hardware and software modules in a processor.

[0126] The memory 1502 is configured to store program instructions and / or data such that the processor 1501 can access the instructions and / or data stored in the memory 1502 to implement the above-described functions of the processor 1501. The memory 1502 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, a random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or an electrically erasable programmable read-only memory (EEPROM), or any other medium usable to carry or store program code in the form of instructions or data structures and accessible by a computer. The memory 1502 may exist independently, e.g., as an off-chip memory, and be connected to the processor 1501 via a communication bus 1504. Alternatively, the memory 1502 may be integrated with the processor 1501.

[0127] The communication interface 1503 uses any device such as a transceiver to communicate with other devices or communication networks such as Ethernet, a radio access network (RAN) or a wireless local area network (WLAN). In this embodiment of the application, the processor 1501 is configured to invoke the communication interface 1503 to perform receiving and / or transmitting functions and to execute a method according to any one of the possible implementations described above.

[0128] The communication bus 1504 may include a path for transmitting information between the above components.

[0129] For example, the communication device may be a terminal device in the above method embodiments, or a component of the terminal device (e.g., a processor, a chip, or a chip system), or a logical node, logical module, or software capable of realizing all or part of the functions of the terminal device. Alternatively, the communication device may be a network device in the above method embodiments, or a component of the network device (e.g., a processor, a chip, or a chip system), or a logical node, logical module, or software capable of realizing all or part of the functions of the network device.

[0130] When the communication device is a terminal device, the processor 1501 is configured to perform the following steps: transmitting, through the communication interface 1503, uplink data corresponding to M hybrid automatic repeat request (HARQ) processes, where M is an integer greater than or equal to 1; receiving, through the communication interface 1503, first indication information, the first indication information indicating whether to start a discontinuous reception (DRX) uplink retransmission timer corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; starting the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer; and receiving, through the communication interface 1503, second indication information, the second indication information indicating a retransmission of the uplink data corresponding to the N HARQ processes when the DRX uplink retransmission timer runs.

[0131] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

[0132] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to multiple HARQ processes.

[0133] In a possible implementation, multiple HARQ processes correspond to one DRX uplink retransmission timer.

[0134] In a possible implementation, multiple HARQ processes correspond to multiple DRX uplink retransmission timers, respectively.

[0135] In a possible implementation, the first indication information includes information indicating N.

[0136] In a possible implementation, the duration of the DRX uplink retransmission timer is related to N.

[0137] In a possible implementation manner, when receiving first indication information through the communication interface 1503, the processor 1503 is specifically configured to receive the first indication information from a first time point through the communication interface 1503, where the first time point is one of the following: a time point that is a first time length after the end of the transmission of uplink data, where the first time length is a downlink feedback information DFI delay time length; or the first time length is configured by a network device, for example, the network adds a new parameter in control signaling to configure the first time length, or configures a new timer, where the timing length of the new timer is the first time length; or the expiration time of an uplink HARQ round trip time timer.

[0138] In a possible implementation manner, after receiving the second indication information, the processor 1501 is further configured to stop operating the DRX uplink retransmission timer.

[0139] In a possible implementation manner, the processor 1501 is further configured to skip starting the DRX uplink retransmission timer when the first indication information indicates to skip starting the DRX uplink retransmission timer.

[0140] In a possible implementation, the first indication information is carried in the wake-up signal WUS, or the first indication information is carried in the low-power WUS, or the first indication information is included in the DFI.

[0141] When the communication device is a network device, the processor 1501 is configured to perform the following steps: receiving, through the communication interface 1503, uplink data corresponding to M hybrid automatic repeat request (HARQ) processes, where M is an integer greater than or equal to 1; sending, through the communication interface 1503, first instruction information, the first instruction information indicating whether to start discontinuous reception (DRX) uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; starting the DRX uplink retransmission timer when the first instruction information indicates to start the DRX uplink retransmission timer; and sending, through the communication interface 1503, second instruction information, the second instruction information indicating retransmission of uplink data corresponding to the N HARQ processes.

[0142] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

[0143] In a possible implementation, the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to multiple HARQ processes.

[0144] In a possible implementation, multiple HARQ processes correspond to one DRX uplink retransmission timer.

[0145] In a possible implementation, multiple HARQ processes correspond to multiple DRX uplink retransmission timers, respectively.

[0146] In a possible implementation, the first indication information includes information indicating N.

[0147] In a possible implementation, the duration of the DRX uplink retransmission timer is related to N.

[0148] In a possible implementation manner, when sending the first indication information through the communication interface 1503, the processor 1503 is specifically configured to send the first indication information from a first time point, where the first time point is one of the following: a time point that is a first time length after the end of the transmission of uplink data, where the first time length is a downlink feedback information DFI delay time length, or an expiration time point of an uplink HARQ round trip time timer.

[0149] In a possible implementation, the first indication information is carried in the wake-up signal WUS, or the first indication information is carried in the low-power WUS, or the first indication information is included in the DFI.

[0150] Based on the same technical concept, an embodiment of this application further provides a computer-readable storage medium, which stores computer-readable instructions, and when the computer-readable instructions run on a computer, performs a method according to any one of the above possible implementations.

[0151] An embodiment of this application provides a computer program product including instructions that, when run on a computer, perform the method embodiments.

[0152] In this embodiment of this application, "sending information to ... (terminal)" may be understood as the destination end of the information being the terminal, and may include directly or indirectly sending information to the terminal. "receiving information from ... (terminal)" may be understood as the source end of the information being the terminal, and may include directly or indirectly receiving information from the terminal. The information may be processed between the information source end and the destination end, for example, format change. However, the destination end may understand the valid information from the source end. Similar descriptions in this application may be understood in the same way, and details will not be described again.

[0153] In the description of the embodiments of this application, the term "and / or" describes an association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may indicate the following three cases: only A exists, both A and B exist, and only B exists. In this application, "plurality" means two or more.

[0154] Furthermore, in the description of this application, terms such as "first" and "second" are used merely for distinction and description purposes, and should not be understood as indicating or implying relative importance or any ordering. References to "an embodiment," "some embodiments," and the like in this specification indicate that one or more embodiments of this application include the particular feature, structure, or characteristic described with reference to the embodiment. Thus, phrases such as "in an embodiment," "in some embodiments," "in some other embodiments," and "in other embodiments" appearing in different places in this specification are not necessarily meant to refer to the same embodiment. Instead, these phrases mean "one or more, but not all, of the embodiments" unless specifically emphasized otherwise. The terms "including," "having," and variations thereof all mean "including, but not limited to," unless specifically emphasized otherwise.

[0155] The steps of the method in the embodiments of this application may be implemented in a hardware manner or may be implemented in a manner in which a processor executes software instructions. The software instructions may include corresponding software modules. The software modules may be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk drive, a removable hard disk drive, a CD-ROM, or any other form of storage medium known in the art. For example, the storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium. Obviously, the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. Furthermore, the ASIC may be located in a base station or a terminal. Obviously, the processor and the storage medium may reside as separate components in the base station or the terminal.

[0156] All or part of the above embodiments may be realized by using software, hardware, firmware, or any combination thereof. When software is used to realize the above embodiments, all or part of the above embodiments may be realized in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, all or part of the procedures or functions in the embodiments of this application are executed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, user equipment, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via a wired or wireless method. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or data center. The available media may be magnetic media, such as floppy disks, hard disk drives, or magnetic tape, or optical media, such as digital video disks, or semiconductor media, such as solid-state drives. The computer-readable storage media may be volatile or non-volatile storage media, or may include both types of storage media: volatile and non-volatile storage media.

[0157] In various embodiments of this application, unless otherwise specified or unless there is a logical conflict, the terms and / or descriptions in different embodiments are consistent and may be cross-referenced, and the technical features in different embodiments may be combined based on their internal logical relationships to form new embodiments.

[0158] It can be understood that various numbers in the embodiments of this application are used for distinction only to facilitate description, and are not used to limit the scope of the embodiments of this application. The sequence numbers of the above processes do not imply an execution order, and the execution order of the processes should be determined based on the functions and internal logic of the processes.

Claims

1. 1. A communication method comprising: transmitting uplink data corresponding to M Hybrid Automatic Repeat Request (HARQ) processes, where M is an integer greater than or equal to 1; receiving first indication information, the first indication information indicating whether to start discontinuous reception (DRX) uplink retransmission timers corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; starting the DRX uplink retransmission timer when the first indication information indicates to start the DRX uplink retransmission timer, and receiving second indication information when the DRX uplink retransmission timer runs, the second indication information indicating retransmission of uplink data corresponding to the N HARQ processes; A method comprising:

2. The method of claim 1 , wherein the first indication indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

3. The method of claim 1 , wherein the first indication indicates whether to start a DRX uplink retransmission timer corresponding to a plurality of HARQ processes.

4. The method of claim 3 , wherein the plurality of HARQ processes correspond to one DRX uplink retransmission timer.

5. The method of claim 3 , wherein the plurality of HARQ processes correspond to a plurality of DRX uplink retransmission timers, respectively.

6. The method according to claim 1 , wherein the first indication information includes information indicating N.

7. The method according to claim 1 , wherein the DRX uplink retransmission timer has a counting time length related to N.

8. The step of receiving the first instruction information includes: receiving the first indication from a first time point; The first time point may be: a time point a first length of time after the end of transmission of the uplink data, the first length of time being a downlink feedback information (DFI) delay time length; or Uplink HARQ round trip timer expiration time 8. The method according to claim 1, wherein the method is one of the following:

9. After receiving the second instruction information, The method according to claim 1 , further comprising the step of stopping the DRX uplink retransmission timer from running.

10. 10. The method according to claim 1, further comprising: skipping starting the DRX uplink retransmission timer when the first indication indicates to skip starting the DRX uplink retransmission timer.

11. The first indication information is carried in a wake-up signal (WUS), or the first indication is carried in a low-power WUS; or The method according to claim 1 , wherein the first indication is included in a DFI.

12. A communication device, an interface module configured to transmit uplink data corresponding to M Hybrid Automatic Repeat Request (HARQ) processes, where M is an integer greater than or equal to 1; the interface module is further configured to receive first indication information, the first indication information indicating whether to start a discontinuous reception (DRX) uplink retransmission timer corresponding to N HARQ processes among the M HARQ processes, where N is a positive integer less than or equal to M; a processing module configured to start the DRX uplink retransmission timer when the first indication indicates that the DRX uplink retransmission timer is to be started; Including, When the DRX uplink retransmission timer runs, the interface module is further configured to receive second indication information, the second indication information indicating retransmission of uplink data corresponding to the N HARQ processes.

13. The apparatus of claim 12 , wherein the first indication indicates whether to start a DRX uplink retransmission timer corresponding to one HARQ process.

14. The apparatus of claim 12 , wherein the first indication indicates whether to start a DRX uplink retransmission timer corresponding to a plurality of HARQ processes.

15. The apparatus of claim 14 , wherein the plurality of HARQ processes correspond to one DRX uplink retransmission timer.

16. The apparatus of claim 14 , wherein the plurality of HARQ processes correspond to a plurality of DRX uplink retransmission timers, respectively.

17. The apparatus according to claim 12 , wherein the first indication information includes information indicating N.

18. 18. The apparatus according to claim 12, wherein the DRX uplink retransmission timer has a counting time length related to N.

19. When receiving the first indication information, the interface module: specifically configured to receive the first indication from a first time point; The first time point may be: a time point a first length of time after the end of transmission of the uplink data, the first length of time being a downlink feedback information (DFI) delay time length; or Uplink HARQ round trip timer expiration time 19. The device according to any one of claims 12 to 18, wherein the device is one of:

20. After the interface module receives the second instruction information, the processing module:

20. The apparatus of claim 12, further configured to stop running the DRX uplink retransmission timer.

21. The processing module includes:

21. The apparatus of claim 12, further configured to: skip starting the DRX uplink retransmission timer when the first indication information indicates to skip starting the DRX uplink retransmission timer.

22. The first indication information is carried in a wake-up signal (WUS), or the first indication is carried in a low-power WUS; or 22. The device according to claim 12, wherein the first indication is included in a DFI.

23. 1. A communications device including a processor, 12. A communications device, wherein the processor is coupled to a memory, the memory configured to store a program or instructions that, when executed by the processor, enable the device to perform the method of any one of claims 1 to 11.

24. 1. A computer-readable storage medium, comprising:

12. A computer readable storage medium storing instructions that, when executed on a computer, enable the computer to perform the method of any one of claims 1 to 11.

25. 1. A computer program product comprising instructions, A computer program product, the instructions of which, when executed on a computer, enable the computer to carry out the method of any one of claims 1 to 11.

Images