CN111836390B

CN111836390B - Data transmission method, terminal and control node

Info

Publication number: CN111836390B
Application number: CN201910657387.0A
Authority: CN
Inventors: 纪子超; 邬华明
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2019-07-19
Filing date: 2019-07-19
Publication date: 2022-03-08
Anticipated expiration: 2039-07-19
Also published as: WO2021013005A1; CN111836390A

Abstract

The invention provides a data transmission method, a terminal and a control node, and relates to the technical field of communication. The data transmission method is applied to the terminal and comprises the following steps: acquiring first information; acquiring a scheduling instruction aiming at the direct communication link sent by the control node according to the first information; transmitting data according to the scheduling instruction; wherein the first information comprises: and the scheduling identifier is used for indicating the terminal to monitor the scheduling instruction. By the method, the scheduling delay and the direct communication link resource overhead can be reduced.

Description

Data transmission method, terminal and control node

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a data transmission method, a terminal, and a control node.

Background

A New Radio (NR) system of the fifth Generation (5Generation, 5G) supports a sidelink (or a sidelink, or the like) from Release 16, and can be used for an operating frequency band above 6GHz that is not supported by Long Term Evolution (LTE), and support a larger operating bandwidth. The NR sidelink supports various transmission modes such as unicast, multicast, and broadcast, and supports Hybrid Automatic Repeat Request (HARQ) in the unicast and multicast modes. The HARQ response is sent through a Physical Sidelink Feedback Channel (PSFCH). In addition, the NR sidelink also supports various resource allocation modes, such as a base station scheduling mode, a UE autonomous resource selection mode, or a UE forwarding configuration to other UEs, and the like.

Current 5G NR sidelink systems support a mode-1 resource allocation mode, i.e. a scheduling node (e.g. a base station) schedules a user's transmission on sidelink, when the base station allocates resources for sidelink transmission.

The whole time delay of the scheme is large, and the base station can know whether the scheduling is successful or not through 4 steps. In addition, in Sidelink, a Physical downlink Control Channel (PSCCH) and a non-data Channel such as a PSFCH (pseudo pilot Channel) are required between UEs, which increases Sidelink overhead.

Disclosure of Invention

The embodiment of the invention provides a data transmission and transmission method, a terminal and a control node, which aim to solve the problems that the scheduling time delay and the sidelink overhead are increased by the conventional resource allocation and scheduling mode of sidelink.

In order to solve the technical problem, the embodiment of the invention adopts the following implementation scheme:

in a first aspect, an embodiment of the present invention provides a data transmission method, applied to a terminal, including:

acquiring first information;

acquiring a scheduling instruction aiming at the direct communication link sent by the control node according to the first information;

transmitting data according to the scheduling instruction;

wherein the first information comprises: and the scheduling identifier is used for indicating the terminal to monitor the scheduling instruction.

In a second aspect, an embodiment of the present invention provides a data sending method, applied to a control node, including:

generating a scheduling instruction for the direct communication link according to the first information;

sending the scheduling instruction to a terminal;

In a third aspect, an embodiment of the present invention provides a terminal, including:

the first acquisition module is used for acquiring first information;

a second obtaining module, configured to obtain, according to the first information, a scheduling instruction for the direct communication link sent by the control node;

the transmission module is used for transmitting data according to the scheduling instruction;

In a fourth aspect, an embodiment of the present invention provides a terminal, where the terminal includes: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data transmission method described above.

In a fifth aspect, an embodiment of the present invention provides a control node, including:

the generating module is used for generating a scheduling instruction aiming at the direct communication link according to the first information;

the first sending module is used for sending the scheduling instruction to the terminal;

In a sixth aspect, an embodiment of the present invention provides a control node, where the control node includes: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data transmission method described above.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores thereon a computer program, and the computer program, when executed by a processor, implements the steps of the above-mentioned data transmission method or the steps of the above-mentioned data transmission method.

The invention has the beneficial effects that:

according to the scheme, the terminal transmits data directly according to the scheduling instruction which is sent by the control node and aims at the direct communication link, so that the scheduling time delay and the direct communication link resource overhead can be reduced.

Drawings

FIG. 1 is a diagram illustrating a conventional communication process for performing direct communication link scheduling;

FIG. 2 is a flow chart of a data transmission method according to an embodiment of the invention;

FIG. 3 is a flow chart of a data transmission method according to an embodiment of the present invention;

fig. 4 shows a block diagram of a terminal according to an embodiment of the invention;

fig. 5 shows a block diagram of a terminal according to an embodiment of the present invention;

FIG. 6 is a block diagram of a control node according to an embodiment of the present invention;

fig. 7 is a block diagram showing a control node according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.

In describing the embodiments of the present invention, a description will first be given of a conventional technique related to the embodiments of the present invention as follows.

A Long Term Evolution (LTE) system supports sidelink from a12 th release version, and is used for direct data transmission between User equipments (UEs, also called terminals) without using a network device.

The UE transmits direct communication link Control Information (SCI) through a Physical direct communication link Control Channel (PSCCH), and schedules transmission of a Physical direct communication link Shared Channel (PSCCH) to transmit data. The transmission is in a broadcast form, and the receiving end does not acknowledge to the transmitting end whether the reception is successful.

The LTE sidelink design supports two resource allocation modes, namely a Scheduled resource allocation (Scheduled resource allocation) mode and an autonomous resource selection (autonomous resource selection) mode. The former is controlled by network side equipment and allocates resources for each UE, and the latter is selected by the UE autonomously.

From release 15, LTE supports sidelink Carrier Aggregation (CA). Unlike the interface between the terminal and the network (i.e., Uu interface, i.e., downlink and uplink), the CA of LTE sidelink has no division between Primary Component Carrier (PCC) and Secondary Component Carrier (SCC). The UE in autonomous resource selection mode performs resource sensing (sensing) and resource reservation independently on each CC.

The design of LTE sidelink is suitable for specific public safety affairs (emergency communication in disaster places such as fire places or earthquakes), vehicle network communication from vehicle to everything (V2X), and the like. The internet of vehicles communication includes various services, such as basic security type communication, advanced (automated) driving, formation, sensor expansion, and the like. Since LTE sidelink supports only broadcast communication, and is therefore mainly used for basic security class communication, other advanced V2X services will be supported by NR sidelink.

