Patent Application
20240049346
This application is directed to the field of wireless communications technologies, and specifically relates to a transmission control method, a terminal, and a network-side device.
SideLink (SL, or may also be referred to as side-link, sidelink, side link, or the like) terminals within coverage of a base station need to monitor Downlink Control Information (DCI) sent by the base station, such as SL DCI for scheduling sidelink resources and/or Uu DCI for Uu interface services. However, continuous monitoring for DCI all the time consumes a large amount of energy. Therefore, monitoring or transmission behaviors of terminals User Equipment (UE) need to be controlled through a Discontinuous Reception (DRX) mechanism to achieve power saving. However, requirements of SL services are usually different from requirements of Uu services, and the terminal may also need to receive an SL feedback after SL DCI schedules the terminal to perform SL transmission. Further, the terminal may also need to report the obtained SL feedback information to the base station, and therefore the sidelink terminal also needs to consider the procedure of SL feedback in comparison to the procedure of Uu DCI-based scheduling and feedback information reporting. How sidelink terminals implement a similar DRX mechanism and monitor for DCI is a technical problem that needs to be resolved at present.
Embodiments of this application provide a transmission control method, a terminal, and a network-side device to implement a DRX mechanism in sidelink.
According to a first aspect, a transmission control method is provided, including: performing, by a terminal based on a first status or based on the first status and a second status, a first operation related to discontinuous reception DRX; where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
According to a second aspect, a transmission control apparatus is provided, including: a first determining module, configured to determine a first status, or the first status and a second status; and a first execution module, configured to, based on the first status or based on the first status and the second status, perform a first operation related to discontinuous reception DRX; where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
According to a third aspect, a transmission control method is provided, including: performing, by a network-side device based on a third status or based on the third status and a fourth status, a second operation related to discontinuous reception DRX; where the third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
According to a fourth aspect, a transmission control apparatus is provided, including: a second determining module, configured to determine a third status, or the third status and a fourth status; and a second execution module, configured to, based on the third status or based on the third status and the fourth status, perform a second operation related to discontinuous reception DRX; where the third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
According to a fifth aspect, a terminal is provided, where the terminal includes a processor, a memory, and a program or instructions stored in the memory and capable of running on the processor, and when the program or the instructions are executed by the processor, the steps of the method according to the first aspect are implemented.
According to a sixth aspect, a terminal is provided, including a processor and a communication interface, where the processor is configured to perform, based on a first status or based on the first status and a second status, a first operation related to discontinuous reception DRX; where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status: and the communication interface is configured to communicate with an external communication device.
According to a seventh aspect, a network-side device is provided, where the network-side device includes a processor, a memory, and a program or instructions stored in the memory and capable of running on the processor, and when the program or the instructions are executed by the processor, the steps of the method according to the third aspect are implemented.
According to an eighth aspect, a network-side device is provided, including a processor and a communication interface, where the processor is configured to perform, based on a third status or based on the third status and a fourth status, a second operation related to discontinuous reception DRX; where the third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status; and the communication interface is configured to communicate with an external communication device.
According to a ninth aspect, a readable storage medium is provided, where a program or instructions are stored in the readable storage medium, and when the program or the instructions are executed by a processor, the steps of the method according to the first aspect are implemented, or the steps of the method according to the third aspect are implemented.
According to a tenth aspect, a chip is provided, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the steps of the method according to the first aspect or implement the steps of the method according to the third aspect.
According to an eleventh aspect, a computer program/program product is provided, where the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the steps of the method according to the first aspect or the steps of the method according to the third aspect.
In the embodiments of this application, the terminal performs the first operation based on the first status or based on the first status and the second status, where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status. In this way, a DRX-related operation can be determined based on the status of the reporting resource, the status of the sidelink feedback resource, and the feedback enablement status, thereby implementing a similar DRX mechanism in sidelink.
The following describes the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are only some rather than all of the embodiments of this application. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of this application shall fall within the protection scope of this application.
In the specification and claims of this application, the terms such as “first” and “second” are intended to distinguish between similar objects but do not necessarily indicate a specific order or sequence. It should be understood that the data used in this way is interchangeable in appropriate circumstances so that the embodiments of this application can be implemented in other orders than the order illustrated or described herein, and “first” and “second” are usually for distinguishing same-type objects but not limiting the number of objects, for example, a first object may be one or multiple. In addition, “and/or” in this specification and claims indicates at least one of connected objects, and the symbol “/” generally indicates that the associated objects are in an “or” relationship.
It should be noted that techniques described in the embodiments of this application are not limited to a Long Term Evolution (LTE) or LTE-Advanced (LTE-A) system, and may also be applied to various wireless communication systems, for example, Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and other systems. The terms “system” and “network” in the embodiments of this application are usually used interchangeably. Techniques described herein may be used in the aforementioned systems and radio technologies, and may also be used in other systems and radio technologies. In the following descriptions, a New Radio (NR) system is described for an illustration purpose, and NR terms are used in most of the following descriptions, although these technologies may also be applied to other applications than an NR system application, for example, the 6th Generation (6G) communication system.
The relay terminal 11 may also be referred to as a relay terminal device or relay user terminal (User Equipment (UE)), and the remote terminal 13 may be a remote terminal device or remote UE. The relay terminal 11 and the remote terminal 13 may be a terminal-side device, such as a mobile phone, a tablet computer, a laptop computer or a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a wearable device or Vehicle User Equipment (VUE), or Pedestrian User Equipment (PUE). The wearable device includes: a wrist band, earphones, glasses, or the like. It should be noted that specific types of the relay terminal 11 and the remote terminal 13 are not limited in the embodiments of this application. The network-side device 12 may be a base station or a core network. The base station may be referred to as a NodeB, an evolved NodeB, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a NodeB, an evolved NodeB (eNB), a home NodeB, a home evolved NodeB, a WLAN access point, a Wi-Fi node, a Transmitting Receiving Point (TRP), or another appropriate term in the art. Provided that a same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that in the embodiments of this application, the base station in the NR system is merely used as an example, and a specific type of the base station is not limited.
The Long Term Evolution (LTE) system supports SideLink (SL, or may also he referred to as side-link, sidelink, side link, or the like) from the 12th release, and terminals (UE) directly perform data transmission over sidelink without passing through network devices.
In an NR sidelink system, the UE sends Sidelink Control Information (SCI) through a Physical Sidelink Feedback CHannel (PSFCH) to schedule Physical Sidelink Shared CHannel (PSSCH) transmission for sending data; and may feed back a sidelink Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) on the Physical Sidelink Feedback CHannel (PSFCH).
The NR sidelink supports two resource allocation modes: Scheduled resource allocation mode (usually referred to as mode-1) and autonomous resource selection mode (usually referred to as mode-2). In the former mode, the network-side device controls and allocates resources for each UE, and in the latter mode, resources are autonomously selected by UEs.
In mode-1, the base station may schedule SL resources for the terminal by sending SL Downlink Control Information (DCI), or configure SL resources for the terminal by configuring a Configured Grant (CG). In addition, a Physical Uplink Control CHannel (PUCCH) resource may be also configured or indicated for the terminal, and the terminal reports obtained sidelink HARQ-ACK information to the base station on the PUCCH, so as to help the base station make subsequent scheduling decision. Using an SL resource being scheduled by SL DCI as an example, the SL DCI schedules the SL resource located in slot n for the terminal, and after using this resource for SL transmission, the terminal receives a HARQ-ACK feedback on a corresponding PSFCH resource and reports the HARQ-ACK feedback to the base station on a subsequent PUCCH resource. The base station determines, based on content of the report, whether retransmission needs to be scheduled.
To reduce power consumption of the SL UE, the DRX mechanism may be introduced to SL. The existing DRX mechanism for Uu PDCCH is referred to as a Uu DRX mechanism. DRX at the Uu interface for SL UE is referred to as bs-scheduled Uu DRX, DRX used for sidelink may be referred to as SL DRX, and DCI for scheduling sidelink resources by the base station may be referred to as SL DCI. SL DCI may be DCI that is scheduled using SL related RNTI, or DCI format 3-0 or 3-1. Uu DCI is DCI for scheduling Uu transmission or Uu RS, or DCI that indicates a resource format or transmit power or resource preemption status of Uu, for example, DCI format 0-x, DCI format 1-x, or DCI format 2-x, where x is a natural number.
DRX described in the embodiments of this application may be at least one of Uu DRX, bs-scheduled Uu DRX, and SL DRX.
The following describes in detail a transmission control method provided in the embodiments of this application by using some embodiments and application scenarios thereof with reference to the accompanying drawings.
S210: A terminal performs a first operation based on a first status or based on the first status and a second status.
The first operation is an operation related to Discontinuous Reception (DRX).
The first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
In this embodiment of this application, the reporting resource is a Physical Uplink Control CHannel. (PUCCH) and/or Physical Uplink Shared CHannel (PUSCH) resource for sending SL-related HARQ-ACK and/or CSI to a control node.
In this embodiment of this application, the sidelink feedback resource is a feedback resource on SL, for example, including but not limited to a PSFCH.
In this embodiment of this application, the first operation may include but is not limited to operations such as starting or not starting a DRX-related timer, and/or whether to monitor for the target control information, and/or whether to enter an inactive time, and/or whether to enter an active time. For example, in some implementations, the first operation may include at least one of the following:
The first timer may he a timer with a running period being an inactive time, and the first timer may include a HARQ Round Trip Time (RTT) timer. That is, the terminal does not need to monitor control signaling and/or data during running of the first timer, and/or the first timer is a HARQ RTT timer.
The second timer is a timer with a running period being an active time, that is, the terminal monitors control signaling and/or data during running of the second timer. The second timer is a retransmission timer. For example, the second timer may include at least one of the following: an inactivity timer (where the terminal enters an inactive time after this timer expires), a retransmission timer, and an on-duration timer (on duration timer).
In this embodiment of this application, the terminal may be a terminal for which the control node schedules an SL: resource, for example, mode-1 UE. In some implementations, the terminal may be an SL terminal within serving coverage of the control node, for example, at least one of mode-2 UE in idle state, mode-2 UE in connected state, mode-1 UE, and the like within the coverage.
The control node may be a network-side device, for example, an eNB, a gNB, a roadside unit, a terminal with a scheduling or control capability, or a header terminal.
In the transmission control method provided in this embodiment of this application, the terminal performs the first operation based on the first status or based on the first status and the second status, where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status. In this way, a DRX-related operation can be determined based on the status of the reporting resource, and the status of the sidelink feedback resource and/or the feedback enablement status, thereby implementing a DRX mechanism in sidelink.
In some implementations, the first status includes at least one of the following (I) to (IV):
(I) No reporting resource is obtained. For example, the base station does not provide a PUCCH Configuration (PUCCH Config) for the terminal, or no configuration information for PUCCH is included in the SL CG configuration,
(II) The reporting resource satisfies a first condition. For example, the reporting resource obtained by the terminal satisfies the first condition. In a case that the first condition is satisfied, it can be determined that the reporting resource is unusable.
In some implementations, the reporting resource satisfying the first condition includes but is not limited to at least one of the following (1) to (20).
(1) No reporting resource has been scheduled, For example, no PUCCH is scheduled by SL DCI.
(2) SL DCI indicates absence of the reporting resource. For example, absence of the PUCCH is indicated in SL DCI.
(3) The reporting resource is not indicated in SL DCI. For example, the PUCCH is not indicated in SL DCI.
(4) The reporting resource is not included in SL CG configuration. For example, configuration information for PUCCH is not included in the SL CG configuration.
(5) SL CG configuration indicates absence of the reporting resource. For example, SL CG configuration indicates absence of configuration information for PUCCH.
(6) At least part of resources indicated by SL CG or SL DCI is not used. Based on the at least part of resources indicated by SL CG or SL DCI, it can be determined that corresponding reporting resources are also unusable. For example, all of the resources indicated by the SL CG or SL DCI are not used.
(7) Transmission of at least part of resources indicated by SL CG or SL DCI is dropped. For example, transmission of at least part of the resources indicated by SL CG or SL DCI is dropped due to a conflict with other transmissions.
(8) Transmission of at least part of resources indicated by SL CG or SL DCI is cancelled. For example, transmission of at least part of the resources indicated by SL CG or SL DCI is cancelled due to a conflict with other transmissions.
(9) A priority of at least part of resources indicated by SL CG or SL DCI is a first priority, where the first priority is a given or specific priority.
(10) A priority of at least part of resources indicated by SL CG or SL DCI is decreased (deprioritized). For example, when a larger priority value corresponds to a lower priority, a method for decreasing the priority is to increase its priority value.
(11) A priority of at least part of resources indicated by SL CG or SL DCI is a second value. For example, at least part of the resources indicated by the SL CG or SL DCI cannot be used because the priority of at least part of the resources indicated by the SL CG or SL DCI is lower than the second value, not satisfying a prioritized transmission condition.
(12) At least part of resources indicated by SL CG or SL DCI has no corresponding priority. For example, at least part of the resources indicated by the SL CG or the SL DCI has no corresponding Uu priority, or at least part of the resources indicated by the SL CG or the SL DCI has no corresponding sidelink priority; therefore, the corresponding reporting resources cannot be used for reporting.
(13) At least part of resources indicated by SL CG or SL DCI is invalid.
In the foregoing statuses (6) to (13), unusability of the reporting resource may be indirectly resulted.
(14) Transmission of the reporting resource is canceled. For example, transmission of the reporting resource is canceled due to a conflict with other transmissions.
(15) Transmission of the reporting resource is dropped. For example, transmission of the reporting resource conflicts with other resources and the reporting resource is dropped.
(16) A priority of the reporting resource is a second priority, where the second priority is a given or specific priority.
(17) A priority of the reporting resource has been decreased (deprioritized). For example, if the reporting resource conflicts with other resources, the priority of the reporting resource is decreased, resulting in the reporting resource being unusable for a period of time. For example, when a larger priority value corresponds to a lower priority, a method for decreasing the priority is to increase its priority value.
(18) A priority of the reporting resource is lower than a first value. For example, the reporting resource is unusable because the priority of the reporting resource is lower than the first value, not meeting a prioritized transmission condition,
(19) The reporting resource has no corresponding priority. For example, the reporting resource does not have a corresponding Uu priority, or the reporting resource has no corresponding sidelink priority, so that the reporting resource cannot be used for reporting SL HARQ ACK.
(20) The reporting resource is invalid. For example, the PUCCH is invalid and therefore cannot be used for transmission.
(III) The reporting resource having been configured, For example, the base station provides PUCCH Config, or the SL CG configuration includes information about the PUCCH and the PUCCH has been indicated or scheduled or expected to be transmitted normally. In this implementation, the sidelink feedback resource or a configuration of the sidelink feedback resource can be obtained by default in this status.
(IV) The reporting resource having been scheduled. For example, the PUCCH has been scheduled by SL DCI. In this implementation, the sidelink feedback resource or a configuration of the sidelink feedback resource can be obtained by default in this status.
In an implementation, a reporting resource being configured or a reporting resource being scheduled may include at least one of the following (1) to (7):
(1) The reporting resource is obtained. For example, the terminal has obtained a PUCCH resource.
(2) A configuration for the reporting resource is obtained. For example, the terminal has obtained a configuration of the PUCCH resource, for example, the terminal has obtained a PUCCH configuration or an SL CG configuration that includes information about the PUCCH.
(3) The reporting resource being scheduled. For example, the PUCCH has been scheduled by SL DCI.
(4) The reporting resource having been indicated by SL DCI. For example, the PUCCH has been indicated by SL DCI.
(5) Presence of the reporting resource having been indicated by SL DCI. For example, presence of the PUCCH has been indicated by SL DCI.
(6) The reporting resource being included in SL CG configuration. For example, the PUCCH is included in the SL CG configuration.
(7) Presence of the reporting resource having been indicated by SL CG configuration. For example, presence of the PUCCH is indicated in the SL CG configuration.
In an implementation, the status of the sidelink feedback resource includes at least one of the following (I) to (V):
In some implementations, the feedback enablement status includes at least one of the following (I) and (II):
In some implementations, that the terminal performs the first operation based on the first status and the second status may include:
The second sub-status includes at least one of the following:
The first operation includes at least one of the following (1) to (6):
(1) Starting a first timer and/or entering an inactive time,
In this embodiment of this application, the first timer may be a timer with a running period being an inactive time, and the first timer may include a HARQ RTT timer. That is, the terminal does not need to monitor control signaling and/or data during running of the first timer, and/or the first timer is a HARQ RTT timer.
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, retransmission scheduling is required by default (which, for example, may be specified by the protocol or preconfigured) and therefore the terminal starts the first timer and/or enters the inactive time to reduce power consumption.
(2) Not starting the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering an active time.
The second timer is a timer with a running period being an active time, that is, the terminal monitors control signaling and/or data during running of the second timer. The second timer is a retransmission timer. For example, the second timer may include at least one of the following: an inactivity timer (where the terminal enters an inactive time after this timer expires), a retransmission timer, and an on-duration timer (on duration timer).
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, retransmission scheduling based on HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer and the first timer may not be started. Further, the terminal may start the second timer and/or does not enter the inactive time and/or enters the active time and/or stops the inactive time, so as to monitor control signaling and/or data.
(3) Determining that an obtained discontinuous reception DRX configuration does not include a first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, retransmission scheduling based on HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer and it can be determined that the obtained discontinuous reception DRX configuration does not include the first timer. Further, the terminal may start the second timer and/or does not enter the inactive time and/or enters the active time and/or stops the inactive time, so as to monitor control signaling and/or data.
(4) Disabling the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, retransmission scheduling based on HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer and the first timer may be disabled. Further, the terminal may start the second timer and/or does not enter the inactive time and/or enters the active time and/or stops the inactive time, so as to monitor control signaling and/or data.
(5) Closing the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, retransmission scheduling based on HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer and the first timer may be closed. Further, the terminal may start the second timer and/or does not enter the inactive time and/or enters the active time and/or stops the inactive time, so as to monitor control signaling and/or data.
(6) Not monitoring target control information.
For example, if no PUCCH is configured or a PUCCH is configured but cannot be used, and if a PSFCH is configured, the RTT timer is started or the RTT timer is not started or SL DCI is not monitored or Uu DCI is not monitored.
In some implementations, the terminal may not monitor for the target control information for a period of time after start of a specific time point.
In some implementations, the target control information includes but is not limited to target DCI and/or target SCI. In some implementations, the target DCI includes at least one of the following: SL DCI and Uu DCI.
In some implementations, in a case that the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, and/or feedback is enabled or feedback is disabled, but no reporting resource is obtained or the reporting resource cannot be used, the network-side device may not perform retransmission scheduling by default (which, for example, may be specified by the protocol or preconfigured) in a period of time and therefore the terminal may not monitor for the target control information to reduce power consumption of the terminal,
In some implementations, at least one of the first timer and the second timer may be a timer configured for Uu DRX or a timer configured for SL DRX.
In some implementations, the terminal may perform the first operation at a first time, that is, the terminal performs the first operation when the first time arrives.
In some implementations, the first time may be a time corresponding to Uu DRX configuration or SL DRX configuration. In some implementations, the first time may include at least one of the following:
In some implementations, the first offset and the second offset may be one symbol or one slot. For example, the first time is a next symbol or next slot of the first target time. For example, if the first target time is a time at which the NACK is received or a time of the sidelink feedback resource, one implementation is that the first time is a next symbol or a next slot of the time at which the NACK is received or the time of the sidelink feedback resource.
In some implementations, the first target time may include at least one of the following (1) to (7):
(1) A time of preset SL DCI, for example, a tune of SL DCI obtained by the terminal.
(2) A time of a preset transmission;
(3) A time of the preset sidelink feedback resource;
(4) A start time or end time of a period of preset sidelink grant;
(5) A time at which negative-acknowledgement information is sent or received; that is, a time point at which the terminal sends a NACK or receives a NACK.
(6) A time at which a transmission failure is determined; for example, a time point at which the terminal determines a transmission failure.
(7) A time corresponding to a preset reporting resource, for example, a time corresponding to a reporting resource obtained by the terminal. This applies to a case that the first status includes the reporting resource being unusable.
An example is a time corresponding to a reporting resource indicated in the SL DCI or a reporting resource included in the SL CG configuration.
It should be noted that if the first target time includes a plurality of the above items, it is indicated that the terminal performs the first operation at the corresponding plurality of first times.
For example, the RTT timer is started at a time point A (that is, the first time), where the time point A may be a time point at which at least one of SL DCI, PSCCH, PSSCH, and PSFCH is located, or a time point corresponding to an offset prior to or behind the time point at which at least one of SL PSCCH, PSSCH, and PSFCH is located.
In some implementations, that the terminal performs the first operation based on the first status and the second status includes: in a case the first status is a first sub-status and the second status is a third sub-status, the terminal performs the first operation.
Same as the first sub-status in the foregoing implementation, the first sub-status in the implementation includes one of the following: no reporting resource being obtained and the reporting resource satisfying a first condition. The third sub-status may include at least one of the following: no sidelink feedback resource is obtained, no configuration of sidelink feedback resource is obtained, or the sidelink feedback resource satisfies a second condition; and feedback is enabled or feedback is disabled.
In the foregoing implementation, the first operation includes at least one of the following (1) to (5):
(1) Not starting the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
The first timer and the second timer in this implementation are the same as the first timer and the second timer in the foregoing implementation. For details, reference may be made to the descriptions in the foregoing implementation, and details are not repeated herein.
In some implementations, if no reporting resource or sidelink feedback resource is obtained, or an obtained reporting resource is unusable and no configuration of the sidelink feedback resource is obtained, it indicates that retransmission and retransmission scheduling based on the HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer. In this case, the first timer is not started.
In addition, no reporting resource or sidelink feedback resource is obtained; therefore, it cannot be determined at what time retransmission and retransmission scheduling are to be performed. In this way, the second timer may be directly started for monitoring, and/or the inactive time is not entered, and/or the active time is entered, and/or the inactive time is stopped, so as to perform monitoring.
Further, if the terminal has not received the control signaling and/or data from the network-side device until the second timer expires, it indicates that the network-side device may have no intention to continue scheduling, and therefore the terminal may no longer monitor the control channel and/or data, and/or enters dormancy to reduce power consumption.
(2) Determining that an obtained discontinuous reception DRX configuration does not include a first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, determining that no RTT timer is included in the DRX configuration may mean that the RTT timer is not required.
In some implementations, if no reporting resource or sidelink feedback resource is obtained, or an obtained reporting resource is unusable and no configuration of the sidelink feedback resource is obtained, it indicates that retransmission and retransmission scheduling based on the HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer. In this way, determining that no RTT timer is included in the DRX configuration may be determining that the RTT timer is not required.
In addition, no reporting resource or sidelink feedback resource is obtained; therefore, it cannot be determined at what time retransmission and retransmission scheduling are to be performed. In this way, the second timer may be directly started for monitoring, and/or the inactive time is not entered, and/or the active time is entered, and/or the inactive time is stopped, so as to perform monitoring.
Further, if the terminal has not received the control signaling and/or data from the network-side device until the second timer expires, it indicates that the network-side device may have no intention to continue scheduling, and therefore the terminal may no longer monitor the control channel and/or data, and/or enters dormancy to reduce power consumption,
(3) Disabling the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, if no reporting resource or sidelink feedback resource is obtained, or an obtained reporting resource is unusable and no configuration of the sidelink feedback resource is obtained, it indicates that retransmission and retransmission scheduling based on the HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer. In this case, the first timer is disabled.
In addition, no reporting resource or sidelink feedback resource is obtained; therefore, it cannot be determined at what time retransmission and retransmission scheduling are to be performed. In this way, the second timer may be directly started for monitoring, and/or the inactive time is not entered, and/or the active time is entered, and/or the inactive time is stopped, so as to perform monitoring.
Further, if the terminal has not received the control signaling and/or data from the network-side device until the second timer expires, it indicates that the network-side device may have no intention to continue scheduling, and therefore the terminal may no longer monitor the control channel and/or data, and/or enters dormancy to reduce power consumption,
(4) Closing the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
In some implementations, if no reporting resource or sidelink feedback resource is obtained, or an obtained reporting resource is unusable and no configuration of the sidelink feedback resource is obtained, it indicates that retransmission and retransmission scheduling based on the HARQ-ACK feedback cannot be implemented, and therefore there is no need to use or start the RTT timer. In this case, the first timer is closed.
In addition, no reporting resource or sidelink feedback resource is obtained; therefore, it cannot be determined at what time retransmission and retransmission scheduling are to be performed. In this way, the second timer may be directly started for monitoring, and/or the inactive time is not entered, and/or the active time is entered, and/or the inactive time is stopped, so as to perform monitoring.
Further, if the terminal has not received the control signaling and/or data from the network-side device until the second timer expires, it indicates that the network-side device may have no intention to continue scheduling, and therefore the terminal may no longer monitor the control channel and/or data, and/or enters dormancy to reduce power consumption.
(5) Starting a first timer and/or entering an inactive time.
In some implementations, no reporting resource is obtained or the reporting resource is unusable, and therefore retransmission scheduling is required by default (which may, for example, be specified by the protocol or preconfigured). In this way, to reduce power consumption, the terminal starts the first timer and/or enters the inactive time, and after the first timer expires, monitors retransmission scheduling information.
For example, the UE starts the RTT timer at a time point A, where the time point A may be a time point at which SL DCI, PSCCH, and PSSCH are located, or a time point corresponding to an offset prior to or behind the time point at which SF DCI, PSCCH, and PSSCH are located.
For example, if no PUCCH is configured or if the PUCCH is configured but is unusable, and if no PSFCH is configured, the terminal does not start the RTT timer.
In some implementations, that the terminal performs the first operation may include: performing the first operation within a second time, where the second time includes one of the following: a first target time, a sum of the first target time and a third offset, and a difference between the first target time and a fourth offset.
That is, the terminal may perform the first operation when the second time arrives. That is, the terminal performs the first operation at a time point corresponding to the second time.
In some implementations, the second time may be a time corresponding to Uu DRX configuration or SL DRX configuration.
The first target time is the same as the first target time In some implementations. For details, reference may be made to the descriptions In some implementations, and details are not repeated herein.
In some implementations, the third offset and the fourth offset are one symbol or one slot. For example, the second time is a next symbol or next slot of the first target time. For example, if the first target time is a time at which the NACK is received or a time of the sidelink feedback resource, one implementation is that the second time is a next symbol or a next slot of the time at which the NACK is received or the time of the sidelink feedback resource.
In still another implementation, that the terminal performs the first operation based on the first status and the second status includes: in a case the first status is a fourth sub-status, the terminal performs the first operation.
The fourth sub-status includes: a reporting resource is configured or a reporting resource is scheduled. For details about the status of a reporting resource being configured or a reporting resource being scheduled, reference may be made to the descriptions according to some implementations.
The first operation includes at least one of the following (1) and (2):
(1) Starting a first timer and/or entering an inactive time.
For example, the UE starts the RTT timer at a time point A, where the time point A may be a time point at which SL DCI, PSCCH, PSSCH, PSFCH, PUCCH, or PUSCH is located, or a time point corresponding to an offset prior to or behind the time point at which SL DCI, PSCCH, PSSCH, PSFCH, PUCCH, or PUSCH is located.
(2) Not monitoring target control information.
The target control information is the same as the target control information in some implementations. For details, reference may be made to the foregoing description of the target control information, and details are not repeated herein.
In some implementations, the terminal may not monitor for the target control information for a period of time after start of a specific time point, for example, for a period of time starting from a time point B, the UE does not monitor for Uu DCI and/or SL DCI, and/or enters dormancy, to reduce power consumption.
In some implementations, in the fourth sub-status, it is considered by default that the second status is the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained. For example, PSFCH or a configuration for PSFCH is obtained.
In some implementations, in a case that the first status is the fourth sub-status and the second status is the sidelink feedback resource is obtained or a configuration of the sidelink feedback resource is obtained, the first operation is performed.
For example, in a case that PUCCH is configured or PUCCH is scheduled (In some implementations, in this case, it can be considered that a PSFCH has been configured), the terminal starts the RTT timer.
In some implementations, the terminal may perform the first operation when the third time arrives. The third time may include one of the following: a second target time, a sum of the second target time and a fifth offset, and a difference between the second target time and a sixth offset.
In some implementations, the fifth offset and the sixth offset may be one symbol or one slot. For example, the third time is a next symbol or next slot of the second target time. For example, if the second target time is a time at which the NACK is received or a time of the sidelink feedback resource, one implementation is that the third time is a next symbol or a next slot of the time at which the NACK is received or the time of the sidelink feedback resource.
In some implementations, the second target time includes at least one of the following:
It should be noted that the above embodiments merely describe part of behaviors or a combination of part of behaviors included in the first operation in a case of the first status being a specific status or the first status being a specific status and the second status being a specific status, which is not limited thereto. In specific applications, the first operation may further include a combination of other behaviors. Details are not limited in this embodiment of this application.
It should be noted that the above describes the first operation performed by the terminal in several specific statuses of the reporting resource, sidelink feedback resource, and feedback being enabled, which is not limited thereto. In other specific statuses not given, the terminal may determine, based on the first status or based on the first status and the second status, the first operation to be performed.
Table 1 lists the first operation that may be performed by the terminal in various statuses in an optional implementation of this embodiment of this application.
In the table, N.A. indicates that such a status (or referred to as a combination thereof) may not be present, or such as status is an error case, or the terminal does not expect occurrence of such a status.
S310: A network-side device performs a second operation based on a third status or based on the third status and a fourth status.
The second operation is an operation related to DRX.
The third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
The transmission control method 300 provided in the embodiments of this application is steps of a network-side device method corresponding to the method 200, and has the same or corresponding implementations as in the method 200. The following mainly describes part of the method 300 that is different from the method 200. For other parts that are the same or corresponding ports, reference may be made to the related description of the method 200.
In some implementations, similar to the first status in the method 200, the third status may include at least one of the following (I) to (IV).
(I) The reporting resource having not been configured.
For example, the network-side device does not provide a PUCCH configuration for the terminal, or SL CG configuration configured for the terminal by the network-side device includes no information about PUCCH.
(II) The reporting resource satisfies a first condition. For example, the reporting resource configured by the network-side device for the terminal satisfies the first condition. In a case that the reporting resource satisfies the first condition, the reporting resource is unusable.
In some implementations, the reporting resource satisfying the first condition may include at least one of the following (1) to (20).
(1) No reporting resource has been scheduled. For example, no PUCCH is scheduled in the SL DCI sent by the network-side device to the terminal.
(2) Sidelink DCI indicates absence of the reporting resource. For example, absence of the PUCCH is indicated in the SL DCI sent by the network-side device to the terminal.
(3) The reporting resource is not indicated in sidelink DCI. For example, the PUCCH is not indicated in the SL DCI sent by the network-side device to the terminal.
(4) The reporting resource is not included in SL CG configuration. For example, the PUCCH is not included in the SL CG configuration configured by the network-side device for the terminal.
(5) SL CG configuration indicates absence of the reporting resource. For example, absence of the PUCCH is indicated in the SL CG configuration configured by the network-side device for the terminal.
(6) At least part of resources indicated by SL CG or SL DCI is not used. For example, all of the resources indicated by SL CG or SL DCI are invalid.
(7) Transmission of at least part of resources indicated by SL CG or SL DCI is dropped.
(8) Transmission of at least part of resources indicated by SL CG or SL DCI is cancelled.
(9) A priority of at least part of resources indicated by SL CG or SL DCI is a first priority.
(10) A priority of at least part of resources indicated by SL CG or SL DCI is decreased.
(11) A priority of at least part of resources indicated by SL CG or SL DCI is a second value.
(12) At least part of resources indicated by SL CG or SL DCI has no corresponding priority.
(13) At least part of resources indicated by SL CG or SL DCI is invalid.
(14) Transmission of the reporting resource is canceled. For example, the PUCCH transmission conflicts with other transmissions such that the PUCCH transmission is canceled.
(15) Transmission of the reporting resource is dropped. For example, the PUCCH resource overlaps with resources of other transmissions such that the PUCCH resource is dropped.
(16) A priority of the reporting resource is a second priority.
(17) A priority of the reporting resource has been decreased. For example, the PUCCH resource overlaps with resources of other transmissions and the priority of the PUCCH resource is decreased; therefore, the transmission cannot be implemented.
(18) A priority of the reporting resource is lower than a first value. For example, the priority of the PUCCH is lower than the first value and does not meet a prioritized transmission condition; therefore, the PUCCH transmission cannot be implemented.
(19) The reporting resource has no corresponding priority. For example, the reporting resource does not have a corresponding Uu priority, or, the reporting resource does not have a corresponding sidelink priority, so that the reporting resource cannot be used for reporting SL HARQ ACK.
(20) The reporting resource is invalid. For example, the PUCCH is invalid and therefore cannot be used for transmission.
(III) The reporting resource having been configured. For example, the network-side device provides a PUCCH configuration to the terminal, or the SL CG configuration configured by the network-side device for the terminal includes information about the PUCCH and indicates or schedules or expects to normally transmit the PUCCH. In some implementations, the sidelink feedback resource or a configuration of the sidelink feedback resource can be obtained by default in this status.
(IV) The reporting resource having been scheduled, For example, the PUCCH has been scheduled by SL DCI. In some implementations, the sidelink feedback resource or a configuration of the sidelink feedback resource can be obtained by default in this status.
In some implementations, a reporting resource being configured or a reporting resource being scheduled may include at least one of (1) to (6):
(1) The reporting resource having been configured. For example, the network-side device provides a PUCCH configuration for the terminal, or SL CG configuration configured for the terminal by the network-side device includes information about the PUCCH.
(2) The reporting resource being scheduled. For example, the PUCCH is scheduled by the SL DCI sent by the network-side device.
(3) The reporting resource having been indicated by SL DCI. For example, the PUCCH has been indicated by SL DCI.
(4) Presence of the reporting resource having been indicated by SL DCI. For example, presence of the PUCCH has been indicated by SL DCI.
(5) The reporting resource being included in SL CG configuration. For example, the PUCCH is included in the SL CG configuration.
(6) Presence of the reporting resource having been indicated by SL CG configuration, example, presence of the PUCCH is indicated in the SL CG configuration.
In some implementations, the status of the sidelink feedback resource includes at least one of the following (I) to (III):
(I) The sidelink feedback resource having been configured. For example, the network-side device configures a PSFCH in the SL DCI.
(II) No configuration of sidelink feedback resource having been configured. For example, the network-side device configures no PSFCH in the SL DCI.
(III) The sidelink feedback resource satisfies a second condition. For example, the sidelink feedback resource configured by the network-side device for the terminal satisfies the second condition. The sidelink feedback resource satisfying the second condition may indicate that the sidelink feedback resource is unusable. In some implementations, the sidelink feedback resource satisfying the second condition may include at least one of the following:
In some implementations, the feedback enablement status includes at least one of the following:
(I) Feedback been enabled, where for example, SL HARQ-ACK is enabled, or no logical channel (or logical channel group) with feedback being disabled is configured, or feedback is enabled for all configured logical channels (or logical channel group), or at least one logical channel (or logical channel group) with feedback being enabled is configured.
(II) Feedback being disabled, where for example, SL HARQ-ACK is disabled, or no logical channel (or logical channel group) with feedback being enabled is configured, or feedback is disabled for all configured logical channels (or logical channel group).
In some implementations of S310, the network-side device performs the second operation in a case that the third status is a fifth sub-status and the fourth status is a sixth sub-status, where the second operation includes one of the following (1) to (6):
(1) Determining to start a first timer and/or determining to enter an inactive time; where the network-side device determining to start the first timer may be the network-side device determining to start a first timer of the terminal, or the network-side device may set one first timer for the terminal, and the network-side device determining to start the first timer is the network-side device starting the first timer. The network-side device determining to enter the inactive time means that the network-side device determines that the terminal enters the inactive time, and during the inactive time, the network-side device does not transmit control signaling and/or data to the terminal.
In some implementations, the network-side device does not need to transmit control signaling and/or data during running of the first timer; and/or the first timer is a HARQ RTT timer.
(2) Determining not to start the first timer, and/or determining not to enter the inactive time, and/or determining to start the second timer, and/or determining to enter the active time, and/or stopping the inactive time.
The network-side device determining not to start the first timer may be the network-side device determining not to start a first timer of the terminal, or the network-side device may set one first timer for the terminal, and the network-side device determining not to start the first timer is the network-side device not starting the first timer. The network-side device determining not to enter the inactive time means that the network-side device determines that the terminal does not enter the inactive time, and the network-side device may transmit control signaling and/or data to the terminal.
Similarly, the network-side device determining to start the second timer may be the network-side device determining to start a second timer of the terminal, or the network-side device may set one second timer for the terminal, and the network-side device determining to start the second timer is the network-side device starting the second timer.
In some implementations, the network-side device does not need to transmit control signaling and/or data during running of the second timer; and/or the second timer is a retransmission timer.
(3) Determining that a configured DRX configuration does not include a first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
(4) Determining to disable the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
The network-side device determining to disable the first timer may be the network-side device determining to disable a first timer of the terminal, or the network-side device may set one first timer for the terminal, and the network-side device determining to disable the first timer is disabling the first timer of the network-side device.
(5) Determining to stop the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
The network-side device determining to stop the first timer may be the network-side device determining to stop a first timer of the terminal, or the network-side device may set one first timer for the terminal, and the network-side device determining to disable the first timer is stopping the first timer of the network-side device.
(6) Not transmitting target control information.
The fifth sub-status includes one of the following: no reporting resource is configured and a reporting resource satisfies a first condition.
The sixth sub-status includes at least one of the following: the sidelink feedback resource is configured; and feedback is enabled or feedback is disabled.
In some implementations, the network-side device may perform the second operation when the first time arrives, where the first time includes one of the following: a first target time, a sum of the first target time and a first offset, and a difference between the first target time and a second offset.
The first time is the same as or corresponding to the first time in the method 200. For details, refer to the description in the method 200.
In some implementations of S310, the network-side device performs the second operation in a case that the third status is a fifth sub-status and the fourth status is a seventh sub-status. The second operation includes one of the following (1) to (5):
(1) Determining not to start the first timer, and/or determining not to enter the inactive time, and/or determining to start the second timer, and/or determining to enter the active time, and/or stopping the inactive time.
(2) Determining that an obtained DRX configuration does not include a first
timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
(3) Determining to disable the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time,
(4) Determining to stop the first timer, and/or not entering the inactive time, and/or starting the second timer, and/or entering the active time, and/or stopping the inactive time.
(5) Determining to start a first timer and/or entering an inactive time.
The meanings of determining to start the first timer, not starting the first timer, and starting the second timer are the same as those implementations, and details are not repeated herein.
The fifth sub-status includes one of the following: no reporting resource is configured and a reporting resource satisfies a first condition.
The seventh sub-status includes at least one of the following: no sidelink feedback resource having been configured or the sidelink feedback resource satisfies a second condition; and feedback is enabled or feedback is disabled.
In some implementations, the network-side device may perform the second operation at a second time (that is, when the second time arrives). The second time includes one of the following: a first target time, a sum of the first target time and a third offset, and a difference between the first target time and a fourth offset.
The second time is the same as or corresponding to the second time in the method 200, and details are not repeated herein.
In some implementations, the first target time may include at least one of the following (1) to (7).
(1) A time of preset sidelink DCI; for example, a time for SL DCI sent by the network-side device.
(2) A time of a preset transmission, for example, a time at which the N-th transmission (for example, the first or the last transmission) in a grant provided in the SL DCI sent by the network-side device is located. In some implementations, the transmission may be a PSCCH or first-stage SCI, for example, SCI format 1-A. In some implementations, the transmission may be second-stage (2nd stage) SCI, for example, SCI format 2-A or SCI format 2-B. In some implementations, the transmission may be PSSCH.
(3) A time of the preset sidelink feedback resource; for example, a time at which
a sidelink feedback resource corresponding to the M-th transmission (for example, the first or the last transmission) in a grant provided in the SL DCI sent by the network-side device is located, for example, a time at which a PSFCH corresponding to a transmission is located.
(4) A start time or end time of a period of preset sidelink grant; for example, a start time or end time of a period of sidelink grant provided in the SL DCI sent by the network-side device.
(5) A time at which negative-acknowledgement information has been received.
(6) A time at which a scheduling failure occurs.
(7) A time corresponding to a preset reporting resource, for example, a time corresponding to a PUCCH configuration provided by the network-side device to the terminal. This applies to a case that the third status includes the reporting resource being unusable.
In some implementations of S310, the network-side device performs the second operation in a case that the third status is an eighth sub-status, where the second operation includes at least one of the following (1) and (2):
(1) Determining to start a first timer and/or determining to enter an inactive time.
Determining to start the first timer has the same meaning as that in some implementations, and details are not repeated herein.
(2) Not transmitting target control information.
The eighth sub-status includes: a reporting resource is configured or a reporting resource is scheduled.
In some implementations, in a case that the third status is the eighth sub-status, the sidelink feedback resource may be configured by default, for example, a PSFCH has been configured. In some implementations, the second operation may be performed in a case that the third status is the eighth sub-status and the fourth status is the sidelink feedback resource having been configured.
In some implementations, the network-side device may perform the second operation at a third time (that is, when the third time arrives). The third time includes one of the following: a second target time, a sum of the second target time and a fifth offset, and a difference between the second target time and a sixth offset.
The third time is the same as or corresponding to the third time in the method 200. For details, refer to the description in the method 200.
In some implementations, the second target time includes at least one of the following (1) to (3):
(1) A start time or end time of a period of preset sidelink grant; for example, a start time or end time of a period of sidelink grant provided in the SL DCI sent by the network-side device.
(2) A time at which negative-acknowledgement feedback information has been received.
(3) A time corresponding to the preset reporting resource, for example, a time corresponding to a PUCCH configuration provided by the network-side device to the terminal.
In some implementations, the target control information may include: target DCI and/or target SCI: where the target DCI includes at least one of the following: sidelink DCI and Uu DCI.
In the following embodiments, the transmission control method provided in the embodiments of this application is described by using the reporting resource being a PUCCH or a PUSCH and the sidelink feedback resource being a PSFCH as an example.
In this embodiment, the UE is not configured with PUCCH or PUSCH, and is neither configured with PSFCH.
Step 1: During configuration for the UE, the base station does not configure, for the UE, a PUCCH or PUSCH resource for reporting HARQ feedback related to a UE sidelink process.
Step 2: The base station configures no PSFCH resource for the UE and/or neither configures any HARQ-enabled logical channel for the UE.
During some implementations, a sequence of steps 1 and 2 is not fixed.
Step 3: The UE performs at least one of the following behaviors:
In this embodiment, the UE is not configured with a PUCCH or PUSCH, but is configured with a PSFCH.
Step 1: The base station does not configure, for the UE, a PUCCH or PUSCH resource for reporting HARQ feedback related to a UE sidelink process.
Step 2: The base station configures a PSFCH resource for the UE and/or configures at least one: HARQ-enabled logical channel for the UE.
In some implementations, a sequence of steps 1 and 2 is not fixed.
In step 3, the UE starts the HARQ RTT timer at the following time points:
Step 4: The UE starts the retransmission timer after the HARQ RTT timer expires.
In this embodiment, the UE is not configured with a PUCCH or PUSCH but is configured with a PSFCH, the HARQ RTT timer is not started, and the retransmission timer may be started.
Step 1: same as step 1 in Embodiment 2.
Step 2: same as step 2 in Embodiment 2.
Step 3: same as step 3 in Embodiment 1.
In this embodiment, the UE is configured with a PUCCH, but is not configured with a PSFCH.
Step 1: The base station configures, for the UE, a PUCCH or PUSCH resource for reporting HARQ feedback related to a UE sidelink process.
Step 2: The base station configures no PSFCH resource for the UE and/or neither configures any HARQ-enabled logical channel for the UE.
In some implementations, a sequence of steps 1 and 2 is not fixed.
Step 3: The UE performs at least one of the following behaviors:
In this embodiment, the UE is configured with a PUCCH and also configured with a PSFCH, and the UE starts the HARQ RTT timer.
Step 1: The base station configures, for the UE, a PUCCH or PUSCH resource for reporting HARQ feedback related to a UE sidelink process.
Step 2: The base station configures a PSFCH resource for the UE and/or configures at least one HARQ-enabled logical channel for the UE.
In some implementations, a sequence of steps 1 and 2 is not fixed.
In step 3, the UE starts the HARQ RTT timer at the following time points:
Step 4: The UE starts the retransmission timer after the HARQ RTT timer expires.
Step 5: In some implementations, if the network-side device does not actually indicate or schedule a PUCCH or PUSCH, or a configured PUCCH is invalid or discarded or knocked out by other transmissions, the UE performs at least one of the following behaviors:
In this embodiment, the UE is configured with a PUCCH and also configured with a PSFCH, and the UE does not start the HARQ RTT timer.
Step 1: The base station configures, for the UE, a PUCCH or PUSCH resource for reporting HARQ feedback related to a UE sidelink process.
Step 2: The base station configures a PSFCH resource for the UE and/or configures at least one HARQ-enabled logical channel for the UE.
In some implementations, a sequence of steps 1 and 2 is not fixed.
Step 3: The UE performs at least one of the following behaviors:
Step 4: The UE starts the retransmission timer after the HARQ RTT timer expires.
It should be noted that, for the transmission control method provided by the embodiments of this application, the execution body may be a transmission control apparatus, or a control module for executing the transmission control method in the transmission control apparatus. In the embodiments of this application, the transmission control method being performed by the transmission control apparatus is used as an example to describe the transmission control apparatus provided in the embodiments of this application.
In this embodiment of this application, the first determining module 401 is configured to determine a first status, or the first status and a second status; and the first execution module 402 is configured to, based on the first status or based on the first status and the second status, perform a first operation related to DRX; where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
In some implementations, the first status includes at least one of the following:
In some implementations, the status of the sidelink feedback resource includes at least one of the following:
In some implementations, the feedback enablement status includes at least one of the following: feedback is enabled and feedback is disabled.
The terminal performs the first operation in a case that the first status is a first sub-status and the second status is a second sub-status, where the first operation includes one of the following:
In some implementations, that the first execution module 402 performs the first operation includes:
In some implementations, that the first execution module 402 performs the first operation based on the first status and the second status includes:
In some implementations, that the first execution module 402 performs the first operation includes:
In some implementations, the first target time includes at least one of the following:
In some implementations, the reporting resource having satisfied the first condition includes at least one of the following:
a priority of at least part of resources indicated by SL CG or SL DCI is a second value;
In some implementations, the sidelink feedback resource satisfying a second condition includes at least one of the following:
In some implementations, that the first execution module 402 performs the first operation based on the first status and the second status includes:
In some implementations, that the first execution module 402 performs the first operation includes:
In some implementations, the second target time includes at least one of the following:
In some implementations, a reporting resource being configured or a reporting resource being scheduled includes at least one of the following:
In some implementations, the target control information includes: target DCI and/or target SCI, where
In some implementations, the terminal does not need to monitor control signaling and/or data during running of the first timer; and/or the first timer is a HARQ RTT timer.
In some implementations, the terminal monitors control signaling and/or data during running of the second timer; and/or the second timer is a retransmission timer.
The transmission control apparatus in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in a terminal. The apparatus may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to the types of the terminal 11 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer, a television, a teller machine, a self-service machine, or the like, which is not specifically limited in this embodiment of this application.
The transmission control apparatus in this embodiment of this application may be an apparatus with an operating system. The operating system may be an Android operating system, an iOS operating system, or other operating systems, and is not specifically limited in the embodiments of this application.
The transmission control apparatus provided in this embodiment of this application can implement the processes implemented in the method embodiment in
In this embodiment of this application, the second determining module 501 is configured to determine a third status, or the third status and a fourth status; and the second execution module 502 is configured to, based on the third status or based on the third status and the fourth status, perform a second operation related to DRX; where the third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status.
In some implementations, the third status includes at least one of the following:
In some implementations, the status of the sidelink feedback resource includes at least one of the following:
In some implementations, the feedback enablement status includes at least one of the following: feedback is enabled and feedback is disabled.
In some implementations, that the second execution module 502 performs the second operation based on the third status and the fourth status includes:
In some implementations, that the second execution module 502 performs the second operation includes:
In some implementations, that the second execution module 502 performs the second operation based on the third status and the fourth status includes:
The fifth sub-status includes one of the following:
a reporting resource has not been configured; and
a reporting resource satisfies a first condition.
The seventh sub-status includes at least one of the following:
no sidelink feedback resource having been configured or the sidelink feedback resource satisfies a second condition; and
feedback is enabled or feedback is disabled.
In some implementations, that the second execution module 502 performs the second operation includes:
In some implementations, the first target time includes at least one of the following:
In some implementations, the reporting resource having satisfied the first condition includes at least one of the following:
In some implementations, the sidelink feedback resource satisfying a second condition includes at least one of the following:
In some implementations, that the second execution module 502 performs the second operation based on the third status and the fourth status includes:
In some implementations, that the second execution module 502 performs the second operation includes:
In some implementations, the second target time includes at east one of the following:
In some implementations, a reporting resource being configured or a reporting resource being scheduled includes at least one of the following:
In some implementations, the target control information includes: target downlink control information DCI and/or target Sidelink Control Information (SCI).
The target DCI includes at least one of the following: SL DCI and Uu DCI.
In some implementations, the network-side device does not need to transmit control signaling and/or data during running of the first timer; and/or the first timer is a HARQ RTT timer.
In some implementations, the network-side device transmits control signaling and/or data during running of the second timer; and/or the second timer is a retransmission timer.
The transmission control apparatus in this embodiment of this application may be an apparatus, or may be a component, an integrated circuit, or a chip in a network-side device. The network-side device may include but is not limited to an eNB, a gNB, a roadside unit, a terminal with a scheduling or control capability, a header terminal, or the like, which is not specifically limited in the embodiments of this application.
The transmission control apparatus in this embodiment of this application may be an apparatus with an operating system. The operating system may be an Android operating system, an iOS operating system, or other operating systems, and is not specifically limited in the embodiments of this application.
The transmission control apparatus provided in this embodiment of this application can implement the processes implemented in the method embodiment in
In some implementations, as shown in
An embodiment of this application further provides a terminal, including a processor and a communication interface, where the processor is configured to perform, based on a first status or based on the first status and a second status, a first operation related to DRX; where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status. The communication interface is configured to communicate with an external communication device. For example, the communication interface may include a PC5 interface, and sidelink communication may be performed with other terminals through the interface. For another example, the communication interface may include a Uu interface, and communication may be performed with a network-side device through the Uu interface. The terminal embodiments correspond to the foregoing terminal-side method embodiments, and the implementation processes and implementations of the foregoing method embodiments can be applied to the terminal embodiments, with the same technical effects achieved. In some implementations,
The terminal 700 includes but is not limited to components such as a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.
Persons skilled in the art can understand that the terminal 700 may further include a power supply (for example, a battery) supplying power to the components, and the power supply may be logically connected to the processor 710 through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system. The structure of the terminal shown in
It can be understood that in this embodiment of this application, the input unit 704 may include a Graphics Processing Unit (GPU) 7041 and a microphone 7042. The graphics processing unit 7041 processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in a form of a liquid crystal display, an organic light-emitting diode, and the like. The user input unit 707 may include a touch panel 7071 and other input devices 7072. The touch panel 7071 is also referred to as a touchscreen. The touch panel 7071 may include two parts: a touch detection apparatus and a touch controller. The other input devices 7072 may include but are not limited to a physical keyboard, a function key (such as a volume control key or a power on/off key), a trackball, a mouse, a joystick, and the like. Details are not described herein.
In this embodiment of this application, the radio frequency unit 701 receives downlink data from a network-side device, and then sends the downlink data to the processor 710 for processing; and also sends uplink data to the network-side device. Generally, the radio frequency unit 701 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 709 may be configured to store software programs or instructions and various data. The memory 709 may include a program or instruction storage area and a data storage area. The program or instruction storage area may store an operating system, an application program or instruction required by at least one function (for example, a sound playback function or an image playback function), and the like. In addition, the memory 709 may include a high-speed random access memory, and may further include a non-transitory memory. The non-transitory memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory, for example, at least one disk storage device, a flash memory device, or another non-transitory solid-state storage device.
The processor 710 may include one or more processing units. In some implementations, an application processor and a modem processor may be integrated in the processor 710. The application processor primarily processes an operating system, user interfaces, application programs or instructions, and the like. The modem processor primarily processes radio communication, for example, being a baseband processor. It can be understood that the modem processor may be not integrated in the processor 710.
The processor 710 is configured to perform a first operation based on a first status or based on the first status and a second status.
The first operation is an operation related to DRX.
The first status includes: a status of a reporting resource; and
In this embodiment of this application, the terminal performs the first operation based on the first status or based on the first status and the second status, where the first status includes: a status of a reporting resource; and the second status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status. In this way, a DRX-related operation can be determined based on the status of the reporting resource, the status of the sidelink feedback resource, or the feedback enablement status, thereby implementing a DRX mechanism in sidelink.
An embodiment of this application further provides a network-side device, including a processor and a communication interface, where the processor is configured to perform a second operation based on a third status or based on the third status and a fourth status, where the third status includes: a status of a reporting resource; and the fourth status includes at least one of the following: a status of a sidelink feedback resource and a feedback enablement status; and the communication interface is configured to communicate with an external communication device (for example, the terminal). The network-side device embodiments correspond to the embodiments of the foregoing network-side device method 300, and the implementation processes and implementations of the foregoing method embodiments can be applied to the network-side device embodiments, with the same technical effects achieved.
In some implementations, an embodiment of this application further provides a network-side device. As shown in
The frequency band processing apparatus may be located in the baseband apparatus 803. The method performed by the network-side device in the foregoing embodiments may be implemented in the baseband apparatus 803, and the baseband apparatus 803 includes a processor 804 and a memory 805.
The baseband apparatus 803 may include, for example, at least one baseband board, where a plurality of chips are disposed on the baseband board. As shown in
The baseband apparatus 803 may further include a network interface 806, configured to exchange information with the radio frequency apparatus 802, where the interface is, for example, a Common Public Radio Interface (CPRI for short).
In some implementations, the network-side device in this embodiment of the present disclosure further includes: instructions or a program stored in the memory 805 and capable of running on the processor 804. The processor 804 invokes the instructions or program in the memory 805 to execute the method executed by the modules shown in FIG. with the same technical effects achieved. To avoid repetition, details are not repeated herein.
An embodiment of this application further provides a readable storage medium, where a program or instructions are stored in the readable storage medium. When the program or the instructions are executed by a processor, the processes of the foregoing embodiments of the transmission control method 200 or the transmission control method 300 can be implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again.
The processor is a processor in the terminal described in the foregoing embodiments, or a processor in the network-side device described in the foregoing embodiments. The readable storage medium includes a computer-readable storage medium, for example, a computer Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disc.
An embodiment of this application further provides a chip, where the chip includes a processor and a communications interface. The communications interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the processes of the foregoing embodiments of the transmission control method 200 or the transmission control method 300, with the same technical effects achieved. To avoid repetition, details are not described herein again.
It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-level chip, a system chip, a chip system, a system-on-chip, or the like.
An embodiment of this application provides a computer program/program product, where the computer program-'program product is stored in a non-transitory storage medium, and when being executed by at least one processor, the program/program product is configured to implement the processes of the foregoing embodiments of the transmission control method 200 or the transmission control method 300, with the same technical effects achieved. To avoid repetition, details are not repeated herein.
It should be noted that in this specification, the term “comprise,” “include,” or any of their variants are intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by “includes a . . . ” does not preclude the existence of other identical elements in the process, method, article, or apparatus that includes the element. In addition, it should be noted that the scope of the method and the apparatus in the embodiments of this application is not limited to executing the functions in an order shown or discussed, but may also include executing the functions in a substantially simultaneous manner or in a reverse order, depending on the functions involved. For example, the described methods may be performed in an order different from that described, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.
According to the foregoing description of the implementations, a person skilled in the art may clearly understand that the methods in the foregoing embodiments may be implemented by using software in combination with a necessary common hardware platform, and certainly may be implemented by using hardware. Based on such an understanding, the technical solutions of this application essentially or the part contributing to the related art may be implemented in a form of a computer software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods described in the embodiments of this application.
The foregoing describes the embodiments of this application with reference to the accompanying drawings, However, this application is not limited to the foregoing specific embodiments. The foregoing specific embodiments are merely illustrative rather than restrictive. As instructed by this application, persons of ordinary skill in the art may develop many other manners without departing from principles of this application and the protection scope of the claims, and all such manners fall within the protection scope of this application.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202110421166.0 | Apr 2021 | CN | national |
The application is a continuation of International Application No. PCT/CN2022/086534, filed on Apr. 13, 2022, which claims priority to Chinese Patent Application No. 202110421166.0, filed Apr. 19, 2021. The entire contents of each of the above-identified applications are expressly incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2022/086534 | Apr 2022 | US |
| Child | 18381609 | US |
