Data transmission method, electronic device and storage medium

Abstract

The present application discloses a data transmission method, comprising: a transmitting device determines an available target address set according to side link authorization information, wherein the side link authorization information includes: time-frequency resources and / or resource pool type, and at least one target address in the available target address set is used for the transmitting device to generate data. The present application also discloses another data transmission method, electronic device and storage medium.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the international application with application number PCT / CN2021 / 073853 and application date January 26, 2021, and the international application with application number PCT / CN2021 / 111173 and application date August 6, 2021, and claims the priority of the international application. The entire contents of the international application are hereby incorporated into this application by reference. Technical Field

[0003] The present application relates to the field of sideline transmission technology, and in particular to a data transmission method, electronic device and storage medium. Background Art

[0004] In the New Radio-Vehicle to Everything (NR-V2X) system, how to effectively transmit data after the transmitting device receives the sidelink authorization is a constant goal. Summary of the Invention

[0005] The embodiments of the present application provide a data transmission method, an electronic device, and a storage medium, which can realize effective data transmission.

[0006] In a first aspect, an embodiment of the present application provides a data transmission method, comprising: a sending device determines a set of available target addresses based on side link authorization information, the side link authorization information including: time-frequency resources and / or resource pool type, and at least one target address in the set of available target addresses is used by the sending device to generate data.

[0007] In a second aspect, an embodiment of the present application provides a data transmission method, including: a receiving device receives data according to whether the receiving device is configured with discontinuous reception (DRX) and / or resource pool type.

[0008] In a third aspect, an embodiment of the present application provides a sending device, a processing unit, configured to determine a set of available target addresses based on side link authorization information, the side link authorization information including: time-frequency resources and / or resource pool type, at least one target address in the set of available target addresses is used for the sending device to generate data.

[0009] In a fourth aspect, an embodiment of the present application provides a receiving device, comprising: a receiving unit configured to receive data based on whether the receiving device is configured with DRX and / or resource pool type.

[0010] In a fifth aspect, an embodiment of the present application provides a sending device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when running the computer program, executes the steps of the data transmission method performed by the above-mentioned sending device.

[0011] In a sixth aspect, an embodiment of the present application provides a receiving device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor, when running the computer program, executes the steps of the data transmission method performed by the above-mentioned receiving device.

[0012] In a seventh aspect, an embodiment of the present application provides a chip, comprising: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned sending device.

[0013] In an eighth aspect, an embodiment of the present application provides a chip, comprising: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned receiving device.

[0014] In a ninth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned sending device.

[0015] In a tenth aspect, an embodiment of the present application provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned receiving device.

[0016] In an eleventh aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned sending device.

[0017] In a twelfth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned receiving device.

[0018] In a thirteenth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned sending device.

[0019] In a fourteenth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned receiving device. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A schematic diagram of the process of selecting transmission resources in the first mode of this application;

[0021] Figure 2 Schematic diagram of the process of selecting transmission resources in the second mode of this application;

[0022] Figure 3 A schematic diagram of an optional processing flow of the data transmission method provided in an embodiment of the present application;

[0023] Figure 4 This is a schematic diagram of a sending device sending a MAC PDU according to an embodiment of the present application;

[0024] Figure 5 A schematic diagram of another optional processing flow of the data transmission method provided in an embodiment of the present application;

[0025] Figure 6 A schematic diagram of another optional processing flow of the data transmission method provided in an embodiment of the present application;

[0026] Figure 7 A schematic diagram of an optional structural composition of a sending device provided in an embodiment of the present application;

[0027] Figure 8 A schematic diagram of an optional structural composition of a receiving device provided in an embodiment of the present application;

[0028] Figure 9 A schematic diagram of another optional structural component of the sending device provided in an embodiment of the present application;

[0029] Figure 10 A schematic diagram of the hardware structure of the electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to enable a more detailed understanding of the features and technical contents of the embodiments of the present application, the implementation of the embodiments of the present application is described in detail below with reference to the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present application.

[0031] Before describing the embodiments of the present application, a brief description of the relevant contents is given.

[0032] Device-to-device (D2D) communication is a sidelink (SL)-based transmission technology. Unlike traditional cellular systems, where communication data is received or sent by network devices, it offers higher spectrum efficiency and lower transmission latency. The Internet of Vehicles (IoV) system utilizes D2D communication (i.e., direct device-to-device communication). The Third Generation Partnership Project (3GPP) defines two transmission modes for D2D communication: Mode 1 (also known as Mode A) and Mode 2 (also known as Mode B). Mode 1 allocates transmission resources to terminal devices, while Mode 2 allows terminal devices to autonomously select transmission resources.

[0033] For the first mode: Figure 1 As shown, the transmission resources of the terminal device are allocated by the network device, and the terminal device sends data on the side link according to the resources allocated by the network device; the network device can allocate resources for a single transmission to the terminal device, or allocate resources for a semi-static transmission to the terminal device.

[0034] For the second mode: Figure 2 As shown, the terminal device selects a transmission resource in the resource pool to send data.

