Dynamic DMRS configuration for uplink transmissions

Abstract

Embodiments of the present application relate to apparatuses, methods, and computer readable storage media for dynamic demodulation reference signal (DMRS) configuration for uplink transmissions. An apparatus receives at least one higher layer parameter configuring a first DMRS configuration type and a second DMRS configuration type. The apparatus receives at least one of a first indication of at least one transmission parameter related to at least one uplink transmission, or a second indication indicating a first DMRS configuration type or a second DMRS configuration type to be applied to the at least one uplink transmission. The apparatus then determines at least one of the first or second DMRS configuration type based on at least one of the first indication or the second indication. The apparatus performs at least one uplink transmission by using the determined at least one of the first DMRS configuration type or the second DMRS configuration type.

Description

Technical Field

[0001] Various example embodiments of the present application relate generally to the field of telecommunications, and more particularly to methods, apparatus, and computer-readable storage media for dynamic demodulation reference signal (DMRS) configuration for uplink transmissions. Background Art

[0002] In a multiple transmit receive point (multi-TRP) deployment, the UE can have multiple transmit panels and can use different antenna panels to operate different links. In multi-TRP communications, the UE can be configured to use multiple links for transmission and reception, and these links can have independent properties or characteristics. However, there is currently no signaling framework that can support dynamic changes in uplink transmission parameters based on uplink transmission assumptions. Summary of the invention

[0003] In a first aspect of the present application, a first device is provided. The first device includes at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the device to at least perform: receiving at least one high-level parameter for configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; receiving at least one of the following: a first indication of at least one transmission parameter related to at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; determining at least one of the first DMRS or the second DMRS configuration type based on at least one of the first indication or the second indication; and performing the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0004] In a second aspect of the present application, a second device is provided. The second device includes: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, causes the device to at least perform: transmitting at least one high-level parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; determining at least one of a first DMRS configuration type or a second DMRS configuration type for at least one uplink transmission; transmitting at least one of the following: a first indication of at least one transmission parameter related to the at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; receiving the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0005] In a third aspect of the present application, a method is provided. The method includes: at a first device, receiving at least one high-level parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; receiving at least one of the following: a first indication of at least one transmission parameter related to at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; determining at least one of the first DMRS or the second DMRS configuration type based on at least one of the first indication or the second indication; and performing the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0006] In a fourth aspect of the present application, a method is provided. The method includes: at a second device, transmitting at least one high-level parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; determining at least one of the first DMRS configuration type or the second DMRS configuration type for at least one uplink transmission; transmitting at least one of the following: a first indication of at least one transmission parameter related to the at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; receiving the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0007] In a fifth aspect of the present application, a device is provided. The device includes: a device for receiving at least one high-level parameter for configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; a device for receiving at least one of the following: a first indication of at least one transmission parameter related to at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; a device for determining at least one of the first DMRS or the second DMRS configuration type based on at least one of the first indication or the second indication; and a device for performing the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0008] In a sixth aspect of the present application, a device is provided. The device includes: a device for transmitting at least one high-level parameter for configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; a device for determining at least one of a first DMRS configuration type or a second DMRS configuration type for at least one uplink transmission; a device for transmitting at least one of the following: a first indication of at least one transmission parameter related to the at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; a device for receiving the at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0009] In a seventh aspect of the present application, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and is used to cause an apparatus to at least execute the method according to the third aspect.

[0010] In an eighth aspect of the present application, a computer-readable medium is provided, wherein the computer-readable medium includes instructions stored thereon, and is used to cause an apparatus to at least execute the method according to the fourth aspect.

[0011] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1 illustrates an example communication environment in which example embodiments of the present application may be implemented;

[0014] Figure 2 An example structure of two DMRS configuration types according to some example embodiments of the present application is illustrated.

[0015] Figure 3 An example signaling diagram illustrating a communication process between two devices according to some example embodiments of the present application;

[0016] Figure 4 A flowchart illustrating a method according to some example embodiments of the present application is shown;

[0017] Figure 5A and 5B illustrates a flow chart of an example process for enabling dynamic indication of DMRS configuration type according to some example embodiments of the present application;

[0018] Figure 6 A flowchart illustrating a method according to some example embodiments of the present application is shown;

[0019] Figure 7 illustrates a simplified block diagram of an apparatus suitable for implementing an example embodiment of the present application; and

[0020] Figure 8 A block diagram of an example computer-readable medium according to some example embodiments of the present application is illustrated.

[0021] Throughout the drawings, the same or similar reference numerals represent the same or similar elements. DETAILED DESCRIPTION

[0022] The principle of the present application will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are only for illustrative purposes, are intended to help those skilled in the art understand and implement the present application content, and do not imply any limitation on the scope of the present application content. The embodiments described herein can be implemented in various ways except the ways described below.

[0023] 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 application belongs.

[0024] References to "one embodiment," "an embodiment," "an example embodiment," etc. in the present application indicate that the embodiment may include a particular feature, structure, or characteristic, but not every embodiment is required to include the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it should be considered that those skilled in the art are aware that the feature, structure, or characteristic can be affected in conjunction with other embodiments, whether or not explicitly described.

[0025] It should be understood that although the terms "first", "second", etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0026] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least any two or more elements, or at least all elements.

[0027] As used herein, unless explicitly stated, performing a step “in response to A” does not mean that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.

[0028] The terms used herein are used only for the purpose of describing specific embodiments and are not intended to limit the example embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "comprise", "comprising", "have", "having", "include", and / or "including" specify the presence of the features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0029] In this application, the term "circuitry" may refer to one or more or all of the following:

[0030] a) Hardware-only circuit implementation (such as implementation in analog and / or digital circuits only)

[0031] as well as

[0032] b) A combination of hardware circuitry and software, such as (if applicable):

[0033] i) a combination of analog and / or digital hardware circuits and software / firmware; and

[0034] ii) any part of a hardware processor and software (including a digital signal processor), software and one or more memories, which work together to enable a device such as a mobile phone to perform its various functions); and

[0035] c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software (eg, firmware) to operate, but the software may not be present when not required to operate.

[0036] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or its) accompanying software and / or firmware. For example, and where applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0037] The term "communication network" used herein refers to a network that complies with any appropriate communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-loT), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any appropriate intergenerational communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocol and / or any other currently known or future developed protocol. The embodiments of the present application can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can embody the content of the present application. This should not be regarded as limiting the scope of the present application to the aforementioned system.

