Method and apparatus for sending and receiving indications

Abstract

The present application provides a method for sending and receiving indications, including: receiving indication information generated according to a DMRS port configuration table corresponding to a demodulation reference signal DMRS pattern type, where the DMRS port configuration table includes multiple rows of DMRS configurations; determining, according to the indication information, the number of DMRS ports and the CDM antenna port groups of DMRS not used for data transmission; where, among the multiple rows of DMRS configurations, there is one or more rows of DMRS configurations applicable to multi-user scheduling, where the number of configured CDM antenna port groups is greater than or equal to 2, the configured DMRS ports come from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with a number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups. Thus, the terminal device can be configured to extend to DMRS configuration schemes in more scenarios, reducing the limitations of DMRS configurations.

Description

[0001] This application is a divisional application of the Chinese patent application with the application number 201910028034.4 and the application title "Method and Apparatus for Sending and Receiving Indications", which was filed with the Chinese Patent Office on January 11, 2019. Technical Field

[0002] This application relates to the field of wireless communications, and more particularly, to a method and apparatus for sending and receiving indications. Background Art

[0003] The rapid development of mobile communications has put forward higher requirements for the performance of cell-edge users. In a communication system, with the rapid development of mobile communications, there are higher requirements in many aspects such as system capacity, instantaneous peak rate, spectral efficiency, cell-edge user throughput, and latency. Coordinated Multiple Point (CoMP) transmission technology can improve system performance both in the uplink and downlink. It is a method for solving the inter-cell interference problem and improving the throughput of cell-edge users, especially improving the spectral efficiency at the cell edge.

[0004] CoMP technology includes technologies such as coordinated beamforming, coordinated scheduling, joint transmission, dynamic point selection, and dynamic point blanking. Base stations can interact through backhaul, air interface, etc. to coordinate the information required for transmission. Through these transmission methods, the interference to edge users can be reduced and the system performance can be improved. In CoMP technology, multiple transmission and receiving points (multi-TRP) may serve the same terminal device simultaneously.

[0005] With the development of multiple input multiple output (MIMO) technology, from the perspective of scheduling in a network system, the transmission scheduling of a network device for a terminal device is divided into single user (SU) scheduling and multiple user (MU) scheduling according to whether the transmission resources are occupied by a single user or shared by multiple users. The transmission scheduling of a network device for a terminal device includes the transmission scheduling of a physical data channel (such as PDSCH, PUSCH). By indicating the relevant configuration parameters of the demodulation reference signal (DMRS) for demodulating the physical data channel, the receiving end can receive / send the DMRS at the corresponding resource position, thereby realizing the demodulation of the corresponding physical data channel. The relevant configuration of the DMRS includes the configuration of the DMRS ports according to the mapping pattern pairs of the DMRS ports in the time-frequency resources.

[0006] Considering the complexity of the CoMP application scenario, the requirements for the DMRS configuration scheme will be higher. The existing technologies do not provide a DMRS configuration scheme that can well implement the corresponding MU scheduling. Therefore, in order to reduce the configuration limitations of the DMRS configuration scheme, it is urgent to propose a new set of DMRS configuration schemes. Summary of the Invention

[0007] This application provides a method and device for sending and receiving indications to reduce the configuration limitations of the DMRS.

[0008] In a first aspect, a method for receiving an indication is provided. This method can be executed by a terminal device, or can also be executed by a chip configured in the terminal device. This application does not make any limitations in this regard.

[0009] Specifically, the method includes: receiving indication information, where the indication information is generated according to a DMRS port configuration table corresponding to a demodulation reference signal DMRS pattern type. The DMRS port configuration table includes multiple rows of DMRS configurations, and each row of the DMRS configurations includes a configuration item of a DMRS port and a configuration item of the number of code division multiplexing CDM antenna port groups of the DMRS that is not used for data transmission. The indication information is used to indicate the DMRS port configured for the terminal device and the number of CDM antenna port groups of the DMRS that is not used for data transmission; determining the DMRS port and the number of CDM antenna port groups of the DMRS that is not used for data transmission according to the indication information; where, among the multiple rows of DMRS configurations, there is one or more rows of DMRS configurations applicable to multi-user scheduling. The number of CDM antenna port groups of the DMRS that is not used for data transmission configured in the configuration item of the number of CDM antenna port groups of the DMRS that is not used for data transmission in the one or more rows of DMRS configurations is greater than or equal to 2, and the DMRS port configured in the configuration item of the DMRS port comes from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups.

[0010] Therefore, the terminal device receives the indication information generated according to the DMRS port configuration table corresponding to the DMRS pattern type, and determines the DMRS port and the number of CDM antenna port groups of the DMRS that is not used for data transmission according to the indication of the indication information. Through the indication information generated by the DMRS port configuration table corresponding to the DMRS pattern type unique to this application, the terminal device can be configured to an extended DMRS configuration scheme in more scenarios such as CoMP-based MU scheduling, reducing the limitations of DMRS configuration.

[0011] In a second aspect, this application provides a method for sending an indication. This method can be executed by a network device, or alternatively, can be executed by a chip configured in the network device. This application does not make any limitations in this regard.

[0012] Specifically, the method includes: generating indication information according to a DMRS port configuration table corresponding to a demodulation reference signal DMRS pattern type; the DMRS port configuration table includes multiple lines of DMRS configurations, each line of the DMRS configurations includes a configuration item of a DMRS port and a configuration item of the number of code division multiplexing CDM antenna port groups of the DMRS that is not used for data transmission, and the indication information is used to indicate the DMRS port configured for the terminal device and the number of CDM antenna port groups of the DMRS that is not used for data transmission; sending the indication information; wherein, one or more lines of DMRS configurations applicable to multi-user scheduling are included in the multiple lines of DMRS configurations, and the number of CDM antenna port groups of the DMRS that is not used for data transmission configured in the configuration item of the number of CDM antenna port groups of the DMRS that is not used for data transmission in the one or more lines of DMRS configurations is greater than or equal to 2, and the DMRS port configured in the configuration item of the DMRS port comes from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups.

[0013] Therefore, the network device can indicate the DMRS port of the terminal device and the number of CDM antenna port groups of the DMRS that is not used for data transmission according to the indication information generated from the DMRS port configuration table corresponding to the DMRS pattern type. Through the indication information generated from the DMRS port configuration table unique to this application corresponding to the DMRS pattern type, a DMRS configuration scheme in more scenarios such as multi-user MU scheduling under CoMP can be extended, reducing the limitation of DMRS configuration.

[0014] Combined with the first aspect or the second aspect, in some possible implementation manners, one or more lines of DMRS configurations applicable to multi-user scheduling include that the DMRS port configured in the configuration item of the DMRS port in at least one line of DMRS configurations matches the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type; and / or, one or more lines of DMRS configurations applicable to multi-user scheduling include that the DMRS port configured in the configuration item of the DMRS port in at least one line of DMRS configurations matches a number of transmission layers less than the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type.

[0015] For the DMRS configuration of multi-user scheduling, the correspondence between DMRS ports and the number of transmission layers can be considered and extended to the DMRS configuration that at least matches the maximum number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type, or can also be extended to at least match the number of transmission layers less than the maximum number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type, or can be extended to match all the number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type. In the design of the DMRS port configuration table, this principle will be taken into account. It can be understood that the number of transmission layers in multi-user scheduling under the corresponding DMRS pattern type is for one terminal device, that is, from the perspective of one terminal device, the configured DMRS configuration matches the number of transmission layers of this terminal device in multi-user scheduling under the corresponding DMRS pattern type. From the perspective of the network device, if not considering one terminal device, the number of transmission layers in multi-user scheduling that the DMRS configuration matches under the corresponding DMRS pattern type is the sum of the number of transmission layers corresponding to all terminal devices involved in multi-user scheduling.

[0016] Combined with the first aspect or the second aspect, in some possible implementation manners, the DMRS pattern type includes at least one of the following: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols.

[0017] The DMRS pattern type can be roughly divided into two categories, namely pattern type (type) 1 and pattern type (type)

[0018] 2. For each pattern type, there are two cases of 1 symbol and 2 symbols. From the perspective of the maximum number of symbols, it can be further divided into 4 categories, namely pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols (there are two cases of 1 symbol and 2 symbols under pattern type 1), pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols (there are two cases of 1 symbol and 2 symbols under pattern type 2). For different DMRS pattern types, there is a corresponding DMRS port configuration table.

[0019] Combined with the first aspect or the second aspect, in some possible implementation manners, one or more rows of DMRS configurations applicable to multi-user scheduling in the DMRS port configuration table corresponding to at least one type included in the DMRS pattern type satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship.

[0020] For at least one type included in the DMRS pattern type, in the DMRS port configuration table, there can be one row or multiple rows of DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship, and further, it can be that in the entire table, all DMRS configurations satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship. That is, in the design of the DMRS port configuration table, this principle will be taken into account.

[0021] Combined with the first aspect or the second aspect, in some possible implementation manners, under the pattern type 2 with a maximum of 1 symbol, or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one row or multiple rows of DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship, and includes one row or multiple rows of DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship.

[0022] For the two classifications of the pattern type 2 with a maximum of 1 symbol and the pattern type 2 with a maximum of 2 symbols, in their respective corresponding DMRS port configuration tables, the DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship do not cover all the DMRS configurations in the configuration table, and there are still some DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship. That is, in the design of the DMRS port configuration table, this principle will be taken into account.

[0023] Combined with the first aspect or the second aspect, in some possible implementation manners, one row or multiple rows of DMRS configurations applicable to multi-user scheduling are used for transmitting one codeword corresponding to transmission layers from 2 to 4 layers, and / or transmitting two codewords corresponding to transmission layers from 2 to 4 layers.

[0024] One row or multiple rows of DMRS configurations applicable to multi-user scheduling in the DMRS port configuration table can be used for specific transmission layers corresponding to specific codeword transmissions, such as transmitting one codeword corresponding to transmission layers from 2 to 4 layers and transmitting two codewords corresponding to transmission layers from 2 to 4 layers, expanding the DMRS configuration schemes in more specific scenarios and reducing the limitations of DMRS configurations.

[0025] In a third aspect, a communication device is provided, including various modules or units for executing the methods in any of the possible implementation manners in the first aspect, such as a processing unit and a transceiver unit.