[0035] In the NR-V2X system, the terminal device can be in the first mode or the second mode; the terminal device can also be in a mixed mode, that is, the terminal device can obtain transmission resources through the first mode and the second mode at the same time. The way in which the terminal device obtains transmission resources can be indicated by the network device through the sidelink authorization, such as the network device indicating the time-frequency position of the corresponding physical sidelink control channel (Physical Sidelink Control Channel, PSCCH) and the physical sidelink shared channel (Physical Sidelink Shared Channel, PSSCH) through the sidelink authorization. Among them, the resource pool (RP) configuration in the NR-V2X system limits the time-frequency resource range of the sidelink communication.

[0036] In Long Term Evolution-Vehicle to Everything (LTE-V2X), the minimum time-domain granularity for resource pool configuration is a subframe, and in NR-V2X systems, the minimum time-domain granularity for resource pool configuration is a timeslot. The subframes or timeslots contained in a resource pool are indicated in a bitmap format by Radio Resource Control (RRC) signaling sent by network devices, allowing terminal devices to flexibly select the location of timeslots or subframes within the resource pool. The minimum frequency-domain granularity for a resource pool is a sub-channel, which is a contiguous number of physical resource blocks (PRBs) in the frequency domain. In LTE-V2X, the minimum subchannel is 4 contiguous PRBs, and the maximum is 100 contiguous PRBs (corresponding to a maximum channel bandwidth of 20 MHz). Since the LTE-V2X system uses single-carrier frequency-division multiple access (SC-FDMA), the number of PRBs contained in a subchannel must be divisible by 2, 3, or 5. In NR-V2X, a subchannel can have 10, 12, 15, 20, 25, 50, 75, or 100 PRBs. Since NR-V2X only supports cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM), to reduce the peak-to-average power ratio (PAPR) of sidelink transmissions, the subchannels in the resource pool must also be contiguous in the frequency domain. In addition, the frequency domain resources contained in the resource pool should be within a single SL bandwidth part (BWP).

[0037] In the NR-V2X system, feedback-based hybrid automatic repeat request (HARQ) retransmission is also introduced, and is not limited to HARQ retransmission for unicast communication, but also includes HARQ retransmission for multicast communication.

[0038] In 3GPP version (Rel) 12 / 13, for the Proximity based Service (ProSe), the position of the resource pool in the time domain can be configured, for example, the resource pool is discontinuous in the time domain, so that the terminal device can discontinuously send and / or receive data on the side link, thereby achieving power saving.

[0039] In R14 / 15, the Internet of Vehicles system sets requirements for vehicle-to-vehicle communication scenarios, which are mainly aimed at relatively high-speed vehicle-to-vehicle and vehicle-to-person communication services.

[0040] In the V2X system, since the vehicle-mounted system has a continuous power supply, the delay of data transmission is the main problem to be solved. Therefore, the system design requires the terminal equipment to perform continuous transmission and reception.

[0041] In Release 14, research was conducted on further enhancements to LTE Device-to-Device (FeD2D) technology for scenarios where wearable devices access the network via mobile phones, particularly for low-speed and low-power access scenarios. For FeD2D, network equipment can configure the DRX parameters of remote devices through a relay terminal.

[0042] In the NR-V2X system, the terminal device will discontinuously monitor the Physical Downlink Control Channel (PDCCH) according to its own DRX configuration to achieve power saving.When the PDCCH carries the cell radio network temporary identifier (C-RNTI), cancellation indication-radio network temporary identifier (CI-RNTI), configuration scheduling-radio network temporary identifier (CS-RNTI), interruption-radio network temporary identifier (INT-RNTI), slot format indicator-radio network temporary identifier (SFI-RNTI), semi-persistent scheduling-channel state information-radio network temporary identifier (SP-CSI-RNTI), transmission power control-physical uplink control channel-radio network temporary identifier (Transmit Power Control-Physical Uplink Control Channel-Radio Network Temporary Identifier, CS-RNTI), interruption-radio network temporary identifier (INT-RNTI), slot format indicator-radio network temporary identifier (SFI-RNTI), semi-persistent scheduling-channel state information-radio network temporary identifier (SP-CSI-RNTI), transmission power control-physical uplink control channel-radio network temporary identifier (Transmit Power Control-Physical Uplink Control Channel-Radio Network Temporary Identifier, CS-RNTI), interruption-radio network temporary identifier (INT-RNTI), slot format indicator-radio network temporary identifier (SFI-RNTI), semi-persistent scheduling-channel state information-radio network temporary identifier (SP-CSI-RNTI), transmission power control-physical uplink control channel-radio network temporary identifier (Transmit Power Control-Physical Uplink Control Channel-Radio Network Temporary Identifier, CS-RNTI), When the DRX operation is performed according to the control information, the terminal device will perform the corresponding DRX operation according to the control information.The network device controls the DRX behavior of the terminal device by configuring a series of parameters. The parameters configured by the network device may include: discontinuous reception duration timer (drx-onDurationTimer), discontinuous reception slot offset (drx-SlotOffset), discontinuous reception deactivation timer (drx-InactivityTimer), discontinuous reception retransmission downlink timer (drx-RetransmissionTimerDL), discontinuous reception retransmission uplink timer (drx-RetransmissionTimerUL), discontinuous reception long cycle start offset (drx-LongCycleStartOffset), discontinuous reception short cycle (optional) (drx-ShortCycle (optional)), short discontinuous reception cycle (the Short DRX cycle), discontinuous reception short cycle timer (optional) (drx-ShortCycleTimer(optional)), hybrid automatic repeat request round trip delay downlink timer (HARQ-RTT-TimerDL), discontinuous reception hybrid automatic repeat request round trip delay uplink timer (drx-HARQ-RTT-TimerUL), ps-Wakeup(optional), ps-TransmitOtherPeriodicCSI(optional) and ps-TransmitPeriodicL1-RSRP(optional).

