Sidelink communication method and apparatus

Abstract

An embodiment of this application provides a sidelink communication method and apparatus. When a first terminal device (transmitter) has first data or first signaling to be sent, the first terminal device first determines whether the first data or first signaling supports multicast or broadcast SL DRX. When the first data or first signaling supports multicast or broadcast SL DRX, the first terminal device acquires the SL resources corresponding to the multicast or broadcast SL DRX, and uses the SL resources corresponding to the multicast or broadcast SL DRX to send the first data or first signaling. Since the SL resources used by the transmitter to send the first data or first signaling are the SL resources corresponding to the multicast or broadcast SL DRX, and the receiving end terminal device also receives on the SL resources corresponding to the multicast or broadcast SL DRX, it can be ensured that the first data or first signaling that supports multicast or broadcast SL DRX can be successfully received by the receiving end terminal device, improving the SL communication quality.

Description

Technical Field

[0001] This application relates to communication technologies, and in particular, to a sidelink communication method and apparatus. Background Art

[0002] User equipment (UE) can communicate with other UEs through a network or directly. The direct communication between UEs is also called sidelink (SL) communication. In SL communication, data is transmitted between two UEs through the PC5 air interface. A typical application of SL communication is the vehicle to everything (V2X) scenario. In the V2X scenario, a vehicle is a UE.

[0003] During the SL communication process, to save the power consumption of the UE, the transmitting UE or the receiving UE can adopt the discontinuous reception (DRX) mechanism. The DRX mechanism means that when there is no data transmission or reception, the UE turns off the transmitter or receiver for a period of time to reduce power consumption. The DRX cycle consists of an active time and a dormant period (or an inactive period). The UE transmits or receives data during the active time and does not transmit or receive data during the dormant period. In the prior art, the UE may support SL DRX based on unicast, and / or support SL DRX for broadcast and multicast.

[0004] However, when the transmitting UE sends data or signaling supporting multicast or broadcast SL DRX, the SL transmission resources used by the transmitting UE may not correspond to the SL reception resources used by the receiving UEs in the broadcast and multicast SL DRX states, resulting in the receiving UEs being unable to receive the data or signaling supporting multicast or broadcast SL DRX, which affects the SL communication quality. Summary of the Invention

[0005] Embodiments of this application provide a sidelink communication method and apparatus, which can avoid the loss of services or signaling supporting multicast or broadcast SL DRX and improve the SL communication quality.

[0006] The first aspect of this application provides a sidelink communication method, which is applied to a first terminal device. The method includes: determining that first data or first signaling supports a first DRX, where the first DRX is a multicast or broadcast SL DRX; obtaining first SL resources, where the first SL resources are the SL resources corresponding to the first DRX; and sending the first data or the first signaling on the first SL resources. When the terminal device has data or signaling corresponding to a multicast or broadcast SL DRX to send, by obtaining the resources corresponding to the multicast or broadcast SL DRX and using the resources corresponding to the multicast or broadcast SL DRX for sending, since both the sending resources used by the sending end and the receiving resources used by the receiving end are the resources corresponding to the multicast or broadcast SL DRX, it can ensure that the data or signaling corresponding to the multicast or broadcast SL DRX is successfully received by the receiving end, improving the SL communication quality.

[0007] In an exemplary manner, the determining that first data or first signaling supports a first DRX includes: the access stratum receives first indication information from the upper layer, and the first indication information is used to indicate that the first data or the first signaling supports a multicast or broadcast SL DRX.

[0008] In an exemplary manner, the first indication information includes that the service or quality of service (QoS) flow associated with the first data supports a multicast or broadcast SL DRX.

[0009] In an exemplary manner, the obtaining first SL resources includes: sending a first request message to a network device, where the first request message is used to request the first SL resources, and receiving information about the first SL resources sent by the network device.

[0010] Optionally, the first request message includes second indication information, and the second indication information is used to indicate that the SL resources required for the data or signaling corresponding to the destination address or QoS flow are the SL resources corresponding to a multicast or broadcast DRX.

[0011] Alternatively, before the first terminal device sends the first request message to the network device, the first terminal device sends second indication information to the network device, and the second indication information is used to indicate that the SL resources required for the data or signaling corresponding to the destination address or QoS flow are the SL resources corresponding to a multicast or broadcast DRX.

[0012] Optionally, the first request message is any one of the following messages: an SL scheduling request (SR), an SL buffer status report (BSR), or a user assistance information (UAI) message.

[0013] When the first request message is any one of the following messages: SL scheduling request SR, SL buffer status report BSR, or user assistance information UAI message, optionally, the second indication information is carried in the sidelink user information SUI message.

[0014] In an exemplary manner, the first request message is a dedicated SL SR, and the first SL resource is allocated by the network device for the first terminal device according to the dedicated SL SR.

[0015] In another exemplary manner, when the first request message is the dedicated SL SR, before the first terminal device sends the dedicated SL SR to the network device, the first terminal device sends an SUI message to the network device, the SUI message includes the second indication information, and the first terminal device receives the dedicated SL SR configured by the network device.

[0016] In yet another exemplary manner, when the first request message is an SL SR, the second indication information is included in the SL SR. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0017] In an exemplary manner, when the first request message is an SL BSR, the first terminal device sends the SL BSR to the network device using a dedicated LCG or a dedicated destination address index. The first SL resource is allocated by the network device for the first terminal device according to the dedicated LCG or the dedicated destination address index or is predefined by the protocol.

[0018] In another exemplary manner, when the first request message is an SL BSR, before the first terminal device sends the SL BSR to the network device using a dedicated LCG or a dedicated destination address index, the first terminal device sends an SUI message to the network device, the SUI message includes the second indication information, and the first terminal device receives the configuration information of the dedicated LCG or the dedicated destination address index sent by the network device, where the dedicated LCG or the dedicated destination address index is configured by the network device according to the second indication information.

[0019] In yet another exemplary manner, when the first request message is an SL BSR, the second indication information is included in the SL BSR. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0020] In another exemplary manner, when the first request message is an SL BSR, before the first terminal device sends the SL BSR to the network device, it sends a SUI to the network device, and the SUI includes second indication information.

[0021] In another exemplary manner, the first request message is an SL BSR in a specific format, and the SL BSR in the specific format is dedicated to requesting SL resources corresponding to multicast or broadcast DRX. The first SL resource is allocated by the network device for the first terminal device according to the format of the SL BSR.

[0022] In an exemplary manner, when the first request message is a UAI message, the UAI message includes the second indication information. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0023] In another exemplary manner, when the first request message is a UAI message, before the first terminal device sends the UAI message to the network device, it sends a SUI message to the network device, and the SUI message includes second indication information. The first SL resource is a semi-static scheduling SPS resource, and the first SL resource is allocated by the network device for the first terminal device according to the second indication information and the UAI message.

[0024] Optionally, the first signaling includes one or more of the following signaling: a message in the SL unicast connection establishment process, a message in the discovery relay UE process, a message related to the SL capability of the UE, or the first PC5 RRC reconfiguration message.

[0025] In another exemplary manner, the first terminal device obtains a first sidelink SL resource, including: the first terminal device obtains the first SL resource by measuring idle SL resources.

[0026] In an exemplary manner, the first terminal device sends the first data or the first signaling on the first SL resource, including: the first terminal device only selects or preferentially selects the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted as the transmission destination address.

[0027] Only selecting or preferentially selecting the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted for transmission can ensure that the first data or the first signaling is preferentially transmitted, and avoid the first data or the first signaling from being delayed or discarded due to LCP.

[0028] In another exemplary manner, the first terminal device transmits the first data or the first signaling on the first SL resource, including: the first terminal device only selects or preferentially selects the logical channel corresponding to the first data or the first signaling from the logical channels to be transmitted as the logical channel for transmission.

[0029] Only selecting or preferentially selecting the logical channel corresponding to the first data or the first signaling from the logical channels to be transmitted for transmission can ensure that the first data or the first signaling is preferentially transmitted, avoiding the delay or discard of the first data or the first signaling due to LCP.

[0030] In a second aspect of the present application, a sidelink communication method is provided, which is applied to a network device. The method includes: receiving a first request message sent by a first terminal device, where the first request message is used to request a first sidelink SL resource, the first SL resource is an SL resource corresponding to a first discontinuous reception DRX, and the first DRX is a multicast or broadcast DRX. According to the first request message, the first SL resource is allocated to the first terminal device. By sending the first request message, the sending end requests the resource corresponding to the multicast or broadcast SL DRX from the network device, and the network device allocates the resource corresponding to the multicast or broadcast SL DRX to the sending end according to the first request message. Since both the sending resource used by the sending end and the receiving resource used by the receiving end are the SL resources corresponding to the multicast or broadcast, it can ensure that the data or signaling supporting the multicast or broadcast SL DRX can be successfully received by the receiving end, improving the SL communication quality.

[0031] In an exemplary manner, the first request message includes second indication information, and the second indication information is used to indicate that the SL resource required for the data or signaling corresponding to the destination address or QoS flow is the SL resource corresponding to the multicast or broadcast DRX.

[0032] In an exemplary manner, before the network device receives the first request message sent by the first terminal device, it further includes: the network device receives the second indication information sent by the first terminal device, and the second indication information is used to indicate that the SL resource required for the data or signaling corresponding to the destination address or QoS flow is the SL resource corresponding to the multicast or broadcast DRX.

[0033] Optionally, the first request message is any one of the following messages: SL scheduling request SR, SL buffer status report BSR, or user assistance information UAI message.

[0034] Optionally, the first request message is any one of the following messages: SL scheduling request SR, SL buffer status report BSR, or user assistance information UAI message, and the second indication information is carried in the sidelink user information SUI message.

[0035] In an exemplary manner, the first request message is a dedicated SL SR, and the dedicated SL SR is used to request SL resources corresponding to multicast or broadcast SL DRX. The network device determines that the resources requested by the SL SR are resources corresponding to multicast or broadcast SL DRX according to the dedicated SL SR, and allocates the first SL resource to the first terminal device.

[0036] In another exemplary manner, before the network device receives the dedicated SL SR, the network device receives the SUI message sent by the first terminal device, and the second indication information is included in the SUI message. The network device configures the dedicated SL SR for the first terminal device according to the second indication information.

[0037] In yet another exemplary manner, when the first request message is an SL SR, the second indication information is included in the SL SR, and the network device allocates the first SL resource to the first terminal device according to the second indication information.

[0038] In an exemplary manner, when the first request message is an SL BSR, the SL BSR is sent by the first terminal device to the network device using a dedicated LCG or a dedicated destination address index. The network device determines that the resources requested by the SL BSR are resources corresponding to multicast or broadcast SL DRX according to the dedicated LCG or the dedicated destination address index, and allocates the first SL resource to the first terminal device.

[0039] In another exemplary manner, when the first request message is an SL BSR, before the network device receives the SL BSR, the network device receives the SUI message sent by the first terminal device, and the second indication information is included in the SUI message. The first terminal device configures the dedicated LCG or the dedicated destination address index for the SL BSR according to the second indication information.

[0040] In yet another exemplary manner, when the first request message is an SL BSR, the second indication information is included in the SL BSR. The network device allocates the first SL resource to the first terminal device according to the second indication information.

[0041] In another exemplary manner, when the first request message is an SL BSR, before the network device receives the SL BSR, the network device receives a SUI message sent by the first terminal device. The SUI includes second indication information, and the network device allocates the first SL resource for the first terminal device according to the second indication information and the SL BSR.

[0042] In another exemplary manner, the first request message is an SL BSR in a specific format, and the SL BSR in the specific format is dedicated to requesting SL resources corresponding to multicast or broadcast DRX. The network device allocates the first SL resource for the first terminal device according to the format of the SL BSR.

[0043] In an exemplary manner, when the first request message is a UAI message, the UAI message includes the second indication information. The network device allocates the first SL resource for the first terminal device according to the second indication information.

[0044] In another exemplary manner, when the first request message is a UAI message, before the network device receives the UAI message, it receives a SUI message sent by the first network device. The SUI message includes second indication information. The first SL resource is the first SL resource allocated by the network device for the first terminal device according to the second indication information and the UAI message, and the first SL resource is a semi-static scheduling SPS resource.

[0045] Optionally, the first signaling includes one or more of the following signaling: a message in the SL unicast connection establishment process, a message in the discovery relay UE process, a message related to the SL capability of the UE, or the first PC5 radio resource control RRC reconfiguration message.

[0046] A third aspect of this application provides a sidelink communication method, including: The access stratum receives first indication information from an upper layer. The first indication information is used to indicate that first data or first signaling supports first discontinuous reception DRX, and the first DRX is multicast or broadcast SL DRX. When it is determined according to the first indication information that the data or signaling to be received currently supports the first DRX, the first DRX is activated.

[0047] A fourth aspect of this application provides a sidelink communication method applied to a second terminal device, including: deactivating a first discontinuous reception (DRX) at a first moment, where the first DRX is a multicast or broadcast sidelink (SL) DRX, and the first moment is the reception moment of an SL unicast connection establishment message or the reception moment of a discovery request message; activating the first DRX at a second moment, where the second moment is the reception moment of an SL unicast connection establishment acceptance message or the reception moment of the first PC5 radio resource control (RRC) reconfiguration message or the moment when the unicast connection DRX configuration is completed or the timeout moment of a first timer.