[0026] Fourthly, a communication device is provided, which includes a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the methods in any of the possible implementation manners of the first aspect above. 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.

[0027] In one implementation manner, the communication device is a terminal device. When the communication device is a terminal device, the communication interface can be a transceiver or an input / output interface.

[0028] In another implementation manner, the communication device is a chip configured in a terminal device. When the communication device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0029] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0030] Fifthly, a communication device is provided, which includes each module or unit for executing the methods in any of the possible implementation manners of the second aspect, such as a processing unit and a transceiver unit.

[0031] Sixthly, a communication device is provided, which includes a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the methods in any of the possible implementation manners of the second aspect above. 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.

[0032] In one implementation manner, the communication device is a network device. When the communication device is a network device, the communication interface can be a transceiver or an input / output interface.

[0033] In another implementation manner, 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 can be an input / output interface.

[0034] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0035] Seventhly, a processor is provided, which includes: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit the signal through the output circuit, so that the processor executes the methods in the first aspect or the second aspect, and any of the possible implementation manners in the first aspect or the second aspect.

[0036] In the specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits, etc. The input signal received by the input circuit can be received and input by, for example but not limited to, a receiver. The signal output by the output circuit can be output to, for example but not limited to, a transmitter and transmitted by the transmitter. Moreover, the input circuit and the output circuit can be the same circuit, which serves as the input circuit and the 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.

[0037] In a fifth aspect, a processing device is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in the first aspect or the second aspect, and any possible implementation manner in the first aspect or the second aspect.

[0038] Optionally, the processor is one or more, and the memory is one or more.

[0039] Optionally, the memory can be integrated with the processor, or the memory is separately provided from the processor.

[0040] In the specific implementation process, the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip or can be separately provided on different chips. The embodiments of the present application do not limit the type of the memory and the setting manner of the memory and the processor.

[0041] It should be understood that relevant data interaction processes, such as sending indication information, can be a process of outputting indication information from the processor, and receiving indication information can be a process of the processor receiving input indication information. Specifically, the data output by the processor can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.

[0042] The processing device in the above fifth aspect can be a chip. The processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.

[0043] In a ninth aspect, a computer program product is provided, which includes a computer program (which may also be referred to as code or instructions). When the computer program is run, it causes a computer to execute the method in the first aspect or the second aspect, and any possible implementation manner in the first aspect or the second aspect.

[0044] In a tenth aspect, a computer-readable medium is provided, which stores a computer program (which may also be referred to as code or instructions). When it runs on a computer, it causes the computer to execute the method in the first aspect or the second aspect, and any possible implementation manner in the first aspect or the second aspect.

[0045] In an eleventh aspect, a communication system is provided, which includes the aforementioned network device and terminal device. Description of the Drawings

[0046] Figure 1 It is a schematic diagram of a DMRS pattern applicable to an embodiment of the present application and the corresponding port mapping;

[0047] Figure 2 It is a schematic diagram of a communication system of a method for sending and receiving indications applicable to an embodiment of the present application;

[0048] Figure 3 It is a schematic flowchart of a method for sending and receiving indications provided by an embodiment of the present application;

[0049] Figure 4 It is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0050] Figure 5 It is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

[0051] Figure 6 It is a schematic structural diagram of a network device provided by an embodiment of the present application. Detailed Embodiments

[0052] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0053] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th generation (5G) system or New Radio (NR), etc.

[0054] It should be understood that the network device in this communication system can be any device with wireless transceiver function or a chip that can be set in the device. The device includes but is not limited to: evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home evolved Node B, or Home Node B (HNB), BaseBand Unit (BBU), Access Point (AP) in a Wireless Fidelity (WIFI) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmit receive point (TRP), etc. It can also be a gNB in a 5G system such as NR, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system. Or, it can also be a network node that constitutes a gNB or a transmission point, such as a BaseBand Unit (BBU), or a distributed unit (DU), etc.

