Method and device for data transmission

Abstract

Embodiments of the present disclosure relate to methods and devices for data transmission. In an example embodiment, a method implemented in a network device is provided. According to the method, a target RS port group is determined from a plurality of RS ports for transmitting RS. The RS port is associated with at least one network device. Then, a configuration of the target RS port group is sent to a terminal device.

Description

[0001] Divisional Application Instructions

[0002] This application is a divisional application of the Chinese invention patent application with international application number PCT / CN2017 / 094017, international application date July 24, 2017, entering the Chinese national phase on January 21, 2020, national application number 201780093453.5, and invention name “Method and device for data transmission”. Technical Field

[0003] Embodiments of the present disclosure generally relate to the field of communications, and in particular, to methods and devices for data transmission. Background Art

[0004] With the development of communication technology, multi-antenna schemes such as beam management and reference signal transmission have been studied for new radio access (NR). In downlink transmission, a network device (e.g., eNB, gNB, or transmit receive point (TRP)) sends a downlink RS, such as a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), and a sounding reference signal (SRS), to a terminal device (e.g., a user equipment (UE)). Upon receiving the RS, the terminal device can perform quality measurement of the channel between the network device and the terminal device, estimation of the channel, and the like. Typically, in downlink transmission, control information including the configuration of the RS can be sent on a physical downlink control channel (PDCCH), and data can be sent on a physical downlink shared channel (PDSCH).

[0005] It has been proposed that a single NR-PDCCH schedules a single NR-PDSCH, where separate RS ports (layers) are sent from separate TRPs, and that multiple NR-PDCCHs each schedule a corresponding NR-PDSCH, where each NR-PDSCH is sent from a separate TRP.

[0006] In the scenario of multi-TRP PDSCH transmission, the coordination of DMRS from multiple TRPs needs to ensure orthogonality. For example, when multiple PDCCHs schedule multiple PDSCHs, the UE also needs to distinguish which RS port(s) are from the first TRP and which RS port(s) are from the second TRP. In other words, it is necessary to indicate the RS port(s) used in RS transmission. Summary of the invention

[0007] In general, example embodiments of the present disclosure provide methods and apparatus for data transmission.

[0008] In a first aspect, a method implemented in a network device is provided. According to the method, the network device determines a target RS port group from a plurality of RS ports for sending RS. The plurality of RS ports are associated with at least one network device. Then, the network device sends a configuration of the target RS port group to a terminal device.

[0009] In a second aspect, a method implemented in a terminal device is provided. According to the method, the terminal device receives a configuration of a target RS port group from a network device. The target RS port group is determined from a plurality of RS ports used to send RS to the terminal device. The plurality of RS ports are associated with at least one network device.

[0010] In a third aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause the network device to perform actions. The actions include: determining a target RS port group from a plurality of RS ports for transmitting RS, the plurality of RS ports being associated with at least one network device; and sending a configuration of the target RS port group to a terminal device.

[0011] In a fourth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions, which, when executed by the processor, cause a network device to perform an action. The action includes: receiving a configuration of a target reference signal (RS) port group from the network device, the target RS port group being determined from a plurality of RS ports for transmitting RS to the terminal device, the plurality of RS ports being associated with at least one network device.

[0012] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0014] Figure 1A-1F are schematic diagrams 100 , 150 , 160 , 170 , 180 , and 190 , respectively, of communication environments in which embodiments of the present disclosure may be implemented;

[0015] Figure 2 A flowchart of a method 200 for configuring an RS port group according to some embodiments of the present disclosure is shown;

[0016] Figure 3A-Figure 3F Schematic diagrams of RS patterns according to embodiments of the present disclosure are respectively shown;

[0017] Figure 4A-4ESchematic diagrams of group segmentation of DMRS ports according to embodiments of the present disclosure are respectively shown;

[0018] Figure 5 A flowchart of a method 500 for configuring an RS port group according to some embodiments of the present disclosure is shown;

[0019] Figure 6 shows a flow chart of a method 600 for determining TRP(s) according to some embodiments of the present disclosure;

[0020] Figure 7 shows a block diagram of a network device 700 according to some embodiments of the present disclosure;

[0021] Figure 8 A block diagram showing a terminal device 800 according to some embodiments of the present disclosure; and

[0022] Fig. 9 is a simplified block diagram of a device 900 suitable for implementing embodiments of the present disclosure.

[0023] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0024] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and help those skilled in the art to understand and implement the present disclosure without any limitation to the scope of the present disclosure. The disclosure described herein can be implemented in various ways except for the way described below.

[0025] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0026] As used herein, the term "network device" or "base station" (BS) refers to a device that is capable of providing or hosting a cell or coverage area in which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved NodeB (eNodeB or eNB), next generation NodeB (gNB), transmission reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power node (such as femto node, micro node, etc.). For the purpose of discussion, some embodiments will be described below with reference to TRP as an example of a network device.

[0027] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs), portable computers, image capture devices (such as digital cameras), gaming devices, music storage and playback devices, or Internet devices that enable wireless or wired Internet access and browsing, etc. For discussion purposes, some embodiments will be described below with reference to UE as an example of a terminal device.

[0028] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations should be understood as open terms meaning "including but not limited to". The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". The terms "first", "second", etc. may refer to different or identical objects. Other definitions, both explicit and implicit, may be included below.

[0029] The communications discussed in the present disclosure may conform to any suitable standard, including but not limited to New Radio Access (NR), Long Term Evolution (LTE), LTE Evolution, Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM), etc. In addition, communications may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, and fifth generation (5G) communication protocols.

[0030] Figure 1A An example communication network 100 in which embodiments of the present disclosure may be implemented is shown. The network 100 includes two network devices (e.g., TRPs) 110 and 130 and a terminal device (e.g., UE) 120. The network device 110 sends data (e.g., DMRS sequence) to the terminal device 120 via multiple RS ports (layers) on the PDSCH 101, and the PDSCH 101 is scheduled by the PDCCH 102. The network device 130 does not communicate with the terminal device 120. Figure 1A The example shows a scenario of 1-TRP with multiple layers (hereinafter also referred to as "scenario 1").

[0031] Figure 1BAnother example communication network 150 in which embodiments of the present disclosure may be implemented is shown. Network 150 also includes two network devices 110 and 130 and a terminal device 120. Network devices 110 and 130 transmit data, such as DMRS sequences, to terminal device 120 via a PUSCH having multiple layers or ports 151 and 153 scheduled by a PDCCH 152. Reference numerals 151 and 153 refer to different RS ports using the same PDSCH. In particular, RS port 151 is some layers of the PDSCH used for transmissions from network device 110, while RS port 153 is other layers of the PDSCH used for transmissions from network device 130. Figure 1B The example shows a scenario with 1 PDCCH and multiple TRPs of PDSCH with multiple layers or ports (hereinafter also referred to as "Scenario 2").

