Methods and apparatus for wireless communication

Abstract

This application provides a method and apparatus for wireless communication. The method includes: determining that a first process satisfies a first condition, the first process being used to transmit first side-channel data; stopping a first timer, the first timer being used to indicate a minimum duration for which retransmission is expected, or the first timer being used to indicate a duration for keeping the device awake; wherein, the first condition is that the first process is not occupied, or the first side-channel data is successfully decoded, or feedback information for the first side-channel data is sent, or a positive acknowledgment (ACK) is received, or a negative acknowledgment (NACK) is not received. The above technical solution can reduce the impact of HARQ process management on services and improve user experience.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method and apparatus for wireless communication. Background Technology

[0002] To improve communication quality, in communication technologies such as vehicle-to-everything (V2X), communication devices (e.g., vehicles) can communicate using sidelink (SL). In the communication method based on sidelink technology, hybrid automatic repeat request (HARQ) feedback is supported. HARQ is combined with the stop-and-wait protocol to send data.

[0003] With the development of communication technology, the requirements for the reliability and quality of communication are getting higher and higher. However, when devices that support HARQ feedback manage the HARQ process, it will affect the business, resulting in data transmission activation time or unnecessary monitoring time, which cannot meet the ever-increasing communication needs.

[0004] Therefore, there is an urgent need to provide a technology that can reduce the impact of HARQ process management on business operations and improve user experience. Summary of the Invention

[0005] This application provides a method and apparatus for wireless communication that can reduce the impact of HARQ process management on services and improve user experience.

[0006] In a first aspect, a wireless communication method is provided, comprising: determining that a first process satisfies a first condition, the first process being used to transmit first side-channel data; stopping a first timer, the first timer being used to indicate a minimum duration for which retransmission is expected, or the first timer being used to indicate a duration for which the device remains awake; wherein the first condition is that the first process is not occupied, or the first side-channel data is successfully decoded, or feedback information for the first side-channel data is sent, or a positive confirmation message ACK is received, or a positive confirmation message ACK is sent, or a negative confirmation message NACK is not received.

[0007] According to the solution of this application, by determining that the first process meets the first condition, and stopping the first timer when the first condition is met, the working state of the first timer can be controlled, avoiding the extra monitoring time caused by the continuous timing of the first timer and reducing energy consumption.

[0008] The “first process” can be understood as the first side-link SL process.

[0009] "The first process is not occupied" can be understood as: the first process is in an unoccupied state.

[0010] Optionally, the wireless communication method can be performed by a receiving terminal device or a transmitting terminal device.

[0011] In conjunction with the first aspect, in one possible implementation, the method further includes: determining that the first process satisfies a second condition, the second condition being that second side data is received through the first process; stopping the first timer includes: determining that the first condition and the second condition are satisfied, and stopping the first timer.

[0012] According to the solution of this application, by determining that the first process meets the first condition, the working state of the first timer can be controlled, avoiding the extra monitoring time caused by the continuous timing of the first timer, reducing energy consumption, and thus avoiding the impact of the operation of the first timer on the activation time of the second side data.

[0013] "Receive second sideline data" can be understood as receiving the second sideline data after the first condition is met.

[0014] In conjunction with the first aspect, in one possible implementation, the method further includes: starting or restarting the first timer based on the configuration information corresponding to the second side data.

[0015] In conjunction with the first aspect, in one possible implementation, the method further includes: configuring configuration information for the second sideline data according to the first signaling.

[0016] Optionally, this configuration information can be the configuration information for non-continuous reception corresponding to the second side row data.

[0017] Optionally, the first signaling can be Radio Resource Control (RRC) signaling.

[0018] In conjunction with the first aspect, in one possible implementation, the method further includes: the first process satisfies a third condition to determine that the first process is not occupied; wherein the third condition is that the first sideline data is successfully decoded; or the third condition is that the first sideline data is decoded but fails, and the first sideline data is received on a second process.

[0019] In conjunction with the first aspect, in one possible implementation, the first process corresponds to one or more first timers, the first timers being associated with the first process, or the first timers being associated with the first process and first information, the first information including at least one of the following: source identifier, destination identifier, communication type, and Hybrid Automatic Repeat Response (HARQ) attributes.

[0020] In conjunction with the first aspect, in one possible implementation, the first timer is a round-trip time (RTT) timer or a retransmission timer.

[0021] Optionally, the first timer can also be implemented as other timers that indicate the minimum duration for which a retransmission is expected.

[0022] Optionally, the first timer can also be another timer that indicates the duration of the wake-up period.

[0023] In conjunction with the first aspect, in one possible implementation, the method further includes starting the first timer before stopping the first timer.

[0024] In conjunction with the first aspect, in one possible implementation, starting the first timer includes: determining that the first side-line data transmission has failed, and then starting the first timer.

[0025] In conjunction with the first aspect, in one possible implementation, determining that the first side-by-side data transmission has failed includes: receiving a negative acknowledgment (NACK); or sending a negative acknowledgment (NACK) to the network device; or not receiving the first feedback information.

[0026] In a second aspect, a wireless communication method is provided, the method comprising: determining that a fourth process satisfies a fourth condition, the fourth process being used to transmit fourth sideline data; determining that the fourth process is not occupied; wherein the fourth condition is that the fourth sideline data transmission is completed and a fourth timer is not running, the fourth timer being used to indicate the minimum duration for which retransmission is expected to be received, or a first timer being used to indicate the duration for which the device remains awake.

[0027] According to the solution of this application, by determining that the fourth process meets the fourth condition, it is determined that the fourth process is not occupied. After determining that the fourth process is not occupied, when the fourth process is allocated to transmit other side data, the impact on the activation time of other side data is reduced. In addition, by determining that the fourth process is not occupied, extra monitoring time can be avoided and energy consumption can be reduced.

[0028] In conjunction with the second aspect, in one possible implementation, the fourth condition is that the fourth sideline data transmission is completed, and the method includes: the fourth sideline data being successfully decoded; or receiving newly transmitted data, the newly transmitted data corresponding to the same transmission information as the fourth sideline data, the transmission information being used to identify the newly transmitted data.

[0029] In conjunction with the second aspect, in one possible implementation, the fourth condition is that the fourth side-row data transmission is completed, and the method further includes: receiving a positive confirmation message ACK; or sending a positive confirmation message ACK; or not receiving a negative confirmation message NACK.

[0030] In conjunction with the second aspect, in one possible implementation, the fourth timer is not running, and the method includes: the fourth timer timing out; or the fourth timer being stopped.

[0031] Optionally, the fourth timer being in a stopped state means that the fourth timer is instructed to stop when it is in the running state.

[0032] Thirdly, a wireless communication method is provided, the method comprising: determining that a first process satisfies a first condition, the first process being used to transmit first side-by-side data; stopping a first timer, the first timer being used to indicate the minimum duration for which retransmission is expected, or the first timer being used to indicate the duration for which the device remains awake; wherein the first condition is feedback information for transmitting the first side-by-side data, or receiving a positive confirmation information ACK, or sending a positive confirmation information ACK, or not receiving a negative confirmation information NACK.

[0033] According to the solution in this application, by determining that the first process meets the first condition and stopping the first timer, the additional monitoring time of the receiving terminal equipment can be avoided, thereby reducing energy consumption.

[0034] In conjunction with the third aspect, in one possible implementation, the method further includes starting the first timer before stopping the first timer.

[0035] In conjunction with the third aspect, in one possible implementation, starting the first timer includes: determining that the first side-line data transmission has failed, and then starting the first timer.

[0036] In conjunction with the third aspect, in one possible implementation, determining that the first side-link data transmission has failed includes: receiving a negative acknowledgment (NACK); or sending a negative acknowledgment (NACK) to the network device; or not receiving the first feedback information.

[0037] Fourthly, a wireless communication method is provided, the method comprising: determining that a fourth process satisfies a fourth condition, the fourth process being used to transmit fourth side-by-side data; determining that the fourth process is not occupied; wherein the fourth condition is that the fourth side-by-side data transmission is completed and a fourth timer is not running, the fourth timer being used to indicate the minimum duration for which retransmission is expected to be received, or a first timer being used to indicate the duration for which the device remains awake.

[0038] In conjunction with the fourth aspect, in one possible implementation, the fourth condition is that the fourth side-line data transmission is completed, and the method further includes: receiving a positive confirmation message ACK; or sending a positive confirmation message ACK; or not receiving a negative confirmation message NACK.

[0039] In conjunction with the fourth aspect, in one possible implementation, the fourth timer is not running, and the method includes: the fourth timer timing out; or the fourth timer being in a stopped state.

[0040] Fifthly, a communication device is provided, comprising: a transceiver unit and a processing unit, wherein the processing unit is configured to determine that a first process satisfies a first condition, the first process being used to transmit first side-channel data; the processing unit is further configured to stop a first timer, the first timer being used to indicate the minimum duration for which retransmission is expected, or the first timer being used to indicate the duration for which the device remains awake; wherein the first condition is that the first process is not occupied, or the first side-channel data is successfully decoded, or feedback information for the first side-channel data is sent, or a positive confirmation message ACK is received, or a positive confirmation message ACK is sent, or a negative confirmation message NACK is not received.

[0041] In conjunction with the fifth aspect, in one possible implementation, the apparatus further includes: the processing unit, further configured to determine that the first process satisfies a second condition, the second condition being receiving second sideline data through the first process; the processing unit, further configured to stop the first timer, including: the processing unit, further configured to stop the first timer when the first condition and the second condition are satisfied.

[0042] In conjunction with the fifth aspect, in one possible implementation, the apparatus further includes: the processing unit, which is further configured to start or restart the first timer based on the configuration information corresponding to the second side data.

[0043] In conjunction with the fifth aspect, in one possible implementation, the apparatus further includes: the processing unit, which is further configured to configure configuration information of the second sideline data according to the first signaling.

[0044] In conjunction with the fifth aspect, in one possible implementation, the apparatus further includes: the processing unit, which is further configured to determine that the first process is not occupied when the first process satisfies a third condition; wherein the third condition is that the first sideline data is successfully decoded; or the third condition is that the first sideline data is decoded but fails, and the transceiver unit receives the first sideline data on the second process.

[0045] In conjunction with the fifth aspect, in one possible implementation, the first process corresponds to one or more first timers, the first timers being associated with the first process, or the first timers being associated with the first process and first information, the first information including at least one of the following: source identifier, destination identifier, communication type, and Hybrid Automatic Repeat Response (HARQ) attributes.

[0046] In conjunction with the fifth aspect, in one possible implementation, the first timer is a round-trip time (RTT) timer or a retransmission timer.

[0047] In conjunction with the fifth aspect, in one possible implementation, the apparatus further includes, before stopping the first timer, the processing unit being configured to start the first timer.

[0048] In conjunction with the fifth aspect, in one possible implementation, starting the first timer includes: the processing unit determining that the first side-row data transmission has failed, and the processing unit starting the first timer.

[0049] In conjunction with the fifth aspect, in one possible implementation, the processing unit determines that the first side-link data transmission has failed, including: the processing unit determines that it has received a negative acknowledgment (NACK) message; or the processing unit determines that it has sent a negative acknowledgment (NACK) message to the network device; or the processing unit determines that it has not received a first feedback message, wherein the first feedback message is associated with the first side-link data.