[0048] In this method, the receiving end terminal device turns off the first DRX between the first moment and the second moment. Turning off the first DRX means that the receiving end terminal device receives data during all time periods corresponding to normal SL resources, not limited to receiving data only on the SL resources corresponding to the multicast or broadcast SL DRX, so as to ensure that the signaling or data supporting the multicast or broadcast SL DRX can be successfully received by the receiving end terminal device, improving the SL communication quality.

[0049] In an exemplary manner, the terminal device starts the first timer at the first moment.

[0050] In an exemplary manner, the terminal device deactivating the first DRX at the first moment includes:

[0051] The terminal device deactivates the first DRX after delaying a preset time at the first moment.

[0052] A fifth aspect of this application provides a sidelink communication method applied to a second terminal device, including: receiving a scheduling control information (SCI) sent by a first terminal device; when the second terminal device is in a multicast or broadcast SL DRX state and the resources corresponding to the transport block (TB) indicated by the SCI do not belong to or partially belong to the SL resources corresponding to the multicast or broadcast SL DRX, not receiving the TB indicated by the SCI, or receiving the TB indicated by the SCI but not starting the hybrid automatic repeat request (HARQ) round trip time (RTT) timer or the inactivity timer corresponding to the SCI.

[0053] In this embodiment, after the second terminal device receives the SCI, not starting the HARQ transmission time (TTT) timer or the INACTIVITY timer corresponding to the TB indicated by the SCI can avoid receiving the corresponding retransmitted data subsequently, saving the energy consumption of the terminal device.

[0054] A sixth aspect of this application provides a first terminal device, including:

[0055] A determination module, configured to determine that first data or first signaling supports first discontinuous reception (DRX), where the first DRX is multicast or broadcast sidelink (SL) DRX;

[0056] An acquisition module, configured to acquire first SL resources, where the first SL resources are SL resources corresponding to the first DRX;

[0057] A sending module, configured to send the first data or the first signaling on the first SL resources.

[0058] In an exemplary manner, the determination module is specifically configured to: receive first indication information from an upper layer of the first terminal device, where the first indication information is used to indicate that the first data or the first signaling supports multicast or broadcast SL DRX.

[0059] In an exemplary manner, the first indication information includes that a service or quality of service (QoS) flow associated with the first data supports multicast or broadcast SL DRX.

[0060] In an exemplary manner, the acquisition module is specifically configured to: send a first request message to a network device, where the first request message is used to request the first SL resources, and receive information about the first SL resources sent by the network device.

[0061] Optionally, the first request message includes second indication information, where the second indication information is used to indicate that SL resources required for a destination address or data or signaling corresponding to a QoS flow are SL resources corresponding to multicast or broadcast DRX.

[0062] Alternatively, the acquisition module is further configured to: before sending the first request message to the network device, send second indication information to the network device, where the second indication information is used to indicate that SL resources required for a destination address or data or signaling corresponding to a QoS flow are SL resources corresponding to multicast or broadcast DRX.

[0063] Optionally, the first request message is any one of the following messages: an SL scheduling request (SR), an SL buffer status report (BSR), or a user assistance information (UAI) message.

[0064] When the first request message is any one of the following messages: an SL scheduling request (SR), an SL buffer status report (BSR), or a user assistance information (UAI) message, optionally, the second indication information is carried in a sidelink user information (SUI) message.

[0065] In an exemplary manner, the first request message is a dedicated SL SR, and the first SL resources are allocated by the network device for the first terminal device according to the dedicated SL BSR.

[0066] In another exemplary manner, when the first request message is the dedicated SL SR, before the obtaining module sends the dedicated SL SR to the network device, it sends an SUI message to the network device. The SUI message includes the second indication information, and the obtaining module receives the dedicated SL SR configured by the network device.

[0067] In yet another exemplary manner, when the first request message is an SL SR, the SL SR includes the second indication information. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0068] In an exemplary manner, when the first request message is an SL BSR, the obtaining module is specifically configured to: send the SL BSR to the network device using a dedicated LCG or a dedicated destination address index. The first SL resource is allocated by the network device for the first terminal device according to the dedicated LCG or the dedicated destination address index or is predefined by the protocol.

[0069] In another exemplary manner, when the first request message is an SL BSR, before the obtaining module sends the SL BSR to the network device using the dedicated LCG or the dedicated destination address, it sends an SUI message to the network device. The SUI message includes the second indication information, and the obtaining module receives the configuration information of the dedicated LCG or the dedicated destination address index sent by the network device. The dedicated LCG or the dedicated destination address index is configured by the network device according to the second indication information.

[0070] In yet another exemplary manner, when the first request message is an SL BSR, the SL BSR includes the second indication information. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0071] In yet another exemplary manner, when the first request message is an SL BSR, before the obtaining module sends the SL BSR to the network device, it sends an SUI to the network device. The SUI includes the second indication information.

[0072] In yet another exemplary manner, when the first request message is an SL BSR in a specific format, the SL BSR in the specific format is dedicated to requesting the SL resources corresponding to multicast or broadcast DRX. The first SL resource is allocated by the network device for the first terminal device according to the format of the SL BSR.

[0073] In an exemplary manner, when the first request message is a UAI message, the second indication information is included in the UAI message. The first SL resource is allocated by the network device for the first terminal device according to the second indication information.

[0074] In another exemplary manner, when the first request message is a UAI message, before the obtaining module sends the UAI message to the network device, it sends a SUI message to the network device, and the second indication information is included in the SUI message. The first SL resource is a semi-static scheduling SPS resource, and the first SL resource is allocated by the network device for the first terminal device according to the second indication information and the UAI message.

[0075] Optionally, the first signaling includes one or more of the following signaling: messages in the SL unicast connection establishment process, messages in the discovery relay UE process, UE's SL capability-related messages, or the first PC5 radio resource control (RRC) reconfiguration message.

[0076] In another exemplary manner, the obtaining module is specifically configured to: obtain the first SL resource by measuring the idle SL resources.

[0077] In an exemplary manner, the sending module is specifically configured to: only select or preferentially select the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted as the transmission destination address.

[0078] In another exemplary manner, the sending module is specifically configured to: only select or preferentially select the logical channel corresponding to the first data or the first signaling from the logical channels to be transmitted as the transmission logical channel.

[0079] The first terminal device provided in the sixth aspect and each implementation manner of the present application can be used to execute the methods provided in the first aspect and each implementation manner of the present application, and the technical effects are similar and will not be elaborated here.

[0080] The seventh aspect of the present application provides a network device, including:

[0081] A receiving module, configured to receive a first request message sent by a first terminal device, where the first request message is used to request a first sidelink (SL) resource, the first SL resource is an SL resource corresponding to a first discontinuous reception (DRX), and the first DRX is a multicast or broadcast DRX;

[0082] An allocation module, configured to allocate the first SL resource for the first terminal device according to the first request message.

[0083] In an exemplary manner, the first request message includes second indication information, which is used to indicate that the SL resources required for the destination address or the data or signaling corresponding to the QoS flow are the SL resources corresponding to multicast or broadcast DRX.

[0084] In another exemplary manner, the receiving module is further configured to: before receiving the first request message, receive second indication information sent by the first terminal device, where the second indication information is used to indicate that the SL resources required for the destination address or the data or signaling corresponding to the QoS flow are the SL resources corresponding to multicast or broadcast DRX.

[0085] Optionally, the first request message is any one of the following messages: SL scheduling request SR, SL buffer status report BSR, or user assistance information UAI message.

[0086] When the first request message is any one of the following messages: SL scheduling request SR, SL buffer status report BSR, or user assistance information UAI message, optionally, the second indication information is carried in the sidelink user information SUI message.

[0087] In an exemplary manner, the first request message is a dedicated SL SR, and the dedicated SL SR is used to request the SL resources corresponding to multicast or broadcast SL DRX. Specifically, the allocation module is configured to: determine, according to the dedicated SL SR, that the resources requested by the SLSR are the resources corresponding to multicast or broadcast SL DRX, and allocate the first SL resource to the first terminal device.

[0088] In another exemplary manner, before receiving the dedicated SL SR, the receiving module further receives an SUI message sent by the first terminal device, where the SUI message includes the second indication information, and the network device further includes a configuration module, which is configured to configure the dedicated SL SR for the first terminal device according to the second indication information.

[0089] In yet another exemplary manner, when the first request message is an SL SR, the SL SR includes the second indication information, and specifically, the allocation module is configured to: allocate the first SL resource to the first terminal device according to the second indication information.

[0090] In an exemplary manner, when the first request message is an SL BSR, the SL BSR is sent by the first terminal device to the network device using a dedicated LCG or a dedicated destination address index. Specifically, the allocation module is configured to: determine, according to the dedicated LCG or the dedicated destination address index, that the resources requested by the SL BSR are resources corresponding to multicast or broadcast SLDRX, and allocate the first SL resources to the first terminal device.

[0091] In another exemplary manner, when the first request message is an SL BSR, before receiving the SL BSR, the receiving module further receives a SUI message sent by the first terminal device, where the SUI message includes the second indication information. Specifically, the allocation module is configured to: configure the dedicated LCG or the dedicated destination address index for the SL BSR according to the second indication information and the SL BSR.

[0092] In yet another exemplary manner, when the first request message is an SL BSR, the second indication information is included in the SL BSR. The network device allocates the first SL resources to the first terminal device according to the second indication information.

[0093] In yet another exemplary manner, when the first request message is an SL BSR, before receiving the SL BSR, the network device receives a SUI message sent by the first terminal device, where the SUI includes the second indication information. The network device further includes a configuration module configured to allocate the first SL resources to the first terminal device according to the second indication information.

[0094] In yet another exemplary manner, the first request message is an SL BSR in a specific format, and the SL BSR in the specific format is dedicated to requesting SL resources corresponding to multicast or broadcast DRX. Specifically, the allocation module is configured to: allocate the first SL resources to the first terminal device according to the format of the SL BSR.

[0095] In an exemplary manner, when the first request message is a UAI message, the second indication information is included in the UAI message. Specifically, the allocation module is configured to: allocate the first SL resources to the first terminal device according to the second indication information.

[0096] In another exemplary manner, when the first request message is a UAI message, before the receiving module receives the UAI message, it receives an SUI message sent by the first network device, and the SUI message includes second indication information. The allocation module is specifically configured to: allocate the first SL resource for the first terminal device according to the second indication information and the UAI message, and the first SL resource is a semi-static scheduling SPS resource.

[0097] Optionally, the first signaling includes one or more of the following signaling: a message in the SL unicast connection establishment process, a message in the process of discovering a relay UE, a message related to the SL capability of the UE, or the first PC5 radio resource control (RRC) reconfiguration message.

[0098] The network device provided in the seventh aspect and each implementation manner of the present application can be used to execute the method provided in the second aspect and each implementation manner of the present application, and the technical effects are similar, which will not be elaborated here.

[0099] The eighth aspect of the present application provides a second terminal device, including:

[0100] A receiving module, which receives first indication information from the upper layer of the second terminal device, and the first indication information is used to indicate that first data or first signaling supports first discontinuous reception (DRX), and the first DRX is multicast or broadcast SL DRX;

[0101] A determining module, configured to determine, according to the first indication information, that the data or signaling to be received currently supports the first DRX;

[0102] An activation module, configured to activate the first DRX.

[0103] The second terminal device provided in the eighth aspect of the present application can be used to execute the method provided in the third aspect of the present application, and the technical effects are similar, which will not be elaborated here.

[0104] The ninth aspect of the present application provides a terminal device, including:

[0105] A deactivation module, configured to deactivate first discontinuous reception (DRX) at a first moment, the first DRX is multicast or broadcast side link (SL) DRX, and the first moment is the reception moment of the SL unicast connection establishment message or the reception moment of the discovery request message;

[0106] An activation module, configured to activate the first DRX at a second moment, and the second moment is the reception moment of the SL unicast connection acceptance message or the reception moment of the first PC5 radio resource control (RRC) reconfiguration message or the moment when the unicast connection DRX configuration is completed or the timeout moment of the first timer.

[0107] In an exemplary manner, the terminal device starts the first timer at the first moment.

[0108] In an exemplary manner, the deactivation module is specifically configured to: deactivate the first DRX after delaying a preset time at the first moment.

[0109] The terminal device provided in the eighth aspect and each implementation manner of the present application can be used to execute the method provided in the fourth aspect and each implementation manner of the present application, and the technical effects are similar, which will not be elaborated here.

[0110] The tenth aspect of the present application provides a second terminal device, including:

[0111] a receiving module, configured to receive an SCI sent by a first terminal device;

[0112] The receiving module is further configured to, when the second terminal device is in the multicast or broadcast SL DRX state, and the resources corresponding to the TB indicated by the SCI do not belong to or partially belong to the SL resources corresponding to the multicast or broadcast SL DRX, not receive the TB indicated by the SCI, or receive the TB indicated by the SCI, but not start the HARQ RTT timer or the inactivity timer corresponding to the SCI.

[0113] The second terminal device provided in the tenth aspect of the present application can be used to execute the method provided in the fifth aspect of the present application, and the technical effects are similar, which will not be elaborated here.

[0114] The eleventh aspect of the present application provides a terminal device, including a processor, a memory, and a transceiver. The memory is used to store instructions, the transceiver is used to communicate with other devices, and the processor is used to execute the instructions stored in the memory, so that the terminal device executes any method provided in the first aspect, the third aspect, the fourth aspect, the fifth aspect, and each implementation manner of the present application.