[0032] Figure 1C A further example communication network 160 in which embodiments of the present disclosure may be implemented is shown. Network 160 includes two network devices 110 and 130, and a terminal device 120. Network devices 110 and 130 transmit data, such as DMRS sequences, to terminal device 120 via PDSCHs 161 and 164 scheduled by PDCCHs 162 and 163, respectively. Figure 1C The example shows a scenario of multiple TRPs with multiple PDCCHs and multiple PDSCHs (hereinafter also referred to as "scenario 3").

[0033] Figure 1D An example communication network 170 in which embodiments of the present disclosure may be implemented is shown. The network 170 includes two network devices (e.g., TRPs) 110 and 130 and a terminal device (e.g., UE) 120. The terminal device 120 sends data, such as a DMRS sequence, to the network device 110 via multiple RS ports (layers) on a PUSCH 171, and the PUSCH 171 is scheduled by a PDCCH 172. The network device 130 does not communicate with the terminal device 120. Figure 1D The example shows a scenario of 1-TRP with multiple layers (hereinafter also referred to as "scenario 1-A").

[0034] Figure 1EAnother example communication network 180 in which embodiments of the present disclosure may be implemented is shown. Network 180 also includes two network devices 110 and 130 and a terminal device 120. Terminal device 120 sends data, such as DMRS sequences, to network devices 110 and 130 via a PUSCH having multiple layers or ports 181 and 183 scheduled by a PDCCH 182. Reference numerals 181 and 183 refer to different RS ports using the same PUSCH. In particular, RS port 181 is some layers of the PUSCH used for transmission to network device 110, while RS port 183 is other layers of the PUSCH used for transmission to network device 130. Figure 1E The example shows a scenario with 1 PDCCH and multiple TRPs of PUSCH with multiple layers or ports (also referred to as "Scenario 2-A" below).

[0035] Figure 1F A further example communication network 190 is shown in which embodiments of the present disclosure may be implemented. Network 190 includes two network devices 110 and 130, and a terminal device 120. The terminal device transmits data, such as DMRS sequences, to network devices 110 and 130 via PUSCHs 191 and 194 scheduled by PDCCHs 192 and 193, respectively. Figure 1F The example shows a scenario of multiple TRPs with multiple PDCCHs and multiple PUSCHs (also referred to as "Scenario 3-A" below).

[0036] It should be understood that the number of base stations and terminal devices is only for illustrative purposes and does not impose any limitation. Networks 100, 150, 160, 170, 180 and 190 may include any suitable number of network devices and / or terminal devices suitable for implementing the embodiments of the present disclosure.

[0037] Conventionally, in scenarios of multi-TRP PDSCH transmission, such as scenario 2 or 3, coordination of DMRS from multiple TRPs needs to ensure orthogonality. For example, when multiple PDCCHs schedule multiple PDSCHs, the UE needs to distinguish which RS port(s) are from the first TRP and which RS port(s) are from the second TRP. In addition, with respect to scenario 2-A or 3-A, when multiple PDCCHs schedule multiple PUSCHs, the UE needs to distinguish which RS port(s) are from the first TRP and which RS port(s) are from the second TRP.

[0038] For multi-layer transmission in LTE, the DMRS sequence and port configuration need to be signaled to the UE in non-codebook based multiple input multiple output (MIMO). In LTE-A, the (multiple) DMRS port, (multiple) sequence and segment in downlink control information (DCI) format 2C and 2D can be indicated by (multiple) antenna port, scrambling identity and number of layers. Table 1 below shows an example of (multiple) antenna port, scrambling identity and number of layers indication.

[0039] Table 1

[0040]

[0041]

[0042] However, in NR, a maximum of 12 orthogonal downlink DMRS ports are supported, and greater flexibility for scheduling is preferred. As a result, the DCI overhead is large, which is undesirable. In addition, the DCI segment must allocate different DMRS sequences to different UEs, which is not suitable for multiple PDCCHs.

[0043] In order to solve the above problems and one or more other potential problems, a solution for RS configuration is provided according to an exemplary embodiment of the present disclosure. With this solution, RS ports from different TRPs can be divided into different groups. By sending the configuration of only a portion of the RS ports (e.g., RS port groups) to the terminal device, the DCI overhead can be reduced. In addition, interference with the RS can be avoided.

[0044] The following will refer to Figure 2-Figure 9 The principles and implementations of the present disclosure are described in detail. Figure 2 A flow chart of a method 200 for configuring an RS port group according to some embodiments of the present disclosure is shown. Using the method 200, the above and other potential defects in conventional methods can be overcome. Those skilled in the art will recognize that the method 200 can be implemented by a network device such as the network device 110 or 130 or other suitable device.

[0045] The method 200 proceeds at 210 where a target RS port group is determined from a plurality of RS ports for transmitting RSs. The plurality of RS ports are associated with at least one network device.

[0046] According to an embodiment of the present disclosure, the RS may include one or more of the following: a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a tracking reference signal (TRS), etc. For the purpose of discussion, some embodiments of the present disclosure are described with reference to DMRS as an example of RS.

[0047] In some embodiments, the target RS port group is used to send RS to the terminal device. Alternatively or additionally, the target RS port group can be used for the terminal device to send RS to the network device. In this case, the network device can receive RS from the terminal device via the target RS port group.

[0048] In some embodiments, a group of RS ports may be configured. In one embodiment, the number of RS ports may be 4, for example, the ports are {P1, P2, P3, P4}, where each of P1-P4 is an RS port. In another embodiment, the number of RS ports may be 6, for example, the ports are {P1, P2, P3, P4, P5, P6}, where each of P1-P6 is an RS port. In another embodiment, the number of RS ports may be 8, the ports are {P1, P2, P3, P4, P5, P6, P7, P8}, where each of P1-P8 is an RS port. In another embodiment, the number of RS ports may be 12, the ports are {P1, P2, P3, P4, P5, P6, P7, P8, P9, P10, P11, P12}, where each of P1-P12 is an RS port.

[0049] Figure 3A-Figure 3F Schematic diagrams of RS patterns according to embodiments of the present disclosure are shown respectively. Figure 3A As shown, ports P1 and P3 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P1 and P3 are configured with different cyclic shift values). In this example, ports P2 and P4 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P2 and P4 are configured with different cyclic shift values). Port P1 and / or port P3 are multiplexed with port P2 and / or port P4 by FDM. For example, port P1 and / or port P3 are configured with a different comb offset value (e.g., interleaved frequency division multiplexing access (IFDMA)) than port P2 and / or port P4. For example, as Figure 3A The pattern shown may be configured in DMRS configuration type 1 with 1 symbol.

[0050] In reference Figure 3BIn the described embodiment, ports P1 and P3 are mapped in 2 symbols and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P1 and P3 are configured with different cyclic shift values). Ports P2 and P4 are mapped in 2 symbols and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P2 and P4 are configured with different cyclic shift values). Ports P5 and P7 are mapped in 2 symbols and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P5 and P7 are configured with different cyclic shift values). Ports P6 and P8 are mapped in 2 symbols and multiplexed in the frequency domain by CDM, such as cyclic shift (ports P6 and P8 are configured with different cyclic shift values).

