WO2022160648A1

WO2022160648A1 - Data transmission method, electronic device and storage medium

Info

Publication number: WO2022160648A1
Application number: PCT/CN2021/111173
Authority: WO
Inventors: 冷冰雪; 卢前溪
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-01-26
Filing date: 2021-08-06
Publication date: 2022-08-04
Also published as: WO2022160106A1

Abstract

A data transmission method, comprising: a sending device determining an available target address set according to sidelink grant information, wherein the sidelink grant information comprises a time-frequency resource and/or a resource pool type, and at least one target address in the available target address set is used for the sending device to generate data. Further disclosed are another data transmission method, an electronic device, and a storage medium.

Description

A data transmission method, electronic device and storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is based on the international application with the application number of PCT/CN2021/073853 and the filing date of January 26, 2021, and claims the priority of the international application. The entire content of the international application is incorporated herein by reference.

technical field

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.

Background technique

In the New Radio-Vehicle to Everything (NR-V2X) system, after the transmitting device receives the sidelink authorization, how to carry out effective data transmission is the goal that has been pursued.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a data transmission method, an electronic device, and a storage medium, which can realize effective data transmission.

In a first aspect, 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.

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 (Discontinuous Reception, DRX) and/or a resource pool type.

In a third aspect, 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.

In a fourth aspect, 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.

In a fifth aspect, 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.

In a sixth aspect, 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.

In a seventh aspect, 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.

In an eighth aspect, 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.

In a ninth aspect, 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.

In a tenth aspect, 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.

In an eleventh aspect, 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.

In a twelfth aspect, 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.

In a thirteenth aspect, 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.

In a fourteenth aspect, 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.

Description of drawings

FIG. 1 is a schematic flowchart of selecting transmission resources under the first mode of the present application;

2 is a schematic flowchart of selecting transmission resources under the second mode of the present application;

3 is a schematic diagram of an optional processing flow of the data transmission method provided by the embodiment of the present application;

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.

Detailed ways

In order to understand the features and technical contents of the embodiments of the present application in more detail, the implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Before describing the embodiments of the present application, relevant contents are briefly described.

Device to Device (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. Efficiency and lower transmission delay, the Internet of Vehicles system adopts the D2D communication method (that is, the method of device-to-device direct communication). For D2D 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, and the second mode is that the terminal device autonomously selects transmission resources.

For the first mode: as shown in Figure 1, 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.

For the second mode: as shown in FIG. 2 , the terminal device selects a transmission resource in the resource pool to send data.

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 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. For example, 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). Among them, the resource pool (Resource Pool, RP) configuration in the NR-V2X system limits the time-frequency resource range of sideline communication.

In LTE-V2X, the minimum time-domain granularity of resource pool configuration is one subframe, and in NR-V2X system, 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. In LTE-V2X, 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), so the number of PRBs contained in a subchannel needs to be divisible by 2, 3, or 5. 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. Multiplexing, CP-OFDM), in order to reduce the peak-to-average power ratio (PAPR) of sideline transmission, the sub-channels in the resource pool must also be continuous in the frequency domain. In addition, the frequency domain included in the resource pool The resource shall be located within one SL bandwidth part (BandWidthPart, BWP).

In the NR-V2X system, feedback-based Hybrid Automatic Repeat reQuest (HARQ) retransmission is also introduced, which is not limited to HARQ retransmission for unicast communication, but also HARQ retransmission for multicast communication. pass.

In the 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 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.

In R14/15, the IoV system is required for vehicle-vehicle communication scenarios, which are mainly oriented towards relatively high-speed moving vehicle-vehicle and vehicle-person communication services.

In the V2X system, since the vehicle system has continuous power supply, the delay of data transmission is the main problem to be solved. Therefore, the terminal equipment is required to perform continuous transmission and reception in system design.

In R14, 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. For FeD2D, the network device can configure the DRX parameters of the remote terminal through a relay terminal.