[0115] The twelfth aspect of the present application provides a network device, including a processor, a memory, and a transceiver. The memory is used to store instructions, the transceiver is used to communicate with other devices, and the processor is used to execute the instructions stored in the memory, so that the network device executes any method provided in the second aspect and each implementation manner of the present application.

[0116] The thirteenth aspect of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed, a computer is enabled to execute any method provided in the first aspect, the third aspect, the fourth aspect, the fifth aspect, and each implementation manner of the present application.

[0117] A fourteenth aspect of the present application provides a computer-readable storage medium storing instructions that, when executed, cause a computer to execute any method provided in the second aspect of the present application and its various implementation manners.

[0118] A fifteenth aspect of the present application provides a computer program product including instructions that, when executed, cause a computer to execute any method provided in the first aspect, the third aspect, the fourth aspect, the fifth aspect, and the various implementation manners of the present application.

[0119] A sixteenth aspect of the present application provides a computer program product including instructions that, when executed, cause a computer to execute any method provided in the second aspect of the present application and its various implementation manners.

[0120] A seventeenth aspect of the present application provides a communication system including: a first terminal device, a second terminal device, and a network device. The first terminal device is configured to execute any method provided in the first aspect of the present application and its various implementation manners. The second terminal device is configured to execute the method provided in the third aspect of the present application. The network device is configured to execute any method provided in the second aspect of the present application and its various implementation manners.

[0121] In the sidelink communication method and apparatus provided in the embodiments of the present application, when the first terminal device (sender) has first data or first signaling to be sent, the first terminal device first determines whether the first data or first signaling supports multicast or broadcast SL DRX. When the first data or first signaling supports multicast or broadcast SL DRX, the first terminal device acquires the SL resources corresponding to the multicast or broadcast SL DRX and uses the SL resources corresponding to the multicast or broadcast SL DRX to send the first data or first signaling. Since the SL resources used by the sender to send the first data or first signaling are the SL resources corresponding to the multicast or broadcast SL DRX, and the receiving-end terminal device also receives on the SL resources corresponding to the multicast or broadcast SL DRX, it can be ensured that the first data or first signaling supporting multicast or broadcast SL DRX can be successfully received by the receiving-end terminal device, improving the SL communication quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0122] Figure 1 is a schematic diagram of a network architecture applicable to the present application;

[0123] Figure 2 is a schematic diagram of a unicast connection establishment process of SL DRX;

[0124] Figure 3 is a schematic diagram of SL resources used for multicast or broadcast SL DRX;

[0125] Figure 4 Another schematic diagram of SL resources for multicast or broadcast SL DRX;

[0126] Figure 5 Flowchart of the sidelink communication method provided in the first embodiment of this application;

[0127] Figure 6 Flowchart of the sidelink communication method provided in the second embodiment of this application;

[0128] Figure 7 Signaling flowchart of the sidelink communication method provided in the third embodiment of this application;

[0129] Figure 8 Signaling flowchart of the sidelink communication method provided in the fourth embodiment of this application;

[0130] Figure 9 Signaling flowchart of the sidelink communication method provided in the fifth embodiment of this application;

[0131] Figure 10 Schematic diagram of the SL resources of the terminal device;

[0132] Figure 11 A schematic diagram of the terminal device sending data;

[0133] Figure 12 Flowchart of the sidelink communication method provided in the sixth embodiment of this application;

[0134] Figure 13 Schematic diagram of the structure of the first terminal device provided in the seventh embodiment of this application;

[0135] Figure 14 Schematic diagram of the structure of the network device provided in the eighth embodiment of this application;

[0136] Figure 15 Schematic diagram of the structure of the second terminal device provided in the ninth embodiment of this application;

[0137] Figure 16 Schematic diagram of the structure of the second terminal device provided in the tenth embodiment of this application;

[0138] Figure 17 A schematic diagram of the structure of the terminal device provided in the eleventh embodiment of this application. Detailed implementation manners

[0139] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B may be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (s) or multiple items (s). For example, at least one (item) of a, b, or c may represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be single or multiple. In addition, in order to clearly describe the technical solutions in the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and roles. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order. For example, "first" in the first device in the embodiments of the present application and "second" in the second device are only used to distinguish different devices.

[0140] It should be noted that in the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0141] Figure 1 FIG. is a schematic diagram of a network architecture applicable to the present application, as Figure 1 shown. The network architecture includes a network device (such as a base station) 11, a first terminal device 12, and a second terminal device 13. The network device 11 communicates with the first terminal device 12 and the second terminal device 13 through the Uu air interface. The first terminal device 12 and the second terminal device 13 communicate with each other through the PC5 air interface. Communication through the PC5 interface is also referred to as SL communication. Figure 1 This is only an example for illustration and not a limitation. The network architecture may also include more network devices and terminal devices.

[0142] In the SL communication scenario, the first terminal device 12 and the second terminal device 13 can be within the coverage of the same base station (such as base station 11), or within the coverage of different base stations, or one of the terminal devices can be within the coverage of a base station while the other is outside the coverage of the base station, or both terminal devices are outside the coverage of the base station (out of coverage). A transmitting terminal device can perform SL communication with one or more receiving terminal devices. From the perspective of a receiving terminal device, a receiving device can also perform SL communication with one or more transmitting terminal devices.

[0143] The terminal device involved in the embodiments of this application is also referred to as a terminal, user equipment (UE), access terminal, user unit, user station, mobile station, mobile terminal, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal device can be a station (ST) in a wireless local area network (WLAN), a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device, or other processing devices connected to a wireless modem, a wearable device, a vehicle-mounted device, a road side unit (RSU), and a next-generation communication system, such as a terminal device in a fifth-generation (5G) network or a terminal device in a future evolved public land mobile network (PLMN), or a terminal device in a new radio (NR) communication system, etc.

[0144] The network device involved in the embodiments of this application may be referred to as an access network device, or a base station, etc. The base station may be an access point (AP) in WLAN, a base transceiver station (BTS) in a global system for mobile communication (GSM) or code division multiple access (CDMA), a node B (NB) in WCDMA, an evolved node B (eNB or eNodeB) in LTE, or a relay station or access point, or a new generation node B (gNodeB) in an NR system, etc. Optionally, the gNodeB may adopt a form with a separation of a central unit (CU) and a distributed unit (DU).

[0145] A typical application of SL communication is V2X communication. Exemplarily, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-people (V2P) communication, and vehicle-to-network (V2N) communication, etc. The embodiments of this application do not limit the specific communication scenarios of V2X. For example, V2X communication may be communication between vehicles, or communication between in-vehicle devices, or communication between an RSU and in-vehicle devices and / or network devices, or communication between network devices and in-vehicle devices and / or RSU, etc. The network device may be an LTE base station device or an NR base station device or a base station in a subsequent evolved system.

[0146] In the V2X scenario, the terminal device supports unicast, multicast, or broadcast communication. Unicast communication requires establishing a unicast connection, and multicast communication requires establishing a multicast communication group. For example, in the vehicle platooning service, vehicles with the same driving direction and close distance can form a convoy. A vehicle in the convoy can send data to other vehicles in the convoy. Further, the lead vehicle can establish a unicast communication connection with a certain member vehicle, and through the unicast connection, perform one-to-one data transmission with the member vehicle.

[0147] Before the transmitting end terminal device performs SL transmission, it needs to obtain transmission resources. In the embodiments of this application, the transmission resources used for SL communication are referred to as SL resources to distinguish from the uplink transmission resources and downlink data resources in the prior art. SL resources are also referred to as SL grants (SL grants). Correspondingly, before the receiving end terminal device performs reception, it also needs to determine the reception resources. Currently, the transmitting end terminal device can obtain SL resources through the following two modes (mode1).

[0148] mode1: The base station scheduling method. This base station scheduling method is similar to the uplink resource acquisition method of the Uu interface. When the terminal device has SL data to be transmitted, it first reports the sidelink buffer status report (SL BSR) to the base station, informing the base station how much data needs to be transmitted. The base station can allocate corresponding-sized SL resources to the terminal device from the SL transmission resource pool (Tx resource pool) according to the SL BSR. For periodic services, the terminal device can report the attributes of the periodic service to the base station, and the base station allocates periodic SL resources to the terminal device according to the attributes of the periodic service. The attributes of the periodic service include start time, period, packet size, etc. The terminal device that has been allocated periodic SL resources does not need to obtain SL resources by frequently sending SL BSRs.

[0149] mode2: The terminal device autonomous contention method. The terminal device can measure whether each time-frequency resource on the SL transmission resource pool is occupied to select an idle (i.e., unoccupied) SL resource for transmission, without the need for the base station to schedule SL resources.

[0150] The SL transmission resource pool includes multiple SL resources (such as time-frequency resources). When the base station schedules SL resources for the terminal device, it can select resources from this SL transmission resource pool. Similarly, when the terminal device autonomously selects SL resources, it also selects resources from this SL transmission resource pool. This SL transmission resource pool can be configured by the base station for the terminal device. It can be understood that there can be one or more SL transmission resource pools.

[0151] Similarly, when the terminal device acts as the receiving end for SL communication, it also needs to determine the corresponding receiving SL resources from the SL receiving resource pool (Rx resource pool). It can be understood that the SL resources of the transmitting resource pool and the receiving resource pool are corresponding, and there can also be one or more SL receiving resource pools.

[0152] In the existing communication protocols, for services that the receiving-end terminal device is interested in, it is necessary to monitor sidelink control information (SCI) at the moments corresponding to all SL resources in the SL receiving resource pool, in order to receive messages that may be sent by the sending-end terminal device. However, the sending-end terminal device may not send data most of the time, so it is not conducive to the energy saving of the receiving-end terminal device.

[0153] In the prior art, the receiving-end terminal device can adopt the DRX mechanism for energy saving. The receiving-end terminal device only receives downlink control information (DCI) during the active period of DRX, does not receive DCI during the dormant period of DRX, and the receiver of the receiving-end terminal device is in the off state during the dormant period of DRX, thereby achieving the purpose of energy saving.

[0154] The DRX mechanism is also introduced in SL communication, hereinafter referred to as SL DRX. The receiving-end terminal device that supports SL DRX only receives SCI during the active period of SL DRX, and turns off the receiver and does not receive SCI during the dormant period of SL DRX. SL DRX includes unicast SL DRX, multicast or broadcast SL DRX. Before the terminal device uses unicast SL DRX, it needs to first establish a unicast connection (PC5-S connection / unicast link), and then configure the corresponding SL DRX parameters through the established unicast connection.

[0155] The process of establishing a unicast connection for SL DRX can refer to Figure 2 the process shown, as Figure 2 shown, the process of establishing this unicast connection includes the following steps:

[0156] S101. The first terminal device sends a connection establishment request message to the second terminal device.

[0157] This connection establishment request message is used to request the establishment of a unicast connection. This connection establishment request is also called a PC5-S connection establishment request message, and this connection establishment request message can be a direct communication request message.

[0158] S102. The second terminal device sends a security establishment command message to the first terminal device.

[0159] S103. The first terminal device sends a security establishment completion message to the second terminal device.

[0160] S104. The second terminal device sends a connection establishment acceptance message to the first terminal device.

[0161] The security establishment command message can be a direct security mode command message, the security establishment completion message can be a direct security mode complete message, and the connection establishment acceptance message can be a direct communication accept message. The connection establishment request message can be sent in a unicast or broadcast manner, while the security establishment command message, the security establishment completion message, and the connection establishment acceptance message are all sent in a unicast manner.

[0162] During the above unicast connection establishment process, the corresponding security is also established. At the same time, after the unicast connection is established, the corresponding PC5-RRC connection also automatically exists. The security can be established by the upper layer of the terminal device (such as the PC5-S layer or the V2X layer). After the upper layer establishes the security, it notifies the access (AS) layer of the security configuration, which includes security algorithms, security parameters, security policies, etc. The AS layer can use the security configuration to protect the security of PC5-S messages, PC5-RRC messages, and user plane data transmissions.

[0163] In a relay communication scenario, before establishing a unicast connection, terminal devices discover each other through a discovery mechanism. Terminal devices can be divided into relay terminal devices and remote terminal devices. Relay terminal devices are always within the coverage area of the base station and can directly communicate with the base station. Remote terminal devices may or may not be within the coverage area of the base station. In order to directly transmit data with the network, remote terminal devices need to discover and connect to a relay terminal device.

[0164] Currently, there are two discovery modes between terminal devices: Discovery mode A, where the relay terminal device broadcasts an announcement message to the surrounding area, aiming to tell the surrounding remote terminal devices "I'm here, and you can find me". Discovery mode B, where the remote terminal device sends a solicitation message to inquire whether there is a relay terminal device around. After receiving the solicitation message, the relay terminal device decides whether to reply with a response message based on its own situation or other factors. If a relay terminal device replies with a response message, the two terminal devices discover each other.

[0165] To support multicast or broadcast SL DRX, it is necessary to configure the SL resources used for multicast or broadcast SL DRX (or the SL resources corresponding to multicast or broadcast SL DRX). The SL resources used for multicast or broadcast SL DRX can be configured in the following two ways. It can be understood that the SL resources here include SL reception resources or SL transmission resources.

[0166] In Method 1, a part of a pattern (which can also be called a subset) is intercepted from an existing resource pool (such as the R16 resource pool) for multicast or broadcast SL DRX. Figure 3 A schematic diagram of SL resources used for multicast or broadcast SL DRX is shown as Figure 3 follows. The gray part represents the intercepted pattern. The network device can define or configure the time-frequency domain location, period, etc. of the pattern resource and notify the terminal device, or the time-frequency domain location, period, etc. of the pattern resource is predefined by the protocol. It can be understood that there can be more discontinuous pattern resources in this resource pool. The terminal device supporting multicast or broadcast SL DRX can send or receive data on the SL resources shown in the gray part, ensuring the normal transmission of multicast or broadcast services.