[0051] exist Figure 3B In the example of , port P1 and / or port P3 are multiplexed with port P5 and / or port P7 in the time domain through CDM (e.g., TD-OCC). For example, in the time domain, port P1 and / or port P3 are configured with an OCC value different from that of port P5 and / or port P7, for example, port P1 and / or port P3 are configured to have OCC {1, 1} in 2 adjacent resource elements (REs). Figure 3B In the illustrated embodiment, where 2 REs are at the same frequency location and in 2 different symbols, port P5 and / or port P7 are configured to have OCC {1, -1} in 2 adjacent REs.

[0052] In addition, port P2 and / or port P4 may be multiplexed with port P6 and / or port P8 via CDM in the time domain (e.g., TD-OCC). Port P2 and / or port P4 may be configured with an OCC value different from that of port P6 and / or port P8. For example, port P2 and / or port P4 may be configured to have OCC {1, -1} in 2 adjacent REs in the time domain, and port P6 and / or port P8 may be configured to have OCC {1, -1} in 2 adjacent REs in the time domain.

[0053] Ports P1 and / or P3 and / or P5 and / or P7 may be multiplexed with ports P2 and / or P4 and / or P6 and / or P8 in an FDM manner. As an example, ports P1 and / or P3 and / or P5 and / or P7 are configured with resources in the frequency domain that are different from the resources of ports P2 and / or P4 and / or P6 and / or P8. For example, ports P1 and / or P3 and / or P5 and / or P7 are configured with comb offset values ​​that are different from those of ports P2 and / or P4 and / or P6 and / or P8. For example, Figure 3B The pattern shown may be configured in DMRS configuration type 1 with 2 symbols.

[0054] In reference Figure 3CIn the described embodiment, ports P1 and P2 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as FD-OCC. For example, port P1 is configured to have OCC {1, 1} in 2 adjacent REs in the frequency domain, where the 2 REs are located in the same symbol and 2 different frequency resource elements, and port P2 can be configured to have OCC {1, -1} in 2 adjacent REs in the frequency domain.

[0055] Ports P3 and P4 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as FD-OCC.

[0056] Ports P5 and P6 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as FD-OCC.

[0057] Port P1 and / or port P2 are multiplexed with port P3 and / or port P4 by FDM. For example, port P1 and / or port P2 are configured with resources in the frequency domain from port P3 and / or port P4.

[0058] Port P1 and / or port P2 are multiplexed with port P5 and / or port P6 by FDM. For example, port P1 and / or port P2 are configured with resources in the frequency domain from port P5 and / or port P6.

[0059] Port P3 and / or port P4 are multiplexed with port P5 and / or port P6 by FDM. For example, port P3 and / or port P4 are configured with resources in the frequency domain from port P5 and / or port P6.

[0060] It should be understood that Figure 3C The illustrated embodiment is for illustration and not limitation. Those skilled in the art will appreciate that the resources for ports P1 and / or P2, and the resources for ports P3 and / or P4, and the resources for ports P5 and / or P6 may be adjacent and / or non-adjacent. Figure 3D The described embodiment shows another example of a DMRS configuration with 1 symbol. Figure 3D In the example of , the resources for ports P1, P2, ports P3, P4 and ports P5, P6 are not adjacent. Figure 3C or Figure 3D The pattern shown may be configured in DMRS configuration type 2 with 1 symbol.

[0061] In reference Figure 3EIn the described embodiment, ports P1 and P2 are mapped in the same symbol and multiplexed in the frequency domain by CDM, for example, FD-OCC. As an example, port P1 is configured to have OCC {1, 1} in 2 adjacent REs in the frequency domain, where the 2 REs are located in the same symbol and 2 different frequency resource elements, and port P2 can be configured to have OCC {1, -1} in 2 adjacent REs in the frequency domain.

[0062] Ports P3 and P4 are mapped in the same symbol and multiplexed by CDM in the frequency domain, eg, FD-OCC.

[0063] Ports P5 and P6 are mapped in the same symbol and multiplexed in the frequency domain by CDM, such as FD-OCC.

[0064] Port P1 and / or port P2 and port P7 and / or P8 are multiplexed in the time domain by CDM, such as TD-OCC. For example, port P1 and / or P2 can be configured to have OCC {1, -1} in the time domain, and port P7 and / or P8 can be configured to have OCC {1, -1} in the time domain.

[0065] Port P3 and / or port P4 and port P9 and / or P10 are multiplexed in the time domain by CDM, such as TD-OCC. For example, port P3 and / or P4 can be configured to have OCC {1, -1} in the time domain, and port P9 and / or P10 can be configured to have OCC {1, -1} in the time domain.

[0066] Port P5 and / or port P6 and port P11 and / or P12 are multiplexed in the time domain by CDM, such as TD-OCC. For example, port P5 and / or P6 can be configured to have OCC {1, -1} in the time domain, and port P11 and / or P12 can be configured to have OCC {1, -1} in the time domain.

[0067] Port P1 and / or port P2 and / or port P7 and / or port P8 are multiplexed with port P3 and / or port P4 and / or port P9 and / or port P10 by FDM. For example, port P1 and / or port P2 and / or port P7 and / or port P8 are configured with resources in the frequency domain from port P3 and / or port P4 and / or port P9 and / or port P10.

[0068] Port P3 and / or port P4 and / or port P9 and / or port P10 are multiplexed with port P5 and / or port P6 and / or port P11 and / or port P12 by FDM. For example, port P3 and / or port P4 and / or port P9 and / or port P10 are configured with resources in the frequency domain from port P5 and / or port P6 and / or port P11 and / or port P12.

[0069] Port P1 and / or port P2 and / or port P7 and / or port P8 are multiplexed with port P5 and / or port P6 and / or port P11 and / or port P12 by FDM. For example, port P1 and / or port P2 and / or port P7 and / or port P8 are configured with resources in the frequency domain from port P5 and / or port P6 and / or port P11 and / or port P12.

[0070] It should be understood that Figure 3E The illustrated embodiments are for illustration and not limitation. Those skilled in the art will appreciate that the resources for ports P1 and / or P2 and / or P7 and / or P8, and the resources for ports P3 and / or P4 and / or P9 and / or P10, and the resources for ports P5 and / or P6 and / or P11 and / or P12 may be adjacent and / or non-adjacent. Figure 3F The described embodiment shows another example of a DMRS configuration with 2 symbols. Figure 3F In the example of , the resources for ports P1, P2, P7, P8, ports P3, P4, P9, P10 and ports P5, P6, P11, P12 are not adjacent. Figure 3E or Figure 3F The pattern shown may be configured under DMRS configuration type 2 with 2 symbols.

[0071] It should be understood that Figure 3A-Figure 3F The port indexes P1-P12 in are for illustration purposes only and do not present any limitation. P1-P12 may be port indexes having any suitable number and / or any suitable order suitable for implementing embodiments of the present disclosure.