[0038] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. Depending on the terminology and technology applied, a network device may refer to a transmit receive point (TRP), such as a base station (BS), an access point (AP), a NRNB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node such as a femto, a micro, a non-terrestrial network (NTN) or non-terrestrial network equipment such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite), an aircraft network device, etc. In some example embodiments, a radio access network (RAN) separation architecture includes a centralized unit (CU) and a distributed unit (DU) at an IAB donor node. An IAB node includes a mobile terminal (IAB-MT) portion, which behaves similarly to a UE for a parent node, and a DU portion of the IAB node behaves similarly to a base station for a next-hop IAB node.

[0039] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), user station (SS), portable user station, mobile station (MS), mobile device, user equipment or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) part of an IAB node (eg, a relay node). In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0040] As used herein, the term "resource", "transmission resource", "resource block", "physical resource block" (PRB), "uplink resource" or "downlink resource" may refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as a resource in the time domain, a resource in the frequency domain, a resource in the space domain, a resource in the code domain, or any other resource capable of communication. Hereinafter, unless explicitly stated, some embodiments of the present application will be described with examples of using resources in both the frequency domain and the time domain as transmission resources. It is noteworthy that the exemplary embodiments of the present application are also applicable to other resources in other domains.

[0041] For multi-downlink control information (multi-DCI) multi-TRP (also known as multi-TRP, multi-TRP or mTRP) operation, it may be necessary to support multiple timing advance (TA) operations for each serving cell / timing advance group (TAG). For example, multiple TA values ​​may be used in multi-DCI multi-TRP (also known as multi-TRP based on multi-DCI) operation. The timing advance value indicates the amount of advance required for uplink transmission relative to the downlink reference timing so that different transmissions from different user equipments (UEs) arrive within a time window such as a cyclic prefix in an orthogonal frequency division multiplexing (OFDM) symbol. In previous versions, the TA value may be configured to be different for different cells (e.g., different TA values ​​are used for different TAGs). In multi-TRP operation, uplink timing may be required for each TRP (e.g., each uplink transmit link). For multi-DCI based multi-TRP operation with two TAs, it may be possible to support configuring two TAGs belonging to the serving cell (and / or two TA values ​​maintained for the serving cell, or two TA values ​​maintained for the serving cell and a cell having a different PCI from the serving cell).

[0042] In a multi-TRP deployment, as an example, a UE may have multiple transmit panels and may operate different links using different antenna panels (e.g., this may enable simultaneous multi-panel / multi-beam transmissions). Alternatively, the UE may operate using one antenna panel but may use different beams per panel for different uplinks. The UE may have separate links to different TRPs that have different path losses (e.g., due to distance).

[0043] A unified Transmission Configuration Indicator (TCI) framework was introduced in Release 17 (Rel-17). In the unified TCI framework, the quasi-co-location (QCL) assumption that TCI has provided so far for the reception of downlink (DL) signals and channels will also be used to provide spatial sources for the transmission of uplink (UL) signals and channels. In addition, the unified TCI framework defines the concept of an indicated TCI state. An indicated TCI state can be a joint DL and UL TCI state or a separate DL and separate UL TCI state. An indicated TCI state provides a QCL source (DL) and a spatial source (UL) for a set of downlink signals and channels and a set of uplink signals and channels, respectively. In Rel-17, for a UE, there can be one indicated joint DL and UL TCI state or one indicated DL TCI state and one indicated UL TCI state.

[0044] In the unified TCI framework, one or more TCI state IDs may be configured / indicated for a group of signals and channels at a time, and the TCI state may be a joint DL / UL TCI state, a separate DL TCI state, or a separate UL TCI state. The indicated TCI state may include a TCI state ID, which is indicated to be used as a joint DL / UL, DL and / or UL TCI state. One or more TCI state IDs may be configured / indicated as one or more indicated TCI states (e.g., a first indication or a second indication TCI state). A group (or pool or list) of joint and / or separate TCI states may be configured via radio resource control (RRC) signaling. Multiple (e.g., 8) joint and / or separate TCI states may be activated via media access control (MAC) signaling (such as a MAC control element (CE)).

[0045] One of the activated TCI states (TCI state ID list) may be indicated via the DCI to be applied. Such a TCI state may also be referred to as an indicated TCI state (i.e., the TCI state ID is regarded as an indicated TCI state ID). Different from indicating which TCI state is to be applied via DCI, if there is only one activated TCI state, the TCI state activated by the MAC CE may be regarded as the TCI state currently to be applied, or the currently indicated TCI state.

[0046] DCI formats 1_1 / 1_2 with or without DL allocation can be used to carry TCI status indication. The indication can be confirmed by a hybrid automatic repeat request (HARQ) confirmation (ACK) from the UE. The application time of the TCI status indication can be the first time slot of at least X ms or Y symbols after the last codeword of the joint or individual DL / UL TCI status indication confirmation. The TCI field code point can indicate the joint TCI state of both DL and UL, a pair of DL TCI state and UL TCI state, or DL ​​TCI state (maintain the current UL TCI state) or UL TCI state (maintain the current DL TCI state).

[0047] Two different DMRS configuration types can be supported in the New Radio (NR), referred to as Type 1 (Type-1) and Type 2 (or Type-2). Configuration Type 1 has a so-called comb-2 structure, which means that within a configured physical resource block (PRB), each second resource element (RE) is allocated to an antenna port associated with the corresponding resource. Therefore, the antenna ports can be multiplexed in the frequency domain, where antenna ports sharing the same resource elements are distinguished using orthogonal cover codes (OCCs), thereby achieving code division multiplexing (CDM). Type-1 provides support for 4 antenna ports per symbol and provides support for up to 8 antenna panels (APs) using double preamble symbols. Type-1 DMRS can be configured in the presence of poor / limited coverage conditions.

[0048] In a Type 2 configuration, every 3rd pair of subcarriers is assigned to an antenna port associated with the corresponding resource element within the configured PRB. Type 2 provides support for 6 antenna ports per symbol and supports up to 12 APs using double preamble symbols. Type 2 can be used for less challenging channel conditions (achieving higher multiplexing capacity) than Type 1.

[0049] In Release 17, multi-TRP operation is defined only for the downlink. Multi-TRP operation needs to be extended to the uplink. In multi-TRP communication, the UE can be configured to use multiple links for transmission and reception and the links can have independent properties or characteristics. One of these properties is the distance (which directly affects the propagation time of the signal) and the channel condition of the specific link. For example, in a typical system operating with multi-beam, the link can be considered as power limited rather than interference limited. Therefore, in the power limited case, the distance / path loss of the link may affect the required uplink transmission characteristics.