[0043] Among them, the terminal device can be in a DRX activation state or an awake state in the following situations: 1) during the operation of drx-onDurationTimer or drx-InactivityTimer; 2) during the operation of drx-RetransmissionTimerDL or drx-RetransmissionTimerUL; 3) during the operation of ra-ContentionResolutionTimer or msgB-ResponseWindow; 4) there is an unprocessed SR; 5) during the PDCCH indication of a new transmission period.

[0044] In the prior art, after a terminal device obtains a sidelink authorization, it can select a target address based on certain rules, such as whether there is data transmission or data priority, and assemble a Media Access Control (MAC) Protocol Data Unit (PDU) to send the target address based on the Logical Channel Prioritization (LCP) criterion. However, after the introduction of the sidelink power saving mechanism, the device corresponding to the target address may be in a non-awake state and unable to receive data. Therefore, how to effectively transmit data by the sending device is a problem that needs to be solved.

[0045] In the data transmission method provided in the embodiment of the present application, the sending device determines the target address based on the time-frequency resources and / or resource pool type included in the side link authorization information, so that the data transmitted by the sending device can be effectively received by the receiving device.

[0046] An optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 3 As shown, the following steps are included:

[0047] Step S201: The sending device determines an available target address set based on sidelink authorization information, where the sidelink authorization information includes: time-frequency resources and / or resource pool type, and at least one target address in the available target address set is used by the sending device to generate data.

[0048] In some embodiments, the sending device may determine a set of available target addresses based on the sidelink grant information and information about the data to be sent.

[0049] In some embodiments, the transmitting device may be a terminal device for transmitting data in a sidelink transmission system. The transmitting device may obtain sidelink authorization information in a first mode and / or a second mode, and the sidelink authorization information may include time-frequency resources and / or resource pool types.

[0050] In some embodiments, if the set of available target addresses does not exist within the time-frequency resources and / or resource pool configured by the sidelink grant information, the transmitting device reports a first message to the network. Furthermore, in some embodiments, if the sidelink grant information comes from the network, the first message indicates that the sidelink grant resources configured by the network are unavailable and / or that the current target addresses are all in a DRX inactive state. Here, the current target address refers to the target address for sidelink communication with the transmitting device.

[0051] It should be noted that the sidelink authorized resources refer to the time-frequency resources and / or resource pool configured by the sidelink authorization information.

[0052] In an embodiment of the above solution, the first message may be physical layer signaling or a MAC control element (CE) or an RRC signaling.

[0053] In the embodiment of the present application, if all receiving devices (i.e., receiving user equipment (UE) (RxUE)) are in an inactive state, they are reported to the network. The network can wait until the next Rx UE's onduration timer runs before scheduling the sending device (i.e., transmitting UE (Tx UE)).

[0054] In some embodiments, the information of the data to be sent may include: a configuration file (profile) corresponding to the data to be sent, where the configuration file is used to indicate an available protocol version.

[0055] In the above solution, the resource pool and the configuration file have a corresponding relationship, and the resource pool supports the configuration file having the corresponding relationship therewith. For example, the resource pool can be configured to support configuration file one or configuration file two.

[0056] In one embodiment of the above solution, the protocol version is used to indicate at least one of the following information: the service corresponds to a terminal device configured with DRX; the service corresponds to a terminal device not configured with DRX; the service corresponds to a terminal device configured with DRX and a terminal device not configured with DRX; the destination address corresponding to the service is the address of a terminal device configured with DRX; and the destination address corresponding to the service is the address of a terminal device not configured with DRX. The data to be transmitted may be data in a logical channel; and the data generated by the transmitting device may be a MAC PDU.

[0057] It can be understood that the configuration file indicates the corresponding transmission format. For example, if the configuration file indicates that the protocol version is R14, the terminal device transmits the corresponding data packets in the format available for R14; if the configuration file indicates that the protocol version is R15, the terminal device transmits the corresponding data packets using the format available for R15. For example, the configuration file is used to indicate that the protocol version number is R17, and the DRX mechanism is introduced in the R17 protocol. If the configuration file corresponding to a service indicates that the protocol version number is R17, then when transmitting the service, it is necessary to consider that the service is sent to a receiving device configured with the DRX mechanism.

[0058] In some embodiments, the time-frequency resources may be the time-frequency resources of the PSCCH and the corresponding time-frequency resources of the PSSCH. The resource pool types may include: a shared resource pool and a non-shared resource pool; wherein the shared resource pool may refer to transmission resources in the shared resource pool being used for terminal devices configured with DRX and terminal devices not configured with DRX, that is, terminal devices configured with DRX (i.e., DRX terminal devices) and terminal devices not configured with DRX share transmission resources in the resource pool.

