Communication methods, devices and apparatus

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, titled "DISCONTINUOUS RECEPTION DRX CONFIGURATION METHOD AND APPARATUS, AND DEVICE", filed with the China National Intellectual Property Administration on December 30, 2022, the entire content of which is incorporated herein by reference.

[0002] [Technical Field] This application relates to the field of wireless communication, and in particular, to communication methods, apparatuses, and devices.

Background Art

[0003] In recent years, with the continuous development of the 5th generation (5G) communication system, data transmission delay has been continuously reduced, and the transmission capacity has become increasingly large. The 5G communication system is gradually being introduced into some 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 increase rapidly, 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 actively. VR, as a type of XR, is entering various fields closely related to people's production and lives, such as education, entertainment, military, medicine, environmental protection, transportation, and public health. Compared to conventional video services, VR offers users a new visual experience with multiple field of view, strong interaction, and other advantages. In addition to smartphones, people may also use terminal devices such as head-mounted displays (HMDs) or smart glasses (VR glasses and AR glasses, etc.) to enhance their XR experience.

[0005] However, regarding uplink data, network devices do not provide feedback to terminal devices with acknowledgment / negative acknowledgment (ACK / NACK). Therefore, terminal devices cannot decide whether or not to start a discontinuous reception (DRX) uplink retransmission timer to perform retransmission. [Overview of the Initiative]

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

[0007] According to a first aspect, an embodiment of the present application provides a communication method which may be performed by a terminal device, by a component of the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of the terminal device. The method includes the steps of: transmitting uplink data corresponding to M hybrid automatic retransmission request HARQ processes, where M is an integer greater than or equal to 1; receiving first instruction information, where the first instruction information indicates whether to start an intermittent receive DRX uplink retransmission timer corresponding to N of 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 receiving second instruction information when the DRX uplink retransmission timer is operating, where the second instruction information indicates the retransmission of uplink data corresponding to 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 or not to start the DRX uplink retransmission timer by using first instruction information. Thus, the terminal device can decide in a timely manner whether or not to start the DRX uplink retransmission timer based on the first instruction information. When there is uplink data corresponding to a HARQ process that needs to be retransmitted, the terminal device starts the DRX uplink retransmission timer. When there is no uplink data corresponding to a 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 instruction indicates whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process. In this implementation, the first instruction may also indicate whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process. A network device may use M first instruction pieces to indicate whether or not to start the DRX uplink retransmission timers corresponding to M HARQ processes, thereby enabling terminal devices to timely determine which DRX uplink retransmission timers correspond to the HARQ processes that should be started.

[0010] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes. In this implementation, the first instruction may also indicate whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes. For example, the first instruction may indicate whether or not to start the DRX uplink retransmission timers corresponding to M HARQ processes, which facilitates a reduction in signaling overhead.

[0011] In possible implementations, multiple HARQ processes correspond to a single DRX uplink retransmission timer. A terminal device may provide a single DRX uplink retransmission timer for multiple HARQ processes, simplifying the operation of the terminal device and facilitating a reduction in the terminal device's power consumption.

[0012] In a possible implementation, multiple HARQ processes correspond to multiple DRX uplink retransmission timers. A terminal device may provide a corresponding DRX uplink retransmission timer for each HARQ process and monitor a second instruction information corresponding to each HARQ process during the operation of each timer, thereby enabling the terminal device to determine which HARQ process corresponds to the second instruction information.

[0013] In a possible implementation, the first instruction information includes information indicating N. The first instruction information includes information indicating N, which in turn enables the terminal device to 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 possible implementations, the timing time of the DRX uplink retransmission timer is related to N. In these implementations, a larger value of N indicates a longer timing time of the DRX uplink retransmission timer, i.e., a longer maximum time for the terminal device to monitor the second instruction information. This helps the network device to perform scheduling and also helps the terminal device to fully receive the second instruction information transmitted by the network device.

[0015] In possible implementations, the step of receiving the first instruction information includes the step of receiving the first instruction information from a first time point in time, where the first time point is one of the following: a time point after a first time length from the end of transmission of uplink data, where the first time length is the downlink feedback information DFI delay time length, or a time point configured by a network device, for example, the network adding a new parameter in control signaling to configure the first time length, or configuring a new timer, the timing length of the new timer being the first time length, or the expiration of the uplink HARQ round trip time timer. After transmitting uplink data, the terminal device may wait for a period of time, then begin monitoring the first instruction 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 instruction information transmitted by the network device, reducing the terminal device's power consumption.

[0016] In possible implementations, after receiving the second instruction information, the method further includes the step of stopping the operation of the DRX uplink retransmission timer. After receiving the second instruction information, the terminal device stops operating the DRX uplink retransmission timer, i.e., no longer monitors the second instruction information transmitted by the network device, thereby reducing the power consumption of the terminal device.

[0017] In a possible implementation, the method further includes the step of skipping the initiation of the DRX uplink retransmission timer when the first instruction indicates that the initiation of the DRX uplink retransmission timer should be skipped. When the first instruction indicates that the initiation of the DRX uplink retransmission timer should be skipped, it indicates that there are no HARQ processes that need to be retransmitted. In this case, the network device skips initiating the DRX uplink retransmission timer and skips monitoring the second instruction to reduce power consumption of the terminal device.

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

[0019] According to a second aspect, embodiments of the present application provide a communication method which may be performed by a network device, by a component of the network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of the network device. The method includes the steps of: receiving uplink data corresponding to M hybrid automatic retransmission request HARQ processes, where M is an integer of 1 or more; transmitting first instruction information, where the first instruction information indicates whether or not to start an intermittent receive DRX uplink retransmission timer corresponding to N of 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 transmitting second instruction information when the DRX uplink retransmission timer is operating, where the second instruction information indicates the retransmission of uplink data corresponding to N HARQ processes.

[0020] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process.

[0021] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes.

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

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

[0024] In possible implementations, the first instruction information includes information indicating N.

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

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

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

