WO2020098661A1 - Method for sending and receiving data, and communication apparatus - Google Patents

Abstract

Provided are a method for sending and receiving data, and a communication apparatus. The method is applied to multiple network devices, such as a first network device and a second network device, wherein same collaboratively send data to a terminal device. The method comprises: in a pre-allocation stage, multiple network devices pre-allocating a beam or beam set for a terminal device, that is, pre-allocating spatial domain resources; and in a real scheduling stage, the multiple network devices collaboratively sending, by means of the pre-allocated beam or beam set, data to the terminal device. According to the present application, pre-allocating spatial domain resources in a pre-allocation stage can simplify scheduling complexities; moreover, using slowly-varying features of a spatial domain of a terminal device to make a pre-allocation module of a network device and an independent scheduling module of the network device be relatively independent of each other reduces the transmission delay and the processing delay and improves the transmission performance.

Description

Method and communication device for sending and receiving data

This application requires the priority of the Chinese patent application filed on November 14, 2018 in the Chinese Patent Office with the application number 201811354053.8 and the application name "Method and Communication Device for Sending and Receiving Data", the entire contents of which are incorporated by reference in this document Applying.

Technical field

The present application relates to the field of wireless communication, and more specifically, to a method and a communication device for transmitting and receiving data.

Background technique

Coordinated multiple point (Coordination multiple point, CoMP) transmission is a method for solving inter-cell interference problems and improving the throughput of cell edge users. In downlink coordinated multi-point transmission, multiple network devices, such as multiple cells, jointly send data to terminal devices to convert inter-cell interference into useful signals to improve the edge users.

At present, in downlink coordinated multi-point transmission, the scheduling method of downlink coordinated joint transmission is generally centralized scheduling, that is, there is a centralized node to collect and manage information of multiple cells and perform joint resource allocation. In some scenarios, for example, massive multiple-input multiple-output (Massive MIMO) scenarios, applying centralized scheduling, the computational complexity will be high.

Summary of the invention

The present application provides a method and a communication device for sending and receiving data, which can simplify the scheduling structure and reduce the calculation complexity when multiple users are paired.

In the first aspect, a method for transmitting data is provided. The method may be executed by a network device or a chip configured in the network device.

Specifically, the method includes: a first network device pre-allocates a first beam to a terminal device; the first network device sends collaboration request information to a second network device, and the collaboration request information is used to request the second network device Cooperate with the first network device to send second data to the terminal device; the first network device receives collaboration response information from the second network device, the collaboration response information is feedback for the collaboration request information Information; based on the collaboration response information, the first network device sends first data to the terminal device through the first beam.

Based on the above technical solution, in cooperative joint transmission, for example, when multiple network devices (for example, denoted as first network device and second network device) perform data transmission with one terminal device, the network device (first network device or second network Equipment) scheduling can use the concept of beams, pre-allocation of beams or beam sets for terminal equipment in the pre-allocation phase, that is, pre-allocation of airspace resources, not only can simplify scheduling complexity, but also use the characteristics of terminal equipment airspace slowly changing, network equipment The two modules of pre-allocation and network device independent scheduling are relatively independent, which avoids the situation that the determination of the cooperative relationship between multiple network devices consumes the transmission delay and processing delay of multiple network devices, which in turn causes scheduling errors. In addition, the scheduling architecture of the embodiment of the present application can reuse the current single-cell scheduling process and the single-cell scheduling module. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. The concept of beams used in scheduling can greatly simplify the complexity of scheduling.

In the embodiment of the present application, the first network device and the second network device may be any two or more network devices, for example, any two or more cells. Alternatively, the first network device may be a serving cell, and the second network device may be a coordinated cell. The coordinated serving cell sends data to the terminal device, and the coordinated cell may be any one or more cells. Regardless of whether it is a serving cell or a cooperative cell, beams can be pre-allocated for the terminal device in the pre-allocation phase. The serving cell and the cooperative cell may correspond to different network devices, or may also correspond to the same network device, which is not limited in this embodiment of the present application.

In addition, the data sent by the first network device and the second network device may be the same or different, specifically described in the following embodiments.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the first network device pre-allocates N sets of beam sets for N terminal devices, and the N terminal devices and the N Group beam sets are in one-to-one correspondence. The N terminal devices include the terminal devices, where N is an integer greater than or equal to 1; the first network device pre-allocating the first beam to the terminal devices includes: The first network device pre-allocates a first set of beam sets for the terminal device, the first set of beam sets includes the first beam, and the N sets of beam sets include the first set of beam sets.

Based on the above technical solution, when the network equipment pre-allocates beams to the terminal equipment, it may adopt a beam domain grouping (also called airspace grouping or beam grouping) method, that is, to allocate a beam or a beam set to the terminal equipment, the allocated beam or beam The set is an airspace resource carried when sending data to the terminal device. For example, in a large-scale multi-input and multi-output scenario, the spatial domain resources can be reserved for users in a beam domain grouping manner. The N terminal devices may include a terminal device for cooperative transmission (that is, multiple network devices jointly send data to the terminal device), a terminal device for non-cooperative transmission (that is, the first network device sends data to the terminal device), and The transmitted terminal device (that is, the network device retransmits data to the terminal device), the newly transmitted terminal device (that is, the network device sends data to the terminal device), etc., this embodiment of the present application is not limited.

With reference to the first aspect, in some implementation manners of the first aspect, the first network device pre-allocating the first beam to the terminal device includes: the first network device assigns the terminal device a channel beam according to channel correlation Pre-allocate the first beam.

Based on the above technical solution, when the network device pre-allocates a beam to the terminal device, it can allocate a beam to the terminal device according to the channel correlation.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the first network device sends first downlink control information and second downlink control information to the terminal device, and the first A downlink control information schedules the first data, the second control information schedules the second data, and the first data corresponds to a first hybrid automatic repeat request process number, and the second data is The second hybrid automatic repeat request process number corresponds.

Based on the above technical solution, in cooperative joint transmission, the serving cell (for example, denoted as the first network device) may send multiple downlink control information (downlink control information, DCI) through multiple physical downlink control channels (physical downlink control channel, PDCCH) ), The multiple DCIs use different hybrid automatic retransmission request process numbers to respectively indicate transmission information on multiple network devices. In this way, the hybrid automatic retransmission request process resource can be shared when it is transmitted on multiple network devices (such as the serving cell and the cooperative cell), while ensuring the combined gain of the hybrid automatic retransmission request of the terminal device, and saving hybrid automatic retransmission Request process resources. In addition, multiple DCIs use different hybrid automatic retransmission request process numbers. Multiple DCIs schedule multiple different hybrid automatic retransmission request process number transmission block buffers (TB buffers) to make the terminal device on multiple networks. The frequency domain resources on the device may not be aligned, which is more conducive to independent scheduling of data of the terminal device on multiple network devices.

With reference to the first aspect, in some implementations of the first aspect, the method further includes: the first network device receives information for the second data from the second network device; the second The network device updates the scheduling information corresponding to the process number of the second hybrid automatic repeat request according to the information for the second data.

Based on the above technical solution, in the coordinated joint transmission, after the serving cell and the coordinated cell are independently scheduled separately, the coordinated cell transmits the transmission information on the local branch back to the serving cell, and the service cell supplements the hybrid automatic on the cooperative branch timely after receiving it. Retransmit the scheduling information under the request process ID.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the first network device receives feedback information regarding the first data and the second data sent by the terminal device .

Based on the above technical solution, the terminal device can feed back positive (acknowledgement, ACK) or negative (negative) information about the first data and the second data through the physical uplink control channel (PUCCH) of the serving cell. . Alternatively, the terminal device may also feed back ACK or NACK information through the respective PUCCH on the serving cell and the cooperative cell.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: when the feedback information for the first data is negative NACK information, the first network device restarts to the terminal device Sending the first data; and / or, when the feedback information for the second data is NACK information, the first network device resends the second data to the terminal device.

Based on the above technical solution, the data transmitted by the serving cell or the coordinated cell is retransmitted on the serving cell.

In a second aspect, a method for transmitting data is provided. The method may be executed by a network device or a chip configured in the network device.

Specifically, the method includes: the second network device receives collaboration request information from the first network device, where the collaboration request information is used to request the second network device to cooperate with the first network device to send second data to the terminal device The second network device pre-allocates a second beam to the terminal device according to the collaboration request information; the second network device sends collaboration response information to the first network device, the collaboration response information is directed Feedback information of the collaboration request information; based on the collaboration response information, the second network device sends the second data to the terminal device through the second beam.

Based on the above technical solution, in cooperative joint transmission, for example, when multiple network devices (for example, denoted as a first network device and a second network device) perform data transmission with a terminal device, the network device (the first network device or the second network) Equipment) scheduling can use the concept of beams, pre-allocation of beams or beam sets for terminal equipment in the pre-allocation phase, that is, pre-allocation of airspace resources, not only can simplify scheduling complexity, but also use the characteristics of terminal equipment airspace slowly changing, network equipment The two modules of pre-allocation and network device independent scheduling are relatively independent, which avoids the situation that the determination of the cooperative relationship between multiple network devices consumes the transmission delay and processing delay of multiple network devices, which in turn causes scheduling errors. In addition, the scheduling architecture of the embodiment of the present application can reuse the current single-cell scheduling process and the single-cell scheduling module. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. Using the concept of beams during scheduling can greatly simplify the scheduling complexity.

In the embodiment of the present application, the first network device and the second network device may be any two or more network devices, for example, any two or more cells. Alternatively, the first network device may be a serving cell, and the second network device may be a coordinated cell. The coordinated serving cell sends data to the terminal device, and the coordinated cell may be any one or more cells. Regardless of whether it is a serving cell or a cooperative cell, beams can be pre-allocated for the terminal device in the pre-allocation phase. The serving cell and the cooperative cell may correspond to different network devices, or may also correspond to the same network device, which is not limited in this embodiment of the present application.

With reference to the second aspect, in some implementation manners of the second aspect, the method further includes: the second network device pre-allocating N sets of beam sets for N terminal devices, and the N terminal devices and the N Group beam sets are in one-to-one correspondence, and the N terminal devices include the terminal devices, where N is an integer greater than or equal to 1; and the second network device pre-allocating a second beam to the terminal device includes: The second network device pre-allocates a second set of beam sets for the terminal device, the second set of beam sets includes the second beam, and the N sets of beam sets include the second set of beam sets.

With reference to the second aspect, in some implementation manners of the second aspect, the second network device pre-allocating a second beam to the terminal device includes: the second network device assigns the terminal device according to channel correlation Pre-allocate the second beam.

In a third aspect, a method for receiving data is provided. The method may be executed by a terminal device or a chip configured in the terminal device.

Specifically, the method includes: the terminal device receives first data from a first network device and second data from a second network device, the first data is carried in a first beam, and the second data is carried in a second Beam, the first beam is a beam pre-allocated by the first network device to the terminal device, and the second beam is a beam pre-allocated by the second network device to the terminal device; the terminal device Sending feedback information for the first data and the second data to the first network device.

Based on the above technical solution, in cooperative joint transmission, for example, when multiple network devices perform data transmission with one terminal device, the network device can use the concept of beams when scheduling, and pre-allocate beams or beam sets for terminal devices in the pre-allocation phase, that is, Pre-allocating airspace resources not only simplifies scheduling complexity, but also utilizes the slow-changing characteristics of terminal equipment airspace to pre-allocate network equipment and network equipment independent scheduling. The two modules are relatively independent of each other, avoiding the cooperative relationship between multiple network equipment. It is determined that the transmission delay and processing delay of multiple network devices are consumed, which in turn causes scheduling errors. In addition, the scheduling architecture of the embodiment of the present application can reuse the current single-cell scheduling process and the single-cell scheduling module. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. Using the concept of beams during scheduling can greatly simplify the scheduling complexity.

