Method for transmitting and receiving demodulation reference signal and communication device

By mapping and configuring DMRS port sets at different time-domain locations in the new wireless communication, the need to increase system capacity was addressed, and compatibility with existing terminal equipment and system capacity improvement were achieved.

CN116648872BActive Publication Date: 2025-10-28HUAWEI TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202080107136.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-31
Publication Date
2025-10-28
Estimated Expiration
2040-12-31

AI Technical Summary

Technical Problem

In new wireless communications, how can we support more orthogonal DMRS ports without increasing system overhead to improve system capacity?

Method used

By mapping different DMRS port sets at different time domain locations and configuring these port sets within scheduling time units, the transmission of DMRS ports can be controlled using predefined rules, supporting more DMRS ports without increasing system overhead.

Benefits of technology

It enables support for more DMRS ports without increasing system overhead, thereby improving system capacity and ensuring compatibility with existing terminal devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116648872B_ABST
    Figure CN116648872B_ABST
Patent Text Reader

Abstract

This application provides a method for transmitting DMRS, a method for receiving DMRS, and a communication apparatus, comprising: receiving indication information for indicating a scheduled DMRS port, and transmitting DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position and a second time domain position, and the first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position. Thus, by mapping different DMRS port sets to the first and second time domain positions respectively, more orthogonal DMRS ports can be supported, improving system capacity.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a method for transmitting a demodulation reference signal (DMRS), a method for receiving DMRS, and a communication apparatus. Background Technology

[0002] In new radio (NR), DMRS is used for data channels, such as demodulation of the physical uplink share channel (PUSCH). The more orthogonal DMRS ports supported in the uplink transmission, the more spatial layers can be used for parallel transmission, resulting in greater system capacity. However, increasing the number of DMRS ports also requires consideration of system overhead. How to support more orthogonal DMRS ports with minimal or no increase in system overhead has become a pressing issue for improving system capacity. Summary of the Invention

[0003] This application provides a method for transmitting DMRS, a method for receiving DMRS, and a communication device that can support more orthogonal DMRS ports and improve system capacity.

[0004] In a first aspect, a method for transmitting DMRS is provided. This method can be executed by a transmitting device (such as a terminal device), or by a chip or circuit configured in the transmitting device, which is not limited in this application.

[0005] The method includes: receiving indication information, which indicates a scheduled DMRS port; and transmitting DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports. These M DMRS ports correspond to a first time-domain location and a second time-domain location. The first DMRS port set corresponding to the first time-domain location is different from the second DMRS port set corresponding to the second time-domain location.

[0006] Secondly, a method for receiving DMRS is provided. This method can be performed by a receiving device (such as a network device), or by a chip or circuit configured in the receiving device, which is not limited in this application.

[0007] The method includes: sending indication information to indicate a scheduled DMRS port; and receiving DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to a first time-domain location and a second time-domain location. The first DMRS port set corresponding to the first time-domain location is different from the second DMRS port set corresponding to the second time-domain location.

[0008] Thirdly, a method for receiving DMRS is provided, which can be executed by a receiving device (such as a terminal device), or by a chip or circuit configured in the receiving device, and this application does not limit the method thereto.

[0009] The method includes: receiving indication information, which indicates a scheduled DMRS port; and receiving DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports. These M DMRS ports correspond to a first time-domain location and a second time-domain location. The first DMRS port set corresponding to the first time-domain location is different from the second DMRS port set corresponding to the second time-domain location.

[0010] Fourthly, a method for transmitting DMRS is provided, which can be executed by a transmitting device (such as a network device), or by a chip or circuit configured in the transmitting device, and this application does not limit the method thereto.

[0011] The method includes: sending indication information, which indicates a scheduled DMRS port; and sending DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports. These M DMRS ports correspond to a first time domain location and a second time domain location. The first DMRS port set corresponding to the first time domain location is different from the second DMRS port set corresponding to the second time domain location.

[0012] In one possible implementation, combining any one of the first to fourth aspects, M is an integer greater than 12.

[0013] It should be understood that, for any of the above aspects, the first time-domain position and the second time-domain position may be contiguous or discontinuous in the time domain. The number of symbols occupied (or corresponding to) the first time-domain position and the second time-domain position may be equal or unequal. For example, both the first and second time-domain positions may occupy 2 symbols, or the first time-domain position may occupy 1 symbol and the second time-domain position may occupy 2 symbols. Furthermore, the number of DMRS ports contained in the first DMRS port set and the number of DMRS ports contained in the second DMRS port set may be equal or unequal.

[0014] The solution provided in this application can map different DMRS port sets at the first time domain location and the second time domain location (i.e., the first DMRS port set and the second DMRS port set). Compared to mapping the same DMRS port set (including a maximum of 12 DMRS ports) at two time domain locations (front-loaded DMRS symbols and additional DMRS symbols), it can support more DMRS ports. For example, the first time domain location can map DMRS ports mapped by the front-loaded DMRS symbols in the current protocol, and the second time domain location can map DMRS ports that are different from the DMRS ports mapped by the front-loaded DMRS symbols in the current protocol. That is, the first time domain location can map DMRS ports in the current protocol, and the second time domain location can map DMRS ports added compared to the current protocol.

[0015] Furthermore, the front DMRS symbol can be 1 or 2 symbols, and the first time domain position and the second time domain position can also occupy 1 or 2 symbols respectively. Therefore, the method provided in this application can control system overhead while supporting more DMRS ports.

[0016] In conjunction with any of the first to fourth aspects, in one possible implementation, the first DMRS port set and the second DMRS port set contain some DMRS ports that are the same and some that are different, or the first DMRS port set and the second DMRS port set contain all different DMRS ports.

[0017] In one possible implementation, combining any one of the first to fourth aspects, the first time-domain position and the second time-domain position are located within the same scheduling time unit. In other words, the first time-domain position and the second time-domain position correspond to the same scheduling time unit.

[0018] In one possible implementation, in conjunction with any of the first to fourth aspects, a first time-domain position is used to transmit front-loaded DMRS, and / or a second time-domain position is used to transmit additional DMRS.

[0019] This means that the first time domain position is the same as the position of the preceding DMRS symbol, and / or the second time domain position is the same as the position of the additional DMRS symbol.

[0020] Therefore, the first time-domain position can be configured in the same way as configuring a preceding DMRS symbol, and / or the second time-domain position can be configured in the same way as configuring an additional DMRS symbol. Thus, the first time-domain position can be configured without modifying the preceding DMRS symbol configuration in the current protocol, and the second time-domain position can be configured without modifying the configuration of additional DMRS symbols in the current protocol.

[0021] In the current protocol, each time slot can be configured with a pre-signed DMRS symbol, and the position of the pre-signed DMRS symbol corresponds to DMRS ports 0 to 11. Existing terminal devices can transmit DMRS corresponding to one or more DMRS ports from DMRS ports 0 to 11 on the pre-signed DMRS symbol. In this application, the scheduling time unit can be a time slot, and each time slot can be configured with a first time domain position and a second time domain position. The first time domain position can be the pre-signed DMRS symbol, and the second time domain position can be an additional DMRS symbol. If an existing terminal device transmits the DMRS transmitted on the pre-signed DMRS symbol at the second time domain position, then the existing terminal device can be compatible with the terminal device provided in this application, that is, the existing terminal device and the terminal device provided in this application can perform paired transmission.

[0022] In one possible implementation, combining any one of the first to fourth aspects, the first time-domain position and the second time-domain position are located within different scheduling time units. Alternatively, the first time-domain position and the second time-domain position can correspond to different scheduling time units.

[0023] This scheme can carry DMRS on different DMRS ports in different scheduling time units, which can reduce DMRS overhead compared to carrying DMRS on all DMRS ports in the same scheduling time unit.

[0024] In one possible implementation, combining any one of the first to fourth aspects, both the first time domain position and the second time domain position are used to transmit the pre-DMRS.

[0025] In one possible implementation, combining any one of the first to fourth aspects, the configuration and / or scheduling time units of the first DMRS port set and / or the second DMRS port set satisfy predefined rules.

[0026] In one possible implementation, the predefined rule is: scheduling time units that satisfy mod(m,N)=1 are configured only for the first DMRS port set, and / or scheduling time units that satisfy mod(m,N)=0 are configured only for the second DMRS port set.

[0027] Wherein, corresponding to the first and second aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH. Corresponding to the third and fourth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH.

[0028] Furthermore, in one possible implementation, N is configured or predefined by the system.

[0029] Furthermore, in one possible implementation, N is the number of scheduling time units corresponding to the scheduled PUSCH (or PDSCH). Alternatively, N is the number of time slots contained in a radio frame with a length of 10ms.

[0030] Furthermore, in one possible implementation, N=2.

[0031] It is understandable that the larger the value of N, the sparser the DMRS transmission, that is, the fewer symbols are used to transmit DMRS, which can reduce overhead.

[0032] It should be understood that in this application, when m represents the m-th scheduling time unit among multiple scheduling time units corresponding to the scheduled PUSCH (or PDSCH), m = 1, 2, ..., that is, the value of m starts from 1.

[0033] It should also be understood that, in this application, configuring a first DMRS port set for a scheduling time unit means that the scheduling time unit configures a first time domain position or a symbol corresponding to the first time domain position, or configures DMRS ports included in the first DMRS port set. If a scheduling time unit configures a first DMRS port set, then it can send or receive DMRS ports in the first DMRS port set within that scheduling time unit. If a scheduling time unit does not configure a first DMRS port set, then it cannot send or receive DMRS ports in the first DMRS port set within that scheduling time unit.

[0034] Similarly, a scheduling time unit configured with a second DMRS port set means that the scheduling time unit has configured a second time domain location, a symbol corresponding to the second time domain location, or DMRS ports included in the second DMRS port set. If a scheduling time unit has a second DMRS port set configured, then DMRS ports in the second DMRS port set can be transmitted or received within that scheduling time unit. If a scheduling time unit has not a second DMRS port set configured, then DMRS ports in the second DMRS port set cannot be transmitted or received within that scheduling time unit.

[0035] In one possible implementation, the predefined rule is: scheduling time units satisfying mod(m,N)=0 are configured only with the first DMRS port set, and / or scheduling time units satisfying mod(m,N)=1 are configured only with the second DMRS port set. Here, m is the index of the scheduling time unit.

[0036] Furthermore, in one possible implementation, N is configured or predefined by the system.

[0037] It should be understood that in this application, when m represents the index of the scheduling time unit, m = 0, 1, 2, ..., but this application does not limit this. For example, m = 1, 2, 3, ..., that is, the value of m can also start from 1.

[0038] In one possible implementation, the predefined rule is: scheduling time units satisfying mod(m,2)=1 are configured only with the first DMRS port set, and / or scheduling time units satisfying mod(m,2)=0 are configured only with the second DMRS port set. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0039] In one possible implementation, the predefined rule is: a scheduling time unit satisfying n+2*k*(P+1) can be configured with only the first DMRS port set, and a scheduling time unit satisfying n+(2*k+1)*(P+1) can be configured with only the second DMRS port set. Here, k = 0, 1, 2, 3, 4, ..., n+2*k*(P+1) and n+(2*k+1)*(P+1) both represent the index of the scheduling time unit, P is an integer greater than or equal to 1, and n is an integer greater than or equal to 0.

[0040] In one possible implementation, the predefined rule is: scheduling time units satisfying mod(m, N) = 1 configure the first DMRS port set and the second DMRS port set. Here, mod() represents the modulo operation, and N is an integer greater than 1. Corresponding to the first and second aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH. Corresponding to the third and fourth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH.

[0041] Furthermore, in one possible implementation, N is configured or predefined by the system.

[0042] In one possible implementation, the predefined rule is: scheduling time units that satisfy mod(m,2)=0 are configured with the first DMRS port set and the second DMRS port set. Here, m is the index of the scheduling time unit.

[0043] In one possible implementation, the predefined rule is: scheduling time units satisfying mod(m,2) = 0 configure the first DMRS port set and the second DMRS port set. Here, corresponding to the first and second aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH. Corresponding to the third and fourth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH.

[0044] In one possible implementation, the predefined rule is: the scheduling time unit that satisfies n+k*(P+1) configures the first DMRS port set and the second DMRS port set, where P is an integer greater than or equal to 1, n+k*(P+1) is the index of the scheduling time unit, k = 0, 1, 2, 3, 4, ..., and n is an integer greater than or equal to 0.

[0045] In conjunction with the first to fourth aspects, in some implementations of the first to fourth aspects, the first DMRS port set includes DMRS ports with indices 0 to 23; and the second DMRS port set includes DMRS ports with indices 0 to 11 and 24 to 35, or the second DMRS port set includes DMRS ports with indices 24 to 35, or the second DMRS port set includes DMRS ports with indices 24 to 47.

[0046] In conjunction with aspects one through four, in some implementations of aspects one through four, the scheduling time unit is a time slot.

[0047] Fifthly, a method for transmitting DMRS is provided, which can be executed by a transmitting device (such as a terminal device), or by a chip or circuit configured in the transmitting device, without limitation thereof.

[0048] The method includes: receiving indication information, which indicates a scheduled DMRS port; and transmitting DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to a first time-domain position, a second time-domain position, and a third time-domain position. Any two DMRS port sets among the first time-domain position's first DMRS port set, the second time-domain position's second DMRS port set, and the third time-domain position's third DMRS port set are different.

[0049] In a sixth aspect, a method for receiving DMRS is provided, which can be performed by a receiving device (such as a network device), or by a chip or circuit configured in the receiving device, without limitation thereof.

[0050] The method includes: sending indication information to indicate a scheduled DMRS port; and receiving DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to a first time-domain position, a second time-domain position, and a third time-domain position. Any two DMRS port sets among the first time-domain position's first DMRS port set, the second time-domain position's second DMRS port set, and the third time-domain position's third DMRS port set are different.

[0051] In a seventh aspect, a method for receiving DMRS is provided. This method can be performed by a receiving device (such as a network device), or by a chip or circuit configured in the receiving device, which is not limited in this application.