[0059] The non-shared resource pool may refer to the transmission resources within the non-shared resource pool being used for terminal devices configured with DRX and terminal devices not configured with DRX; or, the transmission resources within the non-shared resource pool being used for terminal devices configured with DRX; or, the transmission resources within the non-shared resource pool being used for terminal devices not configured with DRX; that is, the resources within the non-shared resource pool are only used for terminal devices configured with DRX, or the resources within the resource pool are only used for terminal devices not configured with DRX, or the resources within the resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX.

[0060] The following describes different resource pool types.

[0061] 1) If the resource pool type is a shared resource pool, the target address determined by the sending device is the address corresponding to the terminal device that is not configured with DRX; or, the target address determined by the sending device is the address corresponding to the DRX terminal device that is in the awake state in the time-frequency resource.

[0062] It can be understood that if the terminal device corresponding to the target address is not configured with DRX, the terminal device is in a state of continuous data reception, and the data transmitted by the transmitting device on the sidelink transmission resource can be received by the terminal device. If the terminal device corresponding to the target address is a terminal device configured with DRX and the terminal device is in an awake state, the data transmitted by the transmitting device on the sidelink transmission resource can also be received by the terminal device.

[0063] In some embodiments, the target address may further include at least one logical channel and / or media access control unit with the highest priority that meets the conditions. The conditions may include at least one of the following: sidelink data is available for transmission (SL data is available for transmission); as long as there is any logical channel having SBj>0 (SBj>0, in case there is any logical channel having SBj>0); sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1; sl-AllowedCG-List, if configured, includes the configured grant index associated to the SLgrant; if the physical sidelink feedback channel (PSFCH) corresponding to the sidelink grant associated with the serial communication interface (SCI) is not configured, sl-HARQ-FeedbackEnabled is set to disabled (sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI).

[0064] In this scenario, the data transmission method may further include: configuring the resource pool type to be a shared resource pool, that is, a terminal device configured with DRX and a terminal device not configured with DRX share a resource pool.

[0065] 2) If the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of DRX terminal devices, the target address determined by the sending device is the address corresponding to the DRX terminal device that is in an awake state in the time-frequency resource.

[0066] It can be understood that if the resource pool type is a non-shared resource pool and the non-shared resource pool only supports the services of DRX terminal devices, the data transmitted by the sending device on the side link transmission resources can be received by the DRX terminal device in the awake state; it cannot be received by the terminal device that is not configured with DRX, nor can it be received by the DRX terminal device in the sleep state (non-awake state).

[0067] In some embodiments, the target address may further include at least one logical channel and / or media access control unit with the highest priority that meets the conditions. The conditions may include at least one of the following: sidelink data is available for transmission (SL data is available for transmission); as long as there is any logical channel having SBj>0 (SBj>0, in case there is any logical channel having SBj>0); type 1 sidelink configuration grant is allowed, if configured, type 1 sidelink configuration grant is set to true (sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1); sidelink configuration grant list is allowed, if configured, includes the configured grant index associated to the SLgrant (sl-AllowedCG-List, if configured, includes the configured grant index associated to the SLgrant); if the PSFCH corresponding to the sidelink grant associated with the SCI is not configured, sl-HARQ-FeedbackEnabled is set to disabled (sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI).

[0068] 3) If the resource pool type is a non-shared resource pool, and the non-shared resource pool supports the services of the DRX terminal device and the services of the terminal device not configured with DRX, then the target address determined by the sending device is the address corresponding to the terminal device not configured with DRX; or, the target address is the address corresponding to the DRX terminal device that is in the awake state in the time-frequency resource.

[0069] It can be understood that if the resource pool type is a non-shared resource pool, and the non-shared resource pool supports the services of the DRX terminal device and the services of the terminal device that is not configured with DRX, then the data transmitted by the sending device on the side link transmission resource can be received by the DRX terminal device in the awakened state, and can also be received by the terminal device that is not configured with DRX.

[0070] In some embodiments, the target address may further include at least one logical channel and / or media access control unit with the highest priority that meets the conditions. The conditions may include at least one of the following: sidelink data is available for transmission (SL data is available for transmission); as long as there is any logical channel having SBj>0 (SBj>0, in case there is any logical channel having SBj>0); type 1 sidelink configuration grant is allowed, if configured, type 1 sidelink configuration grant is set to true (sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1); sidelink configuration grant list is allowed, if configured, includes the configured grant index associated to the SLgrant (sl-AllowedCG-List, if configured, includes the configured grant index associated to the SLgrant); if the PSFCH corresponding to the sidelink grant associated with the SCI is not configured, sl-HARQ-FeedbackEnabled is set to disabled (sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI).

[0071] 4) If the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of terminal devices that are not configured with DRX, then the target address is the address corresponding to the terminal device that is not configured with DRX.

[0072] It can be understood that if the resource pool type is a non-shared resource pool and the non-shared resource pool only supports the services of terminal devices that are not configured with DRX, the data transmitted by the sending device on the side link transmission resources can be received by terminal devices that are not configured with DRX.

[0073] In some embodiments, the target address may further include at least one logical channel and / or media access control unit with the highest priority that meets the conditions. The conditions may include at least one of the following: sidelink data is available for transmission (SL data is available for transmission); as long as there is any logical channel having SBj>0 (SBj>0, in case there is any logical channel having SBj>0); type 1 sidelink configuration grant is allowed, if configured, type 1 sidelink configuration grant is set to true (sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1); sidelink configuration grant list is allowed, if configured, includes the configured grant index associated to the SLgrant (sl-AllowedCG-List, if configured, includes the configured grant index associated to the SLgrant); if the PSFCH corresponding to the sidelink grant associated with the SCI is not configured, sl-HARQ-FeedbackEnabled is set to disabled (sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI).

