Communication method and communication device

CN118985174APending Publication Date: 2024-11-19GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280087613.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-24
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

When the network does not support the sidelink SL DRX function, the terminal equipment cannot perform SL communication based on the DRX mechanism, resulting in communication failure and affecting communication efficiency.

Method used

The terminal device performs SL communication based on the DRX mechanism or non-DRX mechanism according to the configuration of the network device where it is located, to avoid mismatch between the network configuration and the SL DRX configuration.

Benefits of technology

SL communication is performed through the terminal device according to the network configuration, which avoids communication failures, improves communication efficiency, and ensures the normal transmission of SL data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985174A_ABST
    Figure CN118985174A_ABST
Patent Text Reader

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: first terminal equipment acquires configuration of first network equipment; and the first terminal device sends SL data in a discontinuous reception (DRX) mode or a non-DRX mode based on the configuration of the first network device. In the embodiment of the invention, the terminal equipment performs SL communication based on the DRX mechanism according to the configuration of the network equipment where the terminal equipment is located, so that the condition of communication failure caused by mismatching of the network configuration and the SL DRX configuration can be avoided, and the communication efficiency can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] With the development of communication technology, some communication systems have introduced the discontinuous reception (DRX) mechanism to reduce the power consumption of terminal devices. However, if the network does not support the sidelink (SL) DRX function, it is currently unclear how the terminal device can perform SL transmission based on the DRX mechanism.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.

[0005] In a first aspect, a communication method is provided, including: a first terminal device obtains a configuration of a first network device; the first terminal device sends side link SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the first network device.

[0006] According to a second aspect, a communication method is provided, including: a second terminal device obtains a configuration of a second network device; and the second terminal device receives side link SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the second network device.

[0007] According to a third aspect, a communication device is provided, including: an acquisition unit for acquiring the configuration of a first network device; and a sending unit for sending side link SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the first network device.

[0008] In a fourth aspect, a communication device is provided, including: an acquisition unit for acquiring the configuration of a second network device; a receiving unit for receiving side link SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the second network device.

[0009] In a fifth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory to execute the method described in the first aspect.

[0010] In the sixth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory to execute the method described in the second aspect.

[0011] In a seventh aspect, a communication device is provided, comprising a processor configured to call a program from a memory to execute the method described in the first aspect.

[0012] In an eighth aspect, a communication device is provided, comprising a processor for calling a program from a memory to execute the method described in the second aspect.

[0013] In a ninth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.

[0014] In a tenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the second aspect.

[0015] In an eleventh aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect.

[0016] In a twelfth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the second aspect.

[0017] In a thirteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the first aspect.

[0018] In a fourteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the second aspect.

[0019] In a fifteenth aspect, a computer program is provided, which enables a computer to execute the method described in the first aspect.

[0020] In a sixteenth aspect, a computer program is provided, which enables a computer to execute the method described in the second aspect.

[0021] In an embodiment of the present application, the terminal device performs SL communication based on the DRX mechanism according to the configuration of the network device in which it is located, which can avoid communication failure caused by mismatch between the network configuration and the SL DRX configuration, thereby improving communication efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.

[0023] FIG2 is an exemplary diagram of a wireless communication system according to another embodiment of the present application.

[0024] FIG3 is an exemplary diagram of a wireless communication system applied in yet another embodiment of the present application.

[0025] FIG4 is an exemplary diagram of a wireless communication system applied in yet another embodiment of the present application.

[0026] FIG5 is an example diagram of a cache status report in an embodiment of the present application.

[0027] FIG6 is a schematic flowchart of a communication method provided in one embodiment of the present application.

[0028] FIG7 is a schematic flowchart of a communication method provided in another embodiment of the present application.

[0029] FIG8 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0030] FIG9 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0031] FIG10 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0032] FIG11 is a schematic structural diagram of a communication device provided in one embodiment of the present application.

[0033] FIG12 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0034] FIG13 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solution in this application will be described below with reference to the accompanying drawings.

[0036] Figure 1 illustrates the architecture of a wireless communication system 100 applicable to embodiments of the present application. The architecture shown in Figure 1 includes a network device 110 and a terminal device 120. Network device 110 can be a device that communicates with terminal device 120. Network device 110 provides communication coverage for a specific geographic area and can communicate with terminal device 120 within that coverage area.

[0037] It should be noted that FIG1 exemplarily shows a network device and a terminal device. Optionally, the communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area. This is not limited in this embodiment of the present application. In addition, in some implementations, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in this embodiment of the present application.

[0038] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), cellular Internet of Things, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, etc. The technical solutions provided in this application can also be applied to other communication systems, such as wireless fidelity (Wi-Fi) system, vehicle to everything (V2X) system, Internet of Things (IoT) system, local area network, etc.

[0039] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as handheld devices with wireless connection functions, vehicle-mounted devices, household appliances, sensors, electronic tags, etc. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The terminal device in the embodiment of the present application can be a zero-power terminal, or a terminal device that can support backscatter communication.

[0040] The network device in the embodiment of the present application may be a device for communicating with a terminal device. If the terminal device is an electronic tag, the network device may be a reader / writer for reading and writing the electronic tag (for example, a reader / writer based on radio frequency identification (RFID) technology). The network device may also be an access network device or a wireless access network device, such as a base station. The network device in the embodiment of the present application may refer to a radio access network (RAN) node (or device) that connects the terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, and a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form adopted by the network equipment.

[0041] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0042] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0043] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0044] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0045] With the development of communication technology, some communication systems have introduced sidelink (SL) transmission technology to improve transmission efficiency. The following describes the SL transmission technology with reference to Figures 2 to 4.

[0046] Device-to-device (D2D) communication is a sidelink transmission technology. Unlike traditional cellular systems, where communication data is transmitted through base stations, D2D communication uses direct end-to-end communication, resulting in higher spectrum efficiency and lower transmission latency. D2D communication can be applied to connected vehicle systems.

[0047] The 3rd Generation Partnership Project (3GPP) defines two resource acquisition methods for D2D: Mode A and Mode B. The details are as follows:

[0048] Mode A: The transmission resources of the terminal device are allocated by the base station, and the terminal device can transmit data on the sidelink based on the resources allocated by the base station. The base station can allocate transmission resources for a single transmission to the terminal device, or it can allocate semi-static transmission resources to the terminal device. For example, as shown in Figure 1, terminal devices 220 and 230 are both within the network coverage of network device 210, can receive the transmission resources allocated by network device 210, and can conduct sidelink communication based on the transmission resources.

[0049] Mode B: The terminal device can select resources from the resource pool for sideways transmission. For example, as shown in Figure 2, terminal devices 320 and 330 can select resources from the resource pool and perform sideways communication based on the transmission resources. It should be noted that Figure 3 shows the situation where both terminal devices 320 and 330 are within the network coverage of network device 310. Of course, at least one of terminal devices 320 and 330 may also be outside the network coverage of network device 310, and this application does not limit this.

[0050] In 3GPP, D2D is divided into the following different stages for research.

[0051] (1) Proximity-based service (ProSe): In some versions of the communication protocol (e.g., R12 and R13), ProSe scenarios have been studied, primarily for public safety services. In ProSe, by configuring the location of resource pools in the time domain (e.g., resources in the resource pool are non-contiguous in the time domain), the terminal device can enable discontinuous transmission or reception of data on the sidelink, thereby achieving power saving.

[0052] (2) Vehicle to Everything (V2X): In some versions of the communication protocol (e.g., R14 and R15), research has been conducted on the V2X scenario for vehicle-to-vehicle communication, which is mainly aimed at relatively high-speed vehicle-to-vehicle and vehicle-to-person communication services. In V2X, since the vehicle system has a continuous power supply, data transmission latency is the main issue compared to power and efficiency. Therefore, the system design requires terminal devices to perform continuous transmission and reception.

[0053] (3) Wearable devices (further enhancement device-to-device (FeD2D)): In some versions of the communication protocol (e.g., R14), research was conducted on scenarios where wearable devices access the network through mobile phones, primarily targeting low-speed and low-power access scenarios. In FeD2D, the preliminary research phase concluded that the base station can configure the DRX parameters of remote terminal devices through a relay terminal device. However, because this topic did not enter the standardization stage, the specific details of how to perform DRX configuration have not been determined.

[0054] In NR, V2X, based on LTE V2X, is no longer limited to broadcast scenarios, but has been further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.

[0055] Similar to LTE V2X, NR V2X also defines two resource acquisition methods: Mode 1 and Mode 2. Mode 1 is similar to Mode A, and Mode 2 is similar to Mode B. Furthermore, in NR, terminal devices can be in a hybrid mode, that is, the terminal device can use Mode 1 to acquire resources, and Mode 2 to acquire resources at the same time.