[0052] The method includes: receiving indication information, which indicates a scheduled DMRS port; and receiving DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to a first time-domain position, a second time-domain position, and a third time-domain position. Any two DMRS port sets among the first time-domain position's first DMRS port set, the second time-domain position's second DMRS port set, and the third time-domain position's third DMRS port set are different.

[0053] Eighthly, a method for transmitting DMRS is provided, which can be performed by a transmitting device (such as a network device), or by a chip or circuit configured in the transmitting device, without limitation thereof.

[0054] The method includes: sending indication information, which indicates a scheduled DMRS port; and sending DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set containing M DMRS ports, which correspond to a first time-domain position, a second time-domain position, and a third time-domain position. Any two DMRS port sets among the first time-domain position's first DMRS port set, the second time-domain position's second DMRS port set, and the third time-domain position's third DMRS port set are different.

[0055] In one possible implementation, combining any of the fifth to eighth aspects, M is an integer greater than 12.

[0056] It should be understood that, for any of the above aspects, the first, second, and third time-domain positions can be contiguous in the time domain, or at least two of the first, second, and third time-domain positions can be discontinuous in the time domain. The number of symbols occupied (or corresponding to) any two of the first, second, and third time-domain positions can be equal or unequal. For example, the first, second, and third time-domain positions can each occupy 2 symbols. Alternatively, the first and second time-domain positions can each occupy 2 symbols, and the third time-domain position can occupy 1 symbol. Furthermore, the number of DMRS ports contained in any two of the first, second, and third DMRS port sets can be equal or unequal, for example, both containing 12 DMRS ports.

[0057] The solution provided in this application can map different DMRS port sets at the first, second, and third time domain positions (i.e., the first DMRS port set, the second DMRS port set, and the third DMRS port set). Compared to mapping the same DMRS port set (up to 12 DMRS ports) at two time domain positions (prefix DMRS symbols and additional DMRS symbols), it can support more DMRS ports. For example, the first time domain position can map the DMRS ports mapped by the prefix DMRS symbols in the current protocol, while the second and third time domain positions can map DMRS ports that are different from the DMRS ports mapped by the prefix DMRS symbols in the current protocol. That is, the first time domain position can map the DMRS ports in the current protocol, while the second and third time domain positions can map DMRS ports added compared to the current protocol.

[0058] Furthermore, the front-end DMRS symbol can be 1 or 2 symbols, and the first time domain position, the second time domain position, and the third time domain position can each occupy 1 or 2 symbols. Therefore, the method provided in this application can control system overhead while supporting more DMRS ports.

[0059] In a possible implementation, combining any of the fifth to eighth aspects, the first DMRS port set, the second DMRS port set, and the third DMRS port set all contain different DMRS ports.

[0060] In other words, the DMRS ports contained in any two of the first, second, and third DMRS port sets do not overlap.

[0061] In conjunction with any of aspects five through eight, in one possible implementation, the first time-domain position, the second time-domain position, and the third time-domain position are located within the same scheduling time unit. Alternatively, the first time-domain position, the second time-domain position, and the third time-domain position correspond to the same scheduling time unit.

[0062] In conjunction with any of aspects five through eight, in one possible implementation, a first time-domain position is used to transmit the front-loaded DMRS, a second time-domain position is used to transmit the front-loaded DMRS, and / or, a third time-domain position is used to transmit the front-loaded DMRS. This means that the first time-domain position is the same as the front-loaded DMRS symbol position, the second time-domain position is the same as the front-loaded DMRS symbol position, and / or, the third time-domain position is the same as the front-loaded DMRS symbol position.

[0063] Therefore, the first time domain position, the second time domain position, and / or the third time domain position can be configured in the same way as the pre-configured DMRS symbol.

[0064] In conjunction with any one of aspects five through eight, in one possible implementation, any two of the first, second, and third time-domain positions are located within different scheduling time units. Alternatively, any two of the first, second, and third time-domain positions correspond to different scheduling time units.

[0065] This scheme can carry DMRS on different DMRS ports in different scheduling time units, which can reduce DMRS overhead compared to carrying DMRS on all DMRS ports in the same scheduling time unit.

[0066] In one possible implementation, combining any of the fifth to eighth aspects, the first time-domain position, the second time-domain position, and the third time-domain position are all used to transmit the pre-DMRS.

[0067] In conjunction with any of the fifth to eighth aspects, in one possible implementation, the configuration of the first DMRS port set, the configuration of the second DMRS port set, and / or the configuration of the third DMRS port set and the scheduling time units (e.g., time slots) satisfy predefined rules.

[0068] In one possible implementation, the predefined rules include one or more of the following:

[0069] The scheduling time unit that satisfies mod(m,N)=1 is configured only for the first DMRS port set;

[0070] For scheduling time units that satisfy mod(m,N)=2, only the second DMRS port set is configured; or,

[0071] For scheduling time units that satisfy mod(m,N)=3, only the third DMRS port set is configured.

[0072] Where N is a positive integer. Corresponding to the fifth and sixth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; corresponding to the seventh and eighth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH. Alternatively, m is the index of the scheduling time unit.

[0073] Furthermore, in one possible implementation, N is configured or predefined by the system.

[0074] Furthermore, in one possible implementation, N is the number of scheduling time units corresponding to the scheduled PUSCH (or PDSCH).

[0075] Furthermore, in one possible implementation, N is the number of time slots contained in a radio frame with a length of 10ms.

[0076] It is understandable that the larger the value of N, the sparser the DMRS transmission, which can reduce overhead.

[0077] It should be understood that, in this application, configuring a first DMRS port set for a scheduling time unit means that the scheduling time unit configures a first time domain position or a symbol corresponding to the first time domain position, or configures DMRS ports included in the first DMRS port set. If a scheduling time unit configures a first DMRS port set, then it can transmit or receive DMRS ports in the first DMRS port set within that scheduling time unit. If a scheduling time unit does not configure a first DMRS port set, then it cannot transmit or receive DMRS ports in the first DMRS port set within that scheduling time unit.

[0078] Similarly, a scheduling time unit configured with a second DMRS port set means that the scheduling time unit has configured a second time domain position, a symbol corresponding to the second time domain position, or DMRS ports included in the second DMRS port set. If a scheduling time unit has configured a second DMRS port set, then DMRS ports in the second DMRS port set can be transmitted or received within that scheduling time unit. If a scheduling time unit has not configured a second DMRS port set, then DMRS ports in the second DMRS port set cannot be transmitted or received within that scheduling time unit. A scheduling time unit configured with a third DMRS port set means that the scheduling time unit has configured a third time domain position, a symbol corresponding to the third time domain position, or DMRS ports included in the third DMRS port set. If a scheduling time unit has configured a third DMRS port set, then DMRS ports in the third DMRS port set can be transmitted or received within that scheduling time unit. If a scheduling time unit has not configured a third DMRS port set, then DMRS ports in the third DMRS port set cannot be transmitted or received within that scheduling time unit.

[0079] In one possible implementation, the predefined rules include one or more of the following:

[0080] The scheduling time unit that satisfies mod(m,3)=0 is configured only for the first DMRS port set;

[0081] The scheduling time unit that satisfies mod(m,3)=1 is configured only with the second DMRS port set; or,

[0082] The scheduling time unit that satisfies mod(m,3)=2 is configured only for the third DMRS port set.

[0083] In the fifth and sixth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; in the seventh and eighth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH. Alternatively, m is the index of the scheduling time unit.

[0084] In one possible implementation, the predefined rules include one or more of the following:

[0085] The scheduling time unit that satisfies mod(m,3)=1 is configured only for the first DMRS port set;

[0086] The scheduling time unit that satisfies mod(m,3)=2 is configured only with the second DMRS port set; or,

[0087] The scheduling time unit that satisfies mod(m,3)=0 is configured only for the third DMRS port set.

[0088] In the fifth and sixth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; in the seventh and eighth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH. Alternatively, m is the index of the scheduling time unit.

[0089] In one possible implementation, a scheduling time unit satisfying n+2*k*(P+1) can be configured with only the first DMRS port set, a scheduling time unit satisfying n+(2*k+1)*(P+1) can be configured with only the second DMRS port set, and a scheduling time unit satisfying n+(2*k+2)*(P+1) can be configured with only the third DMRS port set, where k = 0, 1, 2, 3, 4, ..., n+2*k*(P+1), n+(2*k+1)*(P+1), and n+(2*k+2)*(P+1) all represent the index of the scheduling time unit, n is an integer greater than or equal to 0, and P is an integer greater than or equal to 1.

[0090] In one possible implementation, the predefined rule could be: configuring the first DMRS port set, the second DMRS port set, and the third DMRS port set with scheduling time units satisfying mod(m,N) = 1. Here, mod() represents the remainder; corresponding to the fifth and sixth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; corresponding to the seventh and eighth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH; and N is an integer greater than 1.

[0091] Furthermore, in one possible implementation, N is configured or predefined by the system.

[0092] In one possible implementation, the predefined rule is: scheduling time units that satisfy mod(m,2)=0 are configured with a first DMRS port set, a second DMRS port set, and a third DMRS port set. Here, m is the index of the scheduling time unit.

[0093] In one possible implementation, the predefined rule is: the scheduling time unit that satisfies mod(m,2)=0 configures the first DMRS port set, the second DMRS port set, and the third DMRS port set. Here, corresponding to the fifth and sixth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; corresponding to the seventh and eighth aspects, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PDSCH.

[0094] In conjunction with any of aspects five through eight, in one possible implementation, the first DMRS port set includes DMRS ports with indices 0 to 23; the second DMRS port set includes DMRS ports with indices 24 to 35; and the third DMRS port set includes DMRS ports with indices 36 to 47. Alternatively, the first DMRS port set includes DMRS ports with indices 0 to 11; the second DMRS port set includes DMRS ports with indices 13 to 23; and the third DMRS port set includes DMRS ports with indices 24 to 35. Alternatively, the first DMRS port set includes DMRS ports with indices 0 to 11; the second DMRS port set includes DMRS ports with indices 13 to 23; and the third DMRS port set includes DMRS ports with indices 24 to 47.

[0095] In one possible implementation, combining any of the fifth to eighth aspects, the scheduling time unit is a time slot.

[0096] A ninth aspect provides a communication apparatus comprising modules or units for performing the methods of the first, third, fifth, or seventh aspect, or any of the possible implementations of the first, third, fifth, or seventh aspect.

[0097] In a tenth aspect, a communication apparatus is provided, comprising modules or units for performing the methods of the second, fourth, sixth, or eighth aspect, or any possible implementation of the second, fourth, sixth, or eighth aspect.

[0098] Eleventhly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to cause the communication device to perform the methods of the first, third, fifth, or seventh aspects described above, or any possible implementation of the first, third, fifth, or seventh aspects. Optionally, the communication device further includes a memory. Optionally, the communication device further includes interface circuitry, to which the processor is coupled.

[0099] In a twelfth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to cause the communication device to perform the methods of the second, fourth, sixth, or eighth aspects described above, or any possible implementation of the second, fourth, sixth, or eighth aspects. Optionally, the communication device further includes a memory. Optionally, the communication device further includes interface circuitry, to which the processor is coupled.

[0100] In a thirteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods of the first, third, fifth, or seventh aspects, or any possible implementation thereof.

[0101] In specific implementation, the 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 a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0102] In a fourteenth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods of the second, fourth, sixth, or eighth aspects, or any possible implementation thereof.

[0103] In specific implementation, the 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 a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0104] In a fifteenth aspect, a processing apparatus is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the methods of the first to eighth aspects or any possible implementation thereof.

[0105] The processing device mentioned in the fifteenth aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in a memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0106] In a sixteenth aspect, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods described in or any possible implementation of the first to eighth aspects.

[0107] In a seventeenth aspect, a computer-readable medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods described in the first to eighth aspects or any possible implementation thereof.

[0108] Eighteenth aspect, a communication system is provided, including at least one terminal device and at least one network device, for performing the method in any possible implementation of the first to eighth aspects. Attached Figure Description

[0109] Figure 1 This is a schematic diagram of a communication system provided in an embodiment of this application.

[0110] Figure 2 These are pilot patterns of two configuration types in the current standard.

[0111] Figure 3 This is a schematic flowchart illustrating a method for sending DMRS according to an embodiment of this application.

[0112] Figures 4 to 12 Several examples of time-domain locations provided in embodiments of this application are shown.

[0113] Figures 13 to 25 Several examples of DMRS patterns provided in embodiments of this application are shown.

[0114] Figure 26 This is a schematic flowchart illustrating another method for sending DMRS provided in an embodiment of this application.

[0115] Figure 27 This is a schematic diagram of a communication device provided in an embodiment of this application.

[0116] Figure 28 This is a schematic diagram of a network device provided in an embodiment of this application.

[0117] Figure 29 This is a schematic diagram of a terminal device provided in an embodiment of this application. Detailed Implementation

[0118] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) system, 5th Generation (5G) system, or New Radio (NR), etc.

[0119] In this application, the terminal device can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in a future 5G network, or terminal device in a future evolved public land mobile network (PLMN), etc. This application does not limit the scope of the terminal device to these specific types.

[0120] The network device in the embodiments of this application can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system; it can also be a module or unit that performs some of the functions of a base station, for example, it can be a central unit (CU) or a distributed unit (DU). The embodiments of this application do not limit the specific technology or specific device form used in the network device.

[0121] In this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device that can call and execute a program.

[0122] Furthermore, various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0123] Before introducing the scheme of this application, the following points should be noted:

[0124] (1) The symbol in this application refers to the orthogonal frequency division multiplexing (OFDM) symbol.

[0125] (2) The scheduling time unit in this application can refer to the smallest scheduling unit in the time domain. For example, in a 4G system, the scheduling time unit can be a subframe, and in a 5G system, the scheduling time unit can be a slot or a mini-slot, etc. As the system evolves, the scheduling time unit can also be the smallest scheduling unit in a new system.

