WO2022160804A1 - 一种数据传输方法、电子设备及存储介质 - Google Patents

一种数据传输方法、电子设备及存储介质 Download PDF

Info

Publication number
WO2022160804A1
WO2022160804A1 PCT/CN2021/125886 CN2021125886W WO2022160804A1 WO 2022160804 A1 WO2022160804 A1 WO 2022160804A1 CN 2021125886 W CN2021125886 W CN 2021125886W WO 2022160804 A1 WO2022160804 A1 WO 2022160804A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
resource pool
data
shared resource
sending device
Prior art date
Application number
PCT/CN2021/125886
Other languages
English (en)
French (fr)
Inventor
冷冰雪
卢前溪
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/CN2021/073853 external-priority patent/WO2022160106A1/zh
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP21922395.5A priority Critical patent/EP4175398A4/en
Priority to CN202180042357.4A priority patent/CN115699981A/zh
Publication of WO2022160804A1 publication Critical patent/WO2022160804A1/zh
Priority to US18/166,545 priority patent/US20230262834A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the technical field of sideline transmission, and in particular, to a data transmission method, an electronic device and a storage medium.
  • NR-V2X New Radio-Vehicle to Everything
  • Embodiments of the present application provide a data transmission method, an electronic device, and a storage medium, which can realize effective data transmission.
  • an embodiment of the present application provides a data transmission method, including: a sending device determining a set of available target addresses according to sidelink authorization information, where the sidelink authorization information includes: time-frequency resources and/or resource pools type, at least one target address in the set of available target addresses is used for the sending device to generate data.
  • 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 (Discontinuous Reception, DRX) and/or a resource pool type.
  • a receiving device receives data according to whether the receiving device is configured with discontinuous reception (Discontinuous Reception, DRX) and/or a resource pool type.
  • DRX discontinuous Reception
  • an embodiment of the present application provides a sending device and a processing unit configured to determine a set of available target addresses according to sidelink authorization information, where the sidelink authorization information includes: time-frequency resources and/or resource pools type, at least one target address in the set of available target addresses is used for the sending device to generate data.
  • an embodiment of the present application provides a receiving device, where the receiving device includes: a receiving unit configured to receive data according to whether the receiving device is configured with DRX and/or a resource pool type.
  • an embodiment of the present application provides a sending device, including 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 sending when the computer program is executed. The steps of the data transfer method performed by the device.
  • an embodiment of the present application provides a receiving device, including 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 above-mentioned receiving device when the computer program is executed. The steps of the data transfer method performed by the device.
  • an embodiment of the present application provides a chip, including: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the data transmission method executed by the sending device.
  • an embodiment of the present application provides a chip, including: a processor for calling and running a computer program from a memory, so that a device installed with the chip executes the data transmission method executed by the receiving device.
  • an embodiment of the present application provides a storage medium that stores an executable program, and when the executable program is executed by a processor, implements the data transmission method executed by the above-mentioned sending device.
  • an embodiment of the present application provides a storage medium that stores an executable program, and when the executable program is executed by a processor, implements the data transmission method executed by the receiving device.
  • an embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute the data transmission method executed by the above-mentioned sending device.
  • an embodiment of the present application provides a computer program product, including computer program instructions, the computer program instructions causing a computer to execute the data transmission method executed by the above receiving device.
  • an embodiment of the present application provides a computer program, where the computer program causes a computer to execute the data transmission method executed by the sending device.
  • an embodiment of the present application provides a computer program, where the computer program causes a computer to execute the data transmission method executed by the receiving device.
  • FIG. 1 is a schematic flowchart of selecting transmission resources under the first mode of the present application
  • FIG. 3 is a schematic diagram of an optional processing flow of the data transmission method provided by the embodiment of the present application.
  • FIG. 4 is a schematic diagram of a sending device sending a MAC PDU according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of another optional processing flow of the data transmission method provided by the embodiment of the present application.
  • FIG. 6 is a schematic diagram of another optional processing flow of the data transmission method provided by the embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an optional composition of a sending device provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an optional composition of a receiving device provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of another optional composition structure of the sending device provided by the embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a hardware composition of an electronic device provided by an embodiment of the present application.
  • D2D communication is a transmission technology based on Sidelink (SL), which is different from the way in which communication data is received or sent through network devices in traditional cellular systems, so it has a higher frequency spectrum.
  • SL Sidelink
  • the Internet of Vehicles system adopts the D2D communication method (that is, the method of device-to-device direct communication).
  • the Third Generation Partnership Project (3GPP) defines two transmission modes: a first mode (also referred to as mode A) and a second mode (also referred to as mode B).
  • the first mode is that the network device allocates transmission resources to the terminal device
  • the second mode is that the terminal device autonomously selects transmission resources.
  • the transmission resources of the terminal equipment are allocated by the network equipment, and the terminal equipment sends data on the side link according to the resources allocated by the network equipment; the network equipment can allocate a single resources for secondary transmission, and resources for semi-static transmission can also be allocated to terminal devices.
  • the terminal device selects a transmission resource in the resource pool to send data.
  • the terminal device can be in the first mode or the second mode; the terminal device can also be in the mixed mode, that is, the terminal device can obtain transmission resources through the first mode, and can also obtain transmission resources through the second mode at the same time .
  • the way that the terminal device obtains the transmission resources can be indicated by the network device through the sidelink authorization.
  • the network device through the sidelink authorization indicates the corresponding Physical Sidelink Control Channel (PSCCH) and the physical The time-frequency position of the Physical Sidelink Shared Channel (PSSCH).
  • the resource pool (Resource Pool, RP) configuration in the NR-V2X system limits the time-frequency resource range of sideline communication.
  • the minimum time-domain granularity of resource pool configuration is one subframe
  • the minimum time-domain granularity of resource pool configuration is one time slot
  • the subframe or time slot contained in the resource pool is sent by the network device
  • the radio resource control (Radio Resource Control, RRC) signaling is indicated in the form of a bitmap, so that the terminal device can flexibly select the position of the time slot or subframe in the resource pool.
  • the minimum frequency domain granularity of the resource pool is a sub-channel (sub-channel), and a sub-channel is a plurality of consecutive physical resource blocks (Physical Resource Block, PRB) in the frequency domain.
  • the minimum sub-channel is 4 consecutive PRBs, and the maximum sub-channel is 100 consecutive PRBs (corresponding to the maximum channel bandwidth of 20MHz).
  • Multiple Access SC-FDMA
  • a sub-channel in NR-V2X can be 10, 12, 15, 20, 25, 50, 75, or 100 PRBs, because only Cyclic Prefix-Orthogonal Frequency Division Multiplexing (Cyclic Prefix-Orthogonal Frequency Division) is supported in NR-V2X.
  • the sub-channels in the resource pool must also be continuous in the frequency domain.
  • the frequency domain included in the resource pool The resource shall be located within one SL bandwidth part (BandWidthPart, BWP).
  • HARQ Hybrid Automatic Repeat reQuest
  • the position of the resource pool in the time domain can be configured, for example, the resource pool is not continuous in the time domain, so that the terminal device can Data is sent and/or received discontinuously on the sidelink, thereby saving power.
  • the IoV system is required for the vehicle-vehicle communication scenario, which is mainly oriented to the relatively high-speed moving vehicle-vehicle and vehicle-person communication services.
  • the terminal equipment is required to perform continuous transmission and reception in system design.
  • the scenario of wearable device (FeD2D) accessing the network through a mobile phone is studied, especially for the scenario of low mobile speed and low power access.
  • the network device can configure the DRX parameters of the remote terminal through a relay terminal.
  • the terminal device will discontinuously monitor the Physical Downlink Control Channel (PDCCH) according to its own DRX configuration to save power.
  • the PDCCH carries the Cell-Radio Network Temporary Identifier (C-RNTI) corresponding to the terminal device, CI-RNTI, Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI) ), blocking-wireless network temporary identifier (Interruption-Radio Network Temporary Identifier, INT-RNTI), slot format indication-wireless network temporary identifier (Slot Format Indicator-Radio Network Temporary Identifier, SFI-RNTI), semi-persistent scheduling- Channel Status Indication-Semi-Persistent Radio Network Temporary Identifier (SP-CSI-RNTI), Transmission Power Control-Physical Uplink Control Channel-Wireless Network Temporary (Transmit Power Control-Physical Uplink Control Channel-Radio Network Temporary Identifier, TPC-PUCCH-RNTI), Transmission Power Control
  • 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 Reception deactivation timer (drx-InactivityTimer), DRX downlink timer (drx-RetransmissionTimerDL), DRX uplink downlink timer (drx-RetransmissionTimerUL), DRX long cycle start offset ( drx-LongCycleStartOffset), discontinuous reception short cycle (drx-ShortCycle(optional)), short discontinuous reception cycle (the Short DRX cycle), discontinuous reception cycle timer (drx-ShortCycleTimer(optional)), hybrid automatic repeat Transmission request round-trip delay downlink timer (HARQ-RTT-TimerDL), discontinuous reception hybrid automatic repeat request round-trip delay uplink timer (drx-HARQ-RTT
  • the terminal device can be in the DRX activation state or the wake-up state under the following conditions: 1) during the running of drx-onDurationTimer or drx-InactivityTimer; 2) during the running of drx-RetransmissionTimerDL or drx-RetransmissionTimerUL; 3) ra-ContentionResolutionTimer or msgB-ResponseWindow Running period; 4) There is an unprocessed SR; 5) The PDCCH indicates that there is a new transmission period.
  • the terminal device after the terminal device obtains the authorization of the side link, it can select the target address according to certain rules, such as selecting the target address according to whether there is data transmission or data priority, etc., and assemble and send the target address according to the LCP criterion.
  • MAC PDUs MAC PDUs.
  • the device corresponding to the target address may be in a non-awake state and cannot receive data. Therefore, how to transmit data efficiently by the sending device is a problem that needs to be solved.
  • the sending device determines the target address according to the time-frequency resource and/or resource pool type included in the sidelink authorization information, so that the data transmitted by the sending device can be effectively received by the receiving device.
  • An optional processing flow of the data transmission method provided by the embodiment of the present application, as shown in FIG. 3 includes the following steps:
  • Step S201 the sending device determines an available target address set according to sidelink authorization information, the sidelink authorization information includes: time-frequency resources and/or resource pool types, at least one target address in the available target address set for the sending device to generate data.
  • the sending device may determine the set of available target addresses according to the sidelink grant information and the information of the data to be sent.
  • the sending device may be a terminal device for sending data in a sidelink transmission system.
  • the sending device may acquire the sidelink grant information in the first mode and/or the second mode, and the sidelink grant information may include time-frequency resources and/or resource pool types.
  • the sending device reports the first message to the network. Further, optionally, if the sidelink authorization information comes from the network, the first message is used to indicate that the sidelink authorization resource configured by the network is unavailable and/or the current target address is in a DRX inactive state. .
  • the current destination address refers to the destination address for sidelink communication with the transmitting device.
  • the sidelink grant resources refer to the time-frequency resources and/or resource pools configured by the sidelink grant information.
  • the first message may be physical layer signaling or MAC CE or RRC signaling.
  • the report is reported to the network, and the network can wait until the on duration timer of the next Rx UE is running.
  • the sending device ie, the sender UE (Tx UE) performs scheduling.
  • 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.
  • the resource pool and configuration files have a corresponding relationship
  • the resource pool supports configuration files that have a corresponding relationship with them.
  • a resource pool can be configured to support profile one, or to support profile two.
  • 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.
  • DRX terminal equipment and terminal equipment not configured with DRX; the destination address corresponding to the service is the address of the terminal equipment configured with DRX; and the destination address corresponding to the service is the address of the terminal equipment not configured with DRX.
  • the data to be sent may be data in a logical channel; the data data generated by the sending device may be a MAC PDU.
  • the configuration file indicates the corresponding transmission format. If the protocol version indicated by the configuration file is R14, the terminal device transmits the corresponding data packet according to the available format of R14; if the protocol version indicated by the configuration file is R15, the terminal device uses The R15-available format transmits the corresponding packet.
  • the configuration file is used to indicate that the version number of the protocol is R17, and the DRX mechanism is introduced into the R17 protocol. If the protocol version number indicated by the configuration file corresponding to the service is R17, it needs to be considered when transmitting the service. This service is sent to the receiving device configured with the DRX mechanism.
  • the time-frequency resources may be PSCCH time-frequency resources and corresponding PSSCH time-frequency resources.
  • the resource pool types may include: shared resource pools and non-shared resource pools; wherein, shared resource pools may refer to the transmission resources in the shared resource pool used to configure DRX terminal equipment and terminal equipment not configured with DRX, that is, configured with DRX.
  • the terminal equipment (that is, the DRX terminal equipment) shares the transmission resources in the resource pool with the terminal equipment that is not configured with DRX,
  • the non-shared resource pool may refer to that the transmission resources in the non-shared resource pool are used to configure DRX terminal equipment and the terminal equipment that is not configured with DRX; or, the transmission resources in the non-shared resource pool are used to configure DRX terminal equipment; Alternatively, the transmission resources in the non-shared resource pool are used for terminal devices without DRX; that is, the resources in the non-shared resource pool are only used for terminal devices configured with DRX, or the resources in the resource pool are only used for terminals without DRX The device is used, or the resources in the resource pool are used by the terminal device configured with DRX and the terminal device not configured with DRX.
  • the target address determined by the sending device is the address corresponding to the terminal device not configured with DRX; or, the target address determined by the sending device is at the time-frequency The address corresponding to the DRX terminal device whose resource is in the awake state.
  • the terminal device corresponding to the target address is not configured with DRX, the terminal device is in a state of continuously receiving data, and the data transmitted by the sending device on the sidelink transmission resources can be received by the terminal device. If the terminal device corresponding to the target address is configured with a DRX terminal device and the terminal device is in an awake state, the data transmitted by the sending device on the sidelink transmission resources can also be received by the terminal device.
  • the target address may further include at least one logical channel with the highest priority and/or a medium access control control unit that satisfies the condition.
  • the conditions may include at least one of the following: side row data is available for transmission (SL data is available for transmission); as long as there is one logical channel with SBj>0 (SBj>0, in case there is any logical channel having SBj>0); allows type 1 sideline configuration authorization, if configured, type 1 sideline configuration authorization is set to true (sl-configuredGrantType1Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1 ); allow the sideline configuration grant list, if configured, including the configuration grant index associated with the sideline grant (sl-AllowedCG-List, if configured, includes the configured grant index associated to the SL grant); if the sideline associated with the SCI The PSFCH corresponding to the row grant is set to not be fed back (sl-HARQ-FeedbackEnabled is set to
  • the data transmission method may further include: configuring the type of the resource pool to be a shared resource pool, that is, configuring the DRX terminal device to share the resource pool with the terminal device not configured with DRX.
  • the target address determined by the sending device is the one that is in an awake state when the time-frequency resource is in an awake state.
  • the data transmitted by the sending device on the sidelink transmission resources can be in an awake state. It cannot be received by the DRX terminal equipment that is not configured with DRX, nor can it be received by the DRX terminal equipment in the dormant state (non-awakening) state.
  • the target address may further include at least one logical channel with the highest priority and/or a medium access control control unit that satisfies the condition.
  • the conditions may include at least one of the following: SL data is available for transmission; 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 SL grant; sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI.
  • the target address determined by the sending device is not configured The address corresponding to the DRX terminal device; or, the target address is the address corresponding to the DRX terminal device in the wake-up state of the time-frequency resource.
  • the sending device transmits the data on the sidelink.
  • the data transmitted on the resource can be received by a DRX terminal device in an awake state, and can also be received by a terminal device not configured with DRX.
  • the target address may further include at least one logical channel with the highest priority and/or a medium access control control unit that satisfies the condition.
  • the conditions may include at least one of the following: SL data is available for transmission; 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 SL grant; sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI.
  • the target address is an address corresponding to the terminal equipment not configured with DRX.
  • the type of the resource pool is a non-shared resource pool and the non-shared resource pool only supports services of terminal devices without DRX configured, the data transmitted by the sending device on the sidelink transmission resources Can be received by terminal devices not configured with DRX.
  • the target address may further include at least one logical channel with the highest priority and/or a medium access control control unit that satisfies the condition.
  • the conditions may include at least one of the following: SL data is available for transmission; 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 SL grant; sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI.
  • the service corresponding to the DRX terminal equipment may refer to the service for the terminal equipment configured with DRX; the service corresponding to the terminal equipment not configured with DRX may refer to the service for the terminal equipment not configured with DRX
  • the service corresponding to terminal equipment configured with DRX and terminal equipment without DRX may mean that the service is for terminal equipment without DRX and terminal equipment configured with DRX; if all If the service corresponds to a terminal device configured with DRX and a terminal device not configured with DRX, the service can be transmitted by multicast or broadcast.
  • the data transmission method may further include:
  • Step S202 the sending device transmits data to the device corresponding to the target address.
  • the sending device after determining the target address, selects a logical channel in the target address that meets the conditions according to the LCP criterion, and generates data (such as a MAC PDU) to be sent to the target address.
  • the process for the sending device to select a logical channel for sending MAC PDUs may be as shown in Figure 4: the sending device obtains the sidelink authorization information, and the sending device determines the type of the resource pool; if the type of the resource pool is If there is a non-shared resource pool, and the non-shared resource pool only supports services of terminal devices not configured with DRX, the sending device selects the target address set to include addresses corresponding to the terminal devices 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 services of terminal equipment configured with DRX, the sending device selects the target address set including addresses corresponding to the terminal equipment configured with DRX.
  • the sending device selects the target address set including the address corresponding to the terminal device configured with DRX The address corresponding to the terminal device that is not configured with DRX. Finally, the sending device selects the logical channel in the selected address to send the MAC PDU.
  • the sending device determines the set of available target addresses according to the time-frequency resources and/or the resource pool type of the sidelink, and when the sending device transmits data to the determined target address from the time-frequency resources, the target address corresponds to The device can effectively receive the data, thereby realizing the effective transmission of sideline data. For example, if the sending device determines that the device (receiving device) corresponding to the target address is a DRX terminal, the receiving device detects the sidelink control information to receive data in an awake state or an active state; avoid the sending device when the receiving device is dormant or active. The receiving device cannot receive the data due to the data transmission in the deactivated state, which improves the data transmission efficiency.
  • Another optional processing flow of the data transmission method provided by the embodiment of the present application, as shown in FIG. 5 includes the following steps:
  • Step S301 the receiving device receives data according to whether the receiving device is configured with DRX and/or a resource pool type.
  • 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 .
  • the resource pool type may include: shared resource pool or non-shared resource pool.
  • the following describes whether the receiving device is configured with DRX and the resource pool type.
  • the receiving device receives the sideline data transmitted by the sending device in an awake state, and the receiving device is in a non-awakening state or inactive state.
  • the state does not receive sideline data; that is, the receiving device detects sideline control information to receive sideline data in an active state, and does not detect sideline control information in an inactive state or inactive state.
  • the receiving device continuously receives the data, that is, the receiving device always detects sideline control information to receive sideline data.
  • the receiving device receives the data in an awake state, Or the receiving device continuously receives the data. That is, a receiving device configured with DRX detects sideline control information in an awake state to receive sideline data, and a receiving device not configured with DRX continuously detects sideline control information to receive sideline data.
  • the resource pool type is a non-shared resource pool
  • the non-shared resource pool only supports services of DRX terminal devices, and the receiving device is configured with DRX, the receiving device receives the data in an awake state; That is, the receiving device detects sideline control information in an active state to receive sideline data.
  • 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, then the receiving device continuously receives the data. . That is, a receiving device that is not configured with DRX continuously detects sideline control information to receive sideline data.
  • the sending device and the receiving device may be terminal devices in sideline transmission.
  • the sending device determines a set of available target addresses according to the time-frequency resources and/or resource pool types of the sidelink, so that the sending device transmits data to the determined target address when the time-frequency resources transmit data to the determined target address.
  • the device corresponding to the target address can effectively receive the data, thereby realizing the effective transmission of the sideline data. For example, if the sending device determines that the device (receiving device) corresponding to the target address is a DRX terminal, the receiving device detects the sidelink control information to receive data in an awake state or an active state; avoid the sending device when the receiving device is dormant or active. The receiving device cannot receive the data due to the data transmission in the deactivated state, which improves the data transmission efficiency.
  • Another optional processing flow of the data transmission method provided by the embodiment of the present application, as shown in FIG. 6 includes the following steps:
  • Step S401 the sending device sends a second message to the receiving device, where the second message is used to instruct the receiving device to enter the DRX inactive state.
  • the sending device sends the second message to at least one target address, where each target address in the at least one target address corresponds to an address of a terminal device.
  • the sending device before the sending device sends the second message to the at least one target address, the sending device receives indication information sent by the network, where the indication information is used to instruct the sending device to send the at least one target address The destination address sends the second message.
  • the sending device after the sending device sends the second message to the 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 the information corresponding to the at least one target address
  • the terminal device has entered the DRX inactive state.
  • the second message is a MAC CE.
  • the sending device ie, the TX UE
  • the first mode ie, mode1
  • the transmission resource configuration of the sending device comes from the network, so the MAC CE's
  • the sending can be controlled by the network, that is, the network instructs the sending device whether to send the MAC CE, and further, optionally, the sending device reports a notification message to the network after sending the MAC CE.
  • the embodiment of the present application further provides a network device.
  • the optional composition structure of the sending device 500 includes:
  • the processing unit 501 is configured to determine an available target address set according to sidelink authorization information, where the sidelink authorization information includes: time-frequency resources and/or resource pool types, at least one target in the available target address set The address is used by the sending device to generate data.
  • the set of available target addresses includes addresses corresponding to terminal devices not configured to receive DRX;
  • the set of available target addresses includes addresses corresponding to the DRX terminal equipment in an awake state when the time-frequency resource is in an awake state.
  • the sending device further includes:
  • the sending unit 502 is configured to report the first message to the network if there is no available target address set in the time-frequency resource configured by the sidelink authorization information and/or in the resource pool.
  • the first message is used to indicate that the sidelink grant resource configured by the network is unavailable and/or the current target address is in a DRX inactive state .
  • the current destination address refers to the destination address for sidelink communication with the transmitting device.
  • the first message is physical layer signaling or MAC CE or RRC signaling.
  • the resource pool type is a shared resource pool.
  • the resource pool type is a non-shared resource pool, and the non-shared resource pool supports services of DRX terminal equipment and services of terminal equipment not configured with DRX.
  • the available target address may include an address corresponding to the DRX terminal device that is in an awake state on the time-frequency resource.
  • the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of DRX terminal devices.
  • the set of available target addresses includes addresses corresponding to terminal devices not configured with DRX.
  • 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.
  • the transmission resources in the shared resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX.
  • the transmission resources in the non-shared resource pool are used for terminal equipment configured with DRX and terminal equipment without DRX;
  • the transmission resources in the non-shared resource pool are used to configure the terminal equipment of DRX;
  • the transmission resources in the non-shared resource pool are used for terminal equipment not configured with DRX.
  • a configuration file corresponding to the data may be determined according to information of the data to be sent, and the configuration file is used to indicate an available protocol version.
  • the resource pool has a corresponding relationship with a configuration file, and the resource pool supports a configuration file with a corresponding relationship therewith.
  • 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 terminal equipment 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 the terminal device configured with DRX;
  • the destination address corresponding to the service is the address of the terminal device not configured with DRX.
  • the set of available target addresses includes at least one logical channel and/or medium access control control element with the highest priority that satisfies the condition.
  • the sending device 500 further includes:
  • the sending unit 502 is configured to transmit the data to the device corresponding to the target address.
  • the data is side row data.
  • the embodiment of the present application further provides a receiving device.
  • the optional composition structure of the receiving device 600 includes:
  • 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.
  • 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.
  • the receiving unit 601 is configured to continuously receive the data if the type of the resource pool is a shared resource pool and the receiving device is not configured with DRX.
  • the receiving unit 601 is configured to, if the type of the resource pool is a non-shared resource pool, and the non-shared resource pool supports the service of the terminal device configured with DRX and the service of the terminal device not configured with DRX service, the data is received in an awake state, or the receiving device continuously receives the data.
  • the receiving unit 601 is configured to, 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, the data is received in the awake state.
  • the receiving unit 601 is configured to, if the type of the resource pool 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 DRX, the data is continuously received.
  • the data is side row data.
  • the function of the processing unit 501 may be implemented by a processor
  • the function of the transmitting unit 502 may be implemented by a transmitter or a transceiver
  • the function of the receiving unit 601 may be implemented by a receiver or a transceiver.
  • the embodiment of the present application further provides a sending device.
  • the optional composition structure of the sending device 500 includes:
  • the sending unit 502 is configured to send a second message to a receiving device, where the second message is used to instruct the receiving device to enter a DRX inactive state.
  • the sending unit 502 is configured to send the second message to at least one target address, where each target address in the at least one target address corresponds to an address of a terminal device.
  • the sending device further includes:
  • the receiving unit 601 is configured to receive indication information sent by a network, where the indication information is used to instruct the sending device to send a second message to the at least one target address.
  • 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.
  • the function of the sending unit 502 may be implemented by a transmitter or a transceiver
  • the function of the receiving unit 601 may be implemented by a receiver or a transceiver.
  • An embodiment of the present application further provides a sending device, including 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 above-mentioned sending device when running the computer program.
  • a sending device including 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 above-mentioned sending device when running the computer program. The steps of the data transfer method.
  • An embodiment of the present application further provides a receiving device, including 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 above-mentioned receiving device when running the computer program.
  • the steps of the data transfer method are described in detail below.
  • 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 on which the chip is installed executes the data transmission method executed by the above-mentioned sending device.
  • 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 on which the chip is installed executes the data transmission method executed by the receiving device.
  • An embodiment of the present application further provides a storage medium storing an executable program, and when the executable program is executed by a processor, the data transmission method executed by the above-mentioned sending device is implemented.
  • An embodiment of the present application further provides a storage medium storing an executable program, and when the executable program is executed by a processor, the data transmission method performed by the above receiving device is implemented.
  • Embodiments of the present application further provide a computer program product, including computer program instructions, the computer program instructions enable a computer to execute the data transmission method executed by the above-mentioned sending device.
  • Embodiments of the present application further provide a computer program product, including computer program instructions, the computer program instructions enable a computer to execute the data transmission method executed by the above receiving device.
  • the embodiment of the present application further provides a computer program, the computer program enables the computer to execute the data transmission method executed by the above-mentioned sending device.
  • the embodiment of the present application further provides a computer program, the computer program enables the computer to execute the data transmission method executed by the receiving device.
  • FIG. 10 is a schematic diagram of a 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 , memory 702 and at least one network interface 704 .
  • the various components in electronic device 700 are coupled together by bus system 705 .
  • the bus system 705 is used to implement the connection communication between these components.
  • the bus system 705 also includes a power bus, a control bus and a status signal bus.
  • the various buses are labeled as bus system 705 in FIG. 10 .
  • memory 702 may be either volatile memory or non-volatile memory, and may include both volatile and non-volatile memory.
  • the non-volatile memory can be ROM, Programmable Read-Only Memory (PROM, Programmable Read-Only Memory), Erasable Programmable Read-Only Memory (EPROM, Erasable Programmable Read-Only Memory), Electrically Erasable Programmable Read-Only Memory Programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), magnetic random access memory (FRAM, ferromagnetic random access memory), flash memory (Flash Memory), magnetic surface memory, optical disk, or CD-ROM -ROM, Compact Disc Read-Only Memory); magnetic surface memory can be disk memory or tape memory.
  • RAM Random Access Memory
  • SRAM Static Random Access Memory
  • SSRAM Synchronous Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • SDRAM Synchronous Dynamic Random Access Memory
  • DDRSDRAM Double Data Rate Synchronous Dynamic Random Access Memory
  • ESDRAM Enhanced Type Synchronous Dynamic Random Access Memory
  • SLDRAM Synchronous Link Dynamic Random Access Memory
  • DRRAM Direct Rambus Random Access Memory
  • the memory 702 described in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.
  • the memory 702 in this 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 used to operate on electronic device 700, such as application 7022.
  • the program for implementing the method of the embodiment of the present application may be included in the application program 7022.
  • the methods disclosed in the above embodiments of the present application may be applied to the processor 701 or implemented by the processor 701 .
  • the processor 701 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above-mentioned method can be completed by an integrated logic circuit of hardware in the processor 701 or an instruction in the form of software.
  • the above-mentioned processor 701 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the processor 701 may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of this application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a storage medium, and the storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702, and completes the steps of the foregoing method in combination with its hardware.
  • the electronic device 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs) , Complex Programmable Logic Device), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic component implementation for performing the aforementioned method.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal processors
  • PLDs Programmable Logic Devices
  • CPLDs Complex Programmable Logic Devices
  • FPGA general-purpose processor
  • controller MCU, MPU, or other electronic component implementation for performing the aforementioned method.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Abstract

本申请公开了一种数据传输方法，包括：发送设备根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。本申请还公开了另一种数据传输方法、电子设备及存储介质。

Description

一种数据传输方法、电子设备及存储介质
相关申请的交叉引用
本申请基于申请号为PCT/CN2021/073853、申请日为2021年01月26日的国际申请、以及申请号为PCT/CN2021/111173、申请日为2021年08月06日的国际申请提出，并要求该国际申请的优先权，该国际申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及侧行传输技术领域，尤其涉及一种数据传输方法、电子设备及存储介质。
背景技术
在新无线-车辆到其他设备(New Radio-Vehicle to Everything，NR-V2X)系统中，发送设备接收到侧行链路授权后，如何进行有效的数据传输是一直追求的目标。
发明内容
本申请实施例提供一种数据传输方法、电子设备及存储介质，能够实现数据的有效传输。
第一方面，本申请实施例提供一种数据传输方法，包括：发送设备根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
第二方面，本申请实施例提供一种数据传输方法，包括：接收设备根据所述接收设备是否配置了非连续接收(Discontinuous Reception，DRX)和/或资源池类型接收数据。
第三方面，本申请实施例提供一种发送设备，处理单元，配置为根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
第四方面，本申请实施例提供一种接收设备，所述接收设备包括：接收单元，配置为根据所述接收设备是否配置了DRX和/或资源池类型接收数据。
第五方面，本申请实施例提供一种发送设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述发送设备执行的数据传输方法的步骤。
第六方面，本申请实施例提供一种接收设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述接收设备执行的数据传输方法的步骤。
第七方面，本申请实施例提供一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行上述发送设备执行的数据传输方法。
第八方面，本申请实施例提供一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行上述接收设备执行的数据传输方法。
第九方面，本申请实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述发送设备执行的数据传输方法。
第十方面，本申请实施例提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述接收设备执行的数据传输方法。
第十一方面，本申请实施例提供一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述发送设备执行的数据传输方法。
第十二方面，本申请实施例提供一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述接收设备执行的数据传输方法。
第十三方面，本申请实施例提供一种计算机程序，所述计算机程序使得计算机执行上述发送设备执行的数据传输方法。
第十四方面，本申请实施例提供一种计算机程序，所述计算机程序使得计算机执行上述接收设备执行的数据传输方法。
附图说明
图1为本申请第一模式下选择传输资源的流程示意图；
图2为本申请第二模式下选择传输资源的流程示意图；
图3为本申请实施例提供的数据传输方法的一种可选处理流程示意图；
图4为本申请实施例发送设备发送MAC PDU的示意图；
图5为本申请实施例提供的数据传输方法的另一种可选处理流程示意图；
图6为本申请实施例提供的数据传输方法的又一种可选处理流程示意图；
图7为本申请实施例提供的发送设备的一种可选组成结构示意图；
图8为本申请实施例提供的接收设备的一种可选组成结构示意图；
图9为本申请实施例提供的发送设备的另一种可选组成结构示意图；
图10为本申请实施例提供的电子设备的硬件组成结构示意图。
具体实施方式
为了能够更加详尽地了解本申请实施例的特点和技术内容，下面结合附图对本申请实施例的实现进行详细阐述，所附附图仅供参考说明之用，并非用来限定本申请实施例。
在对本申请实施例进行说明之前，对相关内容进行简要说明。
设备到设备(Device to Device，D2D)通信是基于侧行链路(Sidelink，SL)的传输技术，与传统的蜂窝系统中通信数据通过网络设备接收或者发送的方式不同，因此具有更高的频谱效率以及更低的传输时延，车联网系统采用D2D通信的方式(即设备到设备直接通信的方式)。对于D2D通信，第三代合作伙伴计划(Third Generation Partnership Project，3GPP)定义了两种传输模式：第一模式(也称为模式A)和第二模式(也称为模式B)。第一模式是网络设备为终端设备分配传输资源，第二模式是终端设备自主选择传输资源。
针对第一模式：如图1所示，终端设备的传输资源是由网络设备分配的，终端设备根据网络设备分配的资源在侧行链路上进行数据的发送；网络设备可以为终端设备分配单次传输的资源，也可以为终端设备分配半静态传输的资源。
针对第二模式：如图2所示，终端设备在资源池中选择一个传输资源进行数据的发送。
在NR-V2X系统中，终端设备可以处于第一模式或第二模式；终端设备也可以处于混合模式，即终端设备既可以通过第一模式获取传输资源，也可以同时通过第二模式获取传输资源。终端设备获取传输资源的方式可以是网络设备通过侧行链路授权的方式指示，如网络设备通过侧行链路授权指示相应的物理侧行控制信道(Physical Sidelink Control Channel，PSCCH)与物理侧行共享信道(Physical Sidelink Shared Channel，PSSCH)的时频位置。其中，NR-V2X系统中的资源池(Resource Pool，RP)配置限定了侧行通信的时频资源范围。
在LTE-V2X中资源池配置的最小时域粒度为一个子帧，在NR-V2X系统中资源池配置的最小时域粒度为一个时隙；资源池内包含的子帧或时隙由网络设备发送的无线资源控制(Radio Resource Control，RRC)信令以比特位图的方式指示，以便终端设备灵活的选择资源池内时隙或子帧的位置。资源池的最小频域粒度为一个子信道(sub-channel)，子信道是频域上连续的多个物理资源块(Physical Resource Block，PRB)。在LTE-V2X中最小子信道为4个连续PRB，最大的子信道为100个连续PRB(对应20MHz最大信道带宽)，由于LTE-V2X系统采用单载波频分多址(Single-carrier  Frequency-Division Multiple Access，SC-FDMA)，所以子信道内包含的PRB个数需要能够被2，3，或5整除。NR-V2X中一个子信道可以为10,12，15,20,25,50,75,或100个PRB，由于NR-V2X中仅支持循环前缀正交频分复用(Cyclic Prefix-Orthogonal Frequency Division Multiplexing，CP-OFDM)，为了降低侧行发送的峰值平均功率比(Peak to Average Power Ratio，PAPR)，资源池内的子信道在频域上也必须是连续的，此外，资源池内包含的频域资源应位于一个SL带宽部分(BandWidthPart，BWP)范围内。
在NR-V2X系统中，还引入了基于反馈的混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)重传，且不限于针对单播通信的HARQ重传，也包括针对组播通信的HARQ重传。
在3GPP版本(Rel)12/13中，针对近场通信服务(Proximity based Service，ProSe)，可通过配置资源池在时域上的位置，例如资源池在时域上非连续，达到终端设备在侧行链路上非连续发送和/或接收数据，从而达到省电的效果。
在R14/15中，车联网系统针对车-车通信的场景进行了要求，其主要面向相对高速移动的车-车、车-人通信的业务。
在V2X系统中，由于车载系统具有持续的供电，因此数据传输的时延是主要解决的问题，因此，在系统设计上要求终端设备进行连续的发送和接收。
在R14中，对于可穿戴设备(FeD2D)通过手机接入网络的场景进行了研究，尤其是针对低移动速度以及低功率接入的场景。针对FeD2D，网络设备可以通过一个中继(relay)终端配置远程(remote)终端的DRX参数。
在NR-V2X系统中，终端设备会根据自身的DRX配置不连续的监控物理下控制信道(Physical Downlink Control Channel，PDCCH)，以实现省电的目的。当PDCCH中携带与终端设备对应的小区无线网络临时标识(Cell-Radio Network Temporary Identifier，C-RNTI)，CI-RNTI、配置调度-无线网络临时标识(Configured 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 Radio Network Temporary Identifier，SP-CSI-RNTI)、传输功率控制-物理上行控制信道-无线网络临时标识(Transmit Power Control-Physical Uplink Control Channel-Radio Network Temporary Identifier，TPC-PUCCH-RNTI)、传输功率控制-物理上行控制信道-无线网络临时标识(Transmit Power Control-Physical Uplink Share Channel-Radio Network Temporary Identifier， TPC-PUSCH-RNTI)、传输功率控制-探测参考信号-无线网络临时标识(Transmit Power Control-Sounding Reference Symbols-Radio Network Temporary Identifier，TPC-SRS-RNTI)和AI-RNTI时，终端设备会根据控制信息执行相应的DRX操作。网络设备通过配置一系列参数来控制终端设备的DRX行为，网络设备配置的参数可以包括：非连续接收持续定时器(drx-onDurationTimer)、非连续接收时隙偏移(drx-SlotOffset)、非连续接收去激活定时器(drx-InactivityTimer)、非连续接收重传下行定时器(drx-RetransmissionTimerDL)、非连续接收重传上下行定时器(drx-RetransmissionTimerUL)、非连续接收长周期起始偏移(drx-LongCycleStartOffset)、非连续接收短周期(drx-ShortCycle(optional))、短非连续接收周期(the Short DRX cycle)，非连续接收端周期定时器(drx-ShortCycleTimer(optional))、混合自动重传请求往返时延下行定时器(HARQ-RTT-TimerDL)、非连续接收混合自动重传请求往返时延上行定时器(drx-HARQ-RTT-TimerUL)、ps-Wakeup(optional)、ps-TransmitOtherPeriodicCSI(optional)和ps-TransmitPeriodicL1-RSRP(optional)。
其中，终端设备在下述情况下可以处于DRX激活状态或唤醒状态：1)drx-onDurationTimer或drx-InactivityTimer运行期间；2)drx-RetransmissionTimerDL或drx-RetransmissionTimerUL运行期间；3)ra-ContentionResolutionTimer或msgB-ResponseWindow运行期间；4)有未被处理的SR；5)PDCCH指示有新的传输期间。
现有技术中，终端设备获取到侧行链路授权之后，可以根据一定的规则选取目标地址，如根据是否有数据传输或数据优先级等选取目标地址，并根据LCP准则组装发送该目标地址的MAC PDU。但是，在引入侧行链路省电机制后，可能存在目标地址对应的设备处于非唤醒状态，而无法接收数据的情况，因此，发送设备如何有效地传输数据是需要解决的问题。
本申请实施例提供的数据传输方法，发送设备根据侧行链路授权信息包括的时频资源和/或资源池类型确定目标地址，使得发送设备传输的数据能够被接收设备有效地接收。
本申请实施例提供的数据传输方法的一种可选处理流程，如图3所示，包括以下步骤：
步骤S201，发送设备根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
在一些实施例中，发送设备可以根据侧行链路授权信息和待发送数据的信息确定可用目标地址集合。
在一些实施例中，所述发送设备可以是侧行链路传输系统中的用于发送数据的终端设备。所述发送设备可通过第一模式和/或第二模式的方式获 取侧行链路授权信息，所述侧行链路授权信息可以包括时频资源和/或资源池类型。
在一些可选实施方式中，若所述侧行链路授权信息配置的时频资源内和/或资源池内不存在可用目标地址集合，则发送设备向网络上报第一消息。进一步，可选地，若所述侧行链路授权信息来自网络，则所述第一消息用于指示网络配置的侧行链路授权资源不可用和/或当前目标地址均处于DRX非激活态。这里，当前目标地址是指与发送设备进行侧行链路通信的目标地址。
需要说明的是，侧行链路授权资源是指侧行链路授权信息配置的时频资源和/或资源池。
上述方案中，可选地，所述第一消息可以为物理层信令或者MAC CE或者RRC信令。
本申请实施例中，若所有接收设备(即收方UE(Rx UE))均处于非激活状态则报告给网络，网络可以等到下一个Rx UE的状态定时器(on duration timer)运行时再为发送设备(即发方UE(Tx UE))做调度。
在一些实施例中，所述待发送数据的信息可以包括：所述待发送数据对应的配置文件(profile)，所述配置文件用于指示可用的协议的版本。
上述方案中，所述资源池和配置文件具有对应关系，所述资源池支持与其具有对应关系的配置文件。例如：资源池可以被配置为支持配置文件一，或支持配置文件二。
上述方案中，可选地，所述协议版本用于指示下述至少一种信息：所述业务对应配置了DRX的终端设备；所述业务对应未配置DRX的终端设备；所述业务对应配置了DRX的终端设备和未配置DRX的终端设备；所述业务对应的目的地址为配置了DRX的终端设备的地址；和所述业务对应的目的地址为未配置DRX的终端设备的地址。其中，所述待发送的数据可以是逻辑信道中的数据；所述发送设备生成的数据数据可以是MAC PDU。
可以理解为，配置文件指示相应的传输格式，如配置文件指示的协议版本为R14，则终端设备按照R14可用的格式传输相应的数据包；如配置文件指示的协议版本为R15，则终端设备利用R15可用的格式传输相应的数据包。举例来说，所述配置文件用于指示协议的版本号为R17，R17协议中引入了DRX机制，则若业务对应的配置文件指示的协议版本号为R17，则在传输所述业务时需考虑该业务为发送给配置了DRX机制的接收设备。
在一些实施例中，时频资源可以是PSCCH的时频资源以及对应的PSSCH的时频资源。所述资源池类型可以包括：共享资源池和非共享资源池；其中，共享资源池可以是指共享资源池内的传输资源用于配置DRX的终端设备和未配置DRX的终端设备，即配置了DRX的终端设备(即DRX终端设备)与未配置DRX的终端设备共享资源池内的传输资源，
非共享资源池可以是指所述非共享资源池内的传输资源用于配置DRX 的终端设备和未配置DRX的终端设备；或者，所述非共享资源池内的传输资源用于配置DRX的终端设备；或者，所述非共享资源池内的传输资源用于未配置DRX的终端设备；即非共享资源池内的资源仅针对配置了DRX的终端设备使用，或该资源池内的资源仅针对未配置DRX的终端设备使用，或者该资源池内的资源针对配置了DRX的终端设备和未配置DRX的终端设备使用。
下面针对不同的资源池类型分别说明。
1)若资源池的类型为共享资源池，则所述发送设备所确定的目标地址为未配置DRX的终端设备对应的地址；或者，所述发送设备所确定的目标地址为在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
可以理解为，若目标地址对应的终端设备未配置DRX，则终端设备处于连续接收数据的状态，则发送设备在侧行链路传输资源上传输的数据均能够被终端设备接收。若目标地址对应的终端设备配置了DRX的终端设备，且该终端设备处于唤醒状态，则发送设备在侧行链路传输资源上传输的数据也能够被终端设备接收。
在一些实施例中，所述目标地址还可以包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。其中，所述条件可以包括以下至少一项：侧行数据是可用于传输的(SL data is available for transmission)；只要有一个逻辑信道的SBj>0(SBj>0,in case there is any logical channel having SBj>0)；允许类型1侧行配置授权，如果被配置，类型1侧行配置授权设置为真(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 SL grant)；如果与SCI关联的侧行授权对应的PSFCH被设置为不反馈(sl-HARQ-FeedbackEnabled is set to disabled,if PSFCH is not configured for the SL grant associated to the SCI)。
在该场景下，所述数据传输方法还可以包括：配置资源池的类型为共享资源池，即配置DRX终端终端设备与未配置DRX的终端设备共享资源池。
2)若所述资源池类型为非共享资源池、且所述非共享资源池仅支持DRX终端设备的业务，则所述发送设备所确定的目标地址为在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
可以理解为，若所述资源池类型为非共享资源池、且所述非共享资源池仅支持DRX终端设备的业务，则发送设备在侧行链路传输资源上传输的数据能够被处于唤醒状态的DRX终端设备接收；不能够被未配置DRX的终端设备接收，也不能被处于休眠状态(非唤醒)状态的DRX终端设备接收。
在一些实施例中，所述目标地址还可以包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。其中，所述条件可以包括以下至少一项：SL data is available for transmission；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 SL grant；sl-HARQ-FeedbackEnabled is set to disabled,if PSFCH is not configured for the SL grant associated to the SCI。
3)若所述资源池类型为非共享资源池、且所述非共享资源池支持DRX终端设备的业务和未配置DRX的终端设备的业务，则所述发送设备所确定的目标地址为未配置DRX的终端设备对应的地址；或者，所述目标地址为在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
可以理解为，若所述资源池类型为非共享资源池、且所述非共享资源池支持DRX终端设备的业务和未配置DRX的终端设备的业务，则所述发送设备在侧行链路传输资源上传输的数据能够被处于唤醒状态的DRX终端设备接收，也能够被未配置DRX的终端设备接收。
在一些实施例中，所述目标地址还可以包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。其中，所述条件可以包括以下至少一项：SL data is available for transmission；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 SL grant；sl-HARQ-FeedbackEnabled is set to disabled,if PSFCH is not configured for the SL grant associated to the SCI。
4)若所述资源池类型为非共享资源池、且所述非共享资源池仅支持未配置DRX的终端设备的业务，则所述目标地址为未配置DRX的终端设备对应的地址。
可以理解为，若所述资源池类型为非共享资源池、且所述非共享资源池仅支持未配置DRX的终端设备的业务，则所述发送设备在侧行链路传输资源上传输的数据能够被未配置DRX的终端设备接收。
在一些实施例中，所述目标地址还可以包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。其中，所述条件可以包括以下至少一项：SL data is available for transmission；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 SL grant；sl-HARQ-FeedbackEnabled is set to disabled,if PSFCH is not configured for the SL grant associated to the SCI。
本申请实施例中，所述业务对应DRX终端设备可以是指，所述业务是 针对配置了DRX的终端设备的；所述业务对应未配置DRX的终端设备可以是指，所述业务是针对未配置DRX的终端设备的；所述业务对应配置了DRX的终端设备和未配置DRX的终端设备可以是指，所述业务是针对未配置DRX的终端设备以及配置了DRX的终端设备的；若所述业务对应配置了DRX的终端设备和未配置DRX的终端设备，则所述业务可以通过组播或广播的方式传输。
在一些实施例中，所述数据传输方法还可以包括：
步骤S202，发送设备向所述目标地址对应的设备传输数据。
在一些实施例中，所述发送设备确定目标地址之后，根据LCP准则选择的目标地址中满足条件的逻辑信道，并生成向所述目标地址发送的数据(如MAC PDU)。
本申请实施例中，发送设备选择用于发送MAC PDU的逻辑信道的流程可以如图4所示：发送设备获取侧行链路授权信息，发送设备判断资源池的类型；若资源池的类型为非共享资源池、且所述非共享资源池仅支持未配置DRX的终端设备的业务，则发送设备选择目标地址集合包括未配置DRX的终端设备对应的地址。若资源池的类型为非共享资源池、且所述非共享资源池仅支持配置DRX的终端设备的业务，则发送设备选择目标地址集合包括配置DRX的终端设备对应的地址。若资源池的类型为共享资源池、且所述共享资源池支持配置DRX的终端设备的业务和未配置DRX的终端设备的业务，则发送设备选择目标地址集合包括配置DRX的终端设备对应的地址和未配置DRX的终端设备对应的地址。最后，发送设备在所选择的地址中选择逻辑信道发送MAC PDU。
本申请实施例中，发送设备根据侧行链路的时频资源和/或资源池类型确定可用目标地址集合，发送设备在所述时频资源向所确定的目标地址传输数据时，目标地址对应的设备能够有效地接收所述数据，进而实现侧行数据的有效传输。举例来说，若发送设备确定目标地址对应的设备(接收设备)为DRX终端，则接收设备在唤醒状态或激活状态检测侧行链路控制信息以接收数据；避免发送设备在接收设备处于休眠或去激活状态时传输数据而导致的接收设备无法接收数据，提高了数据的传输效率。
本申请实施例提供的数据传输方法的另一种可选处理流程，如图5所示，包括以下步骤：
步骤S301，接收设备根据所述接收设备是否配置了DRX和/或资源池类型接收数据。
在一些实施例中，所述接收设备是否配置了DRX可以包括：所述接收设备配置了DRX或所述接收设备未配置DRX；若所述接收设备配置了DRX，则所述接收设备为DRX设备。
在一些实施例中，所述资源池类型可以包括：共享资源池或非共享资源池。
下面分别对接收设备是否配置了DRX和资源池类型进行说明。
1)若所述资源池类型为共享资源池，且所述接收设备配置了DRX，则所述接收设备在唤醒状态接收发送设备传输的侧行数据，所述接收设备在非唤醒状态或非激活状态不接收侧行数据；即所述接收设备在激活状态检测侧行控制信息以接收侧行数据，在非唤醒状态或非激活状态不检测侧行控制信息。
2)若所述资源池类型为共享资源池，且所述接收设备未配置DRX，则所述接收设备连续接收所述数据，即所述接收设备一直检测侧行控制信息以接收侧行数据。
3)若所述资源池类型为非共享资源池、且所述非共享资源池支持DRX终端设备的业务和未配置DRX的终端设备的业务，则所述接收设备在唤醒状态接收所述数据，或者所述接收设备连续接收所述数据。即配置了DRX的接收设备在唤醒状态检测侧行控制信息以接收侧行数据，未配置DRX的接收设备连续检测侧行控制信息以接收侧行数据。
4)若所述资源池类型为非共享资源池、所述非共享资源池仅支持DRX终端设备的业务、且所述接收设备配置了DRX，则所述接收设备在唤醒状态接收所述数据；即所述接收设备在激活状态检测侧行控制信息以接收侧行数据。
5)若所述资源池类型为非共享资源池、所述非共享资源池仅支持未配置DRX的终端设备的业务、且所述接收设备未配置DRX，则所述接收设备连续接收所述数据。即未配置DRX的接收设备连续检测侧行控制信息以接收侧行数据。
在一些实施例中，所述发送设备和所述接收设备可以是侧行传输中的终端设备。
本申请实施例中，发送设备根据侧行链路的时频资源和/或资源池类型确定可用目标地址集合，以使所述发送设备在所述时频资源向所确定的目标地址传输数据时，目标地址对应的设备能够有效地接收所述数据，进而实现侧行数据的有效传输。举例来说，若发送设备确定目标地址对应的设备(接收设备)为DRX终端，则接收设备在唤醒状态或激活状态检测侧行链路控制信息以接收数据；避免发送设备在接收设备处于休眠或去激活状态时传输数据而导致的接收设备无法接收数据，提高了数据的传输效率。
本申请实施例提供的数据传输方法的又一种可选处理流程，如图6所示，包括以下步骤：
步骤S401，发送设备向接收设备发送第二消息，所述第二消息用于指示所述接收设备进入DRX非激活状态。
具体地，所述发送设备向至少一个目标地址发送第二消息，所述至少一个目标地址中的每个目标地址对应一个终端设备的地址。
在一些可选实施方式中，所述发送设备向至少一个目标地址发送第二 消息之前，所述发送设备接收网络发送的指示信息，所述指示信息用于指示所述发送设备向所述至少一个目标地址发送第二消息。
在一些可选实施方式中，所述发送设备向至少一个目标地址发送第二消息之后，所述发送设备向网络发送通知消息，所述通知消息用于向网络报告所述至少一个目标地址对应的终端设备已进入DRX非激活态。
上述方案中，可选地，所述第二消息为MAC CE。对于侧行DRX(SL DRX)中的MAC CE，若发送设备(即TX UE)处于连接态和/或第一模式(即mode1)，发送设备的传输资源配置来自于网络，因此该MAC CE的发送可以受网络的控制，即网络指示发送设备是否发送MAC CE，进一步，可选地，发送设备发完该MAC CE后向网络上报通知消息。
为实现本申请实施例提供的数据传输方法，本申请实施例还提供一种网络设备，所述发送设备500的可选组成结构，如图7所示，包括：
处理单元501，配置为根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
在一些实施例中，所述可用目标地址集合包括未配置非连续接收DRX的终端设备对应的地址；
或者，所述可用目标地址集合包括在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
在一些实施例中，所述发送设备还包括：
发送单元502，配置为若所述侧行链路授权信息配置的时频资源内和/或资源池内不存在可用目标地址集合，则向网络上报第一消息。
在一些实施例中，若所述侧行链路授权信息来自网络，则所述第一消息用于指示网络配置的侧行链路授权资源不可用和/或当前目标地址均处于DRX非激活态。这里，当前目标地址是指与发送设备进行侧行链路通信的目标地址。
在一些实施例中，所述第一消息为物理层信令或者MAC CE或者RRC信令。
在一些实施例中，所述资源池类型为共享资源池。
在一些实施例中，所述资源池类型为非共享资源池，所述非共享资源池支持DRX终端设备的业务和未配置DRX的终端设备的业务。
在一些实施例中，所述可用目标地址可用包括在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
在一些实施例中，所述资源池类型为非共享资源池，所述非共享资源池仅支持DRX终端设备的业务。
在一些实施例中，所述可用目标地址集合包括未配置DRX的终端设备对应的地址。
在一些实施例中，所述资源池类型为非共享资源池，所述非共享资源 池仅支持未配置DRX的终端设备的业务。
在一些实施例中，所述共享资源池内的传输资源用于配置DRX的终端设备和未配置DRX的终端设备。
在一些实施例中，所述非共享资源池内的传输资源用于配置DRX的终端设备和未配置DRX的终端设备；
或者，所述非共享资源池内的传输资源用于配置DRX的终端设备；
或者，所述非共享资源池内的传输资源用于未配置DRX的终端设备。
在一些实施例中，所述数据对应的配置文件可以根据待发送数据的信息确定，所述配置文件用于指示可用的协议的版本。
在一些实施例中，所述资源池和配置文件具有对应关系，所述资源池支持与其具有对应关系的配置文件。
在一些实施例中，所述协议版本用于指示下述至少一种信息：
所述业务对应配置了DRX的终端设备；
所述业务对应未配置DRX的终端设备；
所述业务对应配置了DRX的终端设备和未配置DRX的终端设备；
所述业务对应的目的地址为配置了DRX的终端设备的地址；
所述业务对应的目的地址为未配置DRX的终端设备的地址。
在一些实施例中，所述可用目标地址集合包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。
在一些实施例中，所述发送设备500还包括：
发送单元502，配置为向所述目标地址对应的设备传输所述数据。
在一些实施例中，所述数据为侧行数据。
为实现本申请实施例提供的数据传输方法，本申请实施例还提供一种接收设备，所述接收设备600的可选组成结构，如图8所示，包括：
接收单元601，配置为根据所述接收设备是否配置了非连续接收DRX和/或资源池类型接收数据。
在一些实施例中，所述接收单元601，配置为若所述资源池类型为共享资源池，且所述接收设备配置了DRX，则在唤醒状态接收所述数据。
在一些实施例中，所述接收单元601，配置为若所述资源池类型为共享资源池，且所述接收设备未配置DRX，则连续接收所述数据。
在一些实施例中，所述接收单元601，配置为若所述资源池类型为非共享资源池、且所述非共享资源池支持配置了DRX的终端设备的业务和未配置DRX的终端设备的业务，则在唤醒状态接收所述数据，或者所述接收设备连续接收所述数据。
在一些实施例中，所述接收单元601，配置为若所述资源池类型为非共享资源池、所述非共享资源池仅支持配置了DRX的终端设备的业务、且所述接收设备配置了DRX，则在唤醒状态接收所述数据。
在一些实施例中，所述接收单元601，配置为若所述资源池类型为非共 享资源池、所述非共享资源池仅支持未配置DRX的终端设备的业务、且所述接收设备未配置DRX，则连续接收所述数据。
在一些实施例中，所述数据为侧行数据。
需要说明的是，本申请实施例中，处理单元501的功能可由处理器实现，发送单元502的功能可由发送器或收发器实现，接收单元601的功能可由接收器或收发器实现。
为实现本申请实施例提供的数据传输方法，本申请实施例还提供一种发送设备，所述发送设备500的可选组成结构，如图9所示，包括：
发送单元502，配置为向接收设备发送第二消息，所述第二消息用于指示所述接收设备进入DRX非激活状态。
在一些实施例中，所述发送单元502，配置为向至少一个目标地址发送第二消息，所述至少一个目标地址中的每个目标地址对应一个终端设备的地址。
在一些实施例中，所述发送设备还包括：
接收单元601，配置为接收网络发送的指示信息，所述指示信息用于指示所述发送设备向所述至少一个目标地址发送第二消息。
在一些实施例中，所述发送单元502，还配置为向网络发送通知消息，所述通知消息用于向网络报告所述至少一个目标地址对应的终端设备已进入DRX非激活态。
需要说明的是，本申请实施例中，发送单元502的功能可由发送器或收发器实现，接收单元601的功能可由接收器或收发器实现。
本申请实施例还提供一种发送设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述发送设备执行的数据传输方法的步骤。
本申请实施例还提供一种接收设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，所述处理器用于运行所述计算机程序时，执行上述接收设备执行的数据传输方法的步骤。
本申请实施例还提供一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行上述发送设备执行的数据传输方法。
本申请实施例还提供一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行上述接收设备执行的数据传输方法。
本申请实施例还提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述发送设备执行的数据传输方法。
本申请实施例还提供一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现上述接收设备执行的数据传输方法。
本申请实施例还提供一种计算机程序产品，包括计算机程序指令，该 计算机程序指令使得计算机执行上述发送设备执行的数据传输方法。
本申请实施例还提供一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述接收设备执行的数据传输方法。
本申请实施例还提供一种计算机程序，所述计算机程序使得计算机执行上述发送设备执行的数据传输方法。
本申请实施例还提供一种计算机程序，所述计算机程序使得计算机执行上述接收设备执行的数据传输方法。
图10是本申请实施例的电子设备(发送设备或接收设备)的硬件组成结构示意图，电子设备700包括：至少一个处理器701、存储器702和至少一个网络接口704。电子设备700中的各个组件通过总线系统705耦合在一起。可理解，总线系统705用于实现这些组件之间的连接通信。总线系统705除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图10中将各种总线都标为总线系统705。
可以理解，存储器702可以是易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是ROM、可编程只读存储器(PROM，Programmable Read-Only Memory)、可擦除可编程只读存储器(EPROM，Erasable Programmable Read-Only Memory)、电可擦除可编程只读存储器(EEPROM，Electrically Erasable Programmable Read-Only Memory)、磁性随机存取存储器(FRAM，ferromagnetic random access memory)、快闪存储器(Flash Memory)、磁表面存储器、光盘、或只读光盘(CD-ROM，Compact Disc Read-Only Memory)；磁表面存储器可以是磁盘存储器或磁带存储器。易失性存储器可以是随机存取存储器(RAM，Random Access Memory)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(SRAM，Static Random Access Memory)、同步静态随机存取存储器(SSRAM，Synchronous Static Random Access Memory)、动态随机存取存储器(DRAM，Dynamic Random Access Memory)、同步动态随机存取存储器(SDRAM，Synchronous Dynamic Random Access Memory)、双倍数据速率同步动态随机存取存储器(DDRSDRAM，Double Data Rate Synchronous Dynamic Random Access Memory)、增强型同步动态随机存取存储器(ESDRAM，Enhanced Synchronous Dynamic Random Access Memory)、同步连接动态随机存取存储器(SLDRAM，SyncLink Dynamic Random Access Memory)、直接内存总线随机存取存储器(DRRAM，Direct Rambus Random Access Memory)。本申请实施例描述的存储器702旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例中的存储器702用于存储各种类型的数据以支持电子设备700的操作。这些数据的示例包括：用于在电子设备700上操作的任何计算机程序，如应用程序7022。实现本申请实施例方法的程序可以包含在 应用程序7022中。
上述本申请实施例揭示的方法可以应用于处理器701中，或者由处理器701实现。处理器701可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器701中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器701可以是通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。处理器701可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤，可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于存储介质中，该存储介质位于存储器702，处理器701读取存储器702中的信息，结合其硬件完成前述方法的步骤。
在示例性实施例中，电子设备700可以被一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、FPGA、通用处理器、控制器、MCU、MPU、或其他电子元件实现，用于执行前述方法。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
应理解，本申请中术语“系统”和“网络”在本文中常被可互换使用。本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单 独存在B这三种情况。另外，本申请中字符“/”，一般表示前后关联对象是一种“或”的关系。
以上所述，仅为本申请的较佳实施例而已，并非用于限定本申请的保护范围，凡在本申请的精神和原则之内所作的任何修改、等同替换和改进等，均应包含在本申请的保护范围之内。

Claims (70)

  1. 一种数据传输方法，所述方法包括：
    发送设备根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
  2. 根据权利要求1所述的方法，其中，所述可用目标地址集合包括未配置非连续接收DRX的终端设备对应的地址；
    或者，所述可用目标地址集合包括在所述时频资源处于唤醒状态的配置了DRX的终端设备对应的地址。
  3. 根据权利要求1或2所述的方法，其中，所述方法还包括：
    若所述侧行链路授权信息配置的时频资源内和/或资源池内不存在可用目标地址集合，则所述发送设备向网络上报第一消息。
  4. 根据权利要求3所述方法，其中，若所述侧行链路授权信息来自网络，则所述第一消息用于指示网络配置的侧行链路授权资源不可用和/或当前目标地址均处于DRX非激活态。
  5. 根据权利要求3或4所述方法，其中，所述第一消息为物理层信令或者媒体接入控制MAC控制单元CE或者无线资源控制RRC信令。
  6. 根据权利要求2所述的方法，其中，所述资源池类型为共享资源池。
  7. 根据权利要求2所述的方法，其中，所述资源池类型为非共享资源池，所述非共享资源池支持配置了DRX的终端设备的业务和未配置DRX的终端设备的业务。
  8. 根据权利要求1所述的方法，其中，所述可用目标地址集合包括在所述时频资源处于唤醒状态的配置了DRX的终端设备对应的地址。
  9. 根据权利要求8所述的方法，其中，所述资源池类型为非共享资源池，所述非共享资源池仅支持配置了DRX的终端设备的业务。
  10. 根据权利要求1所述的方法，其中，所述可用目标地址集合包括未配置DRX的终端设备对应的地址。
  11. 根据权利要求10所述的方法，其中，所述资源池类型为非共享资源池，所述非共享资源池仅支持未配置DRX的终端设备的业务。
  12. 根据权利要求6所述的方法，其中，所述共享资源池内的传输资源用于配置了DRX的终端设备和未配置DRX的终端设备。
  13. 根据权利要求7、9和11任一项所述的方法，其中，所述非共享资源池内的传输资源用于配置了DRX的终端设备和未配置DRX的终端设备；
    或者，所述非共享资源池内的传输资源用于配置了DRX的终端设备；
    或者，所述非共享资源池内的传输资源用于未配置DRX的终端设备。
  14. 根据权利要求1至13任一项所述的方法，其中，所述数据对应的配置文件由待发送数据的信息确定，所述配置文件用于指示可用的协议的版本。
  15. 根据权利要求1至14任一项所述的方法，其中，所述资源池和配置文件具有对应关系，所述资源池支持与其具有对应关系的配置文件。
  16. 根据权利要求14或15所述的方法，其中，所述协议版本用于指示下述至少一种信息：
    所述业务对应配置了DRX的终端设备；
    所述业务对应未配置DRX的终端设备；
    所述业务对应配置了DRX的终端设备和未配置DRX的终端设备；
    所述业务对应的目的地址为配置了DRX的终端设备的地址；
    所述业务对应的目的地址为未配置DRX的终端设备的地址。
  17. 根据权利要求1至16任一项所述的方法，其中，所述可用目标地址集合包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。
  18. 根据权利要求1至17任一项所述的方法，其中，所述方法还包括：
    所述发送设备向所述目标地址对应的设备传输所述数据。
  19. 根据权利要求1至18任一项所述的方法，其中，所述数据为侧行数据。
  20. 一种数据传输方法，所述方法包括：
    接收设备根据所述接收设备是否配置了非连续接收DRX和/或资源池类型接收数据。
  21. 根据权利要求20所述的方法，其中，若所述资源池类型为共享资源池，且所述接收设备配置了DRX，则所述接收设备在唤醒状态接收所述数据。
  22. 根据权利要求20或21所述的方法，其中，若所述资源池类型为共享资源池，且所述接收设备未配置DRX，则所述接收设备连续接收所述数据。
  23. 根据权利要求20至22任一项所述的方法，其中，若所述资源池类型为非共享资源池、且所述非共享资源池支持配置了DRX的终端设备的业务和未配置DRX的终端设备的业务，
    则所述接收设备在唤醒状态接收所述数据，或者所述接收设备连续接收所述数据。
  24. 根据权利要求20至23任一项所述的方法，其中，若所述资源池类型为非共享资源池、所述非共享资源池仅支持配置了DRX的终端设备的业务、且所述接收设备配置了DRX，
    则所述接收设备在唤醒状态接收所述数据。
  25. 根据权利要求20至24任一项所述的方法，其中，若所述资源池 类型为非共享资源池、所述非共享资源池仅支持未配置DRX的终端设备的业务、且所述接收设备未配置DRX，
    则所述接收设备连续接收所述数据。
  26. 根据权利要求20至25任一项所述的方法，其中，所述数据为侧行数据。
  27. 一种数据传输方法，所述方法包括：
    发送设备向接收设备发送第二消息，所述第二消息用于指示所述接收设备进入DRX非激活状态。
  28. 根据权利要求27所述的方法，其中，所述发送设备向接收设备发送第二消息，包括：
    所述发送设备向至少一个目标地址发送第二消息，所述至少一个目标地址中的每个目标地址对应一个终端设备的地址。
  29. 根据权利要求28所述的方法，其中，所述发送设备向至少一个目标地址发送第二消息之前，所述方法还包括：
    所述发送设备接收网络发送的指示信息，所述指示信息用于指示所述发送设备向所述至少一个目标地址发送第二消息。
  30. 根据权利要求28所述的方法，其中，所述发送设备向至少一个目标地址发送第二消息之后，所述方法还包括：
    所述发送设备向网络发送通知消息，所述通知消息用于向网络报告所述至少一个目标地址对应的终端设备已进入DRX非激活态。
  31. 一种发送设备，所述发送设备包括：
    处理单元，配置为根据侧行链路授权信息确定可用目标地址集合，所述侧行链路授权信息包括：时频资源和/或资源池类型，所述可用目标地址集合中的至少一个目标地址用于所述发送设备生成数据。
  32. 根据权利要求31所述的发送设备，其中，所述发送设备还包括：
    发送单元，配置为若所述侧行链路授权信息配置的时频资源内和/或资源池内不存在可用目标地址集合，则向网络上报第一消息。
  33. 根据权利要求32所述的发送设备，其中，若所述侧行链路授权信息来自网络，则所述第一消息用于指示网络配置的侧行链路授权资源不可用和/或当前目标地址均处于DRX非激活态。
  34. 根据权利要求32或33所述的发送设备，其中，所述第一消息为物理层信令或者MAC CE或者RRC信令。
  35. 根据权利要求31所述的发送设备，其中，所述资源池类型为共享资源池。
  36. 根据权利要求31所述的发送设备，其中，所述资源池类型为非共享资源池，所述非共享资源池支持DRX终端设备的业务和未配置DRX的终端设备的业务。
  37. 根据权利要求31至36任一项所述的发送设备，其中，所述可用 目标地址集合包括未配置非连续接收DRX的终端设备对应的地址；
    或者，所述可以目标地址集合包括在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
  38. 根据权利要求31所述的发送设备，其中，所述资源池类型为非共享资源池，所述非共享资源池仅支持DRX终端设备的业务。
  39. 根据权利要求31或38所述的发送设备，其中，所述可用目标地址集合包括在所述时频资源处于唤醒状态的DRX终端设备对应的地址。
  40. 根据权利要求31所述的发送设备，其中，所述资源池类型为非共享资源池，所述非共享资源池仅支持未配置DRX的终端设备的业务。
  41. 根据权利要求31或40所述的发送设备，其中，所述可用目标地址集合包括未配置DRX的终端设备对应的地址。
  42. 根据权利要求35所述的发送设备，其中，所述共享资源池内的传输资源用于配置DRX的终端设备和未配置DRX的终端设备。
  43. 根据权利要求36、38和40任一项所述的发送设备，其中，所述非共享资源池内的传输资源用于配置DRX的终端设备和未配置DRX的终端设备；
    或者，所述非共享资源池内的传输资源用于配置DRX的终端设备；
    或者，所述非共享资源池内的传输资源用于未配置DRX的终端设备。
  44. 根据权利要求31至43任一项所述的发送设备，其中，所述数据对应的配置文件由待发送数据的信息确定，所述配置文件用于指示可用的协议的版本。
  45. 根据权利要求31至44任一项所述的发送设备，其中，所述资源池和配置文件具有对应关系，所述资源池支持与其具有对应关系的配置文件。
  46. 根据权利要求44或45所述的发送设备，其中，所述协议版本用于指示下述至少一种信息：
    所述业务对应配置了DRX的终端设备；
    所述业务对应未配置DRX的终端设备；
    所述业务对应配置了DRX的终端设备和未配置DRX的终端设备；
    所述业务对应的目的地址为配置了DRX的终端设备的地址；
    所述业务对应的目的地址为未配置DRX的终端设备的地址。
  47. 根据权利要求31至46任一项所述的发送设备，其中，所述可用目标地址集合包括满足条件的至少一个优先级最高的逻辑信道和/或媒体接入控制控制单元。
  48. 根据权利要求31至47任一项所述的发送设备，其中，所述发送设备还包括：
    发送单元，配置为向所述目标地址对应的设备传输所述数据。
  49. 根据权利要求31至48任一项所述的发送设备，其中，所述数据 为侧行数据。
  50. 一种接收设备，其中，所述接收设备包括：
    接收单元，配置为根据所述接收设备是否配置了非连续接收DRX和/或资源池类型接收数据。
  51. 根据权利要求50所述的接收设备，其中，所述接收单元，配置为若所述资源池类型为共享资源池，且所述接收设备配置了DRX，则在唤醒状态接收所述数据。
  52. 根据权利要求50或51所述的接收设备，其中，所述接收单元，配置为若所述资源池类型为共享资源池，且所述接收设备未配置DRX，则连续接收所述数据。
  53. 根据权利要求50至52任一项所述的接收设备，其中，所述接收单元，配置为若所述资源池类型为非共享资源池、且所述非共享资源池支持配置了DRX的终端设备的业务和未配置DRX的终端设备的业务，则在唤醒状态接收所述数据，或者所述接收设备连续接收所述数据。
  54. 根据权利要求50至53任一项所述的接收设备，其中，所述接收单元，配置为若所述资源池类型为非共享资源池、所述非共享资源池仅支持配置了DRX的终端设备的业务、且所述接收设备配置了DRX，则在唤醒状态接收所述数据。
  55. 根据权利要求50至54任一项所述的接收设备，其中，所述接收单元，配置为若所述资源池类型为非共享资源池、所述非共享资源池仅支持未配置DRX的终端设备的业务、且所述接收设备未配置DRX，则连续接收所述数据。
  56. 根据权利要求50至55任一项所述的接收设备，其中，所述数据为侧行数据。
  57. 一种发送设备，所述发送设备包括：
    发送单元，配置为向接收设备发送第二消息，所述第二消息用于指示所述接收设备进入DRX非激活状态。
  58. 根据权利要求57所述的发送设备，其中，所述发送单元，配置为向至少一个目标地址发送第二消息，所述至少一个目标地址中的每个目标地址对应一个终端设备的地址。
  59. 根据权利要求58所述的发送设备，其中，所述发送设备还包括：
    接收单元，配置为接收网络发送的指示信息，所述指示信息用于指示所述发送设备向所述至少一个目标地址发送第二消息。
  60. 根据权利要求58所述的发送设备，其中，所述发送单元，还配置为向网络发送通知消息，所述通知消息用于向网络报告所述至少一个目标地址对应的终端设备已进入DRX非激活态。
  61. 一种发送设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求1至19任一项所述的数据传输方法的步骤，或者权利要求27至30任一项所述的数据传输方法的步骤。
  62. 一种网络设备，包括处理器和用于存储能够在处理器上运行的计算机程序的存储器，其中，
    所述处理器用于运行所述计算机程序时，执行权利要求20至26任一项所述的数据传输方法的步骤。
  63. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求1至19任一项所述的数据传输方法，或者权利要求27至30任一项所述的数据传输方法。
  64. 一种存储介质，存储有可执行程序，所述可执行程序被处理器执行时，实现权利要求20至26任一项所述的数据传输方法。
  65. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至19任一项所述的数据传输方法，或者权利要求27至30任一项所述的数据传输方法。
  66. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求20至26任一项所述的数据传输方法。
  67. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至19任一项所述的数据传输方法，或者权利要求27至30任一项所述的数据传输方法。
  68. 一种计算机程序，所述计算机程序使得计算机执行如权利要求20至26任一项所述的数据传输方法。
  69. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至19任一项所述的数据传输方法，或者权利要求27至30任一项所述的数据传输方法。
  70. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求20至26任一项所述的数据传输方法。