In the NR-V2X system, the terminal device will discontinuously monitor the Physical Downlink Control Channel (PDCCH) according to its own DRX configuration to save power. When 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-Physical Uplink Control Channel-Wireless Network Temporary Identifier (Transmit Power Control-Physical Uplink Share Channel-Radio Network Temporary Identifier, TPC-PUSCH-RNTI), Transmission Power Control-Probing Reference Signal-Wireless Network Temporary Identifier (Transmit Power Control-Sounding Reference Symbols-Radio Network Temporary Identifier, TPC-SRS-RNTI) and AI-RNTI, 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 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-TimerUL), ps-Wakeup (optional), ps-TransmitOtherPeriodicCSI (optional) and ps-TransmitPeriodicL1-RSRP (optional).

Wherein, 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.

In the prior art, 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. However, after the sidelink power saving mechanism is introduced, 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.

In the data transmission method provided by the embodiment of the present application, 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.

In some embodiments, 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.

In some embodiments, the sending device may be a terminal device for sending data in a sidelink transmission system. The sending device may acquire 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.

In some optional embodiments, if there is no available target address set in the time-frequency resource and/or in the resource pool configured by the sidelink grant information, 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. . Here, the current destination address refers to the destination address for sidelink communication with the transmitting device.

It should be noted that the sidelink grant resources refer to the time-frequency resources and/or resource pools configured by the sidelink grant information.

In the above solution, optionally, the first message may be physical layer signaling or MAC CE or RRC signaling.

In this embodiment of the present application, if all receiving devices (that is, the receiving UE (Rx UE)) are in an inactive state, 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.

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. 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 the terminal device configured with DRX; and the destination address corresponding to the service is the address of the terminal device not configured with DRX. Wherein, 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.

It can be understood that 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. For example, 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.

In some embodiments, 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 the terminal equipment of DRX and the terminal equipment that is not configured with DRX; or, the transmission resources in the non-shared resource pool are used to configure the terminal equipment of DRX; 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 for the terminal device configured with DRX and the terminal device not configured with DRX.

The following describes the different resource pool types.

1) If the type of the resource pool is a shared resource pool, 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.

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 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.

In some embodiments, 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. Wherein, 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 disabled, if PSFCH is not configured for the SL grant associated to the SCI).

In this scenario, 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.

2) If the type of the resource pool is a non-shared resource pool, and the non-shared resource pool only supports services of DRX terminal equipment, 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 address corresponding to the DRX terminal device.

It can be understood that if the type of the resource pool is a non-shared resource pool and the non-shared resource pool only supports the services of the DRX terminal device, 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.

In some embodiments, 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. Wherein, 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.

3) If 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 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.

It can be understood that, if the type of the resource pool is a non-shared resource pool, and the non-shared resource pool supports the services of the DRX terminal equipment and the services of the terminal equipment not configured with DRX, 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.

4) If the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of terminal equipment not configured with DRX, the target address is an address corresponding to the terminal equipment not configured with DRX.

It can be understood that, if 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.

In the embodiment of the present application, 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 For terminal equipment 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.

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

Step S202, the sending device transmits data to the device corresponding to the target address.

In some embodiments, after determining the target address, the sending device 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.

In the embodiment of the present application, 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. If the type of the resource pool is a shared resource pool, and the shared resource pool supports the service of the terminal device configured with DRX and the service of the terminal device not 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.

In this embodiment of the present application, 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.

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 .

In some embodiments, 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.

1) If the resource pool type is a shared resource pool, and the receiving device is configured with DRX, 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.

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 sideline control information to receive sideline data.

3) if the type of the resource pool is a non-shared resource pool, and the non-shared resource pool supports the service of the DRX terminal device and the service of the terminal device 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 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.

4) If 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.

5) 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 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.

In some embodiments, the sending device and the receiving device may be terminal devices in sideline transmission.

In this embodiment of the present application, 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, so that the sending device transmits data to the determined target address when the time-frequency resource transmits 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 in an awake state or an active state to receive data; avoids 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.

Specifically, 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.

In some optional implementation manners, before the sending device sends the second message to 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.

In some optional implementation manners, 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 the information corresponding to the at least one target address The terminal device has entered the DRX inactive state.

In the above solution, optionally, the second message is a MAC CE. For the MAC CE in the sideline DRX (SL DRX), if the sending device (ie, the TX UE) is in the connected state and/or 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.