[0056] Unlike LTE V2X, in addition to the non-feedback, terminal-initiated hybrid automatic repeat request (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication but also includes multicast communication.

[0057] Furthermore, similar to LTE V2X, in NR V2X, since the on-board system has continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue. Therefore, the system design requires terminal devices to perform continuous transmission and reception.

[0058] In NR V2X, the resource allocation method based on network scheduling (such as Mode 1) can be divided into dynamic grant and configured grant (CG).

[0059] For configuration authorization, NR-V2X draws on the configuration authorization mechanism in LTE and introduces sidelink configuration authorization. When a terminal device is configured with a sidelink configuration authorization transmission resource, when sidelink data arrives, the terminal can use the sidelink configuration authorization transmission resource to transmit the sidelink data without having to reapply for transmission resources from the network device. Therefore, the sidelink configuration authorization transmission resource can reduce the latency of sidelink transmission. The sidelink configuration authorization transmission resource can be a periodic transmission resource and is therefore suitable for the transmission of periodic sidelink data. Of course, the sidelink configuration authorization transmission resource can also be used to transmit non-periodic sidelink data.

[0060] For dynamic authorization, the network device can allocate sidelink transmission resources to the terminal device through downlink control information (DCI). For example, as shown in Figure 4, when terminal device 420 has sidelink data to send, it can send a resource request to network device 410. Network device 410 can allocate sidelink transmission resources to terminal device 420 based on the resource request. Terminal device 420 can then perform sidelink communication with terminal device 430 using the sidelink transmission resources allocated by network device 410.

[0061] Resource requests may include scheduling requests (SR) and buffer status reports (BSR), wherein the format of the sidelink BSR may be as shown in FIG5 , and the sidelink BSR includes 2N bytes, which carry N target address indexes, N logical channel group identifiers, and N buffers, where N is a positive integer. For example, the terminal device may first send a scheduling request (SR or random access) to the network device, and then send a sidelink BSR; based on the sidelink BSR, the network device may determine that the terminal device has data to be transmitted on the sidelink, and estimate the resources required to transmit the data; further, the network device may use the configured radio network temporary identifier (RNTI) for the sidelink to schedule transmission resources for sidelink communications. The RNTI for the sidelink may be carried in the DCI.

[0062] The sidelink BSR can be triggered by the following trigger conditions:

[0063] (1) New data to be transmitted appears in the radio link control (RLC) layer entity or the packet data convergence protocol (PDCP) layer entity (if there is other data to be transmitted, the priority of the new data is higher than the priority of any logical channel group to be transmitted with the same destination address, or there is no other data to be transmitted with the same destination address);

[0064] (2) After allocating resource grant space for data and triggering the fill BSR for the uplink channel, the number of remaining bits is equal to or greater than the size of the sidelink BSR (including buffer information of at least one logical channel group for at least one target address);

[0065] (3) The retransmission timer of the sidelink BSR expires and the media access control (MAC) layer entity has data available for sidelink transmission;

[0066] (4) The periodic timer of the sidelink BSR expires;

[0067] (5) Sidelink BSR can also be triggered when the terminal device is configured from autonomous resource selection mode to network scheduled resource selection mode.

[0068] Some communication systems introduce a discontinuous reception (DRX) mechanism, which allows the UE to enter a discontinuous reception state instead of turning on the receiver all the time when there is no data to receive, thereby saving power.

[0069] For example, the terminal device can discontinuously monitor the PDCCH according to the DRX configuration. When the PDCCH carries the RNTI of a specific format corresponding to the terminal device (for example, C-RNTI, CI-RNTI, CS-RNTI, INT-RNTI, SFI-RNTI, SP-CSI-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI and AI-RNTI), the terminal device can perform corresponding DRX operations according to the control information.

[0070] The network device can control the terminal device to perform different DRX operations by configuring different parameters. For example, these parameters may include: drx-onDurationTimer, drx-SlotOffset, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, ps-Wakeup (optional), ps-TransmitOtherPeriodicCSI (optional), ps-TransmitPeriodicL1-RSRP (optional).

[0071] For example, a terminal device may be in the DRX active state in the following situations:

[0072] (1) During the execution of drx-onDurationTimer or drx-InactivityTimer;

[0073] (2) During the operation of drx-RetransmissionTimerDL or drx-RetransmissionTimerUL;

[0074] (3) During the operation of ra-ContentionResolutionTimer or msgB-ResponseWindow;

[0075] (4) There are unprocessed SRs;

[0076] (5) PDCCH indicates that there is a new transmission period.

[0077] In sidelink communications, when a terminal device is in Mode 1 resource acquisition mode, the terminal device's sidelink transmission resources are configured by the network device. If the network does not support SL DRX functionality, a mismatch between the network-configured sidelink transmission resources and the SL DRX configuration may occur. In this case, the terminal device cannot perform SL DRX (i.e., SL communication based on the DRX mechanism). It is currently unclear what actions the terminal device performs in this situation.

[0078] To address one or more of the above technical issues, the present application proposes a communication method and a communication apparatus. A terminal device performs SL communication based on the DRX mechanism according to the configuration of the network device in which it is located, thereby avoiding communication failures caused by a mismatch between the network configuration and the SL DRX configuration, thereby improving communication efficiency.

[0079] The embodiments of the present application are described in detail below with reference to FIG6 to FIG10 .

[0080] FIG6 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 600 shown in FIG6 may include steps S610 and S620, which are as follows:

[0081] S610: The first terminal device obtains the configuration of the first network device.

[0082] The configuration of the first network device may refer to sidelink configuration information sent by the first network device (eg, SL DRX configuration information of the first network device).

[0083] The first terminal device may be in the coverage of the first network device. The first terminal device may be in mode 1.

[0084] Optionally, the first terminal device may receive a configuration of the first network device sent by the first network device. For example, the first terminal device may receive first information sent by the first network device. The first information may be used to carry the configuration of the first network device. For example, the first information may be a system message configuration (such as a system information block (SIB)) and / or a proprietary signaling configuration.

[0085] Alternatively, the first terminal device may also read pre-configuration information that has been pre-written (stored) in the first terminal device, and the pre-configuration information may include the configuration of the first network device.

[0086] Alternatively, the first terminal device may also receive pre-configuration information from other network devices or servers. Optionally, the first network device may be located in an access stratum (AS), and the other network devices or servers may refer to high-layer network devices located above the access stratum.

[0087] Optionally, if the first information does not include SL DRX configuration information of the first network device, the first terminal device may determine that the first network device does not support SL DRX. If the first information includes SL DRX configuration information of the first network device, the first terminal device may determine that the first network device supports SL DRX.

[0088] Of course, the first information may also directly indicate whether the first network device supports SL DRX.

[0089] S620, the first terminal device sends SL data in a DRX manner or in a non-DRX manner based on the configuration of the first network device.

[0090] The SL data may be unicast data, multicast data or broadcast data.

[0091] In S620, the first terminal device may determine whether the first network device supports SL DRX (or whether SL DRX is configured) based on the configuration of the first network device. For example, if the configuration of the first network device does not include relevant configuration information of SL DRX, the first terminal device may determine that the first network device does not support SL DRX; if the configuration of the first network device includes relevant configuration information of SL DRX, the first terminal device may determine that the first network device supports SL DRX.

[0092] The first terminal device may also determine whether the first network device supports SL DRX based on the indication of the first network device. For example, the first terminal device may receive first information, and the first information may indicate that the first network device does not support SL DRX.

[0093] The first terminal device can determine whether to send SL data in DRX mode or in non-DRX mode according to whether the first network device supports SL DRX.

[0094] In some possible implementations, if the first network device does not support SL DRX (or is not configured with SL DRX), the first terminal device may send SL data in a non-DRX manner based on the configuration of the first network device.

[0095] For example, if the first network device does not support SL DRX, the first terminal device may, based on the configuration of the first network device, send data corresponding to a service or layer 2 identifier (L2ID) that supports DRX transmission in a non-DRX manner. Alternatively, if the first network device does not support SL DRX, the first terminal device may not send data corresponding to a service or layer 2 identifier (L2ID) that supports DRX transmission.

[0096] The data corresponding to the service or layer 2 identifier supported for transmission in the DRX mode may refer to the data corresponding to the service or layer 2 identifier supported for transmission in the DRX mode indicated by a transmission profile (Tx-profile). The transmission profile may refer to data sent by a non-access stratum (NAS) layer. Each service type (data flow) of the service may correspond to a transmission profile, and the transmission profile may indicate whether the data corresponding to the service or layer 2 identifier supported for transmission in the DRX mode is sent in the DRX mode.

[0097] Alternatively, the first terminal device may also determine whether to send the service supported by DRX or the data corresponding to the layer 2 identifier in DRX mode or in non-DRX mode based on the sending configuration file. For example, if the sending configuration file indicates that the data corresponding to the layer 2 identifier is to be sent in DRX mode, the first terminal device may send the data corresponding to the layer 2 identifier in DRX mode.

[0098] Alternatively, if the first network device does not support SL DRX, the first terminal device may not send data corresponding to the service or layer 2 identifier that supports DRX transmission.

[0099] In some possible implementations, if the first network device supports SL DRX (or is configured with SL DRX), the first terminal device can send SL data in a DRX manner based on the configuration of the first network device.

[0100] It should be noted that method 600 in Figure 6 takes the first terminal device as the sending end as an example to describe the solution in the embodiment of the present application. The first terminal device can also be used as a receiving end to receive data sent by other terminal devices. This is not limited in the embodiment of the present application.

[0101] In an embodiment of the present application, the terminal device performs SL communication based on the DRX mechanism according to the configuration of the network device in which it is located, which can avoid communication failure caused by mismatch between the network configuration and the SL DRX configuration, thereby improving communication efficiency.

[0102] FIG7 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 700 shown in FIG7 may include steps S710 and S720, which are as follows:

[0103] S710: The second terminal device obtains the configuration of the second network device.

[0104] The configuration of the second network device may refer to sidelink configuration information sent by the second network device (eg, SL DRX configuration information of the first network device).

[0105] The second terminal device may be in the coverage of the second network device. The second terminal device may be in mode 1.

[0106] Optionally, the second terminal device may receive the configuration of the second network device sent by the second network device. For example, the second terminal device may receive fifth information sent by the second network device. The fifth information may be used to carry the configuration of the second network device. For example, the fifth information may include system message configuration and / or proprietary signaling configuration.

[0107] Alternatively, the second terminal device may also read pre-configuration information that has been pre-written (stored) in the second terminal device, where the pre-configuration information may include the configuration of the second network device.

[0108] Alternatively, the second terminal device may also receive the preconfiguration information from other network devices or servers. Optionally, the second network device may be located at an access layer, and the other network devices or servers may refer to high-layer network devices located above the access layer.

[0109] Optionally, if the fifth information does not include SL DRX configuration information of the second network device, the second terminal device may determine that the second network device does not support SL DRX. If the fifth information includes SL DRX configuration information of the second network device, the second terminal device may determine that the second network device supports SL DRX.

[0110] Of course, the fifth information may also directly indicate whether the fifth network device supports SL DRX.

[0111] S720, the second terminal device receives SL data in a DRX manner or in a non-DRX manner based on the configuration of the second network device.

[0112] The SL data may be unicast data, multicast data or broadcast data.

[0113] In S720, the second terminal device may determine whether the second network device supports SL DRX (or whether SL DRX is configured) based on the configuration of the second network device. For example, if the configuration of the second network device does not include relevant configuration information of SL DRX, the second terminal device may determine that the second network device does not support SL DRX; if the configuration of the second network device includes relevant configuration information of SL DRX, the second terminal device may determine that the second network device supports SL DRX.

[0114] The second terminal device may also determine whether the second network device supports SL DRX based on the indication of the second network device. For example, the second terminal device may receive fifth information, and the fifth information may indicate that the second network device does not support SL DRX.

[0115] The second terminal device can determine whether to receive SL data in DRX mode or in non-DRX mode according to whether the second network device supports SL DRX.

[0116] In some possible implementations, if the second network device does not support SL DRX (or is not configured with SL DRX), the second terminal device may receive SL data in a non-DRX manner based on the configuration of the second network device.

[0117] For example, if the second network device does not support SL DRX, the second terminal device may receive the service or data corresponding to the layer 2 identifier sent in DRX mode in a non-DRX manner based on the configuration of the second network device. Alternatively, if the second network device does not support SL DRX, the second terminal device may not receive the service or data corresponding to the layer 2 identifier sent in DRX mode.

[0118] Alternatively, the second terminal device may also determine whether to receive the service or data corresponding to the layer 2 identifier that supports DRX transmission in a DRX manner or in a non-DRX manner based on the transmission profile. For example, if the transmission profile indicates that the data corresponding to the layer 2 identifier is sent (or received) in a DRX manner, the second terminal device may receive the data corresponding to the layer 2 identifier in a DRX manner.

[0119] In some possible implementations, if the second network device supports SL DRX (or is configured with SL DRX), the second terminal device can receive SL data in a DRX manner based on the configuration of the second network device.

[0120] It should be noted that method 700 in Figure 7 takes the second terminal device as the receiving end as an example to describe the solution in the embodiment of the present application. The second terminal device can also be used as a sending end to send data to other terminal devices, which is not limited in the embodiment of the present application.

[0121] In an embodiment of the present application, the terminal device performs SL communication based on the DRX mechanism according to the configuration of the network device in which it is located, which can avoid communication failure caused by mismatch between the network configuration and the SL DRX configuration, thereby improving communication efficiency.

[0122] The method in the embodiment of the present application is further described below in conjunction with Figures 8 to 10. In the following embodiments, it can be assumed that the network configurations of the terminal devices of the sender and the receiver are the same, or the SL DRX configurations in the network where the terminal devices of the sender and the receiver are located are aligned, that is, the configurations (for example, pre-configuration / system message configuration / proprietary signaling configuration) received by the terminal devices of the sender and the receiver from the network device are configurations that both include SL DRX (support SL DRX) or configurations that do not include SL DRX (do not support SL DRX). In the following embodiments, the sending UE can be the first terminal device in the above embodiment, network device 1 can be the first network device in the above embodiment, the receiving UE can be the second terminal device in the above embodiment, and network device 2 can be the second network device in the above embodiment.

[0123] In some possible implementations, if the network does not support SL DRX (SL DRX is not configured), the UEs of both the sender and receiver may not use the SL DRX communication mode according to the network configuration.

[0124] FIG8 is a schematic flow chart of a communication method according to an embodiment of the present application. As shown in FIG8 , the sending UE is within the coverage of network device 1 , and the receiving UE is within the coverage of network device 2 .

[0125] Network device 1 and network device 2 may be the same network device, that is, the sending UE and the receiving UE may be located within the coverage of the same network device.

[0126] As shown in Figure 8, network device 1 and network device 2 may not support SL DRX. The sending UE and the receiving UE can transmit SL data in a non-DRX manner, but cannot transmit SL data in a DRX manner (or, in other words, cannot perform SL DRX transmission).

[0127] The sending UE may obtain the configuration of network device 1 and determine that there is no SL DRX related configuration in the configuration of network device 1, that is, determine that network device 1 does not support SL DRX. For example, the sending UE may receive pre-configuration, system message configuration, and proprietary signaling configuration sent by network device 1.

[0128] In the case that the network device 1 does not support SL DRX, the sending UE may send SL data in a non-DRX manner. The SL data may include unicast data, multicast data, and / or broadcast data.

[0129] For example, the sending UE may send the service or data corresponding to the L2ID indicated by the Tx-profile in DRX mode in non-DRX mode. Alternatively, the sending UE may not send the service or data corresponding to the L2ID indicated by the Tx-profile in DRX mode.

[0130] Accordingly, the receiving UE can obtain the configuration of network device 1 and determine that there is no SL DRX-related configuration in the configuration of network device 2, that is, it is determined that network device 2 does not support SL DRX. For example, the receiving UE can receive the pre-configuration, system message configuration, and proprietary signaling configuration sent by network device 2.

[0131] If network device 2 does not support SL DRX, the receiving UE may receive SL data in a non-DRX mode. The SL data may include unicast data, multicast data, and / or broadcast data. For example, the receiving UE may receive the service indicated by the Tx-profile as being sent in a DRX mode or the data corresponding to the L2ID in a non-DRX mode. Alternatively, the receiving UE may not receive the service indicated by the Tx-profile as being sent in a DRX mode or the data corresponding to the L2ID.

[0132] In some possible implementations, if the network does not support SL DRX (SL DRX is not configured), the UEs of both the sender and receiver can perform multicast / broadcast communication without using the SL DRX communication mode according to the network configuration, and the sending UE can independently decide whether to perform unicast communication using the SL DRX communication mode.

[0133] Figure 9 is a schematic flow chart of a communication method according to an embodiment of the present application. As shown in Figure 9, a transmitting UE is within the coverage of network device 1, and a receiving UE is within the coverage of network device 2. Network device 1 and network device 2 can be the same network device. Network device 1 and network device 2 may not both support SL DRX.

[0134] The method 900 shown in FIG9 may include steps S910 to S950, which are specifically as follows:

[0135] S910: The sending UE sends a unicast connection request (DCR) message. Correspondingly, the receiving UE receives the unicast connection request message.

[0136] Optionally, the sending UE may send a unicast connection request (DCR) message in a non-DRX mode. Optionally, the receiving UE may receive the unicast connection request message in a non-DRX mode.

[0137] Optionally, if network device 1 does not support SL DRX, the sending UE may send a unicast connection establishment request message in a non-DRX mode based on the configuration of network device 1. Correspondingly, if network device 2 does not support SL DRX, the receiving UE may receive a unicast connection establishment request message in a non-DRX mode based on the configuration of network device 2.

[0138] Alternatively, if network device 1 does not support SL DRX, and the sending UE is pre-configured with a default DRX mode, and the sending configuration file indicates that the unicast connection establishment request message is DRX-compatible, the sending UE may send the unicast connection establishment request message in the default DRX mode. Correspondingly, if network device 2 does not support SL DRX, and the receiving UE is pre-configured with a default DRX mode, and the sending configuration file indicates that the unicast connection establishment request message is DRX-compatible, the receiving UE may receive the unicast connection establishment request message in the default DRX mode.

[0139] Alternatively, if network device 1 does not support SL DRX, the sending UE is pre-configured with a default DRX mode, and the sending profile indicates that the unicast connection establishment request message is DRX-compatible, the sending UE may send the unicast connection establishment request message in the default DRX mode. Correspondingly, if network device 2 does not support SL DRX, the receiving UE may receive the unicast connection establishment request message in a non-DRX mode.

[0140] It should be noted that the default DRX mode may refer to performing DRX transmission using a DRX configuration pre-configured in the terminal device (ie, the default DRX configuration).

[0141] Sending a configuration file to indicate that the unicast connection establishment request information is DRX compatible (DRX capable) may mean: sending a configuration file to indicate that the unicast connection establishment request information supports DRX.

[0142] The receiving UE may determine a response mode for the unicast connection establishment request message according to a sending profile corresponding to the unicast connection establishment request message.

[0143] Optionally, if the sending profile corresponding to the unicast connection establishment request message indicates support for SL DRX, then in response to the unicast connection establishment request message, the receiving UE can perform at least one of the following operations: sending a unicast connection establishment accept (DCA) message to the sending UE, not replying to the DCA message, sending a DCA message to the sending UE, receiving SL data in DRX mode, or receiving SL data in non-DRX mode.

[0144] For example, if the network device 2 does not support SL DRX, the receiving UE may perform the following S920: the receiving UE sends a unicast connection establishment accept (DCA) message. Correspondingly, the sending UE receives the unicast connection establishment accept message.

[0145] For example, the receiving UE may send a unicast connection establishment accept (DCA) message in a non-DRX mode. Correspondingly, the sending UE may receive the unicast connection establishment accept message in a non-DRX mode.

[0146] S930: The sending UE sends the second information. Correspondingly, the receiving UE receives the second information.

[0147] Optionally, the second information may be used to indicate the user capabilities of the sending UE. For example, the second information may be capability interaction information. Optionally, the capability interaction information may be defined in a communication protocol. Capability interaction may be performed between SL UEs.

[0148] The sending UE may determine the user capabilities of the sending UE as a PC5 UE based on the SL DRX capabilities of the network device 1 and / or the SL DRX capabilities of the sending UE. Alternatively, the sending UE may determine the user capabilities based on the network configuration, the resource acquisition mode (of the sending UE), and whether the (sending UE) is within the network coverage.

[0149] For example, if the network device 1 supports SL DRX and supports SL DRX, the sending UE may determine that the user capability is supporting SL DRX.

[0150] For another example, if the network device 1 does not support SL DRX and the sending UE supports SL DRX, the sending UE determines that the user capability is to support SL DRX.

[0151] For another example, if the network device 1 does not support SL DRX, the sending UE supports SL DRX, and the sending UE is in an idle state, an inactive state, or out of coverage (OOC), the sending UE can determine that the user capability supports SL DRX.

[0152] For another example, if the network device 1 does not support SL DRX, the sending UE supports SL DRX, the sending UE is in a connected state, and the resource acquisition mode of the sending UE is configured as mode 2, the sending UE may determine that the user capability is to support SL DRX.

[0153] Optionally, in other cases, the sending UE may determine that the user capability does not support SL DRX.

[0154] After receiving the second information, the receiving UE can determine whether to disconnect the PC5 connection between it and the sending UE based on the second information. In the case of disconnecting the PC5 connection, the receiving UE can send an instruction message to the upper layer (e.g., the NAS layer of the receiving UE) to instruct the disconnection of the PC5 connection (between it and the sending UE). Alternatively, the receiving UE can define a new PC5-S signaling disconnection cause value or reuse an existing PC5-S signaling disconnection cause value. The disconnection cause value can refer to a cause value in the NAS layer protocol, and the receiving UE can also reuse the cause value in the protocol, or define a new cause value.

[0155] The receiving UE may determine whether to send SL DRX assistance information to the transmitting UE based on the second information. Optionally, the SL DRX assistance information may be defined in a communication protocol. The SL DRX assistance information may be used by the receiving UE to indicate its desired SL DRX configuration to the transmitting UE.

[0156] For example, if the second information indicates that the user capability of the sending UE as a PC5 UE is not to support SL DRX, the receiving UE may not send SL DRX assistance information to the sending UE.

[0157] For another example, if the second information indicates that the user capability of the sending UE as a PC5 UE is to support SL DRX, S940 may be executed, that is, the receiving UE sends the SL DRX assistance information, and correspondingly, the sending UE receives the SL DRX assistance information.

[0158] S950: The sending UE sends third information. Correspondingly, the receiving UE receives the third information.

[0159] Optionally, the transmitting UE may send the third information to the receiving UE under the first condition. For example, if the transmitting UE receives the SL DRX assistance information sent by the transmitting UE under the first condition, the third information may be sent to the receiving UE.

[0160] The first condition may include at least one of the following: the sending UE does not support SL DRX, the sending UE is in a connected state, and the resource acquisition method of the sending UE is configured as mode 1.

[0161] The third information may indicate at least one of the following: the sending UE does not support SL DRX, the sending UE cannot configure SL DRX, whether the sending UE supports SL DRX, whether the sending UE is configured with SL DRX, whether the sending UE is in mode 1, whether the sending UE is in a connected state, whether the network device 1 supports SL DRX, whether the network device 1 is / configures SL DRX, and the sidelink configuration information does not contain SL DRX configuration.

[0162] The third information may be carried in PC5-radio resource control (RRC) signaling, media access control layer control element (MAC CE) signaling or physical layer signaling.

[0163] Optionally, the content of the third information is determined by the sending UE based on the configuration of the network device 1. For example, if the configuration of the network device 1 does not include the SL DRX configuration, the sending UE may configure the sidelink configuration information not to include the SL DRX configuration. Further, the sending UE may determine that the third information indicates that the sidelink configuration information does not include the SL DRX configuration.

[0164] After receiving the third information, the receiving UE can determine whether to disconnect the PC5 connection between it and the sending UE based on the third information. In the case of disconnecting the PC5 connection, the receiving UE can send an instruction to disconnect the PC5 connection (between it and the sending UE) to an upper layer (e.g., the receiving UE's NAS layer). Alternatively, the receiving UE can define a new PC5-S signaling disconnection cause value or reuse an existing PC5-S signaling disconnection cause value.

[0165] It should be noted that the method 900 in FIG. 9 is merely an example and not a limitation. Not all steps need to be performed, or these steps may be performed in another order, which is not limited in the embodiments of the present application.

[0166] In some possible implementations, if the network does not support SL DRX (SL DRX is not configured), the sending and receiving UEs may not use the SL DRX communication mode for multicast / broadcast communication according to the network configuration, and the receiving UE may independently decide whether to use the SL DRX communication mode for unicast communication.

[0167] Figure 10 is a schematic flow chart of a communication method according to an embodiment of the present application. As shown in Figure 10 , a transmitting UE is within the coverage of network device 1, and a receiving UE is within the coverage of network device 2. Network device 1 and network device 2 may be the same network device. Neither network device 1 nor network device 2 may support SL DRX.

[0168] The method 1000 shown in FIG10 may include steps S1010 and S1020, which are specifically as follows:

[0169] S1010: A sending UE sends a unicast connection request (DCR) message, and a receiving UE receives the unicast connection request message.

[0170] Optionally, the sending UE may send a unicast connection request (DCR) message in a non-DRX mode, and correspondingly, the receiving UE may receive the unicast connection request message in a non-DRX mode.

[0171] Optionally, if network device 1 does not support SL DRX, the sending UE may send a unicast connection establishment request message in a non-DRX mode based on the configuration of network device 1. Correspondingly, if network device 2 does not support SL DRX, the receiving UE may receive a unicast connection establishment request message in a non-DRX mode based on the configuration of network device 2.

[0172] Alternatively, if network device 1 does not support SL DRX, and the sending UE is pre-configured with a default DRX mode, and the sending configuration file indicates that the unicast connection establishment request message is DRX-compatible, the sending UE may send the unicast connection establishment request message in the default DRX mode. Correspondingly, if network device 2 does not support SL DRX, and the receiving UE is pre-configured with a default DRX mode, and the sending configuration file indicates that the unicast connection establishment request message is DRX-compatible, the receiving UE may receive the unicast connection establishment request message in the default DRX mode.

[0173] Alternatively, if network device 1 does not support SL DRX, the sending UE is pre-configured with a default DRX mode, and the sending profile indicates that the unicast connection establishment request message is DRX-compatible, the sending UE may send the unicast connection establishment request message in the default DRX mode. Correspondingly, if network device 2 does not support SL DRX, the receiving UE may receive the unicast connection establishment request message in a non-DRX mode.

[0174] It should be noted that the default DRX mode may refer to a DRX configuration pre-configured in the terminal device (ie, the default DRX configuration).

[0175] The receiving UE may determine a response mode for the unicast connection establishment request message according to a sending profile corresponding to the unicast connection establishment request message.

[0176] Optionally, if the sending profile corresponding to the unicast connection establishment request message indicates support for SL DRX, then in response to the unicast connection establishment request message, the receiving UE can perform at least one of the following operations: sending a unicast connection establishment accept (DCA) message to the sending UE, not replying to the DCA message, sending a DCA message to the sending UE, receiving SL data in DRX mode, or receiving SL data in non-DRX mode.

[0177] For example, if the network device 2 does not support SL DRX, the receiving UE may perform the following S1020: the receiving UE sends a unicast connection establishment accept (DCA) message. Accordingly, the sending UE receives the unicast connection establishment accept message.

[0178] For example, the receiving UE may send a unicast connection establishment accept (DCA) message in a non-DRX mode. Correspondingly, the sending UE may receive the unicast connection establishment accept message in a non-DRX mode.

[0179] S1030: The receiving UE sends sixth information. Correspondingly, the sending UE receives the sixth information.

[0180] Optionally, the sixth information may be used to indicate the user capability of the receiving UE. For example, the sixth information may be capability interaction information.

[0181] The receiving UE may determine the user capabilities of the receiving UE as a PC5 UE based on the SL DRX capabilities of network device 2 and / or the SL DRX capabilities of the receiving UE. Alternatively, the receiving UE may determine the user capabilities based on the network configuration, the resource acquisition mode (of the receiving UE), and whether the receiving UE is within network coverage.

[0182] For example, if the network device 2 supports SL DRX and the receiving UE supports SL DRX, the receiving UE may determine that the user capability is supporting SL DRX.

[0183] For another example, if the network device 2 does not support SL DRX and the receiving UE supports SL DRX capability, the receiving UE may determine that the user capability is to support SL DRX.

[0184] Optionally, in other cases, the receiving UE may determine that the user capability is not supporting SL DRX.

[0185] After receiving the sixth information, the sending UE may determine whether to send SL DRX configuration information to the receiving UE based on the sixth information.

[0186] For example, if the sixth information indicates that the user capability of the receiving UE as a PC5 UE is not to support SL DRX, the sending UE may not send the SL DRX configuration information to the receiving UE.

[0187] For another example, if the sixth information indicates that the user capability of the receiving UE as a PC5 UE is to support SL DRX, S1050 may be executed.

[0188] S1040: The receiving UE sends the fourth information. Correspondingly, the sending UE receives the fourth information.

[0189] The fourth information may be used to indicate whether the receiving UE supports SL DRX and / or whether the receiving UE needs to configure SL DRX. For example, the fourth information may be used to indicate that the receiving UE does not support SL DRX and / or the receiving UE does not need to configure SL DRX.

[0190] Optionally, the fourth information may also be used to indicate at least one of the following information: whether the network device 2 supports SL DRX, and whether the network device 2 is configured with SL DRX.

[0191] The fourth information can be carried in PC5-RRC signaling, MAC CE signaling or physical layer signaling.

[0192] After receiving the fourth information, the sending UE may determine whether to send SL DRX configuration information to the receiving UE according to the fourth information.

[0193] For example, if the fourth information indicates that the receiving UE does not support SL DRX, the sending UE may not send SL DRX configuration information to the receiving UE.

[0194] For another example, if the fourth information indicates that the receiving UE supports SL DRX, the transmitting UE may send SL DRX configuration information to the receiving UE, that is, execute S1050.

[0195] In some possible implementations, the receiving UE may choose not to send SL DRX assistance information to the transmitting UE. Accordingly, if the transmitting UE does not receive the SL DRX assistance information from the receiving UE, the transmitting UE may not send the SL DRX configuration information to the receiving UE.

[0196] S1050: The sending UE sends sidelink configuration information. Correspondingly, the receiving UE receives the sidelink configuration information.

[0197] The sidelink configuration information may include SL DRX configuration information.

[0198] Optionally, the receiving UE may determine whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether network device 2 supports SL DRX. For example, the receiving UE may indicate its acceptance or rejection of the SL DRX configuration information by signaling RRCReconfigurationCompleteSidelink or RRCReconfigurationFailureSidelink.

[0199] Optionally, the receiving UE accepting the SL DRX configuration information may be understood as the receiving UE using the SL DRX configuration information for configuration, and the receiving UE rejecting the SL DRX configuration information may be understood as the receiving UE not using the SL DRX configuration information for configuration. Optionally, the self-capability may refer to the terminal device capability of the receiving UE.

[0200] Optionally, UE implementation may refer to the UE's own decision, that is, the receiving UE determines whether to accept or reject the configuration according to the SL DRX configuration information based on the UE implementation, which may refer to: the receiving UE decides whether to accept or reject the configuration according to the SL DRX configuration information.

[0201] It should be noted that the method 1000 in FIG10 is merely an example and not a limitation. Not all steps need to be performed, or these steps may be performed in another order, which is not limited in the embodiments of the present application.

[0202] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 10. The device embodiment of the present application is described in detail below in conjunction with Figures 11 to 13. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0203] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1100 in FIG11 includes an acquisition unit 1110 and a sending unit 1120, which are specifically as follows:

[0204] An acquiring unit 1110 is configured to acquire a configuration of a first network device;

[0205] The sending unit 1120 is configured to send sidelink SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the first network device.

[0206] Optionally, the acquisition unit 1110 is specifically used to: receive first information sent by the first network device, the first information is used to carry SL DRX configuration information of the first network device; the device 1100 also includes a determination unit 1130, used to: if the first information does not contain the SL DRX configuration information, determine that the first network device does not support SL DRX.

[0207] Optionally, the sending unit 1120 is specifically configured to: if the first network device does not support SL DRX, send SL data in a non-DRX manner based on the configuration of the first network device.

[0208] Optionally, the sending unit 1120 is specifically configured to send data corresponding to a service or layer 2 identifier that supports DRX transmission in a non-DRX manner based on the configuration of the first network device.

[0209] Optionally, the sending unit 1120 is specifically configured to: if the first network device does not support SL DRX, not send data corresponding to a service or layer 2 identifier that supports DRX transmission based on the configuration of the first network device.

[0210] Optionally, the SL data is unicast data, multicast data or broadcast data.

[0211] Optionally, the sending unit 1120 is specifically configured to: if the first network device does not support SL DRX, send a unicast connection establishment request message in a non-DRX manner based on the configuration of the first network device.

[0212] Optionally, the sending unit 1120 is specifically used to: if the first network device does not support SL DRX, and a default DRX mode is pre-configured in the device, and the sending configuration file indicates that the unicast connection establishment request information is DRX compatible, then based on the configuration of the first network device, a unicast connection establishment request message is sent in the default DRX mode.

[0213] Optionally, the device 1100 also includes a determination unit 1130, which is used to: determine the user capability of the device when acting as a PC5 user equipment UE based on the SL DRX capability of the first network device and the SL DRX capability of the device; the sending unit 1120 is specifically used to: send second information to the second terminal device, and the second information is used to indicate the user capability.

[0214] Optionally, the second information is capability interaction information.

[0215] Optionally, the determining unit 1130 is specifically configured to: if the first network device supports SL DRX and the apparatus supports SL DRX, determine that the user capability is to support SL DRX.

[0216] Optionally, the determining unit 1130 is specifically configured to: if the first network device does not support SL DRX and the apparatus supports SL DRX capability, determine that the user capability is to support SL DRX.

[0217] Optionally, the determining unit 1130 is specifically configured to: determine that the user capability is to support SL DRX if the first network device does not support SL DRX, the apparatus supports SL DRX capability, and the apparatus is in an idle state, an inactive state, or out of coverage.

[0218] Optionally, the determination unit 1130 is specifically used to: if the first network device does not support SL DRX, the device supports SL DRX capability, the device is in a connected state and the resource acquisition mode of the device is configured as mode 2, then determine that the user capability is to support SL DRX.

[0219] Optionally, the apparatus 1100 further includes a receiving unit 1140, configured to: receive SL DRX assistance information from a second terminal device, where the SL DRX assistance information is used to indicate a desired SL DRX configuration of the second terminal device.

[0220] Optionally, the sending unit 1120 is also used to: send third information to the second terminal device under the first condition, and the third information indicates at least one of the following: the device does not support / cannot configure SL DRX, whether the device can support / configure SL DRX, whether the device is in mode 1, whether the device is in a connected state, whether the first network device supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

[0221] Optionally, the first condition includes at least one of the following: the device does not support SL DRX, the device is in a connected state, and the resource acquisition method of the device is configured as mode 1.

[0222] Optionally, the third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

[0223] Optionally, the content of the third information is determined by the apparatus based on the configuration of the first network device.

[0224] Optionally, the apparatus 1100 further includes a receiving unit 1140, configured to: receive fourth information from a second terminal device, wherein the fourth information is used to indicate whether the second terminal device supports SL DRX; and the sending unit is specifically configured to: determine whether to send SL DRX configuration information to the second terminal device based on the fourth information.

[0225] Optionally, the sending unit 1120 is specifically used to: if the fourth information indicates that the second terminal device does not support SL DRX, not send SL DRX configuration information to the second terminal device.

[0226] Optionally, the sending unit 1120 is specifically used to: if the apparatus does not receive SL DRX assistance information from the second terminal device, not send SL DRX configuration information to the second terminal device, wherein the SL DRX assistance information is used to indicate the SL DRX configuration desired by the second terminal device.

[0227] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1200 in FIG12 includes an acquisition unit 1210 and a receiving unit 1220, as follows:

[0228] An acquiring unit 1210 is configured to acquire a configuration of a second network device;

[0229] The receiving unit 1220 is configured to receive sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device.

[0230] Optionally, the acquisition unit 1210 is specifically used to: receive the fifth information sent by the second network device, and the fifth information is used to carry the SL DRX configuration information of the second network device; the device 1200 also includes a determination unit 1230, which is used to: if the fifth information does not contain the SL DRX configuration information, determine that the second network device does not support SL DRX.

[0231] Optionally, the receiving unit 1220 is specifically configured to: if the second network device does not support SL DRX, receive SL data in a non-DRX manner based on the configuration of the second network device.

[0232] Optionally, the receiving unit 1220 is specifically configured to: receive data corresponding to a service or layer 2 identifier sent in a DRX manner in a non-DRX manner based on the configuration of the second network device.

[0233] Optionally, the SL data is unicast data, multicast data or broadcast data.

[0234] Optionally, the apparatus 1200 further includes a determining unit 1230, configured to determine a response mode of the unicast connection establishment request message according to a sending profile corresponding to the unicast connection establishment request DCR message.

[0235] Optionally, the receiving unit 1220 is specifically configured to: if the second network device does not support SL DRX, receive a unicast connection establishment request message in a non-DRX manner based on the configuration of the second network device.

[0236] Optionally, the receiving unit 1220 is specifically used to: if the second network device does not support SL DRX, and a default DRX mode is pre-configured in the device, and the sending configuration file indicates that the unicast connection establishment request information is DRX compatible, then based on the configuration of the second network device, the unicast connection establishment request message is received in the default DRX mode.

[0237] Optionally, the determination unit 1230 is specifically used to: if the sending profile indicates support for SL DRX, then perform at least one of the following operations in response to the unicast connection establishment request message: send a unicast connection establishment acceptance DCA message to the first terminal device, do not reply to the DCA message, send a DCA message to the first terminal device, receive SL data in DRX mode, or receive SL data in non-DRX mode.

[0238] Optionally, the determination unit 1230 is specifically used to: if the sending profile indicates that SL DRX is not supported, then perform at least one of the following operations in response to the unicast connection establishment request message: send a unicast connection establishment acceptance DCA message to the first terminal device, refuse to reply to the DCA message, send a DCA message to the first terminal device, receive SL data in DRX mode, or receive SL data in non-DRX mode.

[0239] Optionally, the receiving unit 1220 is specifically used to: receive second information from the first terminal device, the second information being used to indicate the user capability of the first terminal device when acting as a PC5 user equipment UE; the device 1200 also includes a determination unit 1230, being used to: determine whether to send SL DRX assistance information to the first terminal device based on the second information, the SL DRX assistance information being used to indicate the SL DRX configuration desired by the second terminal device.

[0240] Optionally, the determining unit 1230 is specifically configured to: if the second information indicates that the user capability of the first terminal device as a PC5 UE is not to support SL DRX, then not send the SL DRX assistance information to the first terminal device.

[0241] Optionally, the determining unit 1230 is specifically configured to: if the second information indicates that the user capability of the first terminal device as a PC5 UE is to support SL DRX, then send the SL DRX assistance information to the first terminal device.

[0242] Optionally, the determining unit 1230 is further configured to determine whether to disconnect the PC5 connection with the first terminal device based on the second information.

[0243] Optionally, the determining unit 1230 is specifically configured to: disconnect the PC5 connection with the first terminal device if the second information indicates that the user capability of the first terminal device as a PC5 UE does not support SL DRX.

[0244] Optionally, the receiving unit 1220 is specifically used to: receive third information sent by the first terminal device under the first condition; the device 1200 also includes a determining unit 1230, used to: disconnect the PC5 connection with the first terminal device, and the third information indicates at least one of the following: the first terminal device does not support / cannot configure SL DRX, whether the first terminal device can support / configure SL DRX, whether the first terminal device is in mode 1, whether the first terminal device is in a connected state, whether the first network device where the first terminal device is located supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

[0245] Optionally, the first condition includes at least one of the following: the network where the first terminal device is located does not support SL DRX, the first terminal device is in a connected state, and the resource acquisition method of the first terminal device is configured as mode 1.

[0246] Optionally, the third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

[0247] Optionally, the determining unit 1230 is specifically configured to send instruction information for instructing to disconnect the PC5 to an upper layer.

[0248] Optionally, the determining unit 1230 is further configured to define a new PC5-S signaling disconnection cause value or reuse an existing PC5-S signaling disconnection cause value.

[0249] Optionally, the determination unit 1230 is also used to: determine the user capability of the device when acting as a PC5 user equipment UE based on the SL DRX capability of the second network device and the SL DRX capability of the device; the device 1200 also includes a sending unit 1240, used to: send sixth information to the first terminal device, and the sixth information is used to indicate the user capability.

[0250] Optionally, the sixth information is capability interaction information.

[0251] Optionally, the determining unit 1230 is specifically configured to: if the second network device supports SL DRX and the apparatus supports SL DRX, determine that the user capability is to support SL DRX.

[0252] Optionally, the determining unit 1230 is specifically configured to: if the second network device does not support SL DRX and the apparatus supports SL DRX capability, determine that the user capability is to support SL DRX.

[0253] Optionally, the apparatus 1200 further includes a sending unit 1240, configured to send fourth information to the first terminal device, where the fourth information is used to indicate that the apparatus does not support SL DRX and / or that the apparatus does not need to be configured with SL DRX.

[0254] Optionally, the fourth information is further used to indicate at least one of the following information: whether the second network device supports SL DRX, and whether the second network device is configured with SL DRX.

[0255] Optionally, the fourth information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

[0256] Optionally, the receiving unit 1220 is specifically used to: receive side link configuration information from the first terminal device, the side link configuration information including SL DRX configuration information; the device 1200 also includes a determination unit 1230, used to: determine whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

[0257] Optionally, the receiving unit 1220 is specifically used to: receive side link configuration information from the first terminal device, and the side link configuration information does not include SL DRX configuration information; the device 1200 also includes a determination unit 1230, which is used to: determine whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

[0258] FIG13 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dashed lines in FIG13 indicate that the unit or module is optional. Apparatus 1300 may be used to implement the method described in the above method embodiment. Apparatus 1300 may be a chip or a communication device.

[0259] The device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the above method embodiment. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0260] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.