PCT/CN2021/125886 2021-01-26 2021-10-22 一种数据传输方法、电子设备及存储介质 WO2022160804A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21922395.5A EP4175398A4 (en) 2021-01-26 2021-10-22 DATA TRANSMISSION METHOD, ELECTRONIC DEVICE AND STORAGE MEDIUM
CN202180042357.4A CN115699981A (zh) 2021-01-26 2021-10-22 一种数据传输方法、电子设备及存储介质
US18/166,545 US20230262834A1 (en) 2021-01-26 2023-02-09 Data transmission method, electronic device and storage medium

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNPCT/CN2021/073853 2021-01-26
PCT/CN2021/073853 WO2022160106A1 (zh) 2021-01-26 2021-01-26 一种数据传输方法、电子设备及存储介质
CNPCT/CN2021/111173 2021-08-06
PCT/CN2021/111173 WO2022160648A1 (zh) 2021-01-26 2021-08-06 一种数据传输方法、电子设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/166,545 Continuation US20230262834A1 (en) 2021-01-26 2023-02-09 Data transmission method, electronic device and storage medium

Publications (1)

Publication Number Publication Date
WO2022160804A1 true WO2022160804A1 (zh) 2022-08-04

Family

ID=82652954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/125886 WO2022160804A1 (zh) 2021-01-26 2021-10-22 一种数据传输方法、电子设备及存储介质

