CN114980284A - Communication method and device - Google Patents
Communication method and device Download PDFInfo
- Publication number
- CN114980284A CN114980284A CN202110307529.8A CN202110307529A CN114980284A CN 114980284 A CN114980284 A CN 114980284A CN 202110307529 A CN202110307529 A CN 202110307529A CN 114980284 A CN114980284 A CN 114980284A
- Authority
- CN
- China
- Prior art keywords
- timer
- control information
- information
- terminal device
- sidelink
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 102
- 238000004891 communication Methods 0.000 title claims abstract description 70
- 230000004913 activation Effects 0.000 claims description 40
- 238000012544 monitoring process Methods 0.000 claims description 37
- 230000015654 memory Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 6
- 238000013475 authorization Methods 0.000 claims description 3
- 230000006870 function Effects 0.000 description 35
- 238000012545 processing Methods 0.000 description 35
- 230000005540 biological transmission Effects 0.000 description 31
- 230000008569 process Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 11
- 230000006399 behavior Effects 0.000 description 10
- 230000000694 effects Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000013507 mapping Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 206010000117 Abnormal behaviour Diseases 0.000 description 2
- 230000003111 delayed effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000002035 prolonged effect Effects 0.000 description 2
- 230000004622 sleep time Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The application relates to a communication method and equipment. The first terminal equipment configured with the sidestream DRX sends first sidestream control information to the second terminal equipment, and the first sidestream control information is used for triggering the second terminal equipment to send sidestream channel state information. And in a first time period after the first sidelink control information is sent, the first terminal equipment receives second sidelink control information from the second terminal equipment, and the first time period is used for receiving the sidelink channel state information. The first terminal device does not start the sidestream DRX inactivity timer. The first time period itself is used for receiving the sidestream channel state information, so that the first terminal device does not start the sidestream DRX inactivity timer and does not affect the reception of the sidestream channel state information. And by not starting the timer, the power consumption of the first terminal equipment can be saved.
Description
Cross Reference to Related Applications
The present application claims priority from a chinese patent application entitled "a SL DRX inactivity timer activation method" filed by the chinese intellectual property office at 24/02/2021 under the application number 202110209310.4, the entire contents of which are incorporated herein by reference.
Technical Field
The present application relates to the field of communications technologies, and in particular, to a communication method and device.
Background
If communication is required between two adjacent User Equipments (UEs), the two UEs may not need to relay through other network nodes, but may communicate in a direct connection manner, for example, the two UEs may communicate through a Sidelink (SL). Through two UEs in SL communication, one UE may trigger the peer UE to feed back Channel State Information (CSI) in a message sending manner.
For example, UE1 sends a message to UE2 to trigger UE2 to send the sidelink CSI to UE 1. For example, the UE1 employs a Discontinuous Reception (DRX) mechanism, in which the UE1 has a corresponding sleep time. Then the UE1 may not enter the dormant state after sending the message, but continue to listen to a Physical Sidelink Control Channel (PSCCH) in order to receive the sidelink CSI from the UE 2. During the time that the UE1 monitors the PSCCH, the UE1 may also receive Sidelink Control Information (SCI) from the UE2, and if the SCI is received, whether the corresponding sidelink DRX timer of the UE1 should be started (or restarted) or not started is not determined, which may cause confusion in the behavior of the UE 1.
Disclosure of Invention
The embodiment of the application provides a communication method and equipment, which are used for providing an operation rule for UE (user equipment) and avoiding behavior confusion of the UE.
In a first aspect, a first communication method is provided, which may be performed by a terminal device, or by a larger device comprising the terminal device, or by a system-on-chip or other functional module, which is capable of performing the functions of the terminal device. For example, the terminal device is a first terminal device, and the first terminal device is configured with the sidestream DRX. The method comprises the following steps: sending first sideline control information to second terminal equipment, wherein the first sideline control information is used for triggering the second terminal equipment to send sideline channel state information; receiving second sidelink control information from the second terminal equipment in a first time period after the first sidelink control information is sent, wherein the second sidelink control information is used for scheduling MAC PDU, and the first time period is used for receiving the sidelink channel state information; the sidestream DRX inactivity timer is not started.
In this embodiment, after the first terminal device sends the first sidelink control information for triggering the sidelink channel state information to the second terminal device, if the second sidelink control information is received from the second terminal device within the first time period, the first terminal device may not start or restart the sidelink DRX inactivity timer. Since the first terminal device is in a listening state for the PSCCH for the first time period, it is able to receive the side channel state information from the second terminal device, i.e. reception of the side channel state information is not delayed. And because the first terminal equipment does not start or restart the sidestream DRX inactivity timer, the monitoring time (first time period) of the first terminal equipment for the sidestream channel state information is not prolonged, and the electric quantity of the first terminal equipment can be saved. In addition, the embodiment of the application provides an operation rule for the terminal equipment, and the terminal equipment can clearly and definitely control the sidestream DRX timer after triggering the sidestream channel state information, so that the behavior disorder of the terminal equipment is avoided.
With reference to the first aspect, in a first optional implementation manner of the first aspect, the first time period satisfies: the time period is the time period for monitoring the sidestream control information after the first terminal equipment sends the first sidestream control information, and the sidestream DRX activation time does not belong to the first terminal equipment; or, the first time period satisfies: the time period is the time period for monitoring the lateral control information after the first terminal equipment sends the first lateral control information, and neither a lateral DRX duration timer nor a lateral DRX inactivity timer of the first terminal equipment is operated; or, the first time period satisfies: the time period is the time period for monitoring the lateral control information after the first terminal equipment sends the first lateral control information, and the lateral DRX duration timer, the lateral DRX retransmission timer and the lateral DRX inactivity timer of the first terminal equipment do not run. The first time period may not belong to the sidestream DRX activation time of the first terminal device, or the first time period may also belong to the sidestream DRX activation time of the first terminal device, and the definition of the first time period is flexible.
With reference to the first optional implementation manner of the first aspect, in a second optional implementation manner of the first aspect, a time period during which the first terminal device monitors the sidelink control information after sending the first sidelink control information is a time period during which a first timer runs, where the first timer is started after the first terminal device sends the first sidelink control information; or, the time period for monitoring the sidestream control information after the first terminal device sends the first sidestream control information is a time period for expecting to receive the sidestream channel state information after the first terminal device sends the first sidestream control information; or the time period for monitoring the sidelink control information after the first terminal device sends the first sidelink control information is the time period for running a sidelink channel state information reporting timer, and the sidelink channel state information reporting timer is used for indicating the maximum time length until the sidelink channel state information is sent. The time period for monitoring the side row control information after the first terminal equipment sends the first side row control information can have various different implementation modes, and is flexible.
With reference to the first aspect or the first optional implementation manner of the first aspect or the second optional implementation manner of the first aspect, in a third optional implementation manner of the first aspect, the method further includes: sending first information to the second terminal device, where the first information is used to indicate that the first terminal device does not start the sidestream DRX inactivity timer in the first time period after sending the first sidestream control information; or, receiving first information from the second terminal device, where the first information is used to instruct the first terminal device not to start the DRX inactivity timer in the first time period after the first terminal device sends the first sidelink control information; or, receiving first information from a network device, where the first information is used to instruct the first terminal device not to start the sidestream DRX inactivity timer in the first time period after the first sidestream control information is sent; or, the first side-row control information is further configured to instruct the first terminal device not to start the side-row DRX inactivity timer in the first time period after the first side-row control information is sent. The first terminal device may default to not start the sidestream DRX inactivity timer of the first terminal device in the first time period after sending the first sidestream control information to the second terminal device, or whether the first terminal device starts the sidestream DRX inactivity timer of the first terminal device in the first time period after sending the first sidestream control information to the second terminal device, or may be configured by the network device, or determined by the first UE itself, or may be configured by the second UE, and the manner is flexible.
With reference to the first aspect or any one of the first to third alternative embodiments of the first aspect, in a fourth alternative embodiment of the first aspect, the method further comprises: and sending second information to the second terminal equipment, wherein the second information is used for indicating a first mode applied to the first time period, and the first mode is a mode of sending information to the first terminal equipment by the second terminal equipment. Wherein the first mode comprises: the second terminal equipment can send the side channel state information to the first terminal equipment and cannot send data to the first terminal equipment; or, the second terminal device can send sideline channel state information and/or data to the first terminal device; or, the second terminal device may send the sidelink channel status information, or send the sidelink channel status information and the data to the first terminal device, and the sidelink channel status information and the data are carried in the same MAC PDU. The second terminal device sends the MAC PDU to the first terminal device within the first time period, which may have a plurality of different implementation manners, or the second terminal device sends the MAC PDU to the first terminal device within the first time period, which may have a plurality of different implementation manners. For example, one mode is that the MAC PDU sent by the second terminal device to the first terminal device in the first time period can include the sidestream channel state information but cannot include data, and in this implementation mode, the second terminal device only needs to send the sidestream channel state information to the first terminal device, which can reduce the sending time and improve the efficiency of the first terminal device in obtaining the sidestream channel state information. If the retransmission is needed due to one-time transmission error, only the side-row channel state information needs to be retransmitted without retransmitting other information, so that the retransmission time can be saved. For example, the second terminal device may send the sidelink channel status information and/or data to the first terminal device, and the sidelink channel status information and data may be included in the same MAC PDU or may be included in different MAC PDUs. In this implementation, the second terminal device may send the sidelink channel status information to the first terminal device, or may send data to the first terminal device, so that the first time period can be effectively utilized, and the first terminal device can obtain more information in the first time period. And the sidelink channel state information and data can be included in one MAC PDU, can also include in different MAC PDUs, the mode is comparatively flexible, and can send more information. For example, the second terminal device may send the sidelink channel status information to the first terminal device, or send the sidelink channel status information and data to the first terminal device, but if data is to be sent, the sidelink channel status information and data need to be included in the same MAC PDU. In this implementation, the second terminal device may send the sidelink channel status information to the first terminal device, or may send data to the first terminal device, so that the first time period can be effectively utilized, and the first terminal device can obtain more information in the first time period. And the sidestream channel state information and the data can be included in one MAC PDU, so that the transmission efficiency can be improved, and the efficiency of acquiring the sidestream channel state information by the first terminal equipment is improved. Also, if retransmission is involved, only one MAC PDU needs to be retransmitted, which also reduces retransmission time.
With reference to the first aspect or any one of the first to fourth alternative embodiments of the first aspect, in a fifth alternative embodiment of the first aspect, the method further comprises: receiving the MAC PDU from the second terminal device; starting a second timer in case of a failure in decoding the MAC PDU; and during the running of the second timer, monitoring side-line control information to wait for the retransmitted MAC PDU. If the first terminal device fails to decode the MAC PDU, the first terminal device cannot obtain the information included in the MAC PDU, and the first terminal device may start a second timer to wait for the second terminal device to retransmit the MAC PDU. Through a retransmission mechanism, the success rate of the first terminal equipment for acquiring the information can be improved.
With reference to the fifth optional implementation manner of the first aspect, in a sixth optional implementation manner of the first aspect, the starting a second timer in a case that decoding of the MAC PDU fails includes: starting the second timer if decoding the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information and no data. For example, the first terminal device may start the second timer when the MAC PDU decoding fails, so that the success rate of the first terminal device for acquiring information may be improved. Or alternatively, if the second sidelink control information indicates that the MAC PDU includes sidelink channel status information and does not include data, the first terminal device may start the second timer if decoding of the MAC PDU fails; if the second sidelink control information indicates that the MAC PDU includes sidelink channel status information and data, or indicates that the MAC PDU does not include sidelink channel status information (and may also indicate that data is included, and may also indicate that data is not included), the first terminal device may not start the second timer even if decoding of the MAC PDU fails, i.e., may not have to wait for retransmission of the MAC PDU. If the second sidelink control information indicates that the MAC PDU includes sidelink channel status information and does not include data, and the first terminal device does not successfully decode the MAC PDU, the first terminal device may start the second timer to wait for retransmission because only the sidelink channel status information needs to be retransmitted and the required retransmission time is not long. And if the second sidelink control information indicates that the MAC PDU includes sidelink channel state information and data, the retransmission process includes the retransmission of the sidelink channel state information and the retransmission of the data, the required retransmission time is long, and the power loss for the first terminal device is large, the first terminal device may not wait for the retransmission.
With reference to the fifth optional implementation manner of the first aspect or the sixth optional implementation manner of the first aspect, in a seventh optional implementation manner of the first aspect, the starting the second timer includes: starting the second timer in a first time domain unit after the end of the side row data channel corresponding to the second side row control information; or, starting the second timer in a first time domain unit after the first feedback information is sent, where the first feedback information is the feedback information corresponding to the MAC PDU and sent to the second terminal device. The second timer may be started after the second sideline control information is sent, or may be started after the first feedback information is sent, and if the second timer is started after the first feedback information is sent, the time for the first terminal device to monitor the sideline control information may be reduced, and the power consumption of the first terminal device may be saved.
With reference to the first aspect or any one of the first to fourth alternative embodiments of the first aspect, in an eighth alternative embodiment of the first aspect, the method further comprises: receiving the MAC PDU from the second terminal device; starting a third timer under the condition that the decoding of the MAC PDU is failed, wherein the timing duration of the third timer is used for indicating the preparation time of the second terminal equipment before the MAC PDU is retransmitted; starting a second timer when the third timer times out; and during the running of the second timer, monitoring side-line control information to wait for the retransmitted MAC PDU. A certain time is needed between the first terminal device sending the first feedback information and the second terminal device retransmitting the MAC PDU, that is, the second terminal device needs a certain preparation time to retransmit the MAC PDU, and it is obvious that the first terminal device does not receive the retransmitted MAC PDU within the preparation time of the second terminal device. Therefore, the first terminal device can start the third timer, and the first terminal device does not need to monitor the sidestream control information in the running time of the third timer, so that the power consumption of the first terminal device is saved.
With reference to the eighth optional implementation manner of the first aspect, in a ninth optional implementation manner of the first aspect, the starting a third timer in a case that decoding of the MAC PDU fails includes: starting the third timer if decoding the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel status information and no data. With respect to the technical effects of this embodiment, reference is made to the foregoing embodiment.
With reference to the eighth optional implementation manner of the first aspect or the ninth optional implementation manner of the first aspect, in a tenth optional implementation manner of the first aspect, starting the third timer includes: starting the third timer in a first time domain unit after the end of the side row data channel corresponding to the second side row control information; or, starting the third timer in a first time domain unit after the first feedback information is sent, where the first feedback information is the feedback information corresponding to the MAC PDU and sent to the second terminal device. With respect to the technical effects of this embodiment, reference is made to the foregoing embodiment.
With reference to any one of the fifth optional implementation manner of the first aspect to the tenth optional implementation manner of the first aspect, in an eleventh optional implementation manner of the first aspect, the method further comprises: stopping the second timer when the lateral channel state information report timer of the second terminal equipment is overtime; or, when a second time length after the first sidelink control information is sent is reached, stopping the second timer, wherein the second time length is used for waiting for receiving sidelink channel state information, and the timing time length of a sidelink channel state information report timer of the second terminal equipment is determined according to the second time length; or, when the time length for expecting to receive the sideline channel state information after the first sideline control information is sent reaches, the second timer is stopped. The first terminal device may not wait for retransmission of the MAC PDU all the time, and if the lateral channel state information report timer is overtime, or the second duration arrives, or the maximum duration for which the first terminal device expects to receive the lateral channel state information arrives, it may indicate that the second terminal device may not send the lateral channel state information to the first terminal device any more, so the first terminal device does not need to wait unnecessarily to save power consumption.
With reference to the first aspect or any one of the first optional implementation manner of the first aspect to the fourth optional implementation manner of the first aspect, in a twelfth optional implementation manner of the first aspect, the method further comprises: receiving the MAC PDU from the second terminal device; and under the condition that the decoding of the MAC PDU fails and the second downlink control information indicates that the MAC PDU does not comprise the lateral channel state information, not starting a second timer, wherein the running period of the second timer is used for monitoring the lateral control information. If the second sidelink control information indicates that the MAC PDU does not include sidelink channel status information, since the first terminal device actually mainly wants to receive the sidelink channel status information, if the MAC PDU does not include the sidelink channel status information, the first terminal device may not need to wait for retransmission of the MAC PDU, and thus may not need to start the second timer.
In combination with the first aspect or any one of the first to twelfth optional embodiments of the first aspect, in a thirteenth optional embodiment of the first aspect, the method further comprises: and after the first sideline control information is sent, starting a first timer, wherein the timing duration of the first timer is the first time period. The first terminal device may determine the first time period by a first timer.
In combination with the first aspect or any one of the first to twelfth alternative embodiments of the first aspect, in a fourteenth alternative embodiment of the first aspect, the method further comprises: after the first side-row control information is sent, starting a fourth timer, wherein the timing duration of the fourth timer is used for indicating the preparation time of the second terminal equipment before the side-row channel state information is sent; and starting a first timer when the fourth timer is over time, wherein the timing duration of the first timer is the first time period. The first terminal device sends the first sideline control information to the second terminal device sends the sideline channel state information, the second terminal device needs a certain preparation time, in the preparation time, the second terminal device does not send the sideline channel state information, and the first terminal device does not receive the sideline channel state information from the second terminal device. And in the running time of the fourth timer, the first terminal equipment does not need to monitor the side-line control information, and when the fourth timer times out, the first terminal equipment restarts the first timer so as to save the power consumption of the first terminal equipment.
With reference to the fourteenth optional implementation manner of the first aspect, in a fifteenth optional implementation manner of the first aspect, the method further includes: and receiving third information from the second terminal device, wherein the third information is used for indicating the timing duration of the fourth timer. The fourth timer may be configured by the second terminal device, and the second terminal device may indicate a timing duration of the fourth timer to the first terminal device, so that the first terminal device maintains the fourth timer.
With reference to the thirteenth optional implementation manner of the first aspect, the fourteenth optional implementation manner of the first aspect, or the fifteenth optional implementation manner of the first aspect, in a sixteenth optional implementation manner of the first aspect, the operation time of the first timer is a sidelink DRX activation time of the first terminal device; or, the part of the running time of the first timer which is not overlapped with the side-row DRX activation time of the first terminal equipment does not belong to the side-row DRX activation time of the first terminal equipment; or, in the running time of the first timer, the time when the lateral DRX duration timer and/or the lateral DRX inactivity timer of the first terminal device do not run does not belong to the lateral DRX active time of the first terminal device; or, in the running time of the first timer, the non-running time of one or more timers of a lateral DRX duration timer, a lateral DRX inactivity timer, or a lateral DRX retransmission timer of the first terminal device does not belong to the lateral DRX active time of the first terminal device. The running time of the first timer may be the sidestream DRX activation time of the first terminal device, or may not belong to the sidestream DRX activation time of the first terminal device, which is relatively flexible.
With reference to the thirteenth optional implementation manner of the first aspect, the fourteenth optional implementation manner of the first aspect, the fifteenth optional implementation manner of the first aspect, or the sixteenth optional implementation manner of the first aspect, in a seventeenth optional implementation manner of the first aspect, the method further comprises: receiving fourth information from a network device, wherein the fourth information is used for indicating the timing duration of the first timer; or, determining the timing duration of the first timer according to the CBR. The timing duration of the first timer may be configured by the network device, or may also be configured by the first terminal device. For example, the first terminal device may determine the timing duration of the first timer according to the CBR, and under the condition that the value of the CBR is unchanged, the longer the timing duration of the first timer is, the more resources with lower interference that can be selected when the second UE sends the sidelink channel state information are, and the higher the sending success rate is. The timing duration of the first timer is determined according to the CBR, so that a compromise can be made between the interference level of the resource selected by the second terminal equipment and the monitoring duration of the first terminal equipment, and the sending success rate of the second terminal equipment is improved on the premise that the power consumption of the first terminal equipment is saved as much as possible.
With reference to the seventeenth optional implementation manner of the first aspect, in an eighteenth optional implementation manner of the first aspect, the determining a timing duration of the first timer according to the CBR includes: under the condition that the channel occupancy rate indicated by the CBR is greater than or equal to a first threshold value, determining the timing duration of the first timer to be the duration greater than a second threshold value; and/or determining that the timing duration of the first timer is a duration less than a third threshold under the condition that the channel occupancy indicated by the CBR is less than the first threshold. If the CBR indicates that the channel occupancy is high, the timing duration of the first timer determined by the first terminal device may be long, because there is a possibility that the channel contention is large and the channel status is not good, the first UE may wait for receiving the sidelink channel status information for a long time, so as to improve the receiving success rate of the sidelink channel status information; for another example, if the CBR indicates that the channel occupancy is low, the timing duration of the first timer determined by the first terminal device may be short, because the channel status is good at this time, the first terminal device may be able to receive the sidelink channel status information in a short time, and the time is not too long, so that the power consumption of the first terminal device may be saved.
With reference to any one of the thirteenth optional implementation manner of the first aspect to the eighteenth optional implementation manner of the first aspect, in a nineteenth optional implementation manner of the first aspect, the method further comprises: receiving second feedback information from the second terminal equipment; and if the second feedback information is used for indicating that the first sidelink data channel is unsuccessfully received, stopping the first timer, wherein the first sidelink data channel is a sidelink data channel scheduled by the first sidelink control information. The first sidelink control information may also schedule a first sidelink data channel, and the first terminal device may also send the first sidelink data channel to the second terminal device after sending the first sidelink control information. The second terminal device needs to decode both the first side row control information and the first side row data channel, and the second terminal device can send the side row channel state information to the first terminal device under the condition that both the first side row control information and the first side row data channel are successfully decoded, and the second terminal device can possibly cause that the second terminal device cannot send the side row channel state information to the first terminal device no matter whether the decoding of the first side row control information or the first side row data channel fails. After receiving the first side data channel, the second terminal device may send second feedback information to the first terminal device, where the second feedback information is, for example, a negative acknowledgement to indicate that the first side data channel is failed to be received if the second terminal device fails to decode (or fails to receive) the first side data channel, and the second feedback information is, for example, a positive acknowledgement to indicate that the first side data channel is successfully received if the second terminal device succeeds in decoding (or succeeds in receiving) the first side data channel. For the first terminal device, if the second feedback information is used to indicate that the reception of the first sidelink data channel fails, it indicates that the second terminal device cannot send the sidelink channel status information to the first terminal device, and therefore the first terminal device does not need to wait for receiving the sidelink channel status information any more, the first terminal device may stop the first timer, so as to save the power consumption of the first terminal device.
In a second aspect, a second communication method is provided, which may be performed by a terminal device, or by a larger device comprising the terminal device, or by a system-on-chip or other functional module, which is capable of performing the functions of the terminal device. For example, the terminal device is a second terminal device. The method comprises the following steps: receiving first sideline control information from first terminal equipment, wherein the first sideline control information is used for triggering the second terminal equipment to send sideline channel state information; sending second sideline control information to the first terminal equipment, wherein the second sideline control information is used for scheduling MAC PDU; the sidestream DRX inactivity timer is not started.
With reference to the second aspect, in a first optional implementation manner of the second aspect, the method further includes: and sending the MAC PDU to the first terminal equipment according to a first mode applied to a first time period, wherein the first time period is used for the first terminal equipment to wait for the sidestream channel state information. The first mode includes: the first terminal equipment can be sent side channel state information, and data cannot be sent to the first terminal equipment; or, side-row channel state information and/or data can be sent to the first terminal device; or, the side-row channel state information can be sent to the first terminal device, or the side-row channel state information and the data can be sent, and the side-row channel state information and the data are carried in one MAC PDU.
With reference to the second aspect or the first optional implementation manner of the second aspect, in a second optional implementation manner of the second aspect, the method further includes: receiving first information from the first terminal equipment, wherein the first information is used for indicating that the first terminal equipment does not start a side-row DRX inactivity timer in a first time period after the first side-row control information is sent; or, receiving first information from a network device, where the first information is used to instruct the first terminal device not to start a sidestream DRX inactivity timer in the first time period after the first sidestream control information is sent; or, sending first information to the first terminal device, where the first information is used to indicate that the first terminal device does not start a sidestream DRX inactivity timer in a first time period after sending the first sidestream control information; or, the first sidelink control information is further used to instruct the first terminal device not to start a sidelink DRX inactivity timer within a first time period after the first sidelink control information is sent.
With reference to the first alternative implementation manner of the second aspect or the second alternative implementation manner of the second aspect, in a third alternative implementation manner of the second aspect, the method further includes: selecting a target device for receiving the MAC PDU according to a first rule, wherein the first rule comprises: the first time domain resource is located in the first time period after the target device triggers the second terminal device to send the sidestream channel state information, or the first time domain information is located in the sidestream DRX activation time of the target device; the first time domain resource is a time domain resource occupied by the second sideline control information, or a time domain resource occupied by a sideline control channel corresponding to the second sideline control information, or a time domain resource occupied by a sideline authorization information corresponding to the second sideline control information.
With reference to the second aspect or any one of the first optional implementation manner of the second aspect to the third optional implementation manner of the second aspect, in a fourth optional implementation manner of the second aspect, the method further includes: and receiving second information from the first terminal equipment, wherein the second information is used for indicating the first mode.
With reference to the second aspect or any one of the first optional implementation manner of the second aspect to the fourth optional implementation manner of the second aspect, in a fifth optional implementation manner of the second aspect, the method further comprises: and sending third information to the first terminal equipment, wherein the third information is used for indicating the timing duration of a fourth timer, and the timing duration of the fourth timer is used for indicating the preparation time of the second terminal equipment before the side-row channel state information is sent.
With regard to the technical effects brought about by the second aspect or various alternative embodiments of the second aspect, reference may be made to the introduction to the technical effects of the first aspect or the respective embodiments.
In a third aspect, a third communication method is provided, which may be performed by a terminal device, or by a larger device comprising the terminal device, or by a system-on-chip or other functional module, which is capable of performing the functionality of the terminal device. For example, the terminal device is a second terminal device. The method comprises the following steps: receiving first sideline control information from first terminal equipment, wherein the first sideline control information is used for triggering the second terminal equipment to send sideline channel state information; sending second sideline control information to the first terminal equipment, wherein the second sideline control information is used for scheduling MAC PDU; and sending the MAC PDU to the first terminal equipment according to a first mode applied to a first time period, wherein the first mode is a mode that the second terminal equipment sends information to the first terminal equipment, and the first time period is used for the first terminal equipment to wait for the status information of the sidestream channel.
With reference to the third aspect, in a first optional implementation manner of the third aspect, the first mode includes: the first terminal equipment can be sent side channel state information, and data cannot be sent to the first terminal equipment; or, can send sidelink channel status information and/or data to the said first terminal installation; or, the side-row channel state information can be sent to the first terminal device, or the side-row channel state information and the data can be sent, and the side-row channel state information and the data are carried in one MAC PDU.
With reference to the third aspect or the first optional implementation manner of the third aspect, in a second optional implementation manner of the third aspect, the method further includes: the sidestream DRX inactivity timer is not started.
With reference to the third aspect or the first optional implementation manner of the third aspect or the second optional implementation manner of the third aspect, in a third optional implementation manner of the third aspect, the method further includes: receiving first information from the first terminal device, wherein the first information is used for indicating that the first terminal device does not start a side-row DRX (discontinuous reception) inactivity timer in a first time period after the first side-row control information is sent; or, receiving first information from a network device, where the first information is used to instruct the first terminal device not to start a sidestream DRX inactivity timer in the first time period after the first sidestream control information is sent; or, sending first information to the first terminal device, where the first information is used to indicate that the first terminal device does not start a sidestream DRX inactivity timer in a first time period after sending the first sidestream control information; or, the first sidelink control information is further used to instruct the first terminal device not to start a sidelink DRX inactivity timer within a first time period after the first sidelink control information is sent.
With reference to the second optional implementation manner of the third aspect or the third optional implementation manner of the third aspect, in a fourth optional implementation manner of the third aspect, the method further includes: selecting a target device for receiving the MAC PDU according to a first rule, wherein the first rule comprises: the first time domain resource is located in the first time period after the target device triggers the second terminal device to send the sidestream channel state information, or the first time domain information is located in the sidestream DRX activation time of the target device; the first time domain resource is a time domain resource occupied by the second sidelink control information, or a time domain resource occupied by a sidelink control channel corresponding to the second sidelink control information, or a time domain resource occupied by a sidelink authorization information corresponding to the second sidelink control information.
With reference to the third aspect or any one of the first optional implementation manner to the fourth optional implementation manner of the third aspect, in a fifth optional implementation manner of the third aspect, the method further includes: and receiving second information from the first terminal equipment, wherein the second information is used for indicating the first mode.
With reference to the third aspect or any one of the first optional implementation manner to the fifth optional implementation manner of the third aspect, in a sixth optional implementation manner of the third aspect, the method further includes: and sending third information to the first terminal equipment, wherein the third information is used for indicating the timing duration of a fourth timer, and the timing duration of the fourth timer is used for indicating the preparation time of the second terminal equipment before the side channel state information is sent.
With regard to the technical effects brought about by the third aspect or the various alternative embodiments of the third aspect, reference may be made to the introduction of the technical effects of the first aspect or the respective embodiments.
In a fourth aspect, a communication device is provided. The communication device may be the first terminal apparatus according to any one of the first to third aspects. The communication device has the function of the first terminal device. In an alternative implementation, the communication device includes a baseband device and a radio frequency device. In another alternative implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transmitting/receiving means can implement a transmitting function and a receiving function, and when the transmitting/receiving means implements the transmitting function, it may be called a transmitting means (also referred to as a transmitting module in some cases), and when the transmitting/receiving means implements the receiving function, it may be called a receiving means (also referred to as a receiving module in some cases). The sending unit and the receiving unit can be the same functional module, the functional module is called as a receiving and sending unit, and the functional module can realize the sending function and the receiving function; alternatively, the transmitting unit and the receiving unit may be different functional modules, and the transmitting and receiving unit is a general term for these functional modules.
The receiving and sending unit (or the sending unit) is configured to send first sideline control information to a second terminal device, where the first sideline control information is used to trigger the second terminal device to send sideline channel state information;
the transceiver unit (or the receiver unit) is configured to receive second sidelink control information from the second terminal device in a first time period after the first sidelink control information is sent, where the second sidelink control information is used to schedule a MAC PDU, and the first time period is used to receive the sidelink channel status information;
the processing unit is configured to not start the sidestream DRX inactivity timer.
In an optional implementation manner, the communication apparatus further includes a storage unit, and the processing unit is configured to couple with the storage unit and execute a program or an instruction in the storage unit, so as to enable the communication apparatus to perform the function of the first terminal device according to any one of the first to third aspects.
In a fifth aspect, a communications apparatus is provided. The communication device may be the second terminal apparatus according to any one of the first to third aspects. The communication device has the function of the second terminal device. In an alternative implementation, the communication device includes a baseband device and a radio frequency device. In another alternative implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). An implementation of the transceiving unit may refer to the introduction of the fourth aspect.
The receiving and sending unit (or the receiving unit) is configured to receive first sideline control information from a first terminal device, where the first sideline control information is used to trigger the second terminal device to send sideline channel state information;
the transceiver unit (or the transmitter unit) is configured to transmit second sidelink control information to the first terminal device, where the second sidelink control information is used to schedule a MAC PDU;
the processing unit is configured to not start the sidestream DRX inactivity timer.
Alternatively, the first and second electrodes may be,
the transceiver unit (or the receiving unit) is configured to receive first sidelink control information from a first terminal device, where the first sidelink control information is used to trigger the second terminal device to send sidelink channel state information;
the transceiver unit (or the transmitter unit) is configured to transmit second sidelink control information to the first terminal device, where the second sidelink control information is used to schedule a MAC PDU;
the transceiver unit (or the transmitter unit) is configured to transmit the MAC PDU to the first terminal device according to a first manner applied to a first time period, where the first manner is a manner in which the second terminal device transmits information to the first terminal device, and the first time period is used for the first terminal device to wait for the sidelink channel status information.
In an optional implementation manner, the communication apparatus further includes a storage unit, and the processing unit is configured to couple with the storage unit and execute a program or an instruction in the storage unit, so as to enable the communication apparatus to perform the function of the second terminal device according to any one of the first to third aspects.
A sixth aspect provides a computer-readable storage medium for storing a computer program or instructions which, when executed, cause the method performed by the first terminal device or the second terminal device in the above aspects to be implemented. Optionally, the method performed by the first terminal device or the second terminal device in any embodiment of the present application is implemented.
In a seventh aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the method of the above aspects to be carried out. Optionally, the method described in any embodiment of the present application is enabled.
Drawings
Fig. 1A and fig. 1B are schematic diagrams of two application scenarios according to an embodiment of the present application;
fig. 2 is a flowchart of a communication method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a first timer in the embodiment of the present application;
FIG. 4 is a schematic diagram of another operation of the first timer in the embodiment of the present application;
fig. 5 is a schematic diagram illustrating that a second UE sends a MAC PDU to a first UE according to a first implementation manner in an embodiment of the present application;
fig. 6 is a schematic diagram illustrating that a second UE sends a MAC PDU to a first UE according to a second implementation manner in the embodiment of the present application;
fig. 7 is a schematic diagram illustrating that a second UE sends a MAC PDU to a first UE according to a third implementation manner in this embodiment of the present application;
fig. 8 is a schematic block diagram of a communication device provided in an embodiment of the present application;
fig. 9 is a schematic block diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.
Hereinafter, some terms or concepts in the embodiments of the present application will be explained so as to be easily understood by those skilled in the art.
In the embodiment of the present application, the terminal device is a device having a wireless transceiving function, and may be a fixed device, a mobile device, a handheld device (e.g., a mobile phone), a wearable device, an in-vehicle device, or a wireless apparatus (e.g., a communication module, a modem, or a chip system) built in the above device. The terminal device is used for connecting people, objects, machines and the like, and can be widely used in various scenes, such as but not limited to the following scenes: cellular communication, device-to-device communication (D2D), vehicle-to-all (V2X), machine-to-machine/machine-type communication (M2M/MTC), internet of things (IoT), Virtual Reality (VR), Augmented Reality (AR), industrial control (industrial control), unmanned driving (self driving), remote medical (remote medical), smart grid (smart grid), smart furniture, smart office, smart wearing, smart transportation, smart city (smart city), unmanned aerial vehicle, robot, etc. scenarios. The terminal equipment may sometimes be referred to as User Equipment (UE), a terminal, an access station, a UE station, a distant station, wireless communication equipment, or user equipment, among others. For convenience of description, in the embodiments of the present application, a terminal device is described by taking a UE as an example.
The network device in the embodiment of the present application includes, for example, an access network device and/or a core network device. The access network equipment is equipment with a wireless transceiving function and is used for communicating with the terminal equipment. The access network device includes, but is not limited to, a base station (BTS, Node B, eNodeB/eNB, or gbnodeb/gNB), a Transmission Reception Point (TRP) in the above communication system, a base station for subsequent evolution of the third generation partnership project (3 GPP), an access Node in a wireless fidelity (Wi-Fi) system, a wireless relay Node, a wireless backhaul Node, and the like. The base station may be: macro base stations, micro base stations, pico base stations, small stations, relay stations, etc. Multiple base stations may support the same access technology network mentioned above, or may support different access technologies networks mentioned above. A base station may include one or more co-sited or non-co-sited transmission receiving points. The network device may also be a wireless controller, a Centralized Unit (CU), and/or a Distributed Unit (DU) in a Cloud Radio Access Network (CRAN) scenario. The network device may also be a server, a wearable device, or a vehicle mounted device, etc. For example, the network device in vehicle to everything (V2X) technology may be a Road Side Unit (RSU). The following description will take the access network device as a base station as an example. The base station may communicate with the terminal device, and may also communicate with the terminal device through the relay station. A terminal device may communicate with multiple base stations in different access technologies. The core network equipment is used for realizing the functions of mobile management, data processing, session management, policy, charging and the like. The names of devices for implementing the core network function in systems with different access technologies may be different, and this is not limited in this embodiment of the present application. Taking a 5G system as an example, the core network device includes: an access and mobility management function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), or a User Plane Function (UPF), etc.
In the embodiment of the present application, the communication device for implementing the function of the network device may be a network device, or may be a device capable of supporting the network device to implement the function, for example, a system on chip, and the device may be installed in the network device. In the technical solution provided in the embodiment of the present application, a device for implementing a function of a network device is taken as an example, and the technical solution provided in the embodiment of the present application is described.
sidelink transmissions are made between a pair of sources (sources) and destinations (destinations). The source may be identified by a source layer 2ID (source layer-2ID) and the destination may be identified by a destination layer 2ID (destination layer-2 ID). The source layer-2ID is used for identifying a sending end (sender) UE of data in the sidelink communication, and the destination layer-2ID is used for identifying a target end (target) UE of the data in the sidelink communication or a receiving end UE of the data. The transmitting end refers to a source of sidelink communication (or one Media Access Control (MAC) Protocol Data Unit (PDU)), and the receiving end refers to a destination of the sidelink communication (or one MAC PDU).
The source Layer-2ID is self-allocated by the sending UE. For unicast, the destination Layer-2ID depends on the opposite UE of sidelink communication, and the destination Layer-2ID is the Layer-2ID of the opposite UE. It can be understood that the layer-2ID of the UE is the source layer-2ID when the UE is the sending end, or the destination layer-2ID when the UE is the receiving end. In the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged between the two UEs and used for subsequent communications. The UE, which will be described later, may refer to a UE identified using a Layer-2ID, which is assigned the Layer-2ID and used in sidelink communication.
For unicast, a PC5-RRC connection (PC5-RRC connection) is a logical connection between a source and destination pair (the source and destination pair). After the PC5 unicast link (PC5 unicast link) is established, the corresponding PC5 RRC connection is established. There is a one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link.
In NR SL, the SCI may comprise two levels of SCI, namely a primary (1st stage) SCI and a secondary (2nd stage) SCI. PSCCH bears primary SCI, and PSSCH bears secondary SCI and MAC PDU. The primary SCI may contain information indicating the resource where the psch is located, and the UE may determine the resource of the psch according to the primary SCI carried by the PSCCH, so as to receive the psch on the corresponding resource.
In the embodiments of the present application, the number of nouns means "singular nouns or plural nouns" or "one or more" unless otherwise specified. "at least one" means one or more, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. For example, A/B, represents: a or B. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, represents: a, b, c, a and b, a and c, b and c, or a and b and c, wherein a, b and c can be single or multiple.
In the embodiments of the present application, the ordinal numbers such as "first", "second", and the like are used to distinguish a plurality of objects, and are not used to limit the size, content, order, timing, priority, importance, or the like of the plurality of objects. For example, the first side-line control information and the second side-line control information may be the same control information or different control information, and such names do not indicate the difference in the contents, the amount of information, the transmission order, the transmission time, the priority, the degree of importance, or the like of the two pieces of control information. In addition, the numbering of the steps in each embodiment described in the present application is only for distinguishing different steps, and is not used for limiting the sequence of the steps. For example, step S201 may occur before step S202, or may occur after S202, or may also occur simultaneously with S202.
In New Radio (NR), a DRX mechanism is defined in order to save unnecessary power consumption of a UE when the UE is in a Radio Resource Control (RRC) connected (connected) state. The DRX may control the UE to monitor (monitor) a Physical Downlink Control Channel (PDCCH) in some time periods, and not monitor the PDCCH in other time periods, so that power consumption of the UE may be reduced.
In NR SL, to make the UE more energy efficient, SL DRX is also introduced. In SL DRX, a DRX-duration Timer (onDurationTimer), a DRX-inactivity Timer (InactivityTimer), a DRX-hybrid automatic retransmission round trip delay Timer (HARQ-RTT-Timer), and a DRX-retransmission Timer (retransmission Timer) are introduced. To distinguish from the DRX Timer name on the Uu interface, the timers in the SL DRX may be respectively denoted as SL-DRX-OnDurationTimer, SL-DRX-inactivytytimer, SL-DRX-HARQ-RTT-Timer, and SL-DRX-retransmission Timer. The SL-DRX-OnDurationTimer indicates a period of time at the beginning of the SL DRX cycle, for example, the SL-DRX-OnDurationTimer may be started at the beginning of one SL DRX cycle, and during the running time of the SL-DRX-OnDurationTimer, the UE is in the sidelining duration and monitors PSCCH. The SL-DRX-inactivity timer is used to indicate a period of time after an SCI indicating SL new transmission, for example, when the UE monitors PSCCH, if receiving an SCI indicating SL new transmission, the UE starts or restarts the SL-DRX-inactivity timer. The SL-DRX-retransmission Timer is used to indicate the longest time until an SCI indicating SL retransmission is received, and the SL-DRX-HARQ-RTT-Timer is used to indicate the shortest time before an SCI indicating SL retransmission is expected to be received. For example, if the UE receives an SCI indicating data transmission, the UE starts sl-drx-HARQ-RTT-Timer of a corresponding HARQ process (process) at the first symbol after the end of transmission carrying HARQ feedback, and stops sl-drx-retransmission timedl of the corresponding HARQ process. The HARQ feedback refers to HARQ information that is sent by the UE after the data indicated by the SCI is received and is used for indicating whether the data is successfully received. If the sl-drx-HARQ-RTT-Timer is overtime, if the data of the corresponding HARQ process is not decoded successfully, the UE starts the sl-drx-retransmission Timer of the corresponding HARQ process at the first symbol after the sl-drx-HARQ-RTT-Timer is overtime.
The UE monitors PSCCH during SL DRX active time (active time) (or SL active time) when the UE is (is) configured or activated, or monitors PSCCH and secondary SCI (2 scind) carried on a physical side shared channel (psch) during SL DRX active time, or monitors PSCCH and PSCCH during SL DRX active time. The SL DRX active time comprises: run time of one or more timers in sl-DRX-OnDuration timer, sl-DRX-Inactivitytimer, or sl-DRX-Recransmissiontimer.
Through two pieces of UE in SL communication, one piece of UE can trigger the opposite-end UE to feed back SL CSI in a message sending mode. For example, UE1 sends a message to UE2 to trigger UE2 to send the sidelink CSI to UE 1. For example, the UE1 employs a SL DRX mechanism in which the UE1 has a corresponding sleep time. Then UE1 may not enter the dormant state but continue to listen to the PSCCH after sending the message in order to receive SL CSI from the UE. While during the time that the UE1 monitors the PSCCH, the UE1 may also receive the SCI from the UE2, and if the SCI is received, whether the UE1 corresponding sidestream DRX timer (e.g., sl-DRX-OnDurationTimer, sl-DRX-inactivytimer, or sl-DRX-retransmission timer) should start (or restart) or not start, it is not clear at present, which may cause confusion in the behavior of the UE 1.
In view of this, the technical solutions of the embodiments of the present application are provided. In this embodiment, after the first terminal device sends the first sidelink control information for triggering the channel state information to the second terminal device, if the second sidelink control information is received from the second terminal device within the first time period, the first terminal device may not start or restart the sidelink DRX inactivity timer. Since the first terminal device is in a listening state for the sidestream control information during the first time period, the channel state information from the second terminal device can be received, i.e. the reception of the channel state information is not delayed. And because the first terminal device does not start and does not restart the sidestream DRX inactivity timer, the monitoring time (or the first time period) of the first terminal device for the channel state information is not prolonged, and the electric quantity of the first terminal device can be saved. In addition, the embodiment of the application provides an operation rule for the terminal equipment, and the terminal equipment can clearly and definitely control the sidestream DRX timer after triggering the sidestream channel state information, so that the behavior disorder of the terminal equipment is avoided.
Fig. 1A is a schematic view of an application scenario according to an embodiment of the present application. In fig. 1A, a remote terminal device is connected to a relay terminal device, and the remote terminal device can communicate with a network device through the relay terminal device. Fig. 1B is a schematic view of another application scenario according to an embodiment of the present application. In fig. 1B, the remote terminal device is connected to the relay terminal device, and the remote terminal device can communicate with the network device through the relay terminal device. Fig. 1A is different from fig. 1B in that in fig. 1A, the remote end device is in a coverage area (in-coverage), and in fig. 1B, the remote end device is out of the coverage area (out-of-coverage). It should be noted that the technical solution in the embodiment of the present application is not limited to the relay service, that is, a relay service may be performed between two UEs, and also a non-relay service may be performed. Fig. 1A or fig. 1B are only for illustrating the connection between UEs, whether the UEs are covered by the network, and the like, and do not indicate the service types of the UEs.
The network device in fig. 1A or fig. 1B is, for example, an access network device, and the access network device is, for example, a base station. The access network device corresponds to different devices in different systems, for example, in a 4G system, the access network device may correspond to an eNB, and in a 5G system, the access network device in a 5G system, for example, a gNB. Of course, the technical solution provided in the embodiment of the present application may also be applied to a future mobile communication system, and therefore, the access network device in fig. 1A or fig. 1B may also correspond to a network device in the future mobile communication system. In the embodiment of the present application, the access network device is taken as a base station as an example, and actually, with reference to the foregoing description, the access network device may also be a device such as an RSU.
The method provided by the embodiment of the application is described below with reference to the accompanying drawings. In the figures corresponding to the various embodiments of the present application, all optional steps are indicated by dashed lines. The embodiments of the present application can be applied to the network architecture shown in fig. 1A or fig. 1B, where the first UE in the embodiments of the present application is, for example, the UE1 in fig. 1A or fig. 1B, and the second UE in the embodiments of the present application is, for example, the UE2 in fig. 1A or fig. 1B; alternatively, the second UE in the embodiments of the present application is, for example, the UE1 in fig. 1A or fig. 1B, and the first UE in the embodiments of the present application is, for example, the UE2 in fig. 1A or fig. 1B.
An embodiment of the present application provides a communication method, please refer to fig. 2, which is a flowchart of the method.
S201, the first UE sends the first sidelink control information to the second UE, and correspondingly, the second UE receives the first sidelink control information from the first UE. The first sidelink control information may trigger the second UE to send the sidelink CSI, e.g., the first sidelink control information may trigger the second UE to send the sidelink CSI to the first UE.
The first UE is a peer UE of the second UE. There is a PC5-RRC connection between the first UE and the second UE, the PC5-RRC connection corresponding to a source layer-2ID and destination layer-2ID pair. Wherein the source layer-2ID is a layer 2ID of the first UE, and the destination layer-2ID is a layer 2ID of the second UE. Alternatively, the source layer-2ID is the layer 2ID of the second UE and the destination layer-2ID is the layer 2ID of the first UE. The first UE is a SL CSI triggering UE, that is, a UE that triggers CSI (or triggers an opposite terminal to send sideline CSI to itself), which may be understood as that the first UE triggers CSI reporting (that is, the first UE triggers CSI reporting, which may be understood as that the first UE triggers an opposite terminal UE (for example, a second UE) to send sideline CSI to the first UE), for example, in a manner of sending first sideline control information to the first UE; the second UE is a SL CSI reporting UE, that is, a UE triggered to send the sidelink CSI (or a UE triggered to send the sidelink CSI to the opposite end).
A side-row CSI reporting (SL-CSI reporting) process is used for one UE to provide side-row CSI to a peer UE. For example, the first UE may send the first sidelink control information to the second UE to trigger the second UE to send the sidelink CSI to the first UE, and then the second UE sends the sidelink CSI to the first UE. The first side row control information is, for example, SCI, or the first side row control information may be carried in SCI, which is, for example, a secondary SCI. And if the value of a field of a CSI request field in the secondary SCI is 1, indicating that the SCI triggers the opposite end UE to send the sideline CSI. The UE (e.g., the first UE) that transmits the first sidelink control information may be referred to as a CSI triggering UE (CSI triggering UE). In addition, the UE that triggers CSI (e.g., the first UE) may also be referred to as a peer UE. In addition, the first UE may also send a message to the second UE, for example, the message is a PC5-RRC message, the PC5-RRC message is, for example, an RRC reconfiguration sidelink (rrcreeconfiguration sidelink) message, or may also be another PC5-RRC message. The PC5-RRC message may carry a sideline delay bound CSI Report (sl-LatencyBound-CSI-Report) indicating a delay requirement from an associated sidelink CSI triggering to sidelink CSI reporting, or the sl-LatencyBound-CSI-Report indicating a delay requirement from receiving first sideline control information to sending CSI to the first UE.
The first UE may transmit a sidelink CSI reference signal (sidelink CSI-RS) in a psch corresponding to the first sidelink control information. After receiving the side-row CSI-RS, the second UE can perform measurement according to the side-row CSI-RS to obtain the side-row CSI. In addition, after receiving the first sidelink control information and the PC5-RRC message, the second UE may send the sidelink CSI to the first UE within a delay requirement indicated by the SL-latencuband-CSI-Report configured by the first UE, for example, the sidelink CSI is carried in a sidelink CSI reporting media access control element (SL CSI reporting MAC CE). The SL CSI reporting MAC CE may include a Channel Quality Indicator (CQI) and a Rank Indicator (RI). In addition, the SL CSI reporting MAC CE may be included in the SL MAC PDU.
The UE may maintain one sidelink CSI report timer (sl-CSI-report timer) for each source layer-2ID and destination layer-2ID pair associated with the UE. The sl-CSI-ReportTimer is used for a UE (for example, a second UE) that needs to send the sidestream CSI to follow a delay requirement indicated by a UE (for example, a first UE) that triggers the sidestream CSI, and a timing duration of the sl-CSI-ReportTimer may be determined according to a delay indicated by the sl-latenbaund-CSI-Report. For example, the timing duration of the sl-CSI-ReportTimer is equal to the delay indicated by the sl-LatencyBound-CSI-Report, which is, for example, 50 slots (slots), or other durations may be used.
For example, the first UE corresponds to a source layer-2ID and destination layer-2ID pair with the second UE. And after receiving the first sidelink control information from the first UE, the second UE determines that SL-CSI reporting is triggered. And if the sl-CSI-report timer corresponding to the source layer-2ID and the destination layer-2ID is not in the running state, the second UE starts the sl-CSI-report timer. When the SL-CSI-ReportTimer times out, if the second UE has not sent the sidelink CSI, the second UE cancels the triggered SL-CSI reporting, that is, the second UE does not send the sidelink CSI to the first UE. If the SL-CSI-Reporting timer is running and there are SL resources capable of accommodating the SL CSI Reporting MAC CE and its subheader, the second UE may generate and transmit a Sidelink CSI Reporting MAC CE and stop the SL-CSI-Reporting timer.
Optionally, after sending the first sidelink control information, the first UE may start a first timer (or referred to as timer 1) without starting a fourth timer, where the first timer may indicate a time for one UE to monitor the sidelink control information after triggering SL CSI reporting, and the first UE may monitor the sidelink control information during a running time of the first timer to wait for receiving the sidelink CSI from the second UE. For example, the first UE may start the first timer in a first time domain unit after PSCCH (or the first side row control information itself, or PSCCH corresponding to the first side row control information, or HARQ feedback from the second UE for SL transmission corresponding to the first side row control information) corresponding to the first side row control information. Wherein, SL transmission may refer to transmission of PSCCH, or to transmission of PSCCH and PSCCH. The HARQ feedback of the SL transmission corresponding to the first sideline system control information means that the first sideline system control information may schedule the SL transmission, and a receiving end (e.g., a second UE) may send the HARQ feedback of the SL transmission after receiving the SL transmission to indicate whether the SL transmission is successfully received. The "time domain unit" in the embodiments of the present application is, for example, an Orthogonal Frequency Division Multiplexing (OFDM) symbol (symbol), a slot, a mini-slot (mini-slot), or the like. In this embodiment of the present application, for an SCI, the first time-domain unit after the SCI may refer to a first time-domain unit located after a time-domain position of a secondary SCI corresponding to the SCI in a time domain. Wherein, the SCI is, for example, a primary SCI or a secondary SCI, if the SCI is a primary SCI, the secondary SCI corresponding to the SCI refers to the secondary SCI corresponding to the primary SCI, and if the SCI is a secondary SCI, the secondary SCI corresponding to the SCI refers to the SCI itself. If the SCI is a primary SCI and a secondary SCI, the corresponding secondary SCI of the SCI is the secondary SCI of the SCI. For the secondary SCI, the first time domain unit after the secondary SCI may refer to the first time domain unit located after the last time domain unit where the secondary SCI is located in the time domain. The first time domain unit after the SCI may refer to a first time domain unit located after the last time domain unit where the SCI is located in the time domain.
It should be noted that in the embodiment of the present application, there may be a plurality of listening behaviors of the first UE (e.g., listening behavior during runtime of the first timer, or listening behavior during the first time period, etc.). For example, one listening behavior includes the first UE listening for sidestream control information, where listening for sidestream control information includes, for example, listening for SCIs, which may include a primary SCI and/or a secondary SCI; for another example, the other listening behavior includes the first UE listening to the PSCCH; for another example, yet another listening behavior includes the first UE listening to the PSCCH and PSCCH. The first UE may select one of the above listening actions to perform, which may be determined by the first UE, configured by the second UE, configured by the network device, or specified by a protocol, etc. In the embodiment of the present application, the monitoring of the sidestream control information by the first UE is taken as an example for description.
Or, optionally, after the first UE transmits the first sidelink control information, a fourth timer (for example, referred to as timer 4) may be started, and a timing duration of the fourth timer may indicate a preparation time of the second UE before transmitting the sidelink CSI. Sending the first sidelink control information from the first UE to the second UE, where the second UE needs a certain preparation time, and in this preparation time, the second UE does not send the sidelink CSI, and the first UE does not receive the sidelink CSI from the second UE, so the first UE may start a fourth timer, and a timing duration of the fourth timer may indicate a processing delay of the second UE, for example, the timing duration of the fourth timer may include one or more of: a time at which the second UE decodes (decode) the psch (or, alternatively, the first sidelink control information), a time at which the second UE is ready to transmit sidelink CSI, a time at which a Physical Sidelink Feedback Channel (PSFCH) is received and processed, a TX-RX/RX-TX switching time, a minimum interval between an end of a last symbol of the psch and a start of a first symbol of the corresponding PSFCH (e.g., a sidelink minimum time interval PSFCH). In the running time of the fourth timer, the first UE does not need to monitor the sidestream control information, so as to save the power consumption of the first UE. And when the fourth timer times out, the first UE restarts the first timer, and the first UE may monitor the sidestream control information during the running time of the first timer to wait for receiving the sidestream CSI from the second UE. For example, the first UE may start the fourth timer in a first time domain unit after PSCCH (or the first side row control information itself, or PSCCH corresponding to the first side row control information, or HARQ feedback from the second UE for SL transmission corresponding to the first side row control information) corresponding to the first side row control information. For example, the timing duration of the fourth timer may be configured by the second UE, the second UE may send third information to the first UE, the third information may indicate the timing duration of the fourth timer, and the first UE may know the timing duration of the fourth timer after receiving the third information from the second UE. The third information is included in, for example, a PC5-RRC message or a MAC CE. The timing duration of the fourth timer may also be configured by the first UE, or configured by the network device, or preconfigured. The first UE may send information indicating a timing duration of the fourth timer to the second UE. The timing duration of the first timer may be configured, for example, by the first UE, and the first UE may send information indicating the timing duration of the first timer to the second UE. Or, the timing duration of the first timer may also be configured by the second UE, and the second UE sends information indicating the timing duration of the first timer to the first UE. Or, the timing duration of the first timer may also be determined by the first UE and the second UE respectively. In the following, the first UE configures or determines the timing duration of the first timer.
For example, the first UE starts the fourth timer first and then starts the first timer, the first UE may configure the timing duration of the first timer as a difference between the delay indicated by the sl-latency bound-CSI-Report and the timing duration of the fourth timer. Alternatively, the first UE may configure the timing duration of the first timer to be equal to the delay indicated by the sl-LatencyBound-CSI-Report. Alternatively, the first UE may obtain a Channel Busy Rate (CBR), and may determine a timing duration of the first timer (or determine a minimum timing duration of the first timer) according to the CBR. For example, if the occupancy of the CBR is high (e.g., the occupancy of the CBR indicated by the CBR is greater than or equal to the first threshold), the timing duration of the first timer determined by the first UE may be longer (e.g., the timing duration of the first timer is determined to be greater than the second threshold, or the minimum timing duration of the first timer is determined to be greater than the second threshold), because there is a possibility that the channel contention is large at this time and the channel status is not good enough, the first UE may wait for receiving the sidelink CSI for a longer time, so as to improve the success rate of receiving the sidelink CSI; for another example, if the occupancy of the CBR is low (e.g., the occupancy of the CBR is less than the first threshold), the timing duration of the first timer determined by the first UE may be short (e.g., the timing duration of the first timer is determined to be less than the third threshold, or the minimum timing duration of the first timer is determined to be less than the third threshold), because the channel state is good at this time, the first UE may be able to receive the sidelink CSI in a short time, and the time is not too long, so that the power consumption of the first UE may be saved. For example, the timing duration of the first timer and the CBR may be in a direct or positive relationship, or the timing duration of the first timer and the CBR are not in a simple direct relationship, but if the CBR indicates a higher occupancy rate, the timing duration of the first timer may be longer. One or more of the first threshold, the second threshold, the third threshold may be configurable by the first UE, or by the network device, or preconfigured, or specified by a protocol, etc. The second threshold and the third threshold may be equal or unequal. Under the condition that the value of the CBR is not changed, the longer the timing duration of the first timer is, the more resources with lower interference that can be selected when the second UE transmits the side-row CSI are, and the higher the transmission success rate is. The timing duration of the first timer is determined according to the CBR, so that a compromise can be made between the interference level of the resource selected by the second UE and the monitoring duration of the first UE, and the sending success rate of the second UE is improved on the premise of saving the power consumption of the first UE as much as possible. For another example, the first UE may obtain a mapping relationship between the CBR range and the timing duration of the first timer, and determine the timing duration of the first timer according to the mapping relationship between the CBR range and the timing duration of the first timer and the obtained CBR. For example, the first UE determines that the timing duration of the first timer is the timing duration of the first timer corresponding to the CBR range in which the obtained CBR is located. Or, the first UE may obtain a mapping relationship between the CBR range and the minimum timing duration of the first timer, and determine the minimum timing duration of the first timer according to the mapping relationship between the CBR range and the minimum timing duration of the first timer and the obtained CBR. For example, the first UE determines that the minimum timing duration of the first timer is the minimum timing duration of the first timer corresponding to the CBR range in which the obtained CBR is located. The mapping relationship between the CBR range and the timing duration of the first timer, or the mapping relationship between the CBR range and the minimum timing duration of the first timer, may be configured by the network device, or preconfigured, or specified by a protocol, and the like. The first UE may determine a timing duration of the first timer if the first UE determines a minimum timing duration of the first timer, the timing duration of the first timer being greater than or equal to the minimum timing duration of the first timer. Alternatively, the timing duration of the first timer or the minimum timing duration of the first timer may also be configured by the network device, for example, the network device may send fourth information to the first UE and/or the second UE, and the fourth information may indicate the timing duration of the first timer (or indicate the minimum timing duration of the first timer). After the first UE and/or the second UE receives the fourth information, the timing duration of the first timer (or the minimum timing duration of the first timer) can be obtained. Optionally, the first UE sends information indicating a minimum timing duration of the first timer to the second UE. Or the second UE sends information indicating the minimum timing duration of the first timer to the first UE. And under the condition that the first UE and/or the second UE obtain the minimum timing duration of the first timer, the first UE determines the timing duration of the first timer, wherein the timing duration is greater than or equal to the minimum timing duration of the first timer. The first UE sends information used for indicating the timing duration of the first timer to the second UE. Or the second UE sends information indicating the timing duration of the first timer to the first UE. The network device configures the timing duration of the first timer or the minimum timing duration of the first timer, so that a situation that the second UE cannot select a resource with less interference due to too short timing duration of the first timer can be avoided as much as possible, a situation that the second UE does not select the resource within the running time of the first timer due to too short timing duration of the first timer can be avoided as much as possible, or a situation that the network device of the second UE does not have access to scheduling the resource used within the timing duration of the first timer for the second UE due to too short timing duration of the first timer can be avoided as much as possible.
It should be noted that the network device described in the embodiment of the present application may be a network device serving a first UE, or may be a network device serving a second UE. In addition, the network device serving the first UE and the network device serving the second UE may be the same network device or different network devices.
After the first UE starts the first timer, before the first timer expires, if the first UE receives the sidestream CSI from the second UE or the first UE successfully decodes the MAC PDU including the sidestream CSI from the second UE, the first UE may stop running the first timer.
Or after the first UE starts the fourth timer and before the fourth timer expires, if the first UE receives the sidelink CSI from the second UE or the first UE successfully decodes the MAC PDU including the sidelink CSI from the second UE, the first UE may stop running the fourth timer.
Alternatively, the first uplink control information may also schedule a corresponding psch or MAC PDU, for example, if the psch is referred to as a first psch and the MAC PDU is referred to as a first MAC PDU, the first UE may also transmit the first psch or the first MAC PDU to the second UE when transmitting the first uplink control information. The second UE needs to decode both the first sidelink control information and the first PSSCH (or first MAC PDU), and the second UE can send the sidelink CSI to the first UE only when both the first sidelink control information and the first PSSCH (or first MAC PDU) are successfully decoded, and the second UE may not be able to send the sidelink CSI to the first UE no matter whether the decoding of the first sidelink control information or the first PSSCH (or first MAC PDU) fails. After receiving the first lateral control information, the second UE may send second feedback information to the first UE, where the second feedback information is, for example, Negative Acknowledgement (NACK) if the second UE fails to decode (or receives) the first psch (or the first MAC PDU), and indicates that the first psch (or the first MAC PDU) fails to be received, and the second feedback information is, for example, positive Acknowledgement (ACK) if the second UE succeeds to decode (or receives) the first psch (or the first MAC PDU), and indicates that the first psch (or the first MAC PDU) is successfully received. For the first UE, after the first UE starts the first timer, before the first timer expires, if the second feedback information is used to indicate that the reception of the first pscch (or the first MAC PDU) fails, the first UE may stop the first timer. After the first UE starts the fourth timer, before the fourth timer expires, if the second feedback information is used to indicate that the reception of the first pscch (or the first MAC PDU) fails, the first UE may stop the fourth timer. So that the first UE does not start the first timer due to the fourth timer expiring. Because if the second feedback information indicates that the first psch (or the first MAC PDU) is received in failure, indicating that the second UE cannot transmit the sidelink CSI to the first UE, the first UE does not need to wait for receiving the sidelink CSI any more, and the first UE may stop the first timer, so as to save power consumption of the first UE.
Referring to fig. 3, the first UE starts a first timer after sending the first sidelink control information, and listens to the sidelink control information during the running time of the first timer. For example, the first UE receives the second feedback information from the second UE during the running time of the first timer, and stops the first timer if the second feedback information indicates a failure in receiving the first PSSCH (or the first MAC PDU). Since the second feedback information indicates that the first psch reception failed, optionally, the first UE may retransmit the first psch (or first MAC PDU). To retransmit the first PSSCH (or first MAC PDU), the first UE also needs to send control information to the second UE to schedule the retransmitted first PSSCH (or first MAC PDU). For example, the first UE sends third side-row control information to the second UE, the third side-row control information including, for example, the primary SCI and/or the secondary SCI, and the third side-row control information may schedule a retransmitted first pscch (or first MAC PDU). Optionally, because the first UE does not receive the side CSI from the second UE, the third side control information may also be used to trigger the second UE to send the side CSI to the first UE. Then the first UE may start the first timer again after sending the third sidelink control information in order to wait for the receive sidelink CSI. For example, the first UE may receive the sidelink CSI from the second UE during the runtime of the first timer, the first UE may stop the first timer.
Referring to fig. 4 again, the first UE starts the fourth timer after sending the first sidelink control information, starts the first timer when the fourth timer is out of time, and monitors the sidelink control information during the running time of the first timer. For example, the first UE receives the second feedback information from the second UE during the operation time of the first timer, and stops the first timer if the second feedback information indicates a failure in receiving the first pscch (or the first MAC PDU). Since the second feedback information indicates that the first psch was received unsuccessfully, the first UE may optionally retransmit the first psch (or first MAC PDU). For example, the first UE sends third sidelink control information to the second UE, which may schedule a retransmitted first pscch (or first MAC PDU). Optionally, because the first UE does not receive the sidelink CSI from the second UE, the third sidelink control information may also be used to trigger the second UE to send the sidelink CSI to the first UE. Then the first UE may start the fourth timer again after transmitting the third sidelink control information in order to wait for the reception sidelink CSI, and start the first timer when the fourth timer expires. For example, the first UE may receive the sidelink CSI from the second UE during the runtime of the first timer, the first UE may stop the first timer.
In addition, fig. 3 and 4 also show the delay indicated by sl-LatencyBound-CSI-Report.
S202, the second UE sends the second sidelink control information to the first UE, and correspondingly, the first UE receives the second sidelink control information from the second UE in a first time period after sending the first sidelink control information.
The second sidelink control information may be used to schedule a MAC PDU, which is an sidelink MAC PDU. The MAC PDU may be used to carry sidelink CSI and/or data. That is, the MAC PDU scheduled by the second sidelink control information may carry the sidelink CSI required by the first UE (if this is the case, the second sidelink control information may be sent under the trigger of the first sidelink control information), or carry data (if this is the case, the second sidelink control information may not be sent under the trigger of the first sidelink control information, and it may be considered that the first sidelink control information and the second sidelink control information have no relation), or carry the sidelink CSI and the data.
The second sidelink control information is used for scheduling MAC PDUs, it is understood that the second control information may indicate that there is a transmission (e.g., MAC PDU) on a sidelink shared channel (SL-SCH). Alternatively, it is understood that the second control information may be used to schedule Transport Blocks (TBs), which may carry MAC PDUs.
The second sideline control information is, for example, SCI, or the second sideline control information is included in SCI. For example, the SCI includes a secondary SCI, or the SCI includes a primary SCI and a secondary SCI.
Take the example where the second sidelink control information is SCI. The first UE receives the second sidelink control information from the second UE, for example, the first UE receives an SCI, and the SCI includes source layer-1ID and destination layer-1ID, which are consistent with the source and destination pair corresponding to the PC5-RRC connection between the first UE and the second UE. "consistent" specifically means: the SCI includes a source layer-1ID that is the 8 Least Significant Bits (LSBs) of the source layer-2ID of the second UE, and a destination layer-1ID that is the 8 LSBs of the destination layer-2ID (or source layer-2ID, or layer2-ID) of the first UE. So-called 8LSB, i.e. the lower 8 bits.
Alternatively, the first UE receives an SCI from the second UE, for example, the first UE receives an SCI, and the sidelink identity information (sidelink identity information) corresponding to the SCI is consistent with the source and destination pair corresponding to the PC5-RRC connection between the first UE and the second UE. The sideline identity information may include a case type indicator (cast indicator), a source layer-1ID and a destination layer-1 ID. "consistent" specifically means: the cast type indicator indicates unicast, and the Source Layer-1ID included in the sidestream identity information is 8LSB of the Source Layer-2ID of the second UE, and the destination Layer-1ID included in the sidestream identity information is 8LSB of the destination Layer-2ID (or Source Layer-2ID, or Layer2-ID) of the first UE.
The first time period may be used to wait for the sideline CSI or the first time period may be used to receive the sideline CSI. It may be appreciated that the first UE expects to receive (or, alternatively, waits to receive) the sidelink CSI for a first time period. That is, after the first UE sends the first sidelink control information to the second UE, since the first UE needs to wait for receiving the sidelink CSI, a first time period is set, and the first UE continues to monitor the sidelink control information in the first time period to receive the sidelink CSI. There are various implementations of the first time period, as described by way of example below.
As a first optional implementation manner of the first time period, the first time period is a time period during which the first UE monitors the sidestream control information after sending the first sidestream control information, and the first time period is considered not to belong to the sidestream DRX activation time of the first UE.
As a second optional implementation manner of the first time period, the first time period is a time period during which the first UE monitors the sidelink control information after sending the first sidelink control information, and the first time period is satisfied, and neither the sl-DRX-inactivity timer nor the sl-DRX-onDurationTimer of the first UE is running. In other words, the first time period is: and the first UE monitors the side-line control information after sending the first side-line control information, and the first UE has no running time period of the sl-DRX-InactivtyTimer and the sl-DRX-onDuration Timer. It is understood that the period in which the conditions 1 and 2 are satisfied may be regarded as the first period. The condition 1 is a time period for monitoring the sideline control information after the first UE sends the first sideline control information; condition 2 is that neither the sl-DRX-inactivity timer nor the sl-DRX-onduration timer of the first UE is running. If the first time period adopts the implementation manner, the time period for monitoring the sidestream control information after the first UE sends the first sidestream control information may or may not belong to the sidestream DRX activation time of the first UE. If the time period for monitoring the sidelink control information after the first UE sends the first sidelink control information belongs to the sidelink DRX activation time of the first UE, it is considered not to belong to the first time period if the sl-DRX-inactivity timer and/or the sl-DRX-onDurationTimer of the first UE run.
As a second optional implementation manner of the first time period, the first time period is a time period for monitoring the sidelink control information after the first UE sends the first sidelink control information, and the first time period is satisfied, and none of the sl-DRX-onduration timer, the sl-DRX-inactivytytimer, and the sl-DRX-retransmission timer of the first UE is running. In other words, the first time period is: and the first UE monitors the side control information after sending the first side control information, and the first UE has no running time period of the sl-DRX-onDuration timer, the sl-DRX-Inactivitytimer and the sl-DRX-Recransmissiontimer. It is understood that the period in which the conditions 1 and 3 are satisfied may be regarded as the first period. Condition 1 can be referred to the description hereinbefore; condition 2 is that none of the sl-DRX-onDurationTimer, sl-DRX-inactivytytimer, and sl-DRX-retransmission timer of the first UE is running. If the first time period adopts the implementation manner, the time period for monitoring the sidestream control information after the first UE sends the first sidestream control information may or may not belong to the sidestream DRX activation time of the first UE. If a period of monitoring the lateral control information after the first UE transmits the first lateral control information belongs to a lateral DRX active time of the first UE, it is considered not to belong to the first period if a period of one or more timers of an sl-DRX-inactivytytimer, an sl-DRX-onDurationTimer, or an sl-DRX-retransmission timer of the first UE is running.
As to which way the first time period is implemented, the first time period may be configured by the first UE or the second UE, or may be configured by the network device, or may be specified by a protocol, etc.
In the process of introducing the time manner of the first time period, a time period for the first UE to monitor the sidelink control information after transmitting the first sidelink control information is mentioned, for example, the time period is referred to as a second time period. The second time period may also be described as a time period after the first UE transmits the first sidelink control information and receives the sidelink control information. The description of the second time period may be understood that the first UE monitors the sidelink control information for receiving the sidelink CSI after transmitting the first sidelink control information. There are various implementations of the second time period, which are described below by way of example.
As an alternative to the second time period, the second time period is, for example, a time period of operation of the first timer, and reference may be made to the above description for the first timer.
As another optional implementation of the second time period, the second time period is, for example, a time period in which the first UE is expected to receive (or, is expected to monitor) the sidelink CSI after sending the first sidelink control information. For example, the maximum duration of the time period for the first UE to send the first sideline control information and expect the receiving sideline CSI is the delay indicated by sl-LatencyBound-CSI-Report.
As another optional implementation manner of the second time period, the second time period is, for example, a time period during which an sl-CSI-ReportTimer runs, and the sl-CSI-ReportTimer may indicate a time duration from when the second UE receives the first sidelink control information to when the second UE sends the sidelink CSI. The sl-CSI-report timer can be maintained in the second UE, and the first UE does not maintain the sl-CSI-report timer; or, the sl-CSI-ReportTimer is maintained in the second UE and the first UE, for example, after the first UE sends the first sideline control information, the sl-CSI-ReportTimer may also be started, for example, the first UE may start the sl-CSI-ReportTimer and the first timer at the same time, or may start the sl-CSI-ReportTimer and the fourth timer at the same time, or may start the sl-CSI-ReportTimer at other times. For the second UE, the second UE sends the sidelink CSI to the first UE within the running time of the sl-CSI-report timer. For the first UE, the sl-CSI-ReportTimer may indicate a maximum duration until the receipt of the sidelink CSI, or the sl-CSI-ReportTimer may indicate a maximum duration for the receipt of the sidelink CSI. If the sl-CSI-Report timer is maintained in the second UE and the first UE does not maintain the sl-CSI-Report timer, because the timing duration of the sl-CSI-Report timer of the second UE is determined according to the time delay indicated by the sl-Latencybound-CSI-Report of the second UE, which is sent to the second UE by the first UE, the first UE can obtain the running time of the sl-CSI-Report timer although the sl-CSI-Report timer is the timer maintained by the second UE through estimation. Alternatively, if both the first UE and the second UE maintain an sl-CSI-Reporttimer, the first UE may determine the running time of the sl-CSI-Reporttimer of the first UE.
S203, the first UE does not start the sl-DRX-InactivetyTimer of the first UE.
In the embodiment of the application, if the first UE receives the second sidelink control information from the second UE within the first time period, the first UE does not start the sl-DRX-inactivity timer. Since the first time period is already available for the first UE to receive the downlink CSI, the first UE does not start the sl-DRX-inactivity timer and does not delay the reception of the downlink CSI by the first UE. And because the first UE does not start the sl-DRX-inactivity timer, the monitoring time of the first UE is not extended any more (if the first UE starts the sl-DRX-inactivity timer, the first UE needs to keep monitoring the side-row control information during the operation period of the sl-DRX-inactivity timer), so that the power consumption of the first UE can be reduced.
For example, in a first time period after the first UE sends the first sidelink control information to the second UE, if the second sidelink control information is received from the second UE, the first UE may default to not start the sl-DRX-inactivity timer of the first UE; or, whether the sl-DRX-inactivity timer of the first UE is started within a first time period after the first UE sends the first uplink control information to the second UE may also be configured by the network device, or determined by the first UE, or configured by the second UE.
The first UE may inform the second UE of the determination, if determined by the first UE itself. For example, the first UE sends first information to the second UE, where the first information may indicate that the first UE does not start the sl-DRX-inactivity timer for a first period of time after sending the message for triggering the second UE to send the sidelink CSI, or indicate that the first UE starts the sl-DRX-inactivity timer for a first period of time after sending the message for triggering the second UE to send the sidelink CSI (that is, if receiving an SCI from the second UE, the first UE starts the sl-DRX-inactivity timer). The first information is, for example, a message including sl-LatencyBound-CSI-Report, or may be other messages. Alternatively, if the first UE determines the determination result by itself, the first UE may also inform the second UE of the determination result through the SCI. For example, the SCI may instruct the first UE not to start the sl-DRX-inactivity timer for a first time period after sending the message for triggering the second UE to send the lateral CSI, or instruct the first UE to start the sl-DRX-inactivity timer for a first time period after sending the message for triggering the second UE to send the lateral CSI. The SCI is, for example, first sideline control information (or an SCI including the first sideline control information), or the SCI is, for example, another SCI except the first sideline control information.
Alternatively, if determined by the second UE, the second UE may inform the first UE of the determination result. For example, the second UE sends first information to the first UE, where the first information may indicate that the first UE does not start the sl-DRX-inactivity timer in a first time period after sending the message for triggering the second UE to send the lateral CSI, or indicate that the first UE starts the sl-DRX-inactivity timer in a first time period after sending the message for triggering the second UE to send the lateral CSI. Or, the second UE sends an SCI to the first UE, where the SCI may indicate that the first UE does not start the sl-DRX-inactivity timer in a first time period after sending the message for triggering the second UE to send the sidelink CSI, or indicate that the first UE starts the sl-DRX-inactivity timer in a first time period after sending the message for triggering the second UE to send the sidelink CSI. The SCI is, for example, second sideline control information (or an SCI including the second sideline control information), or the SCI is, for example, an SCI other than the second sideline control information.
Optionally, the first information may be, for example, a PC5-RRC message, or may also be a Control Element (CE) or the like. The PC5-RRC message is, for example, an rrcreeconfigurationsidelink message, or may be another message.
Alternatively, if determined by the network device, the network device may inform the first UE and/or the second UE of the determination. Taking a process of informing the first UE by the network device as an example, for example, the network device sends first information to the first UE, where the first information may indicate that the sl-DRX-inactivity timer is not started in a first time period after the first UE sends a message for triggering the second UE to send the sidestream CSI, or indicate that the sl-DRX-inactivity timer is started in the first time period after the first UE sends the message for triggering the second UE to send the sidestream CSI. The first information in this case is included in, for example, an RRC message, or included in a MAC CE, or included in Downlink Control Information (DCI), or may be included in another message that the network device communicates with the UE.
If the first UE enters a sidestream DRX active time (if the first time period is also considered to belong to the sidestream DRX active time, then here the sidestream DRX active time does not include the first time period, but refers to the normal sidestream DRX active time), then the first UE monitors the sidestream control information. If the first UE monitors the sidestream control information, the first UE may start the sl-DRX-InactivetyTimer. That is, the first UE may start the sl-DRX-inactivity timer according to the monitoring condition of the sidestream control information within the normal sidestream DRX activation time.
If the second UE also uses the sidestream DRX mechanism, optionally, the second UE may also control the corresponding timer as the first UE, for example, if the second UE sends the second sidestream control information to the first UE in the first time period, the second UE may also not start the sl-DRX-inactivytytimer of the second UE. Therefore, the side-row DRX activation time and the like of the first UE and the second UE are kept consistent, and the communication between the first UE and the second UE is facilitated. Alternatively, the second UE may not have to be concerned with the sl-DRX-inactivity timer, e.g., the sl-DRX-inactivity timer of the second UE may be started or stopped in a normal manner, regardless of the first time period, or regardless of the first UE triggering the second UE to transmit the side CSI.
Optionally, the embodiment of the present application may further include subsequent S204 to S209.
S204, the second UE sends the MAC PDU to the first UE in the first time period. The MAC PDU is, for example, a MAC PDU indicated by the second sidelink control information. Wherein S203 may occur before S204, or S203 may occur after S204, or S203 and S204 may occur simultaneously.
The second UE may send the MAC PDU to the first UE in the first time period in a variety of different implementations, or the MAC PDU sent by the second UE to the first UE in the first time period may be sent by a variety of different implementations, which is described in the following example.
1. A first implementation of a MAC PDU that the second UE transmits to the first UE during the first time period, the MAC PDU can include the sidelink CSI but cannot include data, or the MAC PDU can include the sidelink CSI but cannot include any information other than the sidelink CSI. Alternatively, the first implementation is described as the second UE being able to send the sidelink CSI to the first UE and being unable to send data to the first UE.
That is, in this implementation, the second UE may only send SL CSI reporting to the first UE during the first time period, and may not send data to the first UE. It can be reversely understood that, in the first time period, the second UE cannot generate (or cannot transmit to the first UE) such MAD PDU: there is no SL CSI reporting MAC CE in the MAC PDU (or PSSCH) (it is understood that the MAC PDU does not include side CSI), or the MAC PDU includes a non-zero MAC Service Data Unit (SDU). By including a non-zero MAD SDU, we mean to include data. That is, the MAC PDU sent by the second UE to the first UE in the first time period needs to include the sidestream CSI, and if the sidestream CSI is not included, the second UE cannot send the MAC PDU to the first UE. In addition, the MAC PDU transmitted by the second UE to the first UE during the first period of time cannot include data, and if data is included, the second UE cannot transmit the MAC PDU to the first UE even if the MAC PDU also includes the sidestream CSI. If the second UE sends the side-row CSI to the first UE, the side-row CSI is, for example, included in a SL CSI reporting MAC CE, which may be included in a MAC PDU.
Fig. 5 may be referred to as an illustration of a first UE receiving sidelink CSI during a first time period. The dashed boxes in fig. 5 indicate the first time periods, and fig. 5 illustrates the first time periods not belonging to the sidestream DRX activation time of the first UE, but the first time periods and the sidestream DRX activation time of the first UE have an overlapping region, and the hatched regions in fig. 5 indicate the overlapping region of the first time periods and the sidestream DRX activation time of the first UE. In addition, fig. 5 also shows the delay indicated by sl-LatencyBound-CSI-Report. It can be seen that after the first UE triggers CSI to the second UE (e.g., after the first UE sends the first sidelink control information to the second UE), the first time period starts, and during the first time period, the first UE monitors the sidelink control information. During the first time period, the first UE receives the sidelink CSI from the second UE, but does not receive other information from the second UE.
For a corresponding newly transmitted SCI (e.g., the second sidelink control information is the SCI, or the second sidelink control information is included in the SCI), the second UE selects a destination for a sidelink grant (SL grant) associated with the SCI, the destination needs to satisfy the PSCCH (or the SCI, or the SL grant associated with the SCI) corresponding to the SCI within a time when the destination triggers the SL CSI reporting of the second UE to monitor PSCCH and/or pscsch, and the second UE has a SL CSI reporting MAC CE of the destination (i.e., the second UE needs to send sidelink CSI to the destination), or the destination needs to satisfy the PSCCH (or the SCI, or the SL grant) corresponding to the SCI within a sidelink activation time of the destination. The SL grant associated with the SCI may refer to the SCI carried in the SL grant. The second UE may correspond to multiple logical channels, and the different MAC PDUs include information from different logical channels. The second UE may want to send a MAC PDU to multiple UEs (or multiple destinations), and then the second UE needs to select a corresponding UE from the multiple UEs (or select a corresponding destination from the multiple destinations) to send the MAC PDU, for example, the second UE may select according to a Logical Channel Priority (LCP), and may preferentially send a MAC PDU (or MAC CE) corresponding to a logical channel with a high priority. For the second sidelink control information, the second UE may select a MAC CE with the highest priority or a destination corresponding to a logical channel among the MAC CEs and logical channels that satisfy the first rule. The first rule includes, for example, a first condition including, for example: the first time domain resource is located in a first time period after the destination triggers the second UE to send the sidelink CSI (for example, the destination is the first UE, that is, the first time domain resource is located in the first time period after the first UE sends the first sidelink control information), or the first time domain information is located in the sidelink DRX activation time of the destination. The first time domain resource is a time domain resource occupied by the second sideline control information, or a time domain resource occupied by a PSCCH corresponding to the second sideline control information, or a time domain resource occupied by a SL grant corresponding to the second sideline control information.
Interpreting the first condition in another way, the first condition comprises: the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a sidelink DRX activation time of a destination corresponding to a MAC CE (including an SL CSI reporting MAC CE) or a logical channel, or the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a time of monitoring the PSCCH and/or the PSCCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. That is to say, the second UE sends the MAC PDU to the first UE as much as possible within a first time period after the first UE triggers the CSI, or sends the MAC PDU to the first UE within a lateral DRX activation time of the first UE, so as to improve a reception success rate of the first UE for the MAC PDU.
If the first implementation is employed, the first UE may stop running the first timer if the first UE receives the sidestream CSI from the second UE or the first UE successfully decodes the MAC PDU including the sidestream CSI from the second UE.
In the first implementation manner, the second UE only needs to send the sidelink CSI to the first UE, which can reduce the sending time and improve the efficiency of obtaining the sidelink CSI by the first UE. If the transmission error in one time needs to be retransmitted, the side-row CSI only needs to be retransmitted without retransmitting other information, so that the retransmission time can be saved.
2. In a second implementation manner of the MAC PDU sent by the second UE to the first UE in the first time period, the second UE may send the sidelink CSI and/or data to the first UE, where the sidelink CSI and the data may be included in the same MAC PDU or may be included in different MAC PDUs. Alternatively, the second implementation may be described as the second UE being capable of sending the sidelink CSI and/or data to the first UE. The data includes, for example, data from a Sidelink Control Channel (SCCH) and/or data from a Sidelink Traffic Channel (STCH).
That is, in this implementation, the second UE may transmit the sidelink CSI without data to the first UE during the first time period, or the second UE may transmit the data without data to the first UE during the first time period, or the second UE may transmit the sidelink CSI and the data to the first UE during the first time period.
Fig. 6 may be referred to as a diagram illustrating a first UE receiving sidelink CSI during a first time period. The dashed boxes in fig. 6 indicate the first time periods, and fig. 6 illustrates the first time periods not belonging to the sidestream DRX activation time of the first UE, but the first time periods and the sidestream DRX activation time of the first UE have an overlapping region, and the hatched region in fig. 6 indicates the overlapping region of the first time periods and the sidestream DRX activation time of the first UE. In addition, fig. 6 also shows the delay indicated by sl-LatencyBound-CSI-Report. It can be seen that after the first UE triggers CSI to the second UE (e.g., after the first UE sends the first sidelink control information to the second UE), the first time period starts, and during the first time period, the first UE monitors the sidelink control information. In the first time period, the first UE receives the sidelink CSI from the second UE and also receives data from the second UE, and fig. 6 illustrates an example in which the data and the sidelink CSI are included in different MAC PDUs.
For a corresponding newly transmitted SCI (e.g., the second sideline control information is the SCI, or the second sideline control information is included in the SCI), the second UE selects a destination for the SL grant associated with the SCI, where the destination needs to satisfy the PSCCH (or the SCI, or the SL grant associated with the SCI) within a time period of PSCCH and/or PSCCH monitoring after the destination triggers SL CSI reporting of the second UE, or the destination needs to satisfy the PSCCH (or the SCI, or the SL grant associated with the SCI) within a sideline DRX activation time of the destination. For example, the second UE may select destination according to the LCP, and may preferentially transmit the MAC PDU (or MAC CE) corresponding to the logical channel with high priority. For the second sidelink control information, the second UE may select a MAC CE with the highest priority or a destination corresponding to a logical channel among the MAC CEs and logical channels that satisfy the first rule. The first rule includes, for example, a second condition including, for example: the first time domain resource is located in a first time period after the destination triggers the second UE to send the sidelink CSI, or the first time domain information is located in the activation time of the sidelink DRX of the destination. The first time domain resource is a time domain resource occupied by the second sideline control information, or a time domain resource occupied by a PSCCH corresponding to the second sideline control information, or a time domain resource occupied by a SL grant corresponding to the second sideline control information.
Interpreting the second condition in another way, the first condition then comprises: the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a sidelink DRX activation time of a destination corresponding to a MAC CE (including an SL CSI reporting MAC CE) or a logical channel, or the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a time of monitoring the PSCCH and/or the PSCCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. That is to say, the second UE sends the MAC PDU to the first UE as soon as possible within a first time period after the first UE triggers the CSI, or sends the MAC PDU to the first UE within a lateral DRX activation time of the first UE, so as to improve a reception success rate of the first UE for the MAC PDU.
If this implementation is used, if the first UE simply receives data from the second UE without receiving the sidestream SCI, and if the first timer has not timed out, the first UE does not stop the first timer, but keeps the first timer running to wait for the receipt of the sidestream SCI from the second UE. The first UE may stop running the first timer if the first UE receives the sidestream CSI from the second UE or the first UE successfully decodes a MAC PDU from the second UE that includes the sidestream CSI. Reference is made to fig. 6 for this.
In a second implementation manner, the second UE may send the sidelink CSI to the first UE, or may send data to the first UE, so that the first time period can be effectively utilized, and the first UE can obtain more information in the first time period. And the sidelink CSI and the data may be included in one MAC PDU, or may be included in different MAC PDUs, for example, if one MAD PDU is not enough to carry the sidelink CSI and all the data that the second UE needs to send, the second UE may send through multiple MAC PDUs, which is more flexible.
3. In a third implementation of the MAC PDU sent by the second UE to the first UE in the first time period, the second UE may send the sidelink CSI to the first UE, or send the sidelink CSI and data to the first UE, but if data is to be sent, the sidelink CSI and the data need to be included in the same MAC PDU. Or, the third implementation may also be described in that the second UE is capable of sending the sidelink CSI, or sending the sidelink CSI and the data to the first UE, and if the sidelink CSI and the data are sent, the sidelink CSI and the data are carried in the same MAC PDU. The data may comprise, for example, data from the SCCH and/or data from the STCH.
That is, in this implementation, the second UE may transmit the sidelink CSI without transmitting data to the first UE during the first time period, or the second UE may transmit the sidelink CSI and data to the first UE during the first time period. However, if the sidelink CSI and the data are to be transmitted to the first UE, the data need to be included in the same MAC PDU as the sidelink CSI, or the data can only be transmitted through the MAC PDU including the sidelink CSI, but not through the MAC PDU not including the sidelink CSI.
Fig. 7 may be referred to as an illustration of a first UE receiving sidelink CSI during a first time period. The dashed boxes in fig. 7 indicate the first period, and fig. 7 illustrates an overlapping area between the first period and the lateral DRX active time of the first UE, where the first period does not belong to the lateral DRX active time of the first UE, but the first period and the lateral DRX active time of the first UE overlap each other, and the hatched area in fig. 7 indicates the overlapping area between the first period and the lateral DRX active time of the first UE. In addition, fig. 7 also shows the delay indicated by sl-LatencyBound-CSI-Report. It can be seen that after the first UE triggers CSI to the second UE (e.g., after the first UE transmits the first sidelink control information to the second UE), a first time period begins during which the first UE listens to the PSCCH and/or pscsch. In the first time period, the first UE receives the sidelink CSI from the second UE and also receives data from the second UE, and the data and the sidelink CSI are included in the same MAC PDU.
It should be noted that, after the first UE transmits the first sidelink control information, the first UE may actually start the first timer immediately, that is, the first time period may start immediately, that is, the time when the first sidelink control information is completely transmitted and the starting time of the first time period may be the same time. However, in fig. 5, 6 and 7, there is a certain time delay from the end of the first sidelink control information transmission to the start time of the first time period, considering that the first UE may have a certain processing time.
For a corresponding newly transmitted SCI (for example, the second sideline control information is the SCI, or the second sideline control information is included in the SCI), the second UE selects a destination for the SL grant associated with the SCI, the destination needs to satisfy the PSCCH (or the SCI, or the SL grant associated with the SCI) in time after the destination triggers the SL CSI reporting of the second UE, and the second UE has the SL CSI reporting MAC CE of the destination, or the destination needs to satisfy the PSCCH (or the SCI, or the SL grant associated with the SCI) in the sideline DRX activation time of the destination. For example, the second UE may select destination according to the LCP, and may preferentially transmit the MAC PDU (or MAC CE) corresponding to the logical channel with high priority. For the second sidelink control information, the second UE may select a MAC CE with the highest priority or a destination corresponding to a logical channel among the MAC CEs and logical channels that satisfy the first rule. The first rule includes, for example, a third condition including, for example: the first time domain resource is located in a first time period after the destination triggers the second UE to send the side row CSI, or the first time domain information is located in the side row DRX activation time of the destination. The first time domain resource is a time domain resource occupied by the second sideline control information, or a time domain resource occupied by a PSCCH corresponding to the second sideline control information, or a time domain resource occupied by a SL grant corresponding to the second sideline control information.
Interpreting the third condition in another way, the third condition then comprises: the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a sidelink DRX activation time of a destination corresponding to a MAC CE (including an SL CSI reporting MAC CE) or a logical channel, or the PSCCH (or the second sidelink control information itself, or the SL grant associated with the second sidelink control information) corresponding to the second sidelink control information is within a time of monitoring the PSCCH and/or the PSCCH after the destination corresponding to the SL CSI reporting MAC CE triggers the SL CSI reporting of the second UE. That is to say, the second UE sends the MAC PDU to the first UE as soon as possible within a first time period after the first UE triggers the CSI, or sends the MAC PDU to the first UE within a lateral DRX activation time of the first UE, so as to improve a reception success rate of the first UE for the MAC PDU.
If such an implementation is employed, the first UE may stop running the first timer if the first UE receives the sidestream CSI from the second UE, or the first UE successfully decodes the MAC PDU from the second UE that includes the sidestream CSI.
In a third implementation manner, the second UE may send the sidelink CSI to the first UE, or may send data to the first UE, so that the first time period can be effectively utilized, and the first UE can obtain more information in the first time period. And the sidelink CSI and the data can be included in one MAC PDU, so that the transmission efficiency can be improved, and the efficiency of acquiring the sidelink CSI by the first UE can be improved. Also, if retransmission is involved, only one MAC PDU needs to be retransmitted, which also reduces retransmission time.
In S204, the second UE may transmit the MAC PDU to the first UE according to one of the above three implementations, for example, the mode used by the second UE is referred to as a first mode, and the first mode is, for example, the first implementation, the second implementation, or the third implementation as above. The first mode may be determined by the second UE itself, or determined by the first UE and notified to the second UE, or may be configured by the network device, or may be specified by a protocol, and the like.
If the first mode is determined by the second UE, the second UE needs to inform the first UE after determining the first mode, so that the first UE can clearly determine the mode of sending the MAC PDU by the second UE, and the MAC PDU from the second UE can be correctly received. For example, the second UE sends second information to the first UE, which may indicate the first manner. Alternatively, the second UE sends the SCI to the first UE, which may indicate the first manner. The SCI is, for example, second sideline control information (or an SCI including the second sideline control information), or the SCI is, for example, an SCI other than the second sideline control information.
Or, if the first mode is determined by the first UE, the first UE also needs to notify the second UE after determining the first mode, so that the second UE can send the MAC PDU to the first UE according to the first mode. For example, a first UE may send second information to a second UE, which may indicate a first manner. Alternatively, the first UE sends the SCI to the second UE, which may indicate the first manner. The SCI is, for example, first sideline control information (or an SCI including the first sideline control information), or the SCI is, for example, an SCI other than the first sideline control information.
Optionally, the first information may be, for example, a PC5-RRC message, or may also be a MAC CE, etc. The PC5-RRC message is, for example, an rrcreeconfigurationsidelink message, or may be another message.
Or, if the first mode is determined by the network device, the network device needs to inform the first UE and/or the second UE after determining the first mode. Taking the network device informing the first UE as an example, for example, the network device sends second information to the first UE, and the second information may indicate the first manner. The second information is included in the RRC message, or in the MAC CE, or in the DCI, or in another message that the network device communicates with the UE, for example.
S205, the first UE decodes the MAC PDU.
The first UE receives the second sidelink control information and the MAC PDU and decodes the MAC PDU according to the second sidelink control information.
S206, if the decoding of the MAC PDU fails, the first UE starts a second timer (alternatively referred to as timer 2). The second timer is, for example, sl-DRX-retransmission timer of the first UE, or may also be a timer newly defined in the embodiment of the present application.
If the first UE fails to decode the MAC PDU, the first UE cannot obtain information included in the MAC PDU (e.g., the MAC PDU carries sidestream CSI and/or data), and the first UE may send first feedback information to the second UE, the first feedback information indicating, for example, that the MAC PDU was received unsuccessfully (e.g., the first feedback information is a Negative Acknowledgement (NACK)). The first UE may start a second timer in addition to transmitting the first feedback information.
For example, the first UE may start the second timer in case of a failure to decode the MAC PDU. Or alternatively, if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and does not include data, the first UE may start the second timer if decoding of the MAC PDU fails; and if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and data, or indicates that the MAC PDU does not include sidelink CSI (and may also indicate that data is included or may also indicate that data is not included), the first UE may not start the second timer even if decoding of the MAC PDU fails, i.e., may not have to wait for retransmission of the MAC PDU. The second sidelink control information may indicate content included in the MAC PDU, and if the second sidelink control information indicates that the MAC PDU includes the sidelink CSI and does not include data, and the first UE does not successfully decode the MAC PDU, the first UE may start the second timer to wait for retransmission because only the sidelink CSI needs to be retransmitted and the required retransmission time is not long. And if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and data, the first UE may not wait for retransmission because the retransmission process includes the retransmission of the sidelink CSI and the retransmission of the data, the required retransmission time is longer, and the power consumption for the first UE is larger. Or, if the second sidelink control information indicates that the MAC PDU does not include sidelink CSI, the first UE actually mainly wants to receive the sidelink CSI, and if the MAC PDU does not include the sidelink CSI, the first UE may not need to wait for retransmission of the MAC PDU.
For example, the first UE may start the second timer in a first time domain unit after the PSSCH corresponding to the second sidelink control information is ended. For another example, the first UE may start the second timer in the first time domain unit after the first feedback information is sent.
S207, in the running time of the second timer, the first UE monitors the sidelink control information to wait for the retransmission of the MAC PDU.
During the running time of the second timer, the first UE listens for sidestream control information to wait for retransmission of the MAC PDU. The running time of the second timer may belong to the sidestream DRX active time of the first UE, or may not belong to the sidestream DRX active time of the first UE. Wherein the first UE may stop the second timer if the first UE receives the retransmitted MAC PDU before the second timer expires.
And S208, under the condition that the MAC PDU is failed to be decoded, the first UE starts a third timer. The timing duration of the third timer may, for example, indicate a preparation time for the second UE before retransmitting (or referred to as retransmitting) the MAC PDU. The third Timer is, for example, sl-DRX-HARQ-RTT-Timer of the first UE, or may also be a Timer newly defined in the embodiment of the present application.
That is, a certain time is required between the first UE transmitting the first feedback information and the second UE retransmitting the MAC PDU, that is, the second UE needs a certain preparation time to retransmit the MAC PDU, and it is obvious that the retransmitted MAC PDU will not be received by the first UE within the preparation time of the second UE. Therefore, the first UE may start the third timer, and during the running time of the third timer, the first UE does not need to monitor the sidestream control information, so as to save the power consumption of the first UE. For example, the third timer may be started in a first time domain unit after the pscch corresponding to the second sidelink control information is finished. For another example, the first UE may start the third timer in the first time domain unit after the first feedback information is sent.
For example, the first UE may start the third timer in case of a failure to decode the MAC PDU. Or alternatively, if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and does not include data, the first UE may start a third timer if decoding of the MAC PDU fails; and if the second sidelink control information indicates that the MAC PDU includes sidelink CSI and data, or indicates that the MAC PDU does not include sidelink CSI (and may also indicate that data is included or may also indicate that data is not included), the first UE may not start the third timer even if decoding of the MAC PDU fails, i.e., may not have to wait for retransmission of the MAC PDU. For the reason of such processing, reference is made to the description of S206.
And S209, when the third timer is over time, the first UE starts a second timer. S207 is then executed.
S206 and S208 to S209 are two parallel schemes, and the first UE selects one of the schemes to execute. As to which scheme is selected at all, it may be determined by the first UE itself, or configured by the network device, or specified by a protocol, etc.
Whether the first UE directly starts the second timer or starts the second timer when the third timer is overtime, the first UE may stop the second timer if the sl-CSI-ReportTimer is overtime, where the sl-CSI-ReportTimer may be maintained in the first UE and the second UE, or in the second UE, for which reference may be made to the foregoing description; or, when a second duration after the first UE triggers SL CSI reporting (for example, the first UE sends the first sidelink control information) arrives, the first UE may stop the second timer; alternatively, the first UE may stop the second timer when the maximum duration of the expected receive-side row CSI after the first UE triggers the SL CSI reporting (or the duration of the expected receive-side row CSI after the first UE triggers the SL CSI reporting) arrives. Wherein, the second duration is, for example, a delay indicated by sl-LatencyBound-CSI-Report, and the timing duration of sl-CSI-Report timer may be determined according to the delay indicated by sl-LatencyBound-CSI-Report. If the sl-CSI-Report timer is overtime, or the delay indicated by the sl-latenbound-CSI-Report is reached, or the maximum duration that the first UE expects to receive the sidelink CSI is reached, it may indicate that the second UE will not send the sidelink CSI to the first UE, so the first UE does not need to wait unnecessarily to save power consumption.
In addition, in the embodiments of the present application, the first UE triggers the second UE to send the sidestream CSI as an example, but in another case, the first UE may also trigger the second UE to send the resource information, and if the first UE triggers the second UE to send the resource information, the behaviors of the first UE and the second UE may also be applicable to the scheme provided in the embodiments of the present application, that is, the "sidestream CSI" described above may also be replaced with the "sidestream resource information". In addition, if the sideline CSI is replaced by the sideline resource information, the sl-CSI-ReportTimer may also be replaced by a timer related to the sideline resource information, and/or the sl-latencubaund-CSI-Report may also be replaced by the delay indication information related to the sideline resource information. For example, the sl-latenbound-CSI-Report may be replaced with sl-latenbound-Resource-Report for indicating a delay requirement from the associated triggering of the sidestream Resource information to the sending of the sidestream Resource information. The sl-CSI-ReportTimer may be replaced with a sidestream Resource Report timer (sl-Resource-ReportTimer), where the sl-Resource-ReportTimer is used for a UE (e.g., a second UE) that needs to send sidestream Resource information to follow a delay requirement indicated by a UE (e.g., a first UE) that triggers the sidestream Resource information, and a timing duration of the sl-Resource-ReportTimer may be determined according to a delay indicated by the sl-latencbound-Resource-Report. For example, the timing duration of sl-Resource-Report timer is equal to the delay indicated by sl-latencobound-Resource-Report, which is, for example, 50 slots (slots), or other durations may be used.
The resource information is briefly introduced as follows. In sidelink communications, inter-UE coordination includes a UE1 (e.g., a second UE) sending information indicating a set of resources to a UE2 (e.g., a first UE), which may be understood as the resource information. The set of resources may include one or more of the following (1), (2), (3).
(1) Prioritized (preferred) resources for the UE2 to make SL transmissions. For example, the UE1 determines the preferred resource for the UE2 for SL transmission according to the sending result.
(2) Non-prioritized (not preferred) resources for the UE2 to make SL transmissions. For example, UE1 determines the non-preferred resource for UE2 for SL transmission based on the sensing result and/or the potential resource conflict.
(3) Conflicting resources are detected. For example, UE1 detects that the SL transmission resources to be used by UE2 and UE3 overlap, and detects that the resources collide.
The information indicating the set of resources may be carried in the MAC CE or may be included in the SCI, for example, a secondary SCI.
In the embodiment of the present application, if the first UE receives the second sidelink control information from the second UE within the first time period, the first UE may not start the sl-DRX-inactivity timer of the first UE. Because the first UE does not start the sl-DRX-inactivity timer, the first UE is prevented from monitoring a channel during the operation of the sl-DRX-inactivity timer, and therefore the power consumption of the first UE can be reduced. Therefore, the scheme of the embodiment of the application can reduce the problem that the power consumption is excessively increased due to the fact that the UE receives the SL CSI reporting after the SL CSI reporting is triggered.
Fig. 8 is a schematic structural diagram of a communication device 800 according to an embodiment of the present disclosure. The communication apparatus 800 may be the first terminal device according to the embodiment shown in fig. 2, and is configured to implement the method performed by the first terminal device in the foregoing method embodiment. Alternatively, the communication apparatus 800 may also be the second terminal device described in the embodiment shown in fig. 2, and is configured to implement the method corresponding to the second terminal device in the foregoing method embodiment. The specific functions can be seen from the description of the above method embodiments.
The communication device 800 includes one or more processors 801. The processor 801 may also be referred to as a processing unit and may perform certain control functions. The processor 801 may be a general purpose processor, a special purpose processor, or the like. For example, it includes: a baseband processor, a central processing unit, an application processor, a modem processor, a graphics processor, an image signal processor, a digital signal processor, a video codec processor, a controller, a memory, and/or a neural network processor, among others. The baseband processor may be used to process communication protocols as well as communication data. The central processor may be used to control the communication device 800, execute software programs and/or process data. The different processors may be separate devices or may be integrated in one or more processors, e.g., on one or more application specific integrated circuits.
Optionally, one or more memories 802 are included in the communication device 800 to store instructions 804, and the instructions 804 can be executed on the processor to enable the communication device 800 to perform the methods described in the above method embodiments. Optionally, the memory 802 may further store data. The processor and the memory may be provided separately or may be integrated together.
Optionally, the communication apparatus 800 may include instructions 803 (which may also be sometimes referred to as code or program), and the instructions 803 may be executed on the processor, so that the communication apparatus 800 performs the method described in the above embodiments. Data may be stored in the processor 801.
Optionally, the communication device 800 may also include a transceiver 805 and an antenna 806. The transceiver 805 may be referred to as a transceiving unit, a transceiver, transceiving circuitry, a transceiver, an input/output interface, etc. for implementing transceiving functions of the communication device 800 through the antenna 806.
Optionally, the communication device 800 may further include one or more of the following components: the wireless communication module, the audio module, the external memory interface, the internal memory, a Universal Serial Bus (USB) interface, the power management module, the antenna, the speaker, the microphone, the input/output module, the sensor module, the motor, the camera, or the display screen. It is understood that in some embodiments, the communication device 800 may include more or fewer components, or some components integrated, or some components separated. These components may be hardware, software, or a combination of software and hardware implementations.
The processor 801 and the transceiver 805 described in the embodiments of the present application may be implemented on an Integrated Circuit (IC), an analog IC, a radio frequency integrated circuit (RFID), a mixed signal IC, an Application Specific Integrated Circuit (ASIC), a Printed Circuit Board (PCB), an electronic device, or the like. The communication apparatus implementing the present description may be a standalone device (e.g., a standalone integrated circuit, a mobile phone, etc.), or may be a part of a larger device (e.g., a module that can be embedded in other devices), and may refer to the foregoing description about the terminal device and the network device, which is not described herein again.
The embodiment of the present application provides a terminal device, which (for convenience of description, referred to as UE) may be used in the foregoing embodiments. The terminal device comprises corresponding means (means), units and/or circuits to implement the functionality of the first terminal device and/or the second terminal device as described in the embodiment shown in fig. 2. For example, the terminal device includes a transceiver module for supporting the terminal device to implement a transceiver function, and a processing module for supporting the terminal device to process a signal.
Fig. 9 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
The terminal device 900 may be adapted to the network architecture shown in fig. 1A or fig. 1B. For ease of illustration, fig. 9 shows only the main components of terminal device 900. As shown in fig. 9, the terminal apparatus 900 includes a processor, a memory, a control circuit, an antenna, and an input-output device. The processor is mainly used for processing a communication protocol and communication data, controlling the entire terminal device 900, executing a software program, and processing data of the software program. The memory is used primarily for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The antenna is mainly used for receiving and transmitting radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, microphones, keyboards, etc., are mainly used for receiving data input by users and outputting data to users.
Taking the terminal device 900 as a mobile phone as an example, when the terminal device 900 is turned on, the processor may read the software program in the storage unit, interpret and execute the instruction of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent and outputs baseband signals to the control circuit, and the control circuit performs radio frequency processing on the baseband signals and sends the radio frequency signals to the outside in the form of electromagnetic waves through the antenna. When data is transmitted to the terminal apparatus 900, the control circuit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor, and the processor converts the baseband signal into data and processes the data.
Those skilled in the art will appreciate that fig. 9 shows only one memory and processor for the sake of illustration. In some embodiments, terminal device 900 can include multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, and the like, which is not limited in this respect in the embodiment of the present invention.
As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process the communication protocol and the communication data, and the central processing unit is mainly used to control the whole terminal device 900, execute a software program, and process data of the software program. The processor in fig. 9 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Terminal device 900 may include multiple baseband processors to accommodate different network formats, terminal device 900 may include multiple central processors to enhance its processing capabilities, and various components of terminal device 900 may be connected by various buses. The baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit can also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.
In one example, the antenna and the control circuit with transceiving functions may be considered as the transceiving unit 910 of the terminal device 900, and the processor with processing functions may be considered as the processing unit 920 of the terminal device 900. As shown in fig. 9, the terminal apparatus 900 includes a transceiving unit 910 and a processing unit 920. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Optionally, a device for implementing a receiving function in the transceiving unit 910 may be regarded as a receiving unit, and a device for implementing a transmitting function in the transceiving unit 910 may be regarded as a transmitting unit, that is, the transceiving unit 910 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc.
Those of ordinary skill in the art will appreciate that the various illustrative elements and steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, the units described as separate components may or may not be physically separate, and components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. The computer readable storage medium can be any available medium that can be accessed by a computer. Taking this as an example but not limiting: a computer-readable medium may include a Random Access Memory (RAM), a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), a compact disc read-only memory (CD-ROM), a universal serial bus flash disk (universal serial bus flash disk), a removable hard disk, or other optical disk storage, magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, by way of illustration and 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 SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), or direct rambus RAM (DR RAM).
The above description is only for the specific implementation of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the embodiments of the present application, and all the changes or substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.
Claims (29)
1. A communication method applied to a first terminal device, wherein the first terminal device is configured with a sidestream DRX, the method comprising:
sending first sideline control information to second terminal equipment, wherein the first sideline control information is used for triggering the second terminal equipment to send sideline channel state information;
receiving second sidelink control information from the second terminal equipment in a first time period after the first sidelink control information is sent, wherein the second sidelink control information is used for scheduling MAC PDU, and the first time period is used for receiving the sidelink channel state information;
the sidestream DRX inactivity timer is not started.
2. The method of claim 1,
the first time period satisfies: the time period is the time period for monitoring the sidestream control information after the first terminal equipment sends the first sidestream control information, and the sidestream DRX activation time does not belong to the first terminal equipment; or the like, or, alternatively,
the first time period satisfies: the time period is the time period for monitoring the lateral control information after the first terminal equipment sends the first lateral control information, and neither a lateral DRX duration timer nor a lateral DRX inactivity timer of the first terminal equipment is operated; or the like, or, alternatively,
the first time period satisfies: the time period is the time period for monitoring the lateral control information after the first terminal equipment sends the first lateral control information, and the lateral DRX duration timer, the lateral DRX retransmission timer and the lateral DRX inactivity timer of the first terminal equipment do not run.
3. The method of claim 2,
the time period for monitoring the side row control information after the first terminal equipment sends the first side row control information is the time period for running a first timer, and the first timer is started after the first terminal equipment sends the first side row control information; or the like, or, alternatively,
the time period for monitoring the sidestream control information after the first terminal equipment sends the first sidestream control information is a time period for expecting to receive the sidestream channel state information after the first terminal equipment sends the first sidestream control information; or the like, or, alternatively,
and the time period for monitoring the sidestream control information after the first terminal equipment sends the first sidestream control information is the time period for running a sidestream channel state information report timer, and the sidestream channel state information report timer is used for indicating the maximum time length until the sidestream channel state information is sent.
4. The method according to any one of claims 1 to 3, further comprising:
sending first information to the second terminal device, where the first information is used to indicate that the first terminal device does not start the sidestream DRX inactivity timer in the first time period after sending the first sidestream control information; or the like, or a combination thereof,
receiving first information from the second terminal device, where the first information is used to instruct the first terminal device not to start the lateral DRX inactivity timer in the first time period after the first lateral control information is sent; or the like, or, alternatively,
receiving first information from a network device, wherein the first information is used for indicating that the first terminal device does not start the sidestream DRX inactivity timer in the first time period after the first sidestream control information is sent; or the like, or, alternatively,
the first sidelink control information is further used for indicating that the first terminal device does not start the sidelink DRX inactivity timer in the first time period after the first sidelink control information is sent.
5. The method according to any one of claims 1 to 4, further comprising:
sending second information to the second terminal device, where the second information is used to indicate a first manner applied to the first time period, and the first manner is a manner in which the second terminal device sends information to the first terminal device, where the first manner includes:
the second terminal equipment can send the side channel state information to the first terminal equipment and cannot send data to the first terminal equipment; or the like, or, alternatively,
the second terminal equipment can send the channel state information and/or data of the side row to the first terminal equipment; or the like, or, alternatively,
the second terminal device can send the side-row channel state information to the first terminal device, or send the side-row channel state information and data, and the side-row channel state information and the data are carried in the same MAC PDU.
6. The method according to any one of claims 1 to 5, further comprising:
receiving the MAC PDU from the second terminal device;
starting a second timer in case of a failure in decoding the MAC PDU;
and during the running of the second timer, monitoring the sidestream control information to wait for the retransmitted MAC PDU.
7. The method of claim 6, wherein starting a second timer in case of failure to decode the MAC PDU comprises:
starting the second timer if decoding the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information and no data.
8. The method of claim 6 or 7, wherein starting the second timer comprises:
starting the second timer in a first time domain unit after the end of the side row data channel corresponding to the second side row control information; or the like, or, alternatively,
and starting the second timer in a first time domain unit after first feedback information is sent, wherein the first feedback information is the feedback information which is sent to the second terminal equipment and corresponds to the MAC PDU.
9. The method according to any one of claims 1 to 5, further comprising:
receiving the MAC PDU from the second terminal device;
starting a third timer under the condition that the decoding of the MAC PDU fails, wherein the timing duration of the third timer is used for indicating the preparation time of the second terminal equipment before the MAC PDU is retransmitted;
starting a second timer when the third timer is overtime;
and during the running of the second timer, monitoring side-line control information to wait for the retransmitted MAC PDU.
10. The method of claim 9, wherein starting a third timer in case of failure to decode the MAC PDU comprises:
starting the third timer if decoding of the MAC PDU fails and the second sidelink control information indicates that the MAC PDU includes sidelink channel state information and no data.
11. The method of claim 9 or 10, wherein starting the third timer comprises:
starting the third timer in a first time domain unit after the end of the side row data channel corresponding to the second side row control information; or the like, or, alternatively,
and starting the third timer in a first time domain unit after first feedback information is sent, wherein the first feedback information is the feedback information which is sent to the second terminal equipment and corresponds to the MAC PDU.
12. The method according to any one of claims 6 to 11, further comprising:
stopping the second timer when the lateral channel state information report timer of the second terminal equipment is overtime; or the like, or, alternatively,
stopping the second timer when a second time length after the first sidelink control information is sent is reached, wherein the second time length is used for waiting for receiving sidelink channel state information, and the timing time length of a sidelink channel state information report timer of the second terminal equipment is determined according to the second time length; or the like, or, alternatively,
and when the time length for expecting to receive the lateral channel state information after the first lateral control information is sent reaches, stopping the second timer.
13. The method according to any one of claims 1 to 5, further comprising:
receiving the MAC PDU from the second terminal device;
and under the condition that the decoding of the MAC PDU fails and the second downlink control information indicates that the MAC PDU does not comprise the lateral channel state information, not starting a second timer, wherein the running period of the second timer is used for monitoring the lateral control information.
14. The method of any one of claims 1 to 13, further comprising:
and after the first sideline control information is sent, starting a first timer, wherein the timing duration of the first timer is the first time period.
15. The method of any one of claims 1 to 13, further comprising:
after the first side-row control information is sent, starting a fourth timer, wherein the timing duration of the fourth timer is used for indicating the preparation time of the second terminal equipment before the side-row channel state information is sent;
and starting a first timer when the fourth timer is over time, wherein the timing duration of the first timer is the first time period.
16. The method of claim 15, further comprising:
and receiving third information from the second terminal device, wherein the third information is used for indicating the timing duration of the fourth timer.
17. The method according to any one of claims 14 to 16,
the running time of the first timer is the sidestream DRX activation time of the first terminal equipment; or the like, or, alternatively,
a part of the running time of the first timer, which is not overlapped with the side-row DRX activation time of the first terminal equipment, does not belong to the side-row DRX activation time of the first terminal equipment; or the like, or, alternatively,
in the running time of the first timer, the non-running time of the lateral DRX duration timer and/or the lateral DRX inactivity timer of the first terminal equipment does not belong to the lateral DRX active time of the first terminal equipment; or the like, or, alternatively,
in the operation time of the first timer, the time when one or more of the lateral DRX duration timer, the lateral DRX inactivity timer, or the lateral DRX retransmission timer of the first terminal device does not operate does not belong to the lateral DRX active time of the first terminal device.
18. The method of any one of claims 14 to 17, further comprising:
receiving fourth information from a network device, wherein the fourth information is used for indicating the timing duration of the first timer; or the like, or, alternatively,
and determining the timing duration of the first timer according to the CBR.
19. The method of claim 18, wherein determining the timing duration of the first timer based on CBR comprises:
under the condition that the channel occupancy rate indicated by the CBR is greater than or equal to a first threshold value, determining the timing duration of the first timer to be the duration greater than a second threshold value; and/or the presence of a gas in the atmosphere,
and under the condition that the channel occupancy rate indicated by the CBR is smaller than the first threshold, determining the timing duration of the first timer to be the duration smaller than a third threshold.
20. The method of any one of claims 14 to 19, further comprising:
receiving second feedback information from the second terminal equipment;
and if the second feedback information is used for indicating that the first side row data channel fails to be received, stopping the first timer, wherein the first side row data channel is the side row data channel scheduled by the first side row control information.
21. A communication method is applied to a second terminal device, and is characterized by comprising the following steps:
receiving first side row control information from first terminal equipment, wherein the first side row control information is used for triggering the second terminal equipment to send side row channel state information;
sending second sideline control information to the first terminal equipment, wherein the second sideline control information is used for scheduling MAC PDU;
the sidelink DRX inactivity timer is not started.
22. The method of claim 21, further comprising:
transmitting the MAC PDU to the first terminal device in a first manner applied to a first time period, where the first time period is used for the first terminal device to wait for the sidelink channel status information, and the first manner includes:
the first terminal equipment can be sent side channel state information, and data cannot be sent to the first terminal equipment; or the like, or, alternatively,
side channel state information and/or data can be sent to the first terminal device; or the like, or, alternatively,
side-row channel state information can be sent to the first terminal device, or side-row channel state information and data can be sent, and the side-row channel state information and the data are carried in one MAC PDU.
23. The method according to claim 21 or 22, further comprising:
receiving first information from the first terminal equipment, wherein the first information is used for indicating that the first terminal equipment does not start a side-row DRX inactivity timer in a first time period after the first side-row control information is sent; or the like, or, alternatively,
receiving first information from a network device, wherein the first information is used for indicating that the first terminal device does not start a side-row DRX (discontinuous reception) inactivity timer in the first time period after the first side-row control information is sent; or the like, or, alternatively,
sending first information to the first terminal equipment, wherein the first information is used for indicating that the first terminal equipment does not start a side-row DRX (discontinuous reception) inactivity timer in a first time period after the first side-row control information is sent; or the like, or, alternatively,
the first sidelink control information is further used for indicating that the first terminal device does not start a sidelink DRX inactivity timer within a first time period after the first sidelink control information is sent.
24. The method according to claim 22 or 23, further comprising:
selecting a target device for receiving the MAC PDU according to a first rule, wherein the first rule comprises:
the first time domain resource is located in the first time period after the target device triggers the second terminal device to send the sidestream channel state information, or the first time domain information is located in the sidestream DRX activation time of the target device; the first time domain resource is a time domain resource occupied by the second sideline control information, or a time domain resource occupied by a sideline control channel corresponding to the second sideline control information, or a time domain resource occupied by a sideline authorization information corresponding to the second sideline control information.
25. The method of any one of claims 21 to 24, further comprising:
and receiving second information from the first terminal equipment, wherein the second information is used for indicating the first mode.
26. The method of any one of claims 21 to 25, further comprising:
and sending third information to the first terminal equipment, wherein the third information is used for indicating the timing duration of a fourth timer, and the timing duration of the fourth timer is used for indicating the preparation time of the second terminal equipment before the side channel state information is sent.
27. A terminal device, comprising:
one or more processors;
one or more memories;
and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, the one or more computer programs comprising instructions which, when executed by one or more processors of the terminal device, cause the terminal device to perform the method of any of claims 1-20, or cause the terminal device to perform the method of any of claims 21-26.
28. A computer-readable storage medium, for storing a computer program which, when run on a computer, causes the computer to perform the method of any of claims 1-20 or causes the computer to perform the method of any of claims 21-26.
29. A chip comprising one or more processors and a communications interface, the one or more processors being configured to read instructions to perform the method of any one of claims 1 to 20 or to perform the method of any one of claims 21 to 26.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2021/136581 WO2022179242A1 (en) | 2021-02-24 | 2021-12-08 | Communication method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2021102093104 | 2021-02-24 | ||
| CN202110209310 | 2021-02-24 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114980284A true CN114980284A (en) | 2022-08-30 |
Family
ID=82973084
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110307529.8A Pending CN114980284A (en) | 2021-02-24 | 2021-03-23 | Communication method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114980284A (en) |
| WO (1) | WO2022179242A1 (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200120596A1 (en) * | 2017-06-16 | 2020-04-16 | Huawei Technologies Co., Ltd. | Drx configuration method, terminal device, network device, and communications system |
| CN112333836A (en) * | 2019-08-05 | 2021-02-05 | 夏普株式会社 | User equipment control method and user equipment |
-
2021
- 2021-03-23 CN CN202110307529.8A patent/CN114980284A/en active Pending
- 2021-12-08 WO PCT/CN2021/136581 patent/WO2022179242A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200120596A1 (en) * | 2017-06-16 | 2020-04-16 | Huawei Technologies Co., Ltd. | Drx configuration method, terminal device, network device, and communications system |
| CN112333836A (en) * | 2019-08-05 | 2021-02-05 | 夏普株式会社 | User equipment control method and user equipment |
Non-Patent Citations (1)
| Title |
|---|
| INTEL CORPORATION: "On general sidelink DRX design", 3GPP TSG-RAN WG2 MEETING#113-E，R2-2100315, 5 February 2022 (2022-02-05), pages 1 - 3 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022179242A1 (en) | 2022-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110351898B (en) | Communication method, device, communication equipment and communication system for discontinuous reception | |
| US9451547B2 (en) | Coordinated signaling of scheduling information for uplink and downlink communications | |
| WO2019137378A1 (en) | Communication method, communication device, and network device | |
| US10594447B2 (en) | Data transmission method, terminal, and ran device | |
| CN110463102B (en) | Method, apparatus, and medium for HARQ-ACK feedback | |
| KR20190067242A (en) | Method and apparatus for transmission scheduling in a wireless communication system | |
| CN112399644A (en) | Discontinuous receiving method, related device and system | |
| WO2020259363A1 (en) | Electronic device and method for wireless communication, and computer-readable storage medium | |
| CN114286310A (en) | Communication method, device and system | |
| EP4122264A1 (en) | Nr sidelink discontinuous reception resource allocation | |
| CN116058064A (en) | Consideration of active reception status in resource selection for D2D communication | |
| WO2022142337A1 (en) | Wireless communication method and terminal device | |
| EP4233332A1 (en) | Method and apparatus for relay communication | |
| WO2022179242A1 (en) | Communication method and device | |
| CN115136718A (en) | Communication apparatus and method | |
| CN113708898A (en) | Communication method and device | |
| US20240121805A1 (en) | Communication method and device | |
| WO2022206925A1 (en) | Sidelink transmission method and apparatus | |
| WO2021171537A1 (en) | Base station device, terminal device, and wireless communication system | |
| WO2023216986A1 (en) | Buffer status report (bsr) indication method, and apparatus | |
| EP4316166A1 (en) | Sidelink discontinuous reception procedures | |
| CN115580921A (en) | Communication method and device | |
| WO2023118310A1 (en) | Paging early indication technique for relaying | |
| CN115843103A (en) | Communication method and device | |
| CN117044383A (en) | Method and device for controlling timer and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |