Method performed by a terminal device, method performed by a network device, terminal device and network device

Abstract

To support a dynamic notification of the number of repetitions while reducing an overhead of a signal to a terminal device from a network device.SOLUTION: In a network 200, a method executed by a terminal device includes: selecting one DMRS table from a plurality of existed demodulation reference signal (DMRS) tables on the basis of a notification and / or downlink control information (DCI) in accordance with reception of the notification and the DCI from a network device at 250; determining a first setting for a DMRS communication via a physical shared channel on the basis of the DCI and the DMRS table in accordance with a notification that a repetition of the physical shared channel is invalid at 260; determining a second step for the DMRS communication by the number of repetitions and the repetition of the physical shared channel on the basis of the DCI and the DMRS table in accordance with the notification that the repetition of the physical shared channel is valid at 260; and performing a communication with the network device via the physical shared channel at 270.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to a method, apparatus, and computer storage medium for indicating the number of repetitions of a physical shared channel. [Background technology]

[0002] In new radio access (NR), a network device (e.g., next-generation NodeB (gNB)) may be configured with multiple transmission / reception points (TRPs) or antenna panels, i.e., the network device communicates with a terminal device (e.g., user equipment (UE)) via one or more of the multiple TRPs or antenna panels, which is also called "multi-TRP communication."

[0003] In some multi-TRP communication schemes, a single downlink control information (DCI) is used to schedule multiple Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) repetitions to achieve better performance. The number of repetitions can be changed to accommodate different service requirements and / or different propagation environments. Therefore, it is desirable to support dynamic notification of the number of repetitions while reducing overhead. Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, the exemplary embodiments of the present disclosure provide a method, apparatus, and computer storage medium for indicating transmission timing of a physical shared channel. [Means for solving the problem]

[0005] A first aspect provides a communication method, including: receiving, in a terminal device, downlink control information (DCI) from a network device for scheduling communication over a physical shared channel; in response to receiving a notification that repetition of the physical shared channel is enabled or disabled, selecting a DMRS table from a plurality of predefined demodulation reference signal (DMRS) tables based on the notification; when repetition of the physical shared channel is disabled, determining a first configuration for DMRS communication over the physical shared channel based on the DCI and the DMRS table; and when repetition of the physical shared channel is enabled, determining a number of repetitions and a second configuration for DMRS communication with repetition of the physical shared channel based on the DCI and the DMRS table.

[0006] A second aspect provides a communication method, including: sending a notification from a network device to a terminal device that repetition of a physical shared channel is enabled or disabled, selecting a DMRS table from a plurality of predefined DMRS tables based on the notification, generating downlink control information (DCI) for scheduling communication over the physical shared channel based on the DMRS table, where if repetition of the physical shared channel is disabled, the DCI indicates a first configuration for DMRS communication over the physical shared channel, and if repetition of the physical shared channel is enabled, the DCI indicates a number of repetitions and a second configuration for DMRS communication with the DCI physical shared channel repetition, and sending the DCI to the terminal device.

[0007] A third aspect provides a terminal device. The terminal device includes a processor and a memory. The memory is coupled to the processor and stores instructions. When executed by the processor, the instructions cause the terminal device to perform the following operations: receive downlink control information (DCI) from a network device for scheduling communication over a physical shared channel; in response to receiving a notification that repetition of the physical shared channel is enabled or disabled, select a DMRS table from a plurality of predefined demodulation reference signal (DMRS) tables based on the notification; when repetition of the physical shared channel is disabled, determine a first configuration for DMRS communication over the physical shared channel based on the DCI and the DMRS table; and when repetition of the physical shared channel is enabled, determine a number of repetitions and a second configuration for DMRS communication by repetition of the physical shared channel based on the DCI and the DMRS table.

[0008] A fourth aspect provides a network device. The network device includes a processor and a memory. The memory is coupled to the processor and has instructions stored therein. When executed by the processor, the instructions cause the network device to perform the following operations: sending a notification to a terminal device that repetition of a physical shared channel is enabled or disabled; selecting a DMRS table from a plurality of predefined DMRS tables based on the notification; generating downlink control information (DCI) for scheduling communication over the physical shared channel based on the DMRS table; where when repetition of the physical shared channel is disabled, the DCI indicates a first configuration for DMRS communication over the physical shared channel, and when repetition of the physical shared channel is enabled, the DCI indicates a number of repetitions and a second configuration for DMRS communication with the DCI physical shared channel repetition, and sending the DCI to the terminal device.

[0009] A fifth aspect provides a computer-readable medium having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to perform a method according to the first aspect of the present disclosure.

[0010] A sixth aspect provides a computer-readable medium having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to perform a method according to the second aspect of the present disclosure.

[0011] Other features of the present disclosure will become readily apparent from the following description. [Brief description of the drawings]

[0012] The above and other objects, features, advantages and merits of the present disclosure will become apparent from a more detailed description of several embodiments of the present disclosure in the drawings.

[0013] [Figure 1] 1 illustrates an exemplary communications network in which some embodiments of the present disclosure may be implemented;

[0014] [Diagram 2] FIG. 1 shows an exemplary signaling diagram of a schematic process according to some embodiments of the present disclosure.

[0015] [Figure 3A] 1 shows schematic diagrams of some embodiments of the present disclosure. [Figure 3B] 1 shows schematic diagrams of some embodiments of the present disclosure. [Figure 3C] 1 shows schematic diagrams of some embodiments of the present disclosure.

[0016] [Figure 4] 1 illustrates an exemplary method according to some embodiments of the present disclosure.

[0017] [Diagram 5]1 illustrates an exemplary method according to some embodiments of the present disclosure.

[0018] [Figure 6] FIG. 1 is a simplified block diagram of an apparatus capable of implementing embodiments of the present disclosure.

[0019] Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0020] Hereinafter, the principles of the present disclosure will be described with reference to some exemplary embodiments. It should be understood that these embodiments are for illustration and for those skilled in the art to understand and realize the present disclosure, and do not limit the scope of the present disclosure. The disclosure described in this specification can be realized in various ways other than the methods described below.

[0021] 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 pertains.

[0022] As used herein, the singular forms "a," "one," and "the" are intended to include the plural unless expressly stated. The term "comprises" and variations thereof are interpreted as open-ended terms and mean "including, but not limited to." The term "based on" should be interpreted as "based at least in part on." The terms "in one embodiment" and "embodiment" should be interpreted as "at least one embodiment." The term "another embodiment" should be interpreted as "at least one other embodiment." The terms "first," "second," etc., may refer to different or the same object. Other definitions, explicit and implicit, may be included below.

[0023] In some instances, values, programs or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It will be apparent that such descriptions contemplate that one may select from many functional alternatives to be used, and that such a selection is not necessarily better, lesser, higher, or preferred than other selections.

[0024] FIG. 1 illustrates an exemplary communication network 100 in which an embodiment of the present disclosure can be implemented. As shown in FIG. 1, the network 100 includes a network device 110 connected to two TRPs / panels 120-1, 120-2 (collectively referred to as TRPs 120 or individually referred to as TRPs 120). The network 100 further includes a terminal device 130 that is served by the network device 110. Note that the number of network devices, terminal devices, and TRPs in FIG. 1 is for illustrative purposes and is not intended to limit the present disclosure. The network 200 includes any number of devices in which an embodiment of the present disclosure can be implemented.

[0025] As used herein, the term "terminal device" refers to any device capable of wireless or wired communication. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, 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 supporting wireless or wired Internet access and browsing, etc. For illustrative purposes, some embodiments are described with reference to an example in which the UE is a terminal device 130.

[0026] The term "network equipment" or "base station" (BS) as used herein refers to equipment that provides or hosts a cell or coverage over which terminal equipment can communicate. Examples of network equipment include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next generation Node B (gNB), remote radio unit (RRU), radio head (RH), remote radio head (RRH), low power node, such as femto node, pico node, etc. The term "TRP" refers to an antenna array (having one or more antenna elements) available to a network equipment in a particular geographic location. For example, to achieve better coverage, a network equipment connects with multiple TRPs in different geographic locations. Here, a TRP may also be referred to as a "panel" and may refer to an antenna array (having one or more antenna elements) or a group of antennas.

[0027] In one embodiment, the terminal device 130 is connected to a first network device and a second network device (not shown in FIG. 1). One of the first network device and the second network device is at a master node and the other is at a slave node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device may be an eNB and the second RAT device may be a gNB. Information about the different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 130. In one embodiment, the first information may be transmitted from the first network device to the terminal device 130, and the second information may be transmitted from the second network device to the terminal device 130 directly or via the first network device. In one embodiment, information regarding the configuration of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device set by the second network device may be transmitted from the second network device to the terminal device directly or via the first network device. The information may be transmitted by radio resource control (RRC) signaling.

[0028] 1, the network device 110 can communicate with the terminal device 130 through TRPs 120-1 and 120-2. Hereinafter, the TRP 120-1 is also referred to as the first TRP, and the TRP 120-2 is also referred to as the second TRP. Each TRP 120 can provide multiple beams for communicating with the terminal device 130.

[0029] Communications in the communication network 100 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), and the like. Communications may also be based on any generation of communication protocols now known or 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] In addition to typical data communications, the network device 110 transmits a reference signal (RS) to the terminal device 130 in a broadcast, multicast, and / or unicast manner on the downlink (e.g., via TRP 120-1 or 120-2). Similarly, the terminal device 130 transmits an RS to the network device 110 on the uplink (e.g., via TRP 120-1 or 120-2). As used herein, "downlink (DL)" refers to a link from the network device to the terminal device, and "uplink (UL)" refers to a link from the terminal device to the network device. Examples of RS include, but are not limited to, a downlink or uplink demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), a sounding reference signal (SRS), a phase tracking reference signal (PTRS), a fine time / frequency tracking reference signal (TRS), and the like. A DMRS is a type of RS that provides modulation / demodulation information associated with a communication channel to ensure the accuracy or integrity of the encryption of information transmitted over the communication channel.

[0031] Prior to UL or DL ​​DMRS transmission, the network device 110 assigns a corresponding port (also referred to as a "DMRS port") for the DMRS transmission and / or designates a DMRS sequence to be transmitted. As used herein, a DMRS port refers to a specific mapping from a part or all of a DMRS sequence to one or more resource elements (REs) of a resource domain allocated for DMRS transmission in the time domain, frequency domain, and / or code domain. In NR, different DMRS ports are multiplexed based on a code division multiplexing (CDM) technique in the time domain and / or frequency domain, and / or a frequency division multiplexing (FDM) technique. For example, a group of DMRS ports is also referred to as a "DMRS port group" or a "DMRS group." A group of DMRS ports that are multiplexed based on a CDM technique is also referred to as a "CDM group."

[0032] In some embodiments, prior to DMRS transmission, such resource allocation information and other necessary information is indicated to terminal device 130. For example, the DMRS configuration is transmitted to terminal device 130 by higher layer signaling (e.g., Radio Resource Control (RRC) signaling and / or Medium Access Control (MAC) layer signaling) and / or dynamic signaling (e.g., Downlink Control Information (DCI)).

[0033] In some embodiments, a number of codewords (CWs) is configured in the terminal device 130. For example, this number may be 1 or 2. The number of CWs may be configured, for example, by RRC signaling, MAC layer signaling, and / or physical layer (PHY) signaling.

[0034] In some embodiments, a group of parameters for DMRS communication is configured in the terminal device 130. The parameters in the group include at least one of the following: maximum number / length of codes for DMRS, type of DMRS, etc. The parameters in the group may be configured by, for example, RRC signaling, MAC layer signaling, and / or physical layer (PHY) signaling.

[0035] In some embodiments, the maximum number / length of DMRS symbols (e.g., the maximum number / length is M) is the maximum number of symbols of each DMRS transmission timing within one PDSCH transmission duration, where one DMRS transmission timing includes K consecutive symbols. For example, M is 1, 2, 3, or 4. For example, K is 1, 2, 3, or 4, and K is less than or equal to M. In some embodiments, the maximum number / length of DMRS symbols (e.g., the maximum number / length is M) is equal to the maximum number of symbols of a front-loaded DMRS, where the front-loaded DMRS is the first DMRS transmission timing of the K consecutive symbols of one PDSCH transmission duration.

[0036] In some embodiments, the DMRS type is a DMRS configuration mode in the time domain and / or the frequency domain. There are a maximum of two DMRS types that can be configured in the terminal device (e.g., DMRS type 1 and / or DMRS type 2). In some embodiments, DMRS type 1 includes a maximum of eight DMRS ports (e.g., when the maximum number / length of DMRS is 2). Multiplexing is performed on the DMRS ports based on at least one of frequency division multiplexing (FDM), code division multiplexing (CDM) in the time domain, and CDM in the frequency domain. In some embodiments, DMRS type 1 includes a maximum of four DMRS ports (e.g., when the maximum number / length of DMRS is 1). Multiplexing is performed on the DMRS ports based on at least one of FDM and CDM in the frequency domain.

[0037] In some embodiments, DMRS Type 2 includes up to 12 DMRS ports (e.g., when the maximum number / length of DMRS is 2). Multiplexing is performed on the DMRS ports based on at least one of FDM (frequency domain multiplexing), CDM (code domain multiplexing) in the frequency domain, and CDM in the time domain. In some embodiments, DMRS Type 2 includes up to 6 DMRS ports (e.g., when the maximum number / length of DMRS is 1). Multiplexing is performed on the DMRS ports based on at least one of FDM and CDM in the frequency domain.

[0038] In some embodiments, when multiplexing to DMRS ports is based only on CDM in the time and / or frequency domain, the DMRS ports QCL each other on {Doppler shift, Doppler spread, average delay, average spread, spatial reception parameters} and / or average gain. Alternatively, the DMRS ports QCL each other on QCL-Type A and QCL-Type D, and / or average gain.

[0039] In some embodiments, DMRS ports in different DMRS groups multiplex using FDM and / or time domain multiplexing (TDM). In some embodiments, for DMRS Type 1, the maximum eight DMRS ports may be {0,1,2,3,4,5,6,7}. DMRS ports {0,1,4,5} multiplex using CDM in frequency and / or time domain, and DMRS ports {0,1,4,5} should QCL with each other for {Doppler shift, Doppler spread, mean delay, mean spread, spatial reception parameters} and / or mean gain and should be in one DMRS group. DMRS ports {2,3,6,7} multiplex using CDM in frequency and / or time domain, and QCL with each other for {Doppler shift, Doppler spread, mean delay, mean spread, spatial reception parameters} and / or mean gain and should be in one DMRS group.

[0040] In some embodiments, as an example of grouping of DMRS ports, for example, for DMRS Type 1 defined in the 3GPP specifications, up to two DMRS groups (DMRS group G1 and / or DMRS group G2) can be configured. For example, when two DMRS groups are configured, DMRS group G1 includes at least one DMRS port among DMRS ports {0, 1, 4, 5}, and DMRS group G2 includes at least one DMRS port among DMRS ports {2, 3, 6, 7}. Also, for example, when only one DMRS group is configured, there is only one DMRS group G1 or DMRS group G2, and DMRS group G1 or DMRS group G2 includes at least one DMRS port among DMRS ports {0, 1, 2, 3, 4, 5, 6, 7}.

[0041] In some embodiments, DMRS ports in different DMRS groups multiplex using FDM and / or TDM. In some embodiments, for DMRS Type 2, the maximum 12 DMRS ports are denoted as DMRS ports {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}. DMRS ports {0, 1, 6, 7} multiplex using CDM in frequency and / or time domain, QCL with each other for {Doppler shift, Doppler spread, average delay, average spread, spatial reception parameters} and / or average gain, and should be in one DMRS group. DMRS ports {2, 3, 8, 9} multiplex using CDM in frequency and / or time domain, QCL with each other for {Doppler shift, Doppler spread, average delay, average spread, spatial reception parameters} and / or average gain, and should be in one DMRS group. The DMRS ports {4,5,10,11} are multiplexed using CDM in the frequency domain and / or time domain, and QCL each other for {Doppler shift, Doppler spread, mean delay, mean expansion, spatial reception parameters} and / or mean gain, and should be in one DMRS group.

[0042] In some embodiments, as an example of grouping of DMRS ports, for example, for DMRS type 2 defined by the 3GPP specifications, up to two DMRS groups (DMRS group G1 and / or DMRS group G2) may be configured. For example, when two DMRS groups are configured, DMRS group G1 includes at least one DMRS port among DMRS ports {0, 1, 6, 7, 4, 5, 10, 11}, and DMRS group G2 includes at least one DMRS port among DMRS ports {2, 3, 8, 9}. Also, for example, when two DMRS groups are configured, DMRS group G1 includes at least one DMRS port among DMRS ports {0, 1, 6, 7}, and DMRS group G2 includes at least one DMRS port among DMRS ports {2, 3, 8, 9, 4, 5, 10, 11}. Also, for example, when two DMRS groups are configured, DMRS group G1 includes at least one DMRS port among DMRS ports {0, 1, 6, 7, 2, 3, 8, 9}, and DMRS group G2 includes at least one DMRS port among DMRS ports {4, 5, 10, 11}. Also, for example, when only one DMRS group is configured, there is only one DMRS group G1 or DMRS group G2, and DMRS group G1 or DMRS group G2 includes at least one DMRS port among DMRS ports {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}.

[0043] In some embodiments, as an example of grouping of DMRS ports, three DMRS groups (DMRS group G1, DMRS group G2, and DMRS group G3) are configured for DMRS type 2 defined in the 3GPP specifications. For example, when three DMRS groups are configured, DMRS group G1 includes at least one DMRS port among DMRS ports {0, 1, 6, 7}, DMRS group G2 includes at least one DMRS port among DMRS ports {2, 3, 8, 9}, and DMRS group G3 includes at least one DMRS port among DMRS ports {4, 5, 10, 11}.

[0044] In a conventional specification, a Transmission Control Indication (TCI) field may exist in the DCI. For example, the TCI field includes three or four bits, and the value of the TCI field is also called a "TCI code point." The TCI code point indicates one or more TCI states. The TCI state indicates a parameter for setting an RS set and a QCL relationship between one or two RSs in the RS set and a DMRS port of a PDSCH. The terminal device 130 may be configured with a DMRS type, a maximum number / length of DMRSs, and / or a number of CWs. When a predetermined DMRS type, a predetermined value of the maximum number / length of DMRSs, and a predetermined value of the number of CWs are configured, the terminal device 130 has one corresponding DMRS table for indicating the number of DMRS CDM groups (multiple) without data, the number of frontloaded DMRS codes, the number of DMRS ports, and the DMRS port index of at least one of the DMRS ports.

[0045] As described above, in some multi-TRP communication schemes, multiple PDSCH or PUSCH repetitions are scheduled using a single DCI to achieve better performance. The number of repetitions can be changed to accommodate different service requirements and / or different propagation environments. Therefore, it is desirable to support dynamic notification of the number of repetitions while reducing overhead.

[0046] An embodiment of the present invention provides a solution for indicating the number of repetitions of a physical shared channel. The solution presents different DMRS tables to indicate DMRS configuration in repetitive and non-repetitive scenarios. For non-repetitive scenarios, a conventional DMRS table is utilized. For repetitive scenarios, a new DMRS table is designed. The number of repetitions of a physical channel is signaled in an additional field in the DCI or is signaled implicitly by the DMRS configuration of the new DMRS table. In this way, dynamic signaling of the number of repetitions can be supported without increasing the signaling overhead in the DCI.

[0047] 2 illustrates an example signaling diagram of a schematic process 200 according to some embodiments of the present disclosure. As illustrated in FIG. 2, the process 200 relates to the network device 110 and the terminal device 130 of FIG. 1. Here, the process 200 may include additional processes not illustrated and / or omit some processes illustrated, and the scope of the present disclosure is not limited in this respect.

[0048] As shown in Fig. 2, the network device 110 sends 210 a notification to the terminal device 130 about whether the repetition of the physical shared channel is enabled. In some embodiments, the physical shared channel may be a PUSCH or a PDSCH. Some embodiments are described below with reference to an example in which the physical shared channel is a PDSCH. It should be understood that this is for illustrative purposes only and does not limit the scope of the present disclosure.

[0049] In some embodiments, the notification is sent from the network device 110 to the terminal device 130 via any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) layer signaling, or DCI. For example, a bit or a parameter may be used to indicate whether the repetition of the physical shared channel is enabled or disabled. When the notification is sent from the network device 110 to the terminal device 130 via DCI, dynamic switching between repetition and non-repetition scenarios may be supported.

[0050] As shown in FIG. 2, the network device 110 selects 220 a DMRS table from a number of predefined DMRS tables based on the notification. The selected DMRS table may be used to indicate a DMRS configuration and / or a number of repetitions of the physical shared channel. The network device 110 generates 230 a DCI for scheduling communication over the physical shared channel based on the selected DMRS table. In some embodiments, when repetition of the physical shared channel is disabled, the generated DCI may indicate a configuration for DMRS communication over the physical shared channel (hereinafter also referred to as a “first configuration”). In some embodiments, when repetition of the physical shared channel is enabled, the generated DCI may indicate both the number of repetitions and a configuration for DMRS communication with repetition of the physical shared channel (hereinafter also referred to as a “second configuration”). The network device 110 transmits 240 the generated DCI to the terminal device 130.

[0051] In response to receiving the notification and the DCI from the network device 110, the terminal device 130 selects one DMRS table from a number of predefined DMRS tables based on the notification and / or the DCI 250. In response to the notification that repetition of the physical shared channel has been disabled, the terminal device 130 determines a first configuration for DMRS communication over the physical shared channel based on the DCI and the DMRS table 260. In response to the notification that repetition of the physical shared channel has been enabled, the terminal device 130 determines a number of repetitions and a second configuration for DMRS communication with repetition of the physical shared channel based on the DCI and the DMRS table 260.

[0052] Then, as shown in FIG. 2, the network device 110 and the terminal device 130 communicate via a physical shared channel 270. For example, in PUSCH communication, if the repetition of PUSCH is disabled, the terminal device 130 transmits a DMRS to the network device 110 by PUSCH based on a first configuration. If the repetition of PUSCH is enabled, the terminal device 130 transmits at least one DMRS to the network device 110 by PUSCH repetition based on a second configuration. For example, in PDSCH communication, if the repetition of PDSCH is disabled, the network device 110 transmits a DMRS to the terminal device 130 by PDSCH based on a first configuration. If the repetition of PDSCH is enabled, the network device 110 transmits at least one DMRS to the terminal device 130 by PDSCH repetition based on a second configuration.

[0053] In some embodiments, multiple DMRS tables indicating different DMRS configurations may be specified or predefined in the network device 110 and / or the terminal device 130. The DMRS table includes multiple configurations for DMRS communication between the network device 110 and the terminal device 130 over a physical shared channel (e.g., PDSCH or PUSCH). Each configuration in the DMRS table (also referred to as a "DMRS configuration") indicates at least one of a DMRS port, a number of DMRS CDM groups without data, a number of frontloaded DMRS codes, a number of DMRS ports, and a DMRS port index. In general, given a predetermined DMRS type, a predetermined value of the maximum number / length of DMRS, and a predetermined value of the number of CWs, a corresponding DMRS table can be determined to indicate the DMRS configuration.

[0054] In some embodiments, the multiple predefined DMRS tables include at least a first DMRS table (hereinafter also referred to as "DMRS Table A") and a second DMRS table (hereinafter also referred to as "DMRS Table B"). DMRS Table A may be different from DMRS Table B. In some embodiments, if the notification indicates that the repetition of the physical shared channel is disabled, select DMRS Table A (i.e., the first DMRS table), and if the notification indicates that the repetition of the physical shared channel is enabled, select DMRS Table B (i.e., the second DMRS table). FIG. 3A illustrates an example of such an embodiment. As shown in FIG. 3A, if the notification is "0", it means that the repetition of the physical shared channel is disabled, in which case DMRS Table A can be selected, and if the notification is "1", it means that the repetition of the physical shared channel is enabled, in which case DMRS Table B can be selected.

[0055] In some embodiments, DMRS Table A may differ from DMRS Table B in at least one of the number of available DMRS ports, the number of available front-loaded symbols for DMRS, the number of available DMRS CDM groups, and the number of available CWs.

[0056] In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table A may be 1, 2, 3, or 4. In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 2, the number of available DMRS ports in DMRS Table A may be 1, 2, 3, 4, 5, 6, 7, or 8. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table A may be 1, 2, 3, 4, 5, or 6. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 2, the number of available DMRS ports in DMRS Table A may be 1, 2, 3, 4, 5, 6, 7, or 8. In some embodiments, the number of available DMRS ports in DMRS Table B may be 1 or 2. In some embodiments, DMRS Table B may not be present, or the bit / field to indicate DMRS Table B may not be present in the DCI. For example, in this case, the number of DMRS ports may be assumed to be 1. Also, for example, in this case, the DMRS port may be assumed to be DMRS port 0.

[0057] In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table A may be one or two. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table B may be only one. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table B may be only two. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table A may be one, two or three. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table B may be only one. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table B may be only two. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table B may be only three.

[0058] In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for frontloading DMRS or the maximum length of the DMRS is 2, the number of available CWs in DMRS Table A may be 1 or 2. In some embodiments, for DMRS Type 2, the number of available CWs in DMRS Table A may be 1 or 2. In some embodiments, the number of available CWs in DMRS Table B may be only 1.

[0059] In some embodiments, if the maximum number of OFDM symbols for a frontload DMRS, or the maximum length of a DMRS, is 2, then the number of available frontload symbols for a DMRS in DMRS Table A may be 1 or 2, and the number of available frontload symbols for a DMRS in DMRS Table B may be only 1 (e.g., there may be no notification of the number of frontload symbols for a DMRS in DMRS Table B).

[0060] In some embodiments, the number of bits required to indicate a setting from DMRS Table A (e.g., the first setting described above) may be similar to the number of bits required to indicate a setting from DMRS Table B (e.g., the second setting described above).

[0061] In some embodiments, the configuration from DMRS Table B indicates the number of repetitions of the physical shared channel. For example, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Table B indicate different numbers of repetitions. For example, the number of repetitions indicated by the configurations in DMRS Table B may be any one of 2, 3, 4, 5, 6, 8, or 16. In some embodiments, the configuration from DMRS Table A may not indicate the number of repetitions of the physical shared channel. Alternatively, in some embodiments, the number of repetitions of the physical shared channel is assumed to be 1 for each configuration from DMRS Table A.

[0062] In some embodiments, the number of bits required to indicate a configuration from DMRS Table A (e.g., the first configuration described above) may be different from the number of bits required to indicate a configuration from DMRS Table B (e.g., the second configuration described above). For example, assume that the number of bits indicating a configuration from DMRS Table A is X and the number of bits indicating a configuration from DMRS Table B is Y, where X is a positive integer and Y is a non-negative integer. In some embodiments, X may be 4, 5 or 6. In some embodiments, X is greater than Y. In some embodiments, Y may be 0, 1, 2 or 3. In some embodiments, DMRS Table B may not be present. Alternatively, the DCI may not have a bit / field to indicate DMRS Table B, i.e., Y is 0.

[0063] In some embodiments, as shown in FIG. 3B, if the notification disables repetition of the physical shared channel, the DCI may not have an additional field to indicate the number of repetitions, while if the notification enables repetition of the physical shared channel, the DCI may have an additional field to indicate the number of repetitions. For example, assume that the size of the additional field is Z bits, where Z is a non-negative integer. For example, Z may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the number of repetitions indicated by the additional field may be any one of 2, 3, 4, 5, 6, 8, or 16. In some embodiments, if the number of bits indicating the configuration from DMRS Table A is X and the number of bits indicating the configuration from DMRS Table B is Y (X is a positive integer and Y is a non-negative integer, for example, X is 4, 5, or 6, and Y is 0, 1, 2, 3, or 4), the number of bits indicating the configuration from DMRS Table A is equal to the sum of the number of bits indicating the configuration from DMRS Table B and the size of the additional field. That is, Y+Z=X. In this way, dynamic reporting of the number of repetitions can be supported without increasing reporting overhead in the DCI. In some embodiments, the number of bits indicating the configuration from DMRS Table A is X (X is a positive integer, e.g., X is 4, 5, or 6), and if there is no reporting of DMRS Table B or the number of bits indicating the configuration from DMRS Table B is 0, the number of bits indicating the configuration from DMRS Table A is equal to the number of bits indicating the number of repetitions in the additional field, i.e., Z=X.

[0064] In some embodiments, the network device 110 determines one or more transmission control indication (TCI) states for data communication between the network device 110 and the terminal device 130 over the physical shared channel, and indicates one or more TCI states in the DCI. A TCI state indicates a reference signal (RS) set and parameters that configure a quasi-co-location (QCL) relationship between RSs in the RS set and DMRS ports for PDSCH or PUSCH. For example, different TCI states are used for different TRPs 120.

[0065] In some embodiments, the multiple predefined DMRS tables may include at least a third DMRS table (hereinafter also referred to as "DMRS Table C"), a fourth DMRS table (hereinafter also referred to as "DMRS Table D"), a fifth DMRS table (hereinafter also referred to as "DMRS Table E"), and a sixth DMRS table (hereinafter also referred to as "DMRS Table F"). In some embodiments, as shown in FIG. 3C, if the indication indicates that physical shared channel repetition is disabled and only one TCI state is indicated in the DCI, DMRS Table C (i.e., the third DMRS table) may be selected, and if the indication indicates that physical shared channel repetition is disabled and multiple TCI states are indicated in the DCI, DMRS Table D (i.e., the fourth DMRS table) may be selected. If the indication indicates that physical shared channel repetition is enabled and only one TCI state is indicated in the DCI, DMRS Table E (i.e., the fifth DMRS table) may be selected. If the indication indicates that physical shared channel repetition is enabled and multiple TCI states are indicated in the DCI, then DMRS Table F (ie, the sixth DMRS table) may be selected.

[0066] In some embodiments, any two of DMRS tables C, D, E, and F may differ from each other in at least one of the number of available DMRS ports, the number of available frontload codes for DMRS, the number of available DMRS CDM groups, and the number of available CWs.

[0067] In some embodiments, DMRS Table C may be a conventional DMRS table in Release 15 (Rel-15) of the 3GPP specifications. In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table C may be 1, 2, 3, or 4. In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for frontload DMRS or the maximum length of the DMRS is 2, the number of available DMRS ports in DMRS Table C may be 1, 2, 3, 4, 5, 6, 7, or 8. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table C may be 1, 2, 3, 4, 5, or 6. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for frontloading DMRS, or the maximum length of the DMRS, is 2, the number of available DMRS ports in DMRS Table C may be 1, 2, 3, 4, 5, 6, 7 or 8.

[0068] In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that have no data in DMRS Table C may be 1 or 2. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that have no data in DMRS Table C may be 1, 2, or 3.

[0069] In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for frontloading DMRS or the maximum length of the DMRS is 2, the number of available CWs in DMRS Table C may be 1 or 2. In some embodiments, for DMRS Type 2, the number of available CWs in DMRS Table C may be 1 or 2.

[0070] In some embodiments, if the maximum number of OFDM symbols for frontload DMRS, or the maximum length of a DMRS, is two, then the number of available frontload symbols for a DMRS in DMRS Table C may be one or two.

[0071] In some embodiments, in DMRS Table D, the number of available DMRS ports may be 1, 2, 3 or 4. In some embodiments, the number of available DMRS ports in DMRS Table D may be 2, 3 or 4. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table D may be only 2. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table D may be 2 or 3. In some embodiments, the number of available CWs in DMRS Table D may be only 1. In some embodiments, the number of available frontload codes for a DMRS in DMRS Table D may be only 1.

[0072] In some embodiments, the configurations from DMRS Tables C and / or D may not indicate the number of repetitions of the Physical Shared Channel. Alternatively, in some embodiments, the number of repetitions of the Physical Shared Channel may be assumed to be 1 for each configuration from DMRS Tables C and / or D.

[0073] In some embodiments, the number of available DMRS ports in DMRS Table E may be one or two. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table E may be only one. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table E may be only two. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table E may be only one. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table E may be only three. In some embodiments, the number of available CWs in DMRS Table E may be only one. In some embodiments, the number of available frontload codes for a DMRS in DMRS Table E may be only one.

[0074] In some embodiments, the number of available DMRS ports in DMRS Table F may be one or two. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table F may be only one. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) that do not have data in DMRS Table F may be only two. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table F may be only one. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) that do not have data in DMRS Table F may be only three. In some embodiments, the number of available CWs in DMRS Table F may be only one. In some embodiments, the number of available frontload codes for a DMRS in DMRS Table F may be only one.

[0075] In some embodiments, the number of bits required to indicate a setting from DMRS Table C, the number of bits required to indicate a setting from DMRS Table D, the number of bits required to indicate a setting from DMRS Table E, and the number of bits required to indicate a setting from DMRS Table F may be similar.

[0076] In some embodiments, the configurations from DMRS Tables E and / or F indicate the number of repetitions of the physical shared channel. For example, there may be several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups with no data. These configurations indicate different numbers of repetitions. For example, the number of repetitions indicated by the configurations in DMRS Tables E and / or F may be any one of 2, 3, 4, 5, 6, 8, or 16. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate the number of repetitions of the physical shared channel.

[0077] In some embodiments, the number of bits required to indicate a configuration from DMRS Table C may be different from the number of bits required to indicate a configuration from DMRS Table E. Alternatively or additionally, the number of bits required to indicate a configuration from DMRS Table D may be different from the number of bits required to indicate a configuration from DMRS Table F. For example, assume that the number of bits indicating a configuration from DMRS Table C or D is X, the number of bits indicating a configuration from DMRS Table E is Y1, and the number of bits indicating a configuration from DMRS Table F is Y2, where X is a positive integer and Y1 and Y2 are non-negative integers. In some embodiments, X may be 4, 5, or 6. In some embodiments, X is greater than Y1. In some embodiments, X is greater than Y2. In some embodiments, Y1 may be 0, 1, 2, or 3. In some embodiments, Y2 may be 0, 1, 2, or 3.

[0078] In some embodiments, as shown in FIG. 3B, if the indication indicates that the repetition of the physical shared channel is disabled, the DCI may not have an additional field to indicate the number of repetitions, while if the indication indicates that the repetition of the physical shared channel is enabled, the DCI may not have an additional field to indicate the number of repetitions. For example, if only one TCI state is indicated in the DCI, the size of the additional field is Z1 bits, where Z1 is a non-negative integer. For example, Z1 may be 0, 1, 2, 3, or 4. Also, if multiple TCI states are indicated in the DCI, the size of the additional field is Z2 bits, where Z2 is a non-negative integer. For example, Z2 may be 0, 1, 2, 3, or 4. In some embodiments, the number of repetitions indicated by the additional field may be any one of 1: 2, 3, 4, 5, 6, 8, or 16. In some embodiments, X, Y1, and Z1 satisfy the formula: Y1+Z1=X. In some embodiments, X, Y2, and Z2 satisfy the formula: Y2 + Z2 = X. In this way, dynamic signaling of the number of repetitions can be supported without increasing the signaling overhead in the DCI.

[0079] In some embodiments, if only one TCI state is indicated to the terminal device 130, the TCI state applies to all DMRS ports indicated to the terminal device 130. In some embodiments, if only one TCI state is indicated and a phase tracking reference signal (PTRS) is configured in the terminal device 130, the number of PTRS ports may be only one. In some embodiments, a first TCI state and a second TCI state may be indicated to the terminal device 130, and the terminal device 130 may be notified that physical shared channel repetition is disabled. In some embodiments, if the indicated DMRS port belongs to only one CDM group, the first TCI state is associated with the DMRS port. In some embodiments, if multiple TCI states are indicated, the indicated DMRS port belongs to only one CDM group, and a PTRS is configured in the terminal device 130, the number of PTRS ports may be only one. In some embodiments, if the notified DMRS port belongs to multiple CDM groups, the first and second TCI states are associated with different DMRS ports. In some embodiments, if multiple TCI states are notified, the notified DMRS port belongs to multiple CDM groups, repetition is disabled, and a PTRS is configured in the terminal device 130, the number of PTRS ports may be two. In some embodiments, the first TCI state and the second TCI state are notified to the terminal device 130, and the terminal device 130 is notified that repetition of the physical shared channel is enabled (i.e., the number of repetitions is greater than one). In this case, for some repetitions, the first TCI state is associated with all DMRS ports notified to the terminal device 130, and for other repetitions, the second TCI state is associated with all DMRS ports notified to the terminal device 130. In some embodiments, when multiple TCI states are notified, the notified DMRS port belongs to multiple CDM groups, repetition is enabled, and the PTRS is configured in the terminal device 130, the number of PTRS ports may be only one for each repeated transmission timing.In some embodiments, when multiple TCI states are signaled, the signaled DMRS ports belong to multiple CDM groups, repetition is enabled, and a PTRS is configured in the terminal device 130, the number of PTRS ports for each repeating transmission timing may be only one. Also, the PTRS port index may be different for the repeating transmission timings associated with different TCI states.

[0080] In some embodiments, the number of repetitions is configured via higher layer parameters, and if the number of repetitions is greater than one, a new DMRS table may be used to generate the DCI. In some embodiments, only one or two DMRS ports may be available in the new DMRS table. In some embodiments, for DMRS Type 1, the number of available CDM groups with no data in the new DMRS table is two. In some embodiments, for DMRS Type 2, the number of available CDM groups with no data in the new DMRS table is three. In some embodiments, for a configuration from the new DMRS table that indicates only one DMRS port, DMRS port 0 may be used. In some embodiments, for a configuration from the new DMRS table that indicates two DMRS ports, DMRS port 0 and DMRS port 2 may be used. In some embodiments, there may be several configurations in the new DMRS table that indicate only one DMRS port, and these configurations indicate different numbers of repetitions. In some embodiments, there may be several configurations in the new DMRS table that indicate two DMRS ports, and these configurations indicate different numbers of repetitions. In some embodiments, the number of bits in the DCI that indicate a configuration from the DMRS table may be zero. In this case, it may be assumed that DMRS Port 0 is used for DMRS communication, and the number of DMRS CDM groups with no data may be assumed to be two or three for DMRS Type 1 and DMRS Type 2, respectively.

[0081] In some embodiments, when the maximum number of layers of the physical shared channel is 2, the DCI may have only one bit indicating the DMRS configuration. For example, two DMRS configurations are supported, one indicating DMRS port 0 and the other indicating DMRS port 0 and DMRS port 2. In some embodiments, when the maximum number of layers of the physical shared channel is 1, the DCI may not have a bit indicating the DMRS configuration. For example, it may be assumed that DMRS port 0 is used for DMRS communication.

[0082] In some embodiments, different schemes for ultra-reliable low latency communication (URLLC) with multiple TRPs with at least single DCI scheduling are classified as follows: Scheme 1 (Spatial Division Multiplexing): Supports n TCI states in a single time slot with overlapping frequency resource allocation; Scheme 2 (FDM): Supports n TCI states in a single time slot with non-overlapping frequency resource allocation, each non-overlapping frequency resource allocation is associated with one TCI state, and single / multiple DMRS ports are associated with all non-overlapping frequency resource allocations; Scheme 3 (TDM): Supports n TCI states in a single time slot with non-overlapping resource allocation; Scheme 4 (TDM): Supports n TCI states in K (n<=K) different time slots. In scheme 1, each transmission timing is one layer or a set of layers of the same TB, and each layer or set of layers is associated with one TCI and a group of DMRS ports. A single codeword (CW) with one redundancy version (RV) is used for all spatial layers or a set of spatial layers. From the UE perspective, different coded bits are mapped to different layers or a set of layers, and the mapping rule is similar to that in Rel-15. Scheme 2 is further divided into two sub-schemes: Scheme 2a and Scheme 2b. In Scheme 2a, a single CW with one RV is used for all resource allocations. From the UE perspective, a common RB mapping (e.g., CW to layer mapping in Rel-15) is used for all resource allocations. In Scheme 2b, a single CW with one RV is used for each allocation of non-overlapping frequency resources. The RVs corresponding to each allocation of non-overlapping frequency resources may be the same or different. In Scheme 3, each transmission timing of a TB has one TCI and one RV, and the time granularity is a mini-timeslot. All transmission timings within a time slot use a common MCS with single or multiple same DMRS ports.The RV / TCI state in each transmission timing may be the same or different. In scheme 4, each transmission timing of the TB has one TCI and one RV. All transmission timings in the K time slots use a common MCS with the same DMRS port or ports. The RV / TCI state in each transmission timing may be the same or different.

[0083] In some embodiments, DMRS Table A may differ from DMRS Table B in at least one of the following: number of available DMRS ports, number of available frontload codes for DMRS, number of available DMRS CDM groups, number of repetitions, repetition scheme (e.g., Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, and / or any combination thereof), code / timeslot offset between repetitions in the time domain, allocation of resources for repetitions in the frequency domain, allocation of resources for repetitions in the time domain, resource block offset or resource block group offset between repetitions in the frequency domain, RV sequence for repetitions, number of TCI states, and number of available CWs.

[0084] In some embodiments, the configuration from DMRS Table B indicates at least one of the number of repetitions of the physical shared channel, the repetition scheme, the RV sequence for the repetition, the number of TCI states, the repetitions in different timeslots, the repetitions in a single timeslot, and the code / timeslot offset between the repetitions in the time domain and / or the RB offset between the repetitions in the frequency domain. In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, the same DMRS port index, the same number of frontload codes and data for DMRS, but the same number of DMRS CDM groups. These configurations in DMRS Table B indicate different numbers of repetitions. For example, the number of repetitions indicated by the configurations in DMRS Table B is any one of 2, 3, 4, 5, 6, 8, or 16. In some embodiments, the configuration from DMRS Table A may not indicate the number of repetitions of the physical shared channel. Alternatively, in some embodiments, it is assumed that for each configuration from DMRS Table A, the number of repetitions of the physical shared channel is 1.

[0085] In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Table B indicate different repetition schemes. For example, the repetition scheme indicated by the configurations in DMRS Table B may be any one of Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, or Scheme 4. In some embodiments, the configurations from DMRS Table A may not indicate a repetition scheme for the physical shared channel. Alternatively, in some embodiments, it may be assumed that for each configuration from DMRS Table A, the repetition scheme for the physical shared channel is Scheme 1.

[0086] In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Table B indicate different code / timeslot offset values ​​between repetitions. For example, the code / timeslot offset value between repetitions indicated by the configurations in DMRS Table B may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. For example, the code offset between repetitions is used for Scheme 3. In some embodiments, the configurations from DMRS Table A may not indicate the code / timeslot offset value between repetitions of the physical shared channel. In some embodiments, the code offset value is only used in repetitions associated with different TCI states. In some embodiments, the code offset may be calculated from the last code of a repetition to the first code of a subsequent repetition. In some embodiments, the code offset may be calculated from the first code of a repetition to the first code of a subsequent repetition. In some embodiments, a code offset may be calculated from the last code of one iteration to the last code of a subsequent iteration.

[0087] In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Table B indicate different RB offset values ​​between repetitions and / or starting RB indexes for each repetition. In some embodiments, the RB offset values ​​between repetitions indicated by the configurations in DMRS Table B are non-negative integers. For example, the RB offset values ​​are greater than 0 and less than 276. For example, the RB offset values ​​between repetitions are used for Scheme 2a and / or Scheme 2b. In some embodiments, the RB offset may be calculated from the end of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the start of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the end of an iteration to the end of a subsequent iteration. In some embodiments, the configurations from DMRS Table A may not indicate RB offset values ​​between repetitions of the physical shared channel.

[0088] In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Table B indicate different RV sequences for repetitions of the physical shared channel. In some embodiments, the configurations in DMRS Table B indicate RV sequences of repetitions or cyclic shifts of RV sequences. For example, the RV sequence indicated by the configurations may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3}, or {0,0,0,0}. In some embodiments, the configurations from DMRS Table A may not indicate RV sequences for repetitions of the physical shared channel.

[0089] In some embodiments, there are several configurations in DMRS Table B that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups with no data. These configurations in DMRS Table B indicate different numbers of TCI states. In some embodiments, the number of TCI states indicated by the configurations in DMRS Table B may be any one of 1, 2, 3, or 4. In some embodiments, the configurations from DMRS Table A may not indicate the number of TCI states for repetition of the physical shared channel.

[0090] In some embodiments, if the notification disables repetition of the physical shared channel, the DCI may not have additional fields to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4. In some embodiments, if the notification enables repetition of the physical shared channel, the DCI may have one or more additional fields to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4.

[0091] In some embodiments, the DCI may have an additional field to indicate the repetition scheme. The size of the additional field is assumed to be W1 bits, where W1 is a non-negative integer. For example, W1 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the repetition scheme indicated by the additional field may be any one of Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, or any combination thereof. In some embodiments, the DCI has an additional field to indicate a code / timeslot offset value between repetitions in the time domain. The size of the additional field is assumed to be W2 bits, where W2 is a non-negative integer. For example, W2 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the code / timeslot offset value between repetitions may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. In some embodiments, the DCI has an additional field to indicate a RB offset value between repetitions in the frequency domain. The size of the additional field is assumed to be W3 bits, where W3 is a non-negative integer. For example, W3 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the value of the additional field is associated with one predefined value of the RB offset configured by RRC and / or MAC signaling. For example, different values ​​of the additional field are associated with different predefined values ​​of the RB offset configured in RRC and / or MAC signaling. In some embodiments, there is an additional field in the DCI to indicate the repeating RV sequence. Assume the size of the additional field is W4 bits, where W4 is a non-negative integer. For example, W4 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the additional field indicates the repeating RV sequence or a cyclic shift of the RV sequence. For example, the RV sequence indicated by the additional field may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3}, or {0,0,0,0}.In some embodiments, there is an additional field in the DCI to indicate the number of TCI states. Assume the size of the additional field is W5 bits, where W5 is a non-negative integer. For example, W5 may be 0, 1, or 2. In some embodiments, the number of TCI states indicated by the additional field may be any one of 1, 2, 3, or 4. In some embodiments, if the number of bits indicating the configuration from DMRS table A is X and the number of bits indicating the configuration from DMRS table B is Y (X is a positive integer and Y is a non-negative integer, for example, X may be 4, 5, or 6, and Y may be 0, 1, 2, 3, or 4), then the number of bits indicating the configuration from DMRS table A is equal to the number of bits indicating the configuration from DMRS table B plus the size of the one or more additional fields. That is, Y+Z+W1+W2+W3+W4+W5=X. In some embodiments, at least one of Z, W1, W2, W3, W4, and W5 is equal to 0. In this way, dynamic reporting of any number of repetitions, repetition schemes, repetition sequences, number of TCI states, code / timeslot offset values ​​between repetitions in the time domain or RB offset values ​​between repetitions in the frequency domain can be supported without increasing the reporting overhead in the DCI.

[0092] In some embodiments, any two of DMRS tables C, D, E, and F may differ from each other in at least one of the following: number of available DMRS ports, number of available frontload codes for DMRS, number of available DMRS CDM groups, number of available CWs, number of repetitions, repetition scheme (e.g., Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, and / or any combination thereof), code / timeslot offset between repetitions in the time domain, resource allocation for repetitions in the frequency domain, resource allocation for repetitions in the frequency domain, resource block offset or resource block group offset between repetitions in the frequency domain, RV sequence for repetitions, and number of TCI states.

[0093] In some embodiments, any two of DMRS tables C, D, E, and F may differ from each other in at least one of the following: number of available DMRS ports, number of available frontload codes for DMRS, number of available DMRS CDM groups, number of repetitions, repetition scheme (e.g., Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, and / or any combination thereof), repetition RV sequence, number of TCI states, code / timeslot offset between repetitions in the time domain, resource allocation for repetitions in the frequency domain, resource allocation for repetitions in the frequency domain, resource block offset or resource block group offset between repetitions in the frequency domain, and number of available CWs.

[0094] In some embodiments, the configuration from DMRS Tables E and / or F indicates at least one of the number of repetitions of the physical shared channel, the repetition scheme, the RV sequence of the repetitions, the number of TCI states, the repetitions in different timeslots, the repetitions within a single timeslot, the code / timeslot offset between the repetitions in the time domain, and the RB offset between the repetitions in the frequency domain. For example, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, the same DMRS port index, the same number of frontload codes for DMRS and the same number of DMRS CDM groups without data. These configurations indicate different numbers of repetitions. For example, the number of repetitions indicated by the configurations in DMRS Tables E and / or F may be any one of 2, 3, 4, 5, 6, 8, or 16. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate the number of repetitions of the physical shared channel.

[0095] In some embodiments, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS CDM groups that do not have the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes and data for DMRS. These configurations in DMRS Tables E and / or F indicate different repetition schemes. For example, the repetition scheme indicated by the configurations in DMRS Tables E and / or F may be any one of Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, and Scheme 4. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate a repetition scheme for the physical shared channel. Alternatively, in some embodiments, for each configuration from DMRS Tables C and / or D, the repetition scheme for the physical shared channel may be assumed to be Scheme 1.

[0096] In some embodiments, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Tables E and / or F indicate different code / timeslot offset values ​​between repetitions. For example, the code / timeslot offset value between repetitions indicated by the configurations in DMRS Tables E and / or F may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. For example, the code offset value between repetitions is used for Scheme 3. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate code / timeslot offset values ​​between repetitions of the physical shared channel. In some embodiments, the code offset value is only used between repetitions associated with different TCI states. In some embodiments, the code offset may be calculated from the last code of a repetition to the first code of a subsequent repetition. In some embodiments, the code offset may be calculated from the first code of a repetition to the first code of a subsequent repetition. In some embodiments, a code offset may be calculated from the last code of one iteration to the last code of a subsequent iteration.

[0097] In some embodiments, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, the same DMRS port index, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Tables E and / or F indicate different RB offset values ​​between repetitions and / or starting RB indexes for each repetition. In some embodiments, the RB offset values ​​between repetitions indicated by the configurations in DMRS Tables E and / or F are non-negative integers. For example, the RB offset values ​​are greater than 0 and less than 276. For example, the RB offset values ​​between repetitions are used for Scheme 2a and / or Scheme 2b. In some embodiments, the RB offset may be calculated from the end of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the start of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the end of an iteration to the end of a subsequent iteration. In some embodiments, the configuration from DMRS Tables C and / or D may not indicate an offset value of the RBs between repetitions of the physical shared channel.