For mode-1 of the 5G NR sidelink system, the base station allocates resources for sidelink transmission through one Downlink Control Information (DCI), where the resource allocation includes resource allocation of PSCCH (data channel on sidelink) and PSCCH (control channel on sidelink), and after receiving the configuration, the transmitting user (UE1) transmits SCI and data on the allocated resources, where the SCI carries information related to the scheduled data, such as resource allocation, modulation and coding, and the like. The receiving user (UE2) performs HARQ feedback on the feedback channel (PSFCH) on sidelink. The UE1 forwards the feedback result to the base station, which is implemented as shown in fig. 1.

In this implementation, the receiving end UE needs to monitor the PSCCH all the time to obtain sidelink data sent by the sending end, and this processing procedure has high complexity and high energy consumption.

In addition, note that each UE on sidelink may be a transmitting end or a receiving end, which means that each UE needs to monitor PDCCH, PSCCH, and demodulate PSFCH to obtain HARQ feedback. This may cause half-duplex restrictions, e.g., the UE may not be able to transmit psch or PUCCH when detecting PSCCH. The scheduling node needs to take this limitation into full account, resulting in high implementation complexity and a limitation on sidelink data rate of the UE.

The invention provides a data transmission and transmission method, a terminal and a control node, aiming at the problem that the scheduling time delay and the sidelink overhead are increased by the existing resource allocation and scheduling mode of sidelink.

As shown in fig. 2, an embodiment of the present invention provides a data transmission method, which is applied to a terminal, and includes:

step 201, acquiring first information;

note that the first information includes: and a scheduling identifier, configured to instruct the terminal to monitor a scheduling instruction, where the scheduling identifier is, for example, a Radio Network Temporary Identifier (RNTI).

The monitoring of the scheduling instruction includes: and carrying out blind detection on the scheduling command, and/or receiving and demodulating the detected scheduling command.

Step 202, obtaining a scheduling instruction aiming at the direct communication link sent by the control node according to the first information;

it should be noted that the control node may be a network side device (e.g., a base station), a Road Side Unit (RSU), a Relay device (Relay), an Integrated Access and Backhaul (IAB) node, or another terminal different from the terminal in the embodiment of the present invention.

Step 203, transmitting data according to the scheduling instruction;

the data transmission may be performed by data transmission or data reception, that is, only data transmission or data reception may be performed by the same terminal at one time, and data transmission or data reception may be performed by the same terminal at a different time.

It should be noted that, in the embodiments of the present invention, the data transmission refers to: in the direct communication link, the transmission of data is performed.

In the embodiment of the invention, as long as the terminal receives the scheduling instruction, the data is transmitted or received in the direct communication link, so that the scheduling time delay can be reduced, and the transmission efficiency of the data is improved.

It should be further noted that, the specific implementation manner of step 201 is:

monitoring a scheduling instruction aiming at a direct communication link in a first search space of a control channel;

wherein the scheduling instruction is associated with the scheduling identifier, and the first search space includes: a common search space (common search space), a group common search space (group common search space), or a terminal-specific search space (UE-specific search space).

Specifically, the terminal needs to monitor (e.g., blind detect) a scheduling instruction for the direct communication link in the first search space of the control channel, perform cyclic redundancy check and scheduling identifier matching on the monitored scheduling instruction, and acquire the scheduling instruction matched with the scheduling identifier.

It should be noted that, when the control node is a network side device, an RSU, a Relay, or an IAB node, the control channel is a physical downlink control channel, and the scheduling instruction is DCI; when the control node is another terminal different from the terminal of the embodiment of the present invention, the control channel is a physical direct communication link control channel, and the scheduling instruction is SCI.

Further, the scheduling instruction may be dynamically scheduled or activate/deactivate a configuration grant (configured grant).

It should be noted that the scheduling commands received by different terminals may be the same or different.

It should also be noted that the scheduling identifier obtained by the terminal may be configured by the control node or agreed by a protocol.

Specifically, when the scheduling identifier can be configured by the control node, the specific configuration manner includes one of the following:

in the first mode, the control node allocates the same scheduling identifier for two unicast terminals;

for example, the control node allocates the same RNTI for unicast for both terminals that are unicast.

In the second mode, the control node allocates the same scheduling identifier to the terminals in the same group;

for example, the control node allocates the same RNTI to all terminals in the same group for multicast in the group.

The control node configures at least one special scheduling identifier for the terminal to broadcast in the direct communication link;

for example, the control node may allocate one or several dedicated RNTIs (special RNTIs) for the terminals to broadcast on the direct communication link.

Specifically, when the scheduling identifier is defined by a protocol, it indicates that all terminals share the scheduling identifier, and may also indicate that the scheduling identifier may be used for unicast, multicast, or broadcast of the direct communication link.

The following describes a specific implementation of step 203 in different cases.

Situation one, the scheduling identifier is also used for indicating the transmission state of the terminal

It should be noted that, in this case, the scheduling identifier acquired by the terminal may be a dedicated scheduling identifier, the scheduling identifier and the transmission indication jointly encode to form a dedicated scheduling identifier, and the transmission state of the terminal may be indirectly obtained through the scheduling identifier, where it is noted that the transmission state of the terminal includes: the data transmission and reception are performed in two transmission states.

It should be noted that, in a specific implementation, different scheduling identifiers may be used to indicate different transmission statuses of the same terminal, that is, one scheduling identifier is used to indicate a transmission status for transmitting data, and another scheduling identifier is used to indicate a transmission status for receiving data.

For example, if the scheduling flag RNTIz indicates that the transmission state of the terminal is to transmit data, the scheduling flag RNTIz + n indicates that the transmission state of the terminal is to receive data.

Specifically, after receiving a corresponding scheduling instruction by using a scheduling identifier, the terminal transmits data according to a transmission state indicated by the scheduling identifier;

in order to smoothly transmit data, the scheduling command includes information necessary for transmitting and receiving data of the direct communication link, for example, resource allocation information (for example, time domain resources and frequency domain resources used for transmitting and receiving data, antennas used for transmitting and receiving data, beams used for transmitting and receiving data, frequency points used for transmitting and receiving data), coding information, and the like.

The terminal transmits data by using the information indicated by the scheduling command, and it should be further noted that the data transmission is implemented by:

in a first implementation manner, when the transmission state of the terminal is data transmission, the implementation manner of data transmission is as follows: and carrying out data transmission on the direct communication link according to the information indicated by the scheduling instruction.

It should be noted that, in this case, since the terminal performing data reception (i.e., the receiving end) and the terminal performing data transmission (i.e., the transmitting end) acquire the same DCI information, the transmitting end does not need to transmit direct communication control information (SCI) on the direct communication link to indicate how the receiving end acquires the direct communication link data, that is, the PSCCH resource does not need to be allocated on the direct communication link, so that signaling overhead is saved, and further, the saved direct communication link resource can be used for data transmission, thereby improving spectrum efficiency.