[0028] According to a third aspect, an embodiment of this application provides a communication device. The communication device includes a module / unit for executing a method according to any one of the first aspect or the possible implementation manners of the first aspect. The device may be a terminal device, or a component of the terminal device (such as a processor, a chip, or a chip system), or a logical node, a 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 that executes the 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, and the first indication information indicates whether to start a DRX uplink retransmission timer corresponding to N of the M HARQ processes, where N is a positive integer less than or equal to M. When the first indication information indicates to start the DRX uplink retransmission timer, the processing module is configured to start the DRX uplink retransmission timer. When the DRX uplink retransmission timer is operating, the interface module is further configured to receive second indication information, and 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 this application provides a communication device. The communication device includes modules / units for executing a method according to any one of the second aspect or possible implementation manners of the second aspect. The device may be a network device, or a component of a network device (such as 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 a network device. These modules / units may be realized by hardware, or may be realized 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 transmit first instruction information, which indicates whether or not to start a DRX uplink retransmission timer corresponding to N of the M HARQ processes, where N is a positive integer less than or equal to M. If the first instruction 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 transmit second instruction information when the DRX uplink retransmission timer is operating, which indicates the retransmission of uplink data corresponding to N HARQ processes.

[0032] According to a fifth aspect, an embodiment of the present application provides a communication device, the device including a processor coupled to memory, the memory configured to store a program or instruction, and when the program or instruction is executed by the processor, the communication device becomes capable of performing a method according to the first aspect or any possible implementation of the first aspect. The device 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 implementing all or part of the functions of a terminal device.

[0033] According to a sixth aspect, an embodiment of the present application provides a communication device, the device including a processor coupled to memory, the memory configured to store a program or instruction, and when the program or instruction is executed by the processor, the communication device becomes capable of performing a method according to the second aspect or any one of the possible implementations of the second aspect. 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 capable of implementing all or part of the functions of a network device.

[0034] According to a seventh aspect, an embodiment of the present application provides a computer-readable storage medium that stores instructions. When the instructions are executed on a computer, the computer is able to perform a method according to either the first aspect or an implementation of the first aspect, or a method according to either the second aspect or an implementation of the second aspect.

[0035] According to the eighth aspect, an embodiment of the present application provides a computer program product including instructions. When the instructions are executed on a computer, the computer is able to perform a method according to either the first aspect or the implementation of the first aspect, or a method according to either the second aspect or the implementation of the second aspect.

[0036] According to the ninth aspect, an embodiment of the present application provides a chip including a processor. The processor is coupled to memory. The memory is configured to store instructions. When instructions are executed by the processor, the chip becomes capable of implementing a method according to 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 the tenth aspect, an embodiment of this application provides a communication system including an apparatus according to the third aspect and an apparatus according to the fourth aspect.

[0038] According to the eleventh aspect, an embodiment of this 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 the second to eleventh aspects, refer to the description of the technical effects that can be achieved in the corresponding implementation solution in the first aspect. Repeating parts are not described herein. [Brief explanation of the drawing]

[0040] [Figure 1] This is a diagram showing the transmission rate of image frames. [Figure 2] This is a diagram of the DRX cycle. [Figure 3] This is a diagram of the short DRX cycle and the long DRX cycle. [Figure 4] This is a diagram of DRX downlink retransmission. [Figure 5] This diagram shows how terminal devices monitor WUS. [Figure 6] This is a diagram of the system architecture according to an embodiment of this application. [Figure 7] This is a schematic flowchart of the DRX configuration method according to the embodiment of this application. [Figure 8(a)] This is a diagram of one type of first instruction information according to an embodiment of this application. [Figure 8(b)] This is a diagram of one type of first instruction information according to an embodiment of this application. [Figure 9] This is a diagram of another type of first instruction information according to an embodiment of this application. [Figure 10] This is a diagram of yet another type of first instruction information according to an embodiment of this application. [Figure 11(a)] This is a diagram of the period for monitoring the first instruction information according to an embodiment of this application. [Figure 11(b)]This is a diagram of the period for monitoring the first instruction information according to an embodiment of this application. [Figure 11(c)] This is a diagram of the period for monitoring the first instruction information according to an embodiment of this application. [Figure 11(d)] This is a diagram of the period for monitoring the first instruction information according to an embodiment of this application. [Figure 12] This diagram shows the timing time length of the DRX uplink retransmission timer according to an embodiment of this application. [Figure 13] This is a diagram showing the structure of a communication device according to an embodiment of this application. [Figure 14] This is a diagram showing the structure of another communication device according to an embodiment of this application. [Figure 15] This is a diagram showing the structure of yet another communication device according to an embodiment of this application. [Modes for carrying out the invention]

[0041] The service model for XR transmission and video transmission services typically involves the periodic transmission of uplink and downlink data based on the frame rate. As shown in Figure 1, ideally, one frame of image is transmitted every 16.67 milliseconds for video with a frame rate of 60 frames per second (FPS). Furthermore, the amount of data in XR transmission and video services is usually large. For example, the size of a 4K video frame is approximately 30KB to 100KB. Moreover, the size of different video frames usually varies. Since different video frames have different compression ratios and different frame types, the size of different video frames also varies considerably.

[0042] Different XR services have different uplink and downlink service models. Changes in the display of VR scene content are caused by changes in the attitude or position of the terminal device. Therefore, the uplink transmission of data for VR services is primarily for positional and attitudeal information, which typically has small amounts of data, usually only tens of kilobits per second (kbps). Downlink transmission is primarily for rendered video streams, which have large amounts of data, potentially reaching tens to hundreds of Mbps. Unlike VR, changes in the display of AR scene content are caused by changes in the gaze focus target and changes in the spatial relationship (action) between position and gaze point. Uplink transmission includes visual information necessary for perception (including depth information, etc.). Therefore, the uplink transmission of data for AR services is primarily for clear and stable image or video streams with large amounts of data. Alternatively, the uplink transmission of data may also be for environmental feature information. Based on industry research and evaluation, the network uplink rate required for initial experiences of interactive AR services is approximately 2 Mbit / s, while the network uplink rate required for advanced experiences is 10 Mbit / s to 20 Mbit / s. Compared to cloud VR, cloud AR has higher requirements for uplink transmission rates, 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, on the terminal device side, downlink control signaling of the network device is monitored in different slots to perform uplink and downlink data transmission, which increases the terminal device's power consumption. When data is not being transmitted, the terminal device may stop receiving the physical downlink control channel (PDCCH) (in this case, the terminal device stops blind detection of the PDCCH) 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, and during the sleep period (opportunity for DRX), the terminal device may enter a sleep state, not receive the PDCCH, and reduce power consumption. It should be noted that a sleep-state terminal device does not receive PDCCHs but may receive data from other physical channels, such as the physical downlink shared channel (PDSCH) or acknowledgments (ACKs). For example, in semi-persistent scheduling (SPS), a sleep-state terminal device may receive PDSCHs in periodically configured downlink subframes.

[0044] When selecting a DRX cycle, a balance between battery conservation and data latency must be considered. Long DRX cycles facilitate extending the battery life of the terminal device. However, short DRX cycles facilitate a faster response when new data transmissions are present. To meet the terminal device's requirements regarding power consumption and data latency, two DRX cycles, namely a short DRX cycle and a long DRX cycle, may be configured for a single terminal device, as shown in Figure 3. However, the terminal can only use one of the configurations at any given time.

[0045] The DRX cycle of a terminal device is typically configured by a network device. For example, a network device may perform DRX configuration by using radio resource control (RRC) signaling. For long DRX cycles, 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 short DRX cycles, the parameter drx-ShortCycle indicates the cycle value of the short DRX cycle, and the parameter drx-ShortCycleTimer is used to configure the number of short DRX cycles. The parameter drx-OnDurationTimer is used to configure the length of the On Duration period in the DRX cycle. The parameter drx-SlotOffset is used to configure 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 an offset within the subframe and is less than 1 ms.

[0046] Furthermore, the DRX configuration information includes the parameters drx-RetransmissionTimerDL and drx-HARQ-RTT-TimerDL. `drx-RetransmissionTimerDL` is the DRX downlink retransmission timer, and `drx-HARQ-RTT-TimerDL` indicates the DRX downlink hybrid automatic repeat request (HARQ) round-trip time (RTT) timer. Both parameters are used for downlink data retransmission. After the PDCCH and PDSCH transmissions are complete, the terminal device provides feedback with an ACK / NACK. If the terminal device provides feedback with a NACK, the DRX downlink HARQ round-trip time timer starts after the ACK / NACK is received, and the timing period of the DRX downlink HARQ round-trip time timer is to wait for the network device to receive and parse the NACK. When the DRX downlink HARQ round-trip time timer expires, the terminal device starts the 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 complete, the terminal device stops operating the DRX downlink retransmission timer.

[0047] Similarly, the DRX configuration information further includes the parameters drx-RetransmissionTimerUL and drx-HARQ-RTT-TimerUL. The parameter drx-RetransmissionTimerUL indicates the DRX uplink retransmission timer, and the parameter drx-HARQ-RTT-TimerUL indicates the DRX uplink HARQ round-trip time timer. Both parameters are used for uplink data retransmission. Unlike downlink transmission, after completing a 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 received the PUSCH. When the DRX uplink HARQ round-trip time timer expires, the terminal device starts the DRX uplink retransmission timer, and the terminal device wakes up to monitor the PDCCH for retransmitting uplink data. When a terminal device receives downlink control information (DCI) indicating a HARQ process that needs to be retransmitted, it stops the DRX uplink retransmission timer. Specifically, the terminal device does not need to perform monitoring throughout the entire configured uplink retransmission (retransmissionUL) period and may preemptively disable the DRX uplink retransmission timer after receiving the DCI indicating retransmission.

[0048] A PDCCH-based wake-up signal (WUS) can further improve energy saving. The WUS is typically 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 point for DCI format 2_6, which begins in the period prior to the On-Duration of the long DRX cycle. The terminal device stops monitoring DCI format 2_6 at a minimum offset prior to the On-Duration of the long DRX cycle. The minimum offset is related to the capabilities of the terminal device and its subcarriers. DCI format 2_6 is a common DCI and may contain DCI information for multiple terminal devices. Since information for different terminal devices is located in different positions within DCI format 2_6, the parameters sizeDCI-2-6-r16 and ps-PositionDCI-2-6-r16 indicate the length of DCI format 2_6 and the position of the DCI information corresponding to the terminal device within DCI format 2_6, respectively. The parameter ps-WakeUp-r16 indicates the default behavior of the terminal device, specifically whether the terminal device monitors PDCCH as usual when it is configured to monitor DCI format 2_6 but has not received the corresponding WUS information.

[0049] In DCI format 2_6, the DCI information corresponding to a terminal device may include a bit to indicate whether the terminal device will skip monitoring the PDCCH during the On Duration period in the next long DRX cycle. When the bit is 1, the terminal device will monitor the PDCCH as usual during the On Duration period in the next long DRX cycle. When the bit is 0, the terminal device will skip monitoring the PDCCH during the On Duration period in the next long DRX cycle.

[0050] The diagram illustrating the WUS effect may be shown in Figure 5. Generally, terminal devices monitor DCI format 2_6 only while sleeping in DRX and do not monitor DCI format 2_6 during On Duration. Furthermore, terminal devices do not monitor more than one DCI format 2_6 within a single long DRX cycle.

[0051] When multiple push transmission opportunities (occasions) are configured within a single XR service cycle to transmit XR frame data, each time a push is transmitted, the terminal device starts the DRX uplink retransmission timer for the HARQ process corresponding to the push, and the terminal device monitors the PDCCH during the timing 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 of terminal devices frequently starting the DRX uplink retransmission timer because they cannot make a timely decision on whether or not to start the DRX uplink retransmission timer.

[0053] The DRX configuration method provided in the embodiments of this application may be applied to the system architecture shown in Figure 6. As shown in Figure 6, the 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 in Figure 6, collectively referred to as 110) and at least one terminal (e.g., 120a to 120j in Figure 6, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 6). The terminal 120 is connected to the RAN node 110 wirelessly. The RAN node 110 is connected to the core network 200 wirelessly or wired. The core network devices within the core network 200 and the RAN nodes 110 within the RAN 100 may be different physical devices, or they may be the same physical device integrating the logical functions of the core network and the logical functions of the wireless access network.