[0098] In some embodiments, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Tables E and / or F indicate different RV sequences for the repetition of the physical shared channel. In some embodiments, the configurations from DMRS Tables E and / or F indicate RV sequences of the repetitions or cyclic shifts of the RV sequences. For example, the RV sequence indicated by the configurations may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3}, or {0,0,0,0}. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate RV sequences for the physical shared channel repetitions.

[0099] In some embodiments, there are several configurations in DMRS Tables E and / or F that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Tables E and / or F indicate different numbers of TCI states. In some embodiments, the number of TCI states indicated by the configurations in DMRS Tables E and / or F may be any one of 1, 2, 3, or 4. In some embodiments, the configurations from DMRS Tables C and / or D may not indicate the number of TCI states for the physical shared channel.

[0100] In some embodiments, if only one TCI state is indicated in the DCI and the notification disables repetition of the physical shared channel, the DCI may not have additional fields to indicate at least one of the following: number of repetitions, repetition scheme, RV sequence for repetition, number of TCI states, code / timeslot offset value between repetitions in the time domain, RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4. In some embodiments, if the notification enables repetition of the physical shared channel, the DCI may have one or more additional fields to indicate at least one of the following: number of repetitions, repetition scheme, RV sequence for repetition, number of TCI states, code / timeslot offset value between repetitions in the time domain, RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4.

[0101] In some embodiments, if the DCI indicates multiple TCI states and the notification disables repetition of the physical shared channel, the DCI may not have additional fields to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4. In some embodiments, if the notification enables repetition of the physical shared channel, the DCI may have one or more additional fields to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4.

[0102] In some embodiments, if only one TCI state is indicated in the DCI, there is an additional field in the DCI to indicate the repetition scheme. The size of the additional field is assumed to be U1 bits, where U1 is a non-negative integer. For example, U1 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the repetition scheme indicated by the additional field may be any one of scheme 1, scheme 2a, scheme 2b, scheme 3, scheme 4, or any combination thereof. In some embodiments, there is an additional field in the DCI to indicate the offset value of the code / timeslot between repetitions in the time domain. The size of the additional field is assumed to be U2 bits, where U2 is a non-negative integer. For example, U2 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the offset value of the code / timeslot between repetitions may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. In some embodiments, there is an additional field in the DCI to indicate the offset value of the RB between repetitions in the frequency domain. Assume the size of the additional field is U3 bits, where U3 is a non-negative integer. For example, U3 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the value of the additional field is associated with one predefined value of the RB offset configured by RRC and / or MAC signaling. For example, different values ​​of the additional field are associated with different predefined values ​​of the RB offset configured in RRC and / or MAC signaling. In some embodiments, the DCI has an additional field to indicate a repeating RV sequence. Assume the size of the additional field is U4 bits, where U4 is a non-negative integer. For example, U4 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the additional field indicates a repeating RV sequence or a cyclic shift of the RV sequence. For example, the RV sequence indicated by the additional field may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3} or {0,0,0,0}.In some embodiments, there is an additional field in the DCI to indicate the number of TCI states. Assume the size of the additional field is U5 bits, where U5 is a non-negative integer. For example, U5 may be 0, 1, or 2. In some embodiments, the number of TCI states indicated by the additional field may be any one of 1, 2, 3, or 4. In some embodiments, if the number of bits indicating the configuration from DMRS Table A is X and the number of bits indicating the configuration from DMRS Table B is Y (X is a positive integer and Y is a non-negative integer, for example, X may be 4, 5, or 6, and Y may be 0, 1, 2, 3, or 4), the number of bits indicating the configuration from DMRS Table A is equal to the number of bits indicating the configuration from DMRS Table B plus the size of the one or more additional fields. That is, Y+Z1+U1+U2+U3+U4+U5=X. In some embodiments, at least one of Z1, U1, U2, U3, U4, and U5 is equal to 0. In this way, dynamic reporting of any number of repetitions, repetition schemes, repetition sequences, number of TCI states, code / timeslot offset values ​​between repetitions in the time domain or RB offset values ​​between repetitions in the frequency domain can be supported without increasing the reporting overhead in the DCI.

[0103] In some embodiments, when multiple TCI states are indicated in the DCI, there may be an additional field in the DCI to indicate the repetition scheme. Assume the size of the additional field is V1 bits, where V1 is a non-negative integer. For example, V1 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the repetition scheme indicated by the additional field may be any one of Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, or any combination thereof. In some embodiments, there is an additional field in the DCI to indicate a code / timeslot offset value between repetitions in the time domain. Assume the size of the additional field is V2 bits, where V2 is a non-negative integer. For example, V2 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the code / timeslot offset value between repetitions may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. In some embodiments, there is an additional field in the DCI to indicate a RB offset value between repetitions in the frequency domain. Assume the size of the additional field is V3 bits, where V3 is a non-negative integer. For example, V3 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the value of the additional field is associated with one predefined value of the RB offset configured by RRC and / or MAC signaling. For example, different values ​​of the additional field are associated with different predefined values ​​of the RB offset configured in RRC and / or MAC signaling. In some embodiments, the DCI has an additional field to indicate a repeating RV sequence. Assume the size of the additional field is V4 bits, where V4 is a non-negative integer. For example, V4 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the additional field indicates a repeating RV sequence or a cyclic shift of the RV sequence. For example, the RV sequence indicated by the additional field may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3} or {0,0,0,0}.In some embodiments, the DCI has an additional field to indicate the number of TCI states. Assume the size of the additional field is V5 bits, where V5 is a non-negative integer. For example, V5 may be 0, 1, or 2. In some embodiments, the number of TCI states indicated by the additional field may be any one of 1, 2, 3, or 4. In some embodiments, if the number of bits indicating the configuration from DMRS Table A is X and the number of bits indicating the configuration from DMRS Table B is Y (X is a positive integer and Y is a non-negative integer, for example, X may be 4, 5, or 6, and Y may be 0, 1, 2, 3, or 4), the number of bits indicating the configuration from DMRS Table A is equal to the number of bits indicating the configuration from DMRS Table B plus the size of the one or more additional fields. That is, Y+Z2+V1+V2+V3+V4+V5=X. In some embodiments, at least one of Z1, V1, V2, V3, V4, and V5 is equal to 0. In this way, dynamic reporting of any number of repetitions, repetition schemes, repetition sequences, number of TCI states, code / timeslot offset values ​​between repetitions in the time domain or RB offset values ​​between repetitions in the frequency domain can be supported without increasing the reporting overhead in the DCI.

[0104] In some embodiments, the multiple predefined DMRS tables include at least a first DMRS table (hereinafter also referred to as "DMRS Table G") and a second DMRS table (hereinafter also referred to as "DMRS Table H"). DMRS Table G may be different from DMRS Table H. In some embodiments, if only one TCI state is indicated in the DCI, DMRS Table G (i.e., the first DMRS table) may be selected, and if multiple TCI states are indicated in the DCI, DMRS Table H (i.e., the second DMRS table) may be selected.

[0105] In some embodiments, DMRS Table G may differ from DMRS Table H in at least one of the following: number of available DMRS ports, number of available frontload codes for DMRS, number of available DMRS CDM groups, number of available CWs, number of repetitions, repetition scheme (e.g., Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, and / or any combination thereof), repetition RV sequence, number of TCI states, code / timeslot offset between repetitions in the time domain, resource allocation for repetitions in the frequency domain, resource allocation for repetitions in the frequency domain, and resource block offset or resource block group offset between repetitions in the frequency domain.

[0106] In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table G may be 1, 2, 3, or 4. In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 2, the number of available DMRS ports in DMRS Table G may be 1, 2, 3, 4, 5, 6, 7, or 8. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 1, the number of available DMRS ports in DMRS Table G may be 1, 2, 3, 4, 5, or 6. In some embodiments, for DMRS Type 2, if the maximum number of OFDM symbols for the frontload DMRS or the maximum length of the DMRS is 2, the number of available DMRS ports in DMRS Table G may be 1, 2, 3, 4, 5, 6, 7, or 8. In some embodiments, the number of available DMRS ports in DMRS Table H may be 1, 2, 3, or 4. In some embodiments, the number of available DMRS ports in DMRS Table H may be 2, 3, or 4.

[0107] In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) with no data in DMRS Table G may be 1 or 2. In some embodiments, for DMRS Type 1, the number of available DMRS CDM group(s) with no data in DMRS Table H may be only 2. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) with no data in DMRS Table G may be 1, 2 or 3. In some embodiments, for DMRS Type 2, the number of available DMRS CDM group(s) with no data in DMRS Table H may be 2 or 3.

[0108] In some embodiments, for DMRS Type 1, if the maximum number of OFDM symbols for frontloaded DMRS or the maximum length of the DMRS is 2, then the number of available CWs in DMRS Table G may be 1 or 2. In some embodiments, for DMRS Type 2, the number of available CWs in DMRS Table G may be 1 or 2. In some embodiments, the number of available CWs in DMRS Table H may be only 1.

[0109] In some embodiments, if the maximum number of OFDM symbols for a frontload DMRS or the maximum length of a DMRS is 2, then the number of available frontload symbols for a DMRS in DMRS Table G may be 1 or 2, and the number of available frontload symbols for a DMRS in DMRS Table H may be only 1 (e.g., there may be no notification of the number of frontload symbols for a DMRS in DMRS Table H).

[0110] In some embodiments, the number of bits required to indicate a setting from DMRS Table G (e.g., the first setting described above) may be the same as the number of bits required to indicate a setting from DMRS Table H (e.g., the second setting described above).

[0111] In some embodiments, if repetition of the Physical Shared Channel is enabled by RRC signaling, MAC layer signaling, and / or DCI, the configuration from DMRS Tables G and / or H indicates at least one of the number of repetitions of the Physical Shared Channel, the repetition scheme, the RV sequence of the repetitions, the number of TCI states, the repetitions in different timeslots, the repetitions within a single timeslot, the code / timeslot offset between repetitions in the time domain, and / or the RB offset between repetitions in the frequency domain. For example, there may be several configurations in DMRS Tables G and / or H indicating the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS and the same number of DMRS CDM groups without data. These configurations in DMRS Tables G and / or H indicate different numbers of repetitions. For example, the number of repetitions indicated by the configurations from DMRS Tables G and / or H may be any one of 1, 2, 3, 4, 5, 6, 8, or 16.

[0112] In some embodiments, if repetition of the physical shared channel is enabled by RRC signaling, MAC layer signaling, and / or DCI, there may be several configurations in DMRS Tables G and / or H indicating the same number of DMRS ports, identical DMRS port indices, the same number of DMRS frontload codes, and the same number of DMRS CDM groups without data. These configurations in DMRS Tables G and / or H indicate different repetition schemes. For example, the repetition scheme indicated by the configuration from DMRS Table H may be Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, or Scheme 4. Also, for example, the repetition scheme indicated by the configuration from DMRS Table G may be Scheme 2b, Scheme 3, or Scheme 4.

[0113] In some embodiments, there are several configurations in DMRS Tables G and / or H that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Tables G and / or H indicate different code offset values ​​between repetitions. For example, the code offset value between repetitions indicated by the configurations in DMRS Tables G and / or H may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. For example, the code offset value between repetitions is used in Scheme 3. In some embodiments, the code offset value is used only in repetitions associated with different TCI states. In some embodiments, the code offset may be calculated from the last code of an repetition to the first code of a subsequent repetition. In some embodiments, the code offset may be calculated from the first code of an repetition to the first code of a subsequent repetition. In some embodiments, the code offset may be calculated from the last code of an repetition to the last code of a subsequent repetition.

[0114] In some embodiments, there are several configurations in DMRS Table G and / or H that indicate the same number of DMRS ports, the same DMRS port index, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Table G and / or H indicate different RB offset values ​​between repetitions and / or starting RB indexes for each repetition. In some embodiments, the RB offset values ​​between repetitions indicated by the configurations in DMRS Table G and / or H are non-negative integers. For example, the RB offset values ​​are greater than 0 and less than 276. For example, the RB offset values ​​between repetitions are used for Scheme 2a and / or Scheme 2b. In some embodiments, the RB offset may be calculated from the end of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the start of an iteration to the start of a subsequent iteration. In some embodiments, the RB offset may be calculated from the end of an iteration to the end of a subsequent iteration.