[0050] In a sixth aspect, a communication device is provided, the device comprising: a processing unit and a transceiver unit, the processing unit being configured to determine that a fourth process satisfies a fourth condition, the fourth process being used to transmit fourth sideline data; the processing unit being further configured to determine that the fourth process is not occupied; wherein the fourth condition is that the processing unit determines that the fourth sideline data transmission is completed and a fourth timer is not running, the fourth timer being used to indicate the minimum duration for which retransmission is expected to be received, or a first timer being used to indicate the duration for which the device remains awake.

[0051] In conjunction with the sixth aspect, in one possible implementation, the fourth condition is that the processing unit determines that the fourth sideline data transmission is complete, including: the processing unit determines that the fourth sideline data decoding is successful; or the processing unit determines that newly transmitted data has been received, the newly transmitted data corresponding to the same transmission information as the fourth sideline data, the transmission information being used to identify the newly transmitted data.

[0052] In conjunction with the sixth aspect, in one possible implementation, the fourth condition is that the processing unit determines that the fourth side-row data transmission is complete, including: the processing unit determines that it has received a positive confirmation message ACK; or the processing unit determines that it has sent a positive confirmation message ACK; or the processing unit determines that it has not received a negative confirmation message NACK.

[0053] In conjunction with the sixth aspect, in one possible implementation, the fourth timer is not running, and the device includes: the fourth timer timed out; or the fourth timer is in a stopped state.

[0054] In a seventh aspect, a communication apparatus is provided, comprising a module or unit for performing the method of the first aspect or any possible implementation thereof, or for performing the method of the second aspect or any possible implementation thereof. The module or unit may be hardware circuitry, software, or a combination of hardware circuitry and software implementation.

[0055] Eighthly, a communication apparatus is provided, comprising a module or unit for performing the methods of the third aspect and any possible implementation thereof, or for performing the methods of the fourth aspect and any possible implementation thereof. The module or unit may be hardware circuitry, software, or a combination of hardware circuitry and software implementation.

[0056] A ninth aspect provides a communication device including a processor and a memory, the memory storing a program or instructions, the processor being configured to call and execute the program or instructions from the memory, causing the device to perform the method of the first aspect or any possible implementation thereof, or to perform the method of the second aspect or any possible implementation thereof.

[0057] Optionally, the device may also include a transceiver.

[0058] Optionally, the processor is coupled to the memory.

[0059] In a tenth aspect, a communication device is provided, comprising a processor and a memory, the memory storing a program or instructions, the processor being configured to call and execute the program or instructions from the memory, causing the device to perform the methods of the third aspect and any possible implementation thereof, or to implement the methods of the fourth aspect and any possible implementation thereof.

[0060] Optionally, the device may also include a transceiver.

[0061] Optionally, the processor is coupled to the memory.

[0062] Eleventhly, a communication device is provided, the device comprising: at least one processor and a communication interface, the communication interface being used for the device to interact with other devices, wherein when program instructions are executed in the at least one processor, the device causes the device to perform the method of the first aspect or any possible implementation thereof, or to perform the method of the second aspect or any possible implementation thereof.

[0063] Optionally, the communication interface can be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0064] Optionally, the device further includes a memory for storing instructions and data. When the processor executes the instructions stored in the memory, it can implement the method described in the first aspect or any possible implementation of the first aspect, or execute the method in the second aspect or any possible implementation of the second aspect.

[0065] In a twelfth aspect, an apparatus is provided, the apparatus comprising: at least one processor and a communication interface, the communication interface being used for the apparatus to interact with other apparatuses, wherein when program instructions are executed in the at least one processor, the apparatus causes the apparatus to perform the methods of the third aspect and any possible implementation thereof, or to implement the methods of the fourth aspect and any possible implementation thereof.

[0066] Optionally, the communication interface can be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0067] Optionally, the device further includes a memory for storing instructions and data. When the processor executes the instructions stored in the memory, it can implement the methods in the third aspect and any possible implementation of the third aspect, or implement the methods in the fourth aspect and any possible implementation of the fourth aspect.

[0068] In a thirteenth aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, and when the computer program is run on a computer, the computer causes the computer to perform the method described in the first aspect or any possible implementation thereof, or to perform the method in the second aspect or any possible implementation thereof.

[0069] In a fourteenth aspect, a computer-readable storage medium is provided, wherein a computer program is stored therein, which, when executed on a computer, causes the computer to perform the methods of the third aspect and any possible implementation thereof, or to implement the methods of the fourth aspect and any possible implementation thereof.

[0070] In a fifteenth aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to perform the method described in the first aspect or any possible implementation thereof, or to perform the method in the second aspect or any possible implementation thereof.

[0071] In a sixteenth aspect, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the methods of the third aspect and any possible implementation thereof, or to implement the methods of the fourth aspect and any possible implementation thereof.

[0072] In a seventeenth aspect, a communication system is provided, comprising the communication apparatus described in the fifth, seventh, ninth, or eleventh aspects above, and the communication apparatus described in the sixth, eighth, tenth, or twelfth aspects above. Attached Figure Description

[0073] Figure 1 This is a schematic diagram of a wireless communication system provided in an embodiment of this application.

[0074] Figure 2 This is a diagram illustrating the dynamic association method for allocating SL processes.

[0075] Figure 3 This is a schematic diagram illustrating the working mode of the retransmission timer.

[0076] Figure 4 This is a schematic diagram of the receiving end managing the timer process in the prior art.

[0077] Figure 5 This is a schematic diagram of the receiving end managing the timer process in the prior art.

[0078] Figure 6 This is a schematic diagram of the receiving end managing the timer process in the prior art.

[0079] Figure 7 This is a schematic diagram of the receiving end managing the timer process in the prior art.

[0080] Figure 8 This is a schematic diagram of the receiving end managing the timer process in the prior art.

[0081] Figure 9 This is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0082] Figure 10 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0083] Figure 11 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0084] Figure 12 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0085] Figure 13 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0086] Figure 14 This is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0087] Figure 15 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0088] Figure 16 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0089] Figure 17 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0090] Figure 18 This is a schematic diagram of the receiving side managing the timer process in the wireless communication method provided in this application embodiment.

[0091] Figure 19 This is a schematic flowchart of a wireless communication method provided in an embodiment of this application.

[0092] Figure 20 This is a schematic flowchart illustrating another wireless communication method provided in an embodiment of this application.

[0093] Figure 21 This is a schematic flowchart illustrating another wireless communication method provided in the embodiments of this application.

[0094] Figure 22 This is a schematic diagram of a communication device provided in an embodiment of this application.

[0095] Figure 23 This is a schematic diagram of a communication device provided in an embodiment of this application.

[0096] Figure 24 This is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0097] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0098] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), future 5th generation (5G) system, or new radio (NR), etc.

[0099] Figure 1 A schematic diagram of a wireless communication system 100 provided in an embodiment of this application is shown.

[0100] The wireless communication system applicable to the embodiments of this application may include at least two terminal devices, such as... Figure 1 The terminal devices 102, 103, 104, 105, 106, 107, and 108 in the communication system 100 shown. The wireless communication system applicable to the embodiments of this application may further include at least one network device, such as... Figure 1 The network device 101 in the wireless communication system 100 shown. A sidelink (SL) can be established between the at least two terminal devices, for example... Figure 1 A side link is established between the middle terminal device 104 and terminal devices 106, 107, and 108. For example... Figure 1 Terminal device 103 establishes side links with terminal devices 105 and 106 respectively, and the terminal devices that have established side links can communicate directly with each other. One terminal device can establish a side link with one or more terminal devices, for example... Figure 1 The terminal device 104 establishes side links with multiple devices. In this wireless communication system, the terminal devices can also establish wireless connections with network devices for data communication, such as... Figure 1 The terminal devices 102 and 104 shown establish wireless links with network device 101, respectively. However, the terminal devices in this wireless communication system may also not establish wireless links with the network device, such as... Figure 1The terminal device 103 shown can establish wireless links with multiple terminal devices even if it does not establish a wireless link with a network device, such as... Figure 1 Terminal device 103 establishes wireless links with terminal devices 105 and 106 respectively. It should be understood that the above wireless communication system is only an illustrative example and is not intended to limit the scope of the application.

[0101] Terminal devices can be devices that provide voice / data connectivity to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0102] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0103] Furthermore, in this embodiment of the application, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0104] In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB) technology. For example, an NB may include a resource block (RB), meaning the NB's bandwidth is only 180KB. To achieve massive access, the terminals must be discrete in their access. The communication method according to this embodiment can effectively solve the congestion problem when a large number of IoT terminals access the network through an NB.

[0105] In addition, the network device in this application embodiment can be a device for communicating with terminal devices. The network device can also be called an access network device or a wireless access network device. For example, the network device can be an evolved NodeB (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario. Alternatively, the network device can be a relay station, access point, vehicle-mounted device, wearable device, or a network device in a future 5G network or a network device in a future evolved PLMN network. It can be an access point (AP) in a WLAN, or a gNB in ​​a new radio (NR) system. This application embodiment is not limited to these limitations.

[0106] Furthermore, in the embodiments of this application, the network device is a device in the RAN, or in other words, a RAN node that connects the terminal device to the wireless network. For example, by way of example and not limitation, network devices can include: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home-evolved Node B, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc. In a network architecture, network devices may include centralized unit (CU) nodes, distributed unit (DU) nodes, RAN devices including CU nodes and DU nodes, or RAN devices including control plane CU nodes (CU-CP nodes), user plane CU nodes (CU-UP nodes), and DU nodes.

[0107] Network devices provide services to cells. Terminal devices communicate with network devices through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or the base station corresponding to a small cell. The small cells here can include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0108] Furthermore, in LTE or 5G systems, multiple cells can operate simultaneously on the same frequency on a carrier. In certain special scenarios, the concepts of carrier and cell can be considered equivalent. For example, in carrier aggregation (CA) scenarios, when configuring a secondary carrier for a UE, the carrier index of the secondary carrier and the cell identification (Cell ID) of the secondary cell operating on that secondary carrier are carried simultaneously. In this case, the concepts of carrier and cell can be considered equivalent; for instance, a terminal device accessing a carrier is equivalent to accessing a cell.

[0109] The communication system of this application can also be applied to vehicle-to-everything (V2X) technology, that is, the terminal device of this application can also be a car, such as a smart car or an autonomous vehicle.

[0110] The "X" in V2X represents different communication targets. V2X can include, but is not limited to: vehicle to vehicle (V2V), vehicle to infrastructure (V2I), vehicle to network (V2N), and vehicle to pedestrian (V2P).

[0111] In V2X, network devices can configure "zones" for UEs. These zones can also be called geographical regions. Once a zone is configured, the world is divided into multiple zones, defined by a reference point, length, and width. When determining a zone identifier (ID), the UE uses the zone's length, width, the number of zones along the length, the number of zones along the width, and the reference point for a modulo operation. This information can be configured by the network device.

[0112] V2X services can be provided in two ways: based on the PC5 interface and based on the Uu interface. The PC5 interface is defined on top of a sidelink, allowing communication devices (e.g., vehicles) to communicate directly. The PC5 interface can be used both out of coverage (OOC) and in coverage (IC), but only authorized communication devices can use it for transmission.