[0054] RAN100 may be a cellular system related to a 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, RAN100 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, RAN100 may be a communication system that integrates two or more of the above systems.

[0055] RAN nodes 110 may also be referred to as access network devices, RAN entities, access nodes, etc., and form part of a communication system to enable terminals to achieve wireless access. Multiple RAN nodes 110 within the communication system 10 may be of the same type or of different types. In some scenarios, the roles of RAN nodes 110 and terminals 120 are relative. For example, network element 120i in Figure 6 may be a helicopter or unmanned aerial vehicle and may be configured as a mobile base station. For terminal 120j that accesses RAN 100 by using network element 120i, network element 120i is a base station. However, for base station 110a, network element 120i is a terminal. RAN nodes 110 and terminals 120 may also be referred to as communication devices. For example, network elements 110a and 110b in Figure 6 may be understood as communication devices with base station functionality, and network elements 120a to 120j may be understood as communication devices with terminal functionality.

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

[0057] In other possible scenarios, multiple RAN nodes cooperate to help terminals achieve radio access, with different RAN nodes independently implementing several base station functions. For example, RAN nodes 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. CUs and DUs may be located separately or may be included in the same network element, such as a baseband unit (BBU). RUs may be included in radio frequency devices or radio frequency units, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

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

[0059] A RAN node may also be described differently, such as a network device. In this application, unless otherwise specified, the term "network device" is used for descriptive purposes.