[0055] In some deployments, a gNB can include a centralized unit (CU) and a DU. A gNB can also include a radio unit (RU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU implements radio resource control (RRC) and the functions of the packet data convergence protocol (PDCP) layer, and the DU implements the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, thus, in this architecture, high-layer signaling, such as RRC layer signaling or PHCP layer signaling, can also be considered to be sent by the DU, or sent by the DU + RU. It can be understood that the network device can 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 classified as a network device in the radio access network (RAN), or the CU can be classified as a network device in the core network (CN), which is not restricted here.

[0056] It should also be understood that the terminal device in this communication system may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application do not limit the application scenarios.

[0057] To facilitate the understanding of the embodiments of the present application, several terms involved in the present application are briefly described first.

[0058] 1. Antenna port: Abbreviated as port. It is the transmitting antenna recognized by the receiving end device, or the transmitting antennas that can be distinguished in space. The antenna port is a logical concept. One antenna port can correspond to one physical transmitting antenna, or it can correspond to multiple physical transmitting antennas. For each virtual antenna, an antenna port can be configured. Each virtual antenna can be a weighted combination of multiple physical antennas, and each antenna port can correspond to a reference signal port. The antenna port is used to carry specific physical channels, at least one of the physical signals. The signals transmitted through the same antenna port, whether these signals are transmitted through the same or different physical antennas, the channels corresponding to the paths they experience in space transmission can be regarded as the same or related (such as large-scale channel characteristics, such as the channel matrix H, being the same). That is to say, for the signals transmitted through the same antenna port, the receiving end can consider their channels to be the same or related when demodulating. That is to say, the antenna port defines the channel at a certain symbol. That is to say, if the antenna ports of two symbols are the same, it means that the channel at one symbol can be inferred from the channel at the other symbol.

[0059] An antenna port is a channel, and the terminal performs channel estimation and data demodulation based on the reference signal corresponding to an antenna port. For example, the terminal performs channel estimation and data demodulation based on the DMRS corresponding to the demodulation reference signal (DMRS) port. In the transmission of DMRS, the antenna port used to transmit DMRS is called the DMRS port.

[0060] 2. Quasi-co-location (QCL): The QCL relationship is used to indicate that multiple resources have one or more identical or similar communication characteristics. For example, if two antenna ports have a quasi-co-location relationship, then the large-scale characteristics of the channel for transmitting a signal on one port can be inferred from the large-scale characteristics of the channel for transmitting a signal on the other port. The signals corresponding to the antenna ports with the QCL relationship have the same parameters, or the parameters of one antenna port can be used to determine the parameters of another antenna port that has a QCL relationship with this antenna port, or the two antenna ports have the same parameters, or the parameter difference between the two antenna ports is less than a certain threshold. Among them, the parameters may include one or more of the following channel large-scale parameters: delay spread, Doppler spread, Doppler shift, average delay, average gain, spatial Rx parameters. Among them, the spatial Rx parameters may include one or more of the angle of arrival (AOA), dominant AoA, average AoA, angle of departure (AOD), channel correlation matrix, power angle spread spectrum of the angle of arrival, average AoD, power angle spread spectrum of the angle of departure, transmit channel correlation, receive channel correlation, transmit beamforming, receive beamforming, spatial channel correlation, spatial filter, or spatial filtering parameters, or spatial Rx parameters, etc.

[0061] Among them, the above angles can be decomposition values in different dimensions or combinations of decomposition values in different dimensions. The antenna port can be an antenna port with different antenna port numbers, or an antenna port with the same antenna port number that sends or receives information within at least one of different time, frequency, and code domains, or an antenna port with different antenna port numbers that sends or receives information within at least one of different time, frequency, and code domains.

[0062] In the existing NR protocol, the above-mentioned QCL relationships can be divided into the following four types based on different parameters:

[0063] Type A: Doppler frequency shift, Doppler spread, average delay, delay spread;

[0064] Type B: Doppler frequency shift, Doppler spread;

[0065] Type C: Doppler frequency shift, average delay; and

[0066] Type D: Spatial reception parameters.

[0067] 3. DMRS pattern: The time-frequency resources allocated to different code division multiplexing (CDM) antenna port groups / DMRS port mappings for DMRS transmission, and the distribution pattern presented in the time-frequency resources. The DMRS pattern can be divided into two major categories, type 1 and type 2, and each category has cases of 1 symbol and 2 symbols, that is, whether the DMRS resource occupies one symbol or two symbols.

[0068] Figure 1 The schematic diagram of the DMRS pattern and the corresponding port mapping is given. The vertical numbers 0 - 11 indicate 12 subcarriers occupied in the frequency domain, and the horizontal 1 symbol or 2 symbols indicate the number of symbols occupied in the time domain. Taking the case of 1 symbol under type 1 as an example, it can be seen from Figure 1 that the DMRS pattern of 1 symbol under this type corresponds to two CDM antenna port groups (hereinafter simply referred to as CDM groups), namely CDM group 0 and CDM group 1. CDM group 0 includes DMRS port 0 and DMRS port 1, and CDM group 1 includes DMRS port 2 and DMRS port 3. In the attached figure, "0 / 1" and "2 / 3" are DMRS port numbers. It can be seen that DMRS port 0 and DMRS port 1 are mapped to the time-frequency resources corresponding to CDM group 0, and DMRS port 2 and DMRS port 3 are mapped to the time-frequency resources corresponding to CDM group 1. In other words, DMRS port 0 and DMRS port 1 are transmitted on the time-frequency resources corresponding to CDM group 0, and DMRS port 2 and DMRS port 3 are transmitted on the time-frequency resources corresponding to CDM group 1.

[0069] It can be understood that Figure 1 only for example, the DMRS pattern applicable to the technical solution of the embodiments of the present application is not limited to this. In the present application, the DMRS pattern can also be referred to as the DMRS resource pattern, the DMRS port pattern, or the mapping pattern of the DMRS port on the time-frequency resources.

[0070] It should be noted that, different from the cases in the above text where the DMRS patterns have 1 symbol and 2 symbols under type 1 and type 2, in the embodiments of the present application, the 4 types of DMRS patterns are further subdivided from the perspective of the maximum number of symbols under type 1 and type 2, including: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols (including two cases of 1 symbol and 2 symbols under type 1), pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols (including two cases of 1 symbol and 2 symbols under type 2). For different DMRS pattern types, there is a corresponding DMRS port configuration table.

[0071] 4. CDM antenna port group: It can be referred to as the CDM group. Multiple antenna ports within the CDM group can occupy the same time-frequency resources, but use different code-domain resources, and they use orthogonal codes in the time domain and / or frequency domain to distinguish. In the embodiments of the present application, the terminal device assumes that the DMRS ports within a CDM group are QCL, that is, the channel condition characteristics of the DMRS ports in a CDM group are similar, which can be understood as coming from the same TRP, and it can also be considered that the signals transmitted by the antenna ports within the same CDM group can be received simultaneously. It should be noted that in the present application, the DMRS ports of different TRPs are generally considered to have no QCL relationship, that is, non-QCL.

[0072] In the embodiments of the present application, the CDM antenna port group of DMRS refers to the CDM antenna port group to which the DMRS port for DMRS transmission belongs.

[0073] The CDM antenna port group of DMRS not for data transmission refers to the CDM antenna port group of DMRS configured for the terminal device, which can transmit DMRS or actually does not use it and does not transmit DMRS. However, whether or not DMRS is transmitted, these CDM antenna port groups are not used for data transmission. For uplink transmission, these CDM antenna port groups refer to the CDM antenna port groups of DMRS not for data transmission. For downlink transmission, these CDM antenna port groups refer to the CDM antenna port groups of DMRS not for data transmission, and the terminal device can simultaneously assume that the indicated CDM antenna port groups contain downlink DMRS that may be multi-user scheduled. Exemplarily, if the number of CDM antenna port groups of DMRS not for data transmission is 1, it can be considered that the configured CDM group is CDM group {0}; if the number is 2, it can be considered that the configured CDM group is CDM group {0, 1}; if the number is 3, it can be considered that the configured CDM group is CDM group {0, 1, 2}. It should be understood that this is only an example and the present application is not limited thereto.

[0074] 5. Transmission layer (also commonly referred to as layer): The concept of the transmission layer is described from the perspective of the data processing process of the physical layer. The data sent from the medium access control (MAC) layer to the physical layer is organized in the form of transport blocks (TBs). The MAC layer can send one TB or multiple TBs to the physical layer. The transmitter performs preprocessing, scrambling, modulation, layer mapping, precoding, and time-frequency resource mapping on each TB, and converts the signal after time-frequency resource mapping into a time domain signal and sends it out. Among them, a TB can be called a codeword (CW) after preprocessing, and the codeword can be regarded as a TB with error protection. Preprocessing includes at least channel coding (turbocoder) and rate matching. The codeword is scrambled and modulated to obtain a constellation symbol. After layer mapping, the constellation symbol will be mapped to one or more transmission layers, and each transmission layer corresponds to a valid data stream. The data stream of each layer is precoded to obtain the precoded data stream. Precoding is the process of mapping the layer to the antenna port using the precoding matrix. The precoded data stream is mapped to the time-frequency resources and then converted into a time domain signal and sent out.

[0075] In the embodiment of the present application, the codeword to layer mapping (CW to layer mapping) principle includes: 1 to 4 layers (1-4 layers) correspond to a transmission scenario of one codeword, 2 to 4 layers (2-4 layers) and 5 to 8 layers (5-8 layers) can correspond to a transmission scenario of two codewords. That is, when there is only one layer of transmission, only one codeword is used; when there are 5-8 layers of transmission, two codewords are used; when there are 2-4 layers of transmission, one codeword or two codewords can be used.

[0076] For two-codeword transmission, the two codewords CW0 and CW1 are exemplified (0 and 1 are only for distinction, and may also be CW1 and CW2, etc.), where CW0 corresponds to "number of layers / 2 rounded down", and the remaining layers correspond to CW1. For example, when the number of transmission layers is 5, the transmission layer corresponding to CW0 is "5 / 2 rounded down", that is, CW0 corresponds to the transmission of layers 1 and 2 ({1,2}); the remaining layers correspond to CW1, that is, CW1 corresponds to the transmission of layers 3, 4 and 5 ({3,4,5}).

[0077] In the embodiment of the present application, the antenna port {p 0 ,……,p v-1}\ is determined according to the order of DMRS ports, where \(v\) is a variable and is the definition of the number of transmission layers. It can be seen that the antenna ports, DMRS ports, and transmission layers correspond and are consistent in number. Further, in the embodiments of the present application, the mapping relationship between the DMRS ports and the layers is that the order of the layers is the same as the indication order in the DMRS port configuration. For example, DMRS port = 0, 1, 6, layer = {layer1, layer2, layer3} = {p 0 , p 1 , p 2} = {0, 1, 6}.

[0078] 6. Multi-user (MU) scheduling: Different from the single-user scheduling where a network device (such as a base station) transmits data point-to-point with a terminal device, in MU scheduling, the point-to-point channel between a network device and a terminal device is extended to a channel between a network device and multiple terminal devices, that is, the transmission resources are shared by multiple users. For example, the data of multiple users can be transmitted in the same time-frequency resource, and the DMRS of multiple users can be distinguished through Figure 1 different DMRS ports in the DMRS patterns given in, so as to achieve multi-user scheduling.

[0079] In addition, for the convenience of understanding the embodiments of the present application, the following points are explained.

[0080] First, in the embodiments shown below, the first, second, and various numerical numbers are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. For example, CDM antenna port group 1 and CDM antenna port group 2 are used to distinguish two antenna port groups. It can be considered that these two antenna port groups are specific antenna port groups, or it can be considered that these two antenna port groups can also be distinguished by numbers such as CDM antenna port group 5 and CDM antenna port group 6. The present application does not limit this.

[0081] Second, the "saving" involved in the embodiments of the present application may refer to saving in one or more memories. The one or more memories may be set separately, or may be integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, and the present application does not limit this.

[0082] Third, the "protocol" involved in the embodiments of the present application may refer to the standard protocols in the communication field. For example, it may include LTE protocols, NR protocols, WLAN protocols, and related protocols in other communication systems. The present application does not limit this.

[0083] Fourth, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (item)" or similar expressions refer to any combination of these items, including any combination of single item or plural items. For example, at least one (item) of a, b, and c can 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, and c can be single or multiple respectively. It should be noted that in the embodiments of the present application, "multiple rows" can refer to "all rows" within a limited range in special scenarios.

[0084] For ease of understanding the embodiments of the present application, the following uses the Figure 2 communication system shown in the appendix as an example to detail the communication system applicable to the method for sending and receiving indications provided by the embodiments of the present application. The appendix Figure 2 shows a schematic diagram of a communication system 100 applicable to the method for sending and receiving indications of the embodiments of the present application. As shown in the figure, the communication system 100 may include at least one terminal device, such as the terminal device 101 shown in the figure, and may also include other terminal devices such as the terminal device 101' in a multi-user scheduling scenario; the communication system 100 may also include at least one network device, such as the network device #1 102 or the network device #2 103 shown in the figure.

[0085] Optionally, the communication system 100 may include multiple network devices, such as the network device #1 102 and the network device #2 103 shown in the figure. The network device #1 102 and the network device #2 103 may be network devices in the same cell or network devices in different cells, and the present application does not make any limitation in this regard. The figure is only an example, showing an example where the network device #1 102 and the network device #2 103 are located in the same cell.

[0086] In the communication system 100, the network device #1 102 and the network device #2 103 can communicate with each other through a backhaul link, and the backhaul link can be a wired backhaul link (such as optical fiber, copper cable) or a wireless backhaul link (such as microwave). The network device #1 102 and the network device #2 103 can cooperate with each other to provide services for the terminal device 101 and / or the terminal device 101'. Therefore, the terminal device 101 and / or the terminal device 101' can communicate with the network device #1 102 and the network device #2 103 respectively through wireless links.

[0087] In addition, taking a terminal device (such as terminal device 101) as an example, one or more of network device #1 102 and network device #2 103 can also respectively adopt carrier aggregation technology to schedule PDSCH for terminal device 101 on one or more carriers (component carriers, CCs). For example, network device #1 102 can schedule PDSCH for terminal device 101 on CC#1 and CC#2, and network device #2 103 can schedule PDSCH for terminal device 101 on CC#1 and CC#3. The CCs scheduled by network device #1 102 and network device #2 103 can be the same or different, and this application does not make any limitation in this regard.

[0088] The communication delay between cooperating network devices can be divided into ideal backhaul and non-ideal backhaul. Between two sites under ideal backhaul, the communication delay can be at the microsecond level, which can be ignored compared with the millisecond-level scheduling in NR; between two sites under non-ideal backhaul, the communication delay can be at the millisecond level, which cannot be ignored compared with the millisecond-level scheduling in NR.

[0089] In view of the complex situations brought about by multi-user scheduling in the coordinated multi-point transmission scenario, this application provides a method for sending and receiving indications, in order to expand the application scenarios of the DMRS configuration scheme and reduce the configuration limitations of the DMRS configuration scheme.

[0090] The method for sending and receiving data provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0091] Figure 3 It is a schematic flowchart of the method 300 for sending and receiving indications provided by the embodiments of this application shown from the perspective of device interaction. It should be noted that in this embodiment and subsequent embodiments, the interaction between the terminal device and the network device is described, which is only for exemplary description, and this application is not limited thereto. For the convenience of understanding the solution, in the description, this embodiment and subsequent embodiments are all described from the behaviors of multiple sides of the terminal device and the network device, and are described as a whole from the perspective of multiple interacting parties. However, it is by no means limited that the steps on each side of the interaction in the system must be executed together. The technical solutions proposed in this application have improvements on each side of the system.

[0092] It should be noted that the method for sending and receiving indications provided by this application can be applied to a wireless communication system.

[0093] For example, Figure 2 in the communication system 100 shown in. There can be a wireless communication connection relationship between communication devices in the communication system. For example, Figure 2The terminal device 101 or terminal device 101' shown in the figure can respectively have a wireless communication connection relationship with network device #1