[0113] In V2X communication, user equipment (UE) and other UEs can communicate via a sidelink (SL). In sidelink-based communication, resource allocation supports two modes: scheduling mode (mode 1) and UE-autonomous resource selection mode (mode 2).

[0114] The scheduling mode requires the UE to be in a connected state with radio resource control (RRC). During scheduling, the UE first requests resources from the network device (e.g., eNB), and then the network device allocates control and data resources on the V2X direct link. As an example and not a limitation, scheduling in this application can include semi-persistent scheduling (SPS). Specifically, when a connected UE in V2X communication transmits data on the sidelink, the UE first needs to send a buffer status report (BSR) to the base station (or network device), reporting the amount of sidelink data that needs to be transmitted, so that the base station can allocate an appropriate amount of sidelink resources based on the data volume. If the UE has not reported uplink resources for BSR, a scheduling request (SR) is triggered. If the UE has configured SR resources, the UE sends an SR request message to the base station through the SR resources, requesting the base station to allocate uplink resources for sending the BSR. When the base station receives the SR request message, it allocates uplink transmission authorization to the UE according to the scheduling result, for the UE to send the BSR request.

[0115] Furthermore, in UE autonomous resource selection mode, the UE selects transmission resources and autonomously adjusts the transmission format of control and data on the V2X direct link. Specifically, when a UE performing sidelink communication needs to transmit data on the sidelink, the UE can select resources from the resource pool configured or pre-configured by the base station for data transmission on the sidelink. The resource pool configured by the base station can be configured through system information, or through dedicated signaling after receiving a request from the user equipment to perform sidelink communication, or through pre-configuration.

[0116] For example, if the UE is configured with a mapping relationship between "zone" and "transmission resources," then the UE selects the appropriate resource pool based on its zone. A resource pool, also called a resource set or resource group, can include one or more resources, such as V2X resources. Furthermore, this resource pool can be pre-configured for the UE by the access device. During resource selection within the resource pool, the UE uses a sensing function; "sensing" can also be called measurement or detection. Based on the sensing results, the UE selects and reserves multiple resources.

[0117] In this application, the resource pool may refer to resources used for the control information and data transmission of sidelinks.

[0118] Optionally, the resources in the resource pool include at least one of time-domain resources, frequency-domain resources, and time-frequency-domain resources.

[0119] For example, the resource may include a resource block (RB).

[0120] For example, in V2X, resources may include a subchannel consisting of multiple consecutive RBs, where the subchannel may be the smallest unit of scheduling / data transmission on a sidelink.

[0121] In this application, in order to assist the access device in configuring V2X pass-through link resources, the UE can report location information to the access device. This reporting can use existing periodic measurement reporting signaling and procedures.

[0122] In this application, V2X resources (or resource pools) may include common type resource pools, exceptional type resource pools, and dedicated type resource pools.

[0123] Furthermore, when a UE performs V2X communication using one of the two resource selection modes mentioned above, the network device can configure the terminal device to execute the other resource selection mode. For example, in LTE V2X, a UE can only be configured to execute one of the two voluntary selection modes. If the UE was previously operating in scheduled mode, and due to the need for sidelink communication and pending data transmission, a sidelink BSR was triggered, and there were no uplink resources to report the BSR at this time, a SR was triggered, putting the UE in a suspended state. Assuming all suspended SRs are triggered by sidelink BSRs, if a UE operating in scheduled mode is reconfigured to operate in autonomous mode, all suspended SRs are canceled. As another example, in NR V2X, a UE can be configured to simultaneously support both scheduled mode and autonomous mode.

[0124] In New Radio (NR) uplink communication, PUSCH transmission is divided into two types: uplink transmission based on dynamic grant and uplink transmission without dynamic grant.

[0125] For uplink transmissions based on dynamic grant, where the gNB schedules a dynamic grant (DG) for the UE, the UE sends a buffer status report (BSR) to the base station to request uplink resources. If no uplink resources are reported in the BSR at this time, the terminal needs to trigger a scheduling request (SR). After receiving the UE's scheduling request, the base station sends downlink control information (DCI) to the UE, indicating the time-frequency resource information of the UL grant in the DCI. In other words, the UE needs to monitor the DCI on the PDCCH to obtain the UL grant.

[0126] The following describes concepts related to the embodiments of this application:

[0127] A. Stop and wait agreement

[0128] The stop-and-wait protocol can be applied to data transmission within the Hybrid Automatic Repeat Request (HARQ) process. In the stop-and-wait protocol, the sending terminal device sends a transport block (TB) to the receiving terminal device and then waits for an acknowledgment. The receiving terminal device acknowledges the transport block TB, for example, through a 1-bit positive acknowledgment (ACK) or a negative acknowledgment (NACK).

[0129] Multiple parallel stop-and-wait protocols: While one HARQ process is waiting for acknowledgment, the sending terminal device can use another HARQ process to continue sending data. Multiple HARQ processes together form a HARQ entity, and the HARQ entity, combined with the stop-and-wait protocol, allows for continuous data transmission simultaneously.

[0130] A UE maintains a HARQ entity on each carrier. Each HARQ entity corresponds to a limited number of HARQ processes. Each HARQ process corresponds to an independent HARQ buffer at the receiver, used for soft combining of received data.

[0131] In NR V2X communication systems, unicast and multicast support HARQ feedback, meaning the receiving terminal device provides feedback for each downlink (SL) transmission sent by the sending terminal device. For example, if the receiving terminal device successfully receives a downlink (TB) transmission from the sending terminal device, it sends an ACK; conversely, if the receiving terminal device fails to receive the TB, it sends a NACK. It's important to note that the HARQ entity used for SL transmissions is independent of the HARQ entity used for uplink UL transmissions.

[0132] Each terminal device corresponds to one or more HARQ entities. It should be noted that a HARQ process can only process one TB (Transmission Time Interval) per transport time interval (TTI). One HARQ process corresponds to one TB, and each HARQ process has an independent HARQ buffer at the receiving end for soft merging of received data. Each HARQ process corresponds to a HARQ process ID. Retransmission resources correspond to HARQ process IDs, and the corresponding retransmission data is sent on the retransmission resource corresponding to the HARQ process ID.

[0133] B. Sidelink HARQ

[0134] In this application, in an NR V2X system, one UE (terminal device) corresponds to one or more MAC entities. Each MAC entity of the transmitting terminal device maintains one or more HARQ entities for communication with network devices, and one or more HARQ entities for communication with other terminal devices (e.g., receiving terminal devices). Among them, the HARQ entities corresponding to communication with other UEs maintain multiple SL processes.

[0135] When performing sidelink services, terminal device #B (i.e., an example of the sending-side terminal device, such as...) Figure 1 Terminal device 104) determines an SL process for transmitting transport block TB from the transmitting side's crosslink SL process. Optionally, terminal device #B can determine the SL process based on its operating mode.

[0136] For example, terminal device #B operates in mode 1 (i.e., when the sending terminal device sends buffered SL data, it requests SL resources from the network device):

[0137] Step 1: Terminal device #B receives downlink control information (DCI) sent by network device, obtains HARQID from the DCI, and uses the DCI for scheduling downlink SL resources on the network device side.

[0138] Step 2: In the SL process of terminal device #B, determine an SL process to handle the resource, and associate the selected SL process with the HARQ ID in the DCI;

[0139] Step 3: Terminal device #B carries the identified ID of the determined SL process in the sideline control information (SCI) and sends it to terminal device #A via the sideline link.

[0140] Terminal device #A:

[0141] Step 1: Terminal device #A receives the sideline control information (SCI) sent by terminal device #B and determines whether the data to be transmitted is newly transmitted data or retransmitted data;

[0142] Step 2: When the data to be transmitted is new data, the terminal device #A allocates an SL process to receive the data corresponding to the SCI and associates the SL process with the SCI (such as ID information).

[0143] This SL process is an unused SL process. Specifically, terminal device #A associates the SL process ID indicated in the received SCI with the determined SL process ID.

[0144] Step 3: Decode the received data (transmission block).

[0145] If decoding is successful, it is determined that the SL process corresponding to #A of the terminal device is not in use.

[0146] It should be noted that the SL process identifier carried in the SCI is determined by the sending-side terminal device. The receiving-side terminal device can receive SL transmissions from multiple sending-side terminal devices. Different sending-side terminal devices can indicate the same SL process identifier (ID) in their corresponding SCIs. The receiving-side terminal devices use a dynamic association method to allocate SL processes for receiving. Figure 2 This diagram illustrates a dynamic association method for allocating SL processes according to an embodiment of this application.

[0147] C.HARQ timer

[0148] The Dynamic Resource Extensions (DRX) configuration includes the configuration parameter for the timer drx-HARQ-RTT-TimerDL (or UL). This parameter is configured for each DL HARQ process or each UL HARQ process and is related to retransmissions. It represents the minimum duration the UE must wait before receiving the expected downlink retransmission schedule (or sending the expected uplink retransmission data). For DL ​​(UL), the round trip time (RTT) timer can be understood as the base station's processing time. During this period, the terminal device determines that there is no retransmission schedule. If the wake-up conditions are not met, the terminal device is in a sleep state. If the RTT timer expires, the base station has completed processing and may need to schedule DL retransmissions. The terminal device then starts drx-RetransmissionTimerDL to return to the wake-up state and monitor retransmission schedules.

[0149] For example, such as Figure 3 A schematic diagram illustrating the operation of the retransmission timer provided in an embodiment of this application is shown. Figure 3 As shown, in the downlink, this timer operates as follows:

[0150] Startup: For a given HARQ process, the UE receives a Media Access Control (MAC) Protocol Data Unit (PDU) on the DL SPS, or the UE receives a PDCCH indicating DL allocation, and starts the timer on the first symbol after sending DL feedback;

[0151] Stop: Protocol undefined;

[0152] Timeout: For a specific HARQ process, if the RTT timer times out and the UE fails to decode the data, drx-RetransmissionTimerDL is started.

[0153] Figures 4 to 8 A schematic diagram illustrates possible methods for managing timers in the prior art. For example... Figures 4 to 8 As shown, the method illustrates a possible implementation of a timer processing mechanism in a receiving-side terminal device.

[0154] Figure 4 A schematic diagram of the receiver-managed timer process in the prior art is shown. For example... Figure 4 The method shown can be derived from Figure 1 The method is executed by the receiving terminal device, such as terminal device #A. The execution steps of the method are as follows:

[0155] Step 1: Terminal device #A receives transport block TB1 and allocates SL process #A1 to receive TB1.

[0156] Step 2: Terminal device #A confirms that SL process #A1 is not in use.

[0157] It should be understood that if terminal device #A determines that SL process #A1 is not occupied, it can receive new data for the same transmission information #A1. Optionally, terminal device #A may allocate process #A2 to receive the new data. The transmission information #A1 includes at least one or more of the following: source identifier, destination identifier, communication type, HARQ attribute of Hybrid Automatic Repeat Response, HARQ process ID, and sidelink process ID.