[0060] Terminals may also be called terminal devices, user equipment (UE), mobile stations, mobile terminals, 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 grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals may also be mobile phones, tablet computers, computers with wireless receiver functionality, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The device form of a terminal is not limited to the embodiments of this application.

[0061] In the methods provided in the following embodiments of this application, it may be understood that examples in which network devices and terminal devices function as execution entities in an interaction diagram are used to illustrate the methods. However, the execution entities in an 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, chip system, or processor that supports the network device in implementing the methods, or a logical node, logical module, or software that can implement all or some 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, chip system, or processor that supports the terminal device in implementing the methods, or a logical node, logical module, or software that can implement all or some of the functions of the terminal device.

[0062] Figure 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: The terminal device sends uplink data corresponding to M HARQ processes.

[0064] M is an integer greater than or equal to 1.

[0065] To support the 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. Whether or not a MAC PDU or PUSCH corresponding to one HARQ process is successfully transmitted does not affect the transmission of MAC PDUs or PUSCHs corresponding to other HARQ processes. To ensure that HARQ processes do not affect each other, both the HARQ round-trip time timer and the HARQ retransmission timer described above are for each HARQ process. In other words, the network device configures a corresponding HARQ round-trip time timer and a corresponding HARQ retransmission timer for each HARQ process. Currently, NR has up to 16 HARQ processes for uplink transmission and up to 16 HARQ processes for downlink transmission.