[0167] In Method 2, a dedicated resource pool is configured for multicast or broadcast SL DRX. Figure 4 Another schematic diagram of SL resources used for multicast or broadcast SL DRX. The gray part represents the dedicated resource pool, which is used for multicast or broadcast SL DRX. The existing resource pool and this dedicated resource pool are independent. The terminal device supporting multicast or broadcast SL DRX can send or receive data or signaling supporting multicast or broadcast SL DRX on the dedicated resource pool shown in the gray part, ensuring the normal transmission of data or signaling supporting multicast or broadcast SL DRX.

[0168] The resource pools in the above Method 1 and Method 2 can be a transmission resource pool or a reception resource pool.

[0169] When the receiving-end terminal device determines that it supports multicast or broadcast SL DRX, the receiving-end terminal device only listens for the SCI during the activation period of multicast or broadcast SL DRX. While the sending-end terminal device may send data or signaling at any time. If the data or signaling sent by the sending-end terminal device is not at the time-frequency location corresponding to the activation period of multicast or broadcast SL DRX, then the receiving-end terminal device cannot receive the data or signaling sent by the sending-end, resulting in the loss of data or signaling. If the data or signaling sent by the sending-end terminal device is data or signaling supporting broadcast or multicast SL DRX, the loss of data or signaling supporting broadcast or multicast SL DRX will affect the communication quality of the terminal device.

[0170] In the embodiments of the present application, the data or signaling that supports broadcast or multicast SL DRX is also referred to as data or signaling that cannot be missed, or data or signaling that cannot be discarded, or important data or signaling, or data or signaling that needs to be received or transmitted on the SL resources corresponding to the supported broadcast or multicast SL DRX, or data or signaling of a specific version (such as R17). The data and signaling can also be collectively referred to as information. Therefore, the data or signaling that supports broadcast or multicast SL DRX is also referred to as the information that supports broadcast or multicast SL DRX.

[0171] The data or signaling that supports multicast or broadcast SL DRX includes services that support multicast or broadcast SL DRX or QoS flows (QoS flow) that support multicast or broadcast SL DRX. A QoS flow is data with a smaller or finer granularity than a service (that is, a service can include one or more QoS flows).

[0172] In the embodiments of the present application, the signaling that supports multicast or broadcast SL DRX includes one or more of the following signaling: four messages during the unicast connection establishment process (refer to Figure 2 the four messages shown), messages during the discovery process, messages related to the SL capabilities of the terminal device, and the first PC5 RRC reconfiguration message. Among them, the four messages during the unicast connection establishment process are Figure 2 the ones shown: connection establishment request message, security establishment command message, security establishment completion message, and connection establishment acceptance message. The messages during the discovery process include the following three messages: announcement message, solicitation message, and response message to the solicitation message. The messages related to the SL capabilities of the terminal device include the UECapabilityEnquirySidelink message and the UECapabilityInformationSidelink message.

[0173] To solve the problems of the prior art, in the embodiments of the present application, a core network device or a V2X application server may instruct a terminal device to support multicast or broadcast SL DRX data or signaling, or instruct the terminal device which data or signaling supports multicast or broadcast SL DRX. When the sending-end terminal device has data to send, it determines whether the data or signaling to be sent is data or signaling that supports multicast or broadcast SL DRX. If the data or signaling to be sent is data or signaling that supports multicast or broadcast SL DRX, the SL resources corresponding to multicast or broadcast DRX are used to send the data or signaling that supports multicast or broadcast SL DRX. The receiving-end terminal device receives the data or signaling that supports multicast or broadcast SL DRX on the SL resources corresponding to multicast or broadcast DRX. Since the sending resources used by the sending-end terminal device correspond to the receiving resources used by the receiving-end terminal, that is, both the sending resources and the receiving resources are the SL resources corresponding to multicast or broadcast DRX, it can be ensured that the data or signaling that supports multicast or broadcast SL DRX can be successfully received by the receiving-end device without affecting the SL communication quality.

[0174] The data or signaling that supports multicast or broadcast SL DRX may be instructed by a core network device or a V2X application server, or may be pre-configured inside the terminal device. This embodiment does not limit this. Among them, the data that supports multicast or broadcast SL DRX includes services or QoS flows that support multicast or broadcast SL DRX. The core network device or the V2X application server may instruct the service type that supports multicast or broadcast SL DRX, the information of the OoS flow, or the destination address, etc. The information of the QoS flow may be the identifier of the QoS flow (PC5 QoS flow identifier, PFI).

[0175] In this embodiment, the core network device or the V2X application server may send first indication information to the terminal device, where the first indication information is used to indicate whether the data or signaling supports multicast or broadcast SL DRX. The upper layer of the terminal device receives the first indication information from the core network device or the V2X application server and sends the first indication information to the AS layer. Among them, the upper layer of the terminal device can be understood as a layer between the application layer and the AS layer. The upper layer includes the PC5-S layer or the V2X layer. The AS layer of the terminal device includes one or more of the following: physical layer, media access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and radio resource control (RRC) layer.

[0176] When the core network device or the V2X application server indicates to the terminal device whether the data supports multicast or broadcast SL DRX, or when the upper layer of the terminal device indicates to the AS layer whether the data supports multicast or broadcast SL DRX, it may indicate whether each service type / each destination address / each QoS flow supports multicast or broadcast SL DRX, or may only indicate the service type / destination address / QoS flow that supports multicast or broadcast SL DRX. Among them, the QoS flow is data with a finer or smaller granularity than the service. When indicating whether the service supports multicast or broadcast SL DRX, it can be achieved by indicating whether the data corresponding to the service type or the destination address supports multicast or broadcast SL DRX. It can be understood that the destination address can be obtained by converting the service type.

[0177] One destination address or service may correspond to or be associated with multiple QoS flows. Among them, some QoS flows among the multiple QoS flows corresponding to one destination address may support multicast or broadcast SL DRX, and some other QoS flows may not support multicast or broadcast SL DRX. Therefore, when the core network device or the V2X application server indicates to the terminal device whether the QoS flow supports multicast or broadcast SL DRX, or when the upper layer of the terminal device indicates to the AS layer whether the QoS flow supports multicast or broadcast SL DRX, it may indicate whether each QoS flow associated with the destination address supports multicast or broadcast SL DRX, or indicate which QoS flows associated with the destination address support multicast or broadcast SL DRX.

[0178] When a core network device or a V2X application server indicates to a terminal device whether a signaling supports multicast or broadcast SLDRX, or when the upper layer of the terminal device indicates to the AS layer whether a signaling supports multicast or broadcast SLDRX, it may indicate whether each type of signaling / signaling corresponding to each destination address supports multicast or broadcast SLDRX, or indicate whether a signaling with a certain name supports multicast or broadcast SLDRX.

[0179] When the upper layer of the terminal device indicates to the AS layer whether it supports multicast or broadcast SLDRX, the indication granularity is understood to be the granularity of the terminal device at this time.

[0180] Figure 5 The flowchart of the sidelink communication method provided in the first embodiment of this application is as Figure 5 shown. The method provided in this embodiment includes the following steps:

[0181] S201. The first terminal device determines that the first data or the first signaling supports the first DRX, and the first DRX is multicast or broadcast SLDRX.

[0182] The first terminal device is a sending end, and the first data or the first signaling is the data or signaling to be currently sent. When there is the first data or the first signaling to be sent, the first terminal device determines whether the first data or the first signaling supports the first DRX.

[0183] Exemplarily, the first terminal device determines that the first data or the first signaling supports the first DRX according to the first indication information, and the first indication information is used to indicate that the first data or the first signaling supports multicast or broadcast SLDRX. The first indication information may be sent by a core network device or a V2X application server to the upper layer of the first terminal device, the upper layer of the first terminal device sends the first indication information to the AS layer, and the AS layer of the first terminal device determines whether the first data or the first signaling supports the first DRX according to the first indication information.

[0184] Optionally, the first indication information includes that the service or QoS flow associated with the first data supports multicast or broadcast SLDRX. When the first indication information is used to indicate that the service associated with the first data supports multicast or broadcast SLDRX, it may indicate that the service type or destination address associated with the first data supports multicast or broadcast SLDRX.

[0185] In one implementation, when determining whether the first signaling supports the first DRX, the first terminal device may also not use the first indication information, and the first terminal device decides which signaling supports the first DRX according to its own policy. In another implementation, the first terminal device may determine whether the first signaling supports the first DRX in combination with the first indication information. For example, the first terminal device determines, according to its own policy, that the first signaling is an alternative signaling that supports the first DRX, and further determines whether the destination address of this signaling is the destination address indicated in the first indication information. If the destination address of this signaling is the destination address indicated in the first indication information, it is determined that the first signaling supports the first DRX.

[0186] Optionally, the first terminal device decides which signaling supports the first DRX according to its own policy, or decides which signaling supports the first DRX according to the rules predefined in the protocol.

[0187] Optionally, the first terminal device may determine that the first terminal device supports the first DRX according to the granularity of the terminal device. It can be understood that the upper layer of the first terminal device indicates that the AS layer of the first terminal device supports the first DRX, and the indication granularity is the granularity of the terminal device.

[0188] S202. The first terminal device obtains a first SL resource, and the first SL resource is the SL resource corresponding to the first DRX.

[0189] After the first terminal device determines that the first data or the first signaling supports the first DRX, the first terminal device obtains the resource corresponding to the multicast or broadcast SL DRX for transmitting the first data or the first signaling, that is, the first SL resource.

[0190] The first terminal device may obtain the first SL resource in the model mode (i.e., the base station scheduling mode). Specifically, the first terminal device sends a first request message to the network device, and this first request message is used to request the first SL resource. The first terminal device receives the information of the first SL resource sent by the network device. The network device may be a base station, and the base station allocates the first SL resource to the first terminal device according to the format, type of the first request message, or the content in the first request message.

[0191] The first terminal device may also obtain the first SL resource in the mode2 mode (i.e., the mode in which the terminal device autonomously selects resources). Specifically, the first terminal device obtains the first SL resource by measuring the idle SL resources. Exemplarily, the first terminal device may use the sensing method to measure whether the SL resource is idle, and determine the finally available first SL resource through resource exclusion.

[0192] When the first terminal device obtains the first SL resource by means of base station scheduling, it is necessary to let the base station know through the first request message that the resource requested by the first terminal device is the resource corresponding to multicast or broadcast SL DRX.

[0193] In the first implementation manner, the first request message includes second indication information, which is used to indicate that the SL resource required by the data or signaling corresponding to the destination address or QoS flow is the SL resource corresponding to multicast or broadcast SL DRX. After receiving the first request message, the base station allocates the SL resource corresponding to multicast or broadcast DRX for the first terminal device according to the second indication information included in the first request message.

[0194] In the embodiments of the present application, the SL resource required by the data or signaling corresponding to the destination address or QoS flow can be understood as the SL resource used or required to be used or about to be used by the data or signaling corresponding to the destination address or QoS flow.

[0195] In the second implementation manner, before the first terminal device sends the first request message to the base station, it first sends second indication information to the base station, which is used to indicate that the SL resource required by the data or signaling corresponding to the destination address or QoS flow is the SL resource corresponding to multicast or broadcast DRX. The base station allocates the SL resource corresponding to multicast or broadcast DRX for the first terminal device according to the first request message and the second indication information.

[0196] In the third implementation manner, the first terminal device sends the first request message to the base station using a dedicated LCG or a dedicated destination address index. The base station determines that the resource requested by the first terminal device is the SL resource corresponding to multicast or broadcast DRX according to the dedicated LCG or dedicated destination address index used to send the first request message. Alternatively, the first terminal device sends a first request message in a specific format to the base station, and the base station determines that the resource requested by the first terminal device is the SL resource corresponding to multicast or broadcast DRX according to the format of the first request message. Alternatively, the first request message is a dedicated SR, and the base station determines that the resource requested by the first terminal device is the SL resource corresponding to multicast or broadcast DRX according to the dedicated SR.

[0197] It should be noted that in the embodiments of the present application, the second indication information is associated with the destination address or QoS flow. When the second indication information is associated with the destination address, the second indication information is used to indicate that the SL resource required by the data or signaling corresponding to the destination address is the SL resource corresponding to multicast or broadcast DRX. When the second indication information is associated with the QoS flow, the second indication information is used to indicate that the SL resource required by the data or signaling corresponding to the QoS flow is the SL resource corresponding to multicast or broadcast DRX.

[0198] Optionally, the second indication information may also be used to indicate that the SL resources required for the data or signaling corresponding to the first terminal device are the SL resources corresponding to multicast or broadcast SL DRX, that is, the second indication information is at the terminal device granularity.

[0199] Optionally, the first request message is any one of the following messages: SL scheduling request (SR), SL BSR, or UAI message. Correspondingly, for the second implementation manner, the second indication information may be carried in the SUI message.

[0200] (1) The first request message is SL SR.

[0201] In an exemplary manner, the first terminal device sends a dedicated SL SR to the base station. After receiving the dedicated SL SR, the base station determines, based on the dedicated SL SR, that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast SL DRX. Herein, the dedicated SL SR may be understood as an SR sent on dedicated transmission resources.