[0094] 102 and network device #2 103. There can be an ideal backhaul link or a non-ideal backhaul link between network device #1 102 and network device #2 103. This application does not make any limitations in this regard. Figure 2 What is shown is only an example of a network system architecture involved in this application, and this application is not limited thereto. It should be understood that Figure 2 The co-transmission scenarios applicable to the embodiments of this application shown can be co-transmission scenarios of a homogeneous network or co-transmission scenarios of a heterogeneous network. The embodiments of this application do not make any limitations in this regard. It should also be understood that Figure 2 The scenarios shown can be low-frequency (such as a center frequency below 6 gigahertz) scenarios or high-frequency (such as a center frequency above 6 gigahertz) scenarios. The embodiments of this application do not make any limitations in this regard.

[0095] Such as Figure 3 As shown, the method 300 of the embodiments of this application can include steps 310 to 330. The following details each step in method 300:

[0096] In step 310, the network device generates indication information according to the DMRS port configuration table corresponding to the demodulation reference signal DMRS pattern type.

[0097] In the embodiments of this application, for different DMRS pattern types, there is one or more DMRS port configuration tables corresponding to each DMRS pattern type. The DMRS pattern types can be roughly divided into two major categories, namely pattern type (type) 1 and pattern type (type) 2, and are further divided into 4 categories, namely pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols. For specific details, refer to the description of the DMRS pattern above, and it will not be elaborated here. For different DMRS pattern types, there is one or more DMRS port configuration tables corresponding to them. The DMRS port configuration tables corresponding to each DMRS pattern type will be introduced in detail below.

[0098] From the perspective of the DMRS port configuration table, the DMRS port configuration tables corresponding to each DMRS pattern type in step 310 have the following characteristics (in other words, the DMRS port configuration table can be designed according to the following requirements):

[0099] Feature 1: Each DMRS port configuration table includes multiple lines of DMRS configurations. Each line of the DMRS configuration includes a configuration item of the DMRS port and a configuration item of the number of code division multiplexing (CDM) antenna port groups of the DMRS that is not used for data transmission.

[0100] The indication information is used to indicate the DMRS ports configured for the terminal device and the number of CDM antenna port groups of the DMRS that is not used for data transmission. Optionally, the indication information may include the line index of the DMRS port configuration table. Through the line index, a line of DMRS configuration can be indicated, so that the terminal device can learn the configuration of the DMRS port and the configuration of the number of CDM antenna port groups of the DMRS that is not used for data transmission in this line of DMRS configuration.

[0101] Feature 2: One or more lines of DMRS configurations applicable to multi-user (MU) scheduling are included in the multiple lines of DMRS configurations. In the one or more lines of DMRS configurations, the number of CDM antenna port groups of the DMRS that is not used for data transmission configured in the configuration item of the number of CDM antenna port groups of the DMRS that is not used for data transmission is greater than or equal to 2, and the DMRS ports configured in the configuration item of the DMRS port come from at least two of the CDM antenna port groups, where at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups.

[0102] According to Feature 2, there is at least one line of DMRS configuration in the DMRS port configuration table that can be applicable to MU scheduling, and it cannot be restricted to only being applicable to single-user (SU) scheduling. Moreover, in the at least one line of DMRS configuration applicable to MU scheduling, the number of CDM antenna port groups of the DMRS that is not used for data transmission configured is greater than or equal to 2, and at least one of the CDM antenna port groups does not have a quasi-co-location (QCL) relationship with other CDM antenna port groups. Such a configuration means that the CDM groups without a quasi-co-location relationship are considered to come from different transmit-receive points (TRPs) (in addition, one or more CDM groups with a QCL relationship are generally considered to come from the same TRP), and this DMRS configuration can be used for the transmission of at least two TRPs. And the configured DMRS ports come from at least two of the CDM antenna port groups. In this way, the DMRS ports configured for the terminal device belong to different TRPs, and the terminal device is served by at least two network devices. If at least two DMRS ports configured for the terminal device both belong to the same CDM antenna port group (from the above Figure 1The exemplary description of has a maximum of 1 symbol for type 1. For example, if DMRS ports 0 and 1 are configured for the terminal device, and both belong to CDM group 0), then the DMRS ports configured for the terminal device are still of the same TRP, and the terminal is still served by only one network device. Therefore, feature 2 defines that the DMRS port configuration table includes DMRS configurations applicable to MU scheduling of multi-TRP.

[0103] Optionally, the DMRS port configuration table may further include at least one of the following features (optional features):

[0104] Feature 3: One or more rows of DMRS configurations applicable to multi-user scheduling include the DMRS ports configured in the configuration items of the DMRS ports in at least one row of DMRS configurations matching the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type.

[0105] For feature 3, in the DMRS configuration for multi-user scheduling, considering the correspondence between DMRS ports and the number of transmission layers, it can be extended to the case where the DMRS configuration at least matches the maximum number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type.

[0106] Feature 4: One or more rows of DMRS configurations applicable to multi-user scheduling include the DMRS ports configured in the configuration items of the DMRS ports in at least one row of DMRS configurations matching the number of transmission layers less than the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type.

[0107] For feature 4, in the DMRS configuration for multi-user scheduling, considering the correspondence between DMRS ports and the number of transmission layers, it can be extended to the case where it at least matches the number of transmission layers less than the maximum number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type.

[0108] If the DMRS port configuration table has both feature 3 and feature 4 at the same time, then the DMRS configuration for multi-user scheduling is extended to match all the number of transmission layers for a terminal device in multi-user scheduling under the corresponding DMRS pattern type.

[0109] It should be noted that the number of transmission layers for multi-user scheduling under the corresponding DMRS pattern type mentioned above is for one terminal device. That is, from the perspective of one terminal device, the configured DMRS configuration matches the number of transmission layers of the terminal device in multi-user scheduling under the corresponding DMRS pattern type. From the perspective of the network device, if the multi-user scheduling is not considered for one terminal device, the number of transmission layers of the DMRS configuration matching in multi-user scheduling under the corresponding DMRS pattern type is the sum of the number of transmission layers corresponding to all terminal devices involved in multi-user scheduling. For example, if the maximum number of transmission layers for one terminal device is 4 layers, and the base station uses the DMRS configuration items applicable to multi-user scheduling and configures them for the multi-user scheduling of 2 terminal devices respectively, then the total number of transmission layers configured from the perspective of the network device is 8 layers.

[0110] Feature 5: One or more DMRS configurations applicable to multi-user scheduling in the DMRS port configuration table corresponding to at least one type included in the DMRS pattern type satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship.

[0111] For at least one type included in the DMRS pattern type, in the DMRS port configuration table, the DMRS configuration that satisfies the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship can have one line or multiple lines. Further, it can be that in the entire table, all DMRS configurations satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship. This enables the terminal device to assume that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship (non-QCLed).

[0112] Feature 6: Under the pattern type 2 with a maximum of 1 symbol or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one or more DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship, and includes one or more DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-collocation relationship.

[0113] Optionally, the number of lines of the DMRS configuration that satisfies CDM antenna port group 0 and CDM antenna port group 1 non-QCLed in Feature 6 is more than the number of lines of the DMRS configuration that satisfies CDM antenna port group 1 and CDM antenna port group 2 non-QCLed. This enables the terminal device to preferentially assume that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-collocation relationship (non-QCLed).

[0114] For the two classifications of having 1 symbol and having 2 symbols under DMRS pattern type 2, in the corresponding DMRS port configuration tables respectively, the assumption that the DMRS configuration satisfies that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi - co - location relationship does not cover all DMRS configurations in this configuration table. There are also some DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi - co - location relationship.

[0115] Feature 7: One or more lines of DMRS configurations applicable to multi - user scheduling are used for transmitting corresponding to one codeword with transmission layers from 2 to 4, and / or transmitting corresponding to two codewords with transmission layers from 2 to 4.

[0116] One or more lines of DMRS configurations applicable to multi - user scheduling in the DMRS port configuration table can be used for specific transmission layers corresponding to specific codeword transmissions. For example, transmitting corresponding to one codeword with transmission layers from 2 to 4, transmitting corresponding to two codewords with transmission layers from 2 to 4, which expands the DMRS configuration schemes in more specific scenarios and reduces the limitations of DMRS configurations.

[0117] In step 320, the network device sends the indication information, and the terminal device receives the indication information.

[0118] The network device can send the indication information through downlink control information (DCI). Optionally, before step 320, the network device also uses high - layer signaling, such as radio resource control (RRC) signaling, to indicate the DMRS pattern type to the terminal device. Specifically, it includes indicating DMRS pattern type 1 or type 2, and indicating the maximum number of symbols of the DMRS pattern. For example, it is indicated through the value of the maxLength field. When maxLength = 1, it indicates that the 1 - symbol DMRS pattern under the currently configured DMRS type is used for data transmission. When maxLength = 2, the network device can further dynamically and specifically indicate to the terminal device whether to use the 1 - symbol or 2 - symbol DMRS pattern under the currently configured DMRS type through DCI. Optionally, DMRS pattern type 1 / type 2 can be default, that is, fixed, without the need for the network device to indicate; or maxLength is default, without indication; or both DMRS pattern type 1 / type 2 and maxLength are default, without indication.

[0119] In step 330, according to the indication information, determine the DMRS ports and the number of CDM antenna port groups of the DMRS that are not used for data transmission.

[0120] The number of DMRS ports mentioned in Steps 310 - 330 and the CDM antenna port groups of DMRS not used for data transmission have been specifically introduced above and will not be elaborated here.

[0121] The following will provide a detailed description of the DMRS port configuration tables corresponding to 4 types of DMRS patterns (Pattern Type 1 with a maximum of 1 symbol, Pattern Type 1 with a maximum of 2 symbols, Pattern Type 2 with a maximum of 1 symbol, Pattern Type 2 with a maximum of 2 symbols), in combination with the above - described characteristics of the DMRS port configuration tables. Table 1 is the DMRS port configuration table for Pattern Type 1 with a maximum of 1 symbol, Table 2 is the DMRS port configuration table for Pattern Type 1 with a maximum of 2 symbols (applicable to both the 1 - symbol and 2 - symbol cases under Type 1), Table 3 is the DMRS port configuration table for Pattern Type 2 with a maximum of 1 symbol, and Table 4 is the DMRS port configuration table for Pattern Type 2 with a maximum of 2 symbols (applicable to both the 1 - symbol and 2 - symbol cases under Type 2). It should be noted that Tables 1 to 4 are only examples, and this application is not limited thereto. The number, order, and index of the DMRS configuration rows in Tables 1 to 4, as well as the values of the configuration items, are only examples for the characteristics of the above - mentioned DMRS port configuration tables. When implementing, it can be flexibly set as long as it meets the characteristic requirements of the DMRS configuration table in this application, and it does not constitute a specific limitation to the embodiments of this application. In addition, Tables 1 to 4 will be described by taking the DMRS configurations for single - codeword transmission and dual - codeword transmission as examples. Optionally, the DMRS port configuration table can only include the DMRS configuration for single - codeword transmission or only include the DMRS configuration for dual - codeword transmission. It can also include the DMRS configuration rows not applicable to multi - user scheduling for single - codeword transmission and the DMRS configuration rows applicable to multi - user scheduling for dual - codeword transmission, or it can include the DMRS configuration rows applicable to multi - user scheduling for single - codeword transmission and the DMRS configuration rows not applicable to multi - user scheduling for dual - codeword transmission. As long as the DMRS port configuration table includes at least the DMRS configuration rows that meet the above - mentioned Characteristics 1 and 2, the other rows are not restricted:

[0122] Table 1

[0123]

[0124] Table 1 includes a DMRS configuration part for the transmission of one codeword (hereinafter referred to as the one-codeword part) and a DMRS configuration part for the transmission of two codewords (hereinafter referred to as the two-codewords part). Each part includes three items: one is the Value representing the row index; one is the Number of DMRS CDM group(s) without data, which is the configuration item for the number of CDM antenna port groups (hereinafter referred to as CDM groups) of the DMRS not used for data transmission, and this item is used to configure the number of CDM groups of the DMRS where the terminal device does not currently transmit data; one is the DMRS port(s) configuration item, and the values therein correspond to the port numbers of the DMRS ports.

[0125] Combined with Figure 1 the correspondence between the CDM groups and the DMRS ports, it can be seen from Table 1 that the DMRS configurations of each row conform to Feature 1. In addition, both the one-codeword part and the two-codewords part are configured with reserved items for future configuration and expansion.

[0126] In the one-codeword part of Table 1, there are at least two rows of DMRS configurations (rows with indexes 12 and 13) that conform to the above-mentioned Feature 1 and Feature 2. Taking the row with index 12 as a specific example, under the pattern type 1 with a maximum of 1 symbol (only corresponding to the case of 1 symbol under type 1), DMRS port 0 belongs to CDM group 0, and DMRS port 2 belongs to CDM group 1. It can be seen that the number of CDM antenna port groups of the DMRS not used for data transmission configured in the number configuration item of the CDM antenna port groups of the DMRS not used for data transmission in this row is equal to 2 (i.e., CDM group 0 and CDM group 1), and the DMRS ports configured in the DMRS port configuration item come from the two CDM antenna port groups. Such a configuration is based on the assumption that both the network device and the terminal device stipulate that these two CDM antenna port groups (CDM group 0 and CDM group 1) do not have a QCL relationship. Therefore, it can correspond to the transmission of multi-TRP. In addition, the DMRS configuration of this row does not additionally limit it to be only used for single-user scheduling, so it can be applicable to multi-user scheduling.

[0127] In addition, under the DMRS pattern type corresponding to Table 1, the maximum number of transmission layers for a terminal device in MU scheduling can be optionally set to 2. According to the correspondence between the DMRS ports and the transmission layers, the DMRS configurations of the one-codeword part with row indexes from 12 to 13 at least further satisfy Feature 3. It can also be directly seen from Table 1 that the DMRS configurations of the one-codeword part with row indexes from 12 to 13 also satisfy Feature 7, that is, the transmission layers from 2 layers to 4 layers correspond to one-codeword transmission.

[0128] In addition to the DMRS configuration for the row indices 12 to 13 of the one codeword part in Table 1 that at least meets Feature 1 and Feature 2, the following provides a brief description of the other rows of the one codeword part (it should be noted that the other rows may exist, partially exist, or exist in a configuration different from that in Table 1 in the DMRS port configuration table of the embodiments of the present application, or the applicable scenarios may also vary, and the present application does not limit. Similarly, the two codeword parts and the rows in Tables 2 to 4 that do not meet Feature 1 and Feature 2 are also not limited):

[0129] For the DMRS configuration of the row indices 0 to 2 of the one codeword part, since the number of CDM groups all takes the value of 1, it can be seen that the configurations of these rows are used for single TRP (single TRP) transmission. For the DMRS configuration of the row indices 3 to 6, although the number of CDM groups all takes the value of 2, only one DMRS port is configured (it can only belong to one CDM group, that is, corresponding to one TRP). Therefore, the configurations of these rows are also used for single TRP transmission. However, since the DMRS ports configured for the terminal device in these rows are all one, not all ports in a CDM group are occupied, and 2 CDM groups are configured, the DMRS configurations of these rows can be paired with the DMRS configurations for multi-TRP MU scheduling. For example, index 3 and / or index 5 can be paired with the DMRS configuration of row index 13. For the DMRS configuration of the row indices 7 to 8, although the number of CDM groups all takes the value of 2, the configured DMRS ports all belong to the same CDM group, and all the DMRS ports in this CDM group are occupied. The remaining ports under this pattern type are also all in one CDM group. Therefore, the DMRS configurations of these rows can only be used for single TRP transmission and cannot be paired with other multi-TRP configurations. For the DMRS configuration of the row indices 9 to 11, since the number of CDM groups all takes the value of 2, and the DMRS ports may not all belong to the same CDM group, the DMRS configurations of these rows can be used for multi-TRP transmission, but these rows can be additionally limited to be only used for single user (SU) scheduling.

[0130] Based on the above-mentioned single-codeword part, by the same analogy, for the two-codeword part, there are at least two DMRS configurations (the rows of index 2 and 3) in the table that meet the above-mentioned Feature 1 and Feature 2. Similar to the DMRS configuration example of the row index 12 in the above single-codeword part, these two DMRS configurations can correspond to the transmission of multi-TRP. In addition, these two DMRS configurations are not additionally limited to being only used for single-user scheduling, so they can be applicable to multi-user scheduling. The DMRS configurations of the two-codeword part with row indexes from 2 to 3 at least further satisfy Feature 3 and Feature 7. Optionally, for the DMRS configuration with row index 4, its values of the DMRS configuration items are the same as those of the DMRS configuration with row index 2, but it can be additionally limited that the DMRS configuration with row index 4 is only used for single-user scheduling, that is, this row of DMRS configuration corresponds to the transmission of multi-TRP and is only used for single-user scheduling.

[0131] Taking Table 2 as an example for illustration below, for the cases similar to or the same as Table 1, a brief description is given in Table 2 and will not be elaborated further.

[0132] Table 2

[0133]

[0134]

[0135] Optionally, compared with Table 1, Table 2 has one more configuration item, that is, the number of symbols occupied by the precoded DMRS, which can be flexibly configured according to the actual situation. For example, for the row with the value of this item being 1, it corresponds to the 1-symbol situation under Type 1, and the row with the value of 2 corresponds to the 2-symbol situation under Type 1, which will not be elaborated further here.

[0136] Similar to Table 1, the DMRS configurations of the single-codeword part with row indexes from 31 to 42 in Table 2 meet Feature 1 and Feature 2 and can be applicable to the MU scheduling scenario of multi-TPR; in addition, under the DMRS pattern type corresponding to Table 2, when the number of symbols occupied by the precoded DMRS is 2, the maximum number of transmission layers for a terminal device in MU scheduling can be optionally set to 4. According to the correspondence between the DMRS ports and the transmission layers, the DMRS configurations of the single-codeword part with row indexes from 31 to 36 at least further satisfy Feature 4, and the DMRS configurations of the row indexes from 37 to 40 at least further satisfy Feature 3. It can also be directly seen from Table 2 that the DMRS configurations of the single-codeword part with row indexes from 31 to 42 also satisfy Feature 7, that is, the transmission layers from 2 to 4 layers correspond to single-codeword transmission.

[0137] The following gives a brief description of other rows of the single-codeword part (it should be noted that other rows can exist in the DMRS port configuration table of the embodiments of the present application, can exist partially, or can exist in a configuration different from that in Table 2, and the present application is not limited thereto):

[0138] The DMRS configurations for row indices 0 to 2, row indices 7 to 8, and row indices 28 to 29 are applicable to the single-TRP scenario; the DMRS configurations for row indices 3 to 6 and row indices 12 to 27 are applicable to the single-TPR scenario but can be paired with the DMRS configurations for multi-TPR MU scheduling; the DMRS configurations for row indices 9 to 11 and row index 30 are applicable to the multi-TRP SU scheduling scenario.

[0139] Similarly, the DMRS configurations with row indices 6 to 17 in two codewords in Table 2 meet Feature 1 and Feature 2, can be applicable to the multi-TRP MU scheduling scenario, and further meet Feature 7. Additionally, under the corresponding DMRS pattern type in Table 2, when the number of symbols occupied by the precoded DMRS is 2, the maximum number of transmission layers for a terminal device in MU scheduling can be optionally set to 4. Among them, the DMRS configurations with row indices 8, 9, 16, and 17 at least further meet Feature 3, and the DMRS configurations with row indices 10 to 15 at least further meet Feature 4; it should be noted that for the DMRS configuration with row index 23 in two codewords, its value is the same as that of the DMRS configuration item with row index 8 in two codewords, but it can be additionally specified that the DMRS configuration with row index 23 is only used for single-user scheduling, that is, this row of DMRS configuration corresponds to multi-TRP transmission and is only used for single-user scheduling.

[0140] It should be noted that the design of the DMRS configuration with 1 precoded DMRS symbol in Table 2 can be similar to or the same as that in Table 1, and will not be repeated here.

[0141] The DMRS configurations for row indices 0 to 3 in two codewords are applicable to the single-TPR scheduling scenario; the DMRS configurations for row indices 4 to 5 and row indices 18 to 23 are applicable to the multi-TRP SU scheduling scenario.