[0066] Accordingly, in step 701, the network device (i.e., 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 over a pre-configured resource that can be used to transmit the PUSCH, or the terminal device may transmit the PUSCH over a PUSCH resource that is dynamically or semi-permanently scheduled by the network device.

[0068] Step 702: The network device sends a first instruction to the terminal device, which indicates whether or not to start the DRX uplink retransmission timers corresponding to N of the M HARQ processes.

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

[0070] The network device transmits a corresponding first instruction information depending on whether or not the uplink data corresponding to M HARQ processes has been successfully received. Specifically, if the network device has successfully received all the uplink data corresponding to M HARQ processes, the first instruction information transmitted by the network device may instruct the terminal device not to start the DRX uplink retransmission timer. If not all of the uplink data corresponding to M HARQ processes has been successfully received by the network device, the first instruction information transmitted by the network device may instruct the terminal device to start the DRX uplink retransmission timer corresponding to N HARQ processes; in other words, it may instruct the terminal device that the uplink data corresponding to N HARQ processes has not been successfully received and needs to be retransmitted.

[0071] Accordingly, in step 702, the terminal device receives the first instruction information transmitted by the network device. After transmitting uplink data, the terminal device does not need to immediately begin monitoring the PDCCH transmitted by the network device; that is, it does not monitor the first instruction information transmitted by using the PDCCH. If the terminal device were to immediately monitor the PDCCH after transmitting uplink data, it would also result in increased power consumption, as the network device requires a certain period of time to receive and analyze the uplink data.

[0072] Step 703: The terminal device starts the DRX uplink retransmission timer when the first instruction indicates that it should start the DRX uplink retransmission timer, and while the DRX uplink retransmission timer is operating, it receives a second instruction which indicates the retransmission of uplink data corresponding to N HARQ processes.

[0073] In possible implementations, the duration of the DRX uplink retransmission timer initiated by the terminal device is related to the value of N. The duration of the DRX uplink retransmission timer is positively correlated with the value of N. Specifically, a larger value of N indicates a longer duration of the DRX uplink retransmission timer. In specific embodiments, the terminal device may preconfigure a reference duration of the DRX uplink retransmission timer. The reference duration is the duration of the DRX uplink retransmission timer required to retransmit uplink data corresponding to one HARQ process. When a first instruction tells the terminal device to initiate DRX uplink retransmission timers corresponding to N HARQ processes, the duration of the DRX uplink retransmission timer initiated by the terminal device is the N reference durations. For example, in the scenario shown in Figure 12, the first instruction indicates that uplink data corresponding to two HARQ processes has not been received correctly, and the terminal device needs to initiate the DRX uplink retransmission timer, and the duration of the DRX uplink retransmission timer is the two reference durations.

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

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

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

[0077] Format 1: The first instruction information transmitted by the network device may include 1 bit. The value of the bit indicates whether the uplink data corresponding to the HARQ process was received correctly. If the uplink data corresponding to the HARQ process was not received correctly, this indicates that retransmission needs to be performed, and the terminal device needs to start the DRX uplink retransmission timer. If the uplink data corresponding to the HARQ process was received correctly, this indicates that retransmission does not need to be performed, in other words, the terminal device does not need to start the 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 received correctly, 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 received correctly, and the terminal device needs to start the DRX uplink retransmission timer. Figure 8(a) uses an example for illustration in which the terminal device sends one CG PUSCH (corresponding to one HARQ process) within one cycle (e.g., within the on-duration of one DRX cycle). In Figure 8(b), the terminal device may send multiple CG PUSCHs within one cycle. If one CG PUSCH is not received correctly and the bit value corresponding to the first instruction information sent by the network device is 1, the terminal device starts the DRX uplink retransmission timer. The network device may specify the HARQ processes that need to be retransmitted by using second instruction information.

[0079] Format 2: A network device may send M first instruction pieces, each indicating whether the uplink data corresponding to the corresponding HARQ process has been successfully received. If the first instruction piece indicates that the uplink data has been successfully received, this indicates that retransmission is not required, in other words, the terminal device does not need to start the DRX uplink retransmission timer. If the first instruction piece indicates that the uplink data has not been successfully received, this indicates that retransmission is required, in other words, the terminal device needs to start the DRX uplink retransmission timer.

[0080] For example, a terminal device may set different DRX uplink retransmission timers for different HARQ processes, and the i-th first instruction information sent by the network device indicates whether the uplink data corresponding to the i-th HARQ process was received correctly. The i-th first instruction information may include one bit. If the bit value is 0, this indicates that the network device has received the uplink data corresponding to the i-th HARQ process correctly. 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 received the uplink data corresponding to the i-th HARQ process correctly. 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, a terminal device sets a common DRX uplink retransmission timer for M HARQ processes. The i-th first instruction sent by the network device indicates whether the uplink data corresponding to the i-th HARQ process was received correctly. The first instruction may contain one bit. If the bit is 0, it indicates that the network device received the uplink data corresponding to the i-th HARQ process correctly. If the bit is 1, it indicates that the network device did not receive the uplink data corresponding to the i-th HARQ process correctly. For a terminal device, if all M received first instruction values ​​indicate that the uplink data was received correctly, there are no HARQ processes that need 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 instruction values ​​indicates that the uplink data was not received correctly, it indicates that there are HARQ processes that need to be retransmitted, and the terminal device needs to start the DRX uplink retransmission timer.

[0082] Format 3: The first instruction information transmitted by the network device may indicate whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes.

[0083] Optionally, the first instruction 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 the uplink data corresponding to the corresponding HARQ process was successfully received, in order to indicate whether the terminal device should start the DRX uplink retransmission timer. Compared to transmitting M pieces of the first instruction information, this scheme facilitates a reduction in signaling overhead.

[0084] For example, a 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 an uplink transmission, and the bitmap may contain 16 bits. Alternatively, if future communication systems allow for more uplink HARQ processes, the bitmap may contain more bits. Alternatively, the number of bits in the bitmap may be equal to M. For example, if there are 4 HARQ processes, the bitmap may contain 4 bits, which correspond to the first, second, third, and fourth HARQ processes, respectively. If a network device has not received the uplink data corresponding to the third HARQ process, the first instruction information sent by the network device may be 0010, the value of the third bit is 1, indicating that the uplink data corresponding to the third HARQ process has not been received correctly, and the terminal device needs to start the DRX uplink retransmission timer corresponding to the third HARQ process.

[0086] In another example, a 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 M HARQ processes has been received correctly, then there are no HARQ processes that need 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 the uplink data corresponding to a HARQ process has not been received correctly, this indicates that there are HARQ processes that need to be retransmitted, and the terminal device needs to start the DRX uplink retransmission timer. As shown in Figure 9, the uplink data corresponding to the second HARQ process has not been received correctly. 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] Form 4: The first instruction information transmitted by the network device may further indicate information about N, i.e., the first instruction 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 that correspond to the incorrectly received uplink data. If the network device has not correctly received the uplink data corresponding to two of the 16 HARQ processes, the first instruction information sent by the network device may be 0010 (which translates to 2 in decimal), indicating that the uplink data corresponding to the two HARQ processes has not been correctly received, and the terminal device needs to start the DRX uplink retransmission timer, as shown in Figure 10.

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

[0090] The start time at which the terminal device monitors the first instruction information, that is, the start time at which the network device transmits the first instruction information, may be determined by one of the following methods.

[0091] Method 1: After transmitting uplink data corresponding to the HARQ process, the terminal device may start the DRX uplink HARQ round trip time timer. After the DRX uplink HARQ round trip time timer has finished or expired, the terminal device may begin monitoring the first instruction information transmitted by the network device. In other words, the time length T1 in Figure 11(a) or Figure 11(b) is the timing time length of the DRX uplink HARQ round trip time timer. The timing 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 timing period of the DRX uplink HARQ round trip time timer, the terminal device does not need to monitor the PDCCH transmitted by the network device, reducing the power consumption of the terminal device.

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

[0093] Method 2: After transmitting uplink data corresponding to the HARQ process, the terminal device begins monitoring the first instruction information transmitted by the network device after a first time length. The first time length, i.e., the time length T1 shown in Figure 11(a) or Figure 11(b), is used to wait for the network device to receive and analyze the uplink data. During the first time length, the terminal device does not need to monitor the PDCCH transmitted by the network device, reducing the power consumption of the terminal device.

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

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