And in a second implementation manner, when the transmission state of the terminal is data reception, the implementation manner of data transmission is as follows: and receiving data on the direct communication link according to the information indicated by the scheduling instruction.

It should be noted that, in this case, the terminal performing data reception does not need to monitor the PSCCH on the direct communication link, which reduces power consumption and processing complexity of the terminal.

Further, when the terminal needs to feed back the demodulation result, the terminal feeds back the data demodulation result to the control node, for example, feeds back a hybrid automatic repeat request acknowledgement (HARQ-ACK) to the control node through a Physical Uplink Control Channel (PUCCH).

It should be noted that, in this case, the terminal that performs data transmission does not need to execute a procedure of receiving the PSFCH feedback of the direct communication link first and then forwarding the PSFCH feedback to the control node, so that PSFCH resources do not need to be allocated on the direct communication link, signaling overhead is saved, and further, the saved direct communication link resources can be used for data transmission, thereby improving spectrum efficiency; for the multicast scene, a plurality of terminals for receiving data can feed back simultaneously, so that the feedback time delay is reduced, and the problem of half-duplex limitation is greatly reduced.

Taking the control node as the base station as an example, the following implementation flows are illustrated in this case:

a11, the base station respectively allocates RNTIs for receiving and sending to UE1 and UE2 for sidelink transmission;

wherein for the UE1, SL-T-RNTI-1 is used for transmission and SL-R-RNTI-1 is used for reception; for the UE2, SL-T-RNTI-2 is used for transmission and SL-R-RNTI-2 is used for reception.

A12, the base station dispatches UE1 to send sidelink unicast data to UE 2;

the base station generates scheduling DCI (e.g., DCI format 3-1) to the UE1, scrambles using SL-T-RNTI-1, and transmits through the PDCCH; meanwhile, the base station generates scheduling DCI to the UE2, scrambles it with SL-R-RNTI-2, and transmits it through the PDCCH.

A13, UE1 and UE2 monitor PDCCH by using SL-T-RNTI and SL-R-RNTI respectively, and decode and demodulate scheduling DCI.

A14 and UE1 use SL-T-RNTI-1 to successfully demodulate DCI, so that the UE knows that the UE is the sending end UE, and UE2 uses SL-R-RNTI-2 to successfully demodulate DCI, so that the UE knows that the UE is the receiving end UE.

A15 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A16 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

It should be noted that, in the above example, SL-T-RNTI-1 may be the same as SL-R-RNTI-2, and SL-T-RNTI-2 may be the same as SL-R-RNTI-1.

And a second situation, in which a transmission instruction is defined in advance, and the terminal transmits data according to the transmission state indicated by the analyzed transmission instruction

Specifically, in this case, the implementation manner of step 203 is:

acquiring a transmission indication domain in the scheduling instruction;

determining the transmission state of the terminal according to the second information in the transmission indication domain;

transmitting data according to the transmission state;

it should be noted that the second information is transmission state identification information.

Specifically, the transmission indication field is used for indicating one of the following information:

m11, indicating at least one terminal for data transmission;

in this case, the transmission instruction field indicates only the transmission state in which data transmission is performed.

M12, indicating at least one terminal for data reception;

in this case, the transmission indication field indicates only the transmission state in which data reception is performed.

M13 indicating at least one terminal for data transmission and at least one terminal for data reception, respectively;

in this case, the transmission instruction field indicates both a transmission state in which data reception is performed and a transmission state in which data transmission is performed.

Optionally, the transmission indication field includes 1 bit, and the bit is used for indicating a transmission status; alternatively, the transmission indication field includes several bits (e.g., some or all bits of the terminal ID) for indicating a transmission status; or, the transmission indication field includes a bitmap (bitmap), and each bit in the bitmap is used for indicating the transmission state of a terminal.

The terminal transmits data using information (e.g., the above-mentioned resource allocation information, coding information, etc.) indicated by the scheduling command, and further, the terminal transmits data in an implementation manner that:

a21, the base station allocates RNTI (e.g., SL-U-RNTI, where UE1 ═ m and UE2 ═ n) to UE1 and UE2, respectively, for sidelink transmission, and defines transmission indicator 0 as transmission and 1 as reception.

A22, the base station schedules UE1 to send sidelink unicast data to UE 2. The base station generates two scheduling DCIs (e.g., DCI format 3-1) to UE1 and UE2, respectively, wherein the DCI sent to UE1 is scrambled using m, wherein transmission state identification information ID is 0; scrambling DCI addressed to the UE2 with n, where transmission state identification information ID is 1; and transmitted through the PDCCH.

A23, UE1 and UE2 monitor PDCCH by using SL-U-RNTI m and n respectively, and decode and demodulate scheduling DCI.

A24 and UE1 find that the transmission status identification information ID in the transmission indication field is 0, so that they know that they are the sending UE; the UE2 finds that the transmission state identification information ID in the transmission indication field is 1, and thus knows that it is the receiving UE.

A25 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A26 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Case three, the first information further includes: at least one transmission identifier for indicating a terminal to transmit or receive data

Specifically, in this case, the implementation manner of step 203 is:

determining the transmission state of the terminal according to the indication information in the transmission indication domain in the scheduling instruction and the at least one transmission identifier;

and transmitting data according to the transmission state.

That is to say, in this case, the transmission indication field includes the transmission identifier, and the terminal needs to determine the transmission state according to the transmission identifier in the transmission indication field and the transmission identifier that the terminal has acquired.

Specifically, the obtaining manner of the at least one transmission identifier includes at least one of the following:

m21, receiving at least one transmission identification distributed by the control node;

m22, generating at least one transmission identifier according to the high-level information;

it should be noted that the high-level information may be: an application layer or IP layer ID, a Media Access Control (MAC) layer terminal ID, etc.

M23, generating at least one transmission identifier according to the configuration rule of the control node.

It should be noted that the transmission identifier may be 1 bit or more, for example, the transmission identifier may use part or all of the bits of the terminal ID.

It should be further noted that the transmission identifier may be a multicast ID or an ID matching multiple terminals, and is used to indicate a multicast scenario.

Further, the determining the transmission state of the terminal according to the indication information in the transmission indication field in the scheduling instruction and the at least one transmission identifier includes one of:

m31, if the transmission identifier of the terminal is matched with the indication information, determining that the transmission state of the terminal is a first state;