[0072] In some embodiments, the configuration of the RS is sent to the terminal device. In some embodiments, the configuration of the RS may be at least one of the following: a DMRS configuration type, such as DMRS configuration type 1 and DMRS configuration type 2; the number of DMRS symbols used for frontloading DMRS, for example, 1 or 2 symbols of frontloading DMRS; the presence of additional DMRS; the number of symbols used for additional DMRS. In some embodiments, the configuration of the RS may be included in high-level signaling, such as radio resource control (RRC) signaling or media access control (MAC) signaling, and the configuration may be sent via high-level signaling. Alternatively or additionally, the configuration of the RS may be sent via dynamic signaling such as downlink control information (DCI) or other suitable signaling sent on a downlink channel.

[0073] In some embodiments, the configuration of communication between a terminal device and multiple TRPs or cells can be configured to the terminal device. For example, the configuration may include at least one of the following: monitoring multiple PDCCHs from different TRPs or cells, configuration of RSs from different TRPs or cells, receiving multiple PDSCHs from different TRPs or cells, receiving one PDSCH from different TRPs or cells, and different layers or ports. In some embodiments, when the configuration of multiple TRPs or cell communications is configured to the terminal device, at least one of the RS configurations from different TRPs or cells should be the same. For example, the DMRS configuration type should be the same for different TRPs or cells. For another example, the number of DMRS symbols should be the same for different TRPs or cells, for example, the number can be the number of DMRS symbols for front-loaded DMRS and / or additional DMRS. For another example, the presence of additional DMRS should be the same for different TRPs or cells. In one embodiment, when the UE is configured with communications with multiple TRPs or cells, the UE may not assume that at least one of the RS configurations is different for different TRPs or cells.

[0074] In some embodiments, the configuration of the maximum number of RS ports and / or the configuration of the number of RS ports and / or the configuration of the number of DMRS symbols and / or the presence of additional DMRS and / or the maximum number of CWs and / or the number of CWs may be configured to the terminal device. In some embodiments, based on different configurations, the communication between the terminal device and multiple TRPs or cells may have different conditions, for example, based on certain configurations, the communication between the terminal device and multiple TRPs or cells may not be supported. For an example, when the (maximum) number of RS ports is 4 and / or the (maximum) number of CWs is 1 and / or there are additional DMRSs and / or the number of DMRS symbols is 1, the communication between the terminal device and multiple TRPs or cells may not be supported. In one embodiment, when some of the configurations are configured to the UE, the UE may not assume that it will communicate with multiple TRPs or cells.

[0075] In some embodiments, the RS port can be divided into one or more RS port groups. Then, the configuration can be determined for each of the RS port groups. The RS port can be divided in several ways, for example, system conditions, standard requirements, time / frequency offset, delay spread, frequency spread, etc. In one embodiment, the RS port can be divided into multiple quasi-co-location (QCL) groups. In this case, the RS port group can be a QCL group.

[0076] In some embodiments, whether the RS ports are divided into groups or the number of RS port groups may be determined based on some configurations. For example, when the number of current DMRS symbols is 1, the RS ports may not be divided into groups, or, for example, the number of RS port groups is 1. For another example, when additional DMRS is configured, the RS ports may not be divided into groups, or, for example, the number of RS port groups is 1.

[0077] In some embodiments, the configuration of the RS port group may include various factors, such as but not limited to the size of the RS port group, the RS ports in the RS port group, the identification of the network device, the RS sequence, the initial value of the RS sequence, etc. It should be understood that these examples are described for illustrative purposes only and do not impose any restrictions. Those skilled in the art will understand that the configuration of the RS port group may also include information about (multiple) symbols and / or (multiple) resource elements used by (multiple) RS ports in the RS port group, multiplexing modes of (multiple) RS ports in the RS port group, etc.

[0078] In some embodiments, the UE may be configured with multiple groups, and each group may include at least one of the RS ports, and different groups may correspond to different TRPs and / or cells and / or panels. In some embodiments, the groups may have the same or different numbers of RS ports. And the RS ports in different groups may not overlap and / or completely overlap and / or partially overlap. In some embodiments, the RS ports in certain groups may have different index orders.

[0079] In some embodiments, the RS ports in the RS port group may include at least the RS ports multiplexed by CDM in the frequency domain. That is, the RS ports that map the same time and frequency resources as the RS ports and multiplexed by CDM in the frequency domain and / or time domain may be included in the same RS port group. For example, Figure 3A As shown, at least P1 and P3 should be in one group, or at least P2 and P4 should be in one group. Figure 3B As shown, at least P1 and P3 should be in one group, or at least P2 and P4 should be in one group, or at least P5 and P7 should be in one group, or at least P6 and P8 should be in one group, or at least P1 and P3 and P5 and P7 should be in one group, or at least P2 and P4 and P6 and P8 should be in one group. Figure 3C or Figure 3D As shown, at least P1 and P2 should be in one group, or at least P3 and P4 should be in one group, or at least P5 and P6 should be in one group. Figure 3E or Figure 3FAs shown, at least P1 and P2 should be in one group, or at least P3 and P4 should be in one group, or at least P5 and P6 should be in one group, or at least P7 and P8 should be in one group, or at least P9 and P10 should be in one group, or at least P11 and P12 should be in one group, or at least P1 and P2 and P7 and P8 should be in one group, or at least P3 and P4 and P9 and P10 should be in one group, or at least P5 and P6 and P11 and P12 should be in one group. In some embodiments, the port indexes in the DMRS port group may be different using different DMRS type configurations.

[0080] In some embodiments, different RS port groups may be configured for different TRPs or cells. For example, for communication between a terminal device and two TRPs or cells, two RS port groups may be configured for the terminal device. Furthermore, one RS port group may be an RS port corresponding to one TRP, while another RS ​​port group may be an RS port corresponding to another TRP. For example, when the UE is configured with DMRS configuration type 1, the two RS port groups may be {P1, P2, P3, P4} and {P5, P6, P7, P8}, or the two RS port groups may be {P1, P3, P5, P7} or {P2, P4, P6, P8}. For another example, when the UE is configured with DMRS configuration type 2, the two RS port groups can be two groups from {P1, P2, P3, P4} or {P5, P6, P7, P8} or {P9, P10, P11, P12}, or the two RS port groups can be two groups from {P1, P2, P7, P8} or {P3, P4, P9, P10} or {P5, P6, P11, P12}.

[0081] In some embodiments, different RS port orders can be configured for different TRPs or cells. For example, for communication between a terminal device and two TRPs or cells, two RS port orders can be configured for the terminal device. One RS port order can be an RS port corresponding to one TRP, and the other RS ​​port order can be an RS port corresponding to another TRP. In one example, the two RS port orders can be {A, B, C, D, E, F, G, H} and {F, G, F, E, D, C, B, A}. In another example, the two RS port orders can be {A, B, C, D, E, F, G, H} and {E, F, G, H, A, B, C, D}.