[0050] The propagation time of the signal can be taken into account by introducing multiple TA values. For example, different links may have different propagation delays (due to distance) and may operate using different TA values. The TA value may be dynamically updated by the network. However, another issue related to multiple TRPs is channel estimation based on the demodulation reference signal (DMRS). Depending on the TRP used by the link, different links may require different DMRS configuration types. In addition, a link to a TRP may be switched to another TRP, which may have different transmission assumptions for uplink transmissions (e.g., different path losses). Transmission switching may mean that the UE receives an indication of a new TCI state ID configured / indicated as the indicated TCI state, so the DMRS configuration type will benefit from dynamic switching capabilities (especially in multiple TRP deployments).

[0051] The current signaling framework cannot support dynamic changes of uplink transmission parameters based on uplink transmission assumptions. One of the key issues involves the uplink DMRS used for uplink channel estimation. The DMRS configuration in NR fifth generation (5G) supports 2 different values ​​(type 1 and type 2) and is applicable to different channel conditions, where type 1 is considered to be more robust than type 2 due to RE density. In turn, type 1 configuration limits the multiplexing capability of different UEs due to RS density. Therefore, the preferred or optimal configuration will depend on the UL transmission characteristics of the link, and therefore the static value (or RRC configuration value) may limit the scheduling flexibility of the network, it may reduce resource utilization efficiency, and may cause unnecessary delays in uplink beam changes when RRC level reconfiguration is required before the beam is changed.

[0052] Another example of such a parameter that can be changed dynamically is the mapping of DMRS to a specific symbol in a time slot. For example, a downlink message (e.g., DCI or MAC CE) may indicate a DMRS symbol mapping type (e.g., mapping type A or B, or dmrs-UplinkForPUSCH-MappingTypeA or dmrs-UplinkForPUSCH-MappingTypeB') to a PUSCH resource at each transmission (e.g., in the DCI) or in a semi-static manner (in a MAC CE of a specific TCI state or an indicated TCI state). In one example, the DMRS configuration type and the DMRS for the PUSCH mapping type may be dynamically indicated / changed. For example, dmrs-UplinkForPUSCH-MappingTypeA / B may refer to the DMRS symbol position in a time slot.

[0053] The example embodiments of the present application propose an enhanced scheme to support dynamic changes in uplink transmission parameters in multi-TRP deployments. The scheme allows a device (e.g., UE) to determine one or more DMRS configuration types (such as type 1 and / or type 2) for one or more uplink transmissions based on dynamic indications from the network. In some examples, the scheme allows the device to determine one or more DMRS configuration types for downlink reception. The DMRS configuration type is determined from a plurality of DMRS configuration types that can be configured via RRC signaling. The dynamic indication includes a first indication of at least one transmission parameter related to the uplink transmission, and / or a second indication indicating a DMRS configuration type (type 1 or type 2) to be applied to the uplink transmission.

[0054] In this way, the DMRS configuration type used can be dynamically indicated and determined. Different numbers of resource elements can be used to implement the first DMRS configuration type and the second DMRS configuration type for efficient UL operation. Thus, the flexibility of scheduling can be increased while achieving more efficient transmission resource utilization. In some embodiments, the DMRS configuration type may also be referred to as a configuration type.

[0055] In some example embodiments, a similar approach may be applied to downlink DMRS (for downlink transmission reception by a UE). The network (e.g., TRP / gNB) may indicate in a downlink message that a particular DMRS configuration or configuration type may be used for demodulation purposes of a scheduled physical downlink shared channel (PDSCH). For example, the indication may be provided in a DCI message that schedules a PDSCH transmission.

[0056] Figure 1 An example communication environment 100 in which an example embodiment of the present application can be implemented is illustrated. In the communication environment 100, a plurality of communication devices, including four apparatuses 110, 120, 130, 135, can communicate with each other. In some embodiments, the apparatuses 110, 120, 130, and 135 will be referred to as a first apparatus 110, a second apparatus 120, a third apparatus 130, and a fourth apparatus 140, respectively. In this example, the first apparatus 110 (which may be a terminal device) may simultaneously communicate with two or more of the second apparatus 120, the third apparatus 130, and the fourth apparatus 135, wherein the second apparatus 120, the third apparatus 130, and the fourth apparatus 135 may be network devices, such as TRPs or gNBs.

[0057] It should be understood that Figure 1 The number of devices and their connections shown in the figure are for illustration purposes only and do not represent any limitation. The communication environment 100 may include any suitable number of devices configured to implement the example embodiments of the present application.

[0058] In the following, for the purpose of illustration, some example embodiments are described with the first device 110 as a terminal device, the second device 120 and the third device 130 as network devices (e.g., TRP). However, in some example embodiments, the operations described with respect to the terminal device may be implemented at the network device or other devices, and the operations described with respect to the network device may be implemented at the terminal device or other devices.

[0059] In some example embodiments, if first device 110 is a terminal device and second device 120, 130, or 140 is a network device, a link from second device 120 or third device 130 to first device 110 is referred to as a downlink (DL), and a link from first device 110 to second device 120 or third device 130 is referred to as an uplink (UL). If first device 110, second device 120, and third device 130 are all terminal devices, a link between these devices is referred to as a side link (SL).

[0060] The communication in the communication environment 100 may be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), sixth generation (6G), etc., wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc., and / or any other currently known or future developed protocol. In addition, the communication may utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other currently known or future developed technology.

[0061] Some example embodiments may be implemented in an example scenario of multi-TRP operation based on multi-DCI. For example, a first device 110 (e.g., UE) may perform simultaneous transmission to two or more (e.g., TRPs) of a second device 120, a third device 130, and a fourth device 135 via multiple channels (e.g., via a physical uplink shared channel (PUSCH) or a physical downlink shared channel (PDSCH) 140, 145, and / or 150).

[0062] The first device 110 may be equipped with multiple APs 152, 154, and 156, and use the corresponding AP 152, 154, or 156 to communicate with the second device 120, 130, or 135. It should be understood that different APs are shown for different links for the purpose of illustration only, and no limitation is implied. Alternatively or additionally, the first device 110 may use different antenna ports or beams in one AP for different links.

[0063] In some example embodiments, for multiple TRP communications, if the first device 110 is configured with more than one control resource set (CORESET) pool index (also referred to as CORESETpoolindex) value and / or configured with multiple TA operations, the first device 110 may be configured with multiple DMRS configuration types, for example including a first DMRS configuration type and a second DMRS configuration type. Different DMRS types have different densities, such as different numbers of resources. In some examples, the methods / schemes herein may be used for multiple TRPs based on S-DCI (single DCI) or any transmission scheme that requires dynamic DMRS configuration type indication (e.g., also a single TRP).