[0142] For Table 1 and Table 2 of the above examples, since under DMRS pattern type 1, regardless of whether the maximum is of the type with 1 symbol or 2 symbols, the maximum number of configurable CDM groups is 2, namely CDM group 0 and CDM group 1. Therefore, the relevant rows satisfy the assumption that the two CDM groups in Feature 2 do not have a QCL relationship. It can be assumed that the DMRS configurations for MU scheduling with multi TPR in Table 1 and Table 2 are based on the situation where CDM group 0 and CDM group 1 do not have a quasi - co - location relationship, that is, they conform to Feature 5 (for example, the DMRS configurations with partial row indices of 12 and 13 for one codeword in Table 1 also conform to Feature 5, and the DMRS configurations with partial row indices of 2 and 3 for two codewords also conform to Feature 5; the DMRS configurations with partial row indices from 31 to 42 for one codeword in Table 2 also conform to Feature 5, and the DMRS configurations with partial row indices from 6 to 17 for two codewords also conform to Feature 5).

[0143] The above is an exemplary introduction to the DMRS port configuration tables corresponding to the two classifications under DMRS pattern type 1. Next, an exemplary introduction will be made to the DMRS port configuration tables corresponding to the two classifications under DMRS pattern type 2. The basic design principles of the following Table 3 and Table 4 are similar to those of Table 1 and Table 2. For situations that are the same as or similar to those in Table 1 or Table 2, only a brief description will be given and no further elaboration will be made:

[0144] Table 3

[0145]

[0146]

[0147] Similar to Table 1 or Table 2, the DMRS configurations with partial row indices of 9, 20 to 22, and 24 to 29 for one codeword in Table 3 conform to Feature 1 and Feature 2 and can be applicable to the MU scheduling scenario with multi TPR. Optionally, they further conform to Feature 7; the DMRS configurations with partial row indices of 0 to 2, 7 to 8, and 17 to 18 are applicable to the single TPR scenario; the DMRS configurations with partial row indices of 3 to 6, 11 to 16, and 19 are applicable to the single TPR scenario but can be paired with the DMRS configurations for MU scheduling with multi TPR; the DMRS configurations with partial row indices of 10 and 23 are applicable to the SU scheduling scenario with multi TPR. Additionally, under the DMRS pattern type corresponding to Table 3, for a terminal device, the maximum number of transmission layers in MU scheduling can be optionally set to 4. According to the correspondence between DMRS ports and the transmission layer, the DMRS configuration with partial row index of 22 for one codeword at least further satisfies Feature 3, and the DMRS configurations with partial row indices of 9, 20 to 21, and 24 to 29 at least further satisfy Feature 4.

[0148] In addition, for individual rows in a single-codeword part, such as the DMRS configuration with a row index of 21, it satisfies the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-colocation relationship (since DMRS port 3 belongs to CDM group 1, and DMRS ports 4 and 5 belong to CDM group 2, if MU scheduling applicable to multi-TRP is satisfied, it is necessary to assume that CDM group 1 and CDM group 2 do not have a QCL relationship). For other DMRS configurations applicable to MU scheduling of multi-TPR, it is preferentially assumed that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-colocation relationship. Therefore, the rows with indexes 9, 20 to 22, and 24 to 29 meet feature 6, and the rows with indexes 9, 20, 22, and 24 to 29 also meet feature 5. Optionally, the DMRS configurations with row indexes 28 and 29 in a single-codeword may not be retained in the table. Retaining the rows with indexes 20 and 21 is applicable to the multi-TRP scenario. In this case, the terminal device needs to assume that CDM group 0 and CDM group 1 are non-QCL in the row with index 20, and CDM group 1 and CDM group 2 are non-QCL in the row with index 21, and it meets feature 6. It is also possible to specifically specify that the row with index 21 cannot be used in the multi-TRP scenario and retain the rows with indexes 28 and 29. In this case, the terminal device in the table can assume that all rows in the single-codeword part are non-QCL between CDM group 0 and CDM group 1, which meets feature 5. For the two-codeword part, there are similar relationships for the rows with indexes 8, 9, 11, and 12. Among them, only 9 needs to assume that CDM1 and 2 are non-QCL, and the rest can assume that CDM0 and 1 are non-QCL.

[0149] Similar to Table 1 or Table 2, the DMRS configurations of the two-codeword part with row indexes 2 to 4 and 6 to 12 in Table 2 meet feature 1 and feature 2 and can be applicable to the MU scheduling scenario of multi-TPR; optionally, they further meet feature 7; among them, the rows with indexes 2 to 4, 6 to 9, and 11 to 12 further meet feature 4, and the row with index 10 further meets feature 3. The DMRS configurations with row indexes 0, 1, 5, and 13 are applicable to the SU scheduling scenario of multi-TPR.

[0150] In addition, for individual rows in the two-codeword part, such as the DMRS configuration with a row index of 9, it satisfies the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-colocation relationship. For other DMRS configurations applicable to MU scheduling of multi-TPR, it is preferentially assumed that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-colocation relationship. Therefore, the rows with indexes 2 to 4 and 6 to 12 meet feature 6, and the rows with indexes 2 to 4, 6 to 8, and 10 to 12 also meet feature 5.

[0151] Taking Table 4 as an example for illustration, for cases similar to or the same as the aforementioned table, a brief description is given in Table 4 and will not be elaborated further.

[0152] Table 4

[0153]

[0154]

[0155]

[0156] Optionally, compared with Table 3, Table 4 has one more configuration item, that is, the number of symbols occupied by the preamble DMRS, which can be flexibly configured according to the actual situation and will not be elaborated further here.

[0157] Similar to the aforementioned table, the DMRS configurations of the partial row indices 9, 20 to 22, and 58 to 81 of one codeword in Table 4 conform to Feature 1 and Feature 2 and can be applied to the MU scheduling scenario of multi TPR. Further, they can also conform to Feature 7; the DMRS configurations of the row indices 0 to 2, 7 to 8, 17 to 18, 45 to 46, and 48 to 53 are applicable to the single TPR scenario; the DMRS configurations of the row indices 3 to 6, 11 to 16, 19, 24 to 44, 47, and 54 to 57 are applicable to the single TPR scenario but can be paired with the DMRS configurations of the multi TPR's MU scheduling; the DMRS configurations of the row indices 10 and 23 are applicable to the multi TPR's SU scheduling scenario. Additionally, under the DMRS pattern type corresponding to Table 4, the maximum number of transmission layers for a terminal device in MU scheduling can be optionally set to 4. According to the correspondence between the DMRS ports and the transmission layers, the DMRS configurations of the partial row indices 22, 70 to 71, and 80 to 81 of one codeword at least also satisfy Feature 3, and the DMRS configurations of the row indices 9, 20 to 21, 58 to 69, and 72 to 79 at least also satisfy Feature 4.

[0158] In addition, for individual rows in a single-codeword part, such as the DMRS configuration with a row index of 21, it satisfies the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship. For other DMRS configurations applicable to MU scheduling with multi-TPR, it is preferentially assumed that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship. Therefore, the rows with indexes 9, 20 to 22, and 58 to 81 conform to feature 6, and the rows with indexes 9, 20, 22, and 58 to 81 also conform to feature 5. Optionally, similar to Table 3, the DMRS configuration with a row index of 21 in a single-codeword part cannot be used in the multi-TRP scenario, and DMRS configurations with indexes 62 and 63 are added. At this time, the terminal device assumes that in the multi-TRP scenario, CDM group 0 and CDM group 1 are non-QCL. Or the DMRS configurations with row indexes 62 and 63 can also be not retained. At this time, the row with index 21 can be used in the multi-TRP, and the terminal device assumes that in the DMRS configuration with row index 21, CDM group 1 and CDM group 2 are non-QCL.

[0159] Similar to the foregoing table, the DMRS configurations with row indexes 6 to 8, 10 to 16, and 18 to 35 in the two-codeword part of Table 4 conform to feature 1 and feature 2, and can be applicable to the MU scheduling scenario with multi-TPR. Further, they also conform to feature 7. Among them, the DMRS configurations with indexes 9, 14, 24, 25, 34, and 35 also conform to feature 3, and the DMRS configurations with indexes 6 to 8, 10 to 13, 15, 16, 18 to 23, and 26 to 33 also conform to feature 4. The DMRS configurations with row indexes 1 to 5 are applicable to the single-TPR scenario; the DMRS configurations with row indexes 0, 9, 17, and 36 to 39 are applicable to the SU scheduling scenario with multi-TPR.

[0160] In addition, for individual rows in the two-codeword part, such as the DMRS configuration with a row index of 13, it satisfies the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship. For other DMRS configurations applicable to MU scheduling with multi-TPR, it is preferentially assumed that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship. Therefore, the rows with indexes 6 to 8, 10 to 16, and 18 to 35 conform to feature 6, and the rows with indexes 6 to 8, 10 to 12, 14 to 16, and 18 to 35 also conform to feature 5. Similar to the foregoing, the rows with indexes 15 and 16 can be retained, and it is assumed that the row with index 13 cannot be used in the multi-TRP. At this time, in the table, both CDM group 0 and CDM group 1 are non-QCL.

[0161] In the implementation of this application, the DMRS configuration is extended to the DMRS configuration schemes in more scenarios such as the MU scheduling of multi-TRP described above, reducing the limitations of the DMRS configuration.

[0162] Above, the method provided by the embodiments of this application has been described in detail in combination with Figure 3 and Tables 1 to 4. Next, the communication device provided by the embodiments of this application will be described in detail in combination with Figures 4 to 6

[0163] Figure 4 is a schematic block diagram of the communication device provided by the embodiments of this application. As shown in the figure, the communication device 1000 may include a communication unit 1100 and a processing unit 1200.

[0164] In a possible design, the communication device 1000 may correspond to the terminal device in the above method embodiments. For example, it may be a terminal device or a chip configured in a terminal device.

[0165] Specifically, the communication device 1000 may correspond to the terminal device in Method 300 according to the embodiments of this application. The communication device 1000 may include units for performing Figure 3 the method executed by the terminal device in Method 300. Moreover, each unit in the communication device 1000 and the above other operations and / or functions respectively are for implementing Figure 3 the corresponding processes of Method 300.

[0166] Among them, when the communication device 1000 is used to execute Figure 3 Method 300, the communication unit 1100 may be used to execute step 320 in Method 300, and the processing unit 1200 may be used to execute step 330 in Method 300.

[0167] It should be understood that the specific processes of each unit executing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be repeated here.