[0082] According to an embodiment of the present disclosure, taking into account the capabilities of the UE, the size of the RS port group may be 4 (corresponding to 1 codeword (CW)), 8 (corresponding to 1 CW / 2 CWs), or other suitable values. In some embodiments, the UE may be configured with an RS port group in scenario 1 or 1-A, the number of RS ports in the RS port group may be N, and the RS port may be N ports selected from P1-P12, for example, the number of RS ports in the RS port group is 4 or 8. Table 2 shows an example of the segmentation of the RS port group in scenario 1 or 1-A. The UE may be configured with either or both rows in Table 2.

[0083] Table 2

[0084] port TRP1 TRP2 At most 4 {A, B, C, D} At most 8 {A,B,C,D,E,F,G,H}

[0085] In scenario 1 or 1-A, the UE is connected to only one TRP, that is, the UE is in single TRP transmission. As shown in Table 2, if the number of RS ports is at most 4, the target RS port group can be {A, B, C, D}, where each of {A, B, C, D} is an RS port, and the target RS port group can be any port selected from ports P1-P12. If the number of RS ports is at most 8, the target RS port group can be {A, B, C, D, E, F, G, H}, where each of {A, B, C, D, E, F, G, H} is an RS port, and the target RS port group can be any port selected from ports P1-P12.

[0086] Additionally or alternatively, in scenario 2 or 2-A of multiple TRP transmissions and a single PDCCH, in the case of UE transparency, the UE may be configured with one RS port group, for example, of size 8, and may be configured with multiple RS port groups, for example, TRPs may notify each other of the configuration of the RS ports. For another example, in the case of opacity, each size is 4. Table 3 shows an example of the segmentation of the RS port group in scenario 2 or 2-A. As shown in Table 3, if the number of RS ports is at most 4, the target RS port group may be {A, B, C, D}, where each of {A, B, C, D} is an RS port, and the target RS port group may be any port selected from ports P1-P12. If the number of RS ports is at most 8, the target RS port group may be {A, B, C, D, E, F, G, H}, where each of {A, B, C, D, E, F, G, H} is an RS port, and the target RS port group may be any port selected from ports P1-P12. The UE may be configured with any one or two rows in Table 3. For example, the target RS port group may be {P1, P2, P3, P4} and {P5, P6, P7, P8} or {P1, P3, P5, P7} and {P2, P4, P6, P8} for two TRPs. For another example, the target RS port group may be any two of {P1, P2, P3, P4}, {P5, P6, P7, P8} and {P9, P10, P11, P12} for two TRPs of DMRS configuration type 2, or any two of {P1, P2, P7, P8}, {P3, P4, P9, P10} and {P5, P6, P11, P12}.

[0087] Table 3

[0088]

[0089] Regarding scenario 3 or 3-A, for multiple PDCCHs, the UE may be configured with multiple groups of size 4. Table 4 shows an example of the segmentation of the RS port group in scenario 3 or 3-A. As shown in Table 4, if the number of RS ports is at most 4, the target RS port group may be {A, B, C, D}, where each of {A, B, C, D} is an RS port, and the target RS port group may be any port selected from ports P1-P12. If the number of RS ports is at most 8, the target RS port group may be {A, B, C, D, E, F, G, H}, where each of {A, B, C, D, E, F, G, H} is an RS port, and the target RS port group may be any port selected from ports P1-P12. The UE may be configured with any one or two rows in Table 4. For example, the target RS port group can be {P1, P2, P3, P4} and {P5, P6, P7, P8} or {P1, P3, P5, P7}5 and {P2, P4, P6, P8} for two TRPs. For another example, the target RS port group can be any two of {P1, P2, P3, P4}, {P5, P6, P7, P8} and {P9, P10, P11, P12} for two TRPs of DMRS configuration type 2, or any two of {P1, P2, P7, P8}, {P3, P4, P9, P10} and {P5, P6, P11, P12}.

[0090] Table 4

[0091] port TRP1 TRP2 At most 8 {A, B, C, D} {E, F, G, H}

[0092] According to an embodiment of the present disclosure, multiple RS ports may be divided into one or more RS port groups in various ways. In some embodiments, each RS port group in the RS port group may be allocated with different resources. Then, the network device may select a target RS port group from the one or more RS port groups. In some embodiments, DMRS from different TRPs may be multiplexed by FDM or configured with different comb offset values ​​or multiplexed by CDM in the time domain. For example, Figure 3B , Figure 3E and Figure 3F In the example shown, ports multiplexed by CDM in the time domain can be multiplexed by TD-OCC. In this case, no restriction on the DMRS sequence is required.