[0115] In some embodiments, there are several configurations in DMRS Tables G and / or H that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups that do not have data. These configurations in DMRS Tables G and / or H indicate different RV sequences for repetitions of the physical shared channel. In some embodiments, the configurations from DMRS Tables G and / or H indicate repeating RV sequences or cyclic shifts of RV sequences. For example, the RV sequences indicated by the configurations may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3}, or {0,0,0,0}.

[0116] In some embodiments, there are several configurations in DMRS Tables G and / or H that indicate the same number of DMRS ports, identical DMRS port indexes, the same number of frontload codes for DMRS, and the same number of DMRS CDM groups without data. These configurations in DMRS Tables G and / or H indicate different numbers of TCI states. In some embodiments, the number of TCI states indicated by the configurations in DMRS Tables E and / or F may be any one of 1, 2, 3, or 4.

[0117] In some embodiments, if only one TCI state is indicated in the DCI, the DCI may not have additional fields to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4. In some embodiments, if multiple TCI states are indicated in the DCI, there may be one or more additional fields in the DCI to indicate at least one of: the number of repetitions, the repetition scheme, the RV sequence for the repetitions, the number of TCI states, the code / timeslot offset value between repetitions in the time domain, the RB offset value between repetitions in the frequency domain, whether the repetitions are based on scheme 2a, whether the repetitions are based on scheme 2b, whether the repetitions are based on scheme 3, and whether the repetitions are based on scheme 4.

[0118] In some embodiments, the DCI may have an additional field to indicate the repetition scheme. The size of the additional field is assumed to be P1 bits, where P1 is a non-negative integer. For example, P1 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the repetition scheme indicated by the additional field may be any one of Scheme 1, Scheme 2a, Scheme 2b, Scheme 3, Scheme 4, or any combination thereof. In some embodiments, the DCI may have an additional field to indicate a code / timeslot offset value between repetitions in the time domain. The size of the additional field is assumed to be P2 bits, where P2 is a non-negative integer. For example, P2 may be 0, 1, 2, 3, 4, 5, or 6. In some embodiments, the code / timeslot offset value between repetitions may be any one of 0, 1, 2, 3, 4, 5, 6, or 7. In some embodiments, the DCI may have an additional field to indicate a RB offset value between repetitions in the frequency domain. The size of the additional field is assumed to be P3 bits, where P3 is a non-negative integer. For example, P3 may be 0, 1, 2, 3, 4, 5 or 6. In some embodiments, the DCI has an additional field to indicate the number of repetitions. Assume the size of the additional field is P4 bits, where P4 is a non-negative integer. For example, P4 may be 0, 1, 2, 3, 4, 5 or 6. In some embodiments, the number of repetitions indicated by the additional field may be any one of 1, 2, 3, 4, 5, 6, 7, 8 or 16. In some embodiments, the value of the additional field is associated with one predefined value of the RB offset configured by RRC and / or MAC signaling. For example, different values ​​of the additional field are associated with different predefined values ​​of the RB offset configured by RRC and / or MAC signaling. In some embodiments, the DCI has an additional field to indicate the repeating RV sequence. Assume the size of the additional field is P5 bits, where P5 is a non-negative integer. For example, P5 may be 0, 1, 2, 3, 4, 5 or 6.In some embodiments, the additional field indicates a repeating RV sequence or a cyclic shift of the RV sequence. For example, the RV sequence indicated by the additional field may be any one of {0,3}, {0,0}, {0,2}, {0,2,3,1}, {0,3,2,1}, {0,3,0,3}, or {0,0,0,0}. In some embodiments, the DCI has an additional field to indicate the number of TCI states. Assume the size of the additional field is P6 bits, where P6 is a non-negative integer. For example, P6 may be 0, 1, or 2. In some embodiments, the number of TCI states indicated by the additional field may be any one of 1, 2, 3, or 4. In some embodiments, if the number of bits indicating a setting from DMRS Table G is M and the number of bits indicating a setting from DMRS Table H is N (where M and N are both positive integers, e.g., M may be 4, 5, or 6 and N may be 1, 2, 3, or 4), then the number of bits indicating a setting from DMRS Table G is equal to the number of bits indicating a setting from DMRS Table H plus the size of one or more additional fields, i.e., N+P1+P2+P3+P4+P5+P6=M. In some embodiments, at least one of P1, P2, P3, P4, P5, and P6 is equal to 0.

[0119] In some embodiments, a list of allocation parameters of time domain resources may be configured to the terminal device 130. For example, the parameters include at least one of a time slot offset, a start code of PDSCH / PUSCH, and a code number of PDSCH / PUSCH. The allocation parameter list of time domain resources may be divided into two groups (e.g., group S1 and group S2). In some embodiments, if the allocation parameters of the time domain resources in group S1 are signaled to the terminal device 130, DMRS Table A may be used, and if the allocation parameters of the time domain resources in group S2 are signaled to the terminal device 130, DMRS Table B may be used. According to the above embodiment, DMRS Table A and DMRS Table B may be different.