In the embodiment of the present application, the first network device and the second network device may be any two or more network devices, for example, any two or more cells. Alternatively, the first network device may be a serving cell, and the second network device may be a coordinated cell. The coordinated serving cell sends data to the terminal device, and the coordinated cell may be any one or more cells. Regardless of whether it is a serving cell or a cooperative cell, beams can be pre-allocated for the terminal device in the pre-allocation phase. The serving cell and the cooperative cell may correspond to different network devices, or may also correspond to the same network device, which is not limited in this embodiment of the present application.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the terminal device receives first downlink control information and second downlink control information from the first network device, the The first downlink control information schedules the first data, the second control information schedules the second data, and,

The first data corresponds to a first hybrid automatic repeat request process number, and the second data corresponds to a second hybrid automatic repeat request process number.

According to a fourth aspect, a communication device is provided, including various modules or units for performing the method in any possible implementation manner of the first aspect or the second aspect.

In a fifth aspect, a communication device is provided, including a processor. The processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in any possible implementation manner of the first aspect or the second aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

In one implementation, the communication device is a network device. When the communication device is a network device, the communication interface may be a transceiver or an input / output interface.

In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface may be an input / output interface.

Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

In a sixth aspect, a communication device is provided, including various modules or units for performing the method in any possible implementation manner of the third aspect.

In a seventh aspect, a communication device is provided, including a processor. The processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in any possible implementation manner of the third aspect. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

In one implementation, the communication device is a terminal device. When the communication device is a terminal device, the communication interface may be a transceiver or an input / output interface.

In another implementation, the communication device is a chip configured in the terminal device. When the communication device is a chip configured in a terminal device, the communication interface may be an input / output interface.

Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

In an eighth aspect, a processor is provided, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive a signal through the input circuit and transmit a signal through the output circuit so that the processor performs the first aspect, the second aspect or the third aspect and the first aspect, the second aspect or the first aspect Any one of the three possible implementation methods.

In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to a receiver, the signal output by the output circuit may be, for example but not limited to, output to and transmitted by the transmitter, and the input circuit and output The circuit may be the same circuit, which is used as an input circuit and an output circuit at different times, respectively. The embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.

In a ninth aspect, a processing device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through the receiver and transmit signals through the transmitter to perform the first aspect, the second aspect or the third aspect and the first aspect, the second aspect or the third aspect Method in any possible implementation manner.

Optionally, there are one or more processors and one or more memories.

Alternatively, the memory may be integrated with the processor, or the memory and the processor are provided separately.

In the specific implementation process, the memory may be a non-transitory (non-transitory) memory, such as a read-only memory (read only memory, ROM), which may be integrated with the processor on the same chip, or may be set in different On the chip, the embodiments of the present application do not limit the type of memory and the manner of setting the memory and the processor.

It should be understood that the related data interaction process, for example, sending instruction information may be a process of outputting instruction information from the processor, and receiving capability information may be a process of receiving input capability information by the processor. Specifically, the processed output data may be output to the transmitter, and the input data received by the processor may come from the receiver. Among them, the transmitter and the receiver may be collectively referred to as a transceiver.

The processing device in the ninth aspect may be a chip, and the processor may be implemented by hardware or software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc .; when implemented by software In implementation, the processor may be a general-purpose processor, implemented by reading software codes stored in a memory, the memory may be integrated in the processor, or may be located outside the processor and exist independently.

According to a tenth aspect, a computer program product is provided. The computer program product includes: a computer program (also referred to as code or instructions), which, when the computer program is executed, causes a computer to perform the first aspect, the first The method in any possible implementation manner of the second aspect or the third aspect and the first aspect, the second aspect, or the third aspect.

In an eleventh aspect, a computer-readable medium is provided, the computer-readable medium storing a computer program (also may be referred to as code or instructions), which when executed on a computer, causes the computer to perform the first aspect, The method in any possible implementation manner of the second aspect or the third aspect and the first aspect, the second aspect, or the third aspect.

In a twelfth aspect, a communication system is provided, including the foregoing first network device, second network device, and terminal device.

BRIEF DESCRIPTION

FIG. 1 is a schematic diagram of a communication system suitable for the method provided by the embodiments of the present application;

2 is another schematic diagram of a communication system applicable to the method provided by the embodiment of the present application;

FIG. 3 shows a schematic diagram of centralized scheduling;

FIG. 4 shows a schematic flowchart of centralized scheduling;

5 is a schematic flowchart of a method for sending and receiving data according to an embodiment of the present application;

6 (1) and (2) show schematic diagrams of DMP and SMP transmission modes applicable to embodiments of the present application;

FIG. 7 shows a schematic flow chart when scheme 1 is adopted when JT users are actually scheduled according to an embodiment of the present application;

FIG. 8 shows a schematic scheduling sequence diagram when scheme 2 is adopted when JT users are actually scheduled according to an embodiment of the present application;

FIG. 9 shows a schematic flow chart when scheme 2 is adopted when JT users are actually scheduled according to an embodiment of the present application;

10 is a schematic flowchart of a method for sending and receiving data according to another embodiment of the present application;

FIG. 11 shows a schematic diagram of a serving cell and a cooperating cell applicable to embodiments of the present application to reserve airspace resources for users;

12 shows a schematic diagram when a serving cell and a cooperating cell that are applicable to the embodiments of the present application jointly send data to a JT user;

13 is a schematic diagram of a method for sending and receiving data according to yet another embodiment of the present application;

14 shows a schematic diagram of a HARQ process scheduling scheme applicable to the SMP transmission mode of an embodiment of the present application;

15 shows a schematic diagram of RTT for codeword transmission on the serving cell and the cooperative cell in the SMP transmission mode applicable to the embodiment of the present application;

16 is a schematic block diagram of a communication device provided by an embodiment of the present application;

17 is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

18 is a schematic structural diagram of a network device provided by an embodiment of the present application.

detailed description

The technical solutions in this application will be described below with reference to the drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: future 5th generation (5G) system or new wireless (new radio (NR), global mobile communication (global system for mobile communications, GSM ) System, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (general packet radio service (GPRS), long-term evolution (long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile communication system (universal mobile telecommunication system, UMTS), global interconnected microwave access Into (worldwide interoperability for microwave access, WiMAX) communication systems, etc.

In order to facilitate understanding of the embodiments of the present application, first, the communication system applicable to the embodiments of the present application will be described in detail with reference to FIGS. 1 and 2.

FIG. 1 shows a schematic diagram of a communication system 100 suitable for a method for sending and receiving data according to an embodiment of the present application. As shown, the communication system 100 may include at least one network device, such as the network device 110 shown in FIG. 1; the communication system 100 may also include at least one terminal device, such as the terminal device 120 shown in FIG. The network device 110 and the terminal device 120 can communicate through a wireless link.

FIG. 2 shows another schematic diagram of a communication system 200 suitable for the method for sending and receiving data according to an embodiment of the present application. As shown, the communication system 200 may include at least two network devices, such as the network devices 210 and 220 shown in FIG. 2; the communication system 200 may also include at least one terminal device, such as the terminal shown in FIG. Device 230. The terminal device 230 may establish a wireless link with the network device 110 and the network device 120 through dual connectivity (DC) technology or multi-connection technology. The network device 110 may be a primary base station, and the network device 120 may be a secondary base station, for example. In this case, the network device 210 is a network device when the terminal device 230 initially accesses, and is responsible for radio resource control (RRC) communication with the terminal device 230. The network device 220 may be added during RRC reconfiguration To provide additional wireless resources.

Of course, the network device 120 may also be the primary base station, and the network device 110 may also be the secondary base station, which is not limited in this application. In addition, the figure is only for ease of understanding, and shows the situation of wireless connection between two network devices and terminal devices, but this should not constitute any limitation to the scenario to which this application applies. The terminal device can also establish a wireless link with more network devices.

Each communication device, such as the network device 110 or the terminal device 120 in FIG. 1, or the network device 210, the network device 220, or the terminal device 230 in FIG. 2, may be configured with multiple antennas. The plurality of antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals. In addition, each communication device additionally includes a transmitter chain and a receiver chain. Those of ordinary skill in the art can understand that they can include multiple components related to signal transmission and reception (such as processors, modulators, and multiplexers) , Demodulator, demultiplexer or antenna, etc.). Therefore, network equipment and terminal equipment can communicate through multi-antenna technology.

It should be understood that the network device in the wireless communication system may be any device having a wireless transceiver function. The network equipment includes but is not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), node B (Node B, NB), base station controller (base station controller, BSC) ), Base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless fidelity (Wireless Fidelity, WIFI) system Access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or sending and receiving point (transmission and reception point, TRP), etc., can also be 5G, such as, NR, gNB in the system, or transmission point (TRP or TP), one or a group (including multiple antenna panels) of the base station in the 5G system, or it can also be a network node that constitutes a gNB or transmission point , Such as baseband unit (BBU), or distributed unit (DU), etc.

In some deployments, gNB may include a centralized unit (CU) and DU. The gNB may also include a radio unit (RU). CU implements some functions of gNB, DU implements some functions of gNB, for example, CU implements radio resource control (RRC), packet data convergence layer protocol (packet, data, protocol, PDCP) layer functions, DU implements wireless chain Road control (radio link control, RLC), media access control (media access control, MAC) and physical (physical, PHY) layer functions. Since the information of the RRC layer will eventually become the information of the PHY layer or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , Or, sent by DU + CU. It can be understood that the network device may be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be divided into network devices in the radio access network (RAN), and can also be divided into network devices in the core network (CN), which is not limited in this application.