[0074] In an embodiment of the present application, the service corresponding to the DRX terminal device may mean that the service is for the terminal device configured with DRX; the service corresponding to the terminal device not configured with DRX may mean that the service is for the terminal device not configured with DRX; the service corresponding to the terminal device configured with DRX and the terminal device not configured with DRX may mean that the service is for the terminal device not configured with DRX and the terminal device configured with DRX; if the service corresponds to the terminal device configured with DRX and the terminal device not configured with DRX, the service can be transmitted via multicast or broadcast.

[0075] In some embodiments, the data transmission method may further include:

[0076] Step S202: The sending device transmits data to the device corresponding to the target address.

[0077] In some embodiments, after determining the target address, the sending device selects a logical channel that meets the conditions in the target address according to the LCP criterion, and generates data (such as MAC PDU) to be sent to the target address.

[0078] In the embodiment of the present application, the process of the sending device selecting the logical channel for sending the MAC PDU can be as follows: Figure 4 As shown: the sending device obtains the side link authorization information, and the sending device determines the type of resource pool; if the type of the resource pool is a non-shared resource pool, and the non-shared resource pool only supports the services of terminal devices that are not configured with DRX, the sending device selects a target address set including the address corresponding to the terminal device that is not configured with DRX. If the type of the resource pool is a non-shared resource pool, and the non-shared resource pool only supports the services of terminal devices that are configured with DRX, the sending device selects a target address set including the address corresponding to the terminal device that is configured with DRX. If the type of the resource pool is a shared resource pool, and the shared resource pool supports the services of terminal devices that are configured with DRX and the services of terminal devices that are not configured with DRX, the sending device selects a target address set including the address corresponding to the terminal device that is configured with DRX and the address corresponding to the terminal device that is not configured with DRX. Finally, the sending device selects a logical channel from the selected address to send the MAC PDU.

[0079] In an embodiment of the present application, a transmitting device determines a set of available target addresses based on the time-frequency resources and / or resource pool type of the sidelink. When the transmitting device transmits data to the determined target address using the time-frequency resources, the device corresponding to the target address can effectively receive the data, thereby achieving effective transmission of the sidelink data. For example, if the transmitting device determines that the device corresponding to the target address (receiving device) is a DRX terminal, the receiving device detects the sidelink control information in an awake state or an activated state to receive data, thereby avoiding the receiving device being unable to receive data due to the transmitting device transmitting data when the receiving device is in a dormant or deactivated state, thereby improving data transmission efficiency.

[0080] Another optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 5 As shown, the following steps are included:

[0081] Step S301: A receiving device receives data according to whether the receiving device is configured with DRX and / or resource pool type.

[0082] In some embodiments, whether the receiving device is configured with DRX may include: the receiving device is configured with DRX or the receiving device is not configured with DRX; if the receiving device is configured with DRX, the receiving device is a DRX device.

[0083] In some embodiments, the resource pool type may include: a shared resource pool or a non-shared resource pool.

[0084] The following describes whether the receiving device is configured with DRX and the resource pool type.

[0085] 1) If the resource pool type is a shared resource pool and the receiving device is configured with DRX, the receiving device receives the sidelink data transmitted by the sending device in an awake state, and the receiving device does not receive the sidelink data in a non-awakened state or an inactive state; that is, the receiving device detects the sidelink control information in an active state to receive the sidelink data, and does not detect the sidelink control information in a non-awakened state or an inactive state.

[0086] 2) If the resource pool type is a shared resource pool and the receiving device is not configured with DRX, the receiving device continuously receives the data, that is, the receiving device always detects the sidelink control information to receive the sidelink data.

[0087] 3) If the resource pool type is a non-shared resource pool and the non-shared resource pool supports services of both DRX terminal devices and services of terminal devices not configured with DRX, the receiving device receives the data in an awake state, or the receiving device continuously receives the data. That is, a DRX-configured receiving device detects sidelink control information in an awake state to receive sidelink data, and a DRX-not configured receiving device continuously detects sidelink control information to receive sidelink data.

[0088] 4) If the resource pool type is a non-shared resource pool, the non-shared resource pool only supports the services of the DRX terminal device, and the receiving device is configured with DRX, then the receiving device receives the data in the awake state, that is, the receiving device detects the side control information in the awake state to receive the side data.

[0089] 5) If the resource pool type is a non-shared resource pool, the non-shared resource pool only supports the services of terminal devices that are not configured with DRX, and the receiving device is not configured with DRX, then the receiving device continuously receives the data, that is, the receiving device that is not configured with DRX continuously detects side control information to receive side data.

[0090] In some embodiments, the transmitting device and the receiving device may be terminal devices in sideline transmission.