[0168] It should also be understood that when the communication device 1000 is a terminal device, the communication unit 1100 in the communication device 1000 may correspond to Figure 5 the transceiver 2020 in the terminal device 2000 shown in Figure 5 , and the processing unit 1200 in the communication device 1000 may correspond to

[0169] the processor 2010 in the terminal device 2000 shown in

[0170] ​In another possible design, the communication device 1000 may correspond to the network device in the above method embodiments. For example, it may be a network device or a chip configured in a network device.

[0171] Specifically, the communication device 1000 may correspond to the network device in the method 300 according to the embodiments of the present application. The communication device 1000 may include units for performing Figure 3 the methods performed by the network device in the method 300. Moreover, each unit in the communication device 1000 and the above other operations and / or functions respectively serve to implement Figure 3 the corresponding processes of the method 300 in

[0172] Among them, when the communication device 1000 is used to perform Figure 3 the method 300 in

[0173] the communication unit 1100 may be used to perform step 320 in the method 300, and the processing unit 1200 may be used to perform step 310 in the method 300.

[0174] It should be understood that the specific processes of each unit performing the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here. Figure 6 Figure 6 Figure 6 It should also be understood that when the communication device 1000 is a network device, the communication unit in the communication device 1000 may correspond to the transceiver 3200 in the network device 3000 shown in

[0175] The processing unit 1200 in the communication device 1000 may correspond to the processor 3202 in the network device 3000 shown in

[0176] Figure 5 is a schematic structural diagram of the terminal device 2000 provided by the embodiments of the present application. The terminal device 2000 may be applied to a system as shown in Figure 2 and perform the functions of the terminal device in the above method embodiments.

[0177] As shown in the figure, 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 path to transmit control and / or data signals. The memory 2030 is used to store computer programs, and the processor 2010 is used to call and run the computer programs from the memory 2030 to control the transceiver 2020 to transmit and receive signals. Optionally, the terminal device 2000 may further include an antenna 2040, which is used to send the uplink data or uplink control signaling output by the transceiver 2020 through wireless signals.

[0178] The above-mentioned processor 2010 and the memory 2030 can be integrated into a processing device. The processor 2010 is used to execute the program code stored in the memory 2030 to implement the above functions. Specifically, in implementation, the memory 2030 can also be integrated in the processor 2010 or independent of the processor 2010. The processor 2010 can correspond to Figure 4 the processing unit in.

[0179] The above-mentioned transceiver 2020 can correspond to Figure 4 the communication unit in, and can also be referred to as a transceiver unit. The transceiver 2020 can include a receiver (or called a receiver, receiving circuit) and a transmitter (or called a transmitter, transmitting circuit). Among them, the receiver is used to receive signals, and the transmitter is used to transmit signals.

[0180] It should be understood that Figure 5 the terminal device 2000 shown can implement Figure 3 each process related to the terminal device in the method embodiment shown. The operations and / or functions of each module in the terminal device 2000 are respectively for implementing the corresponding processes in the above method embodiment. Specifically, reference can be made to the description in the above method embodiment. To avoid repetition, the detailed description is appropriately omitted here.

[0181] The above-mentioned processor 2010 can be used to execute the actions implemented internally by the terminal device described in the previous method embodiment, and the transceiver 2020 can be used to execute the actions of the terminal device sending to or receiving from the network device described in the previous method embodiment. For specific details, please refer to the description in the previous method embodiment, and details are not repeated here.

[0182] Optionally, the above-mentioned terminal device 2000 may further include a power supply 2050, which is used to supply power to various devices or circuits in the terminal device.

[0183] In addition, in order to make the functions of the terminal device more complete, 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, and a sensor 2100. The audio circuit may further include a speaker 2082, a microphone 2084, etc.

[0184] Figure 6 FIG. is a schematic structural diagram of a network device provided by an embodiment of the present application, for example, it may be a schematic structural diagram of a base station. The base station 3000 can be applied to a system as shown in Figure 2 and execute the functions of the network device in the above method embodiment.

[0185] As shown in the figure, the base station 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3102 and one or more baseband units (BBUs) (which may also be referred to as digital units, DUs) 3200. The RRU 3102 may be referred to as a transceiver unit, corresponding to the communication unit 1100 in Figure 4 . Optionally, the transceiver unit 3100 may also be referred to as a transceiver, a transceiver circuit, or a transceiver, etc. It may include at least one antenna 3101 and a radio frequency unit 3102. Optionally, the transceiver unit 3100 may include a receiving unit and a transmitting unit. The receiving unit may correspond to a receiver (or a receiver circuit), and the transmitting unit may correspond to a transmitter (or a transmitter circuit). The RRU 3102 part is mainly used for the transceiver of radio frequency signals and the conversion between radio frequency signals and baseband signals, for example, for sending indication information to the terminal device. The BBU 3200 part is mainly used for baseband processing and controlling the base station, etc. The RRU 3102 and the BBU 3200 may be physically set together or physically separated, that is, a distributed base station.

[0186] The BBU 3200 is the control center of the base station and may also be referred to as a processing unit, corresponding to the processing unit 1200 in Figure 4 . It is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, etc. For example, the BBU (processing unit) may be used to control the base station to execute the operation process of the network device in the above method embodiment, for example, generating the above indication information, etc.

[0187] In one example, the BBU 3200 may be composed of one or more single boards. The multiple single boards may jointly support a radio access network of a single access mode (such as an LTE network), or may separately support radio access networks of different access modes (such as an LTE network, a 5G network, or other networks). The BBU 3200 further 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 operations, for example, to control the base station to execute the operation processes of the network device in the above method embodiments. The memory 3201 and the processor 3202 may serve one or more single boards. That is to say, a memory and a processor may be separately provided on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board.

[0188] It should be understood that Figure 6 the shown base station 3000 can implement Figure 3 each process related to the network device in the method embodiment. The operations and / or functions of each module in the base station 3000 are respectively for implementing the corresponding processes in the above method embodiment. For details, reference may be made to the description in the above method embodiment. To avoid repetition, the detailed description is appropriately omitted here.

[0189] The above BBU 3200 may be used to execute the actions implemented inside the network device described in the previous method embodiment, and the RRU 3102 may be used to execute the actions of the network device sending to or receiving from the terminal device described in the previous method embodiment. For details, please refer to the description in the previous method embodiment, which will not be repeated here.

[0190] An embodiment of the present application further provides a processing device, including a processor and an interface; the processor is used to execute the communication method in the above method embodiment.

[0191] 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), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0192] In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by the hardware processor, or executed and completed by the combination of the hardware and software modules in the processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read only memory, a programmable read only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method. To avoid repetition, it will not be described in detail here.

[0193] It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the above method embodiments can be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above-mentioned 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 gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or 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 a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0194] It can be understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include but not be limited to these and any other suitable types of memory.

[0195] According to the method provided by the embodiments of the present application, the present application further provides a computer program product, which includes: computer program code, when the computer program code runs on a computer, it causes the computer to execute Figures 2 - 4 the method of any one of the embodiments shown.

[0196] According to the method provided by the embodiments of the present application, the present application further provides a computer-readable medium, which stores program code, when the program code runs on a computer, it causes the computer to execute Figures 2 - 4 the method of any one of the embodiments shown.

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

[0198] 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 a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a high-density digital video disc (DVD)), or a semiconductor medium (such as a solid state disc (SSD)), etc.

[0199] In each of the above device embodiments, the network device corresponds exactly to the network device or terminal device in the method embodiments. The corresponding steps are executed by the corresponding modules or units. For example, the communication unit (transceiver) executes the steps of receiving or sending in the method embodiments, and the other steps except for sending and receiving can be executed by the processing unit (processor). The functions of the specific units can be referred to the corresponding method embodiments. Among them, the processor can be one or more.

[0200] As used in this specification, the terms "component", "module", "system", etc. are used to denote computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component can 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 an application running on a computing device and the computing device can be components. One or more components can reside in a process and / or an execution thread, and the components can be located on one computer and / or distributed between two or more computers. In addition, these components can execute from various computer-readable media on which various data structures are stored. The components can communicate, for example, through local and / or remote processes according to signals having one or more data packets (such as data from two components interacting with each other between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems through signals).

[0201] Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in 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 and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0202] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described systems, devices, and units can be referred to the corresponding processes in the foregoing method embodiments, and will not be described herein again.

[0203] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

[0205] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0206] In the above embodiments, the functions of the functional units 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 (programs). When the computer program instructions (programs) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server or data center that contains one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0207] When the above-mentioned 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 this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art or a part of this technical solution can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0208] As described above, the above are only specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed by this application can easily think of changes or substitutions, which should all be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A method for receiving an indication, characterized in that, comprising: receiving type indication information of a demodulation reference signal (DMRS) pattern type; receiving indication information, which is generated according to a DMRS port configuration table corresponding to the DMRS pattern type, the DMRS port configuration table including multiple rows of DMRS configurations, each row of the DMRS configurations including a configuration item of a DMRS port and a configuration item of the number of code division multiplexing (CDM) antenna port groups of DMRS not used for data transmission, the indication information being used to indicate the DMRS port configured for a terminal device and the number of CDM antenna port groups of DMRS not used for data transmission; determining the DMRS port and the number of CDM antenna port groups of DMRS not used for data transmission according to the indication information; wherein, among the multiple rows of DMRS configurations, there is one or more rows of DMRS configurations applicable to multi-user scheduling, and the number of CDM antenna port groups of DMRS not used for data transmission configured in the configuration item of the number of CDM antenna port groups of DMRS not used for data transmission in the one or more rows of DMRS configurations is greater than or equal to 2, and the DMRS port configured in the configuration item of the DMRS port in the one or more rows of DMRS configurations comes from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups.

2. The method according to claim 1, characterized in that, among the one or more rows of DMRS configurations applicable to multi-user scheduling, there is at least one row of DMRS configuration, and the DMRS port configured in the configuration item of the DMRS port included in the at least one row of DMRS configuration matches the maximum number of transmission layers in multi-user scheduling for one terminal device under the DMRS pattern type; and / or, among the one or more rows of DMRS configurations applicable to multi-user scheduling, there is at least one row of DMRS configuration, and the DMRS port configured in the configuration item of the DMRS port included in the at least one row of DMRS configuration matches the number of transmission layers less than the maximum number of transmission layers in multi-user scheduling for one terminal device under the DMRS pattern type.