[0126] For ease of description, and for example, in the following text, "X" in "scheduling time unit X" represents the index (or number) of the scheduling time unit. That is, "scheduling time unit X" represents the scheduling time unit with index X. For example, scheduling time unit X represents the scheduling time unit with index X within a radio frame (10ms). For instance, assuming the scheduling time unit is a time slot, then time slot 2 represents the time slot with index 2 within a radio frame.

[0127] Similarly, in "symbol X", "X" represents the index of a symbol within a scheduling time unit (such as a time slot). That is, "symbol X" represents the symbol with index X within a scheduling time unit. For example, symbol 0 represents the symbol with index 0 within a scheduling time unit.

[0128] Similarly, in "DMRS port X", "X" represents the index (or DMRS port number) of the DMRS port. That is, "DMRS port X" means the DMRS port with index X. For example, DMRS port 0 means the DMRS port with index 0.

[0129] It should be noted that the index of the scheduling time unit (e.g., the index of a scheduling time unit within a radio frame), the index of a symbol within a scheduling time unit, and the index of the DMRS port can all start from 0, 1, or other numbers, and this application does not impose any limitation on this. For ease of understanding and explanation, this application uses the example of the index of the scheduling time unit, the index of a symbol within a scheduling time unit, and the index of the DMRS port all starting from 0, but this does not constitute any limitation on this application.

[0130] (3) In this application, a resource block refers to 12 consecutive subcarriers in the frequency domain. A resource element refers to one subcarrier in the frequency domain and one symbol in the time domain.

[0131] To facilitate understanding of the embodiments of this application, firstly, in conjunction with Figure 1 The communication system applicable to the embodiments of this application is described in detail.

[0132] Figure 1 A schematic diagram of a communication system applicable to an embodiment of this application is shown. For example... Figure 1As shown, the communication system 100 may include at least one network device (e.g., network device 110) and at least one terminal device (e.g., terminal device 120). Typically, sending information from the network device to the terminal device is called downlink (DL) communication, and sending information from the terminal device to the network device is called uplink (UL) communication. In uplink communication, the terminal device may send a demodulation reference signal to the network device, which is used for PUSCH data demodulation. In downlink communication, the network device may send a demodulation reference signal to the terminal device, which is used for physical downlink shared channel (PDSCH) data demodulation. The demodulation reference signal is called DMRS in the LTE or NR protocol, and may have other names in future protocols. In this application, for ease of explanation, the demodulation reference signal is uniformly referred to as DMRS.

[0133] The following is a brief introduction to the time-frequency domain position of DMRS in the current technology.

[0134] 1. Time Domain Location of DMRS

[0135] Depending on their time-domain location, DMRS can be divided into front-loaded DMRS and additional DMRS. The symbols corresponding to (or occupied by) front-loaded DMRS can be called front-loaded DMRS symbols, and the symbols corresponding to additional DMRS can be called additional DMRS symbols.

[0136] The pre-DMRS can be one or more symbols, and the starting position of a pre-DMRS symbol can be the first symbol within a scheduling time unit or the corresponding symbol of a scheduled PUSCH (or PDSCH), or it can be something other than that. The additional DMRS symbols are one or more symbols following the pre-DMRS symbols, and the last symbol in the pre-DMRS symbols is not contiguous with the first symbol in the additional DMRS symbols. Furthermore, additional DMRS can be omitted, or one or more sets of additional DMRS can be configured, and the pilot pattern of each set of additional DMRS is a repetition of the pre-DMRS, meaning that each set of additional DMRS occupies the same subcarrier and the same number of symbols as the pre-DMRS.

[0137] 2. Frequency domain location of DMRS

[0138] DMRS has two configuration types: Configuration Type 1 and Configuration Type 2, which determine the DMRS's position in the frequency domain. Configuration Type 1 uses a comb structure with an orthogonal cover code (OCC), while Configuration Type 2 uses a frequency division multiplexing (FDM) structure with an OCC. Both Configuration Type 1 and Configuration Type 2 can handle single-symbol and double-symbol scenarios.

[0139] See Figure 2 , Figure 2 Pilot patterns for two configuration types are shown. Figure 2 In this diagram, resource elements (REs) with different filling patterns represent different CDM groups; P0, P1, ..., P11 represent DMRS ports 0 to DMRS ports 11, respectively; the numbers on the horizontal axis represent the index of a symbol within a time slot, and the numbers on the vertical axis represent the index of a subcarrier within a resource block (RB). Figure 2 The DMRS occupancy symbol 0 and occupancy symbols 0 and 1 are just examples. In actual implementation, the DMRS occupancy symbol in a time slot can also be other symbols, such as occupancy symbol 1, or occupancy symbols 1 and 2.

[0140] See Figure 2 In (a), for configuration type 1 of 1 symbol, each CDM group supports a maximum of 2 orthogonal DMRS ports, and 2 CDM groups support a maximum of 4 orthogonal DMRS ports.

[0141] See Figure 2 In (b), for configuration type 1 with 2 symbols, each CDM group supports a maximum of 4 orthogonal DMRS ports, and 2 CDM groups support a maximum of 8 orthogonal DMRS ports.

[0142] See Figure 2 In (c), for configuration type 2 with 1 symbol, each CDM group supports a maximum of 2 orthogonal DMRS ports, and 3 CDM groups support a maximum of 6 orthogonal DMRS ports.

[0143] See Figure 2 In (d), for configuration type 2 with 2 symbols, each CDM group supports a maximum of 4 orthogonal DMRS ports, and 3 CDM groups support a maximum of 12 orthogonal DMRS ports.

[0144] The correspondence between DMRS port index, CDM group and OCC code can be found in Table 1 or Section 6.4.1.1.3 of TS 38.211.

[0145] Table 1

[0146]

[0147] in, Indicates the index of the DMRS port; λ represents the index of the CDM group; Δ represents the subcarrier offset; w f (k') represents the frequency domain OCC, w t (l') represents the frequency domain OCC.

[0148] In current technology, the OCC of the additional DMRS is a duplicate of the OCC of the preceding DMRS, that is, for the same DMRS port, the OCC of the additional DMRS is the same as that of the preceding DMRS.

[0149] As can be seen, the current protocol supports a limited number of orthogonal DMRS ports, with a maximum of 12, which limits system capacity. To improve system capacity, more orthogonal DMRS ports need to be supported.

[0150] In view of this, this application provides a method for transmitting DMRS and a method for receiving DMRS. By mapping different sets of DMRS ports at at least two time-domain locations, more orthogonal DMRS ports can be supported, thereby improving system capacity.

[0151] The technical solution provided in this application can be applied to both downlink and uplink communication. The following description, primarily using downlink communication as an example, details the method provided in this application.

[0152] It should be understood that in describing the corresponding methods, some steps are described with the terminal device (an example of a sending device) as the executing entity, while others are described with the network device (an example of a receiving device) as the executing entity. This is only for the convenience of describing the illustrated methods. The steps executed by the terminal device can also be implemented by components of the terminal device (e.g., chips or circuits), and similarly, the steps executed by the network device can also be implemented by components of the network device (e.g., chips or circuits).

[0153] It should also be understood that in this application, terminal devices and / or network devices may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the various steps may be performed in different orders as presented in the embodiments of this application, and it is not necessary to perform all the operations in the embodiments of this application.

[0154] Figure 3 This is a schematic diagram of a method for transmitting DMRS provided in this application. The following example uses the sending device as the terminal device and the receiving device as the network device. Figure 3 Each step in method 300 is described in detail.

[0155] S310, the network device sends an instruction to the terminal device. Correspondingly, the terminal device receives the instruction from the network device.

[0156] This indication information is used to indicate the scheduled DMRS port, or in other words, it indicates the DMRS port configured on the network device. For example, this indication information can be sent via downlink control information (DCI).

[0157] The scheduled DMRS port belongs to a set of DMRS ports, which includes M DMRS ports. In other words, the scheduled DMRS port is one or more of the M DMRS ports. These M DMRS ports can be the maximum number of DMRS ports supported by the system. For example, M is an integer greater than 12.

[0158] The M DMRS ports can correspond to R time-domain locations, meaning the M DMRS ports can be mapped to R time-domain locations, where R is an integer greater than or equal to 2. For example, the M DMRS ports can be mapped to two or three time-domain locations. Each time-domain location occupies or corresponds to one or more consecutive symbols, and the number of symbols occupied by any two time-domain locations can be equal or unequal. The R time-domain locations can be located within the same scheduling time unit or within different scheduling time units.

[0159] Furthermore, each time-domain location corresponds to a DMRS port set, meaning R time-domain locations correspond to R DMRS port sets. Any two of these R DMRS port sets are different, or in other words, all R DMRS port sets are distinct. Each DMRS port set includes multiple DMRS ports, such as 6, 12, or 24 DMRS ports. The number of DMRS ports contained in any two DMRS port sets can be equal or unequal.

[0160] It should be understood that the DMRS set introduced in this application is only for the convenience of explaining the relationship between DMRS ports corresponding to a time-domain location and DMRS ports corresponding to different time-domain locations. In actual implementation, there may be no concept of a set, but the characteristics of DMRS ports corresponding to a time-domain location, such as the number of DMRS ports or the DMRS time-frequency location pattern, can be referred to the description of the characteristics of the corresponding DMRS set in this application.

[0161] In S320, the terminal device sends DMRS on the scheduled DMRS port. Correspondingly, the network device receives DMRS from the terminal device on the scheduled DMRS port.

[0162] It should be understood that sending (or receiving) DMRS can also be referred to as sending (or receiving) DMRS sequences or sending (or receiving) DMRS ports.

[0163] According to the DMRS transmission method provided in this application, by mapping different DMRS port sets (e.g., a first DMRS port set and a second DMRS port set) at at least two time-domain locations (e.g., a first time-domain location and a second time-domain location), more DMRS ports can be supported compared to mapping the same DMRS port set (including a maximum of 12 DMRS ports) at two time-domain locations (prefix DMRS symbol and additional DMRS symbol). For example, the first time-domain location can map the DMRS ports mapped by the prefix DMRS symbol in the current protocol, and the second time-domain location can map DMRS ports that are different from the DMRS ports mapped by the prefix DMRS symbol in the current protocol. That is, the first time-domain location can map the DMRS ports in the current protocol (e.g., DMRS ports 0 to 11), and the second time-domain location can map DMRS ports newly added compared to the current protocol (e.g., DMRS ports 12 to 23).

[0164] The following provides a detailed description of the R time-domain locations and the R DRMS ​​port sets. It should be understood that the terms used below refer to... Figures 4 to 25 In the diagram, the numbers on the horizontal axis represent the index of a symbol in a time slot, and the numbers on the vertical axis represent the index of a subcarrier in a redox array (RB). Furthermore, these diagrams are illustrated using an example of a time slot containing 14 symbols. In actual implementation, a time slot may contain 12 symbols, but this also applies to this application.

[0165] (I) Explanation of the R time-domain locations.

[0166] Scenario 1:

[0167] The R time-domain locations are located within the same scheduling time unit, meaning they correspond to the same scheduling time unit. For example, if the scheduling time unit is a time slot, the R time-domain locations can be located within the same time slot.

[0168] Among these R time-domain locations, the two time-domain locations that are closest to each other in the time domain can be continuous in the time domain or discontinuous in the time domain.

[0169] Furthermore, this scheme can be applied to conventional scheduling scenarios, that is, scenarios where the scheduled PUSCH corresponds to one scheduling time unit, such as scenarios where the scheduled PUSCH corresponds to one time slot. It should be understood that PUSCH corresponding to one scheduling time unit means that the time-domain resource corresponding to PUSCH contains only one or more symbols in one scheduling time unit.

[0170] The following explanation uses R=2 and R=3 as examples to further illustrate the scheme.

[0171] With R=2, for ease of understanding and explanation, the two time-domain positions corresponding to the M DMRS ports are denoted as the first time-domain position and the second time-domain position, respectively.

[0172] The first time-domain location and the second time-domain location can be located within the same scheduling time unit. For example, the first time-domain location and the second time-domain location can be located within the same time slot.

[0173] It should be understood that the number of symbols occupied by the first time domain position and the second time domain position can be equal or unequal. For example, the first time domain position and the second time domain position can each occupy 2 symbols, or the first time domain position occupies 1 symbol and the second time domain position occupies 2 symbols.

[0174] Optionally, the first time-domain location and the second time-domain location may be discontinuous in the time domain.

[0175] That is, if the first time-domain position is before the second time-domain position in the time domain, then the last symbol corresponding to the first time-domain position can be separated from the first symbol corresponding to the second time-domain position by one or more symbols. If the first time-domain position is after the second time-domain position in the time domain, then the last symbol corresponding to the second time-domain position can be separated from the first symbol corresponding to the first time-domain position by one or more symbols.

[0176] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 4 The first time domain position can occupy symbols 0 and 1 in a time slot (i.e., the first and second symbols), and the second time domain position can occupy symbols 7 and 8 in the same time slot (i.e., the eighth and ninth symbols).

[0177] Optionally, the first time-domain position and the second time-domain position can be continuous in the time domain.

[0178] That is, the first time domain position and the second time domain position can jointly occupy multiple consecutive symbols within a scheduling time unit.

[0179] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 5 The first time-domain position can occupy the first and second symbols in a time slot, and the second time-domain position can occupy the third and fourth symbols in the same time slot. In this case, the first to fourth symbols are consecutive symbols.

[0180] For example, the first time-domain position is used to transmit the pre-DMRS. That is, the first time-domain position can be a pre-DMRS symbol.

[0181] Furthermore, regarding how to configure the first time domain position, one can refer to the configuration of the preceding DMRS symbol in the existing technology.

[0182] For example, the second time-domain location is used to transmit additional DMRS. That is, the second time-domain location can be an additional DMRS symbol.

[0183] Furthermore, regarding how to configure the second time-domain location, reference can be made to the configuration of additional DMRS symbols in existing technologies.