[0093] Figure 4A-4E Schematic diagrams of group segmentation of DMRS ports according to embodiments of the present disclosure are shown respectively. Figure 4A As shown, DMRS can be configured as configuration type 1 with 2 OFDM symbols, such as Figure 3BAs shown in the example in . With 2 different comb offset values, 2 different cyclic shift values ​​and 2 different TD-OCC values, up to 8 ports can be supported. In some embodiments, DMRS ports from different TRPs can be multiplexed by FDM or configured with different comb offset values, and RS ports P1-P8 can be divided into an RS port group (referred to as "Group 1") including ports {P1, P3, P5, P7} (such as Figure 4B ) and another RS ​​port group (referred to as "Group 2") including ports {P2, P4, P6, P8} (as shown Figure 4C In some embodiments, DMRS ports from different TRPs can be multiplexed in the time domain through CDM. For example, DMRS ports can be configured with different TD-OCC values, and RS ports P1-P8 can be divided into RS port group 1 including ports {P1, P2, P3, P4} (as shown in FIG. Figure 4D ) and another RS ​​port group 2 including ports {P5, P6, P7, P8} (as shown Figure 4E shown).

[0094] In some embodiments, the DMRS may be configured as a configuration type 2 with 2 OFDM symbols, such as Figure 3E or Figure 3F As shown in the example in . With 3 different RE positions in the frequency domain, 2 different FD-OCC values ​​and 2 different TD-OCC values, up to 12 ports can be supported. In some embodiments, DMRS ports from different TRPs can be multiplexed by FDM or configured to have different RE positions in the frequency domain, and RS ports P1-P12 can be divided into an RS port group including ports {P1, P2, P7, P8} (referred to as "Group 1") and another RS ​​port group including ports {P3, P4, P9, P10} (referred to as "Group 2") and another RS ​​port group including ports {P5, P6, P11, P12} (referred to as "Group 3"). In some embodiments, DMRS ports from different TRPs can be multiplexed in the time domain through CDM, for example, the DMRS ports can be configured with different TD-OCC values, and RS ports P1-P8 can be divided into RS port group 1 including ports {P1, P2, P3, P4} and another RS ​​port group 2 including ports {P7, P8, P9, P10}.

[0095] In some embodiments, if DMRS from different TRPs are multiplexed via FDM or configured with different comb offset values ​​or configured with different RE positions in the frequency domain or configured with CDM in the time domain or configured with different TD-OCC values, the segmentation can be performed as shown in Table 5.

[0096] Table 5

[0097] Group size Group 4 {A, B, C, D}, {E, F, G, H} 8 {A,B,C,D,E,F,G,H}

[0098] Alternatively, in some embodiments, the network device may divide multiple RS ports into at least one RS port group. Each of the at least one RS port group sends the same RS sequence. Then, the network device may select a target RS port group from the at least one RS port group. For example, DMRS from different TRPs may have the same base sequence. For example, in this case, no grouping constraints are required.

[0099] Figure 4D-Figure 4E Schematic diagrams of group segmentation of DMRS ports according to embodiments of the present disclosure are shown respectively. Figure 4A As shown, if RS ports P1-P8 use the same DMRS sequence, there is no constraint on RS ports in different RS port groups. Therefore, there can be multiple ways to divide RS ports P1-P8. In one embodiment, RS ports P1-P8 can be divided into an RS port group (referred to as "group 1") including ports {P1, P2, P3, P4} (e.g. Figure 4D ) and another RS ​​port group (referred to as "Group 2") including ports {P5, P6, P7, P8} (as shown Figure 4D shown).

[0100] It should be understood that Figure 4A , Figure 4D and Figure 4E The segmentation shown is discussed, for example, but not for limitation. In some other embodiments, RS ports P1-P8 may be divided in other suitable ways. For example, group 1 may include ports {P1, P2, P3, P4}, and group 2 may include ports {P5, P6, P7, P8}. Table 6 below shows more possible RS port groups when group size is 4.

[0101] Table 6

[0102]

[0103] At 220, the configuration of the target RS port group is sent to the terminal device. In some embodiments, the configuration of the target RS port group may be included in and sent via high-level signaling, such as radio resource control (RRC) signaling, media access control (MAC) signaling, etc. Alternatively or additionally, the information of the RS pattern may be sent via dynamic signaling such as downlink control information (DCI) or other suitable signaling transmitted on a downlink channel.

[0104] In scenario 3, signaling can come from the master TRP and from all TRPs in the collaboration. In addition to the target RS port group, it may also be necessary to send an identifier (e.g., TRP ID) or a virtual ID (vID) of the network device in order to generate a DMRS base sequence. In one embodiment, the configuration of the target RS port group can be implemented as Table 7.

[0105] Table 7

[0106] part value DMRS Group 1 Size 4 DMRS Group 1 {P1, P2, P3, P4} TRP1 ID n1 DMRS Group 2 Size 4 DMRS Group 2 {P5, P6, P7, P8} TRP2 ID n2

[0107] In addition to the above explicit indication of the configuration of the target RS port group, in some embodiments, the configuration can be indicated in an implicit manner. For example, the configuration can be inferred by the TRP ID or virtual ID. For example, the UE can obtain the TRP ID or cell ID from the synchronization signal or the vID from the RRC. The ID or vID from the first TRP (e.g., TRP1) can be represented as n1, and the ID or vID from the second TRP (e.g., TRP2) can be represented as n2. The RS port group can then be inferred from Table 8 below (maximum 12 ports), where offset = P5-P1.

[0108] Table 8

[0109]

[0110]

[0111] In some embodiments, the configuration of the RS port group and / or RS port order can be indicated in an implicit manner. For example, the configuration can be inferred by TRP ID or cell ID or virtual ID. For example, the UE can obtain TRP ID or cell ID from the synchronization signal, or obtain vID from RRC. For different TPR IDs or cell IDs or virtual IDs, the RS port group and / or RS port order may be different. In one embodiment, when the value of the ID is an even number, the port group may be {A, B, C, D}, wherein each of {A, B, C, D} is an RS port, and the port group may be a port selected from ports P1-P12, and when the value of the ID is an odd number, the port group may be {E, F, G, H}, wherein each of {E, F, G, H} is an RS port, and the port group may be a port selected from ports P1-P12. And, at least one of {E, F, G, H} may be different from any one of {A, B, C, D}. In another embodiment, when the value of ID is an even number, the port group may be {A, B, C, D, E, F, G, H}, wherein each of {A, B, C, D, E, F, G, H} is an RS port, and the port group may be a port selected from ports P1-P12, and when the value of ID is an odd number, the port group may be {E, F, G, H, A, B, C, D} or {H, G, F, E, D, C, B, A}, wherein each of {E, F, G, H} is an RS port, and the port group may be a port selected from ports P1-P12. In another embodiment, the ID or vID from the first TRP or cell may be represented as n1, and the ID or vID from the second TRP or cell may be represented as n2. If mod(n1,3)=0, the port group can be {A, B, C, D}, where each of {A, B, C, D} is an RS port, and the port group can be a port selected from ports P1-P12, if mod(n1,3)=1, the port group can be {E, F, G, H}, where each of {E, F, G, H} is an RS port, and the port group can be a port selected from ports P1-P12, if mod(n1,3)=2, the port group can be {I, J, K, L}, where each of {I, J, K, L} is an RS port, and the port group can be a port selected from ports P1-P12, and at least one of the port indices in each group can be different from any of the port indices in another group.

[0112] Alternatively or additionally, the configuration of the target RS port group may be included in dynamic signaling such as downlink control information (DCI), or included in other suitable signaling on a downlink channel and sent via dynamic signaling.

[0113] According to an embodiment of the present disclosure, DCI may be predefined in several ways to indicate the RS port group. In one embodiment, DCI may be implemented according to Table 9.

[0114] Table 9

[0115]

[0116] As shown in Table 7, if the RS port group is {P1, P2, P3, P4, P5, P6, P7, P8}, when determining that the DCI value is 0, the UE further determines whether 1 CW or 2 CWs will be used. If 1 CW will be used, the UE can determine that the target RS port group includes ports P6 to P8. If 2 CWs will be used, the UE can determine that the target RS port group includes ports P1 to P5.

[0117] It should be understood that the DCI implementation shown in Table 7 is only exemplary and not limiting. It can be understood that DCI can be implemented in other suitable forms.

[0118] In some embodiments, the network device may receive the RS from the terminal device via the target RS port group based on the configuration.

[0119] Reference now Figure 5 , Figure 5 A flow chart of a method 500 for configuring an RS port group according to some embodiments of the present disclosure is shown. It should be understood that the method 500 may be implemented at a terminal device such as the terminal device 120 or any other suitable device.

[0120] Method 500 enters at step 510, where the terminal device receives the configuration of the target RS port group from the network device. For example, the target RS port group can be determined from multiple RS ports used to send RS to the terminal device based on method 200 as described above. Multiple RS ports are associated with at least one network device.

[0121] In some embodiments, the terminal device may receive the RS transmitted from the network device via the target RS port group based on the configuration. Alternatively, the terminal device may transmit the RS to the network device via the target RS port group based on the configuration.

[0122] As described above, the configuration of the target RS port group from the network device can be sent from the network device via high-level signaling or downlink control information. In some embodiments, the terminal device can receive high-level signaling or downlink control information from the network device, and obtain the configuration of the target RS port group from the received high-level signaling or downlink control information.

[0123] In some embodiments, if the configuration of the target RS port group indicates that multiple resources are allocated to RS transmission, the terminal device may determine that the RS is to be sent from different network devices on different downlink data transmission channels.

[0124] Alternatively or additionally, if the terminal device receives configuration of additional target RS port groups from another network device other than network device 110 (e.g., network device 130), the terminal device can determine that RS is to be sent from a different network device on a different downlink data transmission channel.

[0125] In another aspect of the present disclosure, in order to support scene switching, an indication for multi-TRP PDCCH and / or PDSCH is required. If the UE receives the indication, it can determine the correct settings, such as RS port group and sequence. In one embodiment, the indication can be included in the DCI. For example, there can be a 1-bit flag in the DCI to be used as an indication. Table 10 shows an example of an indication in the DCI.

[0126] Table 10

[0127] value Multiple TRP PDCCH and / or PDSCH 0 Fake 1 real

[0128] As shown in Table 10, if the flag in the DCI is "0", it can be determined that there are no multiple TRP PDCCHs and / or PDSCHs. For example, there may be a single PDCCH to be detected. For example, the one detected PDCCH may be the only PDCCH to be detected. On the other hand, if the flag is "1", it can be determined that there are multiple TRP PDCCHs and / or PDSCHs. For example, there may be multiple PDCCHs to be detected. For example, in addition to the one detected PDCCH, there may be one or more additional PDCCHs to be detected. For scenario 3, the same flag may be set by all TRPs.

[0129] Alternatively, in some embodiments, the indication may be implicit. In this case, the UE may infer whether it is a multi-TRP transmission based on the received information. Figure 6 A flow chart of a method 600 for determining TRP(s) according to some embodiments of the present disclosure is shown.

[0130] At 610, the UE determines whether it receives 1 DCI, i.e., downlink control information, from 1 TRP. If the UE receives more than one DCI, at 640, the UE may determine that this is a multi-TRP PDSCH, for example, corresponding to scenario 3. If the UE receives only one DCI, at 620, the UE further determines whether the number of allocated resources is 1. If so, it may be determined at 630 that this is a non-multi-TRP PDSCH, corresponding to scenario 1 or scenario 2 in a UE transparent manner. Otherwise, if more than one resource is allocated, the UE may determine at 640 that this is a multi-TRP PDSCH, for example, corresponding to scenario 2 in a non-UE transparent manner. In this way, the UE may infer the scenario without explicit indication. As a result, switching may be performed in a dynamic and flexible manner.

[0131] Reference now Figure 7 , Figure 7 7 is a block diagram of an apparatus 700 according to an embodiment of the present disclosure. It should be understood that the apparatus 700 may be implemented at a network device such as the network device 110 or 130 or any other suitable device.

[0132] As shown in the figure, the apparatus 700 includes a determining unit 710 and a sending unit 720. The determining unit 710 is configured to: determine a target RS port group from a plurality of RS ports used to send RS to a terminal device, wherein the plurality of RS ports are associated with at least one network device. The sending unit 720 is configured to transmit the configuration of the target RS port group to the terminal device.

[0133] In one embodiment, the determining unit 710 may be configured to divide the plurality of RS ports into at least one RS port group, each of the at least one RS port group being allocated with different resources; and select a target RS port group from the at least one RS port group.

[0134] In one embodiment, the determining unit 710 may be configured to divide the plurality of RS ports into at least one RS port group, each of the at least one RS port group transmitting the same RS sequence; and select a target RS port group from the at least one RS port group.

[0135] In one embodiment, the sending unit 720 can be configured to include the configuration of the target RS port group in high-level signaling and send high-level signaling to the terminal device, and / or include the configuration of the target RS port group in downlink control information; and transmit the downlink control information to the terminal device.

[0136] In one embodiment, the apparatus 700 may further include a receiving unit configured to receive an RS from the terminal device via the target RS port group based on the configuration.

[0137] In one embodiment, the configuration of the target RS port group may include at least one of the following: the size of the target RS port group, the RS ports in the target RS port group, an identifier of the network device, and an RS sequence.

[0138] In one embodiment, the RS includes at least one of the following: DMRS, CSI-RS, SRS, PTRS, and TRS.

[0139] Reference now Figure 8 , Figure 8 8 is a block diagram of an apparatus 800 according to an embodiment of the present disclosure. It should be understood that the apparatus 800 may be implemented at a terminal device such as the terminal device 120 or any other suitable device.

[0140] As shown in the figure, the apparatus 800 includes a receiving unit 810, which is configured to receive information of one or more RS patterns for multiple RS ports from a network device. The RS pattern indicates the configuration of RS to be sent to a terminal device via one or more RS ports.

[0141] In one embodiment, the receiving unit 810 may also be configured to receive configuration of a target RS port group from a network device, where the target RS port group is determined from a plurality of RS ports used to send RS to a terminal, and the plurality of RS ports are associated with at least one network device.

[0142] In an embodiment, the receiving unit 810 may also be configured to: receive high-level signaling or downlink control information from a network device; and acquire the configuration of the target RS port group from the high-level signaling or downlink control information.

[0143] In one embodiment, the receiving unit 810 may be further configured to receive the RS transmitted via the target RS port group based on the configuration. The apparatus 800 may further include a transmitting unit configured to transmit the RS to the network device via the target RS port group based on the configuration.

[0144] In one embodiment, the device 800 may also include a determination unit, which is configured to: determine that the RS will be sent from different network devices on different downlink data transmission channels in response to the configuration of the target RS port group indicating that multiple resources are allocated for RS transmission; and determine that the RS will be sent from different network devices on different downlink data transmission channels in response to receiving another configuration of the target RS port group from another network device.

[0145] It should also be noted that the apparatus 700 or 800 can be implemented by any suitable technology currently known or developed in the future. Figure 2 or Figure 5 The single device shown may alternatively be implemented in multiple devices respectively, and multiple separate devices may be implemented in a single device. The scope of the present disclosure is not limited in these respects.

[0146] Note that apparatus 700 or 800 may be configured to implement reference Figure 2 or Figure 5 Thus, the features discussed with respect to method 200 may be applied to corresponding components of device 700, and the features discussed with respect to method 500 may be applied to corresponding components of device 800. It is also noted that the components of device 700 or 800 may be implemented in hardware, software, firmware, and / or any combination thereof. For example, the components of device 700 or 800 may be implemented by circuits, processors, or any other suitable devices, respectively. Those skilled in the art will appreciate that the above examples are intended to be illustrative only and not limiting.

[0147] In some embodiments of the present disclosure, the device 700 or 800 may include at least one processor. As an example, at least one processor suitable for use with the embodiments of the present disclosure may include a general-purpose processor and a special-purpose processor known now or developed in the future. The device 700 or 800 may also include at least one memory. At least one memory may include, for example, a semiconductor memory device, such as a RAM, ROM, EPROM, EEPROM, and a flash memory device. At least one memory may be used to store a program of computer executable instructions. The program may be written in any high-level and / or low-level compatible or interpretable programming language. According to an embodiment, the computer executable instructions may be configured to, together with at least one processor, cause the device 700 to perform at least according to the method 200 described above, and cause the device 800 to perform at least according to the method 500 described above.

[0148] Based on the above description, it will be appreciated by those skilled in the art that the present disclosure may be implemented in a device, method or computer program product. Generally, various exemplary embodiments may be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, but the present disclosure is not limited thereto. Although various aspects of the exemplary embodiments of the present disclosure may be illustrated and described as block diagrams, flow charts or using some other graphical representations, it is well understood that, as non-limiting examples, these boxes, devices, systems, techniques or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controller or other computing device or some combination thereof.

[0149] Figure 7 or Figure 8The various blocks shown may be viewed as method steps, and / or as operations resulting from the operation of computer program code, and / or as a plurality of coupled logic circuit elements configured to perform the associated function(s). At least some aspects of the exemplary embodiments of the present disclosure may be practiced in various components such as integrated circuit chips and modules, and the exemplary embodiments of the present disclosure may be implemented in an apparatus implemented as an integrated circuit, FPGA, or ASIC that is configurable to operate according to the exemplary embodiments of the present disclosure.

[0150] Fig. 9 900 is a simplified block diagram of a device suitable for implementing an embodiment of the present disclosure. As shown, the device 900 includes one or more processors 910, one or more memories 920 coupled to the processor(s) 910, and one or more transmitters and / or receivers (TX / RX) 940 coupled to the processor 910.

[0151] Processor 910 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 900 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0152] Memory 920 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory.