3. The method according to claim 1 or 2, characterized in that, the DMRS pattern type includes at least one of the following: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, pattern type 2 with a maximum of 2 symbols.

4. The method according to claim 3, characterized in that, in the one or more rows of DMRS configurations applicable to multi-user scheduling in the DMRS port configuration table corresponding to at least one type included in the DMRS pattern type, the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship is satisfied.

5. The method according to claim 3, characterized in that, Under the pattern type 2 with a maximum of 1 symbol, or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one or more rows of DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi - co - location relationship, and includes one or more rows of DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi - co - location relationship.

6. The method according to any one of claims 1 - 2, 4 - 5, wherein, the one or more rows of DMRS configurations applicable to multi - user scheduling are used for transmitting corresponding to one codeword transmission with a layer number from 2 to 4 layers, and / or transmitting corresponding to two codeword transmissions with a layer number from 2 to 4 layers.

7. A method for sending an indication, wherein, comprises: generating indication information according to a DMRS port configuration table corresponding to a demodulation reference signal DMRS pattern type; the DMRS port configuration table includes multiple rows of DMRS configurations, each row of the DMRS configurations includes a configuration item of DMRS ports and a configuration item of the number of code - division multiplexing CDM antenna port groups of DMRS not used for data transmission, and the indication information is used to indicate the DMRS ports configured for the terminal device and the number of CDM antenna port groups of DMRS not used for data transmission; sending the indication information; wherein, among the multiple rows of DMRS configurations, there is one or more rows of DMRS configurations applicable to multi - user scheduling, the configuration item of the number of CDM antenna port groups of DMRS not used for data transmission configured in the one or more rows of DMRS configurations is greater than or equal to 2, the DMRS ports configured by the configuration item of DMRS ports come from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi - co - location relationship with other CDM antenna port groups; before sending the indication information, the method further comprises: sending type indication information of the DMRS pattern type.

8. The method according to claim 7, wherein, among the one or more rows of DMRS configurations applicable to multi - user scheduling, there is at least one row of DMRS configuration, and the DMRS ports configured by the configuration item of DMRS ports included in the at least one row of DMRS configuration match the maximum transmission layer number of a terminal device in multi - user scheduling under the DMRS pattern type; and / or, among the one or more rows of DMRS configurations applicable to multi - user scheduling, there is at least one row of DMRS configuration, and the DMRS ports configured by the configuration item of DMRS ports included in the at least one row of DMRS configuration match the transmission layer number less than the maximum transmission layer number of a terminal device in multi - user scheduling under the DMRS pattern type.

9. The method according to claim 7 or 8, wherein, The DMRS pattern type includes at least one of the following: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols.

10. The method according to claim 9, wherein, one or more lines of DMRS configurations applicable to multi-user scheduling in the DMRS port configuration table corresponding to at least one of the types included in the DMRS pattern type satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship.

11. The method according to claim 9, wherein, under the pattern type 2 with a maximum of 1 symbol or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one or more lines of DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship, and includes one or more lines of DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship.

12. The method according to any one of claims 7-8, 10-11, wherein, the one or more lines of DMRS configurations applicable to multi-user scheduling are used for transmitting one codeword corresponding to 2 to 4 layers, and / or transmitting two codewords corresponding to 2 to 4 layers.

13. A device for receiving an indication, wherein, comprising: a communication unit, configured to receive type indication information of a demodulation reference signal DMRS pattern type; and receiving indication information, the indication information being generated according to a DMRS port configuration table corresponding to the DMRS pattern type, the DMRS port configuration table including multiple lines of DMRS configurations, each line of the DMRS configurations including a configuration item of a DMRS port and a configuration item of the number of code division multiplexing CDM antenna port groups of the DMRS not used for data transmission, the indication information being used to indicate the DMRS ports configured for a terminal device and the number of CDM antenna port groups of the DMRS not used for data transmission; a processing unit, configured to determine the DMRS ports and the number of CDM antenna port groups of the DMRS not used for data transmission according to the indication information; wherein, one or more lines of DMRS configurations applicable to multi-user scheduling are included in the multiple lines of DMRS configurations, the number of CDM antenna port groups of the DMRS not used for data transmission configured in the configuration item of the number of CDM antenna port groups of the DMRS not used for data transmission in the one or more lines of DMRS configurations is greater than or equal to 2, the DMRS ports configured in the configuration item of the DMRS ports come from at least two of the CDM antenna port groups, and at least one of the CDM antenna port groups with the number greater than or equal to 2 does not have a quasi-co-location relationship with other CDM antenna port groups.

14. The device according to claim 13, wherein, One or more DMRS configurations applicable to multi-user scheduling include at least one DMRS configuration, and the DMRS ports configured by the configuration items of the DMRS ports included in the at least one DMRS configuration match the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type; and / or, One or more DMRS configurations applicable to multi-user scheduling include at least one DMRS configuration, and the DMRS ports configured by the configuration items of the DMRS ports included in the at least one DMRS configuration match the number of transmission layers less than the maximum number of transmission layers for a terminal device in multi-user scheduling under the DMRS pattern type.

15. The apparatus according to claim 13 or 14, wherein, The DMRS pattern type includes at least one of the following: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, pattern type 2 with a maximum of 2 symbols.

16. The apparatus according to claim 15, wherein, One or more DMRS configurations applicable to multi-user scheduling included in the DMRS port configuration table corresponding to at least one of the types included in the DMRS pattern type satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship.

17. The apparatus according to claim 15, wherein, Under the pattern type 2 with a maximum of 1 symbol or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one or more DMRS configurations that satisfy the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship, and includes one or more DMRS configurations that satisfy the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship.

18. The apparatus according to any one of claims 13-14, 16-17, wherein, One or more DMRS configurations applicable to multi-user scheduling are used for one-codeword transmission corresponding to 2 to 4 transmission layers, and / or two-codeword transmission corresponding to 2 to 4 transmission layers.

19. A device for sending an indication, wherein, comprising: a processing unit for generating indication information according to a DMRS port configuration table corresponding to a demodulation reference signal DMRS pattern type; The DMRS port configuration table includes multiple DMRS configurations, each of the DMRS configurations includes a configuration item of a DMRS port and a configuration item of the number of code division multiplexing CDM antenna port groups of DMRS not used for data transmission, and the indication information is used to indicate the DMRS ports configured for the terminal device and the number of CDM antenna port groups of DMRS not used for data transmission; a communication unit for sending the indication information; Among them, in the multiple-row DMRS configuration, there is one or more rows of DMRS configuration applicable to multi-user scheduling. In the one or more rows of DMRS configuration, the number of CDM antenna port groups of the DMRS not used for data transmission configured in the configuration item of the number of CDM antenna port groups of the DMRS not used for data transmission is greater than or equal to 2. The DMRS ports configured in the configuration item of the DMRS ports come from at least two of the CDM antenna port groups. Among the CDM antenna port groups with the number greater than or equal to 2, at least one CDM antenna port group does not have a quasi-co-location relationship with other CDM antenna port groups; The communication unit is further configured to send type indication information of the DMRS pattern type before sending the indication information.

20. The apparatus according to claim 19, wherein, in the one or more rows of DMRS configuration applicable to multi-user scheduling, there is at least one row of DMRS configuration. The DMRS ports configured in the configuration item of the DMRS ports included in the at least one row of DMRS configuration match the maximum number of transmission layers in multi-user scheduling for one terminal device under the DMRS pattern type; and / or, in the one or more rows of DMRS configuration applicable to multi-user scheduling, there is at least one row of DMRS configuration. The DMRS ports configured in the configuration item of the DMRS ports included in the at least one row of DMRS configuration match the number of transmission layers less than the maximum number of transmission layers in multi-user scheduling for one terminal device under the DMRS pattern type.

21. The apparatus according to claim 19 or 20, wherein, the DMRS pattern type includes at least one of the following: pattern type 1 with a maximum of 1 symbol, pattern type 1 with a maximum of 2 symbols, pattern type 2 with a maximum of 1 symbol, and pattern type 2 with a maximum of 2 symbols.

22. The apparatus according to claim 21, wherein, in the one or more rows of DMRS configuration applicable to multi-user scheduling in the DMRS port configuration table corresponding to at least one type included in the DMRS pattern type, the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship is satisfied.

23. The apparatus according to claim 21, wherein, under the pattern type 2 with a maximum of 1 symbol or under the pattern type 2 with a maximum of 2 symbols, the DMRS port configuration table includes one or more rows of DMRS configuration satisfying the assumption that CDM antenna port group 0 and CDM antenna port group 1 do not have a quasi-co-location relationship, and includes one or more rows of DMRS configuration satisfying the assumption that CDM antenna port group 1 and CDM antenna port group 2 do not have a quasi-co-location relationship.

24. The apparatus according to any one of claims 19-20, 22-23, wherein, the one or more rows of DMRS configuration applicable to multi-user scheduling are used for one-codeword transmission corresponding to 2 to 4 transmission layers, and / or two-codeword transmission corresponding to 2 to 4 transmission layers.

25. A communication apparatus, wherein, comprising at least one processor, the at least one processor being configured to control a communication interface to implement the method according to any one of claims 1 to 12.

26. A communication device, characterized in that it comprises a processor and a memory, the processor being configured to read instructions stored in the memory and control a communication interface to implement the method according to any one of claims 1 to 12.

27. A communication system, characterized in that it comprises a means for receiving an indication according to any one of claims 13 - 18 and a means for transmitting an indication according to any one of claims 19 - 24.

28. A computer - readable medium, characterized in that it comprises a computer program which, when run on a computer, causes the computer to execute the method according to any one of claims 1 to 12.

29. A processor, characterized in that it comprises: an input circuit, an output circuit and a processing circuit, the processing circuit being configured to receive a signal through the input circuit and transmit a signal through the output circuit, such that the processor executes the method according to any one of claims 1 to 12.

30. A processing device, characterized in that it comprises: a processor and a memory, the processor being configured to read instructions stored in the memory and receive a signal through a receiver and transmit a signal through a transmitter to implement the method according to any one of claims 1 to 12.

31. A computer program product, characterized in that when the computer program product is run on a computer, it causes the computer to execute the method according to any one of claims 1 to 12.

Images