[0184] Since the first time-domain position can be configured by configuring a pre-DMRS symbol, and / or the second time-domain position can be configured by configuring an additional DMRS symbol, the configuration of the first time-domain position does not need to be modified in the current protocol, and the configuration of the second time-domain position does not need to be modified in the current protocol. On the other hand, each time slot in the current protocol can be configured with a pre-DMRS symbol, and the pre-DMRS symbol position corresponds to DMRS ports 0-11. Existing terminal devices can transmit DMRS corresponding to one or more DMRS ports from DMRS ports 0-11 on the pre-DMRS symbol. In this application, the scheduling time unit can be a time slot, and each time slot can be configured with a first time-domain position and a second time-domain position. The first time-domain position can be a pre-DMRS symbol, and the second time-domain position can be an additional DMRS symbol. If an existing terminal device transmits the DMRS transmitted on the pre-DMRS symbol at the second time-domain position, the existing terminal device can be compatible with the terminal device provided in this application, that is, the existing terminal device and the terminal device provided in this application can perform paired transmission.

[0185] With R=3, for ease of understanding and explanation, the three time-domain positions corresponding to the M DMRS ports are denoted as: the first time-domain position, the second time-domain position, and the third time-domain position.

[0186] The first, second, and third time-domain positions can be located within the same scheduling time unit; that is, the first, second, and third time-domain positions can correspond to the same scheduling time unit. For example, if the scheduling time unit is a time slot, the first, second, and third time-domain positions can be located within the same time slot.

[0187] It should be understood that the number of symbols occupied by any two time-domain positions among the first, second, and third time-domain positions can be equal or unequal. For example, the first, second, and third time-domain positions can all occupy 2 symbols; or, the first time-domain position occupies 1 symbol, the second time-domain position occupies 2 symbols, and the third time-domain position occupies 2 symbols; or, the first time-domain position occupies 1 symbol, the second time-domain position occupies 2 symbols, and the third time-domain position occupies 3 symbols.

[0188] Optionally, at least two of the time-domain positions among the first, second, and third time-domain positions may be discontinuous in the time domain.

[0189] For example, only two of the first, second, and third time-domain positions are contiguous in the time domain. For instance, taking a scheduling time unit as a time slot, see [reference needed]. Figure 6 The first time-domain position can occupy symbols 0 and 1 in one time slot, the second time-domain position can occupy symbols 2 and 3 in the same time slot, and the third time-domain position can occupy symbols 7 and 8 in the same time slot. That is, the first and second time-domain positions are continuous in the time domain, while the second and third time-domain positions are discontinuous in the time domain.

[0190] For example, any two of the first, second, and third time-domain positions are not contiguous in the time domain. For instance, taking a scheduling time unit as a time slot, see [reference needed]. Figure 7 The first time domain position can occupy symbols 0 and 1 in a time slot, the second time domain position can occupy symbols 3 and 4 in the same time slot, and the third time domain position can occupy symbols 7 and 8 in the same time slot.

[0191] Optionally, the first time-domain position, the second time-domain position, and the third time-domain position can be consecutive in the time domain.

[0192] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 8The first time domain position can occupy symbols 0 and 1 in a time slot, the second time domain position can occupy symbols 2 and 3 in the same time slot, and the third time domain position can occupy symbols 4 and 5 in the same time slot.

[0193] Scenario 2:

[0194] The R time-domain locations are located within different scheduling time units.

[0195] This means that the R time-domain locations correspond to R scheduling time units. For example, if the scheduling time unit is a time slot, then the R time-domain locations correspond to R time slots.

[0196] This scheme can carry DMRS on different DMRS ports in different scheduling time units, which can reduce DMRS overhead compared to carrying DMRS on all DMRS ports in the same scheduling time unit.

[0197] Furthermore, this scheme can be applied to scenarios where a scheduled PUSCH corresponds to multiple scheduling time units, such as scenarios where a scheduled PUSCH corresponds to multiple time slots. It should be understood that a PUSCH corresponding to multiple scheduling time units means that the time-domain resources corresponding to the scheduled PUSCH include one or more symbols in each of the multiple scheduling time units.

[0198] The following explanation will further illustrate the scheme using R=2 and R=3 as examples.

[0199] When R=2, the first time-domain position and the second time-domain position can be located in different scheduling time units. For example, the first time-domain position and the second time-domain position can be located in different time slots.

[0200] It should be understood that the number of symbols occupied by the first time domain position and the second time domain position can be equal or unequal. For example, the first time domain position and the second time domain position can each occupy 2 symbols, or the first time domain position occupies 1 symbol and the second time domain position occupies 2 symbols.

[0201] It should also be understood that the first time-domain position and the second time-domain position can correspond to symbols with the same index in different scheduling time units, or the first time-domain position and the second time-domain position can correspond to symbols with different indexes in different scheduling time units.

[0202] Optionally, the scheduling time unit corresponding to the first time domain position and the scheduling time unit corresponding to the second time domain position can be continuous in the time domain.

[0203] That is, the scheduling time unit corresponding to the first time domain position and the scheduling time unit corresponding to the second time domain position are two adjacent scheduling time units.

[0204] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 9 The first time domain position can correspond to symbols 0 and 1 in time slot n, and the second time domain position can correspond to symbols 0 and 1 in time slot n+1.

[0205] Optionally, the scheduling time unit corresponding to the first time domain position and the scheduling time unit corresponding to the second time domain position may be discontinuous in the time domain.

[0206] That is, the scheduling time unit corresponding to the first time domain position and the scheduling time unit corresponding to the second time domain position are two non-adjacent scheduling time units. Or, the scheduling time unit corresponding to the first time domain position and the scheduling time unit corresponding to the second time domain position are separated by one or more scheduling time units.

[0207] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 10 The first time domain position can correspond to symbols 0 and 1 in time slot n, and the second time domain position can correspond to symbols 0 and 1 in time slot n+2.

[0208] For example, the first time-domain position is used to transmit the pre-DMRS. That is, the first time-domain position can be a pre-DMRS symbol.

[0209] For example, the second time-domain position is used to transmit the pre-DMRS. That is, the second time-domain position can be a pre-DMRS symbol.

[0210] Furthermore, regarding how to configure the front DMRS symbol, you can refer to the configuration of the front DMRS symbol in the prior art.

[0211] With R=3, the first time-domain position, the second time-domain position, and the third time-domain position can be located in different scheduling time units.

[0212] This means that any two of the three time-domain positions (first, second, and third) can correspond to different scheduling time units. For example, if the scheduling unit is a time slot, the time slots corresponding to the first, second, and third time-domain positions are all different.

[0213] This scheme can carry DMRS on different DMRS ports in different scheduling time units, which can reduce DMRS overhead compared to carrying DMRS on all DMRS ports in the same scheduling time unit.

[0214] It should be understood that the number of symbols occupied by any two time-domain positions among the first, second, and third time-domain positions can be equal or unequal. For example, the first, second, and third time-domain positions can all occupy 2 symbols; or, the first time-domain position occupies 1 symbol, the second time-domain position occupies 2 symbols, and the third time-domain position occupies 2 symbols; or, the first time-domain position occupies 1 symbol, the second time-domain position occupies 2 symbols, and the third time-domain position occupies 3 symbols.

[0215] It should also be understood that at least two of the first, second, and third time-domain positions can correspond to symbols with the same index in different scheduling time units, or the first, second, and third time-domain positions can correspond to symbols with different indices in different scheduling time units.

[0216] Optionally, the scheduling time unit corresponding to the first time domain position, the scheduling time unit corresponding to the second time domain position, and the scheduling time unit corresponding to the third time domain position can be continuous in the time domain.

[0217] That is, the scheduling time unit corresponding to the first time domain position, the scheduling time unit corresponding to the second time domain position, and the scheduling time unit corresponding to the third time domain position are three adjacent scheduling time units.

[0218] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 11 The first time domain position can correspond to symbols 0 and 1 in time slot n, the second time domain position can occupy symbols 0 and 1 in time slot n+1, and the third time domain position can correspond to symbols 0 and 1 in time slot n+2.

[0219] Optionally, at least two of the scheduling time units corresponding to the first time domain position, the second time domain position, and the third time domain position may be discontinuous in the time domain.

[0220] That is, at least two of the scheduling time units corresponding to the first time domain position, the second time domain position, and the third time domain position are not adjacent scheduling time units.

[0221] For example, taking the scheduling time unit as a time slot, see [link to relevant documentation]. Figure 12 The first time-domain position can correspond to symbols 0 and 1 in time slot n, the second time-domain position can correspond to symbols 0 and 1 in time slot n+1, and the third time-domain position can correspond to symbols 0 and 1 in time slot n+3. It should be understood that... Figure 12 The first time domain position, the second time domain position, and the third time domain position are not configured in time slot n+2 (not shown). That is, no DMRS port is mapped in time slot n+2.

[0222] For example, taking the scheduling time unit as a time slot, the first time domain position can correspond to the symbols 0 and 1 in time slot n, the second time domain position can correspond to the symbols 0 and 1 in time slot n+2, and the third time domain position can correspond to the symbols 0 and 1 in time slot n+4.

[0223] For example, the first time-domain position is used to transmit the pre-DMRS. That is, the first time-domain position can be a pre-DMRS symbol.

[0224] For example, the second time-domain position is used to transmit the pre-DMRS. That is, the second time-domain position can be a pre-DMRS symbol.

[0225] For example, the third time-domain location is used to transmit the pre-DMRS. That is, the first time-domain location can be the pre-DMRS symbol.

[0226] Furthermore, regarding how to configure the front DMRS symbol, you can refer to the configuration of the front DMRS symbol in the prior art.

[0227] (ii) A description of the R sets of DMRS ports.

[0228] Similarly, the R sets of DMRS ports will be explained using R=2 and R=3 as examples respectively.

[0229] With R=2, in this paper, for ease of understanding and explanation, the DMRS port set corresponding to the first time domain position and the DMRS port set corresponding to the second time domain position are respectively denoted as the first DMRS port set and the second DMRS port set.

[0230] It should be understood that the number of DMRS ports in the first DMRS port set and the number of DMRS ports in the second DMRS port set may be equal or unequal. For example, the first DMRS port set may contain 12 DMRS ports, and the second DMRS port set may contain 6, 12, or 24 DMRS ports. Alternatively, the first DMRS port set may contain 24 DMRS ports, and the second DMRS port set may contain 6, 12, or 24 DMRS ports. Or, the first DMRS port set may contain 6 DMRS ports, and the second DMRS port set may contain 12 or 24 DMRS ports.

[0231] Optionally, the first DMRS port set and the second DMRS port set contain some of the same DMRS ports and some different ones. That is, the first DMRS port set and the second DMRS port set do not contain completely identical DMRS ports and there is some overlap.

[0232] For example, the second DMRS port set includes some or all of the DMRS ports in the first DMRS port set, as well as the DMRS ports among the M DMRS ports that do not belong to the first DMRS port set. Alternatively, the first DMRS port set includes some or all of the DMRS ports in the second DMRS port set, as well as the DMRS ports among the M DMRS ports that do not belong to the second DMRS port set.

[0233] Taking M=24 as an example, the first DMRS port set can be DMRS ports 0 to 11 (i.e., the first DMRS port set only includes DMRS ports 0 to 11), and the second DMRS port set can be DMRS ports 0 to 23 (i.e., the second DMRS port set only includes DMRS ports 0 to 23). Alternatively, the first DMRS port set can be DMRS ports 0 to 23, and the second DMRS port set can be DMRS ports 0 to 11.

[0234] Alternatively, the first set of DMRS ports can be DMRS ports 0-11, and the second set of DMRS ports can be DMRS ports 0-5 and DMRS ports 12-23.

[0235] Taking M=36 as an example, the first DMRS port set can be DMRS ports 0-11, and the second DMRS port set can be DMRS ports 0-11 and DMRS ports 24-35. Alternatively, the second DMRS port set can be DMRS ports 0-11 and DMRS ports 24-35, and the second DMRS port set can be DMRS ports 0-11.

[0236] Alternatively, the first set of DMRS ports can be DMRS ports 0-23, and the second set of DMRS ports can be DMRS ports 0-11 and DMRS ports 24-35. Alternatively, the second set of DMRS ports can be DMRS ports 0-11 and DMRS ports 24-35, and the second set of DMRS ports can be DMRS ports 0-23.

[0237] To enable those skilled in the art to better understand this application, a time slot is taken as an example, where the scheduling time unit is used. Figures 13 to 15 Several examples are shown where the first DMRS port set and the second DMRS port set are different but overlap. In these examples, the first DMRS port set consists of DMRS ports 0 to 23, and the second DMRS port set consists of DMRS ports 0 to 11 and DMRS ports 24 to 35.

[0238] Figures 13 to 15The DMRS pattern shown supports a maximum of 36 DMRS ports, i.e., M=36. These 36 DMRS ports correspond to 3 CDM groups, and each CDM group supports 12 DMRS ports. Furthermore, each of the 3 CDM groups corresponding to the first time-domain position corresponds to 8 REs, and these 8 REs correspond to 8 DMRS ports. Similarly, each of the 3 CDM groups corresponding to the second time-domain position corresponds to 8 REs, and these 8 REs correspond to 8 DMRS ports. Figure 13 In the DMRS pattern shown, the first time domain position and the second time domain position are located in the same time slot, and the first time domain position and the second time domain position are not continuous in the time domain. Figure 14 In the DMRS pattern shown, the first time domain position and the second time domain position are located in different time slots, and the time slots occupied by the first time domain position and the time slots occupied by the second time domain position are continuous in the time domain. Figure 15 In the DMRS pattern shown, the first time-domain position and the second time-domain position are located in different time slots, and the time slots occupied by the first time-domain position and the second time-domain position are not discontinuous in the time domain. It should be understood that... Figure 15 No DMRS port is mapped in time slot n+1, which is not shown in the figure.