[0158] For example, taking the transmission of information through the PSCCH channel as an example, i.e., the transmission carried in the SCI, we can explain the method for determining whether the received data is newly transmitted data. The SCI1 received by terminal device #A contains {HARQ process 1, SRC ID 1, DST ID 1, unicast mode, NDI = 1}, where the initial value of NDI is 1. Taking the sending device identified by SRC ID 1 as terminal 1 and the receiving device identified by DST ID 1 as terminal 2 as an example, when the receiving device first receives SCI1, it indicates that SCI1 schedules terminal 1 to transmit new data to terminal 2 via HARQ process 1 using unicast mode. If the receiving device subsequently receives SCI1 = {HARQ process 1, SRC ID 1, DST ID 1, unicast mode, NDI = 0}, where only the value of NDI changes, while the values ​​of HARQ process 1, SRC ID 1, DST ID 1, and unicast mode remain unchanged (i.e., only the value of NDI is flipped), it indicates that SCI1 schedules terminal 1 to transmit new data to terminal 2 via HARQ process 1 using unicast mode. If the receiving device subsequently receives SCI1 = {HARQ process 1, SRC ID 1, DST ID 1, DST ID 1, NDI = 0} again... ID1, unicast mode, NDI=0}, HARQ process 1, SRC ID 1, DST ID1, unicast mode and NDI values ​​remain unchanged, indicating that SCI1 schedules terminal 1 to retransmit data to terminal 2 via HARQ process 1 using unicast mode.

[0159] Step 3: Terminal device #A sends the feedback information FB corresponding to TB1 to terminal device #B (i.e., an example of the sending side terminal device), and starts or restarts the RTT timer corresponding to SL process #A1 according to the DRX configuration information 1 corresponding to TB1.

[0160] It should be noted that the timer RTT1 will automatically stop after its timeout and start a retransmission timer to wake up the terminal device for monitoring retransmitted data and / or other side link transmissions.

[0161] Optionally, after SL process #A1 is determined to be unoccupied, terminal device #A can allocate SL process #A1 to receive data. It is understood that after SL process #A1 is determined to be unoccupied, starting the retransmission timer to monitor the downlink transmission will increase the activation time and power consumption.

[0162] Figure 5 A schematic diagram of the receiver-managed timer process in the prior art is shown. For example... Figure 5 The method shown can be derived from Figure 1 The method is executed by the receiving terminal device, such as terminal device #A. The execution steps of the method are as follows:

[0163] Step 1: Terminal device #A decodes the transport block TB1 received on SL process #B1.

[0164] Step 2: Terminal device #A confirms that SL process #B1 is not in use.

[0165] Step 3: Terminal device #A sends feedback information FB1 corresponding to TB1 to terminal device #B (i.e., an example of a sending-side terminal device), and starts or restarts the RTT timer corresponding to SL process #B1 according to the DRX configuration information 1 corresponding to TB1.

[0166] Optionally, the timer RTT1 is associated with the SL process #B1.

[0167] Step 4: Terminal device #A receives transport block TB3 sent by terminal device #B through SL process #B1.

[0168] Optionally, the time when terminal device #A receives TB3 can be within the timing interval corresponding to RTT1, such as... Figure 5 As shown.

[0169] Optionally, the time when terminal device #A receives TB3 may also fall within the timing interval of the retransmission timer. This application does not limit this.

[0170] Optionally, after SL process #B1 is determined to be unoccupied, terminal device #A can allocate SL process #B1 to receive newly transmitted data. It is understood that after SL process #B1 is determined to be unoccupied, starting the retransmission timer to monitor the downlink transmission will increase the activation time and power consumption.

[0171] It should be noted that Figure 5 This illustrates a case where a timer is associated with a process, for example, RTT1 with process #B1 in SL.

[0172] Optionally, a process can also correspond to multiple timers. For example... Figure 6 As shown, Figure 6A schematic diagram of the receiver's timer management process in the prior art is shown, wherein SL process #C1 can correspond to RTT1 and RTT2. Specifically, RTT1 can be associated with SL process #C1 and information #C1, and RTT2 can be associated with SL process #C1 and information #C2. Information #C1 corresponds to TB1 and is used to indicate the transmission characteristics of TB1. Information #C2 corresponds to TB3 and is used to indicate the transmission characteristics of TB1. Information #C1 and information #C2 can be at least one of the following: source identifier, destination identifier, communication type, Hybrid Automatic Repeat Response (HARQ) attribute, HARQ process ID, and sidelink process ID. Information #C1 and information #C2 are different.

[0173] Optionally, SL process #C1 can correspond to RTT1 and RTT2. Terminal device #A sends feedback information FB3 corresponding to TB3. It can configure the RTT2 timing duration based on the DRX configuration information DRX2 corresponding to TB3 and start RTT2. Understandably, after terminal device #A determines that SL process #C1 is unoccupied, it starts timer RTT1 when sending the feedback signal FB1 for TB1. When timer RTT1 times out, a retransmission timer is started to monitor the downlink transmission, which increases the activation time and power consumption.

[0174] Figure 7 A schematic diagram of the receiver-managed timer process in the prior art is shown. For example... Figure 5 The method shown can be derived from Figure 1 The method is executed by the receiving terminal device, such as terminal device #A. The execution steps of the method are as follows:

[0175] Step 1: Terminal device #A decodes the transport block TB1 received on SL process #D1.

[0176] Step 2: Terminal device #A confirms that TB1 has been successfully decoded and determines that SL process #B1 is not in use.

[0177] Step 3: Terminal device #A sends the feedback signal FB1 corresponding to TB1 to terminal device #B (i.e., an example of the sending side terminal device), and starts the RTT timer corresponding to SL process #D1 according to the DRX configuration information DRX1 corresponding to TB1.

[0178] Optionally, the timer RTT is associated with the SL process #B1.

[0179] Step 4: Terminal device #A receives transport block TB2 sent by terminal device #B through SL process #D1.

[0180] Step 5: Terminal device #A sends the feedback signal FB2 corresponding to TB2 to terminal device #B.

[0181] Optionally, the time when terminal device #A receives TB3 can be within the timing interval corresponding to the RTT timer, such as... Figure 7 As shown.

[0182] Optionally, the time when terminal device #A receives TB3 may also fall within the timing interval of the retransmission timer. This application does not limit this.

[0183] It should be noted that the time domain position of the received TB2 may not be within the time interval of the RTT timer or the retransmission timer; this application does not impose any limitations on this.

[0184] Optionally, after SL process #B1 is determined to be unoccupied, terminal device #A can allocate SL process #D1 to receive newly transmitted data.

[0185] It should be noted that, Figure 7 This illustrates a scenario where a timer is associated with a process.

[0186] Optionally, a process can also correspond to multiple timers. For example... Figure 8 As shown, Figure 8 A schematic diagram of the receiver managing the timer process in the prior art is shown. Figure 8 In this context, a process can have multiple timers, and... Figure 6 The SL process #C1 shown can correspond to RTT1 and RTT2 in a similar way. To avoid redundancy, its detailed description is omitted here.

[0187] Figure 9 A schematic flowchart of a wireless communication method 200 provided in an embodiment of this application is shown. Figure 9 The method 200 shown can be applied to the side link hybrid automatic repeat process. This method 200 can be... Figure 1 The receiving terminal device in the middle performs the operation, for example, by Figure 1 The terminal devices 106, 107, or 108 in the process are executed. For ease of description, the terminal device #A is used below to represent the receiving terminal device. For example... Figure 9 The method 200 shown allows terminal device #A to control the operating state of a first timer by determining that the first process meets a first condition, thereby avoiding the additional monitoring time caused by the continuous timing of the first timer and reducing energy consumption. Method 200 includes:

[0188] S210, terminal device #A determines that the first process satisfies the first condition, the first process being used to transmit the first side data;

[0189] Optionally, the side data can be a transport block (TB).

[0190] Optionally, condition #1 (i.e., an example of the first condition) is that the first process is not occupied.

[0191] This first process can be the side-link SL Hybrid Automatic Repeat Response (HARQ) process. For example, this first process is the HARQ process used for PC5 communication.

[0192] It should be noted that "the first process is not occupied" can also be understood as the first process being in an unoccupied state, or the first process being not occupied can also be understood as the first process being released, or the first process being in an idle state, or the terminal device #A allowing the first process to be used to receive other transmissions, for example, the terminal device #A releasing the first process.

[0193] Optionally, terminal device #A determines that the third condition is met and that the first process is not occupied.

[0194] For example, condition #3 (i.e., an example of the third condition) can be that data #A (i.e., an example of the first row of data) is successfully decoded. It should be noted that after the terminal device successfully decodes data #A, it determines that the first process is not currently in use.

[0195] For example, condition #3 can also be for data #A failing to decode, and newly transmitted data #B with the same information identifier being received. This information identifier can include a source identifier (SRC ID), a destination identifier (DST ID), HARQ attributes, and a communication type (cast type). The communication type can also be called the service type, and can be unicast, multicast, or broadcast. Optionally, terminal device #A allocates a second process to receive the newly transmitted data #B. The new transmission or retransmission of data can be indicated by this information identifier and NDI information. For example, terminal device #A receives a sideline control information (SCI) sent by terminal device #B, reads and determines the information identifier and NDI information contained in the SCI. It determines whether terminal device #A has received the same information before. If the same information has been received, it compares the NDI information in the SCI corresponding to the first received information with the NDI information in the second received information. If the two NDI information are the same, the data is determined to be retransmitted data; if the two NDI information are different (i.e., the NDI value is toggled), the data is determined to be newly transmitted data. It should be noted that receiving data #A in the second process can be understood as meaning that data #A is related to the second process.

[0196] Optionally, condition #1 can also mean that the data #A was successfully decoded.

[0197] Optionally, condition #1 can also be used to allocate the first process for receiving new transfers (TB).

[0198] Optionally, condition #1 can also be feedback information associated with sent data #A.

[0199] This feedback information can help the terminal device #A (in this embodiment, #A is the receiving UE) determine whether to send a positive acknowledgment (ACK) or not send a negative acknowledgment (NACK). This feedback information can correspond to two different static feedback modes. The first mode is sending ACK / NACK; for example, if data is received correctly, an ACK is sent; if data is not received correctly, a NACK is sent. The second mode is sending only NACK; for example, if data is received correctly, no NACK is sent; if data is not received correctly, a NACK is sent. It is understood that the second static feedback mode is the case where the feedback information is not sent.

[0200] S220, Terminal device #A stops the first timer, which is used to indicate the minimum duration for which a retransmission is expected, or the first timer is used to indicate the duration for which the device remains awake.

[0201] It should be noted that the first timer, used to indicate the duration of the wake-up period, can also be understood as:

[0202] Optionally, the first process may correspond to one or more first timers, the first timers being associated with the first process, or the first timers being associated with the first process and first information, the first information including at least one of the following: source identifier, destination identifier, communication type, hybrid automatic repeat response (HARQ) attribute, sidelink process ID, and HARQ process ID.

[0203] For example, the first process corresponds to a first timer, and this first timer is associated with the first process. It can be understood that the association between the first timer and the first process means that there is a one-to-one correspondence between the first timer and the first process. Specifically, for example, process #A (an example of the first process) corresponds to RRT timer #A (an example of the first timer), and the timing duration of RRT timer #A can be switched according to different DRX configurations. For instance, at time T1, process #A is associated with pair1, then the length of RRT timer #A is the timing duration of RRT timer #A provided in the DRX configuration corresponding to pair1; at time T2, the receiving terminal device allocates process #A to receive the side-link transmission of pair2 (i.e., process #A is associated with pair2), then the length of the RTT timer of process #A is the timing duration provided in the DRX configuration corresponding to pair2.