[0064] Figure 2 An example structure of two DMRS configuration types according to some example embodiments of the present application is illustrated.

[0065] The first DMRS configuration type 205 may be configuration type 1, where every second RE 210 of the REs within the configured PRB 215 is allocated to an antenna port associated with the corresponding resource. The second DMRS configuration type 220 may be configuration type 2, where every third pair of subcarriers 225 is allocated to an antenna port associated with the corresponding RE within the configured PRB 230. Thus, the first DMRS configuration type may be more robust due to RE density compared to the second DMRS configuration type.

[0066] Different links may require different DMRS configuration types depending on distance or mobility. Figure 1 As shown, due to mobility, the link 145 to the device 130 may be switched to the device 135 which may have a different transmission assumption (e.g., a different path loss). In various embodiments of the present application, one or more DMRS configuration types used by the first device 110 may be dynamically indicated or associated via a transmission parameter for a particular uplink transmission.

[0067] Figure 3 An example signaling diagram of a communication process 300 between a first device 110 and a second device 120 according to some example embodiments of the present application is illustrated.

[0068] like Figure 3 As shown, the first device 110 (which may be a UE) may receive (305) higher layer parameters including a DMRS configuration type from the second device 120 (which may be a network node).

[0069] The first device 110 may also receive (310) one or more dynamic indications related to one or more DMRS configuration types from the second device 120. The dynamic indication may include a first indication of at least one transmission parameter, which may include an indication of a TCI state identifier (ID) via a MAC CE. Alternatively or additionally, the dynamic indication may include a second indication indicating whether the first DMRS configuration type or the second DMRS configuration type or other DMRS configuration type in the DMRS configuration type to be configured is to be applied. The second indication may be transmitted via a UL grant in the DCI.

[0070] The first device 110 may determine (315) the DMRS configuration type from the configured DMRS configuration types based on at least one of the first indication or the second indication, for example, based on an association of the DMRS configuration type with the TCI state ID or based on an UL grant (e.g., a DCI indication). As an example, the DMRS configuration type used in the multiple configuration types for scheduled uplink transmission may be based on an indication in the DCI for scheduling PUSCH transmission, i.e., whether the DMRS of the scheduled PUSCH applies the first configuration type or the second configuration type.

[0071] Alternatively or additionally, the indicated TCI ID and / or the TCI state ID configured as the indicated TCI state may be used to determine a DMRS configuration type for a scheduled PUSCH transmission. The apparatus (320) may then apply the determined DMRS configuration to the PUSCH transmission and then perform (325) the PUSCH transmission. This may be applied to PDSCH reception in a symmetric manner.