[0202] The dedicated SL SR may be pre-configured for the first terminal device by the base station or other network devices, or may be predefined by the protocol. For the first terminal device, the SL SR may be divided into two categories: ordinary SL SR and dedicated SL SR. The dedicated SL SR is used to request the SL resources corresponding to multicast or broadcast DRX, and the ordinary SL SR is used to request other SL resources or unrestricted SL resources other than the SL resources corresponding to multicast or broadcast DRX. The base station can determine whether the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the type of the SL SR.

[0203] Exemplarily, the SR ID corresponding to the dedicated SL SR is predefined by the protocol. When the first terminal device sends an SL SR to the network device on the resources corresponding to the SR ID, the network device can, based on the resources or the SR ID, know that the first terminal device requests the sidelink transmission resources corresponding to multicast or broadcast SL DRX, and thus can configure the corresponding sidelink transmission resources for the first terminal device.

[0204] In another implementation manner, before the first terminal device sends the dedicated SL SR to the base station, it first requests the base station to configure the dedicated SL SR. Before the first terminal device requests the base station to configure the SL SR, it sends the second indication information to the base station, and the base station configures the dedicated SL SR for the first terminal device according to the second indication information. Herein, the base station configuring the dedicated SL SR may be understood as configuring dedicated transmission resources for the SL SR.

[0205] Exemplarily, the first terminal device sends an SUI message to the base station. The SUI message includes a destination address and a QoS flow corresponding to the destination address. Different from the prior art, in this embodiment, the SUI message further includes the second indication information. After receiving the SUI message, the base station allocates a dedicated SLSR for the first terminal device according to the second indication information included in the SUI message. That is to say, the base station can configure a dedicated SLSR for the destination address corresponding to the second indication information or the LCH (logical channel) associated with the QoS flow. It can be understood that the network configures the SR ID corresponding to the dedicated SLSR. When the first terminal device sends an SLSR to the network device on the resources corresponding to the SR ID, the network device can learn, based on the resources or the SR ID, that the first terminal device requests sidelink transmission resources corresponding to multicast or broadcast SL DRX, and then can configure corresponding sidelink transmission resources for the first terminal device.

[0206] In another exemplary manner, the SLSR includes the second indication information, and the base station determines, according to the second indication information, that the resources requested by the first terminal device are sidelink resources corresponding to multicast or broadcast DRX. In this manner, there is no need to define a dedicated SLSR, and the second indication information can be included in all normal SLSRs or ordinary SLSRs.

[0207] (2) The first request message is an SL BSR.

[0208] In an exemplary manner, the first terminal device may send an SL BSR to the base station using a dedicated logical channel group (LCG). After receiving the SL BSR, the base station determines, according to the LCG that sends the SL BSR, that the resources requested by the first terminal device are sidelink resources corresponding to multicast or broadcast DRX.

[0209] The dedicated LCG (such as a dedicated logical channel group identifier) that sends the SL BSR may be pre-configured for the first terminal device by the base station or other network devices, or may be predefined by the protocol. For the first terminal device, the LCGs for sending SL BSRs are divided into two categories: ordinary LCGs and dedicated LCGs. The dedicated LCG is used to request sidelink resources corresponding to multicast or broadcast DRX, and the ordinary LCG is used to request other sidelink resources or unrestricted sidelink resources except for the sidelink resources corresponding to multicast or broadcast DRX. The base station can determine whether the resources requested by the first terminal device are sidelink resources corresponding to multicast or broadcast DRX according to the type of the LCG that sends the SL BSR.

[0210] In another implementation, before the first terminal device sends the SL BSR to the base station using the dedicated LCG, it first requests the base station to configure the dedicated LCG. Before the first terminal device requests the base station to configure the dedicated LCG, it sends the second indication information to the base station, and the base station configures the dedicated LCG for the first terminal device according to the second indication information.

[0211] Exemplarily, the first terminal device sends a SUI message to the base station. The SUI message includes the destination address and the QoS flow corresponding to the destination address. The SUI message also includes the second indication information. After receiving the SUI message, the base station allocates a dedicated LCG for sending the SL BSR to the first terminal device according to the second indication information included in the SUI message. That is to say, the base station can configure the destination address or QoS flow corresponding to the second indication information to be transmitted on the dedicated LCG.

[0212] In another exemplary manner, the first terminal device can send the SL BSR to the base station using a dedicated destination index. After receiving the SL BSR, the base station determines that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the destination index of the SL BSR sent. The dedicated destination index can uniquely identify a dedicated destination address.

[0213] The dedicated destination index for sending the SL BSR can be pre-configured for the first terminal device by the base station or other network devices, or can be predefined by the protocol. For the first terminal device, the destination indexes for sending the SL BSR are divided into two categories: the ordinary destination index and the dedicated destination index. The dedicated destination index is used to request the SL resources corresponding to multicast or broadcast DRX, and the ordinary destination index is used to request other SL resources or unrestricted SL resources except the SL resources corresponding to multicast or broadcast DRX. The base station can determine whether the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the type of the destination index of the SL BSR sent.

[0214] In another exemplary manner, the second indication information is included in the SL BSR, and the base station determines that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the second indication information. In this manner, there is no need to configure a dedicated LCG or a dedicated destination index for the SL BSR.

[0215] In another exemplary manner, the first terminal device sends an SL BSR to the base station using a normal LCG or a normal destination address index. Before sending the SL BSR to the base station, the second indication information is included in the SL BSR. Exemplarily, the destination address index included in the SL BSR or the LCG corresponding to the destination address index may be associated with the second indication information. After receiving the SL BSR, the base station determines that the SL resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX based on the second indication information and the destination address index included in the SL BSR or the LCG corresponding to the destination address index.

[0216] Specifically, the first terminal device determines that the destination address index in the SL BSR is associated with the second indication information according to the destination address associated with the first indication information; or the first terminal device determines that the LCG under the destination address index mapped by the QoS flow in the SL BSR is associated with the second indication information according to the QoS flow associated with the first indication information.

[0217] In another exemplary manner, the first terminal device sends an SL BSR in a specific format to the base station, and the SL BSR in the specific format is dedicated to requesting the SL resources corresponding to multicast or broadcast DRX.

[0218] The format of the SL BSR can be pre-configured by the base station or other network devices to the first terminal device or predefined in the protocol. For the first terminal device, the format of the SL BSR is divided into two categories: normal format and specific format. The SL BSR in the specific format is a newly defined format or a new media access control element (MAC CE), dedicated to requesting the SL resources corresponding to multicast or broadcast DRX. The SL BSR in the normal format includes various existing formats, used to request other SL resources except the SL resources corresponding to multicast or broadcast DRX or unrestricted SL resources. The base station can determine whether the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the format of the SL BSR.

[0219] (3) The first request message is a UAI message.

[0220] In an exemplary manner, the first terminal device sends a UAI message to the base station. The UAI message includes QoS flow information and a service mode. Different from the prior art, the UAI message also includes the second indication information. After receiving the UAI message, the base station determines that the SL resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX according to the second indication information.

[0221] Exemplarily, the QoS flow information or service mode in the UAI message is associated with the second indication information.

[0222] In another implementation, before the first terminal device sends a UAI message to the base station, it first sends the second indication information to the base station, that is, the UAI message does not include the second indication information; for example, the second indication information is associated with the destination address or QoS flow included in the SUI message sent by the first terminal device. Further, the base station determines, based on the SUI message and the UAI message, that the SL resource requested by the first terminal device is the SL resource corresponding to multicast or broadcast DRX when the QoS flow or destination address associated with the second indication information in the SUI message corresponds to the QoS flow or service mode of the UAI message.

[0223] The first SL resource allocated by the base station for the first terminal device according to the UAI message can be a semi-persistent scheduling (SPS) resource, and this SPS resource is the SL resource corresponding to multicast or broadcast DRX.

[0224] S203. The first terminal device sends first data or first signaling on the first SL resource.

[0225] Correspondingly, the second terminal device receives the first data or first signaling on the SL resource corresponding to multicast or broadcast SL DRX, and the second terminal device is the receiving-end terminal device. The first terminal device sends the first data or first signaling in a multicast or broadcast manner. Optionally, the first terminal device can also send the first signaling in a unicast manner.

[0226] As the receiving end, the second terminal device also receives the first indication information from the core network device or the V2X application server. This first indication information is first sent to the upper layer of the second terminal device, and the AS layer of the second terminal device receives this first indication information from the upper layer. The second terminal device determines, based on this first indication information, whether the currently to-be-received data or signaling supports the first DRX. If the second terminal device determines that the currently to-be-received data and / or signaling supports the first DRX, it activates the first DRX. After activating the first DRX, the second terminal device can receive data or signaling on the SL resource corresponding to multicast or broadcast SL DRX, so as to ensure that the data or signaling sent by the first terminal device on the SL resource corresponding to multicast or broadcast SL DRX can be received by the second terminal device.

[0227] Among them, the data to be received by the second terminal device can be understood as the data that the second terminal device is interested in or the data that the upper layer of the second terminal device instructs the AS layer to receive.

[0228] Optionally, when the data and / or signaling to be received currently supports the first DRX, activating the first DRX includes the following two cases: when there are multiple pieces of data and / or signaling to be received, and all of the multiple pieces of data and / or signaling support the first DRX, the first DRX is activated; when some of the multiple pieces of data and / or signaling support the first DRX, the first DRX is activated.

[0229] When some of the multiple pieces of data and / or signaling support the first DRX, activating the first DRX may cause the data and / or signaling that does not support the first DRX among the multiple pieces of data and / or signaling to not be received by the receiving-end terminal device. When all of the data and / or signaling among the multiple pieces of data and / or signaling support the first DRX, all of the multiple pieces of data and / or signaling can be received by the receiving-end terminal device after activating the first DRX.

[0230] To determine whether the data or signaling to be received supports the first DRX, specifically: compare the destination address or QoS flow of the data or signaling to be received with the destination address or QoS flow indicated by the first indication information. If the destination address or QoS flow of the data or signaling to be received belongs to the destination address or QoS flow indicated by the first indication information, it is determined that the data or signaling to be received supports the first DRX.

[0231] It can be understood that although the second terminal device does not know on which resource of the multicast or broadcast SL DRX corresponding SL resources (i.e., the transmission resource pool corresponding to the multicast or broadcast SL DRX configured for the first terminal device) the first terminal device specifically sends data, after the second terminal device activates the first DRX, it will receive on all resources of the multicast or broadcast SL DRX corresponding SL resources (i.e., the reception resource pool corresponding to the multicast or broadcast SL DRX configured for the second terminal device), so that the first data or the first signaling can be successfully received.

[0232] Optionally, when the second terminal device does not activate the first DRX, it will receive data at the full set of time-frequency resource positions corresponding to the reception resource pool. If the SL resources corresponding to the multicast or broadcast SL DRX are a subset of the normal reception resource pool, the second terminal will also receive data on the SL resources corresponding to the multicast or broadcast SL DRX.

[0233] Optionally, the upper layer of the second terminal device sends the first indication information to the AS layer. The first indication information can be used to indicate whether the second terminal device supports the first DRX. That is to say, the granularity of the first indication information is at the granularity of the terminal device. The second terminal device determines that it currently supports the first DRX based on the first indication information, and then activates the first DRX.

[0234] In this embodiment, when the first terminal device has first data or first signaling to be sent, the first terminal device first determines whether the first data or first signaling supports multicast or broadcast SL DRX. When the first data or first signaling supports multicast or broadcast SL DRX, the first terminal device obtains the SL resources corresponding to the multicast or broadcast SL DRX, and uses the SL resources corresponding to the multicast or broadcast SL DRX to send the first data or first signaling. Since the SL resources used by the sending terminal device to send the first data or first signaling are the SL resources corresponding to the multicast or broadcast SL DRX, and the receiving terminal device also receives on the SL resources corresponding to the multicast or broadcast SL DRX, it can be ensured that the first data or first signaling that supports multicast or broadcast SL DRX can be successfully received by the receiving terminal device, thereby improving the SL communication quality.

[0235] Figure 6 FIG. 4 is a flowchart of the sidelink communication method provided in Embodiment 2 of the present application. On the basis of Embodiment 1, this embodiment describes step S203 in detail, as Figure 6 shown, the method provided in this embodiment includes the following steps:

[0236] S301. The first terminal device determines that the first data or first signaling supports a first DRX, and the first DRX is a multicast or broadcast SL DRX.

[0237] S302. The first terminal device obtains first SL resources, and the first SL resources are the SL resources corresponding to the first DRX

[0238] For the specific implementation manners of steps S301 and S302, refer to the descriptions of steps 201 and S202 in Embodiment 1, which will not be elaborated here.

[0239] S303. The first terminal device only selects or preferentially selects the destination address / logical channel corresponding to the first data or first signaling from the destination address / logical channel (LCH) to be transmitted and transmits it on the first SL resources.

[0240] When there is data to be sent on multiple logical channels, and the total amount of data to be transmitted exceeds the transmission capacity of the current transmission time interval (TTI), it is necessary to consider which logical channel to send first, which is called logical channel prioritization (LCP). The TTI is the smallest unit of radio resource scheduling. It can be understood that with the evolution or change of the network, the smallest unit of radio resource scheduling may change.

[0241] When performing sidelink transmission, when the base station allocates transmission resources to the terminal device, it does not specify which resources are for which destination addresses or which logical channels. After obtaining the transmission resources, the terminal device can determine the priorities of the logical channels according to the conditions of each logical channel. Usually, the priority of the control logical channel is higher than that of the data logical channel, and the priority among the data logical channels can be determined according to the QoS parameters of the data transmitted thereon.

