A method and apparatus for indicating a DMRS port

Abstract

The embodiment of the application discloses a DMRS port indication method and device, the method comprises the following steps: in response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, determining a DMRS port configuration table for the first uplink data transmission layer based on a DMRS type parameter, wherein the DMRS port configuration table comprises a DMRS port allocation set defined for the first uplink data transmission layer; and based on the DMRS port configuration table, indicating one or more DMRS ports allocated for the physical uplink shared channel (PUSCH) transmission to the terminal device. In this way, the problem of allocating DMRS ports for a single terminal device when the uplink enhancement of the terminal device is up to 8 layers is solved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a DMRS port indication method and apparatus. Background Technology

[0002] To adapt to current business or scenarios, the uplink transmission layer of the terminal device can be increased to 8 layers to support a higher uplink transmission rate comparable to the downlink. When the uplink of the terminal device is enhanced to 8 layers, the problem that needs to be solved is how to allocate DMRS ports that support up to 8 layers in the enhanced Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform for Single User Multiple Input Multiple Output (SU-MIMO) uplink. Summary of the Invention

[0003] This application provides a DMRS port indication method and apparatus, which solves the problem of allocating DMRS ports to a single terminal device when the uplink of the terminal device is enhanced to layer 8.

[0004] In a first aspect, embodiments of this application provide a DMRS port indication method applicable to network devices. The method includes: responding to a maximum uplink data transmission layer N corresponding to a PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, determining a DMRS port configuration table for a first uplink data transmission layer based on DMRS type parameters, wherein the DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer; and indicating to the terminal device, based on the DMRS port configuration table, one or more DMRS ports allocated for physical uplink shared channel (PUSCH) transmission.

[0005] This application provides a DMRS port indication method. When a single terminal device supports a maximum of 8 uplink data transmission layers, a DMRS port configuration table is configured for the first uplink data transmission layer based on the DMRS type. Based on the configured DMRS port configuration table, one or more DMRS ports required for PUSCH transmission are allocated. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers and fills in the blanks in the DMRS port configuration table required for configuring new uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0006] Secondly, embodiments of this application provide a DMRS port indication method applicable to a terminal device. The method includes: responding to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by the terminal device being equal to 8 layers, determining a DMRS port configuration table for a first uplink data transmission layer based on DMRS type parameters, wherein the DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer; receiving indication information sent by a network device, and obtaining one or more DMRS ports allocated for the PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information.

[0007] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0008] Thirdly, embodiments of this application provide a communication device that implements some or all of the functions of the network device described in the example of the method described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0009] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0010] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0011] Fourthly, embodiments of this application provide another communication device that implements some or all of the functions of the terminal device described in the method example of the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0012] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0013] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0014] Fifthly, embodiments of this application provide a communication device including a processor, which executes the method described in the first aspect when it calls a computer program in memory.

[0015] In a sixth aspect, embodiments of this application provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0016] In a seventh aspect, embodiments of this application provide a communication device, which includes a processor and a memory, wherein the memory stores a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0017] Eighthly, embodiments of this application provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0018] Ninthly, embodiments of this application provide a communication device, the device including a processor and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processor, the processor being used to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0019] In a tenth aspect, embodiments of this application provide a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, which is used to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0020] Eleventhly, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the receiving device, which, when executed, cause the receiving device to perform the method described in the first aspect.

[0021] In a twelfth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the aforementioned transmitting device, which, when executed, cause the transmitting device to perform the method described in the second aspect. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0023] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0024] Figure 2 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0025] Figure 3 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0026] Figure 4 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0027] Figure 5 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0028] Figure 6 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0029] Figure 7 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0030] Figure 8 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0031] Figure 9 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0032] Figure 10 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0033] Figure 11 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application;

[0034] Figure 12 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0035] Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0036] Figure 14 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0038] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0039] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0040] For the sake of brevity and ease of understanding, this document uses the terms "greater than" or "less than", "higher than" or "lower than" to describe size relationships. However, it will be understood by those skilled in the art that the term "greater than" also includes the meaning of "greater than or equal to", and "less than" also includes the meaning of "less than or equal to"; the term "higher than" also includes the meaning of "higher than or equal to", and "lower than" also includes the meaning of "lower than or equal to".

[0041] To facilitate understanding, the terminology used in this application will be introduced first.

[0042] 1. Demodulation Reference Signal (DMRS)

[0043] DMRS, or Demodulation Reference Signal, is used for channel estimation and correlation demodulation of physical channels. DMRS can be mapped to physical channels such as PBCH, PDCCH, PDSCH, PUCCH, and PUSCH. In medium / high-speed scenarios, in addition to the front-load DMRS, more additional DMRS symbols need to be inserted during the scheduling duration to meet the estimation accuracy requirements for channel time-varying characteristics. New Radio (NR) systems employ a DMRS structure combining front-load DMRS with time-density configurable additional DMRS. The accuracy of channel estimation can be improved by configuring additional DMRS. Depending on the specific application scenario, up to three sets of additional DMRS can be configured in each scheduling session. The DMRS pattern is divided into two types: Type 1 and Type 2. In each type, the OFDM symbol length occupied by the DMRS can be either 1 or 2.

[0044] 2. DMRS port indicator

[0045] When network devices schedule data, such as scheduling Physical Uplink Shared Channel (PUSCH) data, they need to indicate the corresponding DMRS port, including the number of DMRS ports and the DMRS port number. The physical resources occupied by different DMRS ports with the same DMRS port number are orthogonal. Physical resources include one or more of spatial resources, time-domain resources and frequency-domain resources.

[0046] The design principles of the data channel (PDSCH / PUSCH) DMRS in NR systems mainly include the following aspects:

[0047] • Front-load DMRS: To reduce demodulation and decoding latency, the data channel (PDSCH / PUSCH) DMRS in NR systems employs a so-called front-load design. Within each scheduling time unit, the first occurrence of the DMRS should be as close as possible to the start of the scheduling. The use of front-load DMRS helps the receiver quickly estimate the channel and perform receiver detection, playing a crucial role in reducing latency and supporting a so-called self-contained structure. Depending on the total number of orthogonal DMRS ports, front-load DMRS can occupy a maximum of two consecutive OFDM symbols.

[0048] • Additional DMRS: For low-mobility scenarios, front-load DMRS can achieve channel estimation performance that meets demodulation requirements with lower overhead. However, NR systems consider mobility speeds up to 500 km / h. Faced with such a large dynamic range of mobility, in addition to front-load DMRS, more DMRS symbols need to be inserted within the scheduling duration in medium / high-speed scenarios to meet the estimation accuracy for time-varying channel characteristics. To address this issue, NR systems employ a DMRS structure combining front-load DMRS with additional DMRS whose time-domain density is configurable. Each additional DMRS pattern is a repetition of the front-load DMRS. Therefore, consistent with front-load DMRS, each additional DMRS group can occupy a maximum of two consecutive DMRS symbols. Depending on the specific use case, a maximum of three additional DMRS groups can be configured in each scheduling. The specific number of additional DMRS groups appearing within the scheduling time range depends on the configuration of higher-layer signaling, the actual scheduling length, and the number of symbols in the front-load DMRS.

[0049] Within each scheduling time unit, if additional DMRS exist, the pattern of each additional DMRS group is consistent with that of the front-load DMRS. Therefore, the pattern design of the front-load DMRS is the foundation of the DMRS design. The design approaches of the front-load DMRS are divided into two categories. The first type (type 1) adopts a COMB+OCC structure, and the second type (type 2) is based on an FDM+OCC structure.

[0050] Depending on the number of orthogonal ports used for transmission, front-load DMRS can be configured with a maximum of two OFDM symbols. Considering power utilization efficiency, when using two-symbol front-load DMRS, TD-OCC is used in the time domain in addition to CS or OCC in the frequency domain.

[0051] In medium / high-speed scenarios, in addition to the front-load DMRS, more DMRS symbols need to be inserted during the scheduling duration to meet the estimation accuracy of channel time-varying characteristics. The NR system employs a DMRS structure combining front-load DMRS with additional DMRS of configurable time-domain density. Each set of additional DMRS patterns is a repetition of the front-load DMRS. Therefore, consistent with front-load DMRS, each set of additional DMRS can occupy a maximum of two consecutive DMRS symbols. Depending on the specific use case, a maximum of three sets of additional DMRS can be configured in each scheduling session. The number of additional DMRS depends on the higher-layer parameter configuration and the specific scheduling duration.

[0052] Currently, the protocol only supports uplink transmission up to a maximum of 4 layers, while downlink supports up to 8 layers. However, future versions will include uplink enhancements to increase the number of transmit antennas to a maximum of 8 antennas, in order to support higher uplink transmission rates comparable to downlink.

[0053] The current protocol supports up to 4 layers of DMRS port allocation in the uplink, but cannot support coherent demodulation at higher RANKs under SU. It is necessary to enhance the SU-MIMO uplink under CP-OFDM waveform to support up to 8 layers of DMRS port allocation.

[0054] To better understand the DMRS port indication method disclosed in the embodiments of this application, the communication system to which the embodiments of this application are applicable is described below.

[0055] This application provides a communication system, which may include, but is not limited to, a transmitting device and a receiving device. Optionally, the transmitting device may be a terminal device, and the receiving device may be a network device.

[0056] Please see Figure 1 , Figure 1 This application provides a schematic diagram of the architecture of a communication system according to an embodiment. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. In actual applications, it may include two or more network devices and two or more terminal devices. Figure 1 The communication system shown is an example including a network device 11 and a terminal device 12.