[0239] It should be noted that in this application, DMRS ports 0 to 11 refer to the DMRS ports in the existing protocol, and DMRS ports 12 to 47 are newly introduced DMRS ports. These newly introduced DMRS ports can be represented by new indexes, such as indexes 12 to 47, but this application does not limit this, for example, they can also be represented by indexes 24 to 59.

[0240] Optionally, the first DMRS port set and the second DMRS port set contain completely different DMRS ports. That is, the DMRS ports contained in the first DMRS port set and the second DMRS port set do not overlap.

[0241] Taking M=24 as an example, the first DMRS port set can be DMRS ports 0 to 11, and the second DMRS port set can be DMRS ports 12 to 23. Alternatively, the first DMRS port set can be DMRS ports 12 to 23, and the second DMRS port set can be DMRS ports 0 to 11.

[0242] Taking M=36 as an example, the first DMRS port set can be DMRS ports 0 to 11, and the second DMRS port set can be DMRS ports 12 to 35. Alternatively, the first DMRS port set can be DMRS ports 12 to 35, and the second DMRS port set can be DMRS ports 0 to 11.

[0243] Alternatively, the first set of DMRS ports can be DMRS ports 0-23, and the second set of DMRS ports can be DMRS ports 24-35.

[0244] Taking M=48 as an example, the first DMRS port set can be DMRS ports 0-23, and the second DMRS port set can be DMRS ports 24-47. Alternatively, the first DMRS port set can be DMRS ports 24-47, and the second DMRS port set can be DMRS ports 0-23.

[0245] Alternatively, the first set of DMRS ports may include DMRS ports with odd indices, and the second set of DMRS ports may include DMRS ports with even indices.

[0246] To enable those skilled in the art to better understand this application, a time slot is taken as an example, where the scheduling time unit is used. Figures 16 to 23 Several examples are shown where the first DMRS port set and the second DMRS port set do not intersect. Among them, Figure 16 , Figure 18 , Figure 20 and Figure 22 In the DMRS diagram shown, the first DMRS port set is DMRS ports 0 to 23, and the second DMRS port set is DMRS ports 24 to 35. Figure 17 , Figure 19 , Figure 21 and Figure 23 In the DMRS diagram shown, the first DMRS port set is DMRS ports 0 to 23, and the second DMRS port set is DMRS ports 24 to 47.

[0247] Figure 16 , Figure 18 , Figure 20 and Figure 22 The DMRS pattern shown supports a maximum of 36 DMRS ports, i.e., M=36. These 36 DMRS ports correspond to 3 CDM groups, and each CDM group supports 12 DMRS ports. Furthermore, each of the 3 CDM groups corresponding to the first time-domain position corresponds to 8 REs, and these 8 REs correspond to 8 DMRS ports; each of the 3 CDM groups corresponding to the second time-domain position corresponds to 8 REs, of which 4 REs are consecutive, and the other 4 REs are non-consecutive, with the 4 consecutive REs corresponding to 4 ports. Figure 16Taking CDM group 0, corresponding to the second time-domain position, as an example, the four REs with frequency-domain positions of subcarriers 0 and 1 and time-domain positions of symbols 7 and 8 correspond to DMRS ports 24, 25, 30, and 31. Similarly, the four REs with frequency-domain positions of subcarriers 6 and 7 and time-domain positions of symbols 7 and 8 also correspond to DMRS ports 24, 25, 30, and 31. The DMRS corresponding to the ports of the four REs with frequency-domain positions of subcarriers 6 and 7 and time-domain positions of symbols 7 and 8 is actually a repetition of the DMRS corresponding to the ports of the four REs with frequency-domain positions of subcarriers 0 and 1 and time-domain positions of symbols 7 and 8.

[0248] Figure 17 , Figure 19 , Figure 21 and Figure 23 The DMRS pattern shown supports a maximum of 48 DMRS ports, i.e., M=48. These 48 DMRS ports correspond to 3 CDM groups, and each CDM group supports 16 DMRS ports. Furthermore, each CDM group corresponding to the first time domain position corresponds to 8 REs, and these 8 REs correspond to 8 DMRS ports. Similarly, each CDM group corresponding to the second time domain position corresponds to 8 REs, and these 8 REs correspond to 8 DMRS ports.

[0249] in, Figure 16 and Figure 17 In the DMRS pattern shown, the first time domain position and the second time domain position are located in the same time slot, and the first time domain position and the second time domain position are not continuous in the time domain. Figure 18 and Figure 19 In the DMRS pattern shown, the first time domain position and the second time domain position are located in the same time slot, and the first time domain position and the second time domain position are continuous in the time domain. Figure 20 and Figure 21 In the DMRS pattern shown, the first time domain position and the second time domain position are located in different time slots, and the time slots corresponding to the first time domain position and the second time domain position are continuous in the time domain. Figure 22 and Figure 23 In the DMRS pattern shown, the first time domain position and the second time domain position are located in different time slots, and the time slots corresponding to the first time domain position and the second time domain position are discontinuous in the time domain. It should be understood that... Figure 22 and Figure 23 No DMRS port is mapped in time slot n+1, which is not shown in the figure.

[0250] In one possible implementation, the configuration and / or scheduling time units of the first DMRS port set and / or the second DMRS port set satisfy predefined rules. This can also be understood as the configuration and / or scheduling time units of the first time-domain location satisfying predefined rules. That is, it can be determined, according to predefined rules, whether a scheduling unit has configured the first time-domain location or can map the first DMRS port set, and / or whether a scheduling unit has configured the second time-domain location or can map the second DMRS port set.

[0251] The following examples illustrate the predefined rule in the cases where the scheme is applied to different scheduling time units corresponding to the first and second time domain positions, and in the cases where the scheme is applied to the same scheduling time unit corresponding to the first and second time domain positions.

[0252] (1) This scheme is applied to situations where the first time domain position and the second time domain position correspond to different scheduling time units.

[0253] Example 1:

[0254] The predefined rule could be: for scheduling time units satisfying mod(m,N)=1, only the first DMRS port set is configured, and / or, for scheduling time units satisfying mod(m,N)=2, only the second DMRS port set is configured. That is, for scheduling time units satisfying mod(m,N)=1, only the first DMRS port set is configured, and the second DMRS port set is not configured; and / or, for scheduling time units satisfying mod(m,N)=2, only the second DMRS port set is configured, and the first DMRS port set is not configured.

[0255] Where mod() represents the remainder; m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; and N is an integer greater than 1.

[0256] It should be understood that in this application, when m represents the m-th scheduling time unit among multiple scheduling time units corresponding to the scheduled PUSCH, m = 1, 2, ..., that is, the value of m starts from 1.

[0257] It should also be understood that in this application, configuring the first DMRS set can also be understood as configuring the first time domain location, and configuring the second DMRS set can also be understood as configuring the second time domain location.

[0258] Furthermore, N can be configured by the system or predefined.

[0259] For example, N can be the number of scheduling time units corresponding to the scheduled PUSCH.

[0260] For example, suppose the scheduled PUSCH corresponds to 4 scheduling time units, then N=4. In this case, the first scheduling time unit can be configured with only the first DMRS port set, the second scheduling time unit can be configured with only the second DMRS port set, and the third and fourth scheduling time units can be configured without DMRS ports.

[0261] For example, N can be the number of scheduling time units contained in a radio frame with a length of 10ms, such as the number of time slots contained in a radio frame with a length of 10ms.

[0262] For example, the value of N can be configured by radio resource control (RRC) signaling or downlink control information (DCI). Alternatively, a set of values ​​can be configured by RRC signaling, and the DCI can indicate which value of that set N specifically represents. For instance, different status values ​​of a field can indicate different values ​​of N. For example, if the set of values ​​configured by RRC is {4, 8}, then the value of M can be indicated by a single bit in the DCI; for example, a bit value of 0 indicates N = 4, and a bit value of 1 indicates N = 8.

[0263] It is understandable that when the number of scheduling time units corresponding to the scheduled PUSCH is greater than N, the larger the value of N, the sparser the DMRS transmission. Therefore, for slowly varying channels, the overhead of DMRS will be reduced without affecting the channel estimation performance.

[0264] Example 2:

[0265] The predefined rule could be: scheduling time units satisfying mod(m,2) = 0 are configured only with the first DMRS port set, and / or scheduling time units satisfying mod(m,2) = 1 are configured only with the second DMRS port set. Here, m is the index of the scheduling time unit.

[0266] In other words, scheduling time units with even-numbered indices can be configured with only the first DMRS port set, and / or scheduling time units with odd-numbered indices can be configured with only the second DMRS port set.

[0267] It should be understood that in this application, when m represents the index of the scheduling time unit, m = 0, 1, 2, ..., that is, the value of m can start from 0, but this application does not limit this. For example, m = 1, 2, 3, ..., that is, the value of m can also start from 1.

[0268] Example 3:

[0269] The predefined rule could be: scheduling time units satisfying mod(m,2)=1 are configured only with the first DMRS port set, and / or scheduling time units satisfying mod(m,2)=0 are configured only with the second DMRS port set. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0270] In other words, among the multiple scheduling time units corresponding to the scheduled PUSCH, the odd-numbered scheduling time unit can be configured with only the first DMRS port set, and / or the even-numbered scheduling time unit can be configured with only the second DMRS port set.

[0271] Example 4:

[0272] The predefined rule can be: the scheduling time unit interval between configuring only the first DMRS port set and configuring only the second DMRS port set is P scheduling time units, where P is a positive integer. Furthermore, scheduling time unit 0, i.e., the scheduling time unit with index 0, can configure only the first DMRS port set or only the second DMRS port set; alternatively, the first scheduling time unit among multiple scheduling time units corresponding to the scheduled PUSCH can configure only the first DMRS port set or only the second DMRS port set.

[0273] For example, scheduling time unit n+2*k*(P+1) can be configured with only the first DMRS port set, and scheduling time unit n+(2*k+1)*(P+1) can be configured with only the second DMRS port set. Here, k = 0, 1, 2, 3, 4, ..., and n is an integer greater than or equal to 0. Both n+2*k*(P+1) and n+(2*k+1)*(P+1) represent the index of the scheduling time unit.

[0274] (2) This scheme is applied to the case where the first time domain position and the second time domain position correspond to the same scheduling time unit.

[0275] Example 1:

[0276] The predefined rule can be: scheduling time units that satisfy mod(m,N)=1 are configured with the first DMRS port set and the second DMRS port set. That is, scheduling time units that satisfy mod(m,N)=1 are configured with the first DMRS port set and the second DMRS port set, while scheduling time units that do not satisfy mod(m,N)=1 are not configured with the first DMRS port set and the second DMRS port set. Here, mod() represents the modulo operation; m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; and N is an integer greater than 1.

[0277] Furthermore, N can be configured by the system or predefined.

[0278] For example, N is the number of scheduling time units corresponding to the scheduled PUSCH.

[0279] For example, suppose the scheduled PUSCH corresponds to 4 scheduling time units, then N=4. The first scheduling time unit can be configured with the first and second DMRS port sets, while the second, third, and fourth scheduling time units do not need to be configured with DMRS ports.

[0280] For example, N can be the number of scheduling time units (e.g., time slots) contained in a radio signal with a length of 10ms.

[0281] For example, the value of N can be configured via RRC signaling or DCI. Alternatively, a set of values ​​can be configured via RRC signaling, and the DCI can indicate which value of that set N specifically represents. For instance, different status values ​​of a field can indicate different values ​​of N. For example, if the RRC-configured value set is {4, 8}, then the DCI can indicate the value of M using only one bit; for example, a bit value of 0 indicates N = 4, and a bit value of 1 indicates N = 8.

[0282] It is understandable that when the number of scheduling time units corresponding to the scheduled PUSCH is greater than N, the larger the value of N, the sparser the DMRS transmission. Therefore, for slowly varying channels, the overhead of DMRS will be reduced without affecting the channel estimation performance.

[0283] Example 2:

[0284] The predefined rule can be: configure the first DMRS port set and the second DMRS port set for scheduling time units that satisfy mod(m,2)=0. Here, m is the index of the scheduling time unit.

[0285] In other words, scheduling time units with even-numbered indices are configured with the first DMRS port set and the second DMRS port set, while scheduling time units with odd-numbered indices are not configured with the first DMRS port set and the second DMRS port set.

[0286] Alternatively, the predefined rule could be: Configure the first DMRS port set and the second DMRS port set for scheduling time units that satisfy mod(m,2)=1. Here, m is the index of the scheduling time unit.

[0287] In other words, scheduling time units with odd-numbered indices are configured with the first DMRS port set and the second DMRS port set, while scheduling time units with even-numbered indices are not configured with the first DMRS port set and the second DMRS port set.

[0288] Example 3:

[0289] The predefined rule can be: Configure the first DMRS port set and the second DMRS port set for scheduling time units that satisfy mod(m,2)=0. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0290] In other words, among the multiple scheduling time units corresponding to the scheduled PUSCH, the even-numbered scheduling time unit is configured with the first DMRS port set and the second DMRS port set, while the odd-numbered scheduling time unit is not configured with the first DMRS port set and the second DMRS port set.

[0291] Alternatively, the predefined rule could be: Configure the first DMRS port set and the second DMRS port set for scheduling time units that satisfy mod(m,2)=1. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0292] In other words, among the multiple scheduling time units corresponding to the scheduled PUSCH, the odd-numbered scheduling time unit is configured with the first DMRS port set and the second DMRS port set, while the even-numbered scheduling time unit is not configured with the first DMRS port set and the second DMRS port set.

[0293] Example 4:

[0294] The predefined rule can be: configure the first DMRS port set and the second DMRS port set at intervals of P scheduling time units, where P is a positive integer.

[0295] In other words, the two scheduling data units that are closest in the time domain and have configured the first DMRS port set and the second DMRS port set are separated by P scheduling time units. For example, scheduling time unit n+k*(P+1) is configured with the first DMRS port set and the second DMRS port set, while other scheduling time units are not configured with the first DMRS port set and the second DMRS port set, k = 0, 1, 2, 3, 4, ..., n is an integer greater than or equal to 0, and n+k*(P+1) represents the index of the scheduling time unit.