[0072] The "indicated TCI state" here can be regarded as a container / variable that takes different TCI state ID values. For example, the first indicated TCI state (e.g., index #0) can carry {TCI state ID x}, and the second indicated TCI state (e.g., index #1) can carry {TCI state ID y}. If a specific DMRS configuration type is associated with the first indicated TCI state, any TCI state ID x configured as the first indicated TCI state is associated with the specific DMRS configuration type, regardless of the TCI state IDs x and y. The use of the second indicated TCI state is the same. The specific DMRS configuration type can be determined by the parameters (e.g., TCI state ID) configured for the first indication or second indication TCI state container / variable. If a specific DMRS configuration type is associated with TCI state ID x or y, it means that the DMRS configuration type is determined based on the value associated with ID x or y, rather than based on the "container / variable" described above.

[0073] It should be understood that Figure 3The operations or actions shown are exemplary only and are not restrictive. An operation or action may be split into multiple operations or actions, and some operations or actions may also be integrated into one step. In addition, other operations or actions may also exist.

[0074] Figure 4 A flowchart of an example method 400 implemented at the first device 110 according to some example embodiments of the present application is illustrated.

[0075] At block 410, the first device 110 receives at least one higher layer parameter that configures the first DMRS configuration type and the second DMRS configuration type. The higher layer parameter may also configure other DMRS configuration types depending on the network configuration.

[0076] For example, the first device 110 (eg, UE) may be configured with one or more (or more than one) PUSCH configurations. These PUSCH configurations may be dedicated to the uplink bandwidth portion. Each PUSCH configuration may include a configuration of a DMRS configuration type.

[0077] In the case where multiple PUSCH configurations are configured for the first device 110, the additional configuration (e.g., second or #2) can be an incremental configuration of the first PUSCH configuration or the default #1 configuration. The incremental configuration can signal only the different parameters between the first configuration (basic configuration) and the second configuration (incremental configuration). For example, if the configurations have many similar parameters, only those parameters that are different are signaled. The additional configuration can include a second value of the DMRS configuration type associated with a specific DMRS codeword mapping type to a PUSCH resource (e.g., mapping type A or B).

[0078] Alternatively or additionally, the PUSCH configuration may have an additional or second configuration for DMRS mapping type to PUSCH transmit symbols, such as parameters dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeA_additional.

[0079] As another example, the first device 110 may receive a PUSCH configuration that indicates or configures multiple (candidate) values ​​of a DMRS configuration type for a specific DMRS symbol mapping for a PUSCH transmission symbol for the first device 110. In some example embodiments, the configuration of the DMRS configuration type may be a DMRS configuration type (1+2), which indicates that for a PUSCH transmission with a specific type of DMRS mapped to a PUSCH transmission symbol, the DMRS configuration type has 2 candidate values. Two candidate values ​​are given as an example. In one example, the DMRS configuration type x may indicate that multiple value indications may be used as a DMRS configuration type (e.g., up to N values).

[0080] At block 420, the first device 110 receives at least one of a first indication of at least one transmission parameter related to at least one uplink transmission or a second indication indicating a first DMRS configuration type or a second DMRS configuration type to be applied to the at least one uplink transmission.

[0081] In some example embodiments, at least one transmission parameter may be pre-associated with one or more DMRS configuration types. In some example embodiments, the first device 110 may receive a configuration of an association of the first and / or second DMRS configuration types with at least one transmission parameter. The association may be configured via RRC signaling or MAC CE (or DCI). The first indication related to the transmission parameter may be received via one of RRC signaling, MAC CE, or DCI.

[0082] For example, the first device 110 may receive an association configured by RRC and receive an indication of association parameters via MAC CE or DCI. Alternatively or additionally, the first device 110 may receive a configuration related to the association via MAC CE and may receive an indication of association parameters via DCI.

[0083] The associated parameters may include a TCI state ID, an indicated TCI state (e.g., index #0 or #1), a reference signal (RS) or list or RS, a scheduling offset, a timing advance (TA), a CORESET pool index value or a CORESET group index value, a DMRS mapping type, a physical cell identifier (PCI), etc. Based on the association of the configured specific DMRS configuration type with the indicated parameters, the specific DMRS configuration type to be used may be determined.

[0084] The second indication of which DMRS configuration type is to be applied may be received via DCI. The DCI may schedule whether the first configuration type or the second configuration type is applied to the DMRS of the scheduled PUSCH.

[0085] Alternatively, a DCI that does not schedule any UL transmission (e.g., no data grant) may be used to trigger the used DMRS configuration type value for the associated PUSCH transmission, e.g., based on a CORESETpoolindex / CORESET group index value / ID (e.g., CORESETgroupindex). For example, how the DMRS configuration type is applied may depend on CORESETpoolindex / CORESETgroupindex. Any UL transmission scheduled by a CORESET using a particular pool index may use the indicated DMRS type.

[0086] Alternatively, such DCI may trigger a DMRS configuration type value based on the indicated TCI state used to schedule the DCI. As an example, if the DCI that schedules a PUSCH transmission uses the indicated TCI state, a specific value associated with the indicated TCI state (or TCI state ID) is used for the scheduled uplink transmission (first or second indicated TCI state). Alternatively or additionally, such an indication may be used to trigger a DMRS association semi-persistently. Any UL transmissions made after the DCI indication may follow the indicated type.

[0087] At block 430, the first device 110 determines at least one of the first DMRS configuration type or the second DMRS configuration type based on at least one of the first indication or the second indication. Use of the first indication and the second indication may be based on predefined or configured rules.

[0088] The DMRS configuration type applied or used may depend on the indicated TCI state. In some example embodiments, the first DMRS configuration type or the second DMRS configuration type may be determined based on a configuration or associated type with an indicated TCI state. The first DMRS configuration type or the second DMRS configuration type may be applied to a TCI state ID configured as an indicated TCI state. For example, if there is a configuration or indication associated with a first indication or a second indication TCI state (or #0 and #1), the first device 110 may use the DMRS configuration type associated with the first indication and the second indication TCI state regardless of the actual TCI state ID.

[0089] In this case, the configuration type is associated with the indicated TCI state. The TCI state ID can change. For example, the TCI state ID configured for the indicated TCI state can change, but the DMRS configuration type comes from the TCI state ID associated with the indicated TCI state. Therefore, for the indicated TCI state, the DMRS configuration type can be 1 or 2 based on the dynamic indication. Since in multi-TRP (or mTRP) operation, the TRP can change in a fairly dynamic manner, dynamic operation can bring more benefits.

[0090] In some example embodiments, an association may be given in the TCI state ID configuration (rather than associating a DMRS configuration type with an indicated TCI state). Based on the association of the TCI state ID with the first DMRS configuration type, the first device 110 may determine the first DMRS configuration type upon receiving the first indication of the TCI state ID. For example, for a particular TCI state or multiple TCI states, depending on which TCI states are indicated as indicated (unified) TCI states, the first device 110 may apply the first DMRS configuration type or the second DMRS configuration type. In one example, the currently indicated TCI states may have the same DMRS configuration type or different DMRS configuration types.

[0091] Alternatively or additionally, the DMRS configuration type may be determined based on a scheduling offset for uplink transmissions. In some example embodiments, if a first DMRS configuration type (or a default DMRS type configuration) is configured to be associated with a scheduling offset less than a threshold offset (which may be configured or indicated based on a network implementation), the first device 110 may determine the first DMRS configuration type upon receiving a first indication of a scheduling offset less than the threshold offset. For example, if the scheduling offset for a PUSCH transmission is less than a configured threshold offset value (such as a K2 value defined in units of time slots), the first device 110 may apply a default DMRS configuration type. The default value may be a first DMRS configuration type value (rather than an additional DMRS configuration type value or the default value may be fixed in the specification or may be a first or second or Nth type value).

[0092] The DMRS configuration type (e.g., type 1 or type 2) applied for an uplink transmission may depend on a TA value associated with / applied to the transmission. In some example embodiments, if the first DMRS configuration type is configured to be associated with a TA having a value equal to or greater than a first threshold time value and less than a second threshold, the first device 110 may determine the first DMRS configuration type upon receiving a first indication of such a TA.

[0093] For example, when TA>=0 (TA=0 may mean that TA is not used, and the UE may be in the center of the cell or the cell may be small (TA>0)) but less than TA-threshold-for-DMRStype (TA threshold for DMRS type), the first configuration type (e.g., type 1) may be used (as type 2 with lower robustness but higher multiplexing capability). Otherwise, the second configuration type is used. In this example, the first threshold time value is 0 and the second threshold time value is TA-threshold-for-DMRStype. Other threshold time values ​​may be used depending on network implementation.

[0094] In some example embodiments, the dynamic indication of the DMRS configuration type may be configured separately for PUSCH DMRS mapping type A or B. In some example embodiments, the DMRS configuration type may be specific to the PCI value associated with the RS or source RS in the TCI state. The association with the PCI may be configured.

[0095] In some example embodiments, the first device 110 may receive a configuration of one or more lists of reference signals associated with the use of a particular DMRS type. For example, if two groups (or lists) of reference signals are associated with first and second configuration types, respectively, the associated first configuration type may be used for the first group (or list) of reference signals, and the associated second configuration type may be used for the second group (or list) of reference signals. If the reference signal used is not listed in the first or second list (or set), a default value for the configuration type may be used. The default value may be predefined.

[0096] The reference signal may be indicated by a reference signal of an indicated TCI state, or an SRS resource indicator associated with a PUSCH transmission, or a QCL source / spatial relationship of an indicated TCI state / SRS. The reference signals in the first and / or second lists may be compared with the indicated reference signals. If the RS associated with the PUSCH transmission matches the first or second list, the associated DMRS configuration type may be used for the PUSCH transmission.

[0097] In some example embodiments, if the first device 110 receives both a first indication of a transmission parameter and a second indication of a DMRS configuration type used, the first device 110 may choose to follow the second indication and select the first DMRS configuration type. For example, after configuring via RRC signaling or indicating the associated transmission parameters via a MAC CE or an earlier DCI, the network may change the scheduling of the DMRS configuration type and indicate the currently used DMRS configuration type via a subsequent DCI. This may further provide more flexibility.

[0098] At block 440, the first device 110 performs at least one uplink transmission using at least one of the determined first DMRS configuration type or the second DMRS configuration type. In some example embodiments, two simultaneous uplink transmissions may be performed based on at least one of the first DMRS configuration type and the second DMRS configuration type. Simultaneous UL transmissions may use multiple antenna panels or multiple beams per panel.

[0099] For example, the first device 110 may schedule two PUSCH transmission opportunities so as to simultaneously transmit PUSCH from two antenna panels in a spatial division multiplexing (SDM) manner. The first device 110 may determine a DMRS configuration type for a first PUSCH opportunity based on a (RRC) configuration, and determine a DMRS device 110 type for a second PUSCH opportunity from a dynamic indication included in a DCI that triggers or schedules the PUSCH transmission opportunity.

[0100] If a dynamic DMRS configuration type is configured for the first device 110, but no indication is provided by the DCI or MAC CE or no association is provided by the TCI state, the first device 110 may adopt a default value of the DMRS configuration type. In some example embodiments, the first device 110 may perform further uplink transmissions based on the default DMRS configuration type without at least one of the first indication or the second indication. The default value is a predefined value for the cell. Alternatively or additionally, the default value may depend on the PCI or be PCI specific.

[0101] The following will refer to Figure 5A and 5B An example dynamic indication procedure for DMRS configuration type is described.

[0102] Figure 5A An example process 500 for enabling dynamic indication using a MAC CE according to some example embodiments of the present application is illustrated.

[0103] In process 500, multiple PUSCH configurations or multiple dmrs-UplinkForPUSCH-MappingTypes are provided to the first device 110 through RRC and associated with a TCI state ID for each uplink transmission or an indicated (unified) TCI state.

[0104] like Figure 5AAs shown, at box 505, the first device 110 may receive one or more PUSCH configurations (e.g., #1 or #1 and #2) or receive one or more configurations for dmrs-UplinkForPUSCH-MappingType (A or B). At box 510, for the provided PUSCH configurations or dmrs-UplinkForPUSCH-MappingTypes, the first device 110 may determine multiple different values ​​for the DMRS configuration type. At box 515, the first device 110 may receive a MAC CE indicating or associating DMRS configuration type 1 or 2 with an indicated TCI state (e.g., a first joint or UL TCI state or a second joint or UL TCI state). At box 520, for scheduled PUSCH transmissions, the first device 110 may apply the associated DMRS configuration type value associated with the TCI state for the PUSCH transmission.

[0105] Figure 5B An example process 530 of using DCI to enable dynamic indication according to some example embodiments of the present application is illustrated.

[0106] In process 530, DCI signaling may indicate which DMRS configuration type to use for the scheduled PUSCH transmission.

[0107] like Figure 5B As shown, at box 535, the first device 110 may receive a PUSCH configuration (or multiple PUSCH configurations) with multiple values ​​for different DMRS configuration types. At box 540, for the provided PUSCH configuration, the first device 110 may determine candidate values ​​of multiple different DMRS configuration types for a particular type of DMRS mapping type. At box 545, the first device 110 may determine the DMRS configuration type value used for the current PUSCH transmission based on the indication value of the DMRS configuration type in the DCI for scheduling the PUSCH transmission. At box 550, for the scheduled PUSCH transmission, the first device 110 may apply the associated DMRS configuration type value indicated by one or more PUSCH configurations.

[0108] Figure 6 FIG. 6 is a flowchart of an example method 600 implemented at the second device 120, the third device 130, or the fourth device 135 according to some example embodiments of the present application. For the purpose of discussion, Figure 1 The method 600 is described from the perspective of the second device 120 in FIG.

[0109] At box 610, the second device 120 transmits at least one high-level parameter configuring a first DMRS configuration type and a second DMRS configuration type. At box 620, the second device 120 determines at least one of the first DMRS configuration type or the second DMRS configuration type for at least one uplink transmission. At box 630, the second device 120 transmits at least one of the following: a first indication indicating at least one transmission parameter related to at least one uplink transmission; a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to at least one uplink transmission. At box 640, the second device 120 receives at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0110] In some example embodiments, the second device 120 may transmit a configuration associating the first and / or second DMRS configuration type with at least one transmission parameter.

[0111] In some example embodiments, at least one transmission parameter may include at least one of: a transmission configuration indicator (TCI) state identifier (ID), an indicated TCI state, a reference signal, a scheduling offset, a timing advance, a control resource set (CORESET) pool index value or a CORESET group index value, a DMRS mapping type, or a physical cell identifier.

[0112] In some example embodiments, if at least one of the determined first DMRS configuration type or the second DMRS configuration type is configured or associated with an indicated TCI state, the indicated TCI state may be transmitted, and the first DMRS configuration type or the second DMRS configuration type may be applied to a TCI state ID configured as the indicated TCI state.

[0113] In some example embodiments, if the first DMRS configuration type is determined, a TCI state ID associated with the first DMRS configuration type may be transmitted.

[0114] In some example embodiments, if the first DMRS configuration type is determined, a first indication of a scheduling offset that is less than a threshold offset may be transmitted.

[0115] In some example embodiments, if the first DMRS configuration type is determined, a first indication of a timing advance equal to or greater than a first threshold time value and less than a second threshold may be transmitted.

[0116] In some example embodiments, the first indication may be transmitted via one of RRC signaling, MAC CE, or DCI, and / or the second indication may be transmitted via DCI or MAC CE.

[0117] In some example embodiments, the at least one uplink transmission may include two simultaneous uplink transmissions based on at least one of the first DMRS configuration type and the second DMRS configuration type.

[0118] In some example embodiments, the second apparatus 120 may receive another uplink transmission based on a default DMRS configuration type among the first DMRS configuration type and the second DMRS configuration type without at least one of the first indication or the second indication.

[0119] In some example embodiments, a device capable of performing method 400 (e.g., Figure 1 The first device 110 in the method 400 may include a device for performing the corresponding operation of the method 400. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or a software module. The device may be implemented as or included in Figure 1 The first device 110 in.

[0120] In some example embodiments, the apparatus includes: means for receiving at least one high-level parameter for configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; means for receiving at least one of a first indication of at least one transmission parameter related to at least one uplink transmission or a second indication indicating a first DMRS configuration type or a second DMRS configuration type to be applied to at least one uplink transmission; means for determining at least one of the first DMRS configuration type or the second DMRS configuration type based on at least one of the first indication or the second indication; and means for performing at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0121] In some example embodiments, the apparatus further comprises means for receiving a configuration associating the first and / or second DMRS configuration type with at least the at least one transmission parameter.

[0122] In some example embodiments, at least one transmission parameter includes at least one of: a transmission configuration indicator (TCI) state identifier (ID), an indicated TCI state, a reference signal, a scheduling offset, a timing advance device, a control resource set (CORESET) pool index value or a CORESET group index value, a DMRS mapping type, or a physical cell identifier.

[0123] In some example embodiments, the first DMRS configuration type or the second DMRS configuration type is determined based on a configuration or an associated type with an indicated TCI state, wherein the first DMRS configuration type or the second DMRS configuration type is applied to a TCI state ID configured as the indicated TCI state.

[0124] In some example embodiments, means for determining the first DMRS configuration type or the second DMRS configuration type includes means for determining the first DMRS configuration type based on an association between the TCI state ID and the first DMRS configuration type in response to receiving the TCI state ID.

[0125] In some example embodiments, means for determining a first DMRS configuration type or a second DMRS configuration type includes means for, in response to receiving a first indication of a scheduling offset, determining the first DMRS configuration type if the scheduling offset is less than a threshold offset.

[0126] In some example embodiments, an apparatus for determining a first DMRS configuration type or a second DMRS configuration type includes: an apparatus for determining the first DMRS configuration type in response to receiving a first indication of a timing advance, if the value of the timing advance is equal to or greater than a first threshold time value and less than a second threshold.

[0127] In some example embodiments, means for determining a first DMRS configuration type or a second DMRS configuration type includes means, in response to receiving a first indication and a second indication, determining the first DMRS configuration type based on the second indication.

[0128] In some example embodiments, the first indication is received via one of radio resource control (RRC) signaling, medium access control (MAC) control element (CE), downlink control information (DCI), and / or the second indication is received via DCI or MAC CE.

[0129] In some example embodiments, the at least one uplink transmission comprises two simultaneous uplink transmissions based on at least one of the first DMRS configuration type and the second DMRS configuration type.

[0130] In some example embodiments, the apparatus further comprises means for performing another uplink transmission based on the default DMRS configuration type without at least one of the first indication or the second indication.

[0131] In some example embodiments, the apparatus further comprises means for performing the method 400 or other operations in some example embodiments of the first device 110. In some example embodiments, the apparatus comprises at least one processor; and at least one memory for storing instructions that, when executed by the at least one processor, cause the apparatus to perform operations.

[0132] In some example embodiments, a device capable of performing method 600 (e.g., Figure 1The second device 120 in the method 600 may include a device for performing the corresponding operation of the method 600. The device may be implemented in any suitable form. For example, the device may be implemented in a circuit or a software module. The device may be implemented as or included in Figure 1 The second device 120 in.

[0133] In some example embodiments, the apparatus includes: means for transmitting at least one high-level parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; means for determining at least one of a first DMRS configuration type or a second DMRS configuration type for at least one uplink transmission; means for transmitting at least one of: a first indication of at least one transmission parameter associated with at least one uplink transmission, or a second indication indicating a first DMRS configuration type or a second DMRS configuration type to be applied to at least one uplink transmission; means for receiving at least one uplink transmission by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

[0134] In some example embodiments, the apparatus further comprises means for transmitting a configuration associating the first and / or second DMRS configuration type with at least the at least one transmission parameter.

[0135] In some example embodiments, at least one transmission parameter includes at least one of: a transmission configuration indicator (TCI) state identifier (ID), an indicated TCI state, a reference signal, a scheduling offset, a timing advance device, a control resource set (CORESET) pool index value or a CORESET group index value, a DMRS mapping type, or a physical cell identifier.

[0136] In some example embodiments, if at least one of the determined first DMRS configuration type or the second DMRS configuration type is configured or associated with an indicated TCI state, the indicated TCI state is transmitted, and wherein the first DMRS configuration type or the second DMRS configuration type is applied to a TCI state ID configured as the indicated TCI state.

[0137] In some example embodiments, if the first DMRS configuration type is determined, a TCI state ID associated with the first DMRS configuration type is transmitted.

[0138] In some example embodiments, if the first DMRS configuration type is determined, a first indication of a scheduling offset that is less than a threshold offset is transmitted.

[0139] In some example embodiments, if the first DMRS configuration type is determined, a first indication of a timing advance equal to or greater than a first threshold time value and less than a second threshold may be transmitted.

[0140] In some example embodiments, the first indication is transmitted via one of radio resource control (RRC) signaling, medium access control (MAC) control element (CE), downlink control information (DCI), and / or the second indication is transmitted via DCI or MAC CE.

[0141] In some example embodiments, the at least one uplink transmission comprises two simultaneous uplink transmissions based on at least one of the first DMRS configuration type and the second DMRS configuration type.

[0142] In some example embodiments, the apparatus further includes means for receiving another uplink transmission based on a default DMRS configuration type of the first DMRS configuration type and the second DMRS configuration type without at least one of the first indication or the second indication.

[0143] In some example embodiments, the apparatus further comprises means for performing the method 600 or other operations in some example embodiments of the second device 120. In some example embodiments, the apparatus comprises at least one processor; and at least one memory for storing instructions that, when executed by the at least one processor, cause the apparatus to perform operations.

[0144] Figure 7 700 is a simplified block diagram of an apparatus 700 suitable for implementing an example embodiment of the present application. The apparatus 700 may be provided to implement a communication device, for example, Figure 1 The first device 110 or the second device 120, the third device 130 or the fourth device 135 shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0145] The communication module 740 is used for two-way communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required to communicate with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.

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

[0147] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0148] The computer program 730 includes computer executable instructions executed by the associated processor 710. The instructions of the program 730 may include instructions for performing the operations / actions of some example embodiments of the present application. The program 730 may be stored in a memory, such as ROM 724. The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0149] The exemplary embodiment of the present invention can be implemented by means of program 730, so that the apparatus 700 can execute the following steps as described in reference to Figures 1 to 6 Any process of the present application discussed. The exemplary embodiments of the present application can also be implemented by hardware, or by a combination of software and hardware.

[0150] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the apparatus 700 (such as in the memory 720) or in other storage devices accessible to the apparatus 700. The apparatus 700 may load the program 730 from the computer-readable medium into the RAM 722 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. The term "non-transitory" as used herein refers to the limitation of the medium itself (i.e., tangible, not a signal) rather than the limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0151] Figure 8 An example of a computer readable medium 800 is illustrated, which may be in the form of a CD, DVD or other optical storage disk. The computer readable medium 800 has a program 730 stored thereon.

[0152] In general, various embodiments of the present application 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, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present application are shown and described in block diagrams, flow charts, or using some other graphical representations, it should be understood that the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0153] Some example embodiments of the present application also provide at least one computer program product tangibly stored on a computer-readable medium (such as a non-transitory computer-readable medium). The computer program product includes computer executable instructions such as those included in a program module that are executed in a device on a target physical or virtual processor to perform any method as described above. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or divided between program modules according to the needs of various embodiments. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0154] The program code for executing the method of the present application can be written in any combination of one or more programming languages. The program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that when the processor or controller executes the program code, the function / operation specified in the flow chart and / or block diagram is realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0155] In the context of this application, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0156] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses, or any suitable combination of the foregoing. More specific examples of computer readable storage media include an electrical connection with one or more wires, a portable computer floppy 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 compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0157] In addition, although the operations are depicted in a particular order, this should not be understood as requiring the operations to be performed in the particular order shown or in a continuous order, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be considered as limitations on the scope of the present application, but should be considered as descriptions of features that may be specific to a particular embodiment. Unless explicitly stated, certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, unless explicitly stated, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0158] Although the content of the present application has been described in language specific to structural features and / or method actions, it should be understood that the present application defined in the appended claims is not necessarily limited to the above-mentioned specific features or actions. Instead, the above-mentioned specific features and actions are disclosed as example forms of implementing the claims.