[0057] It should be noted that the technical solutions of this application embodiment can be applied to various communication systems. For example, long term evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems, etc.

[0058] The network device 11 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 11 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This embodiment does not limit the specific technology or device form used in the network device. The network device provided in this embodiment can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0059] In this embodiment, the terminal device 12 is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be called a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. Terminal devices can be communication-enabled vehicles, smart cars, mobile phones, IoT devices such as NB-IoT or (e)MTC, wearable devices, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, wireless terminal devices in remote medical surgery, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, wireless terminal devices in smart homes, and so on. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0060] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0061] The following is a detailed description of a DMRS port indication method and apparatus provided in this application, with reference to the accompanying drawings.

[0062] Please see Figure 2 , Figure 2 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 2 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0063] Step S21: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0064] Here, the first uplink data transmission layer is a newly added uplink data transmission layer based on the uplink data transmission layer corresponding to the original PUSCH shared channel transmission supported by a single terminal. For example, if the original uplink data transmission layer corresponding to PUSCH was layers 1-4, and a new layer 8 is added, then the first uplink transmission layer consists of layers 5 to 8. The original uplink data transmission layer corresponding to PUSCH is the second uplink data transmission layer, which is layers 1-4. This definition applies to all embodiments of this disclosure.

[0065] It should be noted that the number of uplink data transmission layers for a single terminal device has increased from 4 to 8 layers. The uplink data transmission layers include the newly added first uplink data transmission layer and the existing second uplink data transmission layer. The first uplink data transmission layer includes layers with Rank Indicator (RI) values ​​of 5, 6, 7, and 8, i.e., RI=5, RI=6, RI=7, and RI=8. The second uplink data transmission layer includes layers with RI values ​​of 1, 2, 3, and 4, i.e., RI=1, RI=2, RI=3, and RI=4. The second uplink data transmission layer is an existing data transmission layer, including the existing layers 1, 2, 3, and 4. Different RI values ​​correspond to different uplink data transmission layers.

[0066] In this embodiment, the DMRS type parameter may include the DMRS type, or the DMRS type and the maximum number of preceding DMRS symbols, etc. The DMRS type includes type 1 and type 2, and the maximum number of preceding DMRS symbols may be one or two. Combining the type and the maximum number of preceding DMRS symbols yields four DMRS type parameters: DMRS type 1, FLDMRS = 1; DMRS type 1, FL DMRS = 2; DMRS type 2, FL DMRS = 1; DMRS type 2, FL DMRS = 2.

[0067] Optionally, the DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer. This set of DMRS port allocations includes one or more DMRS ports available to the first uplink data transmission layer.

[0068] Optionally, the DMRS port configuration table may also include one or more parameters from the DMRS type parameters, such as the DMRS type, or the maximum number of front-end DMRS symbols, or both the DMRS type and the maximum number of front-end DMRS symbols.

[0069] Optionally, the DMRS port configuration table may also include the number of code division multiplexing (CDM) that do not carry data.

[0070] Optionally, the row number in the DMRS port configuration table can be used to index one or more DMRS ports.

[0071] As one possible implementation, for each first uplink data transmission layer, a first DMRS port configuration table corresponding to different DMRS type parameters can be generated for the first uplink data transmission layer. That is, for each first uplink data transmission layer, multiple first DMRS port configuration tables can be configured, where each first DMRS port configuration table corresponds to one DMRS type parameter.

[0072] It should be noted that when the DMRS type is type 1 and the maximum number of symbols in the front-end DMRS is 1, the network device cannot configure the DMRS port allocation table for the first uplink transport layer, i.e., layers 5-8, because the maximum number of allocable ports is 4.

[0073] For example, when RI=5, with DMRS type 1 and FL DMRS=2, a first DMRS port configuration table 1 can be generated; with DMRS type 2 and FL DMRS=1, a first DMRS port configuration table 2 can be generated; and with DMRS type 2 and FL DMRS=2, a first DMRS port configuration table 3 can be generated.

[0074] For example, with RI=5, the first DMRS port configuration table for DMRS type 1 and FL DMRS=2 is shown in Table 1 below:

[0075] Table 1

[0076]

[0077] For RI=6, with DMRS type 1 and FL DMRS=2, a first DMRS port configuration table 4 can be generated; with DMRS type 2 and FL DMRS=1, a first DMRS port configuration table 5 can be generated; with DMRS type 2 and FL DMRS=2, a first DMRS port configuration table 6 can be generated.

[0078] For example, with RI=6, the first DMRS port configuration table for DMRS type 1 and FL DMRS=2 is shown in Table 2 below:

[0079] Table 2

[0080]

[0081] For RI=7, with DMRS type 1 and FL DMRS=2, a first DMRS port configuration table 7 can be generated; with DMRS type 2 and FL DMRS=1, a first DMRS port configuration table 8 can be generated; with DMRS type 2 and FL DMRS=2, a first DMRS port configuration table 9 can be generated.

[0082] For example, with RI=7, the first DMRS port configuration table for DMRS type 1 and FL DMRS=2 is shown in Table 3 below:

[0083] Table 3

[0084]

[0085] For RI=8, with DMRS type 1 and FL DMRS=2, a first DMRS port configuration table 10 can be generated; with DMRS type 2 and FL DMRS=1, a first DMRS port configuration table 11 can be generated; with DMRS type 2 and FL DMRS=2, a first DMRS port configuration table 12 can be generated.

[0086] For example, with RI=8, the first DMRS port configuration table for DMRS type 1 and FL DMRS=2 is shown in Table 4 below:

[0087] Table 4

[0088]

[0089] Optionally, the first DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0090] Optionally, the total number of the first DMRS port configuration tables is 10.

[0091] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the Downlink Control Information (DCI). For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated by 4 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0092] As another possible implementation, for each DMRS type parameter, a second DMRS port configuration table corresponding to that DMRS type parameter is generated. This second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers. In other words, each DMRS type parameter corresponds to one second DMRS port configuration table, and each second DMRS port configuration table includes first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0093] Example illustration,

[0094] For DMRS type type 1, FL DMRS=2, a second DMRS port configuration table 1 can be generated, which includes the first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0095] For DMRS type type 2, FL DMRS=1, a second DMRS port configuration table 2 can be generated, which includes the first DMRS port configuration sub-tables for each of the first uplink data transmission layers, such as RI=5, RI=6, RI=7, and RI=8.

[0096] For DMRS type type 2, FL DMRS=2, a second DMRS port configuration table 3 can be generated, which includes the first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0097] For example, the configuration table for the second DMRS port when DMRS type is type 1 and FL DMRS = 2 is shown in Table 5 below:

[0098] Table 5

[0099]

[0100] Optionally, the second DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0101] Optionally, when the DMRS type is type 1 and the maximum number of symbols in the front-end DMRS is 1, since the maximum number of allocable ports is 4, the network device cannot configure the DMRS port allocation table for the first uplink transport layer, i.e., layers 5-8. Therefore, the total number of the second DMRS port configuration tables is 3.

[0102] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the DCI. For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated by 4 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0103] As another possible implementation, a general third DMRS port configuration table is generated. Optionally, the third DMRS port configuration table includes second DMRS port configuration sub-tables for each first uplink data transmission layer under each DMRS type parameter; alternatively, the third DMRS port configuration table includes third DMRS port configuration sub-tables for each type of DMRS type parameter under each first uplink data transmission layer. That is, for first uplink data transmission with RI>4, i.e., RI=5 / 6 / 7 / 8, a single third DMRS port configuration table can be consulted.

[0104] For example, the configuration table for the third DMRS port is shown in Table 6 below:

[0105] Table 6

[0106]

[0107] Optionally, the third DMRS port configuration table may have the same or different table format as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4, and the configuration entries included in the third DMRS port configuration table may differ from those in the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4. The third DMRS port configuration table includes a total of 32 entries.

[0108] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the DCI. For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 32, meaning the DMRS port indication field in the DCI can be indicated by 8 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0109] Step S22: Based on the DMRS port configuration table, indicate to the terminal device one or more DMRS ports allocated for PUSCH transmission.

[0110] In this embodiment of the application, the DMRS port configuration table for the terminal device can be 12 first DMRS port configuration tables, 3 second DMRS port configuration tables, or 1 third DMRS port configuration table. The network device adopts one of the above implementation methods to configure the corresponding DMRS port configuration table for a single terminal device.

[0111] When scheduling PUSCH transmissions from terminal devices, it is necessary to allocate usable DMRS ports for the PUSCH transmissions. Network devices can determine the DMRS ports allocated for PUSCH transmissions from the DMRS port configuration table based on the DMRS type parameters used by the terminal devices for PUSCH transmissions and the first uplink data transmission layer used. Optionally, one or more DMRS ports can be allocated, where multiple DMRS ports can be a combination of DMRS ports. That is, a single DMRS port or a combination of DMRS ports can be allocated for PUSCH transmissions. Specifically, one or more DMRS ports can be selected from the predefined set of DMRS ports corresponding to the first uplink data transmission layer used.

[0112] After determining that a DMRS port or DMRS port combination is allocated for PUSCH transmission, the DMRS port indication field indicates the allocated DMRS port to the terminal device, enabling the terminal device to use the allocated DMRS port or DMRS port combination for PUSCH transmission with the network device. Optionally, the DMRS port indication field in the downlink control command (DCI) indicates the allocated DMRS port or DMRS port combination to the terminal device. The DMRS port indication field indicates the number of bits used by the allocated DMRS port or DMRS port combination, determined by the total number of entries in the DMRS port configuration table. In some implementations, DCI0-1 / 0-2 can be used to indicate the allocated DMRS port or DMRS port combination to the terminal device.