[0261] The apparatus 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.

[0262] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0263] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0264] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the communication device in each embodiment of the present application.

[0265] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0266] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0267] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0268] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0270] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0271] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0272] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The first terminal device obtains the configuration of the first network device; The first terminal device sends sidelink SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the first network device.

2. The method according to claim 1, characterized in that The first terminal device obtains the configuration of the first network device, including: The first terminal device receives first information sent by the first network device, where the first information is used to carry SL DRX configuration information of the first network device; If the first information does not include the SL DRX configuration information, the first terminal device determines that the first network device does not support SL DRX.

3. The method according to claim 1 or 2, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: If the first network device does not support SL DRX, the first terminal device sends SL data in a non-DRX manner based on the configuration of the first network device.

4. The method according to claim 3, characterized in that The first terminal device sending SL data in a non-DRX manner based on the configuration of the first network device includes: The first terminal device sends data corresponding to the service or layer 2 identifier supported by DRX in a non-DRX manner based on the configuration of the first network device.

5. The method according to claim 1 or 2, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: If the first network device does not support SL DRX, the first terminal device does not send data corresponding to the service or layer 2 identifier that supports DRX transmission based on the configuration of the first network device.

6. The method according to any one of claims 1 to 5, characterized in that The SL data is unicast data, multicast data or broadcast data.