[0296] For example, assuming P=2 and n=0, scheduling time units 0, 3, 6, 9, ... can be configured with the first DMRS port set and the second DMRS port set, while other scheduling time units are not configured with the first DMRS port set and the second DMRS port set.

[0297] Alternatively, the predefined rule could be: among the multiple scheduling time units corresponding to the scheduled PUSCH, the first DMRS port set and the second DMRS port set are configured at intervals of P scheduling time units, where P is a positive integer.

[0298] For example, among the multiple scheduling time units corresponding to the scheduled PUSCH, the 1+k*(P+1)th scheduling time unit is configured with the first DMRS port set and the second DMRS port set, while other scheduling time units are not configured with the first DMRS port set and the second DMRS port set, k=0,1,2,3,4,……, and n+k*(P+1)≤m, where m is the number of scheduling time units corresponding to the scheduled PUSCH, and n is an integer greater than or equal to 0.

[0299] For example, assuming P=2 and m=5, then in the 5 scheduling time units corresponding to the scheduled PUSCH, the first and fourth scheduling time units can be configured with the first DMRS port set and the second DMRS port set, while the other scheduling time units do not configure the first DMRS port set and the second DMRS port set.

[0300] With R=3, for ease of understanding and explanation, the DMRS port sets corresponding to the first time domain position, the second time domain position, and the third time domain position are respectively referred to as the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0301] It should be understood that any two DMRS port sets among these three DMRS port sets may contain the same or different numbers of DMRS ports. For example, the first DMRS port set may contain 6, 12, or 24 DMRS ports, the second DMRS port set may contain 6, 12, or 24 DMRS ports, and the third DMRS port set may contain 6, 12, or 24 DMRS ports.

[0302] Optionally, at least two of the first, second, and third DMRS port sets contain DMRS ports that are partially the same and partially different.

[0303] For example, the first DMRS port set can be DMRS ports 0 to 11, the second DMRS port set can be 0 to 23, and the third DMRS port set can be DMRS ports 24 to 35.

[0304] For example, the first DMRS port set can be DMRS ports 0 to 11, the second DMRS port set can be 0 to 23, and the third DMRS port set can be DMRS ports 0 to 5 and 24 to 35.

[0305] Optionally, any two DMRS port sets among the first DMRS port set, the second DMRS port set, and the third DMRS port set contain completely different DMRS ports.

[0306] For example, the first DMRS port set can be DMRS ports 0 to 11, the second DMRS port set can be 12 to 23, and the third DMRS port set can be DMRS ports 24 to 35.

[0307] For example, the first DMRS port set can be DMRS ports 0 to 11, the second DMRS port set can be 12 to 23, and the third DMRS port set can be DMRS ports 24 to 47.

[0308] To enable those skilled in the art to better understand this application, a time slot is taken as an example, where the scheduling time unit is used. Figure 24 and Figure 25 Examples are shown where any two DMRS port sets from the first, second, and third DMRS port sets contain completely different DMRS ports. Specifically, the first DMRS port set consists of DMRS ports 0-11, the second DMRS port set consists of DMRS ports 12-23, and the third DMRS port set consists of DMRS ports 23-35.

[0309] Figure 24 and Figure 25 The DMRS pattern shown supports a maximum of 36 DMRS ports, i.e., M=36. These 36 DMRS ports correspond to 3 CDM groups, and each CDM group supports 12 DMRS ports. Furthermore, in the first time-domain position, each of the 3 CDM groups corresponds to 8 REs, with 4 REs being consecutive and the other 4 non-consecutive; the 4 consecutive REs correspond to 4 ports. In the second time-domain position, each of the 3 CDM groups corresponds to 8 REs, with 4 REs being consecutive and the other 4 non-consecutive; the 4 consecutive REs correspond to 4 ports. In the third time-domain position, each of the 3 CDM groups corresponds to 8 REs, with 4 REs being consecutive and the other 4 non-consecutive; the 4 consecutive REs correspond to 4 ports. Figure 24Taking CDM group 0, corresponding to the first time-domain position, as an example, the four REs with frequency-domain positions of subcarriers 0 and 1 and time-domain positions of symbols 0 and 1 correspond to DMRS ports 0, 1, 6, and 7. Similarly, the four REs with frequency-domain positions of subcarriers 6 and 7 and time-domain positions of symbols 0 and 1 also correspond to DMRS ports 0, 1, 6, and 7. The DMRS corresponding to the ports of the four REs with frequency-domain positions of subcarriers 6 and 7 and time-domain positions of symbols 0 and 1 is actually a repetition of the DMRS corresponding to the ports of the four REs with frequency-domain positions of subcarriers 0 and 1 and time-domain positions of symbols 0 and 1. Figure 24 In the DMRS pattern shown, the first time-domain position, the second time-domain position, and the third time-domain position are located in the same time slot, and these three time-domain positions are continuous in the time domain. Figure 25 In the DMRS pattern shown, the first time domain position, the second time domain position, and the third time domain position are located in different time slots, and the time slots corresponding to these three time domain positions are continuous in the time domain.

[0310] In one possible implementation, the configuration of the first DMRS port set, the configuration of the second DMRS port set, and / or the configuration of the third DMRS port set, and the scheduling time units satisfy predefined rules. This can also be understood as the configuration of the first time-domain position, the configuration of the second time-domain position, and / or the configuration of the third time-domain position, and the scheduling time units satisfying predefined rules. That is, it can be determined according to predefined rules whether a scheduling unit has configured the first time-domain position or can map the first DMRS port set, whether a scheduling unit has configured the second time-domain position or can map the second DMRS port set, and / or whether a scheduling unit has configured the third time-domain position or can map the third DMRS port set.

[0311] The following examples illustrate the predefined rule when the scheme is applied to the cases where the first, second, and third time domain positions are located in different scheduling time units, and when the scheme is applied to the cases where the first, second, and third time domain positions are located in the same scheduling time unit.

[0312] (1) This scheme is applied to situations where the first time domain position, the second time domain position and the third time domain position correspond to different scheduling time units.

[0313] Example 1:

[0314] The predefined rule may include one or more of the following:

[0315] The scheduling time unit that satisfies mod(m,N)=1 is configured only for the first DMRS port set;

[0316] For scheduling time units that satisfy mod(m,N)=2, only the second DMRS port set is configured; or,

[0317] For scheduling time units that satisfy mod(m,N)=3, only the third DMRS port set is configured.

[0318] Where m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH, and N is a positive integer.

[0319] Furthermore, N can be configured by the system or predefined. The value of N can be found in the explanation above regarding the case where R=2.

[0320] Example 2:

[0321] The predefined rule may include one or more of the following:

[0322] The scheduling time unit that satisfies mod(m,3)=0 is configured only for the first DMRS port set;

[0323] The scheduling time unit that satisfies mod(m,3)=1 is configured only with the second DMRS port set; or,

[0324] The scheduling time unit that satisfies mod(m,3)=2 is configured only for the third DMRS port set.

[0325] Where m is the index of the scheduling time unit.

[0326] Example 3:

[0327] The predefined rule may include one or more of the following:

[0328] The scheduling time unit that satisfies mod(m,3)=1 is configured only for the first DMRS port set;

[0329] The scheduling time unit that satisfies mod(m,3)=2 is configured only with the second DMRS port set; or,

[0330] The scheduling time unit that satisfies mod(m,3)=0 is configured only for the third DMRS port set.

[0331] Where m is the m-th scheduling time unit in the scheduled PUSCH.

[0332] Example 4:

[0333] The predefined rule can be: the scheduling time unit interval between configuring only the first DMRS port set and configuring only the second DMRS port set is P scheduling time units, and the scheduling time unit interval between configuring only the second DMRS port set and configuring only the third DMRS port set is Q scheduling time units, where P and Q are both positive integers, and P and Q can be equal or unequal.

[0334] Furthermore, scheduling time unit 0, i.e. scheduling time unit with index 0, can be configured with only the first DMRS port set, or the first scheduling time unit among multiple scheduling time units corresponding to the scheduled PUSCH can be configured with only the first DMRS port set.

[0335] For example, scheduling time unit n+2*k*(P+1) can be configured with only the first DMRS port set, scheduling time unit n+(2*k+1)*(P+1) can be configured with only the second DMRS port set, and scheduling time unit n+(2*k+2)*(P+1) can be configured with only the third DMRS port set, where k = 0, 1, 2, 3, 4, ..., n is an integer greater than or equal to 0, and n+2*k*(P+1) and n+(2*k+2)*(P+1) are the indices of the scheduling time unit.

[0336] (2) This scheme is applied to situations where the first time domain position, the second time domain position and the third time domain position correspond to the same scheduling time unit.

[0337] Example 1:

[0338] The predefined rule can be: Configure the first DMRS port set, the second DMRS port set, and the third DMRS port set for scheduling time units that satisfy mod(m,N) = 1. Here, mod() represents the remainder; m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH; and N is an integer greater than 1.

[0339] Furthermore, N can be configured by the system or predefined. The value of N can be found in the explanation above regarding the case where R=2.

[0340] Example 2:

[0341] The predefined rule can be: Configure the first DMRS port set, the second DMRS port set, and the third DMRS port set for scheduling time units that satisfy mod(m,2)=0. Here, m is the index of the scheduling time unit.

[0342] In other words, scheduling time units with even-numbered indices are configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while scheduling time units with odd-numbered indices are not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0343] Alternatively, the predefined rule could be: Configure the first DMRS port set, the second DMRS port set, and the third DMRS port set for scheduling time units that satisfy mod(m,2)=1. Here, m is the index of the scheduling time unit.

[0344] In other words, scheduling time units with odd-numbered indices are configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while scheduling time units with even-numbered indices are not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0345] Example 3:

[0346] The predefined rule can be: Configure the first DMRS port set, the second DMRS port set, and the third DMRS port set for scheduling time units that satisfy mod(m,2)=0. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0347] In other words, among the multiple scheduling time units corresponding to the scheduled PUSCH, the even-numbered scheduling time unit is configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while the odd-numbered scheduling time unit is not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0348] Alternatively, the predefined rule could be: Configure the first DMRS port set, the second DMRS port set, and the third DMRS port set for scheduling time units that satisfy mod(m,2)=1. Here, m is the m-th scheduling time unit among the multiple scheduling time units corresponding to the scheduled PUSCH.

[0349] In other words, among the multiple scheduling time units corresponding to the scheduled PUSCH, the odd-numbered scheduling time unit is configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while the even-numbered scheduling time unit is not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0350] Example 4: The predefined rule can be: configure the first DMRS port set, the second DMRS port set, and the third DMRS port set at intervals of P scheduling time units, where P is a positive integer.

[0351] In other words, the two scheduling time units that are closest in the time domain and have configured the first, second, and third DMRS port sets are separated by P scheduling time units. For example, scheduling time unit n+k*(P+1) configures the first, second, and third DMRS port sets, while other scheduling time units do not configure the first, second, and third DMRS port sets, k = 0, 1, 2, 3, 4, ..., n is an integer greater than or equal to 0, and n+k*(P+1) is the index of the scheduling time unit.

[0352] For example, assuming P=2 and n=0, scheduling time units 0, 3, 6, 9, ... can be configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while other scheduling time units are not configured with the first DMRS port set or the second DMRS port set.

[0353] Alternatively, the predefined rule could be: among the multiple scheduling time units corresponding to the scheduled PUSCH, the first DMRS port set, the second DMRS port set, and the third DMRS port set are configured at intervals of P scheduling time units, where P is a positive integer.

[0354] For example, among the multiple scheduling time units corresponding to the scheduled PUSCH, the 1+k*(P+1)th scheduling time unit is configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while other scheduling time units are not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set. k = 0, 1, 2, 3, 4, ..., and n+k*(P+1) ≤ m, where m is the number of scheduling time units corresponding to the scheduled PUSCH, and n is an integer greater than or equal to 0.

[0355] For example, assuming P=2 and m=5, the first and fourth scheduling time units corresponding to the scheduled PUSCH can be configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set, while the other scheduling time units are not configured with the first DMRS port set, the second DMRS port set, and the third DMRS port set.

[0356] It should be understood that the predefined rules in this application can also be any other reasonable rules, and this application does not limit what kind of rules the predefined rules are.

[0357] It should be noted that the above-mentioned Figures 13 to 25 The first, second, and third time-domain positions in the DMRS diagram shown are merely examples, and this application does not limit which symbols(s) the first, second, and third time-domain positions specifically occupy. For instance, in some DMRS diagrams, the first time-domain position corresponds to symbols 0 and 1, but in actual implementation, the first time-domain position may correspond to symbols 1 and 2. Furthermore, Figures 13 to 25 The correspondence between CDM groups and DMRS ports shown in the DMRS diagram is only an example. In actual implementation, the correspondence between CDM groups and DMRS ports may not be as shown, or the number of CDM groups may not be 3. For example, in Figures 13 to 23 The system supports a maximum of 3 CDM groups, but in actual implementation, the first time domain position may correspond to 3 CDM groups, and the second time domain position may correspond to another 3 CDM groups, such as CDM groups 3 to 5. For example, regarding... Figure 13 The DMRS diagram shown may correspond to CDM group 0 in actual implementation. Figure 13 The DMRS port corresponding to CDM group 2 in the diagram. CDM group 2 may correspond to... Figure 13 The DMRS port corresponding to CDM group 0 in the table.

[0358] It should be understood that this application does not limit the DMRS drawing. Figures 13 to 25 The DMRS diagram shown is merely an example and should not be construed as limiting this application.

[0359] In summary, the solution provided in this application can support more than 12 orthogonal DMRS ports, such as 24, 36 or 48, or even more, by mapping different DMRS port sets at at least two time domain locations. This is beneficial for parallel transmission of more spatial layers and provides system capacity.