Country Status (4)

Country Link
US (1) US20230262834A1 (zh)
EP (1) EP4175398A4 (zh)
CN (1) CN115699981A (zh)
WO (1) WO2022160804A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150327323A1 (en) * 2012-11-21 2015-11-12 Zte Corporation Discontinuous reception (drx) mode processing method, user equipment, and base station
CN107484249A (zh) * 2016-06-07 2017-12-15 大唐移动通信设备有限公司 一种基于业务类型的预调度方法和系统
CN111466151A (zh) * 2020-03-12 2020-07-28 北京小米移动软件有限公司 直连链路中目的地址选择方法、装置及存储介质
CN111556590A (zh) * 2020-04-13 2020-08-18 中国信息通信研究院 一种边链路非连续接收方法
CN111565443A (zh) * 2019-02-14 2020-08-21 电信科学技术研究院有限公司 一种非连续接收激活状态的确定方法及终端

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110831202B (zh) * 2018-08-10 2023-07-25 华硕电脑股份有限公司 针对多个装置到装置资源池分配资源的方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150327323A1 (en) * 2012-11-21 2015-11-12 Zte Corporation Discontinuous reception (drx) mode processing method, user equipment, and base station
CN107484249A (zh) * 2016-06-07 2017-12-15 大唐移动通信设备有限公司 一种基于业务类型的预调度方法和系统
CN111565443A (zh) * 2019-02-14 2020-08-21 电信科学技术研究院有限公司 一种非连续接收激活状态的确定方法及终端
CN111466151A (zh) * 2020-03-12 2020-07-28 北京小米移动软件有限公司 直连链路中目的地址选择方法、装置及存储介质
CN111556590A (zh) * 2020-04-13 2020-08-18 中国信息通信研究院 一种边链路非连续接收方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4175398A4 *