7. The method according to any one of claims 1 to 6, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: If the first network device does not support SL DRX, the first terminal device sends a unicast connection establishment request message in a non-DRX manner based on the configuration of the first network device.

8. The method according to any one of claims 1 to 6, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: If the first network device does not support SL DRX, and the first terminal device is pre-configured with a default DRX mode, and the configuration file sent indicates that the unicast connection establishment request information is DRX compatible, then the first terminal device sends a unicast connection establishment request message in the default DRX mode based on the configuration of the first network device.

9. The method according to any one of claims 1 to 6, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: The first terminal device determines, based on the SL DRX capability of the first network device and the SL DRX capability of the first terminal device, the user capability of the first terminal device when serving as a PC5 user equipment UE; The first terminal device sends second information to the second terminal device, where the second information is used to indicate the user capability.

10. The method according to claim 9, characterized in that The second information is capability interaction information.

11. The method according to claim 9 or 10, characterized in that The first terminal device determines, based on the SL DRX capability of the first network device and the SL DRX capability of the first terminal device, the user capability of the first terminal device when serving as a PC5 UE, including: If the first network device supports SL DRX and the first terminal device supports SL DRX, the first terminal device determines that the user capability is to support SL DRX.

12. The method according to claim 9 or 10, characterized in that The first terminal device determines, based on the SL DRX capability of the first network device and the SL DRX capability of the first terminal device, the user capability of the first terminal device when serving as a PC5 UE, including: If the first network device does not support SL DRX and the first terminal device supports SL DRX capability, the first terminal device determines that the user capability is to support SL DRX.