In order to implement the data transmission method provided by the embodiment of the present application, the embodiment of the present application further provides a network device. The optional composition structure of the sending device 500, as shown in FIG. 7 , 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.

In some embodiments, the set of available target addresses includes addresses corresponding to terminal devices not configured to receive DRX;

Alternatively, 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.

In some embodiments, the sending device further includes:

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 resource configured by the sidelink authorization information and/or in the resource pool.

In some embodiments, if the sidelink grant information comes from the network, 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 . Here, the current destination address refers to the destination address for sidelink communication with the transmitting device.

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

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

In some embodiments, 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.

In some embodiments, 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.

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.

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

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

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.

In some embodiments, the transmission resources in the non-shared resource pool are used to configure the terminal equipment of DRX and the terminal equipment of not configured with DRX;

Or, the transmission resources in the non-shared resource pool are used to configure the terminal equipment of DRX;

Alternatively, the transmission resources in the non-shared resource pool are used for terminal equipment not configured with DRX.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, the sending device 500 further includes:

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

In some embodiments, the data is side row data.

In order to implement the data transmission method provided by the embodiment of the present application, the embodiment of the present application further provides a receiving device. The optional composition structure of the receiving device 600, as shown in FIG. 8 , 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.

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.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, the data is side row data.

It should be noted that, in this embodiment of the present application, 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, and the function of the receiving unit 601 may be implemented by a receiver or a transceiver.

In order to implement the data transmission method provided by the embodiment of the present application, the embodiment of the present application further provides a sending device. The optional composition structure of the sending device 500, as shown in FIG. 9 , 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.

In some embodiments, 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.

In some embodiments, 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.

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.

It should be noted that, in this embodiment of the present application, the function of the sending unit 502 may be implemented by a transmitter or a transceiver, and 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. 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.

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 above 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 . It can be understood that the bus system 705 is used to implement the connection 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, the various buses are labeled as bus system 705 in FIG. 10 .

It will be appreciated that memory 702 may be either volatile memory or non-volatile memory, and may include both volatile and non-volatile memory. Among them, 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. Volatile memory may be Random Access Memory (RAM), which is used as an external cache. By way of example but 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 Memory (DRAM, Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM, Synchronous Dynamic Random Access Memory), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), Enhanced Type Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus 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.

In an exemplary embodiment, the electronic device 700 may be implemented by one or more of Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), Complex Programmable Logic Device (CPLD) , Complex Programmable Logic Device), FPGA, general-purpose processor, controller, MCU, MPU, or other electronic component implementation for performing the aforementioned method.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block in the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to the processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device produce Means for implementing the functions specified in a flow or flow of a flowchart and/or a block or blocks of a block diagram.

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.

These computer program instructions can also be loaded on a computer or other programmable data processing device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process such that The instructions provide steps for implementing the functions specified in the flow or blocks of the flowcharts and/or the block or blocks of the block diagrams.

It should be understood that the terms "system" and "network" in this application are often used interchangeably herein. The term "and/or" in this application is only an association relationship to describe associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, independently There are three cases of B. In addition, the character "/" in this application generally indicates that the related objects are an "or" relationship.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application shall be included in the within the scope of protection of this application.

Claims

A data transmission method, the method comprising:

The sending device determines an available target address set according to the sidelink authorization information, the sidelink authorization information includes: time-frequency resources and/or resource pool types, and at least one target address in the available target address set is used for all target addresses. The sending device generates the data.
The method according to claim 1, wherein the available target address set includes addresses corresponding to terminal equipment not configured to receive DRX;

Alternatively, the set of available target addresses includes addresses corresponding to the terminal equipment configured with DRX when the time-frequency resource is in an awake state.
The method according to claim 1 or 2, wherein the method further comprises:

If there is no available target address set in the time-frequency resource and/or in the resource pool configured by the sidelink authorization information, the sending device reports the first message to the network.
The method according to claim 3, wherein, if the sidelink grant information comes from a network, 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 both in DRX inactive state.
The method according to claim 3 or 4, wherein the first message is physical layer signaling or medium access control MAC control element CE or radio resource control RRC signaling.
The method of claim 2, wherein the resource pool type is a shared resource pool.
The method according to claim 2, wherein 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.
The method according to claim 1, wherein the set of available target addresses includes addresses corresponding to DRX-configured terminal equipment in an awake state of the time-frequency resource.
The method according to claim 8, wherein the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of terminal devices configured with DRX.
The method according to claim 1, wherein the set of available target addresses includes addresses corresponding to terminal devices not configured with DRX.
The method according to claim 10, wherein the type of the resource pool 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 method according to claim 6, wherein the transmission resources in the shared resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX.
The method according to any one of claims 7, 9 and 11, wherein the transmission resources in the non-shared resource pool are used for terminal equipment configured with DRX and terminal equipment without DRX;

Or, the transmission resources in the non-shared resource pool are used for terminal equipment configured with DRX;

Alternatively, the transmission resources in the non-shared resource pool are used for terminal equipment not configured with DRX.
The method according to any one of claims 1 to 13, wherein a configuration file corresponding to the data is determined by information of the data to be sent, and the configuration file is used to indicate an available protocol version.
The method of claim 14, wherein 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 method according to any one of claims 1 to 15, wherein the set of available target addresses includes at least one logical channel and/or medium access control control unit with the highest priority that satisfy the condition.
The method according to any one of claims 1 to 16, wherein the method further comprises:

The sending device transmits the data to the device corresponding to the target address.
The method according to any one of claims 1 to 17, wherein the data is side row data.
A data transmission method, the method comprising:

The receiving device receives data according to whether the receiving device is configured with discontinuous reception DRX and/or resource pool type.
The method according to claim 19, wherein if the type of the resource pool is a shared resource pool and the receiving device is configured with DRX, the receiving device receives the data in an awake state.
The method according to claim 19 or 20, wherein if the type of the resource pool is a shared resource pool and the receiving device is not configured with DRX, the receiving device continuously receives the data.
The method according to any one of claims 19 to 21, wherein, 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 terminals not configured with DRX equipment business,

Then the receiving device receives the data in an awake state, or the receiving device continuously receives the data.
The method according to any one of claims 19 to 22, wherein, 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 DRX is configured,

Then the receiving device receives the data in an awake state.
The method according to any one of claims 19 to 23, wherein, if the resource pool type is a non-shared resource pool, the non-shared resource pool only supports services of terminal devices not configured with DRX, and the receiving device DRX is not configured,

Then the receiving device continuously receives the data.
The method according to any one of claims 19 to 24, wherein the data is side row data.
A data transmission method, the method comprising:

The sending device sends a second message to the receiving device, where the second message is used to instruct the receiving device to enter a DRX inactive state.
The method of claim 26, wherein the sending device sends the second message to the receiving device, comprising:

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 method according to claim 27, wherein before the sending device sends the second message to the at least one destination address, the method further comprises:

The sending device receives 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.
The method according to claim 27, wherein after the sending device sends the second message to at least one target address, the method further comprises:

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 a DRX inactive state.
A sending device, the sending device includes:

a processing unit, configured to determine an available target address set according to sidelink authorization information, the sidelink authorization information including: 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 according to claim 30, wherein the sending device further comprises:

A sending unit, 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 sending device according to claim 31, wherein if the sidelink grant information comes from a network, the first message is used to indicate that a sidelink grant resource configured by the network is unavailable and/or the current target address All are in DRX inactive state.
The sending device according to claim 31 or 32, wherein the first message is physical layer signaling or MAC CE or RRC signaling.
The sending device according to claim 30, wherein the resource pool type is a shared resource pool.
The sending device according to claim 30, wherein 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 sending device according to any one of claims 30 to 35, wherein the available target address set includes addresses corresponding to terminal devices that are not configured to receive DRX;

Alternatively, the set of available target addresses includes addresses corresponding to the DRX terminal equipment that is in an awake state when the time-frequency resource is in an awake state.
The sending device according to claim 30, wherein the resource pool type is a non-shared resource pool, and the non-shared resource pool only supports services of DRX terminal devices.
The transmitting device according to claims 30 and 37, wherein the set of available target addresses includes addresses corresponding to DRX terminal devices that are in an awake state on the time-frequency resource.
The sending device according to claim 30, wherein the type of the resource pool 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 sending device according to claims 30 and 39, wherein the set of available target addresses includes addresses corresponding to terminal devices not configured with DRX.
The sending device according to claim 34, wherein the transmission resources in the shared resource pool are used for terminal devices configured with DRX and terminal devices not configured with DRX.
The sending device according to any one of claims 35, 37 and 39, wherein the transmission resources in the non-shared resource pool are used for terminal equipment configured with DRX and terminal equipment without DRX;