[0113] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0114] Please see Figure 3 , Figure 3 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 3 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0115] Step S31: In response to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter.

[0116] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0117] The DMRS port allocation set includes one or more DMRS ports. In all embodiments of this disclosure, the DMRS port allocation set contains the same content, namely, one or more DMRS ports.

[0118] The specific implementation of step S31 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0119] Step S32: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0120] In this embodiment, the DMRS type parameter may include the DMRS type, or the DMRS type and the maximum number of preceding DMRS symbols, etc. The DMRS type includes type 1 and type 2, and the maximum number of preceding DMRS symbols may be one or two. Combining the type and the maximum number of preceding DMRS symbols yields four DMRS type parameters: DMRS type 1, FLDMRS = 1; DMRS type 1, FL DMRS = 2; DMRS type 2, FL DMRS = 1; DMRS type 2, FL DMRS = 2.

[0121] When performing PUSCH transmission, the terminal device uses one of the above-mentioned type parameters, and the first uplink data transmission layer used is one of the newly added layers RI=5, RI=6, RI=7, and RI=8. For example, the target DMRS type parameter can be DMRS type 1, FL DMRS=2, and RI=5, which is the newly added 5th uplink data transmission layer.

[0122] Optionally, the network device may explicitly or implicitly determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission. For example, based on protocol agreements or upper-layer instructions.

[0123] Optionally, the network device may explicitly or implicitly indicate to the terminal device the target DMRS type parameters and the target first uplink data transmission layer used for PUSCH transmission.

[0124] Step S33: Based on the target DMRS type parameters and the target first uplink data transmission layer, determine one or more DMRS ports allocated for PUSCH transmission.

[0125] As one possible implementation, the DMRS port configuration table is designated as the first DMRS port configuration table. Since there are multiple first DMRS port configuration tables, the target first DMRS port configuration table can be determined from these multiple first DMRS port configuration tables based on the target DMRS type parameter and the target first uplink data transmission layer. For example, if the DMRS type is type 1, FL DMRS = 2, and RI = 5, the first DMRS port configuration table 1 can be determined from the 12 first DMRS port configuration tables as the target first DMRS port configuration table. The DMRS ports in the target first DMRS port configuration table are then designated as one or more DMRS ports allocated for PUSCH transmission. Referring to Table 1, DMRS ports 0 to 4 can be designated as DMRS ports allocated for PUSCH transmission.

[0126] As another possible implementation, the DMRS port configuration table is a second DMRS port configuration table. Since there are multiple second DMRS port configuration tables, and each second DMRS port configuration table also includes first DMRS port configuration sub-tables for layers RI=5 / 6 / 7 / 8, in this embodiment, the target first DMRS port configuration sub-table can be determined from multiple second DMRS port configuration tables based on the target DMRS type parameter and the target first uplink data transmission layer. For example, if the DMRS type is type 1, FL DMRS=2, and RI=5, the first DMRS port configuration sub-table corresponding to RI=5 in second DMRS port configuration table 1 can be determined from the 12 first DMRS port configuration tables. The DMRS ports in the target first DMRS port configuration sub-table are then identified as one or more DMRS ports allocated for PUSCH transmission. Referring to Table 5, DMRS ports 0 to 4 are identified as DMRS ports allocated for PUSCH transmission.

[0127] As another possible implementation, in the embodiment of this application, where the DMRS port configuration table is the third DMRS port configuration table, the target second DMRS port configuration sub-table or the third DMRS port configuration sub-table can be determined from the third DMRS port configuration table based on the target DMRS type parameter and the target first uplink data transmission layer.

[0128] For example, the DMRS type is type 1, FL DMRS = 2, and RI = 5:

[0129] When the third DMRS port configuration table includes the form of second DMRS port configuration sub-tables for each first uplink data transmission layer under the DMRS type parameter, the second DMRS port configuration sub-tables corresponding to RI=5 / 6 / 7 / 8 in the third DMRS port configuration table can be determined from the third DMRS port configuration table based on DMRS type 1 and FL DMRS=2. The second DMRS port configuration sub-table corresponding to RI=5 is then used as the target second DMRS port configuration sub-table. Further, the DMRS ports in the target second DMRS port configuration sub-table are determined as one or more DMRS ports allocated for PUSCH transmission. Referring to Table 6, DMRS ports 0 to 4 are determined as DMRS ports allocated for PUSCH transmission.

[0130] When the content of the third DMRS port configuration table is in the form of: the third DMRS port configuration sub-table corresponding to various DMRS type parameters of the first uplink data transmission layer, the third DMRS port configuration sub-table corresponding to different DMRS parameter types in the third DMRS port configuration table can be determined from the third DMRS port configuration table based on RI=5. The third DMRS port configuration sub-table corresponding to DMRS type 1 and FL DMRS=2 is used as the target third DMRS port configuration sub-table. The DMRS ports in the target third DMRS port configuration sub-table are determined as one or more DMRS ports allocated for PUSCH transmission. Referring to Table 6, DMRS ports 0 to 4 are determined as DMRS ports allocated for PUSCH transmission.

[0131] Step S34: Indicate one or more DMRS ports to the terminal device.

[0132] After determining that a DMRS port or a combination of DMRS ports is allocated for PUSCH transmission, the DMRS port indicator is used to indicate the allocated DMRS port to the terminal device, so that the terminal device can use the allocated DMRS port or combination of DMRS ports to perform PUSCH transmission with the network device.

[0133] Optionally, the DMRS port indication field in the downlink control command (DCI) indicates to the terminal device one or more DMRS ports allocated for PUSCH transmission, wherein the multiple DMRS ports can be a combination of DMRS ports. In some implementations, DCI0-1 / 0-2 can be used to indicate to the terminal device a single DMRS port or a combination of ports allocated for PUSCH transmission.

[0134] Optionally, the number of bits occupied by the port indication field is determined by the protocol based on protocol conventions, network configuration, or DMRS type parameters. In some implementations, the DMRS port indication field indicates the number of bits used by the one or more DMRS ports, determined by the total number of entries in the DMRS port configuration table.

[0135] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring the DMRS port configuration table for the first uplink data transmission layer, and fills in the blanks in the DMRS port configuration table required for the first uplink data transmission layer configuration, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate the required DMRS ports for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0136] Please see Figure 4 , Figure 4 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 4 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0137] Step S41: In response to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0138] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0139] For each first uplink data transmission layer, a first DMRS port configuration table can be generated corresponding to different DMRS type parameters. In other words, multiple first DMRS port configuration tables can be configured for each first uplink data transmission layer, with each first DMRS port configuration table corresponding to a type of DMRS parameter.

[0140] Optionally, the first DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0141] Optionally, the total number of the first DMRS port configuration tables is 10.

[0142] Step S42: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0143] The specific implementation of step S42 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0144] Optionally, the network device may explicitly or implicitly determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission. For example, based on protocol agreements or upper-layer instructions.

[0145] Optionally, the network device may explicitly or implicitly indicate the target DMRS type parameters and / or the target first uplink data transmission layer to the terminal device.

[0146] Step S43: Based on the target DMRS type parameter and the first parameter in the target first uplink data transmission layer, determine the candidate first DMRS port configuration table from the first DMRS port configuration table.

[0147] Step S44: Based on the target DMRS type parameter and the second parameter in the target first uplink data transmission layer, determine the target first DMRS port configuration table from the candidate first DMRS port configuration table.

[0148] In some implementations, when a network device determines from the first DMRS port configuration table that the DMRS type parameter is the target DMRS type parameter, it uses the first DMRS port configuration tables of different RIs corresponding to the target DMRS type parameter as candidate first DMRS port configuration tables.

[0149] Example illustration: Taking a target DMRS type parameter where DMRS type is type 1, FL DMRS=2, and the target first uplink data transmission layer is RI=5 as an example, the network device determines the first DMRS port configuration tables with different RIs under DMRS type 1 and FL DMRS=2 from 12 first DMRS port configuration tables, as candidate first DMRS port configuration tables. The candidate first DMRS port configuration tables include:

[0150] RI=5, DMRS type is type 1, FL DMRS=2 corresponds to the first DMRS port configuration table 1;

[0151] RI=6, DMRS type is type 1, FL DMRS=2 corresponds to the first DMRS port configuration table 4;

[0152] RI=7, DMRS type is type 1, FL DMRS=2 corresponds to the first DMRS port configuration table 7;

[0153] RI=8, DMRS type is type 1, FL DMRS=2 corresponds to the first DMRS port configuration table 10.

[0154] Furthermore, the network device determines the target first DMRS port configuration table from the candidate first DMRS port configuration table based on the target first uplink data transmission layer. Continuing the above example, the determined candidate first DMRS port configuration tables include: first DMRS port configuration table 1, first DMRS port configuration table 4, first DMRS port configuration table 7, and first DMRS port configuration table 10. Since RI=5 for first DMRS port configuration table 1, first DMRS port configuration table 1 is determined as the target first DMRS port configuration table.

[0155] In other implementations, the network device determines the first DMRS port configuration table under different DMRS type parameters corresponding to the target first uplink data transmission layer from the first DMRS port configuration table, and uses it as a candidate first DMRS port configuration table.

[0156] Example illustration: Taking a target DMRS type parameter where DMRS type is type 1, FL DMRS=2, and the target first uplink data transmission layer is RI=5 as an example, the network device determines the first DMRS port configuration tables for different DMRS parameter types when RI=5 from the 12 first DMRS port configuration tables, as candidate first DMRS port configuration tables. The candidate first DMRS port configuration tables include:

[0157] RI=5, DMRS type is type 1, FL DMRS=2 corresponds to the first DMRS port configuration table 1;

[0158] RI=5, DMRS type is type 2, FL DMRS=1 corresponds to the first DMRS port configuration table 2;

[0159] RI=5, DMRS type is type 2, FL DMRS=2 corresponds to the first DMRS port configuration table 3.

[0160] Furthermore, the network device determines the target first DMRS port configuration table from the candidate first DMRS port configuration tables based on the target DMRS type parameter. Continuing the example above, the determined candidate first DMRS port configuration tables include: first DMRS port configuration table 1, first DMRS port configuration table 2, and first DMRS port configuration table 3. Since RI=5 for first DMRS port configuration table 1, first DMRS port configuration table 1 is determined as the target first DMRS port configuration table.

[0161] Step S45: Based on the target first DMRS port configuration table, determine one or more DMRS ports allocated for PUSCH transmission.

[0162] After determining the target first DMRS port configuration table, the DMRS ports in the target first DMRS port configuration table are identified as one or more DMRS ports allocated for PUSCH transmission. Continuing the above example, the target first DMRS port configuration table is the first DMRS port configuration table 1. You can refer to Table 1 to identify DMRS ports 0 to 4 as DMRS ports allocated for PUSCH transmission.

[0163] Step S46: Indicate one or more DMRS ports to the terminal device.

[0164] Optionally, the DMRS port indication field in the downlink control command (DCI) indicates to the terminal device one or more DMRS ports allocated for PUSCH transmission. In some implementations, DCI0-1 / 0-2 may be used to indicate to the terminal device one or more DMRS ports allocated for PUSCH transmission.

[0165] The DMRS port indication field in the DCI includes a port index value, which indicates the port index value of the one or more DMRS ports. Optionally, the port index value is a row index of a target DMRS port configuration sub-table, or an index offset, based on which the actual port index value can be determined.

[0166] Optionally, the DMRS port indication field in the DCI indicates to the terminal device one or more DMRS ports allocated for PUSCH transmission, wherein multiple DMRS ports can be a combination of DMRS ports. In some implementations, the DMRS port indication field indicates the number of bits used by the one or more DMRS ports, determined by the total number of entries occupied in the DMRS port configuration table. For example, for DMRS type 1, FL DMRS = 2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated by 4 bits.

[0167] Optionally, the first DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4. That is, the number of bits occupied by the DMRS port indication field in the DCI is the same as the number of bits used by one or more DMRS ports in the DMRS port configuration table corresponding to the second uplink data transmission layer.

[0168] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0169] Please see Figure 5 , Figure 5 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 5 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0170] Step S51: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0171] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0172] For each DMRS type parameter, a second DMRS port configuration table corresponding to that DMRS type parameter is generated. This second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers. In other words, each DMRS type parameter corresponds to one second DMRS port configuration table, and each second DMRS port configuration table includes first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0173] Optionally, the second DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0174] Optionally, the total number of second DMRS port configuration tables is 3.

[0175] Step S52: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0176] The specific implementation of step S52 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0177] Optionally, the network device may explicitly or implicitly determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission. For example, based on protocol agreements or upper-layer instructions.

[0178] Optionally, the network device may explicitly or implicitly indicate the target DMRS type parameters and / or the target first uplink data transmission layer to the terminal device.

[0179] Step S53: Based on the target DMRS type parameter, determine the candidate second DMRS port configuration table from the second DMRS port configuration table.

[0180] Step S54: Based on the target first uplink data transmission layer, determine the target first DMRS port configuration sub-table from the candidate second DMRS port configuration table.

[0181] In some implementations, the network device determines the second DMRS port configuration table corresponding to the target DMRS type parameter from multiple configured second DMRS port configuration tables, and uses it as a candidate second DMRS port configuration table.

[0182] For example, if the target DMRS type parameter can be DMRS type 1, FL DMRS=2, and the target first uplink data transmission layer is RI=5, the network device determines the second DMRS port configuration table 1 corresponding to DMRS type 1 and FL DMRS=2 from the three second DMRS port configuration tables, and uses it as the candidate second DMRS port configuration table.

[0183] Furthermore, the network device determines the target first DMRS port configuration sub-table from the candidate second DMRS port configuration table based on the target first uplink data transmission layer. Since the candidate second DMRS port configuration table includes first DMRS port configuration sub-tables with RI=5, RI=6, RI=7, and RI=8, the network device can determine the first DMRS port configuration sub-table corresponding to the target first uplink data transmission layer as the target first DMRS port configuration sub-table.

[0184] Continuing with the example above, the candidate second DMRS port configuration table includes: first DMRS port configuration sub-table 1 corresponding to RI=5, first DMRS port configuration sub-table 2 corresponding to RI=6, first DMRS port configuration sub-table 3 corresponding to RI=7, and first DMRS port configuration sub-table 4 corresponding to RI=8. Since the target first uplink data transmission layer is RI=5, first DMRS port configuration sub-table 1 corresponding to RI=5 is determined as the target first DMRS port configuration sub-table.

[0185] Step S55: Based on the target first DMRS port configuration sub-table, determine one or more DMRS ports allocated for PUSCH transmission.

[0186] After determining the target first DMRS port configuration sub-table, the DMRS ports in the target first DMRS port configuration sub-table are identified as one or more DMRS ports allocated for PUSCH transmission. Continuing the above example, the target first DMRS port configuration sub-table is the first DMRS port configuration sub-table 1. You can refer to Table 5 to identify DMRS ports 0 to 4 as DMRS ports allocated for PUSCH transmission.

[0187] Step S56: Indicate one or more DMRS ports to the terminal device.

[0188] Optionally, the DMRS port indication field in the downlink control command (DCI) indicates to the terminal device one or more DMRS ports allocated for PUSCH transmission. These multiple DMRS ports can be a combination of DMRS ports. The DMRS port indication field in the DCI includes a port index value, which indicates the port index value of the one or more DMRS ports. Optionally, the port index value is a row index of a target DMRS port configuration sub-table, or an index offset, based on which the actual port index value can be determined.

[0189] For details on how the DMRS port indication field in the DCI indicates the DMRS port allocated for PUSCH transmission to the terminal device, please refer to the relevant descriptions in the embodiments of this application, which will not be repeated here.

[0190] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring the DMRS port configuration table for the first uplink data transmission layer, and fills in the blanks in the DMRS port configuration table required for the first uplink data transmission layer configuration, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate the required DMRS ports for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0191] Please see Figure 6 , Figure 6 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 6 As shown, this method is executed by a network device and may include, but is not limited to, the following steps:

[0192] Step S61: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0193] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0194] A general third DMRS port configuration table is generated. Optionally, the third DMRS port configuration table includes second DMRS port configuration sub-tables for each first uplink data transmission layer under each DMRS type parameter. Optionally, the third DMRS port configuration table includes third DMRS port configuration sub-tables for each type of DMRS type parameter under each first uplink data transmission layer. That is, for first uplink data transmission with RI>4 (i.e., RI=5 / 6 / 7 / 8), a single third DMRS port configuration table can be consulted.

[0195] Optionally, the third DMRS port configuration table may have the same or different table format as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4, and the configuration entries included in the third DMRS port configuration table may differ from those in the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4. The third DMRS port configuration table includes a total of 32 entries.

[0196] Step S62: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0197] The specific implementation of step S62 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0198] Optionally, the network device may explicitly or implicitly determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission. For example, based on protocol agreements or upper-layer instructions.

[0199] Optionally, the network device may explicitly or implicitly indicate the target DMRS type parameters and / or the target first uplink data transmission layer to the terminal device.

[0200] Step S63: Based on the target DMRS type parameter and the target first uplink data transmission layer, determine the target DMRS port configuration sub-table from the third DMRS port configuration table.

[0201] The target DMRS port configuration sub-table is either a second DMRS port configuration sub-table within the third DMRS port configuration table or a third DMRS port configuration sub-table within the third DMRS port configuration table.

[0202] When the third DMRS port configuration table includes the second DMRS port configuration sub-tables for each first uplink data transmission layer under the DMRS type parameter, candidate second DMRS port configuration sub-tables can be determined from the third DMRS port configuration table based on the target DMRS type parameter, and used as candidate DMRS port configuration sub-tables. Further, based on the target first uplink data transmission layer, the target second DMRS port configuration sub-table is determined from the determined candidate second DMRS port configuration sub-tables, and used as the target DMRS port configuration sub-table.

[0203] When the third DMRS port configuration table includes sub-tables of third DMRS port configurations corresponding to various DMRS type parameters of the first uplink data transmission layer, candidate third DMRS port configuration sub-tables can be determined from the third DMRS port configuration table based on the target first uplink data transmission layer, and used as candidate DMRS port configuration sub-tables. Further, based on the target DMRS type parameters, the target third DMRS port configuration sub-table is determined from the determined candidate third DMRS port configuration sub-tables, and used as the target DMRS port configuration sub-table.

[0204] Examples and descriptions can be found in the relevant content described in the above embodiments, and will not be repeated here.

[0205] Step S64: Based on the target DMRS port configuration sub-table, determine one or more DMRS ports allocated for PUSCH transmission.

[0206] After determining the target DMRS port configuration sub-table, the DMRS ports in the target DMRS port configuration sub-table are identified as one or more DMRS ports allocated for PUSCH transmission.

[0207] Step S65: Indicate one or more DMRS ports to the terminal device.