13. The method according to claim 9 or 10, characterized in that The first terminal device determines, based on the SL DRX capability of the first network device and the SL DRX capability of the first terminal device, the user capability of the first terminal device when serving as a PC5 UE, including: If the first network device does not support SL DRX, the first terminal device supports SL DRX capability, and the first terminal device is in an idle state, an inactive state, or out of coverage, the first terminal device determines that the user capability is to support SL DRX.

14. The method according to claim 9 or 10, characterized in that The first terminal device determines, based on the SL DRX capability of the first network device and the SL DRX capability of the first terminal device, the user capability of the first terminal device when serving as a PC5 UE, including: If the first network device does not support SL DRX, the first terminal device supports SL DRX capability, the first terminal device is in a connected state, and the resource acquisition mode of the first terminal device is configured as mode 2, the first terminal device determines that the user capability is to support SL DRX.

15. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first terminal device receives SL DRX assistance information from a second terminal device, where the SL DRX assistance information is used to indicate a SL DRX configuration desired by the second terminal device.

16. The method according to claim 15, characterized in that The method comprises: The first terminal device sends third information to the second terminal device under a first condition, where the third information indicates at least one of the following: The first terminal device does not support / cannot configure SL DRX, whether the first terminal device can support / configure SL DRX, whether the first terminal device is in mode 1, whether the first terminal device is in a connected state, whether the first network device supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