Claims

1. A device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving at least one higher layer parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; Receive at least one of the following: a first indication of at least one transmission parameter associated with at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; determining at least one of the first DMRS configuration type or the second DMRS configuration type based on at least one of the first indication or the second indication; as well as The at least one uplink transmission is performed by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

2. The device according to claim 1, wherein: The device is also caused to execute: A configuration of an association of at least one of the first DMRS configuration type or the second DMRS configuration type with at least the at least one transmission parameter is received.

3. The device according to claim 1 or 2, wherein: The at least one transmission parameter includes at least one of the following: Transmit Configuration Indicator (TCI) status identification (ID), Indicates the TCI status, Reference signal, Scheduling offset, Time ahead, Control resource set (CORESET) pool index value or CORESET group index value, DMRS mapping type, or Physical cell identifier.

4. The device as claimed in claim 3, wherein: At least one of the first DMRS configuration type or the second DMRS configuration type is determined based on a configuration or associated type with an indicated TCI state, and wherein the first DMRS configuration type or the second DMRS configuration type is applied to a TCI state ID configured as the indicated TCI state.

5. The device according to claim 3, wherein: In response to receiving the TCI state ID, a first DMRS configuration type is determined based on an association of the TCI state ID and the first DMRS configuration type.

6. The device according to claim 3, wherein: In response to receiving the first indication of the scheduling offset, if the scheduling offset is less than a threshold offset, determining the first DMRS configuration type.