[0208] Optionally, the terminal device is instructed to use the DMRS port indication field in the downlink control command (DCI) to indicate one or more DMRS ports. The multiple DMRS ports can be a combination of DMRS ports. The port indication field contains a port index value, which indicates the port index value of the one or more DMRS ports. Optionally, the port index value can be a row index of a target DMRS port configuration sub-table, or an index offset. The actual port index value can be determined based on the starting index value and the row offset.

[0209] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits used to indicate the port in the DCI. For example, for DMRS type 1, FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 32, meaning the DMRS port indication field in the DCI can be indicated by 8 bits. In other words, when the DMRS port configuration table is the third DMRS port configuration table, the number of bits in the DMRS port indication field is greater than the number of bits used to indicate one or more DMRS ports in the DMRS port configuration table corresponding to the second uplink data transmission layer.

[0210] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0211] Please see Figure 7 , Figure 7 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 7 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0212] Step S71: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0213] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0214] In this application, the description of DMRS type parameters and the first uplink data transmission layer can be found in the relevant descriptions in the various embodiments of this application, and will not be repeated here.

[0215] Optionally, the DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer. The DMRS port set includes one or more DMRS ports available to the first uplink data transmission layer, wherein the multiple DMRS ports can be a combination of DMRS ports.

[0216] Optionally, the DMRS port configuration table may also include one or more parameters from the DMRS type parameters, such as the DMRS type, or the maximum number of front-end DMRS symbols, or both the DMRS type and the maximum number of front-end DMRS symbols.

[0217] Optionally, the DMRS port configuration table may also include the number of code division multiplexing (CDM) that do not carry data.

[0218] Optionally, the row number in the DMRS port configuration table can be used to index one or more DMRS ports.

[0219] As one possible implementation, for each first uplink data transmission layer, a first DMRS port configuration table corresponding to different DMRS type parameters can be generated for the first uplink data transmission layer. That is, for each first uplink data transmission layer, multiple first DMRS port configuration tables can be configured, where each first DMRS port configuration table corresponds to a type of DMRS type parameter.

[0220] Optionally, the first DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0221] Optionally, the total number of the first DMRS port configuration tables is 10.

[0222] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the Downlink Control Information (DCI). For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated by 4 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0223] As another possible implementation, for each DMRS type parameter, a second DMRS port configuration table corresponding to that DMRS type parameter is generated. This second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers. In other words, each DMRS type parameter corresponds to one second DMRS port configuration table, and each second DMRS port configuration table includes first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0224] Optionally, the second DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0225] Optionally, the total number of second DMRS port configuration tables is 3.

[0226] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the DCI. For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated by 4 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0227] As another possible implementation, a general third DMRS port configuration table is generated. Optionally, the third DMRS port configuration table includes second DMRS port configuration sub-tables for each first uplink data transmission layer under each DMRS type parameter; alternatively, the third DMRS port configuration table includes third DMRS port configuration sub-tables for each type of DMRS type parameter under each first uplink data transmission layer. That is, for first uplink data transmission with RI>4, i.e., RI=5 / 6 / 7 / 8, a single third DMRS port configuration table can be consulted.

[0228] Optionally, the third DMRS port configuration table may have the same or different table format as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4, and the configuration entries included in the third DMRS port configuration table may differ from those in the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4. The third DMRS port configuration table includes a total of 32 entries.

[0229] Optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits indicating the port in the DCI. For example, with DMRS type 1 and FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 32, meaning the DMRS port indication field in the DCI can be indicated by 8 bits. In some implementations, DCI0-1 / 0-2 can be used to indicate the port to the terminal device.

[0230] For an exemplary description of the above implementation method, please refer to the relevant content in the above embodiments, which will not be repeated here.

[0231] Step S72: Receive indication information sent by the network device, and obtain one or more DMRS ports allocated for PUSCH transmission from the DMRS port configuration table based on the indication information.

[0232] Once the network device determines that it has allocated a DMRS port or a combination of DMRS ports for PUSCH transmission, it can indicate the allocated DMRS port to the terminal device via the DMRS port indicator, so that the terminal device can use the allocated DMRS port or combination of DMRS ports to perform PUSCH transmission with the network device.

[0233] Optionally, the network device indicates to the terminal device a DMRS port or combination of DMRS ports allocated for PUSCH transmission via the DMRS port indication field in the downlink control command (DCI). Accordingly, the terminal device can receive the DCI, obtain the DMRS port indication field from it, and then determine one or more DMRS ports allocated for PUSCH transmission.

[0234] The DMRS port indication field indicates the number of bits used by the DMRS port or DMRS port combination, determined by the total number of entries occupied in the DMRS port configuration table. In some implementations, DCI0-1 / 0-2 can be used to indicate to the terminal device a DMRS port or port combination allocated for PUSCH transmission.

[0235] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0236] Please see Figure 8 , Figure 8 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 8 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0237] Step S81: In response to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0238] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0239] The specific implementation of step S31 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0240] Step S82: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0241] In this application, the description of DMRS type parameters and the first uplink data transmission layer can be found in the relevant descriptions in the various embodiments of this application, and will not be repeated here.

[0242] In this embodiment, the terminal device uses one of the above-mentioned type parameters when performing PUSCH transmission, and the first uplink data transmission layer used is one of the newly added layers RI=5, RI=6, RI=7, and RI=8. For example, the target DMRS type parameter can be DMRS type 1, FL DMRS=2, and RI=5, which is the newly added 5th uplink data transmission layer.

[0243] Optionally, the terminal device may explicitly or implicitly determine the target DMRS type parameters and the target first uplink data transmission layer used for PUSCH transmission.

[0244] Step S83: Based on the target DMRS type parameters and the target first uplink data transmission layer, determine the DMRS port configuration table to be indexed from the DMRS port configuration table.

[0245] As one possible implementation, the DMRS port configuration table is the first DMRS port configuration table. Since there are multiple first DMRS port configuration tables, the target first DMRS port configuration table can be determined from the multiple first DMRS port configuration tables based on the target DMRS type parameter and the target first uplink data transmission layer, and used as the DMRS port configuration table to be indexed.

[0246] As another possible implementation, the DMRS port configuration table is a second DMRS port configuration table. Since there are multiple second DMRS port configuration tables, and each second DMRS port configuration table also includes a first DMRS port configuration sub-table for layers RI=5 / 6 / 7 / 8, in this embodiment of the application, the target first DMRS port configuration sub-table can be determined from the multiple second DMRS port configuration tables based on the target DMRS type parameter and the target first uplink data transmission layer, and used as the DMRS port configuration table to be indexed.

[0247] As another possible implementation, in the embodiment of this application, where the DMRS port configuration table is the third DMRS port configuration table, the target second DMRS port configuration sub-table or the third DMRS port configuration sub-table can be determined from the third DMRS port configuration table based on the target DMRS type parameter and the target first uplink data transmission layer, and used as the DMRS port configuration table to be indexed.

[0248] When the content of the third DMRS port configuration table is in the form of: the second DMRS port configuration sub-table of each first uplink data transmission layer under the DMRS type parameter, the target second DMRS port configuration sub-table can be determined from the third DMRS port configuration table as the DMRS port configuration table to be indexed.

[0249] When the content of the third DMRS port configuration table is in the form of: the third DMRS port configuration sub-table corresponding to various DMRS type parameters of the first uplink data transmission layer, the target third DMRS port configuration sub-table can be determined from the third DMRS port configuration table as the DMRS port configuration table to be indexed.

[0250] For an exemplary description of the above implementation method, please refer to the relevant content in the above embodiments, which will not be repeated here.

[0251] Step S84: Receive downlink control command (DCI) and obtain the DMRS port indication field from the DCI.

[0252] The port indication field includes a port index value, which is used to index one or more DMRS ports allocated for PUSCH transmission.

[0253] Optionally, the DMRS port indication field in the downlink control command (DCI) can be used to indicate to the terminal device a DMRS port or port combination allocated for PUSCH transmission. Optionally, DCI0-1 / 0-2 can be used to indicate to the terminal device a DMRS port or port combination allocated for PUSCH transmission.

[0254] Optionally, the number of bits occupied by the port index value is determined by the protocol, either based on network configuration or through DMRS type parameters. In some implementations, the DMRS port indication field indicates the number of bits used by a DMRS port or port combination, determined by the total number of entries in the DMRS port configuration table.

[0255] Step S85: Determine one or more DMRS ports allocated for PUSCH transmission from the DMRS port configuration table to be indexed based on the port index value.

[0256] Once the port index value is obtained, a DMRS port or port combination allocated for PUSCH transmission can be indexed from the DMRS port configuration table to be indexed. In some implementations, the DMRS port configuration table to be indexed is directly indexed based on the port index value to determine the DMRS port or port combination; alternatively, in other implementations, a starting index value of a predefined table is determined, and the actual port index value is determined based on the port index value and the starting index value, and the DMRS port configuration table to be indexed is indexed based on the actual port index value to determine the DMRS port or port combination.

[0257] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0258] Please see Figure 9 , Figure 9 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 9 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0259] Step S91: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0260] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0261] Optionally, for each first uplink data transmission layer, a first DMRS port configuration table corresponding to different DMRS type parameters can be generated for the first uplink data transmission layer. That is, multiple first DMRS port configuration tables can be configured for each first uplink data transmission layer, where each first DMRS port configuration table corresponds to a type of DMRS parameter.

[0262] Optionally, the first DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0263] Optionally, the total number of the first DMRS port configuration tables is 10.

[0264] Step S92: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0265] The specific implementation of step S92 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0266] Step S93: Based on the target DMRS type parameter and the first parameter in the target first uplink data transmission layer, determine the candidate first DMRS port configuration table from the first DMRS port configuration table;