17. The method according to claim 16, characterized in that The first condition includes at least one of the following: The first network device does not support SL DRX, the first terminal device is in a connected state, and the resource acquisition method of the first terminal device is configured as mode 1.

18. The method according to claim 16 or 17, characterized in that The third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

19. The method according to claim 16 or 17, characterized in that The content of the third information is determined by the first terminal device based on the configuration of the first network device.

20. The method according to any one of claims 1 to 6, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: The first terminal device receives fourth information from the second terminal device, where the fourth information is used to indicate whether the second terminal device supports SL DRX; The first terminal device determines whether to send SL DRX configuration information to the second terminal device based on the fourth information.

21. The method according to claim 20, characterized in that The first terminal device determining, according to the fourth information, whether to send SL DRX configuration information to the second terminal device includes: If the fourth information indicates that the second terminal device does not support SL DRX, the first terminal device does not send SL DRX configuration information to the second terminal device.

22. The method according to any one of claims 1 to 6, characterized in that The first terminal device sending sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on a configuration of the first network device, including: If the first terminal device does not receive SL DRX assistance information from the second terminal device, the first terminal device does not send SL DRX configuration information to the second terminal device, where the SL DRX assistance information is used to indicate the SL DRX configuration desired by the second terminal device.

23. A communication method, characterized in that: include: The second terminal device obtains the configuration of the second network device; The second terminal device receives sidelink SL data in a discontinuous reception DRX manner or in a non-DRX manner based on the configuration of the second network device.

24. The method according to claim 23, wherein The second terminal device obtains the configuration of the second network device, including: The second terminal device receives fifth information sent by the second network device, where the fifth information is used to carry SL DRX configuration information of the second network device; If the fifth information does not include the SL DRX configuration information, the second terminal device determines that the second network device does not support SL DRX.