[0153] The memory 920 stores at least a portion of the program 930. The TX / RX 940 is used for bidirectional communication. The TX / RX 940 has at least one antenna to facilitate communication, although in practice, the terminal device or network device mentioned in the present disclosure may have several antennas. The communication interface may represent any interface necessary for communication with other network elements.

[0154] Assume that the program 930 includes a program that, when executed by the associated processor 910, enables the device 900 to operate in accordance with embodiments of the present disclosure (as referred to herein). Figure 2 and Figure 5 That is, the embodiments of the present disclosure may be implemented by computer software executable by the processor 910 of the device 900, or by hardware, or by a combination of software and hardware.

[0155] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any disclosed or claimed content, but rather as descriptions of features specific to a specific disclosed embodiment. Certain features described in this specification in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively. In addition, although the features may be described above as working in certain combinations and even initially claimed as such, in some cases, one or more features in the claimed combination may be removed from the combination, and the claimed combination may involve a sub-combination or a variant of a sub-combination.

[0156] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that such operations be performed in the particular order shown or sequentially, or that all of the operations shown be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0157] When read in conjunction with the accompanying drawings, in view of the foregoing description, various modifications and changes to the foregoing exemplary embodiments of the present disclosure will become clear to those skilled in the relevant art. Any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of the present disclosure. In addition, those skilled in the art who benefit from the teachings presented in the foregoing description and the related drawings, and who are related to these embodiments of the present disclosure, will be able to conceive of other embodiments of the present disclosure set forth herein.