[0360] As one embodiment of this application, each time slot can be configured with a first time domain position and a second time domain position, and the first time domain position can be used to send a pre-DMRS, while the second time domain position can be used to send an additional DMRS. In this case, the terminal device provided by this application is compatible with legacy terminal devices in some scenarios, but not with legacy terminal devices in other scenarios. This will be explained below.

[0361] Legacy terminal devices refer to terminal devices supported by current or previous standards (i.e., existing terminal devices, such as those in 4G systems or current 5G systems). Therefore, Legacy terminal devices can only recognize DMRS ports 0-11 in the front DMRS symbol and additional DMRS symbols. Legacy-compatible terminal devices mean that, during multi-user pairing, Legacy terminal devices and new terminal devices can be scheduled to transmit together on the same time-frequency resources.

[0362] 1. Compatible with Legacy terminal devices

[0363] The additional DMRS for a Legacy terminal device is a repetition of the preceding DMRS. That is, the Legacy terminal device transmits the same DMRS on the additional DMRS symbol as on the preceding DMRS symbol.

[0364] The solution provided in this application, while adding orthogonal DMRS ports, is also compatible with existing terminal equipment. This allows for multi-user pairing of the terminal equipment provided in this application with terminal equipment that only supports existing standard capabilities, without requiring any hardware or software updates to the existing terminal equipment.

[0365] 2. Incompatible with Legacy terminal devices

[0366] Legacy terminal devices do not send DMRS on additional DMRS symbols.

[0367] In this scenario, the terminal device provided in this application and terminal devices that only support existing standard capabilities cannot perform multi-user pairing.

[0368] In this application, before S220, that is, before the terminal device sends the DMRS, it can determine the CDM group and OCC corresponding to the DMRS port and generate the corresponding DMRS sequence.

[0369] In one possible implementation, the correspondence between DMRS ports, CDM groups, and OCCs is shown in part or all of Table 2.

[0370] Table 2

[0371]

[0372]

[0373] In Table 2, Indicates the index of the DMRS port; λ represents the index of the CDM group; Δ represents the subcarrier offset; w f (k'+2t) represents the frequency domain OCC, w t (l') represents the frequency domain OCC.

[0374] The last column in Table 2 can also be omitted. In Table 2, when the DMRS extension flag (DMRSextendFlag) is 0, it indicates that it is not in use; when the DMRSextendFlag is 1, it indicates that the DMRS port is mapped to a second time-domain location (e.g., with an appended DMRS symbol). It should be understood that the DMRS extension flag can also be replaced with other flags that have the same function.

[0375] In one possible implementation, the initial sequence r(n) of the DMRS generated based on the gold sequence can satisfy the following formula:

[0376]

[0377] Where c(i) is a pseudo-random sequence, generated by the following formula:

[0378]

[0379] Where, N C =1600, x1(n) can be initialized as x1(0)=1, x1(n)=0, n=1,2,...,30, and x2(n) satisfies:

[0380] c init Defined as:

[0381]

[0382] Where l is the symbol index, The number of time slots within a frame. n is the number of symbols in a time slot. SCID ∈{0,1} are the DMRS sequence initialization parameters. For masking. The value depends on the different high-level parameter configurations.

[0383] When mapping the sequence r(n) to each RE, the following formula is satisfied:

[0384]

[0385] Where k is the subcarrier index and l is the symbol index. This is the index of the DMRS port; mod() is the modulo operation; the meaning of Δ is the same as above; It is the symbol offset; μ is the index of the subcarrier spacing; w f (k'+2t) and w t The meaning of (l') is the same as above; v is the layer index, which is a pre-configured value.

[0386] As an embodiment of this application, the sequence r(n) can be mapped to each RE according to the above formula (4).

[0387] Furthermore, as described above, network devices can indicate the scheduled DMRS port to terminal devices via indication information. For example, this indication information can be an index value corresponding to one or more DMRS ports, which are the scheduled DMRS ports.

[0388] In one possible implementation, when the first time domain position and the second time domain position are located within the same scheduling time unit, the correspondence between the index value (the indication information) and the DMRS port can be shown in part or all of one or more of the tables in Tables 3 to 6.

[0389] When the rank is 1, the correspondence between the index value (this indication information) and the DMRS port is shown in Table 3. It should be understood that for uplink transmission, when the rank of the terminal device configured by the network device for uplink transmission is 1, the terminal device only needs 1 DMRS port to send uplink data, that is, the number of DMRS ports scheduled by the network device is 1.

[0390] Table 3

[0391]

[0392]

[0393] It should be understood that "N / A" in this article means that the corresponding number of symbols is 0.

[0394] In Table 3, the index values ​​from 0 to 27 are the same as those in Table 7.3.1.1.2-20 of the prior art TS 38.212. The index values ​​from 28 to 51 are provided by the embodiments of this application. For example, when the indication information sent by the network device is 30, it indicates that the scheduled DMRS port is the DMRS port with index 14, and the number of symbols occupied by the CDM group to which this DMRS port belongs is 2.

[0395] Additionally, in Table 3, index values ​​of 40-51 correspond to DMRS ports 24-35, with a corresponding additional DMRS symbol count of 2 and a pre-signal count of 0. This means that neither DMRS nor PUSCH signals are sent at the positions corresponding to the pre-signal. When the network device indicates to the terminal device that the scheduled DMRS port index value is in the range of 24-35, even if a pre-signal is configured, the terminal device will not send any signal on that symbol. The number of pre-signal symbols in Table 3 is unrelated to DMRS ports 0-23.

[0396] Optionally, the last column in Table 3 can be omitted, in which case two additional DMRS symbols are configured by default for DMRS ports 24-35.

[0397] When the rank is 2, the correspondence between the index value and the DMRS port is shown in Table 4. It should be understood that for uplink transmission, when the rank of the terminal device configured by the network device for uplink transmission is 2, the terminal device needs 2 DMRS ports to send uplink data, that is, the number of DMRS ports scheduled by the network device is 2.

[0398] Table 4

[0399]

[0400] In Table 4, the index values ​​from 0 to 18 are the same as those in Table 7.3.1.1.2-21 of the prior art TS 38.212. The index values ​​from 19 to 30 are provided by the embodiments of this application. For example, when the indication information sent by the network device is 24, it indicates that the scheduled DMRS ports are the DMRS ports with indices of 22 and 23.

[0401] Optionally, the last column in Table 4 can be omitted, in which case two additional DMRS symbols are configured by default for DMRS ports 24-35.

[0402] When the rank is 3, the correspondence between the index value and the DMRS port is shown in Table 5. It should be understood that for uplink transmission, when the rank of the terminal device configured by the network device for uplink transmission is 3, the terminal device needs 3 DMRS ports to send uplink data, that is, the number of DMRS ports scheduled by the network device is 3.

[0403] Table 5

[0404]

[0405] In Table 5, the index values ​​from 0 to 5 are the same as those in Table 7.3.1.1.2-22 of the prior art TS 38.212. The index values ​​from 6 to 31 are provided in the embodiments of this application. For example, when the indication information sent by the network device is 9, it indicates that the scheduled DMRS port is the DMRS port with index 19, 22, or 23.

[0406] Optionally, the last column in Table 5 can be omitted, in which case two additional DMRS symbols are configured by default for DMRS ports 24-35.

[0407] When the rank is 4, the correspondence between the index value and the DMRS port is shown in Table 6. It should be understood that for uplink transmission, when the rank of the terminal device configured for uplink transmission by the network device is 4, the terminal device needs 4 DMRS ports to send uplink data, that is, the number of DMRS ports scheduled by the network device is 4.

[0408] Table 6

[0409]

[0410]

[0411] In Table 6, the index values ​​from 0 to 4 are the same as those in Table 7.3.1.1.2-23 of the prior art TS 38.212. The index values ​​from 5 to 10 are provided in the embodiments of this application. For example, when the indication information sent by the network device is 7, it indicates that the scheduled DMRS port is the DMRS port with indices 16, 17, 22, and 23.

[0412] Optionally, the last column in Table 6 can be omitted, in which case two additional DMRS symbols are configured by default for DMRS ports 24-35.

[0413] In one possible implementation, where the first time domain position and the second time domain position are located in different scheduling time units, the correspondence between the index value (the indication information) and the DMRS port can be shown in part or all of one or more of the tables in Tables 7 to 10.

[0414] When the rank is 1, the correspondence between the index value (this indication information) and the DMRS port is shown in Table 7.

[0415] Table 7

[0416]

[0417]

[0418] When the rank is 2, the correspondence between the index value and the DMRS port is shown in Table 8.

[0419] Table 8

[0420]

[0421]

[0422] When the rank is 3, the correspondence between the index value and the DMRS port is shown in Table 9.

[0423] Table 9

[0424]

[0425] When the rank is 4, the correspondence between the index value and the DMRS port is shown in Table 10.

[0426] Table 10

[0427]

[0428]

[0429] It should be understood that Tables 2 to 10 above are merely examples and should not constitute any limitation on this application.

[0430] The above text mainly introduced the scheme for sending DMRS in uplink communication. The following text briefly introduces the scheme for sending DMRS in downlink communication.

[0431] Figure 26 This is a schematic diagram of a method for sending DMRS provided in this application. The steps in method 400 are briefly described below.

[0432] S410, the network device sends an instruction to the terminal device. Correspondingly, the terminal device receives the instruction from the network device.

[0433] This indication information is used to indicate the scheduled DMRS port, or in other words, it indicates the DMRS port configured on the network device. For example, this indication information can be sent via DCI.

[0434] The scheduled DMRS port belongs to a DMRS port set, which includes M DMRS ports. These M DMRS ports can be the maximum number of DMRS ports supported by the system.

[0435] The M DMRS ports can correspond to R time-domain locations, meaning the M DMRS ports can be mapped to R time-domain locations, where R is an integer greater than or equal to 2. For example, the M DMRS ports can be mapped to two or three time-domain locations. Each time-domain location occupies or corresponds to one or more consecutive symbols, and the number of symbols occupied by any two time-domain locations can be equal or unequal. Two adjacent time-domain locations can be contiguous or discontinuous in the time domain. Here, two time-domain locations being adjacent means that there are no other time-domain locations among the R time-domain locations between these two time-domain locations.

[0436] Furthermore, each time-domain location corresponds to a DMRS port set, that is, R time-domain locations correspond to R DMRS port sets, and any two port sets in these R port sets are different.

[0437] For possible implementations of the R time-domain locations and the corresponding R DMRS port sets, please refer to the description in method 300 above. However, it should be understood that when the possible implementations in method 300 are applied to method 400, the uplink-related content in method 300 will be changed to downlink-related content. For example, PUSCH in method 300 will be changed to PDSCH.

[0438] In S420, the network device sends DMRS on the scheduled DMRS port. Correspondingly, the terminal device receives DMRS from the network device on the scheduled DMRS port.

[0439] According to the method for transmitting DMRS provided in this application, by mapping different sets of DMRS ports (e.g., the first set of DMRS ports and the second set of DMRS ports) at at least two time domain locations (e.g., the first time domain location and the second time domain location), more DMRS ports can be supported, thereby improving system capacity.

[0440] It should be understood that formulas (1) to (4) described in method 300, as well as tables 2 to 10, are also applicable to method 400, and will not be described in detail here.

[0441] Figure 27 This is a schematic diagram of a communication device provided in an embodiment of this application. Figure 27 As shown, the communication device 2000 may include a receiving unit 2100 and a transmitting unit 2200. Optionally, the communication device may also include a processing unit 2200.

[0442] The receiving unit 2100 may be a receiver, an input interface, a pin, or a circuit, etc. The receiving unit 2100 can be used to perform the receiving steps in the above method embodiments.

[0443] The transmitting unit 2200 may be a transmitter, output interface, pin, or circuit, etc. The transmitting unit 2200 may be used to perform the receiving steps in the above method embodiments.

[0444] It should be understood that the receiving unit 2100 and the transmitting unit 2200 can be combined into a transceiver unit. This transceiver unit may include a transmitting unit and / or a receiving unit. The transceiver unit may be a transceiver (including a transmitter and / or a receiver), an input / output interface (including input and / or output interfaces), pins, or circuitry, etc.

[0445] The processing unit 2300 may be a processor (which may include one or more), a processing circuit with processor functions, etc., and may be used to perform other steps in the above method embodiments besides sending and receiving.

[0446] Optionally, the communication device may further include a storage unit, which may be a memory, an internal storage unit (e.g., a register, a cache, etc.), or an external storage unit (e.g., a read-only memory, a random access memory, etc.). The storage unit is used to store instructions, and the processing unit 2300 executes the instructions stored in the storage unit to cause the communication device to perform the aforementioned method.

[0447] In one possible design, the communication device 2000 may correspond to the terminal device in the above method embodiments and may perform the operations performed by the terminal device in the above method.

[0448] In one example, the receiving unit 2100 is configured to receive indication information, which indicates a scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is configured to transmit DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. The M DMRS ports correspond to R time-domain locations, where R is an integer greater than or equal to 2. Any two DMRS port sets corresponding to the R time-domain locations are different.

[0449] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to transmit DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position and a second time domain position, and the first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position.

[0450] For example, the receiving unit 2100 is used to receive indication information, which is used to indicate the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to transmit DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position, a second time domain position, and a third time domain position. Any two DMRS port sets among the first DMRS port set corresponding to the first time domain position, the second DMRS port set corresponding to the second time domain position, and the third DMRS port set corresponding to the third time domain position are different.

[0451] In another example, the receiving unit 2100 is configured to receive indication information, which indicates a scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is configured to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to R time-domain locations, where R is an integer greater than or equal to 2. Any two DMRS port sets corresponding to the R time-domain locations are different.

[0452] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position and a second time domain position, and the first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position.

[0453] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set containing M DMRS ports. These M DMRS ports correspond to a first time domain position, a second time domain position, and a third time domain position. Any two DMRS port sets among the first DMRS port set corresponding to the first time domain position, the second DMRS port set corresponding to the second time domain position, and the third DMRS port set corresponding to the third time domain position are different.