25. The method according to claim 23 or 24, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device, including: If the second network device does not support SL DRX, the second terminal device receives SL data in a non-DRX manner based on the configuration of the second network device.

26. The method according to claim 25, characterized in that The second terminal device receiving the sidelink (SL) data in a non-DRX manner based on the configuration of the second network device, including: The second terminal device receives the service or data corresponding to the layer 2 identifier sent in a DRX manner in a non-DRX manner based on the configuration of the second network device.

27. The method according to any one of claims 23 to 26, characterized in that The SL data is unicast data, multicast data or broadcast data.

28. The method according to any one of claims 23 to 27, characterized in that The method further comprises: The second terminal device determines a response mode for the unicast connection establishment request message according to a sending profile corresponding to the unicast connection establishment request DCR message.

29. The method according to claim 28, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the network device, including: If the second network device does not support SL DRX, the second terminal device receives the unicast connection establishment request message in a non-DRX manner based on the configuration of the second network device.

30. The method according to claim 28, wherein The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the network device, including: If the second network device does not support SL DRX, and the second terminal device is pre-configured with a default DRX mode, and the configuration file sent indicates that the unicast connection establishment request message is DRX compatible, then the second terminal device receives the unicast connection establishment request message in the default DRX mode based on the configuration of the second network device.

31. The method according to any one of claims 28 to 30, characterized in that The second terminal device determines, according to the sending profile corresponding to the unicast connection establishment request DCR message, a response mode for the unicast connection establishment request message, including: If the sending profile indicates support for SL DRX, the second terminal device performs at least one of the following operations in response to the unicast connection establishment request message: sending a unicast connection establishment acceptance DCA message to the first terminal device, not replying to the DCA message, sending a DCA message to the first terminal device, receiving SL data in DRX mode, or receiving SL data in non-DRX mode.

32. The method according to any one of claims 28 to 30, characterized in that The second terminal device determines, according to the sending profile corresponding to the unicast connection establishment request DCR message, a response mode for the unicast connection establishment request message, including: If the sending profile indicates that SL DRX is not supported, the second terminal device performs at least one of the following operations in response to the unicast connection establishment request message: sending a unicast connection establishment acceptance DCA message to the first terminal device, refusing to reply to the DCA message, sending a DCA message to the first terminal device, receiving SL data in DRX mode, or receiving SL data in non-DRX mode.

33. The method according to any one of claims 23 to 27, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device, including: The second terminal device receives second information from the first terminal device, where the second information is used to indicate user capabilities of the first terminal device when serving as a PC5 user equipment UE; The second terminal device determines whether to send SL DRX assistance information to the first terminal device based on the second information, where the SL DRX assistance information is used to indicate the SL DRX configuration desired by the second terminal device.

34. The method according to claim 33, wherein The second terminal device determining whether to send SL DRX assistance information to the first terminal device based on the second information includes: If the second information indicates that the user capability of the first terminal device as a PC5 UE is not to support SL DRX, the second terminal device does not send the SL DRX assistance information to the first terminal device.

35. The method according to claim 33 or 34, characterized in that The second terminal device determining whether to send SL DRX assistance information to the first terminal device based on the second information includes: If the second information indicates that the user capability of the first terminal device as a PC5 UE is to support SL DRX, the second terminal device sends the SL DRX assistance information to the first terminal device.

36. The method according to any one of claims 33 to 35, characterized in that The method further comprises: The second terminal device determines whether to disconnect the PC 5 from the first terminal device based on the second information.

37. The method according to claim 36, wherein The second terminal device determines whether to disconnect the PC5 connection with the first terminal device based on the second information, including: If the second information indicates that the user capability of the first terminal device as a PC5 UE is not to support SL DRX, the second terminal device disconnects the PC5 connection with the first terminal device.

38. The method according to any one of claims 23 to 27, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device, including: The second terminal device receives third information sent by the first terminal device under the first condition; The second terminal device disconnects the PC5 connection with the first terminal device; The third information indicates at least one of the following: The first terminal device does not support / cannot configure SL DRX, whether the first terminal device can support / configure SL DRX, whether the first terminal device is in mode 1, whether the first terminal device is in a connected state, whether the first network device supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

39. The method according to claim 38, characterized in that The first condition includes at least one of the following: The network where the first terminal device is located does not support SL DRX, the first terminal device is in a connected state, and the resource acquisition method of the first terminal device is configured as mode 1.

40. The method according to claim 38 or 39, characterized in that The third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

41. The method according to claim 38 or 39, characterized in that The second terminal device disconnecting the PC5 connection with the first terminal device includes: The second terminal device sends instruction information for instructing to disconnect the PC5 to an upper layer.

42. The method according to claim 41, wherein The method further comprises: The second terminal device defines a new PC5-S signaling disconnection cause value or reuses an existing PC5-S signaling disconnection cause value.

43. The method according to any one of claims 23 to 27, characterized in that The method further comprises: The second terminal device determines, based on the SL DRX capability of the second network device and the SL DRX capability of the second terminal device, the user capability of the second terminal device when serving as a PC5 user equipment UE; The second terminal device sends sixth information to the first terminal device, where the sixth information is used to indicate the user capability.

44. The method according to claim 43, wherein The sixth information is capability interaction information.

45. The method according to claim 43 or 44, characterized in that The second terminal device determines, based on the SL DRX capability of the second network device and the SL DRX capability of the second terminal device, the user capability of the second terminal device as a PC5 UE, including: If the second network device supports SL DRX and the second terminal device supports SL DRX, the second terminal device determines that the user capability is supporting SL DRX.

46. ​​The method according to any one of claims 43 to 45, characterized in that The second terminal device determines, based on the SL DRX capability of the second network device and the SL DRX capability of the second terminal device, the user capability of the second terminal device as a PC5 UE, including: If the second network device does not support SL DRX and the second terminal device supports SL DRX capability, the second terminal device determines that the user capability is to support SL DRX.

47. The method according to any one of claims 23 to 27, characterized in that The method further comprises: The second terminal device sends fourth information to the first terminal device, where the fourth information is used to indicate that the second terminal device does not support SL DRX and / or that the second terminal device does not need to configure SL DRX.

48. The method according to claim 47, wherein The fourth information is further used to indicate at least one of the following information: whether the second network device supports SL DRX, and whether the second network device is configured with SL DRX.

49. The method according to claim 47 or 48, characterized in that The fourth information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

50. The method according to any one of claims 23 to 27, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device, including: The second terminal device receives sidelink configuration information from the first terminal device, where the sidelink configuration information includes SL DRX configuration information; The second terminal device determines whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

51. The method according to any one of claims 23 to 27, characterized in that The second terminal device receiving the sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device, including: The second terminal device receives sidelink configuration information from the first terminal device, where the sidelink configuration information does not include SL DRX configuration information; The second terminal device determines whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

52. A communication device, characterized in that include: an acquiring unit, configured to acquire a configuration of the first network device; A sending unit is used to send side link SL data in a discontinuous reception DRX mode or in a non-DRX mode based on the configuration of the first network device.

53. The device according to claim 52, characterized in that The acquisition unit is specifically used to: receive first information sent by the first network device, the first information is used to carry SL DRX configuration information of the first network device; the device also includes a determination unit, used to: if the first information does not contain the SL DRX configuration information, determine that the first network device does not support SL DRX.

54. The device according to claim 52 or 53, characterized in that The sending unit is specifically configured to: if the first network device does not support SL DRX, send SL data in a non-DRX manner based on the configuration of the first network device.

55. The device according to claim 54, characterized in that The sending unit is specifically configured to send data corresponding to a service or layer 2 identifier that supports DRX transmission in a non-DRX manner based on the configuration of the first network device.

56. The device according to claim 52 or 53, characterized in that The sending unit is specifically configured to: if the first network device does not support SL DRX, not send the service supported by DRX or data corresponding to the layer 2 identifier based on the configuration of the first network device.

57. The device according to any one of claims 52 to 56, characterized in that The SL data is unicast data, multicast data or broadcast data.

58. The device according to any one of claims 52 to 57, characterized in that The sending unit is specifically configured to: if the first network device does not support SL DRX, send a unicast connection establishment request message in a non-DRX manner based on the configuration of the first network device.

59. The device according to any one of claims 52 to 57, characterized in that The sending unit is specifically used to: if the first network device does not support SL DRX, and a default DRX mode is pre-configured in the device, and the sending configuration file indicates that the unicast connection establishment request information is DRX compatible, then based on the configuration of the first network device, send a unicast connection establishment request message in the default DRX mode.

60. The device according to any one of claims 52 to 57, characterized in that The device also includes a determination unit for determining the user capability of the device as a PC5 user equipment UE based on the SL DRX capability of the first network device and the SL DRX capability of the device; the sending unit is specifically used to send second information to the second terminal device, and the second information is used to indicate the user capability.

61. The device according to claim 60, characterized in that The second information is capability interaction information.

62. The device according to claim 60 or 61, characterized in that The determining unit is specifically configured to: if the first network device supports SL DRX and the apparatus supports SL DRX, determine that the user capability is to support SL DRX.

63. The device according to claim 60 or 61, characterized in that The determining unit is specifically configured to: if the first network device does not support SL DRX and the apparatus supports SL DRX capability, determine that the user capability is to support SL DRX.

64. The device according to claim 60 or 61, characterized in that The determining unit is specifically configured to: if the first network device does not support SL DRX, the apparatus supports SL DRX capability, and the apparatus is in an idle state, an inactive state, or out of coverage, determine that the user capability is to support SL DRX.