It should also be understood that the terminal equipment in the wireless communication system may also be called user equipment (user equipment (UE) (or simply user), access terminal, user unit, user station, mobile station, mobile station, remote station, Remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal devices in the embodiments of the present application may be mobile phones, tablet computers, computers with wireless transceiver functions, virtual reality (virtual reality, VR) terminal devices, and augmented reality (augmented reality, AR) terminals. Wireless terminals in equipment, industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical (remote medical), wireless terminals in smart grid (smart grid), transportation safety ( Wireless terminals in transportation, wireless terminals in smart cities, wireless terminals in smart homes, etc. The embodiments of the present application do not limit the application scenarios.

In order to facilitate understanding of the embodiments of the present application, the following first briefly introduces several terms involved in the present application.

1. Beam

The embodiment of the beam in the NR protocol can be a spatial filter, or a spatial filter or spatial parameters. The beam used to transmit the signal may be called a transmission beam (transmission beam, Tx beam), and may be called a spatial transmission filter (spatial domain domain transmit filter) or a spatial transmission parameter (spatial domain domain transmission parameter). The transmit beam may refer to the distribution of signal strength formed in different directions in space after the signal is transmitted through the antenna.

It should be understood that the embodiment of the NR protocol listed above for the beam is only an example, and should not constitute any limitation to this application. This application does not exclude the possibility of defining other terms to mean the same or similar meanings in future agreements.

In addition, the beam may be a wide beam, or a narrow beam, or other types of beams. The technique of forming beams may be beamforming or other techniques. The beamforming technology may specifically be a digital beamforming technology, an analog beamforming technology, or a hybrid digital / analog beamforming technology. Different beams can be considered as different resources. The same information or different information can be sent through different beams.

Optionally, multiple beams with the same or similar communication characteristics are regarded as one beam. One or more antenna ports can be included in a beam to transmit data channels, control channels, and sounding signals. One or more antenna ports forming a beam can also be regarded as a set of antenna ports.

2. Reference signals and reference signal resources

The reference signal can be used for channel measurement or channel estimation. The reference signal resource can be used to configure the transmission properties of the reference signal, for example, the location of the time-frequency resource, the port mapping relationship, the power factor, and the scrambling code. For details, reference may be made to the prior art. The transmitting end device may transmit the reference signal based on the reference signal resource, and the receiving end device may receive the reference signal based on the reference signal resource.

The channel measurement involved in this application also includes beam measurement, that is, beam quality information is obtained by measuring a reference signal, and parameters used to measure the beam quality include RSRP, but are not limited thereto. For example, the beam quality can also be based on the reference signal reception quality (RSRQ), signal-noise ratio (SNR), signal-to-interference-noise ratio (signal to interference plus noise), SINR, or simply signal Noise ratio) and other parameters. In the embodiments of the present application, for convenience of explanation, the channel measurement involved may be regarded as beam measurement without special explanation.

The reference signal may include, for example, a channel state information reference signal (channel-state information reference (CSI-RS), a synchronization signal block (synchronization signal block (SSB)), and a sounding reference signal (sounding reference signal (SRS)). Correspondingly, the reference signal resources may include CSI-RS resources (CSI-RS resources), SSB resources, and SRS resources (SRS resources).

It should be noted that the above SSB may also be called a synchronization signal / physical broadcast channel block (SS / PBCH block), and the corresponding SSB resource may also be called a synchronization signal / physical broadcast channel block resource. (SS / PBCH block resource), which can be referred to as SSB resource.

In order to distinguish different reference signal resources, each reference signal resource may correspond to a reference signal resource identifier, for example, CSI-RS resource identifier (CSI-RS resource indicator, CRI), SSB resource identifier (SSB resource indicator, SSBRI) , SRS resource index (SRS resource index, SRI).

Among them, the SSB resource identifier may also be called an SSB identifier (SSB index).

In the following embodiments, the reference signals listed above and corresponding reference signal resources are used as an example for illustration. It should be understood that the reference signals and corresponding reference signal resources listed above are only exemplary descriptions, and should not constitute any limitation to this application. This application does not exclude the definition of other reference signals in future protocols to achieve the same or similar functions may.

3. HARQ process number

HARQ uses a stop-and-wait protocol to send data. Taking the upstream transmission as an example, after sending a transport block (TB), the terminal device stops and waits for confirmation information. The network device may use 1 bit of information to confirm the acknowledgement (acknowledgement, ACK) or negative (negative acknowledgement, NACK) of the transport block. However, after each transmission, the terminal equipment stops to wait for confirmation, which will result in a very low throughput. Therefore, the terminal device can use multiple parallel HARQ processes. When one HARQ process is waiting for confirmation information, the terminal device can use another HARQ process to continue sending data.

The HARQ process number is also called HARQ process identifier (ID). A HARQ process number can be used to uniquely specify a HARQ process. After the channel coding is performed on the transmission block, the terminal device may register the data obtained by the channel coding in a buffer and wait for transmission. The transmission blocks in the cache and the HARQ process may have a one-to-one correspondence, and each transmission block may correspond to one HARQ process. The correspondence between the transport block and the HARQ process can be reflected by the correspondence between the transport block and the HARQ process number. Therefore, the terminal device may determine the correspondence between the transport block and the HARQ process number in advance.

Since the network device carries the HARQ process number in the DCI, the HARQ process number has a corresponding relationship with the time-frequency resource indicated in the DCI. That is, when a transport block is transmitted based on the time-frequency resource indicated in the DCI, the HARQ process number corresponding to the transport block is the HARQ process number carried in the DCI. Therefore, both the network device and the terminal device can determine the correspondence between the time-frequency resource and the HARQ process number.

When the data received by the network device on a certain time-frequency resource fails to be successfully decoded, or the data is not received on a certain time-frequency resource, the terminal device may be notified of the HARQ process number corresponding to the time-frequency resource through DCI. The terminal device may determine the transport block that needs to be retransmitted according to the correspondence between the HARQ process number and the transport block.

4. Transmission block (TB)

The transport block may be a data block from a higher layer. A transmission block may include, for example, a data block of a media access control (MAC) protocol data unit (protocol, data, unit, PDU). The data block may be transmitted in a time unit, or may be retransmitted by HARQ. unit. In the existing LTE and NR, for each terminal device, a maximum of two transport blocks can be sent per time unit. As an example and not a limitation, the time unit is a transmission time interval (transmission time interval, TTI).

5. Cell: A cell is described by a high layer from the perspective of resource management or mobility management or service unit. The coverage of each network device can be divided into one or more serving cells, and the serving cell can be regarded as consisting of a certain frequency domain resource. In the embodiment of the present application, the cell may be replaced with a serving cell or a component carrier (CC, or component carrier, component carrier, carrier, etc.).

It should be noted that the cell may be an area within the coverage of the wireless network of the network device. In the embodiments of the present application, different cells may correspond to different network devices. For example, the network device in cell # 1 and the network device in cell # 2 may be different network devices, such as base stations. In other words, cell # 1 and cell # 2 can be managed by different base stations. In this case, it can be called that cell # 1 and cell # 2 are co-sited, or that they are co-sited. The network device in cell # 1 and the network device in cell # 2 may also be different RF processing units of the same base station, for example, a radio remote unit (RRU), that is, cell # 1 and cell # 2 can be managed by the same base station, has the same baseband processing unit and intermediate frequency processing unit, but has different radio frequency processing units. This application does not specifically limit this.

In the embodiment of the present application, a serving cell and a cooperative cell are involved, and the serving cell and the cooperative cell may correspond to different network devices, or may also correspond to the same network device, which is not limited in the embodiment of the present application. The serving cell and the cooperative cell may be any two or more cells, and the two or more cells may jointly send data to the terminal device.

6. Centralized scheduling and distributed scheduling

Centralized scheduling: The user's resources are jointly scheduled among multiple cells. FIG. 3 shows a schematic diagram of centralized scheduling. Multiple cells form a cluster, for example, a cluster can be formed according to preset rules, and centralized scheduling is performed within the cluster. As shown in FIG. 3, physical cell IDs (PCIs) 0, PCI3, PCI6, and PCI9 are located in PCI modulo 3 alignment block 1, and PCI1, PCI4, PCI7, and PCI10 are located in PCI modulo 3 alignment block 2. Under centralized scheduling, there is a centralized node to collect and manage information of multiple cells and do joint resource allocation. Therefore, if centralized scheduling is applied in a massive multiple-input multiple-output (Massive-MIMO) scenario, the computational complexity will be high.

In addition, in general, the multi-cell multi-user multiple-input multiple-output (MIMO) centralized scheduling architecture and process are similar to single-cell multi-user MIMO, as shown in FIG. 4. Data service scheduling begins with retransmission scheduling first, followed by new transmission first layer scheduling. Priority scheduling for retransmission users, in other words, retransmission users preferentially allocate resource block (RB) resources. The retransmission scheduling uses non-adaptive retransmission, that is, the frequency domain and RRU resources allocated by the first transmission and the modulation and coding scheme (MCS) of the first transmission are used. Secondly, the first layer of new transmission scheduling. The first layer of new transmission scheduling takes resource block group (RBG) as the granularity, and sequentially schedules the users with the highest proportional fair (PF) priority on each RBG. Multi-user pairing is also based on the RBG granularity, and the criterion is to cyclically select on each RBG the paired user with the highest PF and priority gain after pairing with the scheduled user until no user meeting the conditions is found.

When the above-mentioned centralized scheduling is applied in a large-scale multi-input multi-output scenario, multi-user pairing gain calculation and weight calculation bring greater calculation complexity. Centralized scheduling cannot completely eliminate interference between centralized scheduling units. In addition, centralized scheduling is a joint scheduling of multiple cells, which is an alternative relationship with single-cell scheduling, and the single-cell scheduling module cannot be reused.

Distributed Scheduling: First, pre-scheduling cooperative users by scheduling information back and forth between the serving cell and the cooperating cell, and preserving the resources of the cooperating user at the actual scheduling time; then, the serving cell and the cooperating cell do real scheduling for the cooperating user. Under distributed scheduling, cells can only exchange information with each other, and each cell independently allocates resources as a single cell. In the existing distributed scheduling, the actual scheduling of each transmission time interval (transmission time interval, TTI) generally requires pre-scheduling information of a certain length of time (such as X milliseconds (ms), where X> 0).

The above-mentioned distributed scheduling requires information exchange between cells, and the determination of the cooperative relationship between the serving cell and the cooperating cell consumes the transmission delay and processing delay between the cells, which will cause scheduling errors and the consumption of more HARQ process resources. .

In view of this, this application provides a method that can be used in a centralized radio access network (centralized radio access network (CRAN) and a network protocol-based radio access network (internet protocol radio access network, IP RAN), different collaboration In the transmission mode scenario, a unified distributed scheduling architecture and corresponding scheduling scheme are used to improve the edge user perception rate.

The embodiments of the present application will be described in detail below with reference to the drawings.

It should be understood that in the embodiments shown below, the first, second, third, fourth, and various numeric numbers are only for the convenience of description, and are not intended to limit the scope of the embodiments of the present application. For example, distinguish between different transport blocks.

It should also be understood that in the embodiments of the present application, "new user transmission" and "new user transmission" can sometimes be used together. It should be noted that when the difference is not emphasized, the meaning to be expressed is the same, both Used to indicate that multiple network devices jointly send data to the user. Similarly, "user retransmission" and "retransmission user" can sometimes be mixed. It should be pointed out that when the difference is not emphasized, the meaning to be expressed is the same, which is used to indicate the combination of multiple network devices Retransmit data to the user.

It should also be understood that, in the embodiments of the present application, a time slot (slot) is used as an example of a time domain unit, and the method provided by the embodiments of the present application is described in detail, but this should not constitute any limitation to the present application. It should be understood that the time slot is only one possible form of the time domain unit, and the time domain unit (also called time unit) may also be a symbol, or a mini-slot, or a subframe (subframe), etc., this application does not limit.

It should also be understood that, in the embodiments of the present application, RB is used as an example of the frequency domain unit, and the method provided by the embodiments of the application is described in detail, but this should not constitute any limitation to the present application. It should be understood that RB is only one possible form of frequency domain unit, and the frequency domain unit may also be a physical resource block (PRB) or an RBG, or a predefined subband (subband), etc. This application does not limit this.

It should also be understood that, in the embodiments shown below, "pre-acquisition" may include signaling instructions or pre-defined by the network device, for example, protocol definition. Among them, "pre-defined" can be achieved by pre-storing corresponding codes, tables or other methods that can be used to indicate relevant information in the device (for example, including terminal devices and network devices), and this application does not do for its specific implementation limited.

It should also be understood that in the embodiments shown below, "saving" may refer to saving in one or more memories. The one or more memories may be provided separately or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partly set separately and partly integrated in a decoder, processor, or communication device. The type of memory may be any form of storage medium, which is not limited in this application.

It should also be understood that in the embodiments shown below, “protocol” may refer to a standard protocol in the communication field, and may include, for example, the LTE protocol, NR protocol, and related protocols applied in future communication systems. Be limited.

It should also be understood that in the embodiments shown below, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the relationship of the related objects, indicating that there can be three relationships, for example, A and / or B, which can mean: A exists alone, A and B exist at the same time, B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the related object is a "or" relationship. "At least one of the following" or a similar expression refers to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one (a) of a, b, and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

The technical solution of the present application may be applied to a wireless communication system, for example, the communication system 100 shown in FIG. 1 or the communication system 200 shown in FIG. 2. There may be a wireless communication connection relationship between two communication devices in a wireless communication system. One of the two communication devices may correspond to, for example, the network device 110 shown in FIG. 1, for example, it may be the network device 110 or a chip configured in the network device 110, and the other of the two communication devices may correspond to, for example. The terminal device 120 in FIG. 1 may be, for example, the terminal device 120 or a chip configured in the terminal device 120. One of the two communication devices may, for example, correspond to the network device 210 shown in FIG. 2, for example, it may be the network device 210 or a chip configured in the network device 210, and the other of the two communication devices may, for example, It may correspond to the terminal device 230 shown in FIG. 2, such as the terminal device 230 or a chip configured in the terminal device 230. One of the two communication devices may correspond to the network device 220 shown in FIG. 2, for example, it may be the network device 220 or a chip configured in the network device 220, and the other of the two communication devices may be another example. It may correspond to the terminal device 230 shown in FIG. 2, such as the terminal device 230 or a chip configured in the terminal device 230.

In the following, without loss of generality, first, the transmission process between a terminal device (referred to as a user in the following embodiments) and a network device is used as an example to describe in detail embodiments of the present application. It can be understood that any terminal device in the wireless communication system or a chip configured in the terminal device can receive data based on the same method, and any network device in the wireless communication system or a chip configured in the network device can Send data based on the same method. This application does not limit this.

FIG. 5 is a schematic flowchart of a method 300 for sending data shown from the perspective of device interaction. As shown in FIG. 5, in the method 300 shown in FIG. 5, from the start of user pre-scheduling to the end of user pre-scheduling, steps 310 to 340 may be included. The steps of the method 300 will be described in detail below with reference to FIG. 5.

For ease of understanding, the following uses an example of pre-scheduling for joint transmission (JT) users as an example. Assuming that multiple cells jointly send data to the terminal device or joint scheduling, the terminal device is referred to as a JT user or JT terminal device for distinction. It should be understood that the JT user or JT terminal device in the embodiment of the present application is just a name, and does not limit the protection scope of the embodiment of the present application.

In step 320, the serving cell: JT user pre-scheduling, multi-user beam domain grouping.

The serving cell performs JT user pre-scheduling. For example, the serving cell arranges JT users and ordinary users in the cell according to the initial transmission scheduling priority to form a multi-user beam domain grouping, and initiates to the cooperating cell for the JT users with successful multi-user beam domain grouping Collaboration request.

The JT user may be a JT user who meets the pre-scheduling prerequisites. Optionally, before step 320, the method 300 includes step 310. In step 310, the pre-scheduling premise judgment of the serving cell: JT user.

The service cell makes JT user pre-scheduling premise judgment to determine which JT user connections to participate in JT user pre-determination based on conditions such as the load of the cell, the number of JT users supported by the cell, the type of data transmitted by the JT user, and the amount of data to be transmitted by the JT user Scheduling. In step 320, the pre-scheduled JT user may be a JT user who satisfies the pre-scheduling prerequisite after the judgment in step 310.

Among them, in step 320, the process of multi-user beam domain grouping may be as follows:

1. After the actual scheduling of the current time slot service cell is completed, update the radio link control layer (RLC) buffer area (Buffer) of all users and the initial transmission scheduling priority.

2. Establish a pre-scheduled user queue, and arrange the priority according to the scheduling priority of the initial transmission.

3. Multi-user beam domain grouping for users in the pre-scheduled user queue in turn.

In the embodiment of the present application, the network device uses the concept of beams for scheduling, and pre-allocates beams for users during the pre-allocation phase, that is, pre-allocates airspace resources, which not only simplifies scheduling complexity, but also uses the characteristics of slowly changing user airspace, such as users The location of the cell is relatively fixed, and the two modules of cell pre-allocation and cell independent scheduling are relatively independent, avoiding the need to consume the transmission delay and processing delay between the cells due to the determination of the cooperative relationship between the serving cell and the cooperative cell. The case of scheduling errors. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. Using the concept of beams during scheduling can greatly simplify the scheduling complexity.

In the pre-allocation phase, ways to reserve airspace resources for users include at least the following two ways.

Method 1, the grouping method of the beam domain.

Beam domain grouping, also known as airspace grouping or beam grouping, is used to indicate the allocation of beams or beamsets to users, that is, to reserve airspace resources, and the allocated beams or beamsets are carried when sending data to the user Airspace resources. For example, in a large-scale multi-input and multi-output scenario, the spatial domain resources can be reserved for users in a beam domain grouping manner.

Specifically, the pre-scheduled user queue may be traversed according to the scheduling priority of the initial transmission, and the users in the user queue may be grouped in the beam domain in turn. Traverse the existing beam sets of each group to determine whether they overlap with the optimal beam set of the current multi-user traversal to obtain the number of overlapping groups. Overlapping grouping means that the same beam set is allocated to multiple users. Suppose that the serving cell allocates beam set A to user A, and includes the following two cases according to the number of overlapping groups.

Case 1: The number of overlapping groups is 0.

If the number of overlapping groups is 0, and it is assumed that the total number of beams of all groups after the new group is less than or equal to the maximum number of matching layers, a new group is created for this user A, that is, beam set A is assigned to user A, and beam set A User A's optimal beam set. The maximum number of pairing layers may be pre-defined, such as pre-defined protocol or pre-set by the network device.

Case 2: The number of overlapping groups is greater than 0.

If the number of overlapping groups is greater than 0, then user A is a conflicting user, the grouping fails, and the next user is traversed.

In the beam-domain grouping process for multiple users in sequence, the JT users with successful multi-user grouping are selected into the JT user pre-scheduling application queue. If the currently selected JT user pre-scheduling application user exceeds the preset threshold, for example, the preset threshold is recorded as JtUeRequest_Thed, or the number of applied collaborative cells exceeds the preset threshold, for example, the preset threshold The limit is recorded as JtCorcellRequest_Thed, then the dynamic grouping for JT users ends, and the grouping for ordinary multi-users continues. Among them, JtUeRequest_Thed and JtCorcellRequest_Thed may be predefined, for example, the protocol is predefined or the network device presets.

In multi-user beam domain grouping, for JT users, the reference beam set when participating in dynamic grouping is the number of data streams (SU) Rank (SU) Rank the strongest RSRP static beam transmitted by the user single user (SU) . For example, under SU transmission, measure the RSRP intensity under each beam, and select the first N beams according to the measured RSRP size, where N = rank. For ordinary users, the reference beam set participating in the dynamic grouping is the number of data streams (MU Rank) transmitted by the multi-user (MU) of the user, and the static beam with the strongest RSRP. Among them, MU Rank indicates that SU participates in multi-user pairing, that is, multiple users send together on the same time-frequency resource. Generally, the Rank value of MU Rank is smaller than the Rank value of SU Rank.

Method 2, according to channel correlation between users.

For example, in a non-large-scale multi-input multi-output scenario, airspace resources can be reserved for users based on channel correlation between users. For example, when the channel is in an ideal state or the correlation between channels is small, the transmitter uses a spatial multiplexing transmission scheme, such as dense urban areas, indoor coverage, etc .; when the correlation between channels is large, the space-time coding transmission scheme is used, such as Scenes in suburbs and rural areas.

The channel correlation here may refer to the spatial correlation between users. According to the correlation between users, it may also be understood to be based on the spatial correlation between users. The change in different transmitting antennas or receiving antennas is called spatial correlation. For example, for two users, denoted as user 1 and user 2, the channel from user 1 to the base station is H1, and the channel from user 2 to the base station is H2. The spatial correlation of H1 and H2 refers to the size of the spatial isolation of user 1 and user 2, for example, if user 1 and user 2 are close together, the spatial correlation is relatively high, for example, user 1 and user 2 can be Divided into a group; if user 1 and user 2 are far away, the airspace correlation is relatively low, for example, user 1 and user 2 can be divided into different groups at this time.

The foregoing describes that the serving cell pre-allocates airspace resources for users in manner 1 and manner 2. The embodiments of the present application are not limited thereto, and any method that can pre-allocate airspace resources for users falls within the protection scope of the present application.

4. The serving cell initiates a collaboration request to the collaborative cell.

In step 340, coordinated cell: JT user pre-scheduling, multi-user beam domain grouping.

The coordinated cell performs JT user pre-scheduling. For example, the coordinated cell arranges the JT users from other cells requesting cooperation and the common users in the cell according to the priority of the initial transmission scheduling to group the multi-user beam domain and group the multi-user beam domain. Successful JT users feed back cooperative responses to other serving cells.

The JT user may be a JT user who meets the pre-scheduling prerequisites. Optionally, before step 340, the method 300 includes step 330. In step 330, coordinated cell: JT user pre-scheduling premise judgment.

The coordinated cell makes the pre-scheduling judgment of JT user pre-scheduling, and determines whether to initiate the collaborative response and JT user pre-scheduling based on conditions such as the load of the cell and the number of JT users that can be coordinated supported by the cell. In step 340, the pre-scheduled JT user may be a JT user who satisfies the pre-scheduling prerequisite after the judgment in step 330.

Among them, in step 340, the multi-user beam domain grouping process may be as follows:

1. Update the RlcBuffer of all users and the scheduling priority of the initial transmission after the actual scheduling of the cooperative cell in the current time slot is completed.

2. Establish a pre-scheduled user queue, and arrange the priority according to the scheduling priority of the initial transmission.

3. Multi-user beam domain grouping for users in the pre-scheduled user queue in turn.

In the embodiment of the present application, the concept of beams is used for scheduling. Pre-allocating beams for users during the pre-allocation phase, that is, pre-allocating airspace resources, not only simplifies scheduling complexity, but also utilizes the characteristics of slowly changing user airspace, such as users and cells The location of the cell is relatively fixed, and the two modules of cell pre-allocation and cell independent scheduling are relatively independent, which avoids the transmission delay and processing delay between cells due to the determination of the cooperative relationship between the coordinated cell and the coordinated cell, which in turn causes scheduling Error situation. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. Using the concept of beams during scheduling can greatly simplify the scheduling complexity.

In the pre-allocation phase, ways to reserve airspace resources for users include at least the following two ways.

Method 1, the grouping method of the beam domain.

As mentioned above, the beam domain grouping may also be referred to as an air domain grouping or beam grouping, which is used to indicate that a beam or a beam set is allocated to a user, that is, an air space resource is reserved, and the allocated beam or beam set is directed to the user. Airspace resources carried when sending data. For example, in a large-scale multi-input and multi-output scenario, the spatial domain resources can be reserved for users in a beam domain grouping manner.

Specifically, the pre-scheduled user queue may be traversed according to the scheduling priority of the initial transmission, and the users in the user queue may be grouped in the beam domain in turn. Traverse the existing beam sets of each group to determine whether they overlap with the optimal beam set of the current multi-user traversal to obtain the number of overlapping groups. Assume that the coordinated cell allocates beam set A to user A, and includes the following two cases according to the number of overlapping groups.

Case 1: The number of overlapping groups is 0.

If the number of overlapping groups is 0, and it is assumed that the total number of beams of all groups after the new group is less than or equal to the maximum number of matching layers, a new group is created for the user, that is, beam set A is assigned to user A, and beam set A is the user A's optimal beam set. The maximum number of pairing layers may be pre-defined, such as pre-defined protocol or pre-set by the network device.

Case 2: The number of overlapping groups is greater than 0.

If the number of overlapping groups is greater than 0, then user A is a conflicting user, the grouping fails, and the next user is traversed.

In the beam domain grouping process for multiple users in sequence, the JT users with successful multi-user grouping are selected into the JT user pre-scheduled success queue. If the users in the currently selected JT user pre-scheduled success queue exceed the preset threshold, for example, The preset threshold is recorded as JtUeAck_Thed, or the number of service cells that have accepted the collaboration application exceeds the preset threshold, for example, the preset threshold is recorded as JtServCellAck_Thed, then the dynamic grouping of JT users ends, and continues to be normal. User grouping. Among them, JtUeAck_Thed and JtServCellAck_Thed may be predefined, for example, the protocol is predefined or the network device is preset.

In the multi-user beam domain grouping, for collaborative JT users, the reference beam set when participating in dynamic grouping is the static static beam with the strongest RSRP of the user. The service beam set of the collaborative JT user in the collaborative cell is maintained by the collaborative cell; for ordinary For users, the reference beam set for dynamic grouping is the static beam with the strongest RSRP of the user MU Rank.

Method 2, according to channel correlation between users.

For example, in a non-large-scale multi-input multi-output scenario, airspace resources can be reserved for users based on channel correlation between users. For example, when the channel is in an ideal state or the correlation between channels is small, the transmitter uses a spatial multiplexing transmission scheme, such as dense urban areas, indoor coverage, etc .; when the correlation between channels is large, the space-time coding transmission scheme is used, such as Scenes in suburbs and rural areas.

Similarly, the channel correlation here may refer to the spatial correlation between users. According to the correlation between users, it may also be understood to be based on the spatial correlation between users.

The above describes that through way 1 and way 2, the coordinated cell pre-allocates airspace resources for users. The embodiments of the present application are not limited thereto, and any method that can pre-allocate airspace resources for users falls within the protection scope of the present application.

4. The collaborative cell feeds back the result of the collaboration application to the serving cell.

The process of pre-allocating airspace resources for users in the pre-allocation phase is described above in conjunction with FIG. 5, and the pre-scheduling and real scheduling modules are separated independently by utilizing the characteristics of slowly changing user airspace. As can be seen from the above, the collaborative distributed scheduling architecture proposed in the embodiments of the present application can be applied to the scenario of different interaction delays between cells and different user-level collaborative transmission modes, and the architecture can reuse the current single-cell scheduling process and single Cell scheduling module.

The method 400 provided according to yet another embodiment of the present application is described below with reference to FIGS. 6 to 9. The method 400 mainly introduces a process in which a serving cell and a cooperative cell perform real scheduling for users. In the method 400, the pre-scheduling process regarding the serving cell or the coordinated cell as a user has been described in detail in the method 300 above, and will not be repeated here for brevity.

In the embodiment of the present application, the scheduling in the real scheduling phase includes at least two schemes:

Scheme 1: RB alignment;

Option 2: RB is not aligned.

Before introducing these two solutions, first introduce two non-coherent JT technologies in conjunction with FIG. 6.

Duplicated multipoint collaboration (DMP)

DMP, that is, multi-point collaboration that sends the same data stream. As shown in (1) in FIG. 6, during DMP transmission, TP0 (ie, serving cell) and TP1 (ie, cooperative cell) send the same data on the same RB, that is, on the same layer 1 (layer 1, L1), layer 2 (layer2, L2), CSI measurement adopts independent channel measurement of two cells. It is transparent to the user, that is, the user considers it to be a single cell transmission.

Independent Multipoint Collaboration (SMP)

SMP, that is, multi-point collaboration that sends different data streams. As shown in (2) in Fig. 6, during SMP transmission, TP0 and TP1 each send a codeword, and CSI measurement uses two cell independent channel measurements. Because two PDCCHs are used to indicate the scheduling information of each codeword, when the SMP transmission mode is used, the RBs when TP0 and TP1 send codewords may or may not be aligned.

Two schemes for scheduling are described below: scheme 1 and scheme 2.

Option 1: RB alignment.

Option 1 is applicable to SMP and DMP in the JT mode, and the RB IDs scheduled by the JT user on the serving cell and the coordinated cell are aligned. FIG. 7 shows a scheduling flowchart of scheme 1 when JT users are actually scheduled. Each cell starts from each scheduling slot.

As shown in FIG. 7, the JT user pre-scheduling stage is first, including step 410 and step 420. Step 410 is performed in the time slot T0. In step 410, the serving cell is pre-scheduled for the JT user at L2, and the multi-user beam domain is grouped. In this process, the serving cell sends a collaboration request to the collaboration cell, and the collaboration request includes scheduling information of the JT user. Step 420 is performed in the time slot T1. In step 420, the coordinated cell is pre-scheduled for the JT user at L2, and the multi-user beam domain is grouped. In this process, the coordinated cell sends a coordinated response to the serving cell. The coordinated response includes the ID of the JT user, the RB bitmap, the multi-user pairing layer on the coordinated cell, and so on.

The following is the actual scheduling stage of JT users in time slot T2, including step 430 and step 440.

In step 430, for the serving cell, dynamic grouping in the L2 multi-user airspace: JT users are preferentially involved in grouping. Beam domain pairing is performed at L2: within the reserved RB resources within the JT user beam grouping: JT retransmission> JT new transmission, that is, the retransmitted JT user can be considered first, and then the newly transmitted JT user. L2 correlation pairing. After L2 is scheduled, L1 determines the information to be jointly sent to the JT user. The information includes: transmission block, MCS, sending right, etc. The serving cell sends the information sent to the JT user on the coordinated cell to the coordinated cell. The information includes: transmission block, MCS, transmission right and other information.

In step 430, for the collaborative cell, dynamic grouping in the L2 multi-user airspace: JT users preferentially participate in the grouping. Beam domain pairing is performed at L2: local cell scheduling is performed outside the reserved RB resources within the JT user beam grouping. L2 correlation pairing: When calculating the multi-user pairing gain on frequency-domain resources (eg PRB, RB), the multi-user queue includes JT users whose beam-domain pairing is successful. L1 receives data information to be sent by the coordinated cell, the information includes: transport block, MCS, transmission right, etc.

In step 430, specifically, in the scheduling pre-processing stage, the retransmitted JT user or the newly transmitted user participates in the multi-user dynamic grouping, and the multi-users with the successful grouping enter the multi-user beam domain pairing in the subsequent scheduling stage. For example, single-priority single-user retransmission and new-transmission scheduling queues and dynamically grouped multi-user scheduling queues can be generated separately for single-user scheduling and multi-user beam-domain pairing during real scheduling. Start resource allocation. In the case of multi-user dynamic group conflict or failed joint retransmission, users give up joint retransmission and participate in single user scheduling; multi-user dynamic grouping successful JT multi-user retransmission and new transmission users participate in multiple Beam domain pairing in the user scheduling phase. After the multi-user beam-domain pairing stage, the multi-user correlation pairing stage is entered. The multi-user dynamic grouping failed new transmission users of the joint transmission give up the joint transmission and participate in the multi-user correlation pairing as ordinary new transmission users (or non-cooperative transmission users). After the correlation pairing is completed, if there are remaining frequency domain resources (for example, PRB, RB) and the basic priority initial transmission connection to be scheduled, supplementary single-user scheduling is performed.

In step 440, for the serving cell, L1 sends control information and data (ie, an example of the first data) to the JT user. For example, during SMP transmission, the content sent includes: 2PDCCH + PDSCH; during DMP transmission, the content included includes : 1PDCCH + PDSCH. For the cooperative cell, L1 sends data (ie, an example of the second data) to the JT user. For example, in SMP transmission, the content sent includes: PDSCH; in DMP transmission, the content sent includes: PDSCH.

Option 2: RB is not aligned.

Scenario 2 is applicable to SMP in the JT mode, and the data sent to the JT user is independently scheduled on the serving cell and the cooperative cell. Therefore, RB may not be aligned. FIG. 8 and FIG. 9 respectively show the scheduling timing and scheduling flowchart of scheme 2 when JT users are actually scheduled. Each cell starts from each scheduling slot.

As shown in FIG. 8, the scheduling sequence for the JT user by the serving cell and the cooperative cell is as follows:

Time slot (N-1)

The serving cell determines the size of the transmission block to be transmitted by the JT user on the coordinated cell 1 slot in advance, and reserves HARQ ID.

In the embodiment of the present application, HARQ ID represents a HARQ process identifier, and the HARQ process identifier may also be called a HARQ process number. For example, HARQ ID means the HARQ process ID or HARQ process number is i. A HARQ process number can be used to uniquely specify a HARQ process. Each transmission block may correspond to a HARQ process, that is, the transmission block transmitted by the coordinated cell may correspond to HARQ ID. The correspondence between the transport block and the HARQ process can be reflected by the correspondence between the transport block and the HARQ process number.

Time slot (N)

The serving cell and the coordinated cell independently schedule JT users, use their respective PDCCHs to send downlink control information (downlink control information, DCI), and their respective PDSCHs transmit independent codewords (CW). The serving cell independently schedules the retransmitted or newly transmitted JT users using HARQ ID; the cooperative cell independently schedules the newly transmitted JT users using HARQ ID.

The serving cell delivers control information and data (that is, an example of the first data), which is recorded as PDCCH_CW0, PDSCH_CW0; the cooperative cell delivers control information and data (that is, an example of the second data), which is recorded as PDCCH_CW1, PDSCH_CW1. The user receives control information and data delivered by the serving cell and the cooperative cell.

In the current time slot, after the serving cell and the cooperating cell are independently scheduled, the cooperating cell returns the transmission information on this branch to the serving cell, and the serving cell supplements the scheduling information under HARQ ID on the cooperating branch in time after receiving it.

Time slot (N + k)

If the serving cell or the cooperative cell delivers downlink control information before the time slot (N + k), the user simultaneously feeds back the positive (acknowledgement, ACK) information or negative (negative) information of the HARQ ID and HARQ ID j. The user can feed back ACK or NACK information through the physical uplink control channel (PUCCH) of the serving cell; alternatively, the user can feed back ACK or NACK information through the respective PUCCH on the serving cell and the cooperating cell, that is, the user can pass The PUCCH on the serving cell feeds back the ACK or NACK information of HARQ IDj, and the PUCCH on the cooperating cell feeds back the ACK or NACK information of HARQ ID. The JT user retransmits the wrong codeword on the serving cell and the cooperative cell and retransmits it on the serving cell.

For example, as shown in FIG. 8, assuming that the user feedback HARQ ID is i NACK, HARQ ID j is ACK. You will receive an ACK message from the user.

Time slot (N + k + 5)

The serving cell determines the size of the transmission block to be transmitted by the JT user on the coordinated cell 1 slot in advance, and reserves HARQ ID.

Time slot (N + k + 6)

The serving cell independently schedules retransmitted JT users, using HARQ ID. The cooperative cell independently schedules the newly transmitted JT users, using HARQ ID.

The control information and data delivered by the serving cell are recorded as PDCCH_CW0 and PDSCH_CW0; the control information and data delivered by the cooperative cell are recorded as PDCCH_CW1 and PDSCH_CW1. The user receives control information and data delivered by the serving cell and the cooperative cell.

In the current time slot, after the serving cell and the cooperating cell are independently scheduled, the cooperating cell returns the transmission information on this branch to the serving cell, and the service cell supplements the scheduling information under HARQ IDj on the cooperating branch in time after receiving it.

It should be noted that the time units involved in the above embodiments are, for example, time slots (N-1), time slots (N + k), time slots (N + k + 5), time slots (N + k + 6) Etc., are only exemplary illustrations for ease of understanding, and the embodiments of the present application are not limited thereto.

As shown in FIG. 9, the process of scheduling the JT user by the serving cell and the cooperative cell is as follows:

In the time slot (N-1): The serving cell determines the size of the transmission block to be transmitted by the JT user on the coordinated cell 1 slot in advance, and reserves the HARQ ID. The serving cell notifies the coordinated cell of the JT user's scheduling information on the coordinated cell, such as the newly transmitted transport block size, HARQ ID, and outer loop adjustment (OllaOffset).

In the time slot (N): for the serving cell, dynamic grouping in the L2 multi-user airspace: JT users are preferred to participate in the grouping. Beam domain pairing is performed at L2: RB resources are allocated within the JT user beam grouping: JT retransmission> JT new transmission, that is, the JT user for retransmission can be considered first, and then the JT user for new transmission is considered. L2 relevance matching: JT users can participate in relevance matching. L2 supplements and updates the HARQ process information on the cooperative branch of the JT user, and is used to judge the user ACK retransmission after receiving the k-slot.

In time slot (N): For cooperative cells, dynamic grouping in L2 multi-user airspace: JT users are preferred to participate in grouping. Beam domain pairing is performed at L2: RB resources are allocated within the JT user beam grouping: only new transmissions for JT users. L2 relevance matching: JT users can participate in relevance matching. L2 determines the transmission information of the JT user on the cooperative branch, and the information includes: transmission block ID, MCS, transmission right and other information.

Optionally, the coordinated cell sends the information sent by the JT user on the coordinated cell to the serving cell, the information includes the MCS, a new data indicator (NDI) field, a redundancy version (redundancy version, RV) field, and RB ID Wait. Among them, the new data indication (NDI) field: under normal circumstances, the NDI field can be used to indicate whether the resources scheduled by the DCI are used for initial transmission or retransmission. For example, the NDI field may include 1 indicator bit. When the indicator bit is "1", the DCI may be considered for retransmission scheduling.

In the time slot (N): the serving cell sends control information and data to the JT user. For example, the control information sent by the serving cell is written as PDCCH_CW0_SercCell, and the data sent by the serving cell is written as PDSCH_CW0_SercCell. The cooperative cell sends control information and data to the JT user, for example, the control information sent by the cooperative cell is written as PDCCH_CW1_CorpCell, and the data sent by the cooperative cell is written as PDSCH_CW1_CorpCell.

The pre-scheduling process applicable to the embodiments of the present application is described above with reference to FIG. 5, and the real scheduling process applicable to the embodiments of the present application is described with reference to FIGS. 6 to 9. The following describes another application according to the present application with reference to FIGS. 10 to 12. The method 500 provided in the embodiment.

Method 500 includes steps 510 to 570, mainly including JT user identification and cooperation set management, JT user CSI measurement and CSI-RS, SRS resource configuration, JT user scheduling information update and maintenance, JT user cooperation information in the serving cell and cooperative cell Modules such as inter-party negotiation, independent scheduling of JT users on the serving cell and cooperative cell. Among them, the method of the service cell and the cooperative cell negotiating the pre-allocation of airspace resources for the JT user, and the method of the service cell and the coordinated cell negotiating the actual scheduling of the JT user have been described in detail in the above method 300 and method 400. ,No longer.

In step 510, the serving cell updates and maintains L3 user candidate coordinated cell information, and the serving cell receives SRS measurement results from the coordinated cell. Based on the measurement result, the L2 user candidate coordinated cell information is updated and maintained, and the JT user identification and collaboration set management. The serving cell configures the A3 event for the accessed user, and performs JT user identification and collaborative set selection based on the reported serving cell and RSRP of the neighboring cell.

In step 520, the serving cell determines the CSI information in different JT transmission modes according to the user's CSI report and uplink SRS channel information measurement, and maintains the outer ring adjustment amount OllaOffset in different transmission modes.

In step 530, the serving cell makes a preliminary judgment of the transmission mode according to the CSI information of the JT user in different transmission modes.

Transmission modes include, for example, SMP transmission mode, DMP transmission mode, single cell transmission mode, and so on.

In step 540, the serving cell and the cooperative cell semi-statically / periodicly perform cooperative negotiation.

The serving cell and the coordinated cell negotiate to pre-allocate airspace resources for the JT user, where the period negotiated between the serving cell and the coordinated cell may be the SRS cycle, or may be predefined, such as the protocol pre-defined. Examples are not limited.

FIG. 11 shows a schematic diagram of the serving cell reserving airspace resources for users. The serving cell performs JT user pre-scheduling: L2 groups the JT user multi-user beam domain according to the scheduling priority of the initial transmission, and the serving cell sends a collaboration request to the coordinated cell, which carries the scheduling information of the JT user.

FIG. 11 also shows a schematic diagram of the cooperative cell reserving airspace resources for the user. The coordinated cell performs JT user pre-scheduling: the coordinated cell arranges the JT users from other cells requesting cooperation and the ordinary users of the cell according to the priority of the initial transmission scheduling to do multi-user beam domain grouping. The JT user feeds back a collaboration response to other serving cells, and the collaboration response carries information such as the JT user ID, RB bitmap, and multi-user pairing layers on the collaboration cell.

In step 550, each cell is scheduled independently per time slot. If it is the moment when the collaboration takes effect, the serving cell and the collaborative cell do real scheduling for the JT user.

For serving cells, dynamic grouping in the L2 multi-user airspace: JT users preferentially participate in grouping. Beam domain pairing at L2: within the reserved RB resources within the JT user beam grouping: JT retransmission> JT new transmission. L2 correlation pairing.

For cooperative cells, dynamic grouping in the L2 multi-user airspace: JT users preferentially participate in grouping. Beam domain pairing is performed at L2: local cell scheduling is performed outside the reserved RB resources within the JT user beam grouping. L2 correlation pairing: When calculating the multi-user pairing gain on frequency-domain resources (eg PRB, RB), the multi-user queue includes JT users whose beam-domain pairing is successful.

In step 560, after L2 scheduling is completed, the serving cell sends the information sent to the JT user on the coordinated cell to the coordinated cell. The information may include: transmission block, MCS, transmission right and other information, such as {transmission block, MCS, right to send}. Accordingly, the cooperative cell receives the information to be sent to the JT user.

In step 570, the serving cell and the cooperating cell simultaneously send JT user data to the air interface.

FIG. 12 shows a schematic diagram when the serving cell and the cooperative cell jointly send data to the JT user. The serving cell and the cooperating cell use pre-allocated airspace resources to send data to JT users.

For the serving cell, L1 sends control information and data to the JT user. For example, during SMP transmission, the content sent includes: 2PDCCH + PDSCH; during DMP transmission, the content sent includes: 1PDCCH + PDSCH. For cooperative cells, L1 sends data to JT users. For example, during SMP transmission, the content sent includes: PDSCH; during DMP transmission, the content sent includes: PDSCH.

FIG. 13 shows a schematic diagram of a method 600 according to yet another embodiment of the present application from the perspective of a JT user. The method 600 includes steps 610 to 630. In the method 600, the pre-scheduling process and the real scheduling process regarding the serving cell or the cooperating cell for the user have been described in detail in the above method 300 and method 400 respectively, and will not be repeated here for brevity.

In step 610, the serving cell and cooperative cell RSPR measurement.

First introduce the beam pairing relationship. Beam pairing relationship: that is, the pairing relationship between the transmit beam and the receive beam, that is, the pairing relationship between the spatial transmit filter and the spatial receive filter. A large beamforming gain can be obtained by transmitting a signal between a transmission beam and a reception beam having a beam pairing relationship.

In an implementation manner, the sending end (for example, serving cell) and the receiving end (for example, user) can obtain the beam pairing relationship through beam training. Specifically, the serving cell may send the reference signal through beam scanning, and the user may also receive the reference signal through beam scanning. Specifically, the serving cell can form beams with different directivities in the space through beamforming, and can poll on multiple beams with different directivities to transmit reference signals through beams with different directivities, so that The power of the reference signal to transmit the reference signal in the direction pointed by the transmit beam can be maximized. The user can also form beams with different directivities in space through beamforming, and can poll on multiple beams with different directivities to receive reference signals through beams with different directivities, so that the user receives reference signals The maximum power can be reached in the direction pointed by the receive beam.

By traversing each transmit beam and receive beam, the user can perform channel measurement based on the received reference signal, and report the measurement result to the serving cell through CSI. For example, the user may report a part of the reference signal resource with a larger reference signal receiving power (reference signal receiving power, RSRP) to the serving cell, such as reporting the identity of the reference signal resource, so that the serving cell can report the identity of the reference signal resource to the serving cell based on RSRP does JT user identification and collaboration set selection.

In step 620, CSI measurement and reporting, SRS transmission.

The reference signal can be used for channel measurement or channel estimation. The reference signal resource can be used to configure the transmission properties of the reference signal, for example, the location of the airspace resource, the port mapping relationship, the power factor, and the scrambling code. For details, reference may be made to the prior art. The channel measurement involved in this application also includes beam measurement, that is, beam quality information is obtained by measuring a reference signal, and parameters used to measure the beam quality include RSRP, but are not limited thereto. For example, beam quality can also be measured by RSRQ, SNR, SINR and other parameters.

The reference signal may include CSI-RS, SSB, and SRS, for example. Correspondingly, the reference signal resources may include CSI-RS resources, SSB resources, and SRS resources.

The serving cell can determine the CSI information under different JT transmission modes and maintain the outer ring adjustment amount under different transmission modes according to the user's CSI report and SRS channel information measurement.

In step 630, data is received and ACK / NACK is fed back.

As in step 570 in the method 500 above, the user receives data sent by the serving cell and the coordinated cell. After receiving the data, the user can perform ACK or NACK feedback on the data.

The overall process of distributed scheduling provided according to an embodiment of the present application is described above with reference to FIGS. 10 to 13. The following describes the scheduling scheme of the HARQ process applicable to the embodiments of the present application with reference to FIGS. 14 and 15.

The HARQ process scheduling scheme provided by the embodiment of the present application complies with the current R15 protocol as much as possible:

1. The maximum number of HARQ processes for users is 16;

2. The SMP transmission mode is still a MAC entity, so the maximum number of HARQ processes during SMP transmission is still 16;

3. At present, the protocol has not defined the specific DCI indication information and ACK feedback form under dual DCI, so it is the implementation scheme that is currently more likely to be adopted.

The product realization of the HARQ process scheduling solution provided by the embodiment of the present application:

1. For the CRAN scheduling architecture, if the JT scheduling scheme 2 is adopted, that is, the RB non-aligned scheme, when the SMP transmission mode is adopted, the RB may be non-aligned when the user transmits jointly on the serving cell and the coordinated cell;

2. The dual PDCCH is independently delivered by the serving cell and the cooperative cell;

3. The ACK feedback of the users with two independent codewords under the double DCI indication is received by the serving cell;

4. The user ACK feedback can be uploaded by the PUCCH of the serving cell, or can also be uploaded by the respective PUCCH of the serving cell and the cooperating cell;

5. Assuming that data is sent to the user in the time slot (N), the current user ACK feedback capability is N + 8 or N + 1, and the time delay for the base station to release the HARQ process is N + 6.

The following uses the user feedback ACK information as an example, and introduces the HARQ process scheduling scheme in the SMP transmission mode with reference to FIG. 14.

The serving cell uses dual PDCCHs, for example, denoted as PDCCH1 and PDCCH2, and the DCI format can be DCI 1_1. For example, in the time slot (N), when the serving cell (denoted as TP0) and the cooperating cell (denoted as TP1) cooperatively transmit the transport block 1 to the user, the codeword sent by TP0 is carried on PDCCH1, which is denoted as TP0CW1 and carried on PDCCH2 The codeword sent by TP1 is recorded as TP1 CW1. For another example, in the time slot (N + 1), when the serving cell and the cooperating cell cooperatively transmit the transport block 2 to the user, the codeword sent by TP0 is carried on PDCCH1, which is denoted as TP0CW2, and the codeword sent by TP1 is carried on PDCCH2, and As TP1 CW2. For the PDCCH1 and PDCCH2 of the time slot (N) and the PDCCH1 and PDCCH2 of the time slot (N + 1), it is possible to distinguish which module failed to transmit, for example, to inform the terminal device through the disable flag on the PDCCH, which one needs to be retransmitted.

The dual DCI uses different HARQ IDs to indicate the transmission information of the user's transmission blocks on the serving cell and the cooperating cell in the SMP transmission mode. As shown in FIG. 14, PDCCH1 indicates TP0CW and PDCCH2 indicates TP1CW. The transmission information may include: {MCS, NDI, RV}, and other field information of the dual DCI may also be the same. The NDI can be used to indicate whether the resources scheduled by the DCI are used for initial transmission or retransmission. For example, the NDI field may include 1 indicator bit. When the indicator bit is "1", the DCI may be considered for retransmission scheduling.

The codewords transmitted on the serving cell and the coordinated cell can be selected as an indication from any two PDCCHs. The number of RBs occupied by codewords on the serving cell and the cooperative cell may be different.

User feedback ACK: When the user feedbacks the ACK, the ACK information of the two TP codewords is fed back on the same uplink control information (uplink control information, UCI), which is equivalent to the ACK feedback under the single DCI double codeword.

The location of the ACK for the transport block carried on PDCCH1 on UCI is in accordance with the bitmap index (BitMapIndex) in DCI, and the location of the ACK for the transport block carried on PDCCH2 is in accordance with BitMapIndex + 1.

Based on the above technical solutions, the HARQ process scheduling scheme that defines HARQ IDs according to codewords or transmission blocks is conducive to the sharing of HARQ process resources when they are transmitted on two transmission points (such as the serving cell and the cooperative cell), ensuring the HARQ merge of JT users While gaining, it also saves HARQ process resources. The HARQ process scheduling scheme can be applied to dual DCI scheduling two different HARQ transmission block buffers (TB buffers) at a time, so that in the SMP transmission mode, the user's RBs on the two transmission points can be misaligned (RB IDs are different), This is more conducive to the independent scheduling of user data on two transmission points in the SMP transmission mode.

The following describes the round trip time (RTT) of codeword transmission between the serving cell and the cooperative cell in the SMP transmission mode with reference to FIG. 15.

After the user performs channel coding on the transmission block, the user can register the data obtained by the channel coding in the buffer and wait for transmission. The transmission blocks in the cache and the HARQ process may have a one-to-one correspondence, and each transmission block may correspond to one HARQ process. The correspondence between the transport block and the HARQ process can be reflected by the correspondence between the transport block and the HARQ process number. Therefore, the terminal device may determine the correspondence between the transport block and the HARQ process number in advance.

The serving cell transmits a code word from the time slot (N), delivers DCI0, uses HARQ ID (or HARQ Process ID: j), and returns ACK to the time slot (N + k), and then to the time slot ( N + k + 6) The serving cell releases the HARQ process: HARQ ID, where the required RTT is (k + 6) time slots.

The cooperating cell transmits a codeword: from the time slot (N-1), the serving cell reserves HARQ ID (i.e., HARQ Process ID: i) in advance, and sends DCI1 to the time slot (N) N + k) The user feeds back the ACK, and then releases the HARQ process: HARQ ID in the (N + k + 6) serving cell, where the required RTT is (k + 6 + 1) time slots.

It can be seen that in order for JT users to be continuously scheduled within a RTT range (from time slot (N-1) to time slot (N + k + 6), assuming FDD), a total of (k + 6) + (k + 6 + 1) = (2k + 13) HARQ TB buffer. NR supports up to 16 HARQ process IDs. According to HARQ process scheduling scheme 2, it is equivalent to 32 HARQ TB buffers. As long as (2k + 13) is less than 32, HARQ process resources are sufficient.

Currently, the user feedback capability K = 8 or 1, so using the HARQ process scheduling scheme, the HARQ process resources are sufficient.

Based on the above technical solution, in cooperative joint transmission, for example, when multiple network devices perform data transmission with one terminal device, the network device can use the concept of beams when scheduling, and pre-allocate beams or beam sets for terminal devices in the pre-allocation phase, that is, Pre-allocating airspace resources not only simplifies scheduling complexity, but also utilizes the slow-changing characteristics of terminal equipment airspace to pre-allocate network equipment and network equipment independent scheduling. The two modules are relatively independent of each other, avoiding the cooperative relationship between multiple network equipment. It is determined that the transmission delay and processing delay of multiple network devices are consumed, which in turn causes scheduling errors. In some scenarios, such as large-scale multi-input and multi-output scenarios, the number of antennas is greater and the beams of multi-antenna shaping are narrower. Using the concept of beams during scheduling can greatly simplify the scheduling complexity. In addition, the scheduling architecture of the embodiment of the present application can reuse the current single-cell scheduling process and the single-cell scheduling module, while improving the perception rate of CoMP users, and also taking into consideration that no loss is caused to the average performance of the system.

In addition, based on the above technical solution, a HARQ process scheduling scheme that defines HARQ process numbers according to codewords or transmission blocks is beneficial for sharing of HARQ process resources when transmitting on multiple network devices (eg, multiple transmission points, such as multiple cells) , While ensuring the HARQ merge gain of JT users, it also saves HARQ process resources.

It should be understood that in the above embodiments, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any implementation process of the embodiments of the present application. limited.

The method provided in the embodiments of the present application has been described in detail above with reference to FIGS. 5 to 15. Hereinafter, the communication device provided by the embodiment of the present application will be described in detail with reference to FIGS. 16 to 18.

16 is a schematic block diagram of a communication device provided by an embodiment of the present application. As shown, the communication device 1000 may include a communication unit 1100 and a processing unit 1200.

In a possible design, the communication device 1000 may correspond to the network device in the foregoing method embodiment. For example, it may be a network device, or a chip configured in the network device.

Specifically, the communication device 1000 may correspond to the network device in the method 300, method 400, method 500, and method 600 according to the embodiment of the present application. The communication device 1000 may include the network device used to execute FIGS. 5-15 The unit of method performed. In addition, each unit in the communication device 1000 and the other operations and / or functions described above are to implement the corresponding flows of the methods in FIGS. 5 to 15, respectively.

Wherein, when the communication device 1000 is used to perform the method 300 in FIG. 5, the communication unit 1100 can be used to perform step 320 or step 340 in the method 300, and the processing unit 1200 can be used to perform step 310 to step 340 in the method 300.

When the communication device 1000 is used to perform the method 400 in FIG. 7, the communication unit 1100 may be used to perform step 440 in the method 400 and the processing unit 1200 may be used to perform steps 410 to 430 in the method 400.

When the communication device 1000 is used to perform the method 500 in FIG. 10, the communication unit 1100 may be used to perform step 570 in the method 500, and the processing unit 1200 may be used to perform steps 510 to 560 in the method 500.

When the communication device 1000 is used to perform the method 600 in FIG. 13, the communication unit 1100 may be used to perform step 620 or step 630 in the method 600, and the processing unit 1200 may be used to perform step 610 in the method 600.

It should be understood that the specific process of each unit performing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, no further description is provided here.

It should also be understood that when the communication device 1000 is a network device, the communication unit 1100 in the communication device 1000 may correspond to the transceiver 3100 in the network device 3000 shown in FIG. 18, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 3200 in the network device 3000 shown in FIG. 18.

It should also be understood that when the communication device 1000 is a chip configured in a network device, the communication unit 1100 in the communication device 1000 may be an input / output interface.

In another possible design, the communication device 1000 may correspond to the terminal device in the foregoing method embodiment. For example, it may be a terminal device, or a chip configured in the terminal device.

Specifically, the communication device 1000 may correspond to the terminal devices in the method 300, the method 400, the method 500, and the method 600 according to the embodiments of the present application. The communication device 1000 may include the terminal devices used to execute FIGS. 5 to 15 The unit of method performed. In addition, each unit in the communication device 1000 and the other operations and / or functions described above are to implement the corresponding flows of the methods in FIGS. 5 to 15, respectively.

Wherein, when the communication device 1000 is used to perform the method 400 in FIG. 7, the communication unit 1100 can be used to perform step 440 in the method 400, and the processing unit 1200 can be used to perform step 410 in the method 400.

When the communication device 1000 is used to perform the method 500 in FIG. 10, the communication unit 1100 may be used to perform step 570 in the method 500, and the processing unit 1200 may be used to perform step 520 in the method 500.

When the communication device 1000 is used to perform the method 600 in FIG. 13, the communication unit 1100 may be used to perform step 620 or step 630 in the method 600, and the processing unit 1200 may be used to perform step 610 in the method 600.

It should also be understood that when the communication device 1000 is a terminal device, the communication unit in the communication device 1000 may correspond to the transceiver 2020 in the terminal device 2000 shown in FIG. 17, and the processing unit 1200 in the communication device 1000 may This corresponds to the processor 2010 in the terminal device 2000 shown in FIG. 17.

It should also be understood that when the communication device 1000 is a chip configured in a terminal device, the communication unit 1100 in the communication device 1000 may be an input / output interface.

17 is a schematic structural diagram of a terminal device 2000 provided by an embodiment of the present application. The terminal device 2000 may be applied to the system shown in FIG. 1 or FIG. 2 to perform the functions of the terminal device in the above method embodiments.

As shown, the terminal device 2000 includes a processor 2010 and a transceiver 2020. Optionally, the terminal device 2000 further includes a memory 2030. Among them, the processor 2010, the transceiver 2002 and the memory 2030 can communicate with each other through an internal connection channel to transfer control and / or data signals. The memory 2030 is used to store a computer program, and the processor 2010 is used from the memory 2030 Call and run the computer program to control the transceiver 2020 to send and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040 for sending uplink data or uplink control signaling output by the transceiver 2020 through a wireless signal.

The processor 2010 and the memory 2030 may be combined into a processing device. The processor 2010 is used to execute the program code stored in the memory 2030 to implement the above functions. During specific implementation, the memory 2030 may also be integrated in the processor 2010 or independent of the processor 2010. The processor 2010 may correspond to the processing unit in FIG. 16.

The above-mentioned transceiver 2020 may correspond to the communication unit in FIG. 16 and may also be referred to as a transceiver unit. The transceiver 2020 may include a receiver (or receiver, receiving circuit) and a transmitter (or transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.

It should be understood that the terminal device 2000 shown in FIG. 17 can implement various processes involving the terminal device in the method embodiments shown in FIGS. 5 to 15. The operations and / or functions of each module in the terminal device 2000 are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments. In order to avoid repetition, the detailed description is appropriately omitted here.

The above-mentioned processor 2010 may be used to perform the actions described in the foregoing method embodiments that are internally implemented by the terminal device, and the transceiver 2020 may be used to perform the operations described in the foregoing method embodiments by the terminal device to or from the network device. action. For details, please refer to the description in the foregoing method embodiment, and no more details are provided here.

Optionally, the above-mentioned terminal device 2000 may further include a power supply 2050 for providing power to various devices or circuits in the terminal device.

In addition, in order to make the functions of the terminal device more perfect, the terminal device 2000 may further include one or more of an input unit 2060, a display unit 2070, an audio circuit 2080, a camera 2090, a sensor 2100, etc. It may also include a speaker 2082, a microphone 2084, and so on.

18 is a schematic structural diagram of a network device provided by an embodiment of the present application, for example, may be a schematic structural diagram of a base station. The base station 3000 may be applied to the system shown in FIG. 1 or FIG. 2 to perform the functions of the network device in the above method embodiments.

As shown in the figure, the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBU) (also called digital units) , Digital, unit, DU) 3200. The RRU 3100 may be called a transceiver unit, corresponding to the communication unit 1200 in FIG. 16. Optionally, the transceiver unit 3100 may also be called a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 3101 and a radio frequency unit 3102. Optionally, the transceiving unit 3100 may include a receiving unit and a transmitting unit, the receiving unit may correspond to a receiver (or receiver, receiving circuit), and the transmitting unit may correspond to a transmitter (or transmitter, transmitting circuit). The RRU 3100 part is mainly used for the transmission and reception of radio frequency signals and the conversion of radio frequency signals and baseband signals, for example, for sending instruction information to terminal devices. The BBU 3200 part is mainly used for baseband processing and control of the base station. The RRU 3100 and the BBU 3200 may be physically arranged together, or may be physically separated, that is, distributed base stations.

The BBU 3200 is the control center of the base station, and may also be referred to as a processing unit, which may correspond to the processing unit 1100 in FIG. 16, and is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spread spectrum, and so on. For example, the BBU (processing unit) may be used to control the base station to perform the operation flow on the network device in the above method embodiment, for example, to generate the above instruction information.

In an example, the BBU 3200 may be composed of one or more boards, and multiple boards may jointly support a wireless access network (such as an LTE network) of a single access standard, or may support different access standards respectively. Wireless access network (such as LTE network, 5G network or other networks). The BBU 3200 also includes a memory 3201 and a processor 3202. The memory 3201 is used to store necessary instructions and data. The processor 3202 is used to control the base station to perform necessary actions, for example, to control the base station to perform the operation flow on the network device in the foregoing method embodiment. The memory 3201 and the processor 3202 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It is also possible that multiple boards share the same memory and processor. In addition, each board can also be provided with necessary circuits.

It should be understood that the base station 3000 shown in FIG. 18 can implement various processes involving network devices in the method embodiments of FIGS. 5 to 15. The operations and / or functions of each module in the base station 3000 are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments. In order to avoid repetition, the detailed description is appropriately omitted here.

The above-mentioned BBU 3200 can be used to perform the actions described in the foregoing method embodiments that are internally implemented by the network device, and the RRU 3100 can be used to perform the actions described in the previous method embodiments that the network device sends to or receives from the terminal device. For details, please refer to the description in the foregoing method embodiment, and no more details are provided here.

An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the method in any of the foregoing method embodiments.

It should be understood that the above processing device may be a chip. For example, the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a system on chip (SoC), or It is a central processor (CPU), it can also be a network processor (NP), it can also be a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller) , MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.