[0120] In some embodiments, when the repetition of the physical channel is configured for URLLC by the higher layer parameters, the DCI may have one or more fields to indicate the number of repetitions of different schemes. For example, the DCI may have a field indicating the number of repetitions for scheme 3 (hereinafter also referred to as "field A"), a field indicating the number of repetitions for scheme 4 (hereinafter also referred to as "field B"), a field indicating the number of repetitions for scheme 2a (hereinafter also referred to as "field C"), and / or a field indicating the number of repetitions for scheme 2b (hereinafter also referred to as "field D"). In some embodiments, when the number of repetitions indicated by each of fields A, B, C, and / or D is 1, it means that the repetition of the physical shared channel is disabled. Also, when two different TCI states are indicated in the TCI, the two different TCI states are associated with two different DMRS groups. In some embodiments, at least two of fields A, B, C, and / or D may be co-coded. Table 1 is an example of such an embodiment. [Table 1] As shown in Table 1, there are two notifications (i.e., notifications #1 and #2) in Table 1, indicating that the number of repetitions is two. However, notification #1 indicates that two repetitions are based on scheme 3 (i.e., repetitions by sub-timeslots), while notification #2 indicates that two repetitions are based on scheme 4 (i.e., repetitions by time slots). There are three notifications (i.e., notifications #3 to #5) in Table 1, indicating that the number of repetitions is three. However, notification #3 indicates that all four repetitions are based on scheme 3, notification #4 indicates that all four repetitions are based on scheme 4, and notification #5 indicates that two of the four repetitions are based on scheme 3 and the other two are based on scheme 4. Here, it should be understood that Table 1 is merely for illustrative purposes. In some embodiments, a table including some settings different from Table 1 may be used to notify the terminal device of the number of repetitions. In some embodiments, there may be a notification that the repetitions are based on scheme 2a or 2b.

[0121] In some embodiments, there may be one or more fields to indicate the number of repeats and / or the repeat scheme in the DCI. In some embodiments, there may be a field indicating the number of repeats R1 for scheme 3. For example, R1 may be any one of 1, 2, 3, 4, 5, 6, 7, and 8. In some embodiments, there may be a field indicating the number of repeats R2 for scheme 4. For example, R2 may be any one of 1, 2, 3, 4, 8, and 16. In some embodiments, there may be a field indicating the number of repeats R3 for scheme 2a. For example, R3 may be any one of 1, 2, 4, 6, 8, and 16. In some embodiments, there may be a field indicating the number of repeats R4 for scheme 2b. For example, R4 may be any one of 1, 2, 4, 6, 8, or 16. In some embodiments, the total number of iterations may be any one of R1*R2, R1*R2*R3, R1*R2*R4, R1*R3, R1*R4, R2*R3, or R2*R4. In some embodiments, there is one field indicating whether scheme 3 and / or scheme 4 are applied. In some embodiments, there is a field indicating the total number of iterations Rt. For example, the total number of iterations is used for scheme 3, scheme 4, scheme 2a, and / or scheme 2b. Also, for example, the total number of iterations is used for scheme 3 and / or scheme 4. In some embodiments, there is a field indicating whether scheme 3 and / or scheme 4 are applied. For example, the field may require one or two bits for notification. In some embodiments, there is a field indicating whether scheme 2a and / or scheme 2b are applied. For example, the field may require one bit for notification. In some embodiments, when Scheme 2a and / or Scheme 2b are applied, the total number of repeats can be any one of R1*R2*2, R1*2, R2*2, or Rt*2. In some embodiments, when Scheme 2b is not applied, the total number of repeats can be any one of R1*R2, R1, R2, or Rt.In some embodiments, when Scheme 2a and / or Scheme 2b are applied, the total number of repeats may be any one of R1*R2, R1, R2, or Rt. For example, of the total number of repeats, the number of repeats based on Scheme 3 is R1 / 2. Also, for example, the number of repeats based on Scheme 4 is R2 / 2. Also, for example, the number of repeats based on Scheme 3 and Scheme 4 is R1*R2 / 2 or Rt / 2.

[0122] In some embodiments, there is a threshold timeDurationForQCL, which is set based on the terminal device's reported capabilities (see TS38.306). In some embodiments, if for a certain repetition transmission timing, the time offset between the reception of the last code of the DL DCI and the first or last code of the repetition is less than the threshold timeDurationForQCL, the terminal device may assume that for the QCL parameter(s) for the PDCCH quasi-co-location notification CORESET, the DMRS port of the repetition is quasi-co-located with the RS(s), and the PDCCH quasi-co-location notification CORESET is associated with the monitored search space with the smallest CORESET-ID in the latest timeslot of one or more CORESETs in the active BWP of the serving cell monitored by the terminal device. In some embodiments, if for a certain repeat transmission timing, the time offset between the reception of the last code of the DL DCI and the first or last code of the repeat is equal to or greater than the threshold timeDurationForQCL, the terminal device may assume that for the QCL type parameter(s) given by the signaled TCI state, the DMRS port of the repeat is quasi-co-located with the RS(s) of the TCI state. In some embodiments, the total number of repeats may be K, e.g., K is a positive integer, and K may be any one of 2, 4, 6, 8, 12, 14, or 16. If T repeats are performed, then for each of the T repeat transmission timings, the time offset between the reception of the last code of the DL DCI and the first or last code of the repeat may be equal to or greater than the threshold timeDurationForQCL. For KT repeats, for each of the KT repeat transmission timings, the time offset between the reception of the last code of the DL DCI and the first or last code of the repeat is less than the threshold timeDurationForQCL. For example, T is a non-negative integer and 0≦T≦K.In some embodiments, it is assumed that at least one TCI state is used for K repetitions of PDSCH / PUSCH transmission / reception, and for TK repetitions, the terminal device may assume that for the QCL parameter(s) for the PDCCH quasi-co-location notification CORESET, the DMRS port of the repetition is quasi-co-located with the RS(s), and the PDCCH quasi-co-location notification CORESET is associated with the monitored search space having the smallest CORESET-ID in the latest time slot of one or more CORESETs in the active BWP of the serving cell monitored by the terminal device. In some embodiments, if two TCI states (TCI A and TCI B) are used for the repetition, then for T repetitions, TCI A is used for ceiling or floor (T / 2) times, and TCI B is used for floor or ceiling (T / 2). In some embodiments, when three TCI states (TCI A, TCI B, and TCI C) are used in an iteration, for T iterations, TCI A is used T1 times, e.g., of which T1=ceiling (T / 3) or T1=floor (T / 3), TCI B is used T2 times, e.g., of which T2=ceiling (T / 3) or T2=floor (T / 3), and TCI C is used T-T1-T2 times. In some embodiments, when four TCI states (TCI A, TCI B, TCI C, and TCI D) are used in an iteration, for T iterations, TCI A is used T1 times, e.g., of which T1=ceiling (T / 4) or T1=floor (T / 4), TCI B is used T2 times, e.g., of which T2=ceiling (T / 4) or T2=floor (T / 4), TCI C is used T3 times, e.g., of which T3=ceiling (T / 4) or T3=floor (T / 4), and TCI D is used T-T1-T2-T3 times.

[0123] In some embodiments, the physical resource block (PRB) bundle size and / or precoding granularity are set to "bandwidth" and if the terminal 130 is configured with repetition and / or FDM repetition, the terminal 130 may not be scheduled with non-consecutive PRBs. Alternatively, the terminal 130 may be assumed to be scheduled with non-consecutive PRBs. In this case, the total assigned resources are divided into two groups and the terminal 130 may assume that the same predefined number is used for the assigned resources of each group.

[0124] In some embodiments, when the PRB bundle size and / or precoding granularity are set as a "bandwidth" and repetition and / or repetition with FDM are configured for the terminal 130, the terminal 130 may not be scheduled with more than two portions of non-consecutive PRBs. Alternatively, the terminal 130 may be expected to be scheduled with two portions of non-consecutive PRBs. Alternatively, when the PRB bundle size and / or precoding granularity are set as a "bandwidth" and repetition and / or repetition with FDM are configured for the terminal 130, the terminal 130 may schedule with multiple consecutive PRBs and / or with two groups of consecutive PRBs (two groups of PRBs, where the PRBs in each group are consecutive), where the two groups of PRBs may or may not be adjacent. In some embodiments, if terminal device 130 is scheduled with multiple consecutive PRBs and the PRBs are divided into two groups, terminal device 130 may assume that the same predefined number is used for the assigned resources of each group. In some embodiments, if terminal device 130 is scheduled with two groups of consecutive PRBs, terminal device 130 may assume that the same predefined number is used for each group PRB.

[0125] In some embodiments, when repetition and / or repetition by FDM is set for the terminal device 130, there are two groups of PRBs used for scheduling the terminal device 130, and each group of PRBs is associated with one TCI state. If the TCI states associated with the two groups of PRBs are different, any PRB from group A may not schedule the terminal device 130 by two groups of PRBs (for example, group A and group B) that are in the same physical resource block group (PRG) as the PRBs from group B.

[0126] Assume that in one time slot, the index for the start symbol of repetition is S and the symbol length of repetition is L. In some embodiments, for a typical cyclic prefix (CP), when the number of TCI states exceeds 1 and 14 - (S + L) < L, it can be assumed that repetition by scheme 3 is not set for the terminal device 130. In some embodiments, for an extended CP, when the number of TCI states exceeds 1 and 12 - (S + L) < L, it can be assumed that repetition by scheme 3 is not set for the terminal device 130.

[0127] FIG. 4 shows an exemplary method 400 according to some embodiments of the present disclosure. In some embodiments, for example, method 400 is executed in the terminal device 130 of FIG. 1. Here, it should be understood that method 400 may include additional blocks not shown and / or omit some of the blocks shown, and the scope of the present disclosure is not limited thereto.

[0128] In block 410, the terminal device 130 receives DCI from the network device 110 for scheduling communication via the physical shared channel.

[0129] In some embodiments, before receiving the DCI, the terminal device 130 receives an indication from the network device 110 that repetition of the physical shared channel has been enabled or disabled by one of RRC signaling, MAC layer signaling, or DCI.

[0130] In some embodiments, the physical shared channel may include one of a PUSCH or a PDSCH.

[0131] In block 420, the terminal device 130 selects a DMRS table from a number of predefined DMRS tables based on the indication that repetition of the physical shared channel has been enabled or disabled.

[0132] In some embodiments, any two of the multiple predefined DMRS tables may differ from each other in at least one of the number of available DMRS ports, the number of available frontload codes for DMRS, the number of available DMRS groups, and the number of available CWs.

[0133] In some embodiments, the multiple default DMRS tables may include at least a first DMRS table and a second DMRS table. When repetition of the physical shared channel is disabled, the terminal device 130 selects the first DMRS table as the DMRS table. When repetition of the physical shared channel is enabled, the terminal device 130 selects the second DMRS table as the DMRS table.

[0134] In some embodiments, the DCI indicates one or more TCI states for communication over the physical shared channel, and based on the indication and the number of TCI states, terminal device 130 selects a DMRS table from a number of predefined DMRS tables.

[0135] In some embodiments, the multiple default DMRS tables may include at least a third DMRS table, a fourth DMRS table, a fifth DMRS table, and a sixth DMRS table. If the one or more TCI states include a single TCI state and repetition of the physical shared channel is disabled, the terminal device 130 selects the third DMRS table as the DMRS table. If the one or more TCI states include multiple TCI states and repetition of the physical shared channel is disabled, the terminal device 130 selects the fourth DMRS table as the DMRS table. If the one or more TCI states include a single TCI state and repetition of the physical shared channel is enabled, the terminal device 130 selects the fifth DMRS table as the DMRS table. If the one or more TCI states include multiple TCI states and repetition of the physical shared channel is enabled, the terminal device 130 selects the sixth DMRS table as the DMRS table.

[0136] At block 430, terminal device 130 determines whether repetition of the physical shared channel is enabled or disabled.

[0137] If repetition of the physical shared channel is disabled, then in block 440, based on the DCI and the DMRS table, the terminal device 130 determines a first configuration for DMRS communication over the physical shared channel.

[0138] In some embodiments, the DMRS table may include multiple configurations for DMRS communication. When repetition of the physical shared channel is disabled, the terminal device 130 determines from the DCI a field indicating one of the multiple configurations and determines a first configuration from the multiple configurations indicated by the field.

[0139] In some embodiments, once the first configuration is determined, the terminal device 130 transmits the DMRS to the network device 110 over the physical shared channel based on the first configuration.

[0140] If repetition of the physical shared channel is enabled, then in block 450, based on the DCI and the DMRS table, the terminal device 130 determines the number of repetitions and a second configuration for DMRS communication with repetition of the physical shared channel.

[0141] In some embodiments, the DMRS table includes multiple configurations for DMRS communication. When repetition of the physical shared channel is enabled, the terminal device 130 determines from the DCI a first field for indicating a number of repetitions and a second field for indicating one of the multiple configurations, and determines the number of repetitions based on the first field and a second configuration indicated by the second field from the multiple configurations.

[0142] In some embodiments, the DMRS table includes multiple configurations for DMRS communication, the multiple configurations being associated with a number of distinct repetitions of the physical shared channel. When repetition of the physical shared channel is enabled, the terminal device 130 determines from the DCI a field indicating one of the multiple configurations, determines a second configuration indicated by the field from the multiple configurations, and determines the number of repetitions associated with the second configuration.

[0143] In some embodiments, once the number of repetitions and the second configuration are determined, the terminal device 130 transmits at least one DMRS to the network device through the repetition of the physical shared channel based on the second configuration.

[0144] 5 illustrates an example method 500 according to some embodiments of the present disclosure. In some embodiments, for example, the method 500 is performed in the network device 110 of FIG. It should be understood that the method 500 may include additional blocks not shown and / or omit some blocks shown, and the scope of the present disclosure is not limited in this respect.

[0145] At block 510, the network device 110 sends a notification to the terminal device 130 that the repetition of the physical shared channel has been enabled or disabled.

[0146] In some embodiments, network device 110 sends the notification to terminal device 130 by one of RRC signaling, MAC layer signaling, or DCI.

[0147] In some embodiments, the physical shared channel may include one of a PUSCH or a PDSCH.

[0148] At block 520, the network device 110 selects a DMRS table from a number of predefined DMRS tables based on the notification.

[0149] In some embodiments, any two of the multiple predefined DMRS tables may differ from each other in at least one of the number of available DMRS ports, the number of available frontload codes for DMRS, the number of available DMRS groups, and the number of available CWs.

[0150] In some embodiments, the multiple default DMRS tables may include at least a first DMRS table and a second DMRS table. When repetition of the physical shared channel is disabled, the network device 110 selects the first DMRS table as the DMRS table. When repetition of the physical shared channel is enabled, the network device 110 selects the second DMRS table as the DMRS table.

[0151] In some embodiments, the network device 110 determines one or more Transmission Control Indication (TCI) states for communication over the physical shared channel and selects a DMRS table from a number of predefined DMRS tables based on the number of indications and TCI states.

[0152] In some embodiments, the multiple default DMRS tables may include at least a third DMRS table, a fourth DMRS table, a fifth DMRS table, and a sixth DMRS table. If the one or more TCI states include a single TCI state and physical shared channel repetition is disabled, the network device 110 selects the third DMRS table as the DMRS table. If the one or more TCI states include multiple TCI states and physical shared channel repetition is disabled, the network device 110 selects the fourth DMRS table as the DMRS table. If the one or more TCI states include a single TCI state and physical shared channel repetition is enabled, the network device 110 selects the fifth DMRS table as the DMRS table. If the one or more TCI states include multiple TCI states and physical shared channel repetition is enabled, the network device 110 selects the sixth DMRS table as the DMRS table.

[0153] At block 530, the network device 110 generates a DCI for scheduling communication over the physical shared channel based on the DMRS table. When repetition of the physical shared channel is disabled, the generated DCI indicates a first configuration for DMRS communication over the physical shared channel. When repetition of the physical shared channel is enabled, the generated DCI indicates a number of repetitions and a second configuration for DMRS communication with repetition of the physical shared channel.

[0154] In some embodiments, the network device 110 may indicate one or more TCI states in the DCI.

[0155] In some embodiments, the DMRS table may include multiple configurations for DMRS communication, and the DCI may include a field indicating one of the multiple configurations. When physical shared channel repetition is disabled, the network device 110 determines a first configuration from the multiple configurations and indicates the first configuration in the field.

[0156] In some embodiments, the DMRS table includes multiple configurations for DMRS communication, and the DCI may include a first field for indicating a number of repetitions and a second field for indicating one of the multiple configurations. When repetition of the physical shared channel is enabled, the network device 110 determines a number of repetitions and indicates the number of repetitions in the first field, determines a second configuration from the multiple configurations and indicates the second configuration in the second field.

[0157] In some embodiments, the DMRS table includes multiple configurations for DMRS communication, the multiple configurations being associated with a number of distinct repetitions of the physical shared channel. The DCI may include a field indicating one of the multiple configurations. When repetition of the physical shared channel is enabled, the network device 110 determines the number of repetitions, determines a second configuration associated with the number of repetitions from the multiple configurations, and indicates the second configuration associated with the number of repetitions in the field.

[0158] At block 540 , the network device 110 transmits the DCI to the terminal device 130 .

[0159] In some embodiments, when repetition of the physical shared channel is disabled and a DCI is transmitted to the terminal device 130, the network device 110 transmits a DMRS to the terminal device over the physical shared channel based on the first configuration.

[0160] In some embodiments, when repetition of the physical shared channel is enabled and a DCI is transmitted to the terminal device 130, the network device 110 transmits at least one DMRS to the terminal device by repetition of the physical shared channel based on the second configuration.

[0161] 6 is a simplified block diagram of an apparatus 600 capable of implementing embodiments of the present disclosure. The apparatus 600 can be viewed as another exemplary embodiment of the network apparatus 110, the TRP 120, or the terminal apparatus 130 shown in FIG. 1. Thus, the apparatus 600 may be implemented in, or at least as part of, the network apparatus 110, the TRP 120, or the terminal apparatus 130.

[0162] As shown in the figure, the device 600 includes a processor 610, a memory 620 connected to the processor 610, a suitable transmitter (TX) and receiver (RX) 640 connected to the processor 610, and a communication interface connected to the TX / RX 640. The memory 620 stores at least a portion of a program 630. The TX / RX 640 is used for bidirectional communication. The TX / RX 640 has at least one antenna to support communication, but in practice, the access nodes referred to in this application may have multiple antennas. The communication interface refers to any interface for communicating with other network components, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / service gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or an Uu interface for communication between an eNB and a terminal device.

[0163] The program 630 is assumed to include program instructions that, when executed by an associated processor 610, cause the device 600 to perform operations in accordance with embodiments of the present disclosure, as described herein with reference to Figures 1-5. The embodiments of the present disclosure may be implemented by computer software, hardware, or a combination of software and hardware executable by the processor 610 of the device 600. The processor 610 is configured to implement various embodiments of the present disclosure. Additionally, the combination of the processor 610 and the memory 620 may form a processing means 650 configured to implement various embodiments of the present disclosure.

[0164] The memory 620 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, a non-transitory computer-readable storage medium, a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, a fixed memory, and a removable memory. Although only one memory 620 is shown in the device 600, the device 600 may have several physically separate memory modules. The processor 610 may be of any type suitable for a local technology network and may, by way of non-limiting example, include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor with a multi-core processor architecture. The device 600 may include multiple processors, such as, by way of non-limiting example, a dedicated integrated circuit chip time-slaved to a clock synchronous to a main processor.

[0165] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Although aspects of the embodiments of the present disclosure may be illustrated and described as block diagrams, flow charts, or other graphical representations, it is understood that, by way of non-limiting example, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller, or other computing device, or any combination thereof.

[0166] The present disclosure further provides at least one computer program product tangibly stored in a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, e.g., instructions included in program modules, which, when executed by a target real or virtual processor in the device, perform the process or method described with reference to Figures 4-5. Generally, program modules include routines, programs, bases, objects, categories, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split among the program modules as appropriate. The machine-executable instructions of the program modules may be executed in a local device or in a distributed device. In a distributed device, the program modules are stored in both local and remote storage media.

[0167] The program codes for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, a special purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, the program codes may implement the functions / operations specified in the flowcharts and / or block diagrams. The program codes may be entirely executed on the machine, partially executed on the machine, executed as a stand-alone package, partially executed on the machine and other parts executed on a remote machine, or entirely executed on a remote machine or server.

[0168] The above-mentioned program code is included in a machine-readable medium, which is any tangible medium that contains or stores a program for use by or in connection with a system, device, or device that executes instructions. The machine-readable medium is a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination thereof. More specific examples of machine-readable storage media include an electrical connection having one or more conductors, a portable computer magnetic disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable optical disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0169] Also, although operations have been described in a particular order, this should not be understood as requiring that such operations be performed in the particular order or sequential order set forth above, or that all of the operations set forth above be performed, in order to achieve desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the above description includes details of several specific embodiments, these should not be construed as limiting the scope of the disclosure, but rather as describing features specific to certain embodiments. Certain features described in the context of separate embodiments may be combined and implemented in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in separate embodiments, or in any suitable subcombination.