m32, if the transmission identifier of the terminal is not matched with the indication information, determining that the transmission state of the terminal is a second state;

one of the first state and the second state is for data transmission, and the other is for data reception.

It should be noted that, the transmission indication field is used to indicate one of the following information:

m41, indicating at least one terminal for data transmission;

M42, indicating at least one terminal for data reception;

M43 indicating at least one terminal for data transmission and at least one terminal for data reception, respectively;

Optionally, the transmission indication field includes 1 bit, and the bit is used for indicating a transmission status; alternatively, the transmission indication field includes several bits (e.g., some or all bits of the terminal ID) for indicating a transmission status; or, the transmission indication field includes a bitmap, and each bit in the bitmap is used to indicate a transmission status of a terminal.

It should be noted that, in this case, since the terminal performing data reception (i.e., the receiving end) and the terminal performing data transmission (i.e., the transmitting end) acquire the same DCI information, the transmitting end does not need to transmit direct communication control information (SCI) on the direct communication link to indicate how the receiving end acquires the direct communication link data, that is, the direct communication link does not need to allocate physical direct communication control channel (PSCCH) resources, which saves signaling overhead, and further, the saved direct communication link resources can be used for data transmission, thereby improving spectrum efficiency.

example 1, the base station configures the same DCI for the terminal, and the transmission status indicated by the transmission indication field is data transmission

First, when a direct communication link unicast is in progress

A31, the base station assigns RNTI (e.g., SL-G-RNTI) to UE1, UE2 for sidelink transmission, and assigns transmission ID of UE1 and UE2 as 0 and 1, respectively.

A32, the base station schedules UE1 to send sidelink unicast data to UE2, the base station generates scheduling DCI (e.g. DCI format 3-1) to UE1 and UE2, wherein the transmission indication field is 0, scrambles the DCI using SL-G-RNTI, and sends through PDCCH.

A33, UE1, and UE2 monitor PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A34, UE1 finds that the transmission ID allocated to it in the transmission indication field is 0, thereby knowing that the UE is the sending end; the UE2 finds that the transmission indication field does not match its ID and knows that it is the receiving UE.

A35 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A36 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Second, when broadcasting of direct communication link is carried out

A41, the base station allocates sidelink broadcast RNTI (for example SL-B-RNTI) to the UE, and allocates transmission identification IDs of the UE1 and the UE2 to be 0 and 1 respectively;

wherein the RNTI may be protocol predefined, or vendor pre-configured.

A42, when base station scheduling UE1 transmits sidelink broadcast data, generating scheduling DCI, wherein the transmission identifier ID in the transmission indication domain is 0, scrambling the DCI by using SL-B-RNTI, and transmitting the data through PDCCH.

A43, UE1, and UE2 monitor the PDCCH using SL-B-RNTI, decode and demodulate the scheduling DCI.

A44, UE1 finds that the transmission indication domain is the transmission ID assigned to it is 0, thus knowing that the UE is the sending end; the other UEs find that the transmission indication field does not match its ID, and thus know that they are the receiving UEs of the broadcast data.

A45 and UE1 transmit broadcast data on sidelink using the coding scheme and resources indicated by the DCI.

A46, the other UE receives the broadcast data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by the DCI.

Example 2, the base station configures the same DCI for the terminal, and the transmission status indicated by the transmission indication field is for receiving data and performing unicast of the direct communication link

A51, the base station allocates RNTI (e.g. SL-G-RNTI) to UE1 and UE2 for sidelink transmission, and allocates transmission identity IDs of UE1 and UE2 to be 0 and 1 respectively.

A52, the base station schedules UE1 to send sidelink unicast data to UE2, the base station generates scheduling DCI (e.g. DCI format 3-1) to UE1 and UE2, wherein the transmission identifier ID in the transmission indication field is 1, the DCI is scrambled by using SL-G-RNTI and sent through PDCCH.

A53, UE1, and UE2 monitor PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A54, UE2 finds that the transmission indication domain is the transmission ID assigned to it is 1, thus knowing that it is the receiving UE; the UE1 finds that the transmission indication field does not match its transmission identification ID, and knows that it is the sending UE.

A55 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A56 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Example 3, the base station configures the same DCI for the terminal, and the transmission status indicated by the transmission indication field is for data reception and data transmission, and unicast of the direct communication link is performed

A61, the base station allocates RNTI (e.g. SL-G-RNTI) to UE1 and UE2 for sidelink transmission, and allocates transmission identity IDs of UE1 and UE2 to be 0 and 1 respectively.

A62, the base station schedules UE1 to send sidelink unicast data to UE2, the base station generates scheduling DCI (e.g. DCI format 3-1) to UE1 and UE2, wherein the transmission identifier ID in the transmission indication field includes 0 and 1, 0 represents the transmitting end, 1 represents the receiving end, the DCI is scrambled by using SL-G-RNTI and sent through PDCCH.

A63, UE1, and UE2 monitor PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A64, UE1 finds that the transmission indication domain sender is the transmission ID assigned to it is 0, thus knowing that it is the sender UE; the UE2 finds that the transmission indicates that the domain receiver is 1 for the transmission ID assigned to it, and thus knows that it is the receiver UE.

A65 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A66 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Example 4, the base station configures the same DCI for the terminal, and transmits the terminal ID bits with partial or full identifier

First, when a direct communication link unicast is in progress

A71, UE1 and UE2 obtain RNTI and transmission identity ID;

wherein the RNTI may be a RNTI (e.g., SL-X-RNTI) allocated by a base station or predefined by a protocol, and the transmission identity ID may be a part or all of the UE ID bits, generated by the UE or allocated by the network.

A72, the base station schedules UE1 to send sidelink unicast data to UE2, the base station generates scheduling DCI (e.g. DCI format 3-1) to UE1 and UE2, wherein the transmission identifier in the transmission indication field is used for indicating the transmission state for data transmission and the transmission state for data reception, the transmission identifier ID of UE1 is sent for data transmission (namely the sending end), the transmission identifier ID of UE2 is sent for data reception (the receiving end), and the DCI is scrambled by using SL-X-RNTI and sent through PDCCH.

A73, UE1, and UE2 monitor PDCCH using SL-X-RNTI, decode and demodulate the scheduling DCI.

A74, UE1 finds that the transmission indication domain sender is ID of itself, thus knowing that it is sender UE; the UE2 finds that the transmission indicates that the domain receiver is its own ID and thus knows that it is a receiver UE.

A75 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A76 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Secondly, when the multicast of the direct communication link is carried out