[0091] In an embodiment of the present application, a transmitting device determines a set of available target addresses based on the time-frequency resources and / or resource pool type of the sidelink, so that when the transmitting device transmits data to the determined target address using the time-frequency resources, the device corresponding to the target address can effectively receive the data, thereby achieving effective transmission of the sidelink data. For example, if the transmitting device determines that the device corresponding to the target address (receiving device) is a DRX terminal, the receiving device detects the sidelink control information in an awake state or an activated state to receive data, thereby avoiding the receiving device being unable to receive data due to the transmitting device transmitting data when the receiving device is in a dormant or deactivated state, thereby improving data transmission efficiency.

[0092] Another optional processing flow of the data transmission method provided in the embodiment of the present application is as follows: Figure 6 As shown, the following steps are included:

[0093] Step S401: A sending device sends a second message to a receiving device, where the second message is used to instruct the receiving device to enter a DRX inactive state.

[0094] Specifically, the sending device sends the second message to at least one target address, and each of the at least one target address corresponds to an address of a terminal device.

[0095] In some implementations, before the sending device sends the second message to at least one target address, the sending device receives indication information sent by a network, where the indication information is used to instruct the sending device to send the second message to the at least one target address.

[0096] In some embodiments, after the sending device sends the second message to at least one target address, the sending device sends a notification message to the network, where the notification message is used to report to the network that the terminal device corresponding to the at least one target address has entered the DRX inactive state.

[0097] In one embodiment of the above solution, the second message is a MAC CE. For a MAC CE in sidelink DRX (SL DRX), if the transmitting device (i.e., TX UE) is in a connected state and / or a first mode (mode 1), the transmission resource configuration of the transmitting device comes from the network. Therefore, the transmission of the MAC CE can be controlled by the network, that is, the network instructs the transmitting device whether to send the MAC CE. Furthermore, in some embodiments, after sending the MAC CE, the transmitting device reports a notification message to the network.

[0098] In order to implement the data transmission method provided in the embodiment of the present application, the embodiment of the present application further provides a sending device, and the optional component structure of the sending device 500 is as follows: Figure 7 As shown, including:

[0099] The processing unit 501 is configured to determine a set of available target addresses based on sidelink authorization information, where the sidelink authorization information includes: time-frequency resources and / or resource pool type, and at least one target address in the set of available target addresses is used for the sending device to generate data.

[0100] In some embodiments, the set of available target addresses includes addresses corresponding to terminal devices that are not configured with discontinuous reception (DRX);

[0101] Alternatively, the available target address set includes addresses corresponding to DRX terminal devices that are in an awake state in the time-frequency resources.

[0102] In some embodiments, the sending device further includes:

[0103] The sending unit 502 is configured to report a first message to the network if there is no available target address set in the time-frequency resources configured by the sidelink grant information and / or in the resource pool.

[0104] In some embodiments, if the sidelink grant information comes from the network, the first message is used to indicate that the sidelink grant resources configured by the network are unavailable and / or the current target address is in a DRX inactive state. Here, the current target address refers to the target address for sidelink communication with the transmitting device.

[0105] In some embodiments, the first message is physical layer signaling or MAC CE or RRC signaling.

[0106] In some embodiments, the resource pool type is a shared resource pool.

[0107] In some embodiments, the resource pool type is a non-shared resource pool, and the non-shared resource pool supports services of DRX terminal devices and services of terminal devices that are not configured with DRX.

[0108] In some embodiments, the set of available target addresses includes addresses corresponding to DRX terminal devices that are in an awake state on the time-frequency resources.

[0109] In some embodiments, the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of DRX terminal devices.

[0110] In some embodiments, the set of available target addresses includes addresses corresponding to terminal devices that are not configured with DRX.

[0111] In some embodiments, the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of terminal devices that are not configured with DRX.

[0112] In some embodiments, the transmission resources in the shared resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX.

[0113] In some embodiments, the transmission resources in the non-shared resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX;

[0114] Alternatively, the transmission resources in the non-shared resource pool are used to configure a DRX terminal device;

[0115] Alternatively, the transmission resources in the non-shared resource pool are used for terminal devices that are not configured with DRX.

[0116] In some embodiments, the configuration file corresponding to the data can be determined based on information about the data to be sent, and the configuration file is used to indicate an available protocol version.

[0117] In some embodiments, the resource pool and the configuration file have a corresponding relationship, and the resource pool supports the configuration file having the corresponding relationship therewith.

[0118] In some embodiments, the protocol version is used to indicate at least one of the following information:

[0119] The service corresponds to a terminal device configured with DRX;

[0120] The service corresponds to a terminal device that is not configured with DRX;

[0121] The service corresponds to a terminal device configured with DRX and a terminal device not configured with DRX;

[0122] The destination address corresponding to the service is the address of the terminal device configured with DRX;

[0123] The destination address corresponding to the service is the address of the terminal device that is not configured with DRX.

[0124] In some embodiments, the set of available target addresses includes at least one logical channel and / or media access control element with the highest priority that meets the conditions.

[0125] In some embodiments, the sending device 500 further includes:

[0126] The sending unit 502 is configured to transmit the data to the device corresponding to the target address.

[0127] In some embodiments, the data is sideline data.

[0128] In order to implement the data transmission method provided in the embodiment of the present application, the embodiment of the present application further provides a receiving device, and the optional component structure of the receiving device 600 is as follows: Figure 8 As shown, including:

[0129] The receiving unit 601 is configured to receive data according to whether the receiving device is configured with discontinuous reception (DRX) and / or resource pool type.