[0170] Although the present disclosure has been described in language specific to structural features and / or method operations, it should be understood that the present disclosure as defined in the appended claims is not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as example forms of implementing the claims.

Claims

1. A method performed by a terminal device, comprising: receiving configuration information from a network device indicating a list of time domain resource allocation parameters; receiving a notification indicating a time domain resource allocation parameter from the network device, the time domain resource allocation parameter list; determining whether the time domain resource allocation parameters indicate an allocation including a number of repetitions; receiving from the network device transmission timings of multiple PDSCHs of one PDSCH if the time domain resource allocation parameters indicate the allocation including the number of repetitions and one or two Transmission Control Indication (TCI) states are indicated in a Downlink Control Information (DCI) scheduling a Physical Downlink Shared Channel (PDSCH); or receiving transmission timings of a single PDSCH of the PDSCH if the time domain resource allocation parameters do not indicate the allocation including the number of repetitions and one or two TCI states are indicated in the DCI; The method includes:

2. the list of time domain resource allocation parameters includes a first group of time domain resource allocation parameters and a second group of time domain resource allocation parameters; each of the first group of time domain resource allocation parameters includes the number of repetitions; The method of claim 1 , wherein none of the second group of time domain resource allocation parameters includes the number of repetitions.

3. The step of receiving the transmission timings of the plurality of PDSCHs includes receiving the transmission timings of the plurality of PDSCHs when the time domain resource allocation parameter belongs to a first group of the time domain resource allocation parameters and the one or two TCI states are indicated in the DCI; 3. The method of claim 2, wherein receiving the transmission timing of the single PDSCH comprises receiving the transmission timing of the single PDSCH when the time domain resource allocation parameter belongs to a second group of time domain resource allocation parameters and the one or two TCI states are indicated in the DCI.

4. A method performed by a terminal device, comprising: receiving configuration information from a network device indicating a recurrence scheme; receiving downlink control information (DCI) from the network device for scheduling a physical downlink shared channel (PDSCH); the DCI indicating a first transmission control indication (TCI) state and a second TCI state; receiving from the network device a transmission timing of a first PDSCH and a transmission timing of a second PDSCH of the PDSCH if the repetition scheme is a time domain multiplexing (TDM) scheme; A method according to claim 1, wherein a first symbol of the transmission timing of the second PDSCH begins a first number of symbols after a last symbol of the transmission timing of the first PDSCH.

5. determining a second number of consecutive physical resource blocks (PRBs) scheduled for the PDSCH when the repetition scheme is a frequency division multiplexing (FDM) scheme, the second number of consecutive PRBs including a first group of PRBs associated with the first TCI state and a second group of PRBs associated with the second TCI state; receiving the PDSCH from the network device; 5. The method of claim 4, wherein a first precoding is applied to each of the first group of PRBs, a second precoding is applied to each of the second group of PRBs, and a granularity of precoding configured in the terminal device is configured as wideband.

6. 6. The method of claim 5, wherein receiving the PDSCH includes receiving a single PT-RS port for the PDSCH from the network device if the DCI indicates one Code Division Multiplexing (CDM) group of Demodulation Reference Signal (DMRS) ports.

7. 1. A method performed by a network device, comprising: transmitting configuration information indicating a list of time domain resource allocation parameters to a terminal device; transmitting a notification indicating a time domain resource allocation parameter from the list of time domain resource allocation parameters to the terminal device, the time domain resource allocation parameter being used by the terminal device to determine whether the time domain resource allocation parameter indicates an allocation including a number of repetitions; transmitting transmission timings of multiple PDSCHs of a physical downlink shared channel (PDSCH) to the terminal device when the time domain resource allocation parameter indicates the allocation including the number of repetitions and one or two communication control indicator (TCI) states are indicated in downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH); or transmitting transmission timings of a single PDSCH of the PDSCH to the terminal device when the time domain resource allocation parameter does not indicate the allocation including the number of repetitions and the one or two TCI states are indicated in the DCI; The method includes:

8. the list of time domain resource allocation parameters includes a first group of time domain resource allocation parameters and a second group of time domain resource allocation parameters; each of the first group of time domain resource allocation parameters includes the number of repetitions; The method of claim 7 , wherein none of the second group of time domain resource allocation parameters includes the number of repetitions.

9. The step of transmitting the transmission timings of the plurality of PDSCHs includes a step of transmitting the transmission timings of the plurality of PDSCHs when the time domain resource allocation parameter belongs to a first group of the time domain resource allocation parameters and the one or two TCI states are indicated in the DCI; 9. The method of claim 8, wherein transmitting the transmission timing of the single PDSCH comprises transmitting the transmission timing of the single PDSCH when the time domain resource allocation parameter belongs to a second group of time domain resource allocation parameters and the one or two TCI states are indicated in the DCI.

10. 1. A method performed by a network device, comprising: sending configuration information indicating a repetition scheme to a terminal device; transmitting downlink control information (DCI) to the terminal device for scheduling a physical downlink shared channel (PDSCH); the DCI indicating a first transmission control indication (TCI) state and a second transmission control indication (TCI) state; If the repetition scheme is a time domain multiplexing (TDM) scheme, transmitting a transmission timing of a first PDSCH and a transmission timing of a second PDSCH of the PDSCH to the terminal device; A method according to claim 1, wherein a first symbol of the transmission timing of the second PDSCH begins a first number of symbols after a last symbol of the transmission timing of the first PDSCH.

11. determining a second number of consecutive physical resource blocks (PRBs) scheduled for the PDSCH if the repetition scheme is a frequency division multiplexing (FDM) scheme, the second number of consecutive PRBs including a first group of PRBs associated with the first TCI state and a second group of PRBs associated with the second TCI state; and transmitting the PDSCH to the terminal device; The method according to claim 10, wherein a first precoding is applied to each of a first group of PRBs, a second precoding is applied to each of a second group of PRBs, and a granularity of the precoding configured in the terminal device is configured as a wideband.

12. 12. The method of claim 11, wherein transmitting the PDSCH comprises transmitting a single PT-RS port for PDSCH from the network device if the DCI indicates one Code Division Multiplexing (CDM) group of Demodulation Reference Signal (DMRS) ports.

13. means for receiving configuration information from a network device, the configuration information indicating a list of time domain resource allocation parameters; means for receiving, from the network device, a notification indicating a time domain resource allocation parameter from the list of time domain resource allocation parameters; means for determining whether the time domain resource allocation parameters indicate an allocation including a number of repetitions; means for receiving from the network device transmission timings of multiple PDSCHs of one PDSCH when the time domain resource allocation parameters indicate the allocation including the number of repetitions and one or two Transmission Control Indication (TCI) states are indicated in a Downlink Control Information (DCI) scheduling a Physical Downlink Shared Channel (PDSCH), or means for receiving transmission timings of a single PDSCH of a PDSCH when the time domain resource allocation parameters do not indicate the allocation including the number of repetitions and the one or two TCI states are indicated in the DCI; A terminal device including:

14. the list of time domain resource allocation parameters includes a first group of time domain resource allocation parameters and a second group of time domain resource allocation parameters; The first group of time domain resource allocation parameters includes a number of repetitions; The terminal device according to claim 13 , wherein the second group of time domain resource allocation parameters does not include a number of repetitions.

15. The means for receiving transmission timings of the plurality of PDSCHs includes means for receiving transmission timings of the plurality of PDSCHs when the time domain resource allocation parameters belong to a first group of the time domain resource allocation parameters and the one or two TCI states are indicated in the DCI; The terminal device according to claim 14, wherein the means for receiving the transmission timing of the single PDSCH includes means for receiving the transmission timing of the single PDSCH when the time domain resource allocation parameters belong to a second group of the time domain resource allocation parameters and the one or two TCI states are indicated in the DCI.

16. means for receiving configuration information from a network device that indicates a recurrence scheme; means for receiving downlink control information (DCI) from the network device for scheduling a physical downlink shared channel (PDSCH); the DCI indicating a first transmission control indication (TCI) state and a second TCI state; and means for receiving, from the network device, a transmission timing of a first PDSCH and a transmission timing of a second PDSCH of a PDSCH when the repetition scheme is a time domain multiplexing (TDM) scheme; A terminal device, wherein a first symbol of the transmission timing of the second PDSCH starts a first number of symbols after the last symbol of the transmission timing of the first PDSCH.

17. means for determining a second number of consecutive physical resource blocks (PRBs) scheduled for a PDSCH when the repetition scheme is a frequency division multiplexing (FDM) scheme, the second number of consecutive PRBs including a first group of PRBs associated with the first TCI state and a second group of PRBs associated with the second TCI state; and means for receiving the PDSCH from the network device; The terminal device according to claim 16, wherein a first precoding is applied to each of the first group of PRBs, a second precoding is applied to each of the second group of PRBs, and a granularity of the precoding set in the terminal device is set as a wideband.

18. The terminal device of claim 17, wherein the means for receiving the PDSCH includes means for receiving a single PT-RS port for the PDSCH from the network device when the DCI indicates one code division multiplexing (CDM) group of demodulation reference signal (DMRS) ports.

19. means for transmitting configuration information indicating a list of time domain resource allocation parameters to a terminal device; a means for transmitting a notification indicating a time domain resource allocation parameter from the list of time domain resource allocation parameters to the terminal device, the time domain resource allocation parameter being used by the terminal device to determine whether the time domain resource allocation parameter indicates an allocation including a number of repetitions; means for transmitting transmission timings of multiple PDSCHs of a physical downlink shared channel (PDSCH) to the terminal device when the time domain resource allocation parameter indicates the allocation including the number of repetitions and one or two communication control indicator (TCI) states are indicated in downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH); or means for transmitting transmission timing of a single PDSCH of a PDSCH when the time domain resource allocation parameter does not indicate the allocation including the number of repetitions and the one or two TCI states are indicated in the DCI. A network device comprising:

20. the list of time domain resource allocation parameters includes a first group of time domain resource allocation parameters and a second group of time domain resource allocation parameters; each of the first group of time domain resource allocation parameters includes the number of repetitions; 20. The network device of claim 19, wherein none of the second group of time domain resource allocation parameters includes the number of repetitions.

21. The means for transmitting transmission timings of the plurality of PDSCHs includes means for transmitting transmission timings of the plurality of PDSCHs when the time domain resource allocation parameters belong to a first group of the time domain resource allocation parameters and the one or two TCI states are indicated in the DCI; 21. The network device of claim 20, wherein the means for transmitting the transmission timing of the single PDSCH includes means for transmitting the transmission timing of the single PDSCH when the time domain resource allocation parameter belongs to a second group of time domain resource allocation parameters and the one or two TCI states are indicated in the DCI.

22. means for transmitting configuration information indicating a repetition scheme to a terminal device; means for transmitting downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) to the terminal device, the DCI indicating a first transmission control indication (TCI) state and a second TCI state; When the repetition scheme is a time domain multiplexing (TDM) scheme, a means for transmitting a transmission timing of a first PDSCH and a transmission timing of a second PDSCH of the PDSCH to the terminal device, A network device, wherein a first symbol of the transmission timing of the second PDSCH starts a first number of symbols after a last symbol of the transmission timing of the first PDSCH.

23. means for determining a second number of consecutive physical resource blocks (PRBs) scheduled for the PDSCH when the repetition scheme is a frequency division multiplexing (FDM) scheme, the second number of consecutive PRBs including a first group of PRBs associated with the first TCI state and a second group of PRBs associated with the second TCI state; and means for transmitting the PDSCH to the terminal device; a first precoding is applied to each of the first group of PRBs; a second precoding is applied to each of the second group of PRBs; The network device according to claim 22, wherein the granularity of precoding set in the terminal device is set as a wideband.

24. The means for transmitting the PDSCH includes:

24. The network device of claim 23, comprising: means for transmitting, from the network device, a single PT-RS port for the PDSCH if the DCI indicates one Code Division Multiplexing (CDM) group of Demodulation Reference Signal (DMRS) ports.

Images