[0204] For example, the first process corresponds to multiple first timers, and each first timer is associated with the first process and the first information. Specifically, for example, process #B (i.e., one example of the first process) corresponds to multiple RTT timers (i.e., multiple instances of the first timers, such as RTT#B1, RTT#B2, etc.). For each pair's DRX configuration, process #B is associated with a different RTT timer. For example, at time T1, process #B is associated with pair1, and the length of this timer is the timing length of RTT#B1 provided in the DRX configuration corresponding to pair1; at time T2, the receiving terminal device allocates process #B to receive the side-link transmission of pair2, and associates timer RTT#B2 with process #B, the timing length of which is the length of RTT#B2 provided in the DRX configuration corresponding to pair2.

[0205] It should be understood that the aforementioned pair can be identified by a set of source and target identifiers, with each pair corresponding to a set of source and target identifiers. For example, {target identifier 1, source identifier 1} is used to identify pair 1, and {target identifier 2, source identifier 2} is used to identify pair 2. Alternatively, a pair can be identified by a link identifier, such as link identifier 1 for pair 1 and link identifier 2 for pair 2. Or, a pair can correspond to a set of transmitting and receiving devices, such as transmitting device 1 and receiving device 1 being referred to as pair 1, and transmitting device 1 and receiving device 2 being referred to as pair 2. The transmitting and receiving devices can be terminal devices, network devices, etc., and are not limited here.

[0206] Optionally, the first timer is a Round-Trip Time (RTT) timer or a Retransmission Timer. It is understood that when terminal device #A stops the first timer, it means stopping the RTT timer or the retransmission timer. It should be understood that in some other embodiments, the first timer may also be other timers to achieve the function of the first timer described above.

[0207] Optionally, if condition #1 is that the first process is not occupied, and before step S210, the method 200 may further include:

[0208] Upon receiving or sending the first side data, a first feedback message is sent to start or restart the first timer.

[0209] Specifically, for example, the first timer can be started after terminal device #A receives the Physical Link Control Channel (PSCCH) or Physical Link Shared Channel (PSSCH) sent by terminal device #B (an example of a transmitting terminal device). For instance, after receiving the Link Control Information (SCI) sent by terminal device #B, terminal device #A receives the PSSCH sent by terminal device #B according to the SCI; upon receiving the PSSCH, terminal device #A starts the first timer. Alternatively, terminal device #A starts the first timer after receiving the Link Control Information (SCI) sent by terminal device #B.

[0210] For example, the first timer can be started after terminal device #A sends the Physical Side Feedback Channel (PSFCH) to terminal device #B. For instance, after receiving the Side Control Information (SCI) sent by terminal device #B, terminal device #A receives the PSSCH sent by terminal device #B based on the SCI; after receiving the PSSCH, terminal device #A sends the PSFCH to terminal device #B based on the decoding result, and starts or restarts the first timer.

[0211] Optionally, the first feedback information is the feedback information corresponding to the first side data. For example, the first feedback information can be transmitted on the physical side feedback channel PSFCH.

[0212] Figures 10 to 13 A schematic diagram of a timer management method provided in an embodiment of this application is shown. For example... Figures 10 to 13 As shown, the method illustrates a possible implementation of timer processing by the receiving terminal device. Figures 10 to 13 The method shown is used to process the timer after the data transfer block TB has been processed.

[0213] Figure 10 This diagram illustrates the receiving side's timer management process in the wireless communication method provided in this application embodiment. Figure 10 The method shown can be derived from Figure 1 The receiving terminal device executes the command, such as terminal device #A.

[0214] It should be noted that the steps involved in the embodiments of this application do not have strict time constraints. In some embodiments, the steps described below can be executed in chronological order, while in other embodiments, different steps can be executed synchronously. The embodiments of this application do not limit this.

[0215] Step 1: Terminal device #A decodes the transport block TB1 received through SL process #1 and starts the RTT timer according to the configuration information DRX1 corresponding to TB1.

[0216] Optionally, terminal device #A can start the corresponding RTT timer when it receives TB1.

[0217] Step 2: Terminal device #A determines that the SL process #1 is not in use, and stops the RTT timer or retransmission timer.

[0218] It should be understood that if terminal device #A determines that SL process #1 is unoccupied, it can receive new data for the same information #1. Optionally, terminal device #A may allocate SL process #2 to receive the new data. The transmitted information #1 includes at least one or more of the following: source identifier, destination identifier, communication type, HARQ attribute, HARQ process ID, and sidelink process ID.

[0219] In one possible scenario, when terminal device #A determines that SL process #1 is not in use, the RTT timer may have timed out, and after the RTT timeout, a retransmission timer is started. At this time, the RTT timer is not running while the retransmission timer is running, so the retransmission timer is stopped.

[0220] Step 3: Terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B.

[0221] It should be understood that the feedback information FB#1 is the feedback information sent by terminal device #A to terminal device #B in response to TB1. This feedback can be an affirmative acknowledgment (ACK) or a negative confirmation (NACK), or no ACK or NACK may be sent. It should also be understood that these two feedback signals correspond to different static feedback modes.

[0222] Step 4: Terminal device #A assigns the SL process #1 to receive the newly transmitted data TB3, and starts or restarts the RTT timer according to the DRX configuration information DRX2 of TB3, and / or sends the feedback information FB3 corresponding to TB3.

[0223] It should be noted that, Figure 10 In this context, process #1 of the SL class corresponds to one RTT timer (i.e., the first process corresponds to one first timer). Figure 10 The timing duration of the RTT timer shown is for illustrative purposes only. Figure 10 The shaded area represents the duration for which the RTT timer of SL process #1 stops after it is no longer in use.

[0224] It should also be noted that steps 1 through 4 above are not sequential and can be executed in any order. For example, after terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B, it determines that SL process #1 is unused, and then stops the RTT timer or retransmission timer.

[0225] For example, Figure 10 The illustration only shows the case where the RTT timer is started when TB1 is received; however, this application is not limited to this.

[0226] It should also be noted that Figure 10 The time of receiving TB3 can be within the time range after the RTT timeout, or the time of receiving TB3 can be within the time range of the RTT timeout. This application is not limited to this.

[0227] Figure 11 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figure 11 The method shown can be derived from Figure 1 The receiving terminal device executes the command, such as terminal device #A.

[0228] Step 1: Terminal device #A receives transport block TB1 through SL process #1 and starts the RTT timer according to the configuration information DRX1 corresponding to TB1.

[0229] Optionally, terminal device #A can start the corresponding RTT timer when it receives TB1.

[0230] Step 2: Terminal device #A confirms that TB1 has been successfully decoded, determines that SL process #1 is not in use, and stops the RTT timer.

[0231] Optionally, step 2 can also be that the terminal device #A determines that TB1 has been successfully decoded and stops the RTT timer.

[0232] Optionally, step 2 can also involve the terminal device #A sending feedback information corresponding to TB1 to stop the RTT timer. This feedback information can be a positive acknowledgment (ACK) or a negative acknowledgment (NACK).

[0233] Step 3: Optionally, terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B.

[0234] Step 4: Optionally, terminal device #A assigns the SL process #1 to receive the newly transmitted data TB3, starts the RTT timer according to the configuration information DRX2 of TB3, and sends the feedback information FB3 corresponding to TB3.

[0235] It should be noted that, Figure 11 The reception time of TB3 shown in the figure is within the RTT timer timing range. For example, Figure 11 The illustration only shows the start of the RTT timer when TB1 is received; however, this application is not limited to this.

[0236] It should also be noted that, Figure 11 Zhongyu Figure 10 The execution steps in the code correspond to two scenarios: successful decoding and decoding failure. Figure 11 and Figure 10 The method of starting the RTT timer and sending feedback signals are the same, so to avoid redundancy, a detailed description will be omitted here.

[0237] It should also be noted that steps 1 through 4 above are not sequential and can be executed in any order. For example, after terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B, it determines that SL process #1 is unused, and then stops the RTT timer or retransmission timer.

[0238] Optionally, if terminal device #A determines that TB1 was successfully decoded, it does not start the RTT timer. Alternatively, if terminal device #A determines that TB1 was decoded unsuccessfully, it starts the RTT timer. For example, the RTT timer can be started when terminal device #A determines that decoding has failed, or when sending or generating the negative feedback information NACK corresponding to TB1.

[0239] Figure 12 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figure 12 The method shown can be derived from Figure 1 The receiving terminal device executes the command, such as terminal device #A.

[0240] Step 1: Terminal device #A receives transport block TB1 through SL process #3 and starts the RTT timer according to the configuration information DRX1 corresponding to TB1.

[0241] Optionally, terminal device #A can start the corresponding RTT timer when it receives TB1.

[0242] Step 2: Terminal device #A determines that the SL process #3 is not in use and stops the RTT timer.

[0243] In one possible scenario, when terminal device #A determines that SL process #1 is not in use, the RTT timer may have timed out, and after the RTT timeout, a retransmission timer is started. At this time, the RTT timer is not running while the retransmission timer is running, so the retransmission timer is stopped.

[0244] Step 3: Optionally, terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B.

[0245] It should be understood that the feedback information FB#1 is the feedback information sent by terminal device #A to terminal device #B in response to TB1. This feedback can be an affirmative acknowledgment (ACK) or a negative confirmation (NACK), or no ACK or NACK may be sent. It should also be understood that these two feedback signals correspond to different static feedback modes.

[0246] Step 4: Terminal device #A assigns SL process #3 to receive newly transmitted data TB3, starts the RTT timer according to the configuration information DRX2 of TB3, and sends the feedback information FB3 corresponding to TB3.

[0247] Optionally, RTT1 is associated with SL process #3 and message #31, and RTT2 is associated with SL process #3 and message #32. Message #31 and message #32 can be at least one of the following: source identifier (SRC ID), destination identifier (DST ID), communication type or HARQ attribute of the hybrid automatic repeat response, HARQ process ID, and sidelink process ID, and messages #31 and #32 can be different. For example, message #31 can correspond to {SRC ID 1, DST ID 1}, and message #32 can correspond to {SRC ID 2, DST ID 2}.

[0248] It should be noted that, Figure 12 In the example, SL process #3 corresponds to two RTT timers (i.e., an example of the first process corresponding to multiple first timers). Figure 10 The timing duration of the RTT timer shown is for illustrative purposes only. Figure 10 The shaded area represents the duration for which the RTT timer of SL process #1 stops after it is no longer in use.

[0249] For example, Figure 10 The illustration only shows the case where the RTT timer is started when TB1 is received; however, this application is not limited to this.

[0250] It should also be noted that Figure 10 The time at which TB3 is received may be within the time range of the RTT timeout, or the time at which TB3 is received may be within the time range of the RTT. This application is not limited to this.

[0251] Figure 13 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figure 13 The method shown can be derived from Figure 1 The receiving terminal device executes the command, such as terminal device #A.

[0252] Step 1: Terminal device #A receives transport block TB1 through SL process #4.

[0253] It should be noted that RTT1 is associated with SL process #4 and information #41.

[0254] Step 2: Terminal device #A determines that SL process #4 is not in use.