In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware processor, or may be executed and completed by a combination of hardware and software modules in the processor. The software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. In order to avoid repetition, they will not be described in detail here.

It should be noted that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the foregoing method embodiment may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components . The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly embodied and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, and registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electronically Erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (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 (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous RAM), SDRAM), double data rate synchronous dynamic random access memory (double data SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) ) And direct memory bus random access memory (direct RAMbus RAM, DR RAM). It should be noted that the memories of the systems and methods described herein are intended to include, but are not limited to these and any other suitable types of memories.

According to the method provided in the embodiment of the present application, the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code runs on the computer, the computer is caused to perform the operations shown in FIGS. 5 to 15 The method of any one of the embodiments is shown.

According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium that stores program code, and when the program code is run on a computer, the computer is caused to execute the operations shown in FIGS. 5 to 15. The method of any one of the embodiments is shown.

According to the method provided in the embodiments of the present application, the present application further provides a system, which includes the foregoing one or more terminal devices and one or more network devices.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server or data center Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device including a server, a data center, and the like integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disc, SSD)) etc.

The network device in each of the above device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding steps are performed by the corresponding modules or units, for example, the communication unit (transceiver) performs the receiving or The steps of sending, other than sending and receiving, can be executed by the processing unit (processor). The function of the specific unit can refer to the corresponding method embodiment. There may be one or more processors.