[0242] In SL LCP, the first terminal device needs to make two selections. First, it selects the destination address to be transmitted. This destination address corresponds to multiple QoS flows, and different QoS flows are mapped to different logical channels. The priority of the logical channel is determined by the priority of the QoS flow carried on the logical channel.

[0243] It can be understood that S304 is only executed when the first terminal device obtains the first SL resource. When the first terminal device selects the destination address for transmission, it only selects or preferentially selects the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted as the destination address for transmission, and maps the selected destination address to the logical channel for transmission.

[0244] The destination addresses to be transmitted may include the destination address corresponding to the first data or the first signaling and other destination addresses. Selecting only the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted can be understood as that for the first SL resource, only the destination address corresponding to the first data or the first signaling is selected for this transmission, and other destination addresses will not be selected for transmission.

[0245] Or, preferentially selecting the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted can be understood as selecting the destination address for transmission according to the priority of the destination addresses to be transmitted. Among them, the priority of the destination address corresponding to the first data or the first signaling is set to the highest. When the first terminal device makes a selection, it preferentially selects the destination address with the highest priority for transmission. Therefore, the first terminal device can preferentially select the destination address corresponding to the first data or the first signaling. It can be understood that when the destination address corresponding to the first data or the first signaling does not exist, other destination addresses can be selected for transmission.

[0246] When the first terminal device selects the logical channel for transmission, the first terminal device only selects or preferentially selects the logical channel corresponding to the first data or the first signaling from the logical channels to be transmitted as the logical channel for transmission.

[0247] When the logical channels to be transmitted may include the logical channels corresponding to the first data or the first signaling and other logical channels, selecting only the logical channels corresponding to the first data or the first signaling from the logical channels to be transmitted can be understood as, for the first SL resource, only the logical channels corresponding to the first data or the first signaling are selected for this transmission, and other logical channels will not be selected for transmission.

[0248] Alternatively, preferentially selecting the logical channels corresponding to the first data or the first signaling from the logical channels to be transmitted can be understood as selecting the logical channels for transmission according to the priorities of the logical channels to be transmitted. In this embodiment, the priorities of the logical channels corresponding to the first data or the first signaling are set to the highest. In the prior art, the logical channel priorities are usually determined according to the logical channels of the QoS flows carried on the logical channels. When the first terminal device selects, it preferentially selects the logical channel with the highest priority for transmission. Therefore, the first terminal device can preferentially select the logical channels corresponding to the first data or the first signaling. The other logical channels in the logical channels to be transmitted can determine the logical channel priorities according to the logical channels of the QoS flows carried on the logical channels. It can be understood that when the logical channels corresponding to the first data or the first signaling do not exist, other logical channels can be selected for transmission.

[0249] It can be understood that in other embodiments of the present application, when the first terminal device selects the destination address / logical channel corresponding to the first data or the first signaling for transmission, it can also use the existing solutions for selection.

[0250] In this embodiment, when the first terminal device transmits the first data or the first signaling on the first SL resource, only or preferentially selecting the destination address / logical channel corresponding to the first data or the first signaling from the destination address / logical channels to be transmitted can ensure that the first data or the first signaling is preferentially transmitted, and avoid the first data or the first signaling being delayed or discarded due to LCP. Since the first data or the first signaling supporting multicast or broadcast SL DRX is usually important data or signaling, preferentially transmitting the first data or the first signaling further improves the SL communication quality.

[0251] Figure 7 This is the signaling flowchart of the sidelink communication method provided in Embodiment 3 of the present application. On the basis of Embodiment 1 and Embodiment 2, this embodiment takes the base station scheduling as an example to illustrate the sidelink communication method. This embodiment takes the network device as the base station as an example for illustration, as Figure 7 shown, the method provided in this embodiment includes the following steps:

[0252] S401. The first terminal device determines that the first data or the first signaling supports the first DRX, and the first DRX is a multicast or broadcast SL DRX.

[0253] The specific implementation manner of this step refers to the description of step S201 in Embodiment 1, which will not be elaborated here.

[0254] S402. The first terminal device sends a first request message to the base station, and the first request message includes second indication information.

[0255] The second indication information is used to indicate that the SL resources required for the destination address or the data or signaling corresponding to the QoS flow are the SL resources corresponding to multicast or broadcast DRX. Optionally, the first request message is any one of the following messages: SLSR, SL BSR, or UAI message. Correspondingly, the second indication information may be carried in the SUI message.

[0256] S403. The base station allocates first SL resources for the first terminal device according to the first request message.

[0257] When the first request message is SLSR, in an exemplary manner, the first terminal device sends a dedicated SLSR to the base station. After receiving the dedicated SLSR, the base station determines, according to the dedicated SLSR, that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources for the first terminal device. The dedicated SLSR may be pre-configured for the first terminal device by the base station or other network devices, or may be defined by the protocol. In this manner, the dedicated SLSR may not include the second indication information, and the base station can determine, according to the dedicated SLSR, that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX. Optionally, the dedicated SLSR may also include the second indication information, and the base station determines, according to the dedicated SLSR and the second indication information, that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX.

[0258] Exemplarily, the SR ID corresponding to the dedicated SLSR is pre-defined by the protocol. When the first terminal device sends an SLSR to the network device on the resources corresponding to the SR ID, the network device can learn, based on the resources, that the first terminal device requests side-link transmission resources corresponding to multicast or broadcast SL DRX, and thus can configure corresponding side-link transmission resources for the first terminal device.

[0259] In another implementation manner, before receiving the dedicated SLSR, the base station configures the dedicated SLSR for the first terminal device according to the request of the first terminal device. When the first terminal device requests to configure the dedicated SLSR, it sends the second indication information to the base station in the request message, and the base station configures the dedicated SLSR for the first terminal device according to the second indication information.

[0260] When the first request message is an SL SR, in another exemplary manner, the first terminal device sends an SL SR (which may also be referred to as a normal SL SR) to the base station. The SL SR includes second indication information. The base station determines, based on the second indication information, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources to the first terminal device.

[0261] When the first request message is an SL BSR, in one exemplary manner, the first terminal device may send an SL BSR to the base station using a dedicated LCG or a dedicated destination address index. After receiving the SL BSR, the base station determines, based on the dedicated LCG or the dedicated destination address index of the SL BSR, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources to the first terminal device. The dedicated LCG or the dedicated destination address index is pre-configured for the first terminal device by the base station or other network devices, or may also be pre-defined by the protocol. In this manner, the SL BSR may not include second indication information, and the base station can determine, based on the dedicated LCG or the dedicated destination address index, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX. Optionally, the SL BSR may also include second indication information, and the base station determines, based on the dedicated LCG or the dedicated destination address index, and the second indication information, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX.

[0262] When the first request message is an SL BSR, in another exemplary manner, the first terminal device sends an SL BSR to the base station using the normal LCG or the normal destination address index of the SL BSR. The SL BSR includes second indication information. The base station determines, based on the second indication information, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources to the first terminal device.

[0263] When the first request message is an SL BSR, in yet another exemplary manner, the first terminal device sends an SL BSR in a specific format to the base station. The specific format of the SL BSR is dedicated to requesting SL resources corresponding to multicast or broadcast DRX. After receiving the SL BSR, the base station determines, based on the format of the SL BSR, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources to the first terminal device.

[0264] When the first request message is a UAI message, after receiving the UAI message, the base station determines, based on the second indication information included in the UAI message, that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates first SL resources to the first terminal device.

[0265] Alternatively, before the base station receives the UAI message, it receives the SUI message sent by the first terminal device. The SUI message includes second indication information, and the second indication information is associated with the destination address or QoS flow included in the SUI message. After the base station receives the UAI message, when the QoS flow or service mode included in the UAI message corresponds to the destination address or QoS flow associated with the second indication information, the base station determines that the SL resource requested by the first terminal device is the SL resource corresponding to multicast or broadcast DRX, and allocates the first SL resource to the first terminal device.

[0266] S404. The base station sends the information of the first SL resource to the first terminal device.

[0267] The base station may carry the information of the first SL resource in the response message of the first request message or the RRC reconfiguration message or the DCI and send it to the first terminal device.

[0268] S405. The first terminal device sends the first data or the first signaling to the second terminal device on the first SL resource.

[0269] The first terminal device may use the existing LCP rules to send the first data or the first signaling on the first SL resource, or may use the method of Embodiment 2 to only select or preferentially select the destination address / logical channel corresponding to the first data or the first signaling from the destination address / logical channel to be transmitted and transmit the first data or the first signaling on the first SL resource. The specific implementation manner refers to the description of step 304 in Embodiment 2 and will not be elaborated here.

[0270] Correspondingly, the second terminal device receives the first data or the first signaling on the first SL resource. It can be understood that the first terminal device sends the first data or the first signaling in a multicast or broadcast manner, and the terminal devices within the multicast or broadcast reception range can all be used as the second terminal device to receive the first data or the first signaling.

[0271] In this embodiment, when the first terminal device requests resources from the first base station, by carrying the second indication information in the first request message, the base station can determine according to the second indication information that the resources requested by the first terminal device are the SL resources corresponding to multicast or broadcast DRX, so as to be able to allocate the required resources to the first terminal device.

[0272] Figure 8 This is the signaling flowchart of the sidelink communication method provided in Embodiment 4 of this application. The difference between this embodiment and Embodiment 3 is that before the first terminal device sends the first request message to the base station, it first sends the second indication information to the base station, and the base station allocates resources to the first terminal device according to the second indication information and the first request message. As Figure 8As shown in the figure, the method provided in this embodiment includes the following steps:

[0273] S501. The first terminal device determines that the first data or the first signaling supports the first DRX, and the first DRX is a multicast or broadcast SL DRX.

[0274] S502. The first terminal device sends an SUI message to the base station, and the SUI message includes second indication information.

[0275] In this embodiment, the case where the second indication information is carried in the SUI message is taken as an example for illustration. It can be understood that the second indication information can also be carried in other messages, and this embodiment does not limit this.

[0276] S503. The first terminal device sends a first request message to the base station.

[0277] Optionally, the first request message is any one of the following messages: SL SR, SL BSR, or UAI message.

[0278] S504. The base station allocates a first SL resource for the first terminal device according to the first request message.

[0279] When the first request message is SL SR, in an exemplary manner, the first terminal device sends a dedicated SL SR to the base station. After receiving the dedicated SL SR, the base station determines, according to the dedicated SL SR, that the resources requested by the first terminal device are SL resources corresponding to the multicast or broadcast DRX, and allocates a first SL resource for the first terminal device. Wherein, the dedicated SL SR is allocated by the base station for the first terminal device according to the second indication information in the SUI message. Correspondingly, before S503, the base station sends the configuration information of the dedicated SL SR to the first terminal device through an SUI response message or other messages.

[0280] When the first request message is SL BSR, in an exemplary manner, the first terminal device can send an SL BSR to the base station using a dedicated LCG or a dedicated destination address index. After receiving the SL BSR, the base station determines, according to the dedicated LCG or the dedicated destination address index of the SL BSR, that the resources requested by the first terminal device are SL resources corresponding to the multicast or broadcast DRX, and allocates a first SL resource for the first terminal device. The dedicated LCG or the dedicated destination address index is configured by the base station for the first terminal device according to the second indication information in the SUI message. Correspondingly, before S503, the base station sends the configuration information of the dedicated LCG or the dedicated destination address index to the first terminal device through an SUI response message or other messages.

[0281] Optionally, the SL BSR may also include second indication information, and the base station determines that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX based on the dedicated LCG or the dedicated destination address index and the second indication information.

[0282] When the first request message is an SL BSR, in another exemplary manner, the first terminal device sends an SL BSR to the base station using a normal LCG or a normal destination address index. The SL BSR includes a destination address index or an identifier of a QoS flow. The base station allocates a first SL resource for the first terminal device based on the destination address or QoS flow associated with the second indication information and the destination address index or the identifier of the QoS flow included in the SL BSR. Specifically, when the destination address index or the identifier of the QoS flow included in the SL BSR corresponds to the destination address or QoS flow associated with the second indication information, the base station determines that the SL resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX.

[0283] When the first request message is a UAI message, after receiving the UAI message, when the QoS flow information and service mode included in the UAI message correspond to the destination address or QoS flow associated with the second indication information, the base station determines that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX, and allocates a first SL resource for the first terminal device.

[0284] S505. The base station sends information on the first SL resource to the first terminal device.

[0285] S506. The first terminal device sends first data or first signaling to the second terminal device on the first SL resource.

[0286] In this embodiment, before requesting resources from the first base station, the first terminal device sends the second indication information to the base station. The second indication information is used to indicate that the SL resources required for data or signaling corresponding to the destination address or QoS flow are SL resources corresponding to multicast or broadcast DRX, and requests the first SL resource from the base station through the first request message. The base station determines that the resources requested by the first terminal device are SL resources corresponding to multicast or broadcast DRX based on the second indication information and the first request message, so as to be able to allocate the required resources for the first terminal device.