[0130] In some embodiments, the receiving unit 601 is configured to receive the data in an awake state if the resource pool type is a shared resource pool and the receiving device is configured with DRX.

[0131] In some embodiments, the receiving unit 601 is configured to continuously receive the data if the resource pool type is a shared resource pool and the receiving device is not configured with DRX.

[0132] In some embodiments, the receiving unit 601 is configured to receive the data in an awake state, or the receiving device continuously receives the data, if the resource pool type is a non-shared resource pool and the non-shared resource pool supports services of terminal devices configured with DRX and services of terminal devices not configured with DRX.

[0133] In some embodiments, the receiving unit 601 is configured to receive the data in an awake state if the resource pool type is a non-shared resource pool, the non-shared resource pool only supports services of terminal devices configured with DRX, and the receiving device is configured with DRX.

[0134] In some embodiments, the receiving unit 601 is configured to continuously receive the data if the resource pool type is a non-shared resource pool, the non-shared resource pool only supports services of terminal devices that are not configured with DRX, and the receiving device is not configured with DRX.

[0135] In some embodiments, the data is sideline data.

[0136] It should be noted that in the embodiment of the present application, the function of the processing unit 501 can be implemented by a processor, the function of the sending unit 502 can be implemented by a transmitter or a transceiver, and the function of the receiving unit 601 can be implemented by a receiver or a transceiver.

[0137] In order to implement the data transmission method provided in the embodiment of the present application, the embodiment of the present application further provides a sending device, and the optional component structure of the sending device 500 is as follows: Figure 9 As shown, including:

[0138] The sending unit 502 is configured to send a second message to the receiving device, where the second message is used to instruct the receiving device to enter a DRX inactive state.

[0139] In some embodiments, the sending unit 502 is configured to send the second message to at least one target address, each of the at least one target address corresponds to an address of a terminal device.

[0140] In some embodiments, the sending device further includes:

[0141] The receiving unit 601 is configured to receive indication information sent by the network, where the indication information is used to instruct the sending device to send a second message to the at least one target address.

[0142] In some embodiments, the sending unit 502 is further configured to send a notification message to the network, where the notification message is used to report to the network that the terminal device corresponding to the at least one target address has entered the DRX inactive state.

[0143] It should be noted that, in the embodiment of the present application, the function of the sending unit 502 can be implemented by a transmitter or a transceiver, and the function of the receiving unit 601 can be implemented by a receiver or a transceiver.

[0144] An embodiment of the present application also provides a sending device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the steps of the data transmission method executed by the above-mentioned sending device when running the computer program.

[0145] An embodiment of the present application also provides a receiving device, comprising a processor and a memory for storing a computer program that can be run on the processor, wherein the processor is configured to execute the steps of the data transmission method executed by the above-mentioned receiving device when running the computer program.

[0146] An embodiment of the present application further provides a chip, including: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned sending device.

[0147] An embodiment of the present application further provides a chip, comprising: a processor, configured to call and execute a computer program from a memory, so that a device equipped with the chip executes the data transmission method executed by the above-mentioned receiving device.

[0148] An embodiment of the present application further provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned sending device.

[0149] An embodiment of the present application further provides a storage medium storing an executable program, which, when executed by a processor, implements the data transmission method executed by the above-mentioned receiving device.

[0150] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned sending device.

[0151] An embodiment of the present application further provides a computer program product, including computer program instructions, which enable a computer to execute the data transmission method executed by the above-mentioned receiving device.

[0152] An embodiment of the present application further provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned sending device.

[0153] An embodiment of the present application further provides a computer program, which enables a computer to execute the data transmission method executed by the above-mentioned receiving device.

[0154] Figure 10 700 is a schematic diagram of the hardware structure of an electronic device (sending device or receiving device) according to an embodiment of the present application. The electronic device 700 includes: at least one processor 701, a memory 702, and at least one network interface 704. The various components in the electronic device 700 are coupled together through a bus system 705. It can be understood that the bus system 705 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 705 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 10 Various buses are labeled as bus system 705.

[0155] It is understood that memory 702 can be volatile memory or non-volatile memory, or can include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM); magnetic surface memory can be magnetic disk memory or magnetic tape memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 702 described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memories.

[0156] The memory 702 in the embodiment of the present application is used to store various types of data to support the operation of the electronic device 700. Examples of such data include any computer program for operating on the electronic device 700, such as the application 7022. The program for implementing the method of the embodiment of the present application may be included in the application 7022.

[0157] The methods disclosed in the above embodiments of the present application can be applied to or implemented by the processor 701. The processor 701 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the hardware integrated logic circuit in the processor 701 or by instructions in the form of software. The above processor 701 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 701 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 702. The processor 701 reads the information in the memory 702 and completes the steps of the above method in combination with its hardware.

[0158] In an exemplary embodiment, the electronic device 700 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field programmable gate arrays (FPGAs), general-purpose processors, controllers, micro control units (MCUs), micro processors (MPUs), or other electronic components to perform the aforementioned method.

[0159] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0160] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0161] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0162] It should be understood that the terms "system" and "network" are often used interchangeably in this application. The term "and / or" in this application simply describes a relationship between associated 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 application generally indicates that the associated objects are in an "or" relationship.