[0096] If a network device transmits one common first instruction for M HARQ processes, the terminal device may begin monitoring the first instruction transmitted by the network device after a first time period, after transmitting the uplink data corresponding to the last HARQ process. If a network device transmits one first instruction for each HARQ process, the terminal device may begin monitoring the first instruction transmitted by the network device, corresponding to each HARQ process, after a first time period, after transmitting the uplink data corresponding to one HARQ process.

[0097] Method 3: The start time for the terminal device to monitor the first instruction information may, alternatively, be a second time length before the terminal device starts the DRX uplink retransmission timer.

[0098] As shown in Figure 11(c) or Figure 11(d), if a terminal device needs to start the DRX uplink retransmission timer after sending a 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 instruction information at time t1 = t2 - T1, where T1 represents a 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 timing time length of the DRX uplink HARQ round-trip time timer or the time length indicated by cg-minDFI-Delay.

[0099] If a terminal device sets a common DRX uplink retransmission timer for M HARQ processes, the second time length is subtracted from the time the common DRX uplink retransmission timer starts, and the terminal device may begin monitoring the first instruction information at the corresponding time. If a terminal device sets different DRX uplink retransmission timers for different HARQ processes, the second time length is subtracted from the time the DRX uplink retransmission timer starts, and the terminal device begins monitoring the first instruction information corresponding to the HARQ process at the corresponding time.

[0100] The above describes the method for determining the start time when the terminal device monitors the first instruction information. Below, we describe the method for determining the end time when the terminal device monitors the first instruction information.

[0101] In possible implementations, the terminal device may determine the end time for monitoring the first instruction information based on a third time length. Specifically, the time reached after the third time length has elapsed from the start time for monitoring the first instruction information is the time when the terminal device stops monitoring the first instruction information. For example, T2 in Figure 11(b) or Figure 11(b) represents the third time length. The third time length may be pre-configured in the terminal device or configured by the network device. In this case, the network device must transmit the first instruction information to the terminal device after the start time has begun and before the third time length has been reached. The terminal device monitors the first instruction information when the third time length has been reached after the start time has begun. After the third time length has been reached, the terminal device no longer monitors the first instruction information. If the terminal device receives the first instruction information transmitted by the network device before the third time length has been reached, the terminal device no longer needs to continue monitoring the first instruction information and decide whether or not to start the DRX uplink retransmission timer based on the first instruction information.

[0102] In other possible implementations, the terminal device may, alternatively, determine the end time for monitoring the first instruction information based on a minimum offset. The minimum offset indicates the point at which the terminal device stops monitoring the first instruction information before starting the DRX uplink retransmission timer. If the terminal device receives the first instruction information at a time less than the minimum offset before the DRX uplink retransmission timer starts, the terminal device does not need to start the DRX uplink retransmission timer in a timely manner and, as a result, misses receiving the second instruction information. Therefore, the network device must send the first instruction information to the terminal device before the point at which the terminal device starts the DRX uplink retransmission timer starts, and the terminal device stops monitoring the first instruction information at the point at which the terminal device starts the DRX uplink retransmission timer starts. For example, T2 in Figure 11(a) or Figure 11(d) represents the minimum offset. If a terminal device receives first instruction information transmitted by a network device before the minimum offset time before the terminal device starts the DRX uplink retransmission timer, the terminal device no longer needs to continue monitoring the first instruction information or decide whether or not to start the DRX uplink retransmission timer based on the first instruction information.

[0103] If a terminal device decides to start the DRX uplink retransmission timer based on the first instruction information it has received, the terminal device monitors the second instruction information sent by the network device while the DRX uplink retransmission timer is running. 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 the second instruction information sent by the network device for the HARQ process corresponding to the DRX uplink retransmission timer while the DRX uplink retransmission timer is running. Alternatively, the terminal device may set a common DRX uplink retransmission timer for M HARQ processes. In this case, the terminal device monitors the second instruction information sent by the network device while the common DRX uplink retransmission timer is running. The second instruction information may include N second instruction pieces, each indicating a retransmission of uplink data corresponding to the corresponding HARQ process, or one second instruction piece may indicate a retransmission of uplink data corresponding to N HARQ processes.

[0104] When a terminal device sets a corresponding DRX uplink retransmission timer for each HARQ process, the terminal device monitors for a second instruction information sent by a network device for the HARQ process while the DRX uplink retransmission timer is operating. If the terminal device receives the second instruction information for the HARQ process during the operation 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 has finished timing.

[0105] When a terminal device sets a common DRX uplink retransmission timer for M HARQ processes, and a network device transmits N second instruction pieces for N HARQ processes, the terminal device monitors the N second instruction pieces transmitted by the network device while the common DRX uplink retransmission timer is operating. If the terminal device receives N second instruction pieces during the operation of the common DRX uplink retransmission timer, it may immediately stop the DRX uplink retransmission timer, regardless of whether the timer has finished running.

[0106] When a terminal device sets a common DRX uplink retransmission timer for M HARQ processes, but a network device sends one second instruction for N HARQ processes, the terminal device monitors the one second instruction sent by the network device while the common DRX uplink retransmission timer is operating. If the terminal device receives the one second instruction during the operation of the common DRX uplink retransmission timer, it may immediately stop the DRX uplink retransmission timer, regardless of whether the timer has finished running.

[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 or not to start the DRX uplink retransmission timer by using first instruction information. Thus, the terminal device can decide in a timely manner whether or not to start the DRX uplink retransmission timer based on the first instruction information. When there is uplink data corresponding to a HARQ process that needs to be retransmitted, the terminal device starts the DRX uplink retransmission timer. When there is no uplink data corresponding to a 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, embodiments of this application further provide a communication device including a module / unit for implementing a terminal device in embodiments of the method described above. The device may be a terminal device, or a component of a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a terminal device. These modules / units may be implemented by hardware, or by hardware running the corresponding software.

[0109] For example, as shown in Figure 13, the 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 enable message processing by the communication device. In this embodiment of the application, it should be understood that the processing module 1302 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit). The interface module 1301 may be implemented by a transceiver or a transceiver-related circuit component.