A81, UE1 and UE2 obtain RNTI and transmission identity ID;

A82, the base station schedules the UE1 to send a multicast message, the base station generates scheduling DCI (e.g. DCI format 3-1) to the UE1 and the UE2, wherein the transmitting end indicated by the transmission identifier in the transmission indication domain is the transmission identifier ID of the UE1, the receiving end indicated by the transmission identifier is the multicast ID, the DCI is scrambled by using SL-X-RNTI and sent through PDCCH.

A83, UE1, and UE2 monitor PDCCH using SL-X-RNTI, decode and demodulate the scheduling DCI.

A84, UE1 finds that the transmission indication domain sender is ID of itself, thus knowing that it is sender UE; the UE2 finds the multicast ID that the transmission indicates to the receiving end as it needs to receive, and thus knows that it is the receiving UE.

A85 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A86 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Example 5, the base station configures the same DCI for the terminals, the transmission status indicated by the transmission indication field is for data reception and data transmission, and there are multiple terminals receiving the information

First, when a direct communication link unicast is in progress

A91, the base station allocates RNTI (for example, SL-G-RNTI) to UE1, UE2 and UE3 for sidelink transmission, and allocates transmission ID of UE1, UE2 and UE3 to be 0, 1 and 2 respectively, and transmission ID 3 is used for indicating multicast reception.

A92, the base station schedules the UE1 to send sidelink unicast data to the UE2, the base station generates a scheduling DCI (e.g. DCI format 3-1) to the UE, wherein the sending end indicated by the transmission identifier in the transmission indication field is 0, the receiving end is 1, the DCI is scrambled by using SL-G-RNTI and sent through PDCCH.

A93, UE1, UE2, and UE3 monitor PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A94, UE1 finds that the transmission indication domain sender is the transmission ID assigned to it is 0, thus knowing that it is the sender UE; the UE2 finds that the transmission indication field receiver is 1 for the transmission identifier ID assigned to it, and thus knows that it is a receiver UE; the UE3 finds that its transmission ID does not match either the sender or the receiver, and therefore interrupts the process and continues to monitor the PDCCH.

A95 and UE1 use the coding scheme and resources indicated by the DCI to transmit data to UE2 on sidelink.

A96 and UE2 receive data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Secondly, when the multicast of the direct communication link is carried out

A101, the base station allocates RNTI (for example, SL-G-RNTI) to UE1, UE2 and UE3 for sidelink transmission, and allocates transmission identification IDs of UE1, UE2 and UE3 to be 0, 1 and 2 respectively, and transmission identification ID 3 is used for indicating multicast reception.

A102, the base station schedules the UE1 to send a multicast message, the base station generates scheduling DCI (e.g. DCI format 3-1) to the UE1, the UE2 and the UE3, wherein a transmitting end indicated by a transmission identifier in a transmission indication domain is 0, namely the transmission identifier ID of the UE1, a receiving end indicated by the transmission identifier is 3, namely the transmission identifier ID of the multicast, the DCI is scrambled by using SL-X-RNTI and sent through the PDCCH.

A103, UE1, UE2, and UE3 monitor the PDCCH using SL-X-RNTI, decode and demodulate the scheduling DCI.

A104, UE1 finds that the transmission indication domain sender is ID of itself, thus knowing that it is sender UE; the UE2 and UE3 find the transmission indicates the domain receiver as a multicast ID that the receiver needs to receive for itself, and thus know that it is the receiver UE.

A105 and UE1 use the DCI indicated coding scheme and resource to transmit data to UE2 on sidelink.

A106, UE2, and UE3 receive the data transmitted by UE1 on sidelink according to the coding scheme and resource indicated by the DCI, and feed back the demodulation result (ACK or NACK) to the base station.

Example 6, the base station configures the same DCI for the terminal, the transmission indication field is a bitmap, and the direct communication link multicast is performed

A111, the base station allocates RNTIs (for example, SL-G-RNTIs) to the UE1, the UE2 and the UE3 for sidelink transmission, and the transmission identification ID is 3-bit long bitmap, wherein 1 st, 2 nd and 3 rd bits are respectively allocated to the UE1, the UE2 and the UE3, a bit value of 0 represents the indication of a transmitting end, and a bit value of 1 represents the indication of a receiving end.

A112, the base station schedules the UE1 to send sidelink multicast data to the UE2 and the UE3 in the group, the base station generates a scheduling DCI (e.g. DCI format 3-1), wherein the transmission indication field is 011, scrambles the DCI by using SL-G-RNTI, and sends the data through the PDCCH.

A113, UE1, UE2, and UE3 monitor the PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A114, UE1 find that the 1 st bit in the transmission indication field is 0, so that it knows that it is the sending end UE; UE2 and UE3 find that the 2 nd and 3 rd bits of the transmission indicator field are 1, so that the scheduling is known to be multicast data, and UE2 and UE3 are receiving UEs.

A115 and UE1 use the coding scheme and resources indicated by the DCI to transmit multicast data on sidelink.

A116, UE2, and UE3 receive the data sent by UE1 on sidelink according to the coding scheme and resource indicated by the DCI, and feed back the demodulation result to the base station.

Example 7 first implementation of the Transmission identifier Using bitmap

A121, the base station allocates RNTIs (for example, SL-G-RNTIs) to the UE1, the UE2, the UE3 and the UE4 for sidelink transmission, and allocates transmitting end transmission identifiers IDs of the UE1, the UE2, the UE3 and the UE4 to be 0, 1, 2 and 3 respectively, and a receiving end transmission identifier ID to be a bitmap with the length of 4 bits, wherein the 1 st, 2 nd, 3 th and 4 th bits are allocated to the UE1, the UE2, the UE3 and the UE4 respectively, a bit value of 0 indicates no reception, and a bit value of 1 indicates reception.

A122, the base station schedules the UE1 to send sidelink multicast data to the UE2 and the UE3 in the group, the base station generates a scheduling DCI (e.g. DCI format 3-1), wherein the transmission indication domain of the sending end is 0, the transmission indication domain of the receiving end is 0110, the DCI is scrambled by using SL-G-RNTI, and the DCI is sent through the PDCCH.

A123, UE1, UE2, UE3, and UE4 monitor the PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A124, UE1 finds that the transmission ID allocated to it by the transmitting end indicated by the transmission ID in the transmission indication domain is 0, so that it knows that it is the transmitting end UE; UE2 and UE3 find that the 2 nd and 3 rd bits of the receiver-side transmission indicator field are 1, so that UE2 and UE3 are known as receiver-side UEs; the UE4 finds that its ID does not match either the sender or the receiver, and therefore interrupts the process and continues to monitor the PDCCH.