[0287] In practical applications, the terminal device not only supports multicast or broadcast SL DRX, but also supports unicast SL DRX. Before the unicast connection is established, the terminal device may only be able to use the SL resources corresponding to multicast or broadcast SL DRX for sending or receiving, that is, the terminal device only turns on the radio frequency receiver at the time corresponding to the SL resources of multicast or broadcast SL DRX. Since the terminal device can only receive at some moments (i.e., the time corresponding to the SL resources of multicast or broadcast SL DRX), if the sending terminal device sends data at other times outside the time corresponding to the SL resources of multicast or broadcast SL DRX, and the receiving terminal device only receives at the time corresponding to the SL resources of multicast or broadcast SL DRX, it will cause message loss during the unicast connection establishment process, thus affecting the establishment of the unicast connection.

[0288] To solve the above problems, Embodiment 5 of the present application provides a sidelink communication method. Figure 9 It is a signaling flowchart of the sidelink communication method provided in Embodiment 5 of the present application. This embodiment is described from the perspective of the receiving end. As Figure 9 shown, the method provided in this embodiment includes the following steps:

[0289] S601. The terminal device deactivates the first DRX transmission at a first moment. The first DRX is multicast or broadcast SL DRX, and the first moment is the receiving moment of the SL unicast connection establishment request message or the receiving moment of the discovery request message.

[0290] In this embodiment, the terminal device can immediately deactivate the first DRX at the first moment, or can deactivate the first DRX after delaying a preset time at the first moment. The preset time for the delay can be configured by the network device.

[0291] Optionally, the first moment can also be the sending moment of the announcement message.

[0292] S602. The terminal device activates the first DRX at a second moment. The second moment is the sending moment of the SL unicast connection establishment acceptance message or the receiving moment of the first PC5 RRC reconfiguration message or the moment when the unicast connection DRX configuration is completed or the timeout moment of the first timer.

[0293] In this method, the receiving-end terminal device turns off the first DRX between the first moment and the second moment, and the receiving-end terminal device receives data during all time periods corresponding to normal SL resources. In this embodiment, after the receiving-end terminal device turns off the first DRX between the first moment and the second moment, it means that the receiving-end terminal device can receive data during all times corresponding to the resource pool between the first moment and the second moment, not limited to receiving data only on the SL resources corresponding to multicast or broadcast SL DRX.

[0294] Among them, the first moment is the receiving moment of the SL unicast connection establishment message (i.e., the first message shown in Figure 3 ) or the receiving moment of the discovery request message (such as the discovery message of solicitation). The message received at the second moment corresponds to the message received at the first moment. Correspondingly, the second moment is the sending moment of the SL unicast connection establishment acceptance message (i.e., the fourth message in Figure 3 ) or the receiving moment of the first PC5 RRC reconfiguration message or the moment when the unicast connection DRX configuration is completed or the timeout moment of the first timer.

[0295] Optionally, the first timer is started at the first moment, and the timing duration of the first timer is pre-configured or predefined. Optionally, the terminal device can also delay a certain time after the first moment and then start the first timer.

[0296] According to the values of the above first moment and second moment, the method of this embodiment is equivalent to turning off the first DRX from the start to the completion of the unicast connection establishment. That is, the receiving-end terminal device can normally receive data from the start to the completion of the unicast connection establishment, so as to ensure that all messages sent by the sending-end device during the unicast connection establishment process can be received by the receiving-end terminal device, and the messages during the unicast connection establishment process will not be lost. Multicast or broadcast SL DRX does not affect the establishment of the unicast connection.

[0297] In this embodiment, from the perspective of the receiving end, similarly, there are similar problems on the sending end. In this embodiment, the sending-end terminal device can deactivate the first DRX at the third moment and activate the first DRX at the fourth moment. That is, between the third moment and the fourth moment, the sending-end terminal device turns off the first DRX. Among them, the third moment can be the sending moment of the SL unicast connection establishment message or the sending moment of the discovery request message. Correspondingly, the fourth moment is the receiving moment of the SL unicast connection establishment acceptance message or the sending moment of the first PC5 RRC reconfiguration message or the moment when the unicast connection DRX configuration is completed or the start moment of the first timer.

[0298] Optionally, the third moment can also be the receiving moment of the announcement message.

[0299] After the unicast connection is established, there are both multicast or broadcast SL DRX and unicast SL DRX. Correspondingly, the terminal device can use the SL resources corresponding to the multicast or broadcast SL DRX to send or receive, and can also use the SL resources corresponding to the unicast connection to send or receive. In this embodiment, the terminal device can take the union of the resources corresponding to the multicast or broadcast SL DRX and the resources corresponding to the unicast SL DRX in the time domain as the time for the terminal device to send or receive data.

[0300] Figure 11 A schematic diagram for a terminal device to send data, as Figure 11 shown, part of the SL resources occupied by the first terminal device to send data (i.e., the resources shown by the slashes in the figure) is located in the SL resources corresponding to the multicast or broadcast SL DRX (i.e., the resources shown by the gray part in the figure), and the other part is outside the SL resources corresponding to the multicast or broadcast SL DRX. For example, the resources occupied by the SCI in the data sent by the first terminal device are located within the SL resources corresponding to the multicast or broadcast SL DRX, and all or part of the resources occupied by the transport block (TB) indicated by the SCI are outside the SL resources corresponding to the multicast or broadcast SL DRX. In this case, if the data sent by the first terminal device is of interest to the second terminal device and the second terminal device activates the multicast / broadcast SL DRX, the second terminal device can successfully receive the SCI on the SL resources corresponding to the multicast or broadcast SL DRX, while the TB indicated by the SCI cannot be received on the SL resources corresponding to the multicast or broadcast SL DRX. In the prior art, there is no description on how to handle this TB, which may lead to abnormal SL communication or abnormal reception of the terminal device.

[0301] To solve the above problems, this embodiment provides a sidelink communication method. Figure 12 The flowchart of the sidelink communication method provided in the sixth embodiment of this application, as Figure 12 shown, the method provided in this embodiment includes the following steps:

[0302] S701. The second terminal device receives the SCI sent by the first terminal device.

[0303] S702. When the second terminal device is in the multicast or broadcast SL DRX state, and the resources corresponding to the TB indicated by the SCI do not belong to or partially belong to the SL resources corresponding to the multicast or broadcast SL DRX, the second terminal device does not receive the TB indicated by the SCI, or the second terminal device receives the TB indicated by the SCI, but does not start the hybrid automatic repeat request round trip time (HARQ TTT) timer or the inactivity timer corresponding to the SCI.

[0304] The second terminal device being in the multicast or broadcast SL DRX state can be understood as the second terminal device currently activating the multicast or broadcast SL DRX, or the second terminal device currently using the SL resources corresponding to the multicast or broadcast SL DRX for data reception.

[0305] The HARQ TTT timer is associated with a HARQ process. When the HARQ TTT timer is running, the terminal device does not need to listen to the physical sidelink control channel (PSCCH) which is used to transmit the SCI. In the prior art, when the second terminal device receives the SCI, it will start the HARQ TTT timer and receive the TB indicated by the SCI. In this embodiment, after the second terminal device receives the SCI, it does not start the HARQ TTT timer, thus avoiding receiving the corresponding retransmitted data subsequently.

[0306] The inactivity timer is associated with a unicast connection. When the inactivity timer is running, the terminal device needs to listen to the PSCCH. In the prior art, when the second terminal device receives the SCI and the SCI indicates new transmission, it will start the inactivity timer and receive the TB indicated by the SCI. In this embodiment, after the second terminal device receives the SCI, it does not start the inactivity timer, thus avoiding receiving the corresponding retransmitted data subsequently.

[0307] In this embodiment, when the second terminal device is in the multicast or broadcast SL DRX state, and the resources corresponding to the TB indicated by the received SCI do not belong to or partially belong to the SL resources corresponding to the multicast or broadcast SL DRX, the actions of the second terminal device are specified, that is, not receiving the TB indicated by the SCI, or receiving the TB indicated by the SCI, but not starting the HARQRTT timer or the inactivity timer corresponding to the SCI, thus ensuring normal SL communication.

[0308] Figure 13 The structural schematic diagram of the first terminal device provided in the seventh embodiment of the present application is shown as Figure 13 As shown, the first terminal device 200 provided in this embodiment includes:

[0309] A determination module 21, configured to determine that first data or first signaling supports first discontinuous reception (DRX), where the first DRX is a multicast or broadcast sidelink (SL) DRX;

[0310] An acquisition module 22, configured to acquire first SL resources, where the first SL resources are the SL resources corresponding to the first DRX;

[0311] A sending module 23, configured to send the first data or the first signaling on the first SL resources.

[0312] Optionally, the determination module 21 is specifically configured to: receive first indication information from an upper layer of the first terminal device, where the first indication information is used to indicate that the first data or the first signaling supports multicast or broadcast SL DRX.

[0313] Optionally, the first indication information includes that the service or QoS flow associated with the first data supports multicast or broadcast SL DRX.

[0314] Optionally, the acquisition module 22 is specifically configured to: send a first request message to a network device, where the first request message is used to request the first SL resources, and receive the information of the first SL resources sent by the network device.

[0315] In an exemplary manner, the first request message includes second indication information, where the second indication information is used to indicate that the SL resources required by the data or signaling corresponding to the destination address or QoS flow are the SL resources corresponding to multicast or broadcast DRX.

[0316] In another exemplary manner, the acquisition module 22 is further configured to: before sending the first request message to the network device, send second indication information to the network device, where the second indication information is used to indicate that the SL resources required by the data or signaling corresponding to the destination address or QoS flow are the SL resources corresponding to multicast or broadcast DRX.

[0317] Optionally, the first request message is any one of the following messages: SL SR, SL BSR, or UAI message.

[0318] When the first request message is any one of the following messages: SL SR, SL BSR, or UAI message, optionally, the second indication information is carried in an SUI message.

[0319] Optionally, the first signaling includes one or more of the following signaling: messages in the SL unicast connection establishment process, messages in the process of discovering a relay UE, UE SL capability-related messages, or the first PC5 radio resource control (RRC) reconfiguration message.

[0320] Optionally, the obtaining module 22 is specifically configured to: obtain the first SL resource by measuring idle SL resources.

[0321] Optionally, the sending module 23 is specifically configured to: only select or preferentially select the destination address corresponding to the first data or the first signaling from the destination addresses to be transmitted as the transmission destination address. Or, only select or preferentially select the logical channel corresponding to the first data or the first signaling from the logical channels to be transmitted as the transmission logical channel.

[0322] The first terminal device 200 provided in this embodiment can be used to execute the method steps executed by the first terminal device in Embodiments 1 to 4. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0323] Figure 14 It is a schematic structural diagram of a network device provided in Embodiment 8 of this application, as Figure 14 shown. The network device 300 provided in this embodiment includes:

[0324] A receiving module 31, configured to receive a first request message sent by a first terminal device, where the first request message is used to request a first sidelink (SL) resource, the first SL resource is an SL resource corresponding to a first discontinuous reception (DRX), and the first DRX is a multicast or broadcast DRX;

[0325] An allocation module 32, configured to allocate the first SL resource to the first terminal device according to the first request message.

[0326] In an exemplary manner, the first request message includes second indication information, where the second indication information is used to indicate that the SL resource required by the data or signaling corresponding to the destination address or QoS flow is an SL resource corresponding to a multicast or broadcast DRX.

[0327] In another exemplary manner, the receiving module 31 is further configured to: before receiving the first request message, receive second indication information sent by the first terminal device, where the second indication information is used to indicate that the SL resource required by the data or signaling corresponding to the destination address or QoS flow is an SL resource corresponding to a multicast or broadcast DRX.

[0328] Optionally, the first request message is any one of the following messages: SL SR, SL BSR, or UAI message.

[0329] When the first request message is any one of the following messages: SL SR, SL BSR, or UAI message, optionally, the second indication information is carried in the sidelink user information (SUI) message.

[0330] Optionally, the first signaling includes one or more of the following signaling: messages in the SL unicast connection establishment procedure, messages in the discovery relay UE procedure, UE's SL capability-related messages, or the first PC5 radio resource control (RRC) reconfiguration message.

[0331] The network device 300 provided in this embodiment can be used to execute the method steps performed by the network device in Embodiments 1 to 4. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0332] Figure 15 FIG. is a schematic structural diagram of a second terminal device provided in Embodiment 9 of the present application. As Figure 15 shown, the second terminal device 400 provided in this embodiment includes:

[0333] A receiving module 41, which receives first indication information from the upper layer of the second terminal device. The first indication information is used to indicate that first data or first signaling supports first discontinuous reception (DRX), and the first DRX is multicast or broadcast SL DRX;

[0334] A determining module 42, configured to determine, according to the first indication information, that the data or signaling to be received currently supports the first DRX;

[0335] An activation module 43, configured to activate the first DRX.

[0336] It can be understood that the receiving module 41 and the activation module 43 can also be implemented by one module, such as a processing module, and all functions of the receiving module 41 and the activation module 43 are implemented by this processing module.

[0337] The second terminal device 400 provided in this embodiment can be used to execute the method steps performed by the second terminal device in Embodiments 1 to 4. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0338] Figure 16 FIG. is a schematic structural diagram of a second terminal device provided in Embodiment 10 of the present application. As Figure 16 shown, the second terminal device 500 provided in this embodiment includes:

[0339] The deactivation module 51 is used to deactivate the first discontinuous reception (DRX) at a first moment, where the first DRX is a multicast or broadcast sidelink (SL) DRX, and the first moment is the reception moment of the SL unicast connection establishment message or the reception moment of the discovery request message.

[0340] The activation module 52 is used to activate the first DRX at a second moment, where the second moment is the reception moment of the SL unicast connection establishment acceptance message or the reception moment of the first PC5 radio resource control (RRC) reconfiguration message or the moment when the unicast connection DRX configuration is completed or the timeout moment of the first timer.