The terms "component", "module", "system", etc. used in this specification are used to denote computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both the application running on the computing device and the computing device can be components. One or more components can reside in a process and / or thread of execution, and a component can be localized on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The component may, for example, be based on a signal having one or more data packets (eg, data from two components that interact with another component between the local system, the distributed system, and / or the network, such as the Internet that interacts with other systems through signals) Communicate through local and / or remote processes.

Those of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a division of logical functions. In actual implementation, there may be other divisions, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (22)

1. A method for sending data, which is characterized by comprising:

   The first network device pre-allocates the first beam to the terminal device;

   The first network device sends collaboration request information to a second network device, where the collaboration request information is used to request the second network device to cooperate with the first network device to send second data to the terminal device;

   The first network device receives collaboration response information from the second network device, where the collaboration response information is feedback information for the collaboration request information;

   Based on the collaboration response information, the first network device sends first data to the terminal device through the first beam.
2. The method according to claim 1, wherein the method further comprises:

   The first network device pre-allocates N sets of beam sets for N terminal devices, the N terminal devices correspond to the N sets of beam sets in one-to-one correspondence, and the N terminal devices include the terminal devices, wherein, N Is an integer greater than 1 or equal to 1;

   The first network device pre-allocating the first beam to the terminal device includes:

   The first network device pre-allocates a first set of beam sets for the terminal device, the first set of beam sets includes the first beam, and the N sets of beam sets include the first set of beam sets.