A125 and UE1 use the coding scheme and resources indicated by the DCI to transmit multicast data on sidelink.

A126, UE2 and UE3 receive the data sent by UE1 on sidelink according to the coding scheme and resource indicated by the DCI, and feed back the demodulation result to the base station.

Example 8, a second implementation manner in which the transmission identifier is represented by bitmap is a further optimization manner of the foregoing example 7, because the sending-end UE obviously cannot receive data, the size of the bitmap indicated by the receiving-end transmission in actual DCI transmission may be reduced by one from the total number of UEs, that is, the bit allocated by the UE indicated by the sending-end transmission is subtracted from the original bitmap, and when the UE receives the DCI, the UE constructs a correct bitmap according to the ID indicated by the sending-end transmission, so that the DCI overhead may be reduced.

A131, the base station allocates RNTIs (for example, SL-G-RNTIs) to UE1, UE2, UE3 and UE4 for sidelink transmission, and allocates transmitting end transmission identifiers IDs of UE1, UE2, UE3 and UE4 to be 0, 1, 2 and 3 respectively, and a receiving end transmission identifier ID to be bitmap with 4-bit length, wherein 1, 2, 3 and 4 bits are allocated to UE1, UE2, UE3 and UE4 respectively, a bit value of 0 indicates no reception, and a bit value of 1 indicates reception.

A132, the base station schedules the UE2 to send sidelink multicast data to the UE1 and the UE3 in the group, the base station generates a scheduling DCI (e.g. DCI format 3-1), wherein the transmission identifier ID of the sending end indicated by the transmission identifier in the transmission indication domain is 1, the receiving end bitmap indicated by the transmission identifier in the transmission indication domain is 110, the DCI is scrambled by using SL-G-RNTI, and the DCI is sent through the PDCCH.

A133, UE1, UE2, UE3, and UE4 monitor the PDCCH using SL-G-RNTI, decode and demodulate the scheduling DCI.

A134, UE2 find that the transmission ID allocated to it by the transmitting end indicated by the transmission ID in the transmission indication domain is 1, so that it knows that it is the transmitting end UE; UE1, UE3, and UE4 know that UE2 is the sender UE, and reconstruct the receiver transport indicator field in DCI to 1010 (padding bit 2 to 0). UE1 and UE3 find the 1 st and 3 rd bits of the receiver-side transmission indicator field to be 1, and thus know that UE2 and UE3 are receiver-side UEs. The UE4 finds that its ID does not match either the sender or the receiver, and therefore interrupts the process and continues to monitor the PDCCH.

A135 and UE2 use the coding scheme and resources indicated by the DCI to transmit multicast data on sidelink.

A136, UE1, and UE3 receive the data sent by UE2 on sidelink according to the coding scheme and resource indicated by the DCI, and feed back the demodulation result to the base station.

The following describes an implementation of the present invention by taking a control node as a terminal (C-UE) as an example:

a141, a plurality of UEs communicate through sidelink, and the control node C-UE schedules and distributes the transmission of the UE1 and the UE 2.

A142, C-UE dispatches UE1 to send sidelink unicast data to UE2, and C-UE generates dispatching SCI, wherein the sending end indicated by the transmission identification in the transmission indication domain is UE1ID, the receiving end is UE-2ID, and the dispatching SCI is sent through PSCCH.

A143, UE1 and UE2 use listen to the PSCCH and demodulate the scheduled SCI.

A144, UE1 finds that the sender indicated by the transmission identifier in the transmission indication field is its own UE ID, and thus knows that it is the sender UE; the UE2 finds that the receiver indicated by the transmission identity in the transmission indication field is its UE ID, and thus knows that it is the receiver UE.

A145 and UE1 use the coding scheme and resources indicated by SCI to send data to UE2 on sidelink.

A146, C-UE dispatches UE1 to send multicast message, C-UE generates dispatching SCI, wherein the sending end of transmission indication domain is UE1ID, the receiving end is multicast ID, and sends through PSCCH.

A147, UE1 and UE2 use listen to the PSCCH and demodulate the scheduled SCI.

A148, UE1 finds that the transmission indication domain sender is its own UE ID, thus knowing that it is the sender UE; the UE2 discovers the multicast ID for which the transmission indicates the domain receiver is interested, and thus knows that it is the receiver UE.

A149 and UE1 use the coding scheme and resources indicated by SCI to transmit multicast data on sidelink.

It should be noted that the embodiment of the present invention may be extended to a similar scenario of LTE sidelink; or in the NR/LTE uplink scheduling scene, the UE knows the uplink scheduling of other UE by receiving DCI, thereby carrying out uplink Multiple Input Multiple Output (MIMO) transmission or interference coordination.

The embodiment of the invention can support various services such as unicast, multicast or broadcast, etc., reduce scheduling delay and system overhead, improve spectrum efficiency, reduce terminal energy consumption and solve the half-duplex problem.

As shown in fig. 3, an embodiment of the present invention provides a data sending method, applied to a control node, including:

step 301, generating a scheduling instruction for the direct communication link according to the first information;

step 302, sending the scheduling instruction to a terminal;

Optionally, the scheduling identifier is further used to indicate a transmission status of the terminal.

Optionally, the scheduling instruction includes: a transmission indication field for indicating one of the following information:

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

at least one terminal for data transmission and at least one terminal for data reception are indicated, respectively.

Specifically, the transmission indication field includes 1 bit, or the transmission indication field includes a bitmap, and each bit in the bitmap is used to indicate a transmission status of a terminal.

Optionally, before the step 301, the method further includes:

configuring a scheduling identifier;

and sending the scheduling identification to the terminal.

Further, the configuring of the scheduling identifier includes at least one of:

distributing the same scheduling identification for the two unicast terminals;

distributing the same scheduling identification for the terminals in the same group;

at least one dedicated scheduling identity is configured for the terminal to broadcast on the direct communication link.

Optionally, after the sending the scheduling instruction to the terminal, the method further includes:

receiving a data demodulation result fed back by the terminal;

and the data demodulation result is that the terminal receives data according to the information indicated by the scheduling instruction and feeds back the data to the control node.

It should be noted that the control node may be a network side device, a Road Side Unit (RSU), a Relay device (Relay), an IAB node, or another terminal different from the terminal performing the data transmission method.

It should be noted that all the descriptions regarding the control node in the above embodiments are applied to the embodiment of the data transmission method, and the same technical effects can be achieved.