[0454] In another possible design, the communication device 2000 may correspond to the network device in the above method embodiment and may perform the operations performed by the network device in the above method.

[0455] In one example, the transmitting unit 2200 is configured to transmit indication information, which indicates a scheduled demodulation reference signal (DMRS) port. The receiving unit 2100 is configured to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. The M DMRS ports correspond to R time-domain locations, where R is an integer greater than or equal to 2. Any two DMRS port sets corresponding to the R time-domain locations are different.

[0456] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to transmit DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position and a second time domain position, and the first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position.

[0457] For example, the receiving unit 2100 is used to receive indication information, which is used to indicate the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to transmit DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position, a second time domain position, and a third time domain position. Any two DMRS port sets among the first DMRS port set corresponding to the first time domain position, the second DMRS port set corresponding to the second time domain position, and the third DMRS port set corresponding to the third time domain position are different.

[0458] In another example, the receiving unit 2100 is configured to receive indication information, which indicates a scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is configured to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a set of DMRS ports, which contains M DMRS ports corresponding to R time-domain locations, where R is an integer greater than or equal to 2. Any two DMRS port sets corresponding to the R time-domain locations are different.

[0459] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. These M DMRS ports correspond to a first time domain position and a second time domain position, and the first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position.

[0460] For example, the receiving unit 2100 is used to receive indication information, which indicates the scheduled demodulation reference signal (DMRS) port. The transmitting unit 2200 is used to receive DMRS on the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set containing M DMRS ports. These M DMRS ports correspond to a first time domain position, a second time domain position, and a third time domain position. Any two DMRS port sets among the first DMRS port set corresponding to the first time domain position, the second DMRS port set corresponding to the second time domain position, and the third DMRS port set corresponding to the third time domain position are different.

[0461] It should be understood that the possible implementations of the R time-domain locations and the R DMRS port sets can be found in the descriptions above. For example, the implementations of the first and second time-domain locations, as well as the first and second DMRS port sets, can be found in the descriptions above for the case where R=2. Similarly, the implementations of the first, second, and third time-domain locations, as well as the first, second, and third DMRS port sets, can be found in the descriptions above for the case where R=3, and will not be repeated here.

[0462] It should be understood that the above division of units is only a functional division, and there may be other division methods in actual implementation.

[0463] It should also be understood that the above processing unit can be implemented in hardware, software, or a combination of both.

[0464] It should also be understood that when the communication device 2000 is a network device, the receiving unit 2100 and the transmitting unit 2200 in the communication device can correspond to Figure 28 The RRU 3100 in the network device 2000 shown in the figure, the processing unit 2300 in the communication device can correspond to Figure 28 The network device 2000 shown includes a BBU 3200. When the communication device 2000 is a chip configured in the network device, the transceiver unit 2100 in the communication device can be an input / output interface.

[0465] It should also be understood that when the communication device 2000 is a terminal device, the receiving unit 2100 and the transmitting unit 2200 in the communication device 2000 can correspond to Figure 29 The transceiver 4002 in the terminal device 4000 shown in the diagram, and the processing unit 2300 in the communication device 2000 can correspond to Figure 29 The processor 4001 in the terminal device 4000 shown in the figure.

[0466] Figure 28 This is a schematic diagram of the network device provided in the embodiments of this application, such as a schematic diagram of a base station. The network device 3000 can perform the functions of the network device in the above method embodiments.

[0467] As shown in the figure, the network device 3000 may include one or more radio frequency units, such as a remote radio unit (RRU) 3100 and one or more baseband units (BBUs) (also known as distributed units (DUs)) 3200. The RRU 3100 may be referred to as a transceiver unit or communication unit, and... Figure 27 The corresponding transceiver unit 2100 in the middle.

[0468] Optionally, the transceiver unit 3100 can also be referred to as a transceiver, transceiver circuit, or transceiver, etc., and 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, whereby the receiving unit may correspond to a receiver (or receiver circuit), and the transmitting unit may correspond to a transmitter (or transmitter circuit). The RRU 3100 is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals to baseband signals. The BBU 3200 is mainly used for baseband processing and base station control, etc. The RRU 3100 and BBU 3200 may be physically installed together or physically separated, i.e., a distributed base station.

[0469] The BBU 3200 is the control center of the base station, also known as the processing unit, and can communicate with... Figure 27 The processing unit 2200 in the above-mentioned method is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, spreading, etc. For example, the BBU (processing unit) can be used to control the base station to execute the operation process of the network device in the above-described method embodiment.

[0470] In one example, the BBU 3200 can be composed of one or more single boards. Multiple boards can collectively support a single access standard wireless access network (such as an LTE network), or they can each support different access standards wireless access networks (such as LTE, 5G, or other networks). The BBU 3200 also includes a memory 3201 and a processor 3202. The memory 3201 is used to store necessary instructions and data. The processor 3202 is used to control the base station to perform necessary actions, such as controlling the base station to execute the operation procedures related to the network device in the above method embodiments. The memory 3201 and processor 3202 can serve one or more single boards. That is, each single board can have its own memory and processor, or multiple single boards can share the same memory and processor. Furthermore, each single board can also have necessary circuitry.

[0471] It should be understood that Figure 28 The network device 3000 shown can implement the various processes involved in the network device in the foregoing method embodiments. The operation or function of each module in the network device 3000 is to implement the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0472] The BBU 3200 described above can be used to perform the actions implemented internally by the network device as described in the preceding method embodiments, while the RRU 3100 can be used to perform the network device transmission and reception actions as described in the preceding method embodiments. Please refer to the descriptions in the preceding method embodiments for details, which will not be repeated here.

[0473] Figure 29 This is a schematic diagram of the structure of a terminal device 4000 provided in an embodiment of this application. As shown in the figure, the terminal device 4000 includes a processor 4001 and a transceiver 4002. Optionally, the terminal device 4000 may also include a memory 4003. The processor 4001, transceiver 4002, and memory 4003 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 4003 is used to store computer programs, and the processor 4001 is used to call and run the computer program from the memory 4003 to control the transceiver 4002 to transmit and receive signals.

[0474] The processor 4001 and memory 4003 described above can be combined into a processing device 4004. The processor 4001 executes the program code stored in the memory 4003 to achieve the above functions. It should be understood that the processing device 4004 shown in the figure is only an example. In a specific implementation, the memory 4003 may also be integrated into the processor 4001 or independent of the processor 4001. This application does not limit this.

[0475] The aforementioned terminal device 4000 may also include an antenna 4010 for transmitting uplink data or uplink control signaling output by transceiver 4002 via wireless signals.

[0476] It should be understood that Figure 29 The terminal device 4000 shown can implement the various processes involved in the terminal device in the foregoing method embodiments. The operation or function of each module in the terminal device 4000 is to implement the corresponding process in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0477] Optionally, the terminal device 4000 may also include a power supply 4005 for providing power to various devices or circuits in the terminal device.

[0478] In addition, to make the terminal device more functional, the terminal device 4000 may also include one or more of the following: an input unit 4006, a display unit 4007, an audio circuit 4008, a camera 4009, and a sensor 4011. The audio circuit may also include a speaker 40081, a microphone 40082, etc.

[0479] It should be understood that the processing device 4004 or processor 4001 can be a chip. For example, the processing device 4004 or processor 4001 can be a field-programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, a system-on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0480] The memory in this application (such as memory 4003) can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), 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 linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0481] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the method executed by the aforementioned terminal device.

[0482] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the method executed by the aforementioned network device.

[0483] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to execute the method executed by the aforementioned terminal device.

[0484] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to perform the method executed by the aforementioned network device.

[0485] According to the method provided in the embodiments of this application, this application also provides a system including a network device. Optionally, the system may further include a terminal device.

[0486] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.

[0487] It should be understood that the aforementioned processing device can be a chip. For example, the processing device can be a field-programmable gate array (FPGA), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, a system on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0488] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as 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, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. 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 via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0489] The terms “component,” “module,” “system,” etc., used in this specification are used to refer to 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, or a computer. As illustrated, applications running on computing devices and computing devices can both be components. One or more components may reside in a process or execution thread, and components may be located on a single computer or distributed among two or more computers. Furthermore, these components can be executed from various computer-readable media on which various data structures are stored. Components can communicate, for example, via local or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system, or a network, such as the Internet interacting with other systems via signals).

[0490] It should be understood that the term "embodiment" used throughout this specification means that a specific feature, structure, or characteristic related to an embodiment is included in at least one embodiment of this application. Therefore, various embodiments throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0491] It should be understood that in the embodiments of this application, the designations "first", "second", etc. are only for distinguishing different objects, such as different network devices, and do not constitute a limitation on the scope of the embodiments of this application. The embodiments of this application are not limited thereto.

[0492] It should also be understood that in this application, “when…”, “if” and “if” all refer to the network element making a corresponding processing under certain objective circumstances, and are not time-limited, nor do they require the network element to make a judgment when it is implemented, nor do they mean that there are other limitations.

[0493] It should also be understood that in this application, "at least one" means one or more, and "more than one" means two or more.

[0494] It should also be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0495] It should also be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0496] In this application, expressions such as "the item includes one or more of the following: A, B, and C" generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above example uses three elements, A, B, and C, to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

[0497] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0498] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0499] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0501] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0502] If the aforementioned functions are implemented as 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 portion of the 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 to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0503] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting a demodulation reference signal DMRS, characterized in that, include: Receive indication information, which indicates the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. The M DMRS ports correspond to a first time domain position and a second time domain position. The first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position. The first DMRS port set and the second DMRS port set contain some DMRS ports that are the same and some that are different. DMRS is sent on the scheduled DMRS port.

2. The method as described in claim 1, characterized in that, The first time-domain location and the second time-domain location are located in the same time slot or in different time slots.

3. The method as described in claim 2, characterized in that, The first time-domain location and the second time-domain location are located in the same time slot; Furthermore, the first time-domain location is used to send front-loaded DMRS, and / or the second time-domain location is used to send additional DMRS.

4. The method as described in claim 2, characterized in that, The first time-domain location and the second time-domain location are located in different time slots, and both the first time-domain location and the second time-domain location are used to transmit the front-loaded DMRS.

5. The method according to any one of claims 2 to 4, characterized in that, The configuration of the first DMRS port set and / or the configuration and time slots of the second DMRS port set meet predefined rules.

6. The method as described in claim 5, characterized in that, The predefined rules include: Time slots satisfying mod(m,2)=1 are configured only with the first DMRS port set, and / or time slots satisfying mod(m,2)=0 are configured only with the second DMRS port set. Where m is the m-th time slot among the multiple time slots corresponding to the scheduled uplink physical shared channel PUSCH; or, Time slots satisfying mod(m,2)=0 are configured only with the first DMRS port set, and / or time slots satisfying mod(m,2)=1 are configured only with the second DMRS port set. m is the index of the time slot.

7. The method according to any one of claims 1 to 4, characterized in that, The first DMRS port set includes DMRS ports with indices from 0 to 23; and, The second DMRS port set includes DMRS ports indexed 0 to 11 and 24 to 35.

8. The method according to any one of claims 1 to 4, characterized in that, Both the first time-domain position and the second time-domain position correspond to two symbols.

9. A method for receiving a demodulated reference signal DMRS, characterized in that, include: Send indication information, which is used to indicate the scheduled DMRS port. The scheduled DMRS port belongs to a DMRS port set, which contains M DMRS ports. The M DMRS ports correspond to a first time domain position and a second time domain position. The first DMRS port set corresponding to the first time domain position is different from the second DMRS port set corresponding to the second time domain position. The first DMRS port set and the second DMRS port set contain some DMRS ports that are the same and some that are different. DMRS is received on the scheduled DMRS port.

10. The method as described in claim 9, characterized in that, The first time-domain location and the second time-domain location are located in the same time slot or in different time slots.

11. The method as described in claim 10, characterized in that, The first time-domain location and the second time-domain location are located in the same time slot; Furthermore, the first time-domain location is used to send front-loaded DMRS, and / or the second time-domain location is used to send additional DMRS.

12. The method as described in claim 10, characterized in that, The first time-domain location and the second time-domain location are located in different time slots, and both the first time-domain location and the second time-domain location are used to transmit front-loaded DMRS.

13. The method according to any one of claims 10 to 12, characterized in that, The configuration of the first DMRS port set and / or the configuration and time slots of the second DMRS port set meet predefined rules.

14. The method as described in claim 13, characterized in that, The predefined rules include: Time slots satisfying mod(m,2)=1 are configured only with the first DMRS port set, and / or time slots satisfying mod(m,2)=0 are configured only with the second DMRS port set. Where m is the m-th time slot among the multiple time slots corresponding to the scheduled uplink physical shared channel PUSCH; or, Time slots satisfying mod(m,2)=0 are configured only with the first DMRS port set, and / or time slots satisfying mod(m,2)=1 are configured only with the second DMRS port set. m is the index of the time slot.

15. The method according to any one of claims 9 to 12, characterized in that, The first DMRS port set includes DMRS ports with indices from 0 to 23; and, The second DMRS port set includes DMRS ports indexed 0 to 11 and 24 to 35.

16. The method according to any one of claims 9 to 12, characterized in that, Both the first time-domain position and the second time-domain position correspond to two symbols.

17. A communication device, characterized in that, Includes units or modules for performing the method as described in any one of claims 1 to 8.

18. A communication device, characterized in that, It includes units or modules for performing the method as described in any one of claims 9 to 16.

19. A communication device, characterized in that, include: A memory for storing a program or instructions that, when executed by a processor, cause the apparatus to perform the method as described in any one of claims 1 to 8.

20. A communication device, characterized in that, include: A memory for storing a program or instructions that, when executed by a processor, cause the apparatus to perform the method as described in any one of claims 9 to 16.

21. A readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 8 or 9 to 16.

22. A computer program product, characterized in that, Includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 8 or 9 to 16.

Citation Information

Patent Citations

  • DMRS indicating and receiving method, transmitting end and receiving end

    CN109391456A

  • Data transmission method and communication device

    CN111049628A