[0255] It should also be noted that RTT2 is associated with SL process #4 and message #42. Message #41 and message #42 may be different.

[0256] Step 3: Terminal device #A sends the feedback information FB#1 corresponding to TB1 to terminal device #B.

[0257] Step 4: Terminal device #A assigns the SL process #4 to receive the newly transmitted data TB3, and starts the RTT timer (i.e., RTT2) according to the configuration information DRX2 of TB3, and sends the feedback information FB3 corresponding to TB3.

[0258] It should be noted that in step 2, determining that SL process #4 is unoccupied can be understood as meaning that SL process #4 and information #41 are not associated, or that terminal device #A releases the association between SL process #4 and information #41. Timer RTT1 does not start after TB1 decoding fails.

[0259] It should be understood that the above embodiments are merely illustrative and this application is not limited thereto.

[0260] Figure 14 A schematic flowchart of a wireless communication method 300 provided in an embodiment of this application is shown. Figure 10 The method 300 shown can be applied to Figure 1 The system shown, method 200 can be derived from Figure 1 The receiving terminal device in the middle performs the operation, for example, by Figure 1 The terminal devices 106, 107, or 108 in the process are executed. For ease of description, the terminal device #A is used below to represent the receiving terminal device. For example... Figure 14 In the method 300 shown, the terminal device #A determines that the first process meets the first condition, thereby controlling the working state of the first timer, avoiding the extra monitoring time caused by the continuous timing of the first timer, reducing energy consumption, and thus avoiding the impact of the first timer's operation on the activation time of the second side data.

[0261] The method 300 includes:

[0262] S310, Terminal device #A determines that the first process meets the first condition, the first process being used to transmit first side data;

[0263] Optionally, the first condition may be that the first process is not occupied;

[0264] Optionally, the first condition can also be that the first side row data was successfully decoded;

[0265] Optionally, the first condition can also be feedback information for sending the first side data.

[0266] It should be noted that step S310 and step S210 have the same execution steps, and their detailed description is omitted here to avoid redundancy.

[0267] S320, Terminal device #A determines that the first process satisfies the second condition, the second condition being that the second side data is received through the first process;

[0268] Optionally, the second side row data can be transport block TB#2.

[0269] It should be noted that terminal device #A can determine that the sidelink HARQ process is in an unoccupied state (or is already unoccupied). Terminal device #A can allocate an unoccupied process for transmitting second sidelink data. For example, terminal device #A can allocate a first process to receive second sidelink data. It is understood that after determining that a process is unoccupied, the transport block TB associated with that process before it was determined to be unoccupied will not be retransmitted. Alternatively, terminal device #A may not process the transport block TB associated with that process before it was determined to be unoccupied.

[0270] S330, Terminal device #A stops the first timer, which is used to indicate the minimum duration for which a retransmission is expected, or the first timer is used to indicate the duration for which the device remains awake.

[0271] Optionally, terminal device #A determines that the first process satisfies the first condition and the second condition, and stops the first timer.

[0272] Optionally, the method 300 may further include:

[0273] Terminal device #A starts or restarts the first timer based on the configuration information corresponding to the second side row data.

[0274] Optionally, this configuration information can be DRX configuration information.

[0275] Optionally, terminal device #A configures the configuration information of the second sideline data according to the first signaling. This first signaling can be RRC signaling. Specifically, for example, the RRC layer of terminal device #A instructs the MAC to configure the DRX configuration information of the IDpair corresponding to the second sideline data. This step can be performed independently of other steps as a separate scheme, or it can be combined with any other step as a scheme.

[0276] It should also be noted that the execution process of steps S330 and S220 is similar, and their detailed description is omitted here to avoid redundancy. For example, the first process in step S330 can correspond to one first timer, or the first process in step S330 can correspond to multiple first timers.

[0277] Figures 15 to 18 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figures 15 to 18 As shown, the method illustrates another possible implementation of the receiving-side terminal device processing the timer. Figures 10 to 13 The method shown is used to process the timer when new data (TB) is received on the side link process.

[0278] Figure 15 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figure 15 The method shown can be derived from Figure 1 The receiving terminal device in the process executes the command, such as terminal device #A (e.g., terminal device 107).

[0279] Step 1: Terminal device #A receives transport block TB1 through SL process #1 and starts the RTT timer according to the configuration information DRX1 corresponding to TB1.

[0280] Optionally, terminal device #A can start the corresponding RTT timer when it receives TB1.

[0281] Step 2: Terminal device #A determines that SL process #1 is not in use.

[0282] It should be understood that if terminal device #A determines that SL process #1 is not occupied, it can receive new data for the same information #1. Optionally, terminal device #A may allocate SL process #2 to receive the new data. The transmitted information #1 includes at least one or more of the following: source identifier, destination identifier, communication type, HARQ attribute of Hybrid Automatic Repeat Response, HARQ process ID, and sidelink process ID.

[0283] Step 3: Optionally, terminal device #A sends the feedback signal FB#1 corresponding to TB1 to terminal device #B through the SL process #1.

[0284] It should be understood that the feedback signal FB#1 is the feedback signal sent by terminal device #A to terminal device #B in response to TB1. This feedback can be a positive acknowledgment (ACK) or a negative confirmation (NACK), or no ACK or NACK may be sent. It should also be understood that these two feedback signals correspond to different static feedback modes.

[0285] Step 4: Terminal device #A assigns the SL process #1 to receive the newly transmitted data TB3, stops the currently running RTT timer, and starts the RTT timer according to the configuration information DRX2 of TB3.

[0286] It should be noted that, Figure 15 The time when TB3 is received via SL process #5 can be within the time range of the RTT, or the time when TB3 is received can be outside the time range of the RTT. For example, the time when TB3 is received can also be within the running time range of the retransmission timer. Figure 15 The timing range of the RTT timer is only shown schematically, and this application is not limited to it. For example, Figure 15 The diagram shown may also include a retransmission timer.

[0287] In one possible scenario, when terminal device #A determines that SL process #1 is not in use, the RTT timer may have timed out, and after the RTT timeout, a retransmission timer is started. At this time, the RTT timer is not running while the retransmission timer is running, so the retransmission timer is stopped.

[0288] Optionally, when the RTT timer is running (i.e., the RTT timer is running according to the configuration information DRX1), the new TB is received through the SL process #5, and the RTT timer is restarted according to the RTT configuration of the DRX corresponding to the new data (i.e. TB3).

[0289] Optionally, when the retransmission timer is running (i.e., the RTT timer expires and the retransmission timer is started), the new TB is received through the SL process #5, and the retransmission timer is stopped. The RTT timer is restarted according to the RTT configuration of the DRX corresponding to the new data (i.e., TB3).

[0290] Optionally, if a new TB is received through this SL process #5, the running timer (RTT timer or retransmission timer) is stopped.

[0291] Step 5: Optionally, send the feedback information FB3 corresponding to TB3.

[0292] It should be noted that, Figure 15 In the process, SL process #5 corresponds to one RTT timer (i.e., the first process corresponds to one first timer). Figure 15 The timing duration of the RTT timer shown is for illustrative purposes only.

[0293] It should also be noted that steps 1 through 5 above are not sequential and can be executed in any order.

[0294] For example, Figure 15 The illustration only shows the case where the RTT timer is started when TB1 is received; however, this application is not limited to this.

[0295] Figure 15 The illustration shows a scenario where TB1 decoding fails and a transport block is received via the SL process, but this application is not limited to this; for example, Figure 15 This can also be used in the case of successful TB1 decoding, or by starting the RTT timer after sending the feedback signal for transport block TB. It should be noted that starting the RTT timer after successful TB1 decoding and sending the feedback information for transport block TB can be done as follows: Figure 16 The diagram illustrates the process management method.

[0296] like Figure 16 The schematic diagram shown in this application embodiment illustrates the receiving side's timer management process in the wireless communication method, which can be applied to... Figure 1 The receiving terminal device in the process, such as terminal device #A (e.g., terminal device 107), performs the operation.

[0297] Figure 16 Optionally, in the method shown, when the RTT timer or retransmission timer is running (i.e., the RTT timer or retransmission timer is running according to the configuration information DRX1), the new transmission TB is received through the SL process #6, the RTT timer is stopped, and the RTT timer is started according to the RTT configuration of the DRX corresponding to the new transmission data (i.e., TB3).

[0298] Figure 17 A schematic diagram of the receiving side managing a timer process in the wireless communication method provided in this application embodiment is shown. For example... Figure 17 The method shown can be derived from Figure 1 The receiving terminal device in the process executes the command, such as terminal device #A (e.g., terminal device 107).

[0299] Step 1: Terminal device #A receives transport block TB1 through SL process #7 and starts RTT timer (RTT1) according to the configuration information DRX1 corresponding to TB1.

[0300] Optionally, terminal device #A can start the corresponding RTT timer when it receives TB1.

[0301] Step 2: Terminal device #A determines that SL process #1 is not in use.

[0302] It should be understood that if terminal device #A determines that SL process #7 is not occupied, it can receive new data for the same information #1. Optionally, terminal device #A may allocate SL process #2 to receive the new data. The transmission information #1 includes at least one or more of the following: source identifier, destination identifier, communication type, HARQ attribute of Hybrid Automatic Repeat Response, HARQ process ID, and sidelink process ID.

[0303] Step 3: Terminal device #A sends the feedback signal FB#1 corresponding to TB1 to terminal device #B.

[0304] It should be understood that the feedback signal FB#1 is the feedback signal sent by terminal device #A to terminal device #B in response to TB1. This feedback can be a positive acknowledgment (ACK) or a negative confirmation (NACK), or no ACK or NACK may be sent. It should also be understood that these two feedback signals correspond to different static feedback modes.

[0305] Step 4: Terminal device #A assigns SL process #7 to receive newly transmitted data TB3, stops the retransmission timer, and starts the RTT2 timer according to the DRX configuration information DRX2 of TB3.

[0306] Optionally, terminal device #A assigns SL process #7 to receive newly transmitted data TB3 and stops the retransmission timer.

[0307] It should be noted that, Figure 17 The timing range of the RTT timer is only shown schematically, and this application is not limited to it. For example, Figure 17 The diagram shown may also include a retransmission timer.

[0308] Optionally, when the RTT timer is running (i.e., the RTT timer is running according to the configuration information DRX1), if a new TB is received through the SL process #7, the timer RTT1 is stopped.

[0309] Optionally, if the retransmission timer is running (i.e., the RTT timer expires and the retransmission timer is started), the new TB is received through the SL process #7, and the retransmission timer is stopped.

[0310] Step 5: Send the feedback information FB3 corresponding to TB3.

[0311] It should be noted that, Figure 17 In the example, SL process #7 corresponds to two RTT timers (i.e., the first process corresponds to multiple first timers). Figure 17 The timing duration of the RTT timer shown is for illustrative purposes only.

[0312] It should also be noted that steps 1 through 5 above are not sequential and can be executed in any order.

[0313] For example, Figure 17 The illustration only shows the case where the RTT timer is started when TB1 is received; however, this application is not limited to this.

[0314] Figure 17 The illustration shows a scenario where TB1 decoding fails and a transport block is received via SL process #7, but this application is not limited to this; for example, Figure 17 Alternatively, the RTT timer can be started after the feedback signal of transport block TB1 is sent. It should be noted that starting the RTT timer after sending the feedback signal of transport block TB1 can be done as follows: Figure 18 The diagram illustrates the process management method.