As shown in fig. 4, an embodiment of the present invention provides a terminal 400, including:

a first obtaining module 401, configured to obtain first information;

a second obtaining module 402, configured to obtain, according to the first information, a scheduling instruction for the direct communication link sent by the control node;

a transmission module 403, configured to transmit data according to the scheduling instruction;

Optionally, the second obtaining module 402 is configured to:

wherein the scheduling instruction is associated with the scheduling identifier, and the first search space includes: a common search space, a group common search space, or a terminal-specific search space.

Optionally, the scheduling identifier is further configured to indicate a transmission status of the terminal, and the transmission module 403 is configured to:

and transmitting data according to the transmission state indicated by the scheduling identification.

Optionally, the transmission module 403 includes:

a first obtaining unit, configured to obtain a transmission indication field in the scheduling instruction;

a first determining unit, configured to determine a transmission state of the terminal according to the second information in the transmission indication field;

the first transmission unit is used for transmitting data according to the transmission state;

and the second information is transmission state identification information.

Optionally, the first information further includes: at least one transmission identifier for instructing the terminal to perform data transmission or data reception, where the transmission module 403 includes:

a second determining unit, configured to determine a transmission state of the terminal according to the indication information in the transmission indication field in the scheduling instruction and the at least one transmission identifier;

and the second transmission unit is used for transmitting data according to the transmission state.

receiving at least one transmission identifier allocated by the control node;

generating at least one transmission identifier according to the high-level information;

and generating at least one transmission identifier according to the configuration rule of the control node.

Optionally, the second determining unit is configured to implement one of:

if the transmission identifier of the terminal is matched with the indication information, determining that the transmission state of the terminal is a first state;

if the transmission identifier of the terminal is not matched with the indication information, determining that the transmission state of the terminal is a second state;

one of the first state and the second state is used for data transmission, and the other one is used for data reception.

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

Optionally, when the transmission state of the terminal is data transmission, the data transmission is performed in the following manner:

and carrying out data transmission on the direct communication link according to the information indicated by the scheduling instruction.

Optionally, when the transmission state of the terminal is data reception, the data transmission is performed in the following manner:

and receiving data on the direct communication link according to the information indicated by the scheduling instruction.

Further, after the data reception is performed on the direct communication link, the method further includes:

and the feedback module is used for feeding back a data demodulation result to the control node.

It should be noted that the terminal embodiment is a terminal corresponding to the data transmission method applied to the terminal, and all implementation manners of the above embodiments are applicable to the terminal embodiment, and the same technical effects as those of the terminal embodiment can also be achieved.

Fig. 5 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present invention.

The terminal 50 includes but is not limited to: radio unit 510, network module 520, audio output unit 530, input unit 540, sensor 550, display unit 560, user input unit 570, interface unit 580, memory 590, processor 511, and power supply 512. Those skilled in the art will appreciate that the terminal configuration shown in fig. 5 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The processor 511 is configured to obtain first information; acquiring a scheduling instruction aiming at the direct communication link sent by the control node according to the first information; transmitting data according to the scheduling instruction;

The terminal of the embodiment of the invention transmits data directly according to the scheduling instruction aiming at the direct communication link sent by the control node, thereby reducing the scheduling time delay and the direct communication link resource overhead.

It should be understood that, in the embodiment of the present invention, the radio frequency unit 510 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, after receiving downlink data from a network side device, the downlink data is processed by the processor 511; in addition, the uplink data is sent to the network side equipment. In general, radio frequency unit 510 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio unit 510 may also communicate with a network and other devices through a wireless communication system.

The terminal provides the user with wireless broadband internet access through the network module 520, such as helping the user send and receive e-mails, browse webpages, access streaming media, and the like.

The audio output unit 530 may convert audio data received by the radio frequency unit 510 or the network module 520 or stored in the memory 590 into an audio signal and output as sound. Also, the audio output unit 530 may also provide audio output related to a specific function performed by the terminal 50 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 530 includes a speaker, a buzzer, a receiver, and the like.

The input unit 540 is used for receiving an audio or video signal. The input Unit 540 may include a Graphics Processing Unit (GPU) 541 and a microphone 542, and the Graphics processor 541 processes image data of a still picture or video obtained by an image capturing device (e.g., a camera) in a video capture mode or an image capture mode. The processed image frames may be displayed on the display unit 560. The image frames processed by the graphic processor 541 may be stored in the memory 590 (or other storage medium) or transmitted via the radio frequency unit 510 or the network module 520. The microphone 542 may receive sound, and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to a mobile communication network side device via the radio frequency unit 510 in case of the phone call mode.

The terminal 50 also includes at least one sensor 550, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of the display panel 561 according to the brightness of ambient light, and a proximity sensor that turns off the display panel 561 and/or the backlight when the terminal 50 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; the sensor 550 may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be described herein.

The display unit 560 is used to display information input by a user or information provided to the user. The Display unit 560 may include a Display panel 561, and the Display panel 561 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 570 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, the user input unit 570 includes a touch panel 571 and other input devices 572. The touch panel 571, also referred to as a touch screen, can collect touch operations by a user (e.g., operations by a user on the touch panel 571 or near the touch panel 571 using a finger, a stylus, or any suitable object or attachment). The touch panel 571 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 511, and receives and executes commands sent from the processor 511. In addition, the touch panel 571 can be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave. The user input unit 570 may include other input devices 572 in addition to the touch panel 571. In particular, the other input devices 572 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described herein.

Further, the touch panel 571 can be overlaid on the display panel 561, and when the touch panel 571 detects a touch operation on or near the touch panel 571, the touch panel is transmitted to the processor 511 to determine the type of the touch event, and then the processor 511 provides a corresponding visual output on the display panel 561 according to the type of the touch event. Although the touch panel 571 and the display panel 561 are shown in fig. 5 as two independent components to implement the input and output functions of the terminal, in some embodiments, the touch panel 571 and the display panel 561 may be integrated to implement the input and output functions of the terminal, and the implementation is not limited herein.

The interface unit 580 is an interface for connecting an external device to the terminal 50. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 580 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the terminal 50 or may be used to transmit data between the terminal 50 and an external device.

The memory 590 may be used to store software programs as well as various data. The memory 590 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 590 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 511 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 590 and calling data stored in the memory 590, thereby integrally monitoring the terminal. Processor 511 may include one or more processing units; preferably, the processor 511 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 511.

The terminal 50 may further include a power source 512 (e.g., a battery) for supplying power to various components, and preferably, the power source 512 may be logically connected to the processor 511 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.