[0341] Optionally, the terminal device starts the first timer at the first moment.

[0342] Optionally, the deactivation module 51 is specifically configured to: deactivate the first DRX after delaying a preset time at the first moment.

[0343] It can be understood that the deactivation module 51 and the activation module 52 can also be implemented by one module, such as a processing module, and the processing module implements all the functions of the deactivation module 51 and the activation module 52.

[0344] The second terminal device 500 provided in this embodiment can be used to execute the method of Embodiment 5. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0345] It can be understood that the modules in the embodiments of the present application can also be referred to as units. For example, the deactivation module can also be referred to as a deactivation unit.

[0346] The systems, devices, and methods described in the present application can also be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units / modules is only a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0347] In addition, each functional unit in the embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0348] Each of the above modules or units can be implemented by software, hardware, or a combination of software and hardware. For example, the Figure 13 determination module in the above can be implemented based on software.

[0349] In this application, "implemented by software" means that the processor reads and executes program instructions stored in the memory to implement the functions corresponding to the above-mentioned modules or units. Herein, the processor refers to a processing circuit having the function of executing program instructions, including but not limited to at least one of the following: central processing unit (CPU), microprocessor, digital signal processor (DSP), microcontroller unit (MCU), or various processing circuits such as artificial intelligence processors that can run program instructions. In some other embodiments, the processor may further include circuits with other processing functions (such as hardware circuits for hardware acceleration, bus and interface circuits, etc.). The processor may be presented in the form of an integrated chip. For example, it may be presented in the form of an integrated chip whose processing function only includes the function of executing software instructions, or it may also be presented in the form of a system on a chip (SoC). That is, on one chip, in addition to including a processing circuit that can run program instructions (usually referred to as a "core"), it also includes other hardware circuits for implementing specific functions (which can be implemented based on ASIC or FPGA). Correspondingly, in addition to the function of executing software instructions, the processing function may also include various hardware acceleration functions (such as AI computing, encoding and decoding, compression and decompression, etc.).

[0350] In this application, "implemented by hardware" means that the functions of the above-mentioned modules or units are implemented by a hardware processing circuit that does not have the function of processing program instructions. This hardware processing circuit can be composed of discrete hardware components or can be an integrated circuit. To reduce power consumption and size, the form of an integrated circuit is usually adopted for implementation. The hardware processing circuit can include an ASIC (application-specific integrated circuit) or a PLD (programmable logic device); among them, the PLD can further include an FPGA (field programmable gate array), a CPLD (complex programmable logic device), etc. These hardware processing circuits can be a separately packaged semiconductor chip or can be integrated with other circuits (such as a CPU, a DSP) and then packaged into a semiconductor chip. For example, an ASIC can be integrated with a CPU to form an SoC and be separately packaged into a chip, or an FPGA can also be integrated with a CPU to form an SoPC (system on a programmable chip).

[0351] It should be noted that when this application is implemented in a software, hardware, or software-hardware combination manner, different software and hardware can be used, and it is not limited to only using one kind of software or hardware. For example, one of the modules or units can be implemented using a CPU, and another module or unit can be implemented using a DSP. Similarly, when implemented using hardware, one of the modules or units can be implemented using an ASIC, and another module or unit can be implemented using an FPGA. Of course, it is not limited that some or all of the modules or units are implemented using the same software (such as all through a CPU) or the same hardware (such as all through an ASIC). In addition, for those skilled in the art, it can be known that software is generally more flexible but has lower performance than hardware, while hardware is just the opposite. Therefore, those skilled in the art can choose software or hardware or a combination of both according to actual needs for implementation.

[0352] Figure 17 It is a schematic structural diagram of a terminal device provided in the eleventh embodiment of this application, as Figure 17As shown, the terminal device 600 includes: a processor 61, a memory 62, and a transceiver 63. The memory 62 is used to store instructions, the transceiver 63 is used to communicate with other devices, and the processor 61 is used to execute the instructions stored in the memory, so that the terminal device 600 executes the methods performed by the first terminal device or the second terminal device in the foregoing method embodiments.

[0353] Embodiment 12 of this application provides a network device, and the structure of the network device may refer to Figure 17 As shown, the memory 62 is used to store instructions, the transceiver 63 is used to communicate with other devices, and the processor 61 is used to execute the instructions stored in the memory 62, so that the network device can execute the methods performed by the network device in the foregoing method embodiments.

[0354] In specific implementation, as an embodiment, the network device or the terminal device may include multiple processors. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). The processor may be a digital signal processor (DSP), a general-purpose microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other equivalent integrated or discrete logic circuits, etc.

[0355] The memory may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), or other types of dynamic storage devices that can store information and instructions. It may also be an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor through a communication bus. The memory may also be integrated with the processor.

[0356] Embodiment 13 of this application provides a computer-readable storage medium that stores instructions. When the instructions are executed, the computer is caused to execute the methods performed by the first terminal device or the second terminal device in the foregoing method embodiments.

[0357] Embodiment 14 of the present application provides a computer-readable storage medium storing instructions, which, when executed, cause a computer to execute the method performed by the network device in the above method embodiment.

[0358] The present application also provides a computer program product, which, when executed by a computer, implements the functions of any of the above method embodiments.

[0359] As described above, the foregoing is only an exemplary specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by those skilled in the art within the technical scope disclosed by the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A sidelink communication method, applied to a first terminal device or a chip in the first terminal device, characterized in that, including: The access stratum receives first indication information from an upper layer, where the first indication information indicates that a destination address associated with first data or a destination address associated with first signaling supports first discontinuous reception (DRX), and the first DRX is a multicast sidelink (SL) DRX or a broadcast SL DRX; obtain a first SL resource, where the first SL resource is an SL resource corresponding to the first DRX; transmit the first data or the first signaling on the first SL resource.

2. The method according to claim 1, wherein The obtaining the first SL resource includes: send a first request message to a network device, where the first request message is used to request the first SL resource; receive information about the first SL resource from the network device.

3. The method according to claim 2, wherein Before sending the first request message to the network device, it further includes: send second indication information to the network device, where the second indication information is used to indicate that an SL resource required for data or signaling corresponding to a destination address is the first SL resource.

4. The method according to claim 3, characterized in that, The first request message is any one of the following messages: an SL scheduling request (SR), an SL buffer status report (BSR), or a user assistance information (UAI) message, and the second indication information is carried in a sidelink user information (SUI) message.

5. The method according to claim 4, wherein The BSR includes a destination address index.

6. The method according to any one of claims 1-5, characterized in that, The first signaling includes one or more of the following signaling: a connection establishment request message, a notification message, a solicitation message, and a response message to the solicitation message.

7. The method according to any one of claims 1-5, characterized in that, The obtaining the first SL resource includes: obtain the first SL resource by measuring available SL resources.

8. A sidelink communication method, applied to a network device or a chip in the network device, characterized in that, including: receive second indication information from a first terminal device, where the second indication information is used to indicate that a first sidelink (SL) resource required for data or signaling corresponding to a destination address is an SL resource corresponding to a multicast DRX or a broadcast DRX; before the first terminal device sends the second indication information, determine that first data or first signaling supports first discontinuous reception (DRX) according to first indication information received by the access stratum from an upper layer, where the first indication information indicates that a destination address associated with the first data or a destination address associated with the first signaling supports first discontinuous reception (DRX); receive a first request message from the first terminal device, where the first request message is used to request the first SL resource, the first SL resource is an SL resource corresponding to the first DRX, and the first DRX is a multicast sidelink (SL) DRX or a broadcast SL DRX; allocate the first SL resource to the first terminal device according to the first request message.

9. The method according to claim 8, wherein The first request message is any one of the following messages: an SL scheduling request (SR), an SL buffer status report (BSR), or a user assistance information (UAI) message, and the second indication information is carried in a sidelink user information (SUI) message.

10. The method according to claim 9, characterized in that, The BSR includes a destination address index.

11. The method according to claim 10, wherein The method further includes: when a destination address index included in the SL BSR corresponds to a destination address associated with the second indication information, determine that the first SL resource requested by the first terminal device is an SL resource corresponding to a multicast or broadcast DRX.

12. A sidelink communication method, applied to a second terminal device or a chip in the second terminal device, characterized in that, including: The access stratum receives first indication information from an upper layer, where the first indication information indicates that the destination address associated with first data or the destination address associated with first signaling supports first discontinuous reception (DRX), and the first DRX is multicast sidelink (SL) DRX or broadcast SL DRX; When it is determined, according to the first indication information, that the data or signaling to be received currently supports the first DRX, activate the first DRX.

13. The method according to claim 12, wherein The activating the first DRX when it is determined that the data or signaling to be received currently supports the first DRX includes: When there are multiple pieces of the currently to-be-received data and / or signaling, activate the first DRX when it is determined that the destination addresses of the currently to-be-received data and / or signaling all support the first DRX.

14. A communication device, characterized in that, including: a determination module, configured to receive first indication information from an upper layer of the communication device, where the first indication information indicates that the destination address associated with first data or the destination address associated with first signaling supports first discontinuous reception (DRX), and the first DRX is multicast sidelink (SL) DRX or broadcast SL DRX; an acquisition module, configured to acquire first SL resources, where the first SL resources are SL resources corresponding to the first DRX; a transmission module, configured to transmit the first data or the first signaling on the first SL resources.

15. The device according to claim 14, characterized in that, Specifically, the acquisition module is configured to: send a first request message to a network device, where the first request message is used to request the first SL resources; receive information about the first SL resources sent by the network device.

16. The device according to claim 15, characterized in that, The acquisition module is further configured to: before sending the first request message to the network device, send second indication information to the network device, where the second indication information is used to indicate that the SL resources required for the data or signaling corresponding to the destination address are the first SL resources.

17. The device according to claim 16, characterized in that, The first request message is any one of the following messages: SL scheduling request (SR), SL buffer status report (BSR), or user assistance information (UAI) message, and the second indication information is carried in a sidelink user information (SUI) message.

18. The device according to claim 17, characterized in that, The BSR includes a destination address index.

19. The device according to any one of claims 14-18, characterized in that, The first signaling includes one or more of the following signaling: connection establishment request message, notification message, solicitation message, response message to the solicitation message.

20. The device according to any one of claims 14-18, characterized in that, Specifically, the acquisition module is configured to: obtain the first SL resources by measuring idle SL resources.

21. A communication device, characterized in that, including: a reception module, configured to receive second indication information from a first terminal device, where the second indication information is used to indicate that the first sidelink (SL) resources required for the data or signaling corresponding to the destination address are SL resources corresponding to multicast or broadcast DRX; before sending the second indication information, the first terminal device determines, according to first indication information received by the access stratum from an upper layer, that first data or first signaling supports first discontinuous reception (DRX), and the first indication information indicates that the destination address associated with first data or the destination address associated with first signaling supports first discontinuous reception (DRX); The receiving module is further configured to receive a first request message from the first terminal device, where the first request message is used to request the first SL resource, and the first SL resource is an SL resource corresponding to a first discontinuous reception DRX, and the first DRX is a multicast sidelink SL DRX or a broadcast sidelink SL DRX; The allocation module is configured to allocate the first SL resource to the first terminal device according to the first request message.

22. The device according to claim 21, characterized in that, The first request message is any one of the following messages: an SL scheduling request SR, an SL buffer status report BSR, or a user assistance information UAI message, and the second indication information is carried in a sidelink user information SUI message.

23. The device according to claim 22, wherein, The BSR includes a destination address index.

24. The device according to claim 23, characterized in that, When the destination address index included in the SL BSR corresponds to the destination address associated with the second indication information, The communication device is configured to: determine that the first SL resource requested by the first terminal device is an SL resource corresponding to a multicast or broadcast DRX.

25. A communication device, characterized in that, including: The receiving module receives first indication information from the upper layer of the communication device, where the first indication information indicates that the destination address associated with the first data or the destination address associated with the first signaling supports a first discontinuous reception DRX, and the first DRX is a multicast sidelink SL DRX or a broadcast sidelink SL DRX; The determining module is configured to determine, according to the first indication information, that the data or signaling to be received currently supports the first DRX; The activation module is configured to activate the first DRX.

26. The device according to claim 25, wherein, The determining module is specifically configured to: When there are multiple pieces of data and / or signaling to be received currently, Activate the first DRX when it is determined that the destination addresses of the data and / or signaling to be received currently all support the first DRX.

27. A communication device, characterized in that, including a processor, a memory, and a transceiver, where the memory is used to store instructions, the transceiver is used to communicate with other devices, and the processor is used to execute the instructions stored in the memory, so that the communication device executes the method according to any one of claims 1-7, or any one of claims 12-13.

28. A network device, characterized in that, including a processor, a memory, and a transceiver, where the memory is used to store instructions, the transceiver is used to communicate with other devices, and the processor is used to execute the instructions stored in the memory, so that the network device executes the method according to any one of claims 8-11.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions, and when the instructions are executed, the computer is caused to execute the method according to any one of claims 1-13.

30. A computer program product, characterized in that, The computer program product includes instructions, and when the instructions are executed, the computer is caused to execute the method according to any one of claims 1-13.

31. A communication system, characterized in that, including: A first terminal device, a second terminal device, and a network device, where the first terminal device is configured to execute the method according to any one of claims 1-7, the second terminal device is configured to execute the method according to any one of claims 12-13, and the network device is configured to execute the method according to any one of claims 8-11.

Images