Also Published As

Publication number Publication date
CN115699981A (zh) 2023-02-03
US20230262834A1 (en) 2023-08-17
EP4175398A1 (en) 2023-05-03
EP4175398A4 (en) 2024-01-17

Similar Documents

Publication Publication Date Title
JP7352039B2 (ja) 無線リソース制御（ｒｒｃ）インアクティブ状態での小規模データ伝送
US20230363014A1 (en) Communications device, infrastructure equipment and methods
JP6846435B2 (ja) ウェアラブルデバイスをｌｔｅマスターｕｅと共にグループ化する手順
JP7332814B2 (ja) マルチｓｉｍ動作のためのユーザ機器及び方法
JP2021061639A (ja) 無線アクセスネットワーク通知エリア更新障害
JP2022549513A (ja) 省電力およびセル休止動作
JP7392960B2 (ja) フィードバックチャネルの無線リソースマッピング
JP7362093B2 (ja) アップリンクリソース構成
JP2019504573A (ja) 無線通信システムにおける端末によりトリガされた半静的スケジューリング活性化を実行するための方法及び装置
JP2018511197A (ja) ライセンス補助アクセスのための不連続受信動作
WO2018210254A1 (zh) 频域资源的处理方法、装置及系统
US20230120065A1 (en) Logical Channel Configuration
JP2023500324A (ja) 新しい無線のライセンスされていない帯域におけるアップリンク送信
US11464000B2 (en) Information indication method, terminal device, and network device
JP2024502872A (ja) 非アクティブコンテキスト管理
JP2023544526A (ja) スモールデータ伝送の完了表示
WO2022147186A1 (en) Methods for data transmission and user equipment using the same
US20230102937A1 (en) Configuration release
WO2010111820A1 (zh) 一种随机接入方法、演进基站及终端设备
WO2021263106A2 (en) Discontinuous reception
EP3944656B1 (en) Entering drx active time for drx groups
WO2022160804A1 (zh) 一种数据传输方法、电子设备及存储介质
WO2022160648A1 (zh) 一种数据传输方法、电子设备及存储介质
WO2020061873A1 (zh) 一种资源指示方法、设备及存储介质
WO2021159541A1 (zh) 确定激活期方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21922395

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021922395

Country of ref document: EP

Effective date: 20230126

NENP Non-entry into the national phase

Ref country code: DE