[0315] like Figure 18 The schematic diagram shown in this application embodiment illustrates the receiving side's timer management process in the wireless communication method, which can be applied to... Figure 1 The receiving terminal device in the process, such as terminal device #A (e.g., terminal device 107), performs the operation.

[0316] Figure 18 In the method shown, optionally, when the timer RTT1 is running (i.e., the RRT timer is running according to the configuration information DRX1), the timer (RRT1 or retransmission timer #1) is stopped when the new transmission TB2 is received through the SL process #8.

[0317] It should be noted that, Figure 17 The stop RTT timer or retransmission timer shown is the timer (RTT1 or retransmission timer) associated with SL process #7 and message #71 before SL process #7 is released; Figure 18 The stop RTT timer or retransmission timer shown is the timer (RTT1 or retransmission timer) associated with SL process #8 and message #81 before SL process #8 is released.

[0318] Figure 19 A schematic flowchart of a wireless communication method 400 provided in an embodiment of this application is shown. Figure 19 The method 400 shown can be applied to the side link hybrid automatic repeat process. This method 400 can be... Figure 1 The receiving terminal device in the middle performs the operation, for example, by Figure 1 The terminal devices 106, 107, or 108 in the process are executed. For ease of description, the terminal device #A is used below to represent the receiving terminal device. For example... Figure 19The method 400 shown describes how terminal device #A determines that when the fourth process meets the fourth condition, by determining that the fourth process is in an unoccupied state, it can avoid the impact on the activation time of other sideline data when the fourth process is allocated to transmit other sideline data after successfully decoding the sideline data. Furthermore, determining that the fourth process is unoccupied avoids additional monitoring time and reduces energy consumption. Method 400 includes:

[0319] S410, the terminal device determines that the fourth process meets the fourth condition, and the fourth process is used to transmit fourth side data;

[0320] Optionally, the fourth condition can be that the fourth side data is successfully decoded and the fourth timer times out, wherein the fourth timer is used to time the fourth process.

[0321] It should be noted that the fourth timer will stop timing after it times out.

[0322] Optionally, the fourth timer is associated with the fourth process, or the fourth timer is associated with both the fourth process and the fourth information. Associating the fourth timer with the fourth process can be understood as a one-to-one correspondence between the fourth timer and the fourth process; associating the fourth timer with both the fourth process and the fourth information can be understood as the fourth timer potentially corresponding to multiple timers.

[0323] S420, Determine that the fourth process is not in use;

[0324] Optionally, "the fourth process is not occupied" can be understood as the fourth process being in an unoccupied state. "The fourth process is not occupied" can also be understood as the fourth process not being associated with a timer, or the fourth process not being associated with a timer or fourth information, where the fourth information may include at least one of the following: source identifier, destination identifier, communication type, and Hybrid Automatic Repeat Response (HARQ) attributes.

[0325] S430, receive fifth side data through the fourth process.

[0326] Optionally, the fifth side data can be newly transmitted data, for example, the fifth side data can be TB2, and the fourth side data can be TB1.

[0327] Optionally, the fifth side row data has different information pairs than the fourth side row data.

[0328] Figure 20 A schematic flowchart of another wireless communication method 500 provided in an embodiment of this application is shown. Figure 20 The method 500 shown can be applied to the side link hybrid automatic repeat process. This method 500 can be... Figure 1 The sending-side terminal device in the process is executed, for example by... Figure 1 The terminal device 104 in the process is executed, and for ease of description, it will be referred to as terminal device #C (i.e., an example of the sending-side terminal device) below. For example... Figure 20 The method 500 shown describes a method where, when the data transmission success condition is met, the sixth process stops or does not start the sixth timer, thereby avoiding the impact of the sixth timer continuing to time after the sixth data transmission is successful on the sixth process's service transmission. Method 500 includes:

[0329] S510, Terminal device #C determines that the sixth process meets the sixth condition, which is used to transmit the sixth side data, and the sixth condition indicates that the sixth side data transmission is complete;

[0330] Optionally, the sixth condition may be to send a first acknowledgment to the network device on the first physical uplink control channel (PUCCH); for example, to send an affirmative acknowledgment (ACK) on the first PUCCH.

[0331] Optionally, the sixth condition may also be that the terminal device #D (i.e., an example of the receiving terminal device) receives the first acknowledgment information on the first physical side line feedback channel PSFCH, and the first acknowledgment information may be an affirmative acknowledgment information ACK.

[0332] Optionally, the sixth condition can also be that no negative acknowledgment (NACK) message has been received;

[0333] Optionally, the sixth condition may also be to send a first physical side row shared channel (PSSCH) on the sixth process.

[0334] S520, stop or not start the sixth timer, which is used to indicate the minimum duration for which retransmission resources are expected to be received, or the first timer is used to indicate the duration for which the wake-up is maintained.

[0335] The method further includes, if the terminal device #C determines that the sixth side-link data transmission has failed, starting or restarting the sixth timer. For example, determining that the sixth side-link data transmission has failed may include: receiving a negative ACK feedback from the side-link, or not receiving an ACK or NACK. Specific methods can be found in the above embodiments and will not be repeated here.

[0336] Figure 21 A schematic flowchart of another wireless communication method 600 provided in an embodiment of this application is shown. Figure 21 The method 600 shown can be applied to the side link hybrid automatic repeat process. This method 600 can be... Figure 1 The sending-side terminal device in the process is executed, for example by... Figure 1 The terminal device 104 in the process is executed, and for ease of description, it will be referred to as terminal device #C (i.e., an example of the sending-side terminal device) below. For example... Figure 21 The method 600 shown describes a terminal device #C determining that when the seventh process meets the seventh condition, by determining that the seventh process is in an unoccupied state, when the seventh process is allocated for transmitting eighth sideline data, it can prevent the seventh timer from continuing to run under the configuration information corresponding to the seventh sideline data and affecting the timing of the eighth sideline data. Method 600 includes:

[0337] S610, Terminal device #C determines that the seventh process meets the seventh condition, the seventh process is used to transmit the seventh side data, and the seventh process corresponds to the seventh timer;

[0338] Optionally, the seventh condition may be that the seventh timer is not running, the seventh timer is used to indicate the monitoring time for the network device to schedule the seventh process, or to indicate the minimum duration for which retransmission resources are expected to be received, or the first timer is used to indicate the duration of the keep-wake-up period.

[0339] For example, the seventh timer not running can be understood as the seventh timer being in a stopped state. For instance, terminal device #C can stop the running fourth timer in some cases. For example, when terminal device #C receives a new transmission schedule for the same HARQ ID, optionally, terminal device #C allocates the seventh process to receive and process the new transmission resource, then terminal device #C stops the fourth timer; or, terminal device #A confirms that the seventh side link data transmission is successful and stops the seventh timer; or, terminal device #C preempts the seventh process to process other side link resources, then the terminal device stops the seventh timer; or, the seventh timer times out, then the seventh timer stops.

[0340] S620, confirm that the seventh process is not in use;

[0341] S630, the eighth side data is transmitted through the seventh process, and the information transmitted by the eighth side data is different from that of the seventh side data.

[0342] The above text combined Figures 1 to 21 The method embodiments of this application are described in detail below, in conjunction with... Figures 22 to 24 This application provides a detailed description of the apparatus embodiments. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be found in the preceding method embodiments.

[0343] Figure 22 This is a schematic diagram of the communication device provided in an embodiment of this application. Figure 22 The communication device 700 can be the terminal device mentioned above, for example, it can be... Figure 1 The terminal devices 104, 107, and 108 shown are a specific example. The communication device 700 can be used to implement the steps performed by the terminal devices described above, for example... Figure 9 or Figure 14 The method can also be used for specific implementations. Figures 10 to 13 The illustrated embodiment is described below. To avoid redundancy, it will not be described again.

[0344] Figure 22 The communication device 700 shown includes a determining unit 710 and a stopping unit 720.

[0345] The determining unit 710 is used to determine that the first process satisfies the first condition, and the first process is used to transmit the first side data.

[0346] Stop unit 720 is used to stop the first timer, which is used to indicate the minimum duration for which a retransmission is expected, or the duration for which the first timer is kept awake.

[0347] The first condition is that the first process is not occupied, or the first side data is successfully decoded, or feedback information of the first side data is sent, or a positive confirmation message ACK is received, or a positive confirmation message ACK is sent, or a negative confirmation message NACK is not received.

[0348] Optionally, the determining unit 710 is further configured to determine that the first process satisfies a second condition, wherein the second condition is that the second side data is received through the first process.

[0349] The stopping unit 720 is specifically used to determine that the first condition and the second condition are met, and then stop the first timer.

[0350] Optionally, the communication device further includes a startup unit, which is used to start or restart the first timer according to the configuration information corresponding to the second side data.

[0351] Optionally, the communication device includes a configuration unit for configuring configuration information of the second sideline data according to a first signaling.

[0352] Optionally, the determining unit is further configured to determine that the first process is not occupied if the first process satisfies the third condition.

[0353] The third condition is that the first side data is successfully decoded; or the third condition is that the first side data is decoded but fails, and the first side data is received in the second process.

[0354] Optionally, the first process corresponds to one or more first timers, the first timers are associated with the first process, or the first timers are associated with the first process and first information, the first information including at least one of the following: source identifier, destination identifier, communication type, hybrid automatic repeat response (HARQ) attribute, HARQ process ID, and sidelink process ID.

[0355] Optionally, the first timer is a round-trip time (RTT) timer or a retransmission timer.

[0356] Optionally, the communication device includes a startup unit for starting the first timer before stopping it.

[0357] Optionally, the startup unit is specifically used to determine that the first side-line data transmission has failed and to start the first timer.

[0358] Optionally, determining that the first side-line data transmission failed includes: receiving a negative acknowledgment (NACK); or

[0359] Send a negative acknowledgment (NACK) message to the network device; or do not receive the first acknowledgment message.

[0360] Figure 23 This is a schematic diagram of the communication device provided in an embodiment of this application. Figure 23 The communication device 800 can be the terminal device mentioned above, for example, it can be... Figure 1 The terminal devices 104, 107, and 108 shown are a specific example. The communication device 800 can be used to implement the steps performed by the terminal devices described above, for example... Figure 19 The method is described below. To avoid redundancy, it will not be described again.

[0361] Figure 23 The communication device 800 shown includes a determining unit 810.

[0362] The determining unit 810 is used to determine that the fourth process satisfies the fourth condition, wherein the fourth process is used to transmit the fourth side data.

[0363] The determining unit 810 is also used to determine that the fourth process is not occupied.

[0364] The fourth condition is that the fourth side data transmission is completed and the fourth timer is not running. The fourth timer is used to indicate the minimum duration for which a retransmission is expected, or the first timer is used to indicate the duration for which the device remains awake.

[0365] Optionally, the fourth condition is the completion of the fourth sideline data transmission, including: the fourth sideline data is successfully decoded; or new data is received, the new data corresponding to the same transmission information as the fourth sideline data, the transmission information being used to identify the new data.

[0366] Optionally, the fourth condition is the completion of the fourth side-line data transmission, including: receiving a positive confirmation message ACK; or sending a positive confirmation message ACK; or not receiving a negative confirmation message NACK.

[0367] Optionally, the fourth timer not running includes: the fourth timer timing out; or the fourth timer being stopped.

[0368] Figure 24 This is a schematic diagram of the structure of the terminal device 900 provided in an embodiment of this application. The terminal device 900 can be applied to, for example... Figure 1 In the system shown, the functions of the terminal device in the above method embodiments are executed. As shown, the terminal device 900 includes a processor 920 and a transceiver 910. Optionally, the terminal device 900 also includes a memory 930. Exemplarily, the processor 920, transceiver 910, and memory 930 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory is used to store computer programs, and the processor 920 is used to execute the computer programs in the memory 930 to control the transceiver 910 to transmit and receive signals. Optionally, the terminal device 900 may include a bus system 940, through which the transceiver 910, processor 920, and memory 930 can transmit information.

[0369] The processor 920 and the memory 930 can be combined into a single processing device. The processor 920 executes the program code stored in the memory 930 to achieve the aforementioned functions. In specific implementations, the memory can be integrated into the processor 920 or be independent of the processor 920.

[0370] Transceiver 910 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). For example, the receiver is used to receive signals, and the transmitter is used to transmit signals.