[0110] Specifically, 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. Interface module 1301 is further configured to receive first instruction information, which indicates whether or not to start the DRX uplink retransmission timer corresponding to N of the M HARQ processes, where N is a positive integer less than or equal to M. Processing module 1302 is configured to start the DRX uplink retransmission timer when the first instruction information indicates to start the DRX uplink retransmission timer, and when the DRX uplink retransmission timer is operating, interface module 1301 is further configured to receive second instruction information, which indicates the retransmission of uplink data corresponding to N HARQ processes.

[0111] Furthermore, the above modules may be further configured to support other processes performed by the terminal device in the embodiments shown in Figures 7 to 12. For beneficial effects, please refer to the above description. Further details will not be described again herein.

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

[0113] For example, as shown in Figure 14, the 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 enable message processing by the communication device. In this embodiment of the application, it should be understood that the processing module 1402 may be implemented by a processor or a processor-related circuit component (or referred to as a processing circuit). The interface module 1401 may be implemented by a transceiver or a transceiver-related circuit component.

[0114] Specifically, 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. Interface module 1401 is further configured to transmit first instruction information, which indicates whether or not to start the DRX uplink retransmission timer corresponding to N of the M HARQ processes, where N is a positive integer less than or equal to M. If the first instruction information indicates to start the DRX uplink retransmission timer, processing module 1402 is configured to start the DRX uplink retransmission timer, and interface module 1401 is further configured to transmit second instruction information when the DRX uplink retransmission timer is operating, which indicates the retransmission of uplink data corresponding to N HARQ processes.

[0115] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process.

[0116] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes.

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

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

[0119] In possible implementations, the first instruction information includes information indicating N.

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

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

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

[0123] Furthermore, the above modules may be further configured to support other processes performed by the terminal device in the embodiments shown in Figures 7 to 12. For beneficial effects, please refer to the above description. Further details will not be described again herein.

[0124] Based on the same technical concept, embodiments of this application further provide a communication device. The communication device includes a processor 1501 shown in Figure 15, the processor 1501 is coupled to a memory 1502. Furthermore, 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, or one or more integrated circuits configured to control the programmed execution of the solution in this application. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the method disclosed with reference to embodiments of this application may be performed directly by a hardware processor or by using a combination of hardware and software modules within the processor.

[0126] Memory 1502 is configured to store program instructions and / or data, so that the processor 1501 can retrieve the instructions and / or data stored in memory 1502 to perform the functions of the processor 1501 described above. Memory 1502 may be read-only memory (ROM), or other types of static storage devices capable of storing static information and instructions, random access memory (RAM), or other types of dynamic storage devices capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), or any other medium that can be used to carry or store program code envisioned in the form of instructions or data structures and is accessible by a computer. Memory 1502 may exist independently, for example, as off-chip memory and connected to the processor 1501 via a communication bus 1504. Alternatively, memory 1502 may be integrated with the processor 1501.

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

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

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

[0130] When the communication device is a terminal device, the processor 1501 is configured to perform the following steps: a step of transmitting uplink data corresponding to M hybrid automatic retransmission request HARQ processes through the communication interface 1503, where M is an integer greater than or equal to 1; a step of receiving first instruction information through the communication interface 1503, where the first instruction information indicates whether or not to start an intermittent receive DRX uplink retransmission timer corresponding to N of the M HARQ processes, where N is a positive integer less than or equal to M; and a step of starting the DRX uplink retransmission timer when the first instruction information indicates to start the DRX uplink retransmission timer, and receiving second instruction information through the communication interface 1503 when the DRX uplink retransmission timer is operating, where the second instruction information indicates the retransmission of uplink data corresponding to N HARQ processes.

[0131] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process.

[0132] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes.

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

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

[0135] In possible implementations, the first instruction information includes information indicating N.

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

[0137] In a possible implementation, when the processor 1503 receives first instruction information through the communication interface 1503, the processor 1503 is specifically configured to receive the first instruction information through the communication interface 1503 from a first point in time, where the first point in time is one of the following: a point in time after a first time length from the end of transmission of uplink data, where the first time length is the downlink feedback information DFI delay time length, or a point in time configured by a network device, for example, the network adding a new parameter in its control signaling to constitute the first time length, or configuring a new timer, where the timing time length of the new timer is the first time length, or the expiration of the uplink HARQ round trip time timer.

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

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

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

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

[0142] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timer corresponding to a single HARQ process.

[0143] In a possible implementation, the first instruction indicates whether or not to start the DRX uplink retransmission timers corresponding to multiple HARQ processes.

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

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

[0146] In possible implementations, the first instruction information includes information indicating N.

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

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

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

[0150] Based on the same technical concept, embodiments of this application further provide a computer-readable storage medium. The computer-readable storage medium stores computer-readable instructions. When the computer-readable instructions are executed on a computer, one of the methods described above is performed.

[0151] Embodiments of this application provide a computer program product including instructions. When the computer program product runs on a computer, embodiments of the method are performed.

[0152] In this embodiment of the application, "transmitting information to...(terminal)" may be understood as the destination end of the information being the terminal, and may include directly or indirectly transmitting 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 source and destination ends, for example, by formatting changes. However, the destination end may understand valid information from the source end. Similar descriptions in this application may be understood similarly, and further details will not be described again.

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

[0154] Furthermore, it should be understood that in the description of this application, terms such as “first” and “second” are used merely for distinction and descriptive purposes, and should not be understood as indicating or implying relative importance, or as indicating or implying order. References to “embodiments,” “some embodiments,” etc., in this specification indicate that one or more embodiments of this application include certain features, structures, or characteristics described by reference to the embodiments. Thus, phrases such as “in some embodiments,” “in some other embodiments,” and “in other embodiments,” appearing in different places in this specification, do not necessarily mean referring to the same embodiments. Instead, these phrases mean “one or more embodiments, but not all of them,” unless specifically emphasized otherwise. The terms “include,” “have,” and variations thereof all mean “include, but not limited to,” unless specifically emphasized otherwise.