3. The method according to claim 1, wherein the first network device pre-allocating the first beam to the terminal device includes:

   The first network device pre-allocates a first beam to the terminal device according to channel correlation.
4. The method according to any one of claims 1 to 3, wherein the method further comprises:

   The first network device sends first downlink control information and second downlink control information to the terminal device, the first downlink control information schedules the first data, and the second control information schedules the first Two data, and,

   The first data corresponds to a first hybrid automatic repeat request process number, and the second data corresponds to a second hybrid automatic repeat request process number.
5. The method according to claim 4, wherein the method further comprises:

   The first network device receives information for the second data from the second network device;

   The second network device updates scheduling information corresponding to the process number of the second hybrid automatic repeat request according to the information for the second data.
6. The method according to claim 4 or 5, wherein the method further comprises:

   The first network device receives feedback information for the first data and feedback information for the second data sent by the terminal device.
7. The method according to claim 6, wherein the method further comprises:

   When the feedback information for the first data is negative NACK information, the first network device resends the first data to the terminal device; and / or,

   When the feedback information for the second data is NACK information, the first network device retransmits the second data to the terminal device.
8. A method for sending data, which is characterized by comprising:

   The second network device receives collaboration request information from the first network device, where the collaboration request information is used to request the second network device to cooperate with the first network device to send second data to a terminal device;

   The second network device pre-allocates a second beam to the terminal device according to the collaboration request information;

   The second network device sends collaboration response information to the first network device, where the collaboration response information is feedback information for the collaboration request information;

   Based on the cooperation response information, the second network device sends the second data to the terminal device through the second beam.