[0158] Therefore, it should be understood that the embodiments of the present disclosure are not limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims.Although specific terms are used herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A method performed by a terminal device, comprising: Receiving a plurality of physical downlink control channels PDCCH for scheduling a plurality of physical downlink shared channels PDSCH, wherein the PDCCH comes from a plurality of transmission receiving points TRP; Receiving the plurality of PDSCHs from the plurality of TRPs; as well as receiving a plurality of demodulation reference signals DMRS for the plurality of PDSCHs, The configurations of the multiple DMRSs are the same, One of the configurations of the plurality of DMRSs is a DMRS configuration regarding a DMRS configuration type, a number of symbols used for a frontloading DMRS, and a number of symbols used for an additional DMRS. 2 . The method according to claim 1 , wherein the DMRS configuration type is DMRS configuration type 1 or DMRS configuration type 2. 3 . The method according to claim 2 , wherein the DMRS configuration type is configured using radio resource control (RRC) signaling. The method according to claim 1 , wherein the number of symbols used for the frontload DMRS is 1. . 5 . The method according to claim 1 , wherein the number of symbols used for the frontloaded DMRS is configured using radio resource control (RRC) signaling and / or via downlink control information (DCI).

6. A terminal device, comprising a processor, wherein the processor is configured to: Receiving a plurality of physical downlink control channels PDCCH for scheduling a plurality of physical downlink shared channels PDSCH, wherein the PDCCH comes from a plurality of transmission receiving points TRP; receiving the plurality of PDSCHs from the plurality of TRPs; and receiving a plurality of demodulation reference signals DMRS for the plurality of PDSCHs, The configurations of the multiple DMRSs are the same, One of the configurations of the plurality of DMRSs is a DMRS configuration regarding a DMRS configuration type, a number of symbols used for a frontloading DMRS, and a number of symbols used for an additional DMRS.

7. The terminal device according to claim 6, wherein the DMRS configuration type is DMRS configuration type 1 or DMRS configuration type 2. 8 . The terminal device according to claim 7 , wherein the DMRS configuration type is configured using radio resource control (RRC) signaling. 9 . The terminal device according to claim 6 , wherein the number of symbols used for the frontload DMRS is 1.

10. The terminal device according to claim 6, wherein the number of symbols used for the frontloaded DMRS is configured using radio resource control (RRC) signaling and / or via downlink control information (DCI).

11. A method performed by a network device, comprising: Sending a plurality of physical downlink control channels PDCCH for scheduling a plurality of physical downlink shared channels PDSCH; Sending the multiple PDSCHs; as well as sending a plurality of demodulation reference signals DMRS for the plurality of PDSCHs, The configurations of the multiple DMRSs are the same, One of the configurations of the plurality of DMRSs is a DMRS configuration regarding a DMRS configuration type, a number of symbols used for a frontloading DMRS, and a number of symbols used for an additional DMRS. 12 . The method according to claim 11 , wherein the DMRS configuration type is DMRS configuration type 1 or DMRS configuration type 2. 13 . The method according to claim 12 , wherein the DMRS configuration type is configured using Radio Resource Control (RRC) signaling. The method of claim 11 , wherein the number of symbols used for the frontload DMRS is 1. 15 . The method of claim 11 , wherein the number of symbols used for the frontloaded DMRS is configured using radio resource control (RRC) signaling and / or via downlink control information (DCI).

16. A network device, comprising a processor, wherein the processor is configured to: Sending a plurality of physical downlink control channels PDCCH for scheduling a plurality of physical downlink shared channels PDSCH; transmitting the plurality of PDSCHs; and sending a plurality of demodulation reference signals DMRS for the plurality of PDSCHs, The configurations of the multiple DMRSs are the same, One of the configurations of the plurality of DMRSs is a DMRS configuration regarding a DMRS configuration type, a number of symbols used for a frontloading DMRS, and a number of symbols used for an additional DMRS. 17 . The network device according to claim 16 , wherein the DMRS configuration type is DMRS configuration type 1 or DMRS configuration type 2. 18 . The network device according to claim 17 , wherein the DMRS configuration type is configured using radio resource control (RRC) signaling.

19. The network device of claim 16, wherein the number of symbols used for the frontload DMRS is 1.

20. The network device of claim 16, wherein the number of symbols used for the frontloaded DMRS is configured using radio resource control (RRC) signaling and / or via downlink control information (DCI).

Images