[0155] The steps of the method in the embodiments of this application may be implemented in hardware, or by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk drives, removable hard disk drives, CD-ROMs, or any other form of storage medium known in the art. For example, the storage medium may be coupled to a processor so that the processor can read information from and write information to the storage medium. Obviously, the storage medium may also 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 terminal. Obviously, the processor and the storage medium may exist as separate components in the base station or terminal.

[0156] All or part of the embodiments described above may be implemented using software, hardware, firmware, or a combination thereof. When software is used to implement the embodiments described above, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded onto a computer and executed, all or part of the procedures or functions in the embodiments of this application are performed. The computer may be a general-purpose computer, a dedicated computer, a computer network, a network device, user equipment, or other programmable device. The computer program or instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instructions may be transmitted by wired or wireless means from one website, computer, server, or data center to another website, computer, server, or data center. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device that integrates one or more available media, such as a server or data center. The usable media may be magnetic media, such as floppy disks, hard disk drives, or magnetic tapes; optical media, such as digital video discs; or semiconductor media, such as solid-state drives. The computer-readable storage medium may be volatile or non-volatile storage medium, or may include two types of storage media, namely volatile and non-volatile storage media.

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

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

Claims

1. A method of communication, The step involves sending uplink data corresponding to M Hybrid Auto-Retransmission Request (HARQ) processes, where M is an integer greater than or equal to 1. The step of receiving first instruction information, wherein the first instruction information is carried by a wake-up signal (WUS), or by a low-power WUS, or is included in downlink feedback information (DFI), and the first instruction information indicates whether or not to start intermittent receive (DRX) uplink retransmission timers corresponding to N HARQ processes out of the M HARQ processes, where N is a positive integer less than or equal to M. The steps include: starting the DRX uplink retransmission timer when the first instruction information indicates that the DRX uplink retransmission timer should be started, and receiving a second instruction information when the DRX uplink retransmission timer is operating, wherein the second instruction information indicates the retransmission of uplink data corresponding to the N HARQ processes; and A method that includes this.

2. The method according to claim 1, further comprising the step of skipping the start of the DRX uplink retransmission timer when the first instruction information indicates to skip starting the DRX uplink retransmission timer.

3. The method according to claim 1, wherein the first instruction information indicates whether or not to start a DRX uplink retransmission timer corresponding to a single HARQ process.

4. The method according to claim 1, wherein the first instruction information indicates whether or not to start the DRX uplink retransmission timer corresponding to a plurality of HARQ processes.

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

6. The method according to claim 4, wherein the plurality of HARQ processes correspond to a plurality of DRX uplink retransmission timers, respectively.

7. The method according to claim 1, wherein the first instruction information includes information indicating N.

8. The method according to claim 1, wherein the timing time length of the DRX uplink retransmission timer is related to N.

9. The step of receiving the first instruction information is: The process includes the step of receiving the first instruction information from a first point in time, The first point in time mentioned above is the following, namely, A point in time after a first time length from the end of transmission of the uplink data, where the first time length is the downlink feedback information (DFI) delay time length, or Uplink HARQ round trip time timer expires The method according to claim 1, which is one of the following.

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

11. A communication device, An interface module configured to transmit uplink data corresponding to M Hybrid Automatic Retransmission Request (HARQ) processes, where M is an integer greater than or equal to 1. The interface module is further configured to receive first instruction information, the first instruction information being carried by a wake-up signal (WUS), or by a low-power WUS, or by being included in downlink feedback information (DFI), the first instruction information indicating whether or not to start intermittent receive (DRX) uplink retransmission timers corresponding to N HARQ processes out of the M HARQ processes, where N is a positive integer less than or equal to M, and the interface module, When the first instruction information indicates that the DRX uplink retransmission timer should be started, a processing module configured to start the DRX uplink retransmission timer and Includes, When the DRX uplink retransmission timer is operating, the interface module is further configured to receive a second instruction information, the second instruction information indicating the retransmission of uplink data corresponding to the N HARQ processes, the device.

12. The aforementioned processing module is The apparatus according to claim 11, further configured to skip starting the DRX uplink retransmission timer when the first instruction information indicates to skip starting the DRX uplink retransmission timer.

13. The apparatus according to claim 11, wherein the first instruction information indicates whether or not to start a DRX uplink retransmission timer corresponding to a single HARQ process.

14. The apparatus according to claim 11, wherein the first instruction information indicates whether or not to start a DRX uplink retransmission timer corresponding to a plurality of HARQ processes.

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

16. The apparatus according to claim 14, wherein each of the multiple HARQ processes corresponds to a multiple DRX uplink retransmission timer.

17. The apparatus according to claim 11, wherein the first instruction information includes information indicating N.

18. The apparatus according to claim 11, wherein the timing time length of the DRX uplink retransmission timer is related to N.

19. When the first instruction information is received, the interface module will It is configured to receive the first instruction information from a first point in time, The first point in time mentioned above is the following, namely, A point in time after a first time length from the end of transmission of the uplink data, where the first time length is the downlink feedback information (DFI) delay time length, or Uplink HARQ round trip time timer expires The apparatus according to claim 11, which is one of the following.

20. After the interface module receives the second instruction information, the processing module: The apparatus according to claim 11, further configured to stop the operation of the DRX uplink retransmission timer.

21. A communication device including a processor, A communication device wherein the processor is coupled to a memory, the memory is configured to store a program or instruction, and when the program or instruction is executed by the processor, the device becomes capable of performing the method according to any one of claims 1 to 10.

22. A computer-readable storage medium, A computer-readable storage medium that stores instructions, and when the instructions are executed on a computer, the computer is able to perform the method according to any one of claims 1 to 10.

23. A program that includes instructions, A program in which, when the instruction is executed on a computer, the computer is able to perform the method according to any one of claims 1 to 10.

24. A communication device including a module for performing the method described in any one of claims 1 to 10.

Images