[0371] It should be understood that Figure 24 The terminal device 900 shown can achieve Figure 9 , Figure 14 , Figure 19 , Figure 20 or Figure 21The methods illustrated in the embodiments involve various processes of the terminal device. The operations and / or functions of each module in the terminal device 900 are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the descriptions in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0372] The processor 920 described above can be used to perform the actions implemented internally by the terminal device as described in the preceding method embodiments, while the transceiver 910 can be used to perform the actions described in the preceding method embodiments of sending data to or receiving data from the network device by the terminal device. Please refer to the descriptions in the preceding method embodiments for details, which will not be repeated here.

[0373] Optionally, the terminal device 900 may also include a power supply for providing power to various devices or circuits in the terminal device.

[0374] In addition, to further enhance the functionality of the terminal device, the terminal device 900 may also include one or more of an input unit, a display unit, an audio circuit, a camera, and a sensor, and the audio circuit may also include a speaker, a microphone, etc.

[0375] This application also provides a processing apparatus, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the methods in any of the above method embodiments.

[0376] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0377] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0378] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0379] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. For example, non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0380] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when executed by one or more processors, causes a device including the processor to perform... Figure 9 , Figure 14 , Figure 19 , Figure 20 or Figure 21 The method in the illustrated embodiment.

[0381] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code that, when executed by one or more processors, causes a device including the processor to perform... Figure 9 , Figure 14 , Figure 19 , Figure 20 or Figure 21 The method in the illustrated embodiment.

[0382] According to the method provided in the embodiments of this application, this application also provides a system that includes one or more of the aforementioned terminal devices.

[0383] In the above-described device embodiments, the network devices and terminal devices in the method embodiments completely correspond to each other, with corresponding modules or units performing the corresponding steps. For example, the communication unit (transceiver) performs the receiving or sending steps in the method embodiments, while other steps besides sending and receiving can be performed by the processing unit (processor). The functions of specific units can be found in the corresponding method embodiments. For example, there may be one or more processors.

[0384] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0385] In the above-described device embodiments, the network devices and terminal devices in the method embodiments completely correspond to each other, with corresponding modules or units executing the corresponding steps. For example, the communication unit (transceiver) executes the receiving or sending steps in the method embodiments, while other steps besides sending and receiving can be executed by the processing unit (processor). The functions of specific units can be found in the corresponding method embodiments. There can be one or more processors.

[0386] As used in this specification, the terms "component," "module," "system," etc., are used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process and / or an execution thread, and components may be located on a single computer and / or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0387] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0388] It should be noted that the terms "after" and "time" in this application do not strictly limit the specific point in time.

[0389] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0390] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0391] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0392] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0393] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0394] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0395] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for wireless communication, characterized in that, The method includes: The first process is determined to satisfy the first condition, and the first process is used to transmit the first side data. Determine that the first process satisfies the second condition, wherein the second condition is that the first process receives second side data. If the first condition and the second condition are met, the first timer is stopped. The first timer is used to indicate the minimum duration for which a retransmission is expected to be received, or the first timer is used to indicate the duration for which the device remains awake. The first condition is that the first process is not occupied, or the first side data is successfully decoded, or feedback information of the first side data is sent, or a positive confirmation message ACK is received, or a positive confirmation message ACK is sent, or a negative confirmation message NACK is not received.

2. The method according to claim 1, characterized in that, The method further includes: The first timer is started or restarted based on the configuration information corresponding to the second side row data.

3. The method according to claim 2, characterized in that, The method further includes: Configure the configuration information of the second side data according to the first signaling.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The first process satisfies the third condition, thus determining that the first process is not occupied; The third condition is that the first side-row data was successfully decoded; or The third condition is that the first side data decoding fails, and the first side data is received in the second process.

5. The method according to claim 4, characterized in that, The first process corresponds to one or more first timers. The first timer is associated with the first process, or the first timer is associated with the first process and first information. The first information includes at least one of the following: source identifier, destination identifier, communication type, and Hybrid Automatic Repeat Response (HARQ) attributes.

6. The method according to claim 5, characterized in that, The first timer is either a round-trip time (RTT) timer or a retransmission timer.

7. The method according to claim 6, characterized in that, The method further includes starting the first timer before stopping the first timer.

8. The method according to claim 7, characterized in that, Starting the first timer includes: It was determined that the first side-line data transmission failed. Start the first timer.

9. The method according to claim 8, characterized in that, The method for determining that the first side-row data transmission has failed includes: Receive a negative acknowledgment (NACK); or Send a negative acknowledgment (NACK) message to the network device; or No first feedback information was received; the first feedback information is associated with the first side data.

10. A method for wireless communication, characterized in that, The method includes: The fourth process is determined to satisfy the fourth condition, and the fourth process is used to transmit fourth side row data; The fourth process is determined to meet the fifth condition, which is that the fourth process is not occupied. If the fourth and fifth conditions are met, the fifth side data is received through the fourth process; The fourth condition is that the fourth side data transmission is completed and the fourth timer is not running. The fourth timer is used to indicate the minimum duration for which a retransmission is expected to be received, or the fourth timer is used to indicate the duration for which the device remains awake.

11. The method according to claim 10, characterized in that, The fourth condition is that the fourth side-row data transmission is completed, and the method includes: The fourth row of data was successfully decoded; or Receive newly transmitted data, which corresponds to the same transmission information as the fourth side row data, and the transmission information is used to identify the newly transmitted data.

12. The method according to claim 11, characterized in that, The fourth condition is that the fourth side-row data transmission is completed, and the method further includes: Receive a positive ACK message; or Send an ACK message to confirm the information; or No negative acknowledgment (NACK) message was received.

13. The method according to any one of claims 10 to 12, characterized in that, The method includes: If the fourth timer is not running, the method includes: The fourth timer times out; or The fourth timer is in a stopped state.

14. A communication device, characterized in that, include: Transceiver unit and processing unit, The processing unit is used to determine that the first process meets the first condition, and the first process is used to transmit the first side data; The processing unit is further configured to determine that the first process satisfies a second condition, wherein the second condition is that the second side data is received through the first process; The processing unit is further configured to stop the first timer when the first condition and the second condition are met, wherein the first timer is configured to indicate the minimum duration for which retransmission is expected, or the first timer is configured to indicate the duration for which the device remains awake. The first condition is that the first process is not occupied, or the first side data is successfully decoded, or feedback information of the first side data is sent, or a positive confirmation message ACK is received, or a positive confirmation message ACK is sent, or a negative confirmation message NACK is not received.

15. The apparatus according to claim 14, characterized in that, The device further includes: The processing unit is further configured to start or restart the first timer based on the configuration information corresponding to the second side row data.

16. The apparatus according to claim 15, characterized in that, The device further includes: The processing unit is further configured to configure the configuration information of the second side data according to the first signaling.

17. The apparatus according to any one of claims 14 to 16, characterized in that, The device further includes: The processing unit is further configured to determine that the first process is not occupied when the first process satisfies the third condition; The third condition is that the first side-row data was successfully decoded; or The third condition is that the first side data decoding fails, and the transceiver unit receives the first side data in the second process.

18. The apparatus according to claim 17, characterized in that, The first process corresponds to one or more first timers. The first timer is associated with the first process, or the first timer is associated with the first process and first information. The first information includes at least one of the following: source identifier, destination identifier, communication type, and Hybrid Automatic Repeat Response (HARQ) attributes.

19. The apparatus according to claim 18, characterized in that, The first timer is either a round-trip time (RTT) timer or a retransmission timer.

20. The apparatus according to claim 19, characterized in that, The device further includes, before stopping the first timer, the processing unit is also configured to start the first timer.

21. The apparatus according to claim 20, characterized in that, Starting the first timer includes: The processing unit determines that the first side-row data transmission failed. The processing unit starts the first timer.

22. The apparatus according to claim 21, characterized in that, The processing unit determines that the first side-row data transmission failed, including: The processing unit determines that a negative acknowledgment (NACK) message has been received; or The processing unit determines to send a negative acknowledgment (NACK) message to the network device; or The processing unit determines that it has not received the first feedback information, which is associated with the first side data.

23. A wireless communication device, characterized in that, The device includes: a processing unit and a transceiver unit. The processing unit is used to determine that the fourth process meets the fourth condition, and the fourth process is used to transmit the fourth side row data; The processing unit is further configured to determine that the fourth process satisfies a fifth condition, wherein the fifth condition is that the fourth process is not occupied; The processing unit is further configured to receive fifth sideline data through the fourth process if the fourth condition and the fifth condition are met; The fourth condition is that the processing unit determines that the fourth side-row data transmission is completed and the fourth timer is not running. The fourth timer is used to indicate the minimum duration for which a retransmission is expected to be received, or the fourth timer is used to indicate the duration for which the device remains awake.

24. The apparatus according to claim 23, characterized in that, The fourth condition is that the processing unit determines that the fourth side-row data transmission is complete, including: The processing unit determines that the fourth side row data has been successfully decoded; or The processing unit determines that newly transmitted data has been received. The newly transmitted data corresponds to the same transmission information as the fourth side row data. The transmission information is used to identify the newly transmitted data.

25. The apparatus according to claim 24, characterized in that, The fourth condition is that the processing unit determines that the fourth side row data transmission is complete, including: The processing unit determines that it has received a positive confirmation message ACK; or The processing unit determines to send a positive confirmation message (ACK); or The processing unit determines that it has not received a negative acknowledgment (NACK) message.

26. The apparatus according to any one of claims 23 to 25, characterized in that, The fourth timer is not running, and the device includes: The fourth timer times out; or The fourth timer is in a stopped state.

27. A communication device, characterized in that, Includes at least one processor coupled to a memory for storing programs or instructions; The at least one processor is configured to execute the program or instructions to cause the apparatus to implement the method as described in any one of claims 1 to 9, or to implement the method as described in any one of claims 10 to 13.

28. A computer-readable storage medium, characterized in that, Includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1 to 13.

29. A communication system, characterized in that, Includes the apparatus as described in claim 27.

Images