9. A method for receiving data, characterized in that it includes:

   The terminal device receives first data from the first network device and second data from the second network device, the first data is carried in a first beam, the second data is carried in a second beam, and the first beam Is a beam pre-allocated by the first network device to the terminal device, and the second beam is a beam pre-allocated by the second network device to the terminal device;

   The terminal device sends feedback information for the first data and the second data to the first network device.
10. The method according to claim 9, wherein the method further comprises:

    The terminal device receives first downlink control information and second downlink control information from the first network device, the first downlink control information schedules the first data, and the second control information schedules the Second data, and,

    The first data corresponds to a first hybrid automatic repeat request process number, and the second data corresponds to a second hybrid automatic repeat request process number.
11. A communication device, characterized in that it includes:

    The processing unit is used to pre-allocate the first beam to the terminal device;

    A transceiver unit, configured to send collaboration request information to a second network device, where the collaboration request information is used to request the second network device to cooperate with the apparatus to send second data to the terminal device;

    The transceiving unit is further configured to: receive collaboration response information from the second network device, where the collaboration response information is feedback information for the collaboration request information;

    The transceiver unit is further configured to send first data to the terminal device through the first beam based on the cooperation response information.
12. The apparatus according to claim 11, wherein the processing unit is further configured to:

    N terminal devices are pre-allocated with N groups of beam sets, and the N terminal devices are in one-to-one correspondence with the N groups of beam sets. The N terminal devices include the terminal devices, where N is greater than or equal to 1. An integer of

    The processing unit is specifically used for:

    A first set of beam sets is pre-allocated for the terminal device, the first set of beam sets includes the first beam, and the N sets of beam sets include the first set of beam sets.