7. The device of claim 3, wherein In response to receiving the first indication of the timing advance, if the value of the timing advance is equal to or greater than a first threshold time value and less than a second threshold, determining the first DMRS configuration type.

8. The device of claim 1, wherein: In response to receiving the first indication and the second indication, determining the first DMRS configuration type based on the second indication.

9. The device according to any one of claims 1 to 8, wherein: The first indication is received via one of radio resource control (RRC) signaling, medium access control (MAC) control element (CE), or downlink control information (DCI), and / or The second indication is received via DCI or MAC CE.

10. The device according to any one of claims 1 to 9, wherein: The at least one uplink transmission includes two simultaneous uplink transmissions based on at least one of the first DMRS configuration type and the second DMRS configuration type.

11. The device according to any one of claims 1 to 10, wherein: The device is also caused to execute: Another uplink transmission is performed based on a default DMRS configuration type without at least one of the first indication or the second indication.

12. An apparatus comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: transmitting at least one higher layer parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; determining at least one of the first DMRS configuration type or the second DMRS configuration type for at least one uplink transmission; Emit at least one of the following: a first indication of at least one transmission parameter associated with the at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; as well as The at least one uplink transmission is received by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

13. The device of claim 10, wherein: The device is further caused to execute: Transmitting a configuration that associates the first DMRS configuration type or the second DMRS configuration type with at least the at least one transmission parameter 14. The device according to claim 12 or 13, wherein: The at least one transmission parameter includes at least one of the following: Transmit Configuration Indicator (TCI) status identification (ID), Indicates the TCI status, Reference signal, Scheduling offset, Time ahead, Control resource set (CORESET) pool index value or CORESET group index value, DMRS mapping type, or Physical cell identifier.