[0267] Step S94: Based on the target DMRS type parameter and the second parameter in the target first uplink data transmission layer, determine the target first DMRS port configuration table from the candidate first DMRS port configuration table, and use it as the DMRS port configuration table to be indexed.

[0268] In some implementations, the terminal device determines the first DMRS port configuration table corresponding to different RIs with DMRS type parameters as the target DMRS type parameter from the first DMRS port configuration table, and uses it as the candidate first DMRS port configuration table. Further, based on the target first uplink data transmission layer, the terminal device determines the target first DMRS port configuration table from the candidate first DMRS port configuration table, and uses it as the DMRS port configuration table to be indexed.

[0269] In other implementations, the terminal device determines the first DMRS port configuration table corresponding to different DMRS type parameters for the target first uplink data transmission layer from the first DMRS port configuration table, and uses it as a candidate first DMRS port configuration table. Further, based on the target DMRS type parameters, the terminal device determines the target first DMRS port configuration table from the candidate first DMRS port configuration table, and uses it as the DMRS port configuration table to be indexed.

[0270] For an exemplary description of the above implementation method, please refer to the relevant content in the above embodiments, which will not be repeated here.

[0271] Step S95: Receive downlink control command DCI and obtain the DMRS port indication field from DCI.

[0272] It should be noted that the DMRS port indication field in the DCI indicates to the terminal device a DMRS port or port combination allocated for PUSCH transmission. In some implementations, the DMRS port indication field indicates the number of bits used for the DMRS port or port combination, which is determined by the total number of entries in the DMRS port configuration table. For example, for DMRS type 1, FLDMRS = 2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated using 4 bits.

[0273] Step S96: Determine one or more DMRS ports allocated for PUSCH transmission from the DMRS port configuration table to be indexed based on the port index value.

[0274] The specific implementation methods of steps S95 and S96 in the embodiments of this application can be implemented by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0275] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0276] Please see Figure 10 , Figure 10 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 10 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0277] Step S101: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0278] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0279] For each DMRS type parameter, a second DMRS port configuration table corresponding to that DMRS type parameter is generated. This second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers. In other words, each DMRS type parameter corresponds to one second DMRS port configuration table, and each second DMRS port configuration table includes first DMRS port configuration sub-tables for each of the first uplink data transmission layers, RI=5, RI=6, RI=7, and RI=8.

[0280] Optionally, the second DMRS port configuration table can have the same table format and included configuration entries as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4.

[0281] Optionally, the total number of second DMRS port configuration tables is 3.

[0282] Step S102: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0283] The specific implementation of step S102 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0284] Step S103: Based on the target DMRS type parameter, determine the candidate second DMRS port configuration table from the second DMRS port configuration table.

[0285] Step S104: Based on the target first uplink data transmission layer, determine the target first DMRS port configuration sub-table from the candidate second DMRS port configuration table.

[0286] In some implementations, the terminal device determines the second DMRS port configuration table corresponding to the target DMRS type parameter from multiple configured second DMRS port configuration tables, and uses it as a candidate second DMRS port configuration table. Further, based on the target first uplink data transmission layer, the terminal device determines the target first DMRS port configuration sub-table from the candidate second DMRS port configuration table. Since the candidate second DMRS port configuration table includes first DMRS port configuration sub-tables with RI=5, RI=6, RI=7, and RI=8, the terminal device can determine the first DMRS port configuration sub-table corresponding to the target first uplink data transmission layer as the target first DMRS port configuration sub-table, which is the DMRS port configuration table to be indexed.

[0287] For an exemplary description of the above implementation method, please refer to the relevant content in the above embodiments, which will not be repeated here.

[0288] Step S105: Receive downlink control command (DCI) and obtain the DMRS port indication field from the DCI.

[0289] It should be noted that the DMRS port indication field in the DCI indicates to the terminal device a DMRS port or combination of DMRS ports allocated for PUSCH transmission. In some implementations, the DMRS port indication field indicates the number of bits used by the DMRS port or combination of DMRS ports, which is determined by the total number of entries in the DMRS port configuration table. For example, for DMRS type 1, FL DMRS = 2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 16, meaning the DMRS port indication field in the DCI can be indicated using 4 bits.

[0290] Step S106: Determine one or more DMRS ports allocated for PUSCH transmission from the DMRS port configuration table to be indexed based on the port index value.

[0291] The specific implementation methods of steps S105 and S106 in the embodiments of this application can be implemented by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0292] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0293] Please see Figure 11 , Figure 11 This is a flowchart illustrating a DMRS port indication method provided in an embodiment of this application. Figure 11 As shown, this method is executed by the terminal device and may include, but is not limited to, the following steps:

[0294] Step S111: In response to the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer.

[0295] The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0296] A general third DMRS port configuration table is generated. Optionally, the third DMRS port configuration table includes second DMRS port configuration sub-tables for each first uplink data transmission layer under each DMRS type parameter. Optionally, the third DMRS port configuration table includes third DMRS port configuration sub-tables for each type of DMRS type parameter under each first uplink data transmission layer. That is, for first uplink data transmission with RI>4 (i.e., RI=5 / 6 / 7 / 8), a single third DMRS port configuration table can be consulted.

[0297] Optionally, the third DMRS port configuration table may have the same or different table format as the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4, and the configuration entries included in the third DMRS port configuration table may differ from those in the original DMRS port configuration table configured when RI=1 / 2 / 3 / 4. The third DMRS port configuration table includes a total of 32 entries.

[0298] Step S112: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0299] The specific implementation of step S102 in the embodiments of this application can be achieved by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0300] Step S113: Based on the target DMRS type parameter and the target first uplink data transmission layer, determine the target DMRS port configuration sub-table from the third DMRS port configuration table as the DMRS port configuration table to be indexed.

[0301] The target DMRS port configuration sub-table is either a second DMRS port configuration sub-table within the third DMRS port configuration table or a third DMRS port configuration sub-table within the third DMRS port configuration table.

[0302] When the third DMRS port configuration table includes the second DMRS port configuration sub-tables for each first uplink data transmission layer under the DMRS type parameter, candidate second DMRS port configuration sub-tables can be determined from the third DMRS port configuration table based on the target DMRS type parameter, and used as candidate DMRS port configuration sub-tables. Further, based on the target first uplink data transmission layer, the target second DMRS port configuration sub-table is determined from the determined candidate second DMRS port configuration sub-tables, and used as the target DMRS port configuration sub-table, i.e., the DMRS port configuration table to be indexed.

[0303] When the third DMRS port configuration table includes sub-tables of third DMRS port configurations corresponding to various DMRS type parameters of the first uplink data transmission layer, candidate third DMRS port configuration sub-tables can be determined from the third DMRS port configuration table based on the target first uplink data transmission layer. Further, based on the target DMRS type parameters, the target third DMRS port configuration sub-table is determined from the determined candidate third DMRS port configuration sub-tables, becoming the target DMRS port configuration sub-table, i.e., the DMRS port configuration table to be indexed.

[0304] Examples and descriptions can be found in the relevant content described in the above embodiments, and will not be repeated here.

[0305] Step S114: Receive downlink control command (DCI) and obtain the DMRS port indication field from the DCI.

[0306] It should be noted that, optionally, the number of entries in the DMRS port allocation table corresponding to RI=5 / 6 / 7 / 8 can determine the number of bits used to indicate the port in the DCI. For example, for DMRS type 1, FL DMRS=2, the number of entries in the DMRS port allocation table corresponding to RANK5-8 is 32, meaning the DMRS port indication field in the DCI can be indicated by 8 bits. In other words, when the DMRS port configuration table is the third DMRS port configuration table, the number of bits in the DMRS port indication field is greater than the number of bits used to indicate one or more DMRS ports in the DMRS port configuration table corresponding to the second uplink data transmission layer.

[0307] Step S115: Determine one or more DMRS ports allocated for PUSCH transmission from the DMRS port configuration table to be indexed based on the port index value.

[0308] The specific implementation methods of steps S105 and S106 in the embodiments of this application can be implemented by referring to any implementation method in the embodiments of this application, as detailed in the relevant content, and will not be repeated here.

[0309] The DMRS port indication method provided in this application, when a single terminal device supports a maximum of 8 uplink data transmission layers, configures a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type, and allocates one or more DMRS ports required for PUSCH transmission based on the configured DMRS port configuration table. This application provides multiple configuration methods for configuring DMRS port configuration tables for newly added uplink data transmission layers, and fills in the blanks in the DMRS port configuration table required for configuring newly added uplink data transmission layers, providing a basis for enhancing uplink transmission capabilities. Furthermore, the ability to allocate DMRS ports required for PUSCH transmission to the terminal device based on the configured DMRS port configuration table helps avoid conflicts between PUSCH and the DMRS of other scheduled terminal devices.

[0310] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspectives of terminal devices and network devices, respectively. To implement the functions of the methods provided in the embodiments of this application, the terminal device and network device may include hardware structures and software modules, and may implement the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0311] Please see Figure 12 This is a schematic diagram of the structure of a communication device 120 provided in an embodiment of this application. Figure 12 The communication device 120 shown may include a processing module 121 and a transceiver module 122. The transceiver module 122 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 122 can implement both sending and / or receiving functions.

[0312] The communication device 120 can be a terminal device, a device within a terminal device, or a device that can be used in conjunction with a terminal device. Alternatively, the communication device 120 can be a network device, a device within a network device, or a device that can be used in conjunction with a network device.

[0313] Communication device 120 is a network device, including:

[0314] Processing module 121 is used to determine a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer, when the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by a single terminal device is equal to 8 layers. The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0315] The transceiver module 122 is used to indicate to the terminal device, based on the DMRS port configuration table, one or more DMRS ports allocated for Physical Uplink Shared Channel (PUSCH) transmission.

[0316] Optionally, the processing module 121 is further configured to: generate a first DMRS port configuration table corresponding to different DMRS type parameters for each of the first uplink data transmission layers.

[0317] Optionally, the processing module 121 is further configured to: generate a second DMRS port configuration table corresponding to each DMRS type parameter, wherein the second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers.

[0318] Optionally, the processing module 121 is further configured to: generate a general third DMRS port configuration table, wherein the content of the third DMRS port configuration table includes one of the following forms: a second DMRS port configuration sub-table for each first uplink data transmission layer under each DMRS type parameter; a third DMRS port configuration sub-table for each DMRS type parameter under each first uplink data transmission layer.

[0319] Optionally, the transceiver module 122 is further configured to: determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission; determine one or more DMRS ports allocated for the PUSCH transmission based on the target DMRS type parameters and the target first uplink data transmission layer; and indicate the one or more DMRS ports to the terminal device.

[0320] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a first DMRS port configuration table, determine a candidate first DMRS port configuration table from the first DMRS port configuration table based on the target DMRS type parameter and a first parameter in the target first uplink data transmission layer; determine a target first DMRS port configuration table from the candidate first DMRS port configuration table based on the target DMRS type parameter and a second parameter in the target first uplink data transmission layer; and determine one or more DMRS ports allocated for the PUSCH transmission based on the target first DMRS port configuration table.

[0321] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a second DMRS port configuration table, determine a candidate second DMRS port configuration table from the second DMRS port configuration table based on the target DMRS type parameter; determine a target first DMRS port configuration sub-table from the candidate second DMRS port configuration table based on the target first uplink data transmission layer; and determine one or more DMRS ports allocated for the PUSCH transmission based on the target first DMRS port configuration sub-table.

[0322] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a third DMRS port configuration table, determine a candidate second target DMRS port configuration sub-table from the third DMRS port configuration table based on the target DMRS type parameter; determine a target second DMRS port configuration sub-table from the candidate second DMRS port configuration sub-table based on the target first uplink data transmission layer, and determine one or more DMRS ports allocated for the PUSCH transmission based on the target second DMRS port configuration sub-table; or, determine a candidate third target DMRS port configuration sub-table from the third DMRS port configuration table based on the target first uplink data transmission layer; determine a target third DMRS port configuration sub-table from the candidate third DMRS port configuration sub-table based on the target DMRS type parameter, and determine one or more DMRS ports allocated for the PUSCH transmission based on the target third DMRS port configuration sub-table.

[0323] Optionally, the transceiver module 122 is further configured to: indicate the one or more DMRS ports to the terminal device via the DMRS port indication field in the downlink control command DCI, wherein the port indication field includes the port index value of the one or more DMRS ports.

[0324] Optionally, in response to the target DMRS port configuration table being a first DMRS port configuration table or a second DMRS port configuration table, the number of bits occupied by the port indication field is the same as the number of bits used in the DMRS port configuration table for indicating a DMRS port or port combination corresponding to the second uplink data transmission layer.

[0325] Optionally, in response to the target DMRS port configuration table being a third DMRS port configuration table, the number of bits in the DMRS port indication field is greater than the number of bits used by a DMRS port or port combination in the second uplink data transmission layer DMRS port configuration table.

[0326] Optionally, the number of bits occupied by the port indication field is determined by the protocol, either through network configuration or by the DMRS type parameter.

[0327] Optionally, the transceiver module 122 is further configured to: indicate the target DMRS type parameters and the target first uplink data transmission layer to the terminal device.

[0328] Optionally, the transceiver module 122 is further configured to: explicitly or implicitly indicate the target first uplink data transmission layer to the terminal device.

[0329] Optionally, the DMRS port configuration table includes the maximum number of symbols in the preceding DMRS and / or the DMRS mapping type corresponding to the DMRS type parameter.

[0330] Communication device 120 is a terminal device, including:

[0331] Processing module 121 is configured to determine a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type parameter and the second uplink data transmission layer, when the maximum uplink data transmission layer N corresponding to the PUSCH shared channel transmission supported by the terminal device is equal to 8 layers. The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer.

[0332] The transceiver module 122 is used to receive indication information sent by the network device and, based on the indication information, obtain one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table.

[0333] Optionally, the processing module 121 is further configured to: generate a first DMRS port configuration table corresponding to different DMRS type parameters for each of the first uplink data transmission layers.

[0334] Optionally, the processing module 121 is further configured to: generate a second DMRS port configuration table corresponding to each DMRS type parameter, wherein the second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers.

[0335] Optionally, the processing module 121 is further configured to: generate a general third DMRS port configuration table, wherein the content of the third DMRS port configuration table includes one of the following forms: a second DMRS port configuration sub-table for each first uplink data transmission layer under each DMRS type parameter; a third DMRS port configuration sub-table for each DMRS type parameter under each first uplink data transmission layer.

[0336] Optionally, the transceiver module 122 is further configured to: determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission.

[0337] Optionally, the transceiver module 122 is also configured to: explicitly or implicitly determine the target first uplink data transmission layer.

[0338] Optionally, the transceiver module 122 is further configured to: receive a downlink control command (DCI); obtain a DMRS port indication field from the DCI, wherein the port indication field includes a port index value, the port index value being used to index one or more DMRS ports allocated for the PUSCH transmission; determine a DMRS port configuration table to be indexed from the DMRS port configuration table based on the target DMRS type parameter and the target first uplink data transmission layer; and determine the one or more DMRS ports from the DMRS port configuration table to be indexed based on the port index value.

[0339] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a first DMRS port configuration table, determine a candidate first DMRS port configuration table from the first DMRS port configuration table based on the target DMRS type parameter and the first parameter in the target first uplink data transmission layer; and determine a target first DMRS port configuration table from the candidate first DMRS port configuration table based on the target DMRS type parameter and the second parameter in the target first uplink data transmission layer, and use it as the DMRS port configuration table to be indexed.

[0340] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a second DMRS port configuration table, determine a candidate second DMRS port configuration table from the second DMRS port configuration table based on the target DMRS type parameter and the second uplink data transmission layer number; and determine a target first DMRS port configuration sub-table from the candidate second DMRS port configuration table based on the target first uplink data transmission layer, and use it as the DMRS port configuration table to be indexed.

[0341] Optionally, the transceiver module 122 is further configured to: in response to the DMRS port configuration table being a third DMRS port configuration table, determine a candidate second target DMRS port configuration sub-table from the third DMRS port configuration table based on the target DMRS type parameter; determine a target second DMRS port configuration sub-table from the candidate second DMRS port configuration sub-table based on the target first uplink data transmission layer, as the DMRS port configuration table to be indexed, and determine one or more DMRS ports allocated for the PUSCH transmission based on the target second DMRS port configuration sub-table; or, determine a candidate third target DMRS port configuration sub-table from the third DMRS port configuration table based on the target first uplink data transmission layer; determine a target third DMRS port configuration sub-table from the candidate third DMRS port configuration sub-table based on the target DMRS type parameter, as the DMRS port configuration table to be indexed, and determine one or more DMRS ports allocated for the PUSCH transmission based on the target third DMRS port configuration sub-table.

[0342] Optionally, the transceiver module 122 is further configured to: directly index the DMRS port configuration table to be indexed based on the port index value to determine the one or more DMRS ports therefrom; or, determine the starting index value of a predefined table, and determine the actual port index value based on the port index value and the starting index value, and index the DMRS port configuration table to be indexed based on the actual port index value to determine the one or more DMRS ports therefrom.

[0343] Please see Figure 13 , Figure 13 This is a schematic diagram of another communication device 130 provided in an embodiment of this application. The communication device 130 can be a terminal device, a network device, a chip, chip system, or processor that supports the terminal device in implementing the above methods, or a chip, chip system, or processor that supports the network device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0344] The communication device 130 may include one or more processors 131. The processor 131 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0345] Optionally, the communication device 130 may further include one or more memories 132, on which a computer program 134 may be stored. The processor 131 executes the computer program 134 to cause the communication device 130 to perform the method described in the above method embodiments. Optionally, the memory 132 may also store data. The communication device 130 and the memory 132 may be provided separately or integrated together.

[0346] Optionally, the communication device 130 may also include a transceiver 135 and an antenna 136. The transceiver 135 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 135 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0347] Optionally, the communication device 130 may further include one or more interface circuits 137. The interface circuits 137 are used to receive code instructions and transmit them to the processor 131. The processor 131 executes the code instructions to cause the communication device 130 to perform the methods described in the above method embodiments.

[0348] In one implementation, the processor 131 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0349] In one implementation, processor 131 may store computer program 133, which runs on processor 131 and causes communication device 130 to perform the methods described in the above method embodiments. Computer program 133 may be embedded in processor 131; in this case, processor 131 may be implemented in hardware.

[0350] In one implementation, the communication device 130 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0351] The communication device described in the above embodiments can be a transmitting device or a receiving device (such as the receiving device in the foregoing method embodiments), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device is not subject to these limitations. Figure 13 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0352] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0353] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0354] (3) ASIC, such as modem;

[0355] (4) Modules that can be embedded in other devices;

[0356] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0357] (6) Others, etc.

[0358] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 14 The diagram shows the structure of the chip. Figure 14 The chip shown includes a processor 141 and an interface 142. There can be one or more processors 141, and multiple interfaces 142.