13. The apparatus according to claim 11, wherein the processing unit is specifically configured to:

    Pre-allocate the first beam to the terminal device according to the channel correlation.
14. The device according to any one of claims 11 to 13, wherein the transceiver unit is further used to:

    Send first downlink control information and second downlink control information to the terminal device, the first downlink control information schedules the first data, the second control information schedules the second data, and,

    The first data corresponds to a first hybrid automatic repeat request process number, and the second data corresponds to a second hybrid automatic repeat request process number.
15. The apparatus according to claim 14, wherein the transceiver unit is further configured to:

    Receiving information for the second data from the second network device;

    The processing unit is also used to:

    According to the information for the second data, the scheduling information corresponding to the process number of the second hybrid automatic repeat request is updated.
16. The device according to claim 14 or 15, wherein the transceiver unit is used to:

    Receiving feedback information for the first data and feedback information for the second data sent by the terminal device.
17. The apparatus according to claim 16, wherein the transceiver unit is further configured to:

    When the feedback information for the first data is negative NACK information, resend the first data to the terminal device; and / or,

    When the feedback information for the second data is NACK information, resend the second data to the terminal device.
18. A communication device, characterized in that it includes:

    A transceiver unit, configured to receive collaboration request information from a first network device, where the collaboration request information is used to request the apparatus to cooperate with the first network device to send second data to a terminal device;

    Processing unit: configured to pre-allocate a second beam to the terminal device according to the collaboration request information;

    The transceiver unit is further configured to: send collaboration response information to the first network device, where the collaboration response information is feedback information for the collaboration request information;

    The transceiver unit is further configured to send the second data to the terminal device through the second beam based on the cooperation response information.
19. A communication device, characterized in that it includes:

    The transceiver unit is used to receive the first data from the first network device and the second data from the second network device, the first data is carried on the beam, the second data is carried on the second beam, The beam is a beam pre-allocated by the first network device for the device, and the second beam is a beam pre-allocated by the second network device for the device;

    The transceiver unit is further configured to send feedback information for the first data and the second data to the first network device.
20. The apparatus according to claim 19, wherein the transceiver unit is further configured to:

    Receiving first downlink control information and second downlink control information from the first network device, the first downlink control information schedules the first data, and the second control information schedules the second data, as well as,

    The first data corresponds to a first hybrid automatic repeat request process number, and the second data corresponds to a second hybrid automatic repeat request process number.
21. A communication device, characterized in that it includes:

    Memory, used to store computer programs;

    A processor, configured to execute a computer program stored in the memory, so that the device executes the method according to any one of claims 1 to 10.
22. A computer-readable storage medium including a computer program, which when run on a computer, causes the computer to perform the method according to any one of claims 1 to 10.

Images