15. A method comprising: receiving at least one higher layer parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; Receive at least one of the following: a first indication of at least one transmission parameter related to at least one uplink transmission, or a second indication indicating the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; determining at least one of the first DMRS configuration type or the second DMRS configuration type based on at least one of the first indication or the second indication; as well as The at least one uplink transmission is performed by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

16. The method of claim 15, further comprising: A configuration of an association of the first DMRS configuration type and / or the second DMRS configuration type with at least the at least one transmission parameter is received.

17. The method according to claim 15 or 16, wherein: The at least one transmission parameter includes at least one of the following: Transmit Configuration Indicator (TCI) status identification (ID), Indicates the TCI status, Reference signal, Scheduling offset, Time ahead, Control resource set (CORESET) pool index value or CORESET group index value, DMRS mapping type, or Physical cell identifier.

18. A method comprising: transmitting at least one higher layer parameter configuring a first demodulation reference signal (DMRS) configuration type and a second DMRS configuration type; determining at least one of the first DMRS configuration type or the second DMRS configuration type for at least one uplink transmission; Emit at least one of the following: a first indication of at least one transmission parameter associated with the at least one uplink transmission, or at least one of a second indication of the first DMRS configuration type or the second DMRS configuration type to be applied to the at least one uplink transmission; as well as The at least one uplink transmission is received by using at least one of the determined first DMRS configuration type or the second DMRS configuration type.

19. The method of claim 18, wherein: The device is further caused to execute: A configuration of an association of the first DMRS configuration type and / or the second DMRS configuration type with at least the at least one transmission parameter is transmitted.

20. The method of claim 18 or 19, wherein: The at least one transmission parameter includes at least one of the following: Transmit Configuration Indicator (TCI) status identification (ID), Indicates the TCI status, Reference signal, Scheduling offset, Time ahead, Control resource set (CORESET) pool index value or CORESET group index value, DMRS mapping type, or Physical cell identifier.

21. A computer-readable medium, comprising instructions stored thereon, for causing an apparatus to at least perform the method of any one of claims 15-17 or the method of any one of claims 18-20.

Images