[0359] Optionally, the chip also includes a memory 143 for storing necessary computer programs and data.

[0360] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0361] This application also provides a DMRS port indication system, which includes the aforementioned... Figure 12 The embodiments include a communication device as a terminal device (such as the terminal device in the aforementioned method embodiments) and a communication device as a network device; or, the system includes the aforementioned... Figure 13 The embodiments include a communication device as a terminal device (such as the terminal device in the aforementioned method embodiments) and a communication device as a network device.

[0362] This application also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0363] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0364] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is 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 program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred 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)).

[0365] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0366] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0367] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0368] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0369] 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.

[0370] Those skilled in the art will clearly 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.

[0371] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A port indication method for a demodulation reference signal DMRS, characterized in that, Applicable to network devices, the method includes: In response to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by a single terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter. The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer. Based on the DMRS port configuration table, indicate to the terminal device one or more DMRS ports allocated for Physical Uplink Shared Channel (PUSCH) transmission; The step of indicating to the terminal device, based on the DMRS port configuration table, one or more DMRS ports allocated for Physical Uplink Shared Channel (PUSCH) transmission includes: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission; Based on the target DMRS type parameters and the target first uplink data transmission layer, the target DMRS port configuration table is determined from the DMRS port configuration table; Based on the target DMRS port configuration table, determine one or more DMRS ports allocated for the PUSCH transmission; The one or more DMRS ports are indicated to the terminal device.

2. The method according to claim 1, characterized in that, The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: For each layer of the first uplink data transmission layer, determine the first DMRS port configuration table corresponding to different DMRS type parameters.

3. The method according to claim 1, characterized in that, The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: For each of the DMRS type parameters, a second DMRS port configuration table corresponding to that DMRS type parameter is generated, wherein the second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers.

4. The method according to claim 2, characterized in that, The determination of one or more DMRS ports allocated for the PUSCH transmission based on the target DMRS port configuration table includes: In response to the DMRS port configuration table being a first DMRS port configuration table, a candidate first DMRS port configuration table is determined from the first DMRS port configuration table based on the target DMRS type parameter and the first parameter in the target first uplink data transmission layer; Based on the target DMRS type parameter and the second parameter in the target first uplink data transmission layer, the target first DMRS port configuration table is determined from the candidate first DMRS port configuration table; Based on the target first DMRS port configuration table, one or more DMRS ports are determined for the PUSCH transmission.

5. The method according to claim 3, characterized in that, The determination of one or more DMRS ports allocated for the PUSCH transmission based on the target DMRS port configuration table includes: In response to the DMRS port configuration table being a second DMRS port configuration table, a candidate second DMRS port configuration table is determined from the second DMRS port configuration table based on the target DMRS type parameter; Based on the target first uplink data transmission layer, determine the target first DMRS port configuration sub-table from the candidate second DMRS port configuration table; Based on the target first DMRS port configuration sub-table, one or more DMRS ports allocated for the PUSCH transmission are determined.

6. The method according to claim 1, characterized in that, The step of indicating the one or more DMRS ports to the terminal device includes: The terminal device is instructed to use the DMRS port indication field in the downlink control command (DCI) to indicate one or more DMRS ports, wherein the port indication field includes the port index value of the one or more DMRS ports.

7. The method according to claim 6, characterized in that, The method further includes: In response to the target DMRS port configuration table being either a first DMRS port configuration table or a second DMRS port configuration table, the number of bits occupied by the port indication field is the same as the number of bits used by one or more DMRS ports in the DMRS port configuration table corresponding to the second uplink data transmission layer.

8. The method according to claim 6, characterized in that, The number of bits occupied by the port indication field is determined by the protocol, either through network configuration or by the DMRS type parameter.

9. The method according to claim 1, characterized in that, After determining the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission, the method further includes: Indicate the target DMRS type parameters and the target first uplink data transmission layer to the terminal device.

10. The method according to claim 9, characterized in that, The method further includes: The target first uplink data transmission layer is explicitly or implicitly indicated to the terminal device.

11. The method according to claim 1, characterized in that, The DMRS port configuration table includes the maximum number of symbols in the preceding DMRS and / or the DMRS mapping type corresponding to the DMRS type parameter.

12. A port indication method for a demodulation reference signal DMRS, characterized in that, Applicable to terminal devices, the method includes: In response to the maximum number of uplink data transmission layers N corresponding to the PUSCH shared channel transmission supported by the terminal device being equal to 8 layers, a DMRS port configuration table is determined for the first uplink data transmission layer based on the DMRS type parameter, wherein the DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer; Receive indication information sent by the network device, and obtain one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information; Before receiving the indication information sent by the network device and obtaining the DMRS port allocated for the PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information, the method further includes: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission; The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: Based on the target DMRS type parameters and the target first uplink data transmission layer, the DMRS port configuration table to be indexed is determined from the DMRS port configuration table; The step of obtaining one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information includes: Based on the indicated information, obtain one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table to be indexed.

13. The method according to claim 12, characterized in that, The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: For each layer of the first uplink data transmission layer, determine the first DMRS port configuration table corresponding to different DMRS type parameters.

14. The method according to claim 12, characterized in that, The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: For each DMRS type parameter, a second DMRS port configuration table corresponding to the DMRS type parameter is determined, wherein the second DMRS port configuration table includes a first DMRS port configuration sub-table for each of the first uplink data transmission layers.

15. The method according to claim 12, characterized in that, The method further includes: The target first uplink data transmission layer is explicitly or implicitly determined.

16. The method according to claim 12, characterized in that, The step of retrieving one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table to be indexed based on the indication information includes: Receive downlink control command (DCI), and obtain a DMRS port indication field from the DCI, wherein the port indication field includes a port index value, which is used to index one or more DMRS ports allocated for the PUSCH transmission; Based on the port index value, the one or more DMRS ports are determined from the DMRS port configuration table to be indexed.

17. The method according to claim 16, characterized in that, The step of determining the DMRS port configuration table to be indexed from the DMRS port configuration table based on the target DMRS type parameters and the target first uplink data transmission layer includes: In response to the DMRS port configuration table being a first DMRS port configuration table, a candidate first DMRS port configuration table is determined from the first DMRS port configuration table based on the target DMRS type parameter and the first parameter in the target first uplink data transmission layer; Based on the target DMRS type parameter and the second parameter in the target first uplink data transmission layer, the target first DMRS port configuration table is determined from the candidate first DMRS port configuration table and used as the DMRS port configuration table to be indexed.

18. The method according to claim 16, characterized in that, The step of determining the DMRS port configuration table to be indexed from the DMRS port configuration table based on the target DMRS type parameters and the target first uplink data transmission layer includes: In response to the DMRS port configuration table being a second DMRS port configuration table, a candidate second DMRS port configuration table is determined from the second DMRS port configuration table based on the target DMRS type parameter; Based on the target first uplink data transmission layer, the target first DMRS port configuration sub-table is determined from the candidate second DMRS port configuration table and used as the DMRS port configuration table to be indexed.

19. The method according to claim 16, characterized in that, The step of determining the one or more DMRS ports from the DMRS port configuration table to be indexed based on the port index value includes: The one or more DMRS ports can be determined by directly indexing the DMRS port configuration table based on the port index value; or... Determine the starting index value of the predefined table, and determine the actual port index value based on the port index value and the starting index value. Then, index the DMRS port configuration table to be indexed based on the actual port index value to determine one or more DMRS ports.

20. A communication device, characterized in that, include: The processing module is used to determine a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type parameter when the maximum number of uplink data transmission layers N is equal to 8 layers for transmission on the PUSCH shared channel supported by a single terminal device. The DMRS port configuration table includes a set of DMRS ports allocated for the first uplink data transmission layer. The transceiver module is used to indicate to the terminal device, based on the DMRS port configuration table, one or more DMRS ports allocated for Physical Uplink Shared Channel (PUSCH) transmission; The step of indicating to the terminal device, based on the DMRS port configuration table, one or more DMRS ports allocated for Physical Uplink Shared Channel (PUSCH) transmission includes: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission; Based on the target DMRS type parameters and the target first uplink data transmission layer, the target DMRS port configuration table is determined from the DMRS port configuration table; Based on the target DMRS port configuration table, determine one or more DMRS ports allocated for the PUSCH transmission; The one or more DMRS ports are indicated to the terminal device.

21. A communication device, characterized in that, include: The processing module is used to determine a DMRS port configuration table for the first uplink data transmission layer based on the DMRS type parameter when the maximum number of uplink data transmission layers N is equal to 8 layers for transmission on the PUSCH shared channel supported by the terminal device. The DMRS port configuration table includes a set of DMRS port allocations defined for the first uplink data transmission layer. The transceiver module is used to receive indication information sent by the network device and, based on the indication information, obtain one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table. Before the receiving network device sends an indication information, and before obtaining the DMRS port allocated for PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information, the transceiver module is further configured to: Determine the target DMRS type parameters and the target first uplink data transmission layer used by the terminal device for PUSCH transmission; The process of determining the DMRS port configuration table for the first uplink data transmission layer based on DMRS type parameters includes: Based on the target DMRS type parameters and the target first uplink data transmission layer, the DMRS port configuration table to be indexed is determined from the DMRS port configuration table; The step of obtaining one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table based on the indication information includes: Based on the indicated information, obtain one or more DMRS ports allocated for PUSCH transmission of the terminal device from the DMRS port configuration table to be indexed.

22. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 11.

23. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 12 to 19.

24. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 1 to 11.

25. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 12 to 19.

26. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 11 to be implemented.

27. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 12 to 19 to be implemented.

Images