In addition, the terminal 50 includes some functional modules that are not shown, and will not be described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, including a processor 511, a memory 590, and a computer program stored in the memory 590 and operable on the processor 511, where the computer program, when executed by the processor 511, implements each process of the embodiment of the transmission control method applied to the terminal side, and can achieve the same technical effect, and in order to avoid repetition, the detailed description is omitted here.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the embodiment of the transmission control method applied to the terminal side, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

As shown in fig. 6, an embodiment of the present invention further provides a control node 600, including:

a generating module 601, configured to generate a scheduling instruction for the direct communication link according to the first information;

a first sending module 602, configured to send the scheduling instruction to a terminal;

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

Further, the transmission indication field includes 1 bit, or the transmission indication field includes a bitmap, and each bit in the bitmap is used to indicate a transmission status of a terminal.

Optionally, before the generating module 601 generates the scheduling instruction for the direct communication link according to the first information, the method further includes:

the configuration module is used for configuring the scheduling identifier;

and the second sending module is used for sending the scheduling identifier to the terminal.

Further, the configuration module implements at least one of:

distributing the same scheduling identification for the two unicast terminals;

Optionally, after the first sending module 602 sends the scheduling instruction to the terminal, the method further includes:

the receiving module is used for receiving a data demodulation result fed back by the terminal;

An embodiment of the present invention further provides a control node, including: the data transmission method applied to the control node comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, each process in the data transmission method embodiment applied to the control node is realized, the same technical effect can be achieved, and details are not repeated here to avoid repetition.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process in the data transmission method embodiment applied to the control node, and can achieve the same technical effect, and is not described herein again to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

Fig. 7 is a structural diagram of a control node according to an embodiment of the present invention, which can achieve the details of the data transmission method described above and achieve the same effects. As shown in fig. 7, the control node 700 includes: a processor 701, a transceiver 702, a memory 703 and a bus interface, wherein:

the processor 701 is configured to read the program in the memory 703 and execute the following processes:

sending the scheduling instruction to the terminal via the transceiver 702;

In fig. 7, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 701, and various circuits, represented by memory 703, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 702 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

Optionally, the processor 701 is configured to read the program in the memory 703, and further perform the following processes:

configuring a scheduling identifier;

and sending the scheduling identification to the terminal.

Optionally, the processor 701 is configured to read a program for performing configuration of the scheduling identifier in the memory 703, and execute the following processes:

distributing the same scheduling identification for the two unicast terminals;

receiving a data demodulation result fed back by the terminal;

When the control node is a network side device, the network side device may be a Base Transceiver Station (BTS) in Global System for Mobile communication (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved node b (evolved node b, eNB, or eNodeB) in LTE, or a relay Station, an Access point, or a Base Station in a future 5G network, and the like, which is not limited herein.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.

Claims

1. A data transmission method is applied to a terminal, and is characterized by comprising the following steps:

acquiring first information;

transmitting data according to the scheduling instruction;

wherein the first information comprises: the scheduling identifier is used for indicating the terminal to monitor a scheduling instruction;

the scheduling identifier is further configured to indicate a transmission state of the terminal, and the transmitting of the data includes:

transmitting data according to the transmission state indicated by the scheduling identification;

or

The transmitting of the data comprises:

acquiring a transmission indication domain in the scheduling instruction;

transmitting data according to the transmission state;

wherein the second information is transmission state identification information;

or

The first information further includes: at least one transmission identifier for indicating the terminal to transmit or receive data, wherein the transmitting of data according to the scheduling instruction comprises:

transmitting data according to the transmission state;

wherein, the transmission indication field contains 1 bit, or the transmission indication field contains a bitmap, and each bit in the bitmap is used for indicating the transmission state of a terminal.

2. The data transmission method according to claim 1, wherein the obtaining, according to the first information, a scheduling instruction for the direct communication link sent by the control node includes:

3. The data transmission method according to claim 1, wherein the at least one transmission identifier is obtained by at least one of:

receiving at least one transmission identifier allocated by the control node;

4. The data transmission method according to claim 1, wherein the determining the transmission status of the terminal according to the indication information in the transmission indication field in the scheduling instruction and the at least one transmission identifier comprises one of:

5. The data transmission method according to claim 1, wherein the transmission indication field is used to indicate one of the following information:

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

6. The data transmission method according to claim 1, wherein when the transmission status of the terminal is data transmission, the data transmission comprises:

7. The data transmission method according to claim 1, wherein when the transmission status of the terminal is data reception, the data transmission comprises:

8. The data transmission method of claim 7, further comprising, after the receiving the data over the direct communication link:

and feeding back a data demodulation result to the control node.

9. A data transmission method is applied to a control node, and is characterized by comprising the following steps:

sending the scheduling instruction to a terminal;

the scheduling identification is also used for indicating the transmission state of the terminal; or

The scheduling instruction comprises: a transmission indication field; or

The scheduling instruction comprises: a transmission indication field, the first information further comprising: at least one transmission identifier for indicating the terminal to transmit or receive data;

10. The data transmission method according to claim 9, wherein the transmission indication field is used to indicate one of the following information:

indicating at least one terminal for data transmission;

indicating at least one terminal for data reception;

11. The data transmission method according to claim 9, further comprising, before the generating a scheduling instruction for the direct communication link according to the first information:

configuring a scheduling identifier;

and sending the scheduling identification to the terminal.

12. The data transmission method according to claim 11, wherein the configuring of the scheduling identifier includes at least one of:

distributing the same scheduling identification for the two unicast terminals;

13. The data transmission method according to claim 9, further comprising, after said transmitting the scheduling command to the terminal:

receiving a data demodulation result fed back by the terminal;

14. A terminal, comprising:

the first acquisition module is used for acquiring first information;

the scheduling identifier is further configured to indicate a transmission state of the terminal, and the transmission module is configured to:

or

The transmission module includes:

or

The first information further includes: at least one transmission identifier for indicating the terminal to transmit or receive data, wherein the transmission module comprises:

the second transmission unit is used for transmitting data according to the transmission state;

15. A terminal, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when being executed by the processor, carries out the steps of the data transmission method according to one of claims 1 to 8.

16. A control node, comprising:

The scheduling instruction comprises: a transmission indication field; or

17. A control node, comprising: memory, processor and computer program stored on the memory and executable on the processor, which computer program, when being executed by the processor, carries out the steps of the data transmission method according to any one of claims 9 to 13.

18. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the data transmission method according to one of claims 1 to 8 or the steps of the data transmission method according to one of claims 9 to 13.