65. The device according to claim 60 or 61, characterized in that The determining unit is specifically configured to: if the first network device does not support SL DRX, the apparatus supports SL DRX capability, the apparatus is in a connected state, and the resource acquisition mode of the apparatus is configured as mode 2, then determine that the user capability supports SL DRX.

66. The device according to any one of claims 52 to 57, characterized in that The apparatus further includes a receiving unit configured to receive SL DRX assistance information from a second terminal device, where the SL DRX assistance information is used to indicate a SL DRX configuration desired by the second terminal device.

67. The device according to claim 66, characterized in that The sending unit is also used to: send third information to the second terminal device under a first condition, and the third information indicates at least one of the following: the device does not support / cannot configure SL DRX, whether the device can support / configure SL DRX, whether the device is in mode 1, whether the device is in a connected state, whether the first network device supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

68. The device according to claim 67, characterized in that The first condition includes at least one of the following: the device does not support SL DRX, the device is in a connected state, and the resource acquisition method of the device is configured as mode 1.

69. The device according to claim 67 or 68, characterized in that The third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

70. The device according to claim 67 or 68, characterized in that The content of the third information is determined by the apparatus based on the configuration of the first network device.

71. The device according to any one of claims 52 to 57, characterized in that The apparatus further includes a receiving unit configured to receive fourth information from a second terminal device, the fourth information being used to indicate whether the second terminal device supports SL DRX; and the sending unit being specifically configured to determine whether to send SL DRX configuration information to the second terminal device based on the fourth information.

72. The device according to claim 71, characterized in that The sending unit is specifically configured to: if the fourth information indicates that the second terminal device does not support SL DRX, not send SL DRX configuration information to the second terminal device.

73. The device according to any one of claims 52 to 57, characterized in that The sending unit is specifically configured to: if the apparatus does not receive SL DRX assistance information from the second terminal device, not send SL DRX configuration information to the second terminal device, where the SL DRX assistance information is used to indicate the SL DRX configuration desired by the second terminal device.

74. A communication device, characterized in that include: an acquiring unit, configured to acquire a configuration of a second network device; A receiving unit is configured to receive sidelink SL data in a discontinuous reception (DRX) mode or in a non-DRX mode based on the configuration of the second network device.

75. The device according to claim 74, characterized in that The acquisition unit is specifically used to: receive the fifth information sent by the second network device, and the fifth information is used to carry the SL DRX configuration information of the second network device; the device also includes a determination unit, which is used to: if the fifth information does not contain the SL DRX configuration information, determine that the second network device does not support SL DRX.

76. The device according to claim 74 or 75, characterized in that The receiving unit is specifically configured to: if the second network device does not support SL DRX, receive SL data in a non-DRX manner based on the configuration of the second network device.

77. The device according to claim 76, characterized in that The receiving unit is specifically configured to receive, in a non-DRX manner, a service or data corresponding to a layer 2 identifier sent in a DRX manner based on the configuration of the second network device.

78. The device according to any one of claims 74 to 77, characterized in that The SL data is unicast data, multicast data or broadcast data.

79. The device according to any one of claims 74 to 78, characterized in that The apparatus further includes a determining unit configured to determine a response mode for the unicast connection establishment request message according to a sending profile corresponding to the unicast connection establishment request DCR message.

80. The device according to claim 79, characterized in that The receiving unit is specifically configured to: if the second network device does not support SL DRX, receive the unicast connection establishment request message in a non-DRX manner based on the configuration of the second network device.

81. The device according to claim 79, characterized in that The receiving unit is specifically used to: if the second network device does not support SL DRX, and a default DRX mode is pre-configured in the device, and the sending configuration file indicates that the unicast connection establishment request information is DRX compatible, then based on the configuration of the second network device, receive the unicast connection establishment request message in the default DRX mode.

82. The device according to any one of claims 79 to 81, characterized in that The determination unit is specifically used to: if the sending profile indicates support for SL DRX, then perform at least one of the following operations in response to the unicast connection establishment request message: send a unicast connection establishment acceptance DCA message to the first terminal device, do not reply to the DCA message, send a DCA message to the first terminal device, receive SL data in DRX mode, or receive SL data in non-DRX mode.

83. The device according to any one of claims 79 to 81, characterized in that The determination unit is specifically used to: if the sending profile indicates that SL DRX is not supported, then perform at least one of the following operations in response to the unicast connection establishment request message: send a unicast connection establishment acceptance DCA message to the first terminal device, refuse to reply to the DCA message, send a DCA message to the first terminal device, receive SL data in DRX mode, or receive SL data in non-DRX mode.

84. The device according to any one of claims 74 to 78, characterized in that The receiving unit is specifically used to: receive second information from the first terminal device, the second information is used to indicate the user capability of the first terminal device when it acts as a PC5 user equipment UE; the device also includes a determination unit, used to: determine whether to send SL DRX assistance information to the first terminal device based on the second information, the SL DRX assistance information is used to indicate the SL DRX configuration desired by the second terminal device.

85. The device according to claim 84, characterized in that The determining unit is specifically configured to: if the second information indicates that the user capability of the first terminal device as a PC5 UE is not to support SL DRX, then not send the SL DRX assistance information to the first terminal device.

86. The device according to claim 84 or 85, characterized in that The determining unit is specifically configured to: if the second information indicates that the user capability of the first terminal device as a PC5 UE is to support SL DRX, then send the SL DRX assistance information to the first terminal device.

87. The device according to any one of claims 84 to 86, characterized in that The determining unit is further configured to determine whether to disconnect the PC5 from the first terminal device based on the second information.

88. The device according to claim 87, characterized in that The determining unit is specifically configured to disconnect the PC5 connection with the first terminal device if the second information indicates that the user capability of the first terminal device as a PC5 UE does not support SL DRX.

89. The device according to any one of claims 74 to 78, characterized in that The receiving unit is specifically used to: receive the third information sent by the first terminal device under the first condition; the device also includes a determination unit, used to: disconnect the PC5 connection with the first terminal device; wherein, the third information indicates at least one of the following: the first terminal device does not support / cannot configure SL DRX, whether the first terminal device can support / configure SL DRX, whether the first terminal device is in mode 1, whether the first terminal device is in a connected state, whether the first network device where the first terminal device is located supports / configures SL DRX, and the side link configuration information does not contain SL DRX configuration.

90. The device according to claim 89, characterized in that The first condition includes at least one of the following: the network where the first terminal device is located does not support SL DRX, the first terminal device is in a connected state, and the resource acquisition method of the first terminal device is configured as mode 1.

91. The device according to claim 89 or 90, characterized in that The third information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

92. The device according to claim 89 or 90, characterized in that The determining unit is specifically configured to send instruction information for instructing to disconnect the PC5 to an upper layer.

93. The device according to claim 92, characterized in that The determining unit is further configured to define a new PC5-S signaling disconnection cause value or reuse an existing PC5-S signaling disconnection cause value.

94. The device according to any one of claims 74 to 78, characterized in that The determination unit is also used to: determine the user capability of the device when acting as a PC5 user equipment UE based on the SL DRX capability of the second network device and the SL DRX capability of the device; the device also includes a sending unit for: sending sixth information to the first terminal device, and the sixth information is used to indicate the user capability.

95. The device according to claim 94, characterized in that The sixth information is capability interaction information.

96. The device according to claim 94 or 95, characterized in that The determining unit is specifically configured to: if the second network device supports SL DRX and the apparatus supports SL DRX, determine that the user capability is to support SL DRX.

97. The device according to any one of claims 94 to 96, characterized in that The determining unit is specifically configured to: if the second network device does not support SL DRX and the apparatus supports SL DRX capability, determine that the user capability is to support SL DRX.

98. The device according to any one of claims 74 to 78, characterized in that The apparatus further includes a sending unit configured to send fourth information to the first terminal device, where the fourth information is used to indicate that the apparatus does not support SL DRX and / or that the apparatus does not need to be configured with SL DRX.

99. The device according to claim 98, characterized in that The fourth information is further used to indicate at least one of the following information: whether the second network device supports SL DRX, and whether the second network device is configured with SL DRX.

100. The device according to claim 98 or 99, characterized in that The fourth information is carried in PC5-Radio Resource Control RRC signaling, Media Access Control Layer Control Element MAC CE signaling or physical layer signaling.

101. The device according to any one of claims 74 to 78, characterized in that The receiving unit is specifically used to: receive side link configuration information from the first terminal device, the side link configuration information including SL DRX configuration information; the device also includes a determination unit, used to: determine whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

102. The device according to any one of claims 74 to 78, characterized in that The receiving unit is specifically used to: receive side link configuration information from the first terminal device, and the side link configuration information does not include SL DRX configuration information; the device also includes a determination unit, used to: determine whether to accept or reject the configuration according to the SL DRX configuration information based on at least one of its own capabilities, user equipment UE implementation, whether there is a power saving requirement, and whether the second network device supports SL DRX.

103. A communication device, characterized in that It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory to execute the method as described in any one of claims 1 to 22.

104. A communication device, characterized in that It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory to execute the method as described in any one of claims 23 to 51.

105. A communication device, characterized in that The device comprises a processor configured to call a program from a memory to execute the method according to any one of claims 1 to 22.

106. A communication device, characterized in that The device comprises a processor configured to call a program from a memory to execute the method according to any one of claims 23 to 51.

107. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 22.

108. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 23 to 51.

109. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 22.

110. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 23 to 51.

111. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 1 to 22.

112. A computer program product, characterized in that A program is included, the program causing a computer to execute the method according to any one of claims 23 to 51.

113. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 22.

114. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 23 to 51.