[0163] The above is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A data transmission method, the method comprising: The sending device determines a set of available target addresses according to the sidelink authorization information and the information of the data to be sent, wherein the sidelink authorization information includes: time-frequency resources, and the information of the data to be sent includes: a configuration file corresponding to the data to be sent; when the version of the protocol indicated by the configuration file is R17, the sending device considers whether to send the service corresponding to the data to be sent to a receiving device configured with a discontinuous reception DRX mechanism when transmitting the service corresponding to the data to be sent; at least one target address in the set of available target addresses is used by the sending device to generate data corresponding to the data to be sent; the version of the protocol is used to indicate at least one of the following information: the service corresponds to a terminal device configured with DRX; the service corresponds to a terminal device not configured with DRX; If there is no available target address set within the time-frequency resources configured by the side link authorization information, the sending device reports a first message to the network.

2. The method according to claim 1, wherein: The available target address set includes addresses corresponding to terminal devices that are not configured with DRX; Alternatively, the set of available target addresses includes addresses corresponding to terminal devices configured with DRX that are in an awake state when the time-frequency resources are in an awake state.

3. The method according to claim 1, wherein: If the sidelink grant information comes from the network, the first message is used to indicate that the sidelink grant resources configured by the network are unavailable and / or the current target addresses are in a DRX inactive state.

4. The method according to claim 1, wherein: The first message is physical layer signaling or media access control MAC control element CE or radio resource control RRC signaling.

5. The method according to any one of claims 1 to 4, wherein: The configuration file corresponding to the data to be sent is determined by information of the data to be sent, and the configuration file is used to indicate an available protocol version.

6. The method according to claim 5, wherein: The protocol version is also used to indicate at least one of the following information: The service corresponds to a terminal device configured with DRX and a terminal device not configured with DRX; The destination address corresponding to the service is the address of the terminal device configured with DRX; The destination address corresponding to the service is the address of a terminal device that is not configured with DRX.

7. The method according to any one of claims 1 to 4, wherein: The available target address set includes at least one logical channel and / or media access control unit with the highest priority that meets the conditions.

8. The method according to any one of claims 1 to 4, wherein: The method further comprises: The sending device transmits data corresponding to the data to be sent to the device corresponding to the target address.

9. The method according to any one of claims 1 to 4, wherein: The data corresponding to the data to be sent is sideline data.

10. A sending device, comprising: a processing unit configured to determine a set of available target addresses according to sidelink authorization information and information about data to be sent, wherein the sidelink authorization information includes: time-frequency resources, and the information about the data to be sent includes: a configuration file corresponding to the data to be sent; when the version of the protocol indicated by the configuration file is R17, the sending device considers whether to send the service corresponding to the data to be sent to a receiving device configured with a discontinuous reception DRX mechanism when transmitting the service corresponding to the data to be sent; at least one target address in the set of available target addresses is used by the sending device to generate data corresponding to the data to be sent; The sending unit is configured to report a first message to the network if there is no available target address set within the time-frequency resources configured by the side link authorization information; the version of the protocol is used to indicate at least one of the following information: the service corresponds to a terminal device configured with DRX; the service corresponds to a terminal device not configured with DRX.

11. The transmitting device according to claim 10, wherein: If the sidelink grant information comes from the network, the first message is used to indicate that the sidelink grant resources configured by the network are unavailable and / or the current target addresses are in a DRX inactive state.

12. The transmitting device according to claim 10, wherein: The first message is physical layer signaling or media access control MAC control element CE or radio resource control RRC signaling.

13. The transmitting device according to any one of claims 10 to 12, wherein: The available target address set includes addresses corresponding to terminal devices that are not configured with DRX; Alternatively, the set of available target addresses includes addresses corresponding to DRX terminal devices that are in an awake state in the time-frequency resources.

14. The transmitting device according to any one of claims 10 to 12, wherein: The configuration file corresponding to the data to be sent is determined by information of the data to be sent, and the configuration file is used to indicate an available protocol version.

15. The transmitting device according to claim 14, wherein: The protocol version is also used to indicate at least one of the following information: The service corresponds to a terminal device configured with DRX and a terminal device not configured with DRX; The destination address corresponding to the service is the address of the terminal device configured with DRX; The destination address corresponding to the service is the address of a terminal device that is not configured with DRX.

16. The transmitting device according to any one of claims 10 to 12, wherein: The available target address set includes at least one logical channel and / or media access control unit with the highest priority that meets the conditions.

17. The transmitting device according to any one of claims 10 to 12, wherein: The sending device also includes: The sending unit is configured to transmit data corresponding to the data to be sent to the device corresponding to the target address.

18. The transmitting device according to any one of claims 10 to 12, wherein: The data corresponding to the data to be sent is sideline data.

19. A transmitting device comprising a processor and a memory for storing a computer program that can be run on the processor, wherein: When the processor is used to run the computer program, the processor executes the steps of the data transmission method according to any one of claims 1 to 9.

20. A storage medium storing an executable program, wherein when the executable program is executed by a processor, the data transmission method according to any one of claims 1 to 9 is implemented.

21. A computer program product, comprising computer program instructions, which enable a computer to execute the data transmission method according to any one of claims 1 to 9.

22. A chip, comprising: A processor, used to call and run a computer program from a memory, so that a device equipped with the chip executes the data transmission method as described in any one of claims 1 to 9.

Images