Or, the transmission resources in the non-shared resource pool are used to configure the terminal equipment of DRX;

Alternatively, the transmission resources in the non-shared resource pool are used for terminal equipment not configured with DRX.
The sending device according to any one of claims 30 to 42, wherein a configuration file corresponding to the data is determined by information of the data to be sent, and the configuration file is used to indicate an available protocol version.
The sending device according to claim 43, wherein 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 sending device according to any one of claims 30 to 44, wherein the set of available target addresses includes at least one logical channel and/or a medium access control control unit with the highest priority that satisfies the condition.
The sending device according to any one of claims 30 to 45, wherein the sending device further comprises:

A sending unit, configured to transmit the data to the device corresponding to the target address.
The transmitting device according to any one of claims 30 to 46, wherein the data is side row data.
A receiving device, wherein the receiving device comprises:

A receiving unit, configured to receive data according to whether the receiving device is configured with discontinuous reception DRX and/or a resource pool type.
The receiving device according to claim 48, wherein the receiving unit 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 device according to claim 48 or 49, wherein the receiving unit 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.
The receiving device according to any one of claims 48 to 50, wherein the receiving unit is configured to, if the resource pool type is a non-shared resource pool, and the non-shared resource pool supports a terminal device configured with DRX The data is received in the wake-up state, or the receiving device continuously receives the data.
The receiving device according to any one of claims 48 to 51, wherein the receiving unit is configured to, if the resource pool type is a non-shared resource pool, the non-shared resource pool only supports terminal devices configured with DRX and the receiving device is configured with DRX, the data is received in the wake-up state.
The receiving device according to any one of claims 48 to 52, wherein the receiving unit is configured to, if the resource pool type is a non-shared resource pool, the non-shared resource pool only supports terminal devices without DRX configured and the receiving device is not configured with DRX, the data is continuously received.
The receiving device according to any one of claims 48 to 53, wherein the data is side row data.
A sending device, the sending device includes:

A sending unit, 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 device according to claim 55, wherein the sending unit is configured to send the second message to at least one target address, and each target address in the at least one target address corresponds to an address of a terminal device.
The sending device of claim 56, wherein the sending device further comprises:

The receiving unit 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.
The sending device according to claim 56, wherein the sending unit 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 DRX inactive state.
A transmission device comprising a processor and a memory for storing a computer program executable on the processor, wherein,

When the processor is configured to execute the computer program, the steps of the data transmission method described in any one of claims 1 to 18 or the steps of the data transmission method described in any one of claims 26 to 29 are executed.
A network device comprising a processor and a memory for storing a computer program executable on the processor, wherein,

The processor is configured to execute the steps of the data transmission method according to any one of claims 19 to 25 when running the computer program.
A storage medium that stores an executable program, and when the executable program is executed by a processor, implements the data transmission method described in any one of claims 1 to 18, or the data transmission method described in any one of claims 26 to 29 data transfer method.
A storage medium storing an executable program, when the executable program is executed by a processor, the data transmission method according to any one of claims 19 to 25 is implemented.
A computer program product comprising computer program instructions that cause a computer to perform the data transmission method of any one of claims 1 to 18, or the data transmission method of any one of claims 26 to 29.
A computer program product comprising computer program instructions that cause a computer to perform the data transmission method of any one of claims 19 to 25.
A computer program that causes a computer to execute the data transmission method of any one of claims 1 to 18, or the data transmission method of any one of claims 26 to 29.
A computer program that causes a computer to perform the data transmission method of any one of claims 19 to 25.
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 according to any one of claims 1 to 18, or claims 26 to 26 29. The data transmission method of any one of 29.
A chip, comprising: a processor for calling and running a computer program from a memory, so that a device on which the chip is installed executes the data transmission method according to any one of claims 19 to 25.