WO2024142014A1 - Systems and methods for dynamic density reference signal patterns - Google Patents

Abstract

A method (1900) by a user equipment, UE (1112), for extending Reference Signal, RS, patterns includes receiving (1902), from a network node (1110), information for identifying a primary RS pattern and at least one secondary RS pattern The UE generates (1904) an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern. The UE uses (1906) the extended RS pattern to perform at least one operation associated with a RS.

Description

SYSTEMS AND METHODS FOR DYNAMIC DENSITY REFERENCE SIGNAL PATTERNS TECHNICAL FIELD The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for dynamic density reference signal patterns. BACKGROUND New Radio (NR) uses Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP- OFDM) in both downlink (i.e., from a network node, gNodeB (gNB), or base station, to a user equipment (UE) and uplink (i.e., from UE to gNB or base station). Discrete Fourier Transform (DFT) spread OFDM is also supported in the uplink. In the time domain, NR downlink (DL) and uplink (UL) are organized into equally sized subframes of 1 ms each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing.7 Data scheduling in NR is typically on a slot basis. FIGURE 1 illustrates an example NR time domain structure with a 14-symbol slot and 15 KHz subcarrier spacing. As illustrated, the first two symbols contain physical downlink control channel (PDCCH) and the rest contains physical shared data channel, which is either physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH). Different subcarrier spacing values are supported in NR. The supported subcarrier spacing ^{values (also referred to as different numerologies) are given by ∆ ^^ = (15 × 2 ^^) ^^ ^^ ^^ where ^^ ∈} _{0,1,2,3,4 . ∆ ^^ = 15 ^^ ^^ ^^ is the basic subcarrier spacing. The slot durations at different subcarrier} spacings is given by ¹ 2 ^{^^} ^^ ^^. In the a system bandwidth is divided into resource blocks (RBs), each corresponding to 12 contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. FIGURE 2 illustrates the basic NR physical time-frequency resource grid. Only one RB within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE). DL PDSCH transmissions can be either dynamically scheduled, i.e., in each slot the gNB transmits downlink control information (DCI) over PDCCH about which UE data is to be transmitted to and which RBs in the current DL slot the data is transmitted on, or semi-persistently scheduled (SPS) in which periodic PDSCH transmissions are activated or deactivated by a DCI. Different DCI formats are defined in NR for DL PDSCH scheduling including DCI format 1_0, DCI format 1_1, and DCI format 1_2. Similarly, UL PUSCH transmission can also be scheduled either dynamically or semi- persistently with UL grants carried in PDCCH. NR supports two types of semi-persistent UL transmission, i.e., type 1 configured grant (CG) and type 2 configured grant, where Type 1 configured grant is configured and activated by Radio Resource Control (RRC) while type 2 configured grant is configured by RRC but activated/deactivated by DCI. The DCI formats for scheduling PUSCH include DCI format 0_0, DCI format 0_1, and DCI format 0_2. DMRS Configuration Demodulation reference signals (DMRS) are used for coherent demodulation of physical layer data channels, i.e., PDSCH and PUSCH, as well as of PDCCH. The DMRS is confined to RBs carrying the associated physical layer channel and is mapped on allocated REs of the time- frequency resource grid such that the receiver can efficiently handle time/frequency-selective fading radio channels. The mapping of DMRS to REs is configurable in both frequency and time domain. There are two mapping types in the frequency domain, i.e., type 1 and type 2. In addition, there are two mapping types in the time domain, i.e., mapping type A and type B, which define the symbol position of the first OFDM symbol containing DMRS within a transmission interval. The DMRS mapping in time domain can further be single-symbol based or double-symbol based, where the latter means that DMRS is mapped in pairs of two adjacent OFDM symbols. For single symbol based DMRS, a UE can be configured with one, two, three, or four single-symbol DMRS in a slot. For double-symbol based DMRS, a UE can be configured with one or two such double-symbol DMRS in a slot. In scenarios with low Doppler, it may be sufficient to configure front-loaded DMRS only, i.e. one single-symbol DMRS or one double-symbol DMRS, whereas in scenarios with high Doppler additional DMRS will be required in a slot. FIGURE 3 shows an example of type 1 and type 2 front-loaded DMRS where different Code Division Multiplexing (CDM) groups are indicated by different patterns. Specifically, FIGURE 3 shows single-symbol and double-symbol DMRS and time domain mapping type A with first DMRS in the third OFDM symbol of a transmission interval of 14 symbols. It may be observed from FIGURE 3 that type 1 and type 2 differs with respect to both the mapping structure and the number of supported DMRS CDM groups where type 1 support 2 CDM groups and type 2 support 3 CDM groups. A DMRS antenna port is mapped to the resource elements within one CDM group only. For single-symbol DMRS, two antenna ports can be mapped to each CDM group whereas for double-symbol DMRS four antenna ports can be mapped to each CDM group. Thus, for DMRS type 1 the maximum number of DMRS ports is four for a single-symbol based DMRS configuration and eight for double-symbol based DMRS configuration. For DMRS type 2, the maximum number of DMRS ports is six for a single-symbol based DMRS configuration and twelve for double-symbol based DMRS configuration. An orthogonal cover code (OCC) of length 2 (i. e. , [+1, +1] or [+1, −1]) is used to separate antenna ports mapped in the same two REs within a CDM group. The OCC is applied in frequency domain (FD) as well as in time domain (TD) when double-symbol DMRS is configured. This is illustrated in FIGURE 3 for CDM group 0. In NR Rel-15, the mapping of a PDSCH DMRS sequence ^^⁽ ^^⁾, ^^ = 0,1, … on antenna port ^^ and subcarrier ^^ in OFDM symbol ^^ for the numerology index ^^ is specified in 3GPP TS38.211 as: ^^^{( ^^, ^^)} ^_{^, ^^} = ^^_P ^D D^M S^R C^S H ^^ _^^( ^^^′) ^^ _^^( ^^^′) ^^(2 ^^ + ^^^′) ¹ 2 = 0,1 ^_{^ = ^^} ^̅ _{+ ^^} ^′ ^^ = 0,1, … where ^^ _^^( ^^^′) represents a frequency domain length 2 OCC code and ^^ _^^ ⁽ ^^^′) represents a time domain length 2 OCC code. Table 1 and Table 2 show the PDSCH DMRS mapping parameters for configuration type 1 and type 2, respectively. Table 1: PDSCH DMRS mapping parameters for configuration type 1. CDM w_f ( k ^{^} ) w_t( l ^{^} ) p group λ ^ k ^{^} ^ 0 k ^{^} ^ 1 l ^{^} ^ 0 l ^{^} ^ 1 1000 0 0 +1 +1 +1 +1 1001 0 0 +1 -1 +1 +1 1002 1 1 +1 +1 +1 +1 1003 1 1 +1 -1 +1 +1 1004 0 0 +1 +1 +1 -1 1005 0 0 +1 -1 +1 -1 1006 1 1 +1 +1 +1 -1 1007 1 1 +1 -1 +1 -1 Table 2: PDSCH DMRS mapping parameters for configuration type 2. CDM w_f ( k ^{^} ) w_t( l ^{^} ) p group λ ^ k ^{^} ^ 0 k ^{^} ^ 1 l ^{^} ^ 0 l ^{^} ^ 1 1000 0 0 +1 +1 +1 +1 1001 0 0 +1 -1 +1 +1 1002 1 2 +1 +1 +1 +1 1003 1 2 +1 -1 +1 +1 1004 2 4 +1 +1 +1 +1 1005 2 4 +1 -1 +1 +1 1006 0 0 +1 +1 +1 -1 1007 0 0 +1 -1 +1 -1 1008 1 2 +1 +1 +1 -1 1009 1 2 +1 -1 +1 -1 1010 2 4 +1 +1 +1 -1 1011 2 4 +1 -1 +1 -1 For PDSCH mapping type A, DMRS mapping is relative to slot boundary. That is, the first front-loaded DMRS symbol in DMRS mapping type A is in either the 3^rd or 4^th symbol of the slot. In addition to the front-loaded DMRS, type A DMRS mapping can consist of up to 3 additional DMRS. FIGURE 4 illustrates some examples of DMRS configurations for PDSCH mapping type A. FIGURE 4 assumes that the PDSCH duration is the full slot. If the scheduled PDSCH duration is shorter than the full slot, the positions of the DMRS changes according to the specification 3GPP TS 38.211. It is noted that a PDSCH length of 14 symbols is assumed in the examples of FIGURE 4. For PDSCH mapping type B, DMRS mapping is relative to transmission start. That is, the first DMRS symbol in DMRS mapping type B is in the first symbol in which type B PDSCH starts. FIGURE 5 illustrates examples of DMRS configurations for mapping type B. The same DMRS design for PDSCH is also applicable for PUSCH when transform precoding is not enabled, where the sequence r ( m ) shall be mapped to the intermediate quantity ^^̃^{( ^^̃ ^^, ^^)} ^_{^, ^^} for DMRS port ^^ _^^ according to ^^^{~( ^^̃ ^^, ^^)} ^_^ = ^^ _^^( ^^^′) ^^ _^^( ^^^′) ^^(2 ^^ + ^^^′) 1 2 ^^ = ^^ ^̅ + ^^^′ ^^ = 0,1, … ^^ = 0,1, … , ^^ − 1 where w_f ^k ^{^} ^ , w_t ^l ^{^} ^ , and Δ are given by Tables 3 and 4, which correspond to Tables 6.4.1.1.3-1 and TS 38.211, and ^^ is the number of PUSCH transmission layers. The intermediate quantity ^^̃^{( ^^̃ ^^, ^^)} ^_{^, ^^} = 0 if Δ corresponds to any other antenna ports than ^^ _^^. The ^^̃^{( ^^̃ ^^, ^^)} ^_{^, ^^} shall be precoded, multiplied with the amplitude scaling factor ^ in order to conform to the transmit power specified in clause 6.2.2 of TS 38.214, and mapped to physical resources according to ^^^{( ^^} ^_{^, ^^} ^{0, ^^)} ^^̃^{( ^^̃ , ^ )} ^_{^, ^} ^{0 ^} ^ ⋮ ^{DMRS ^^ ]} where - the precoding ^^ 3GPP TS 38.211, - _^ ^p _0,..., ^p _{^ ^1 ^} is a set of physical antenna ports used for transmitting the PUSCH, and - _^ ^~ _p0,..., ^~ _{p ^ ^1 ^} is a set of DMRS ports for the PUSCH; Table 3: Parameters for PUSCH DMRS configuration type 1. ~ _p CDM group _{w ( k ) w ( l )} ^^ _f ^{^} _t ^{^} ^^ k ^ ^ 0 k ^ ^ 1 l ^ ^ 0 l ^ ^ 1 0 0 0 +1 +1 +1 +1 1 0 0 +1 -1 +1 +1 2 1 1 +1 +1 +1 +1 3 1 1 +1 -1 +1 +1 4 0 0 +1 +1 +1 -1 5 0 0 +1 -1 +1 -1 6 1 1 +1 +1 +1 -1 7 1 1 +1 -1 +1 -1 Table 4: Parameters for PUSCH DMRS configuration type 2. ~ _p CDM group w_f ( k ^ ) w_t( l ^ ) ^^ ^^ k ^{^} ^ 0 k ^{^} ^ 1 l ^{^} ^ 0 l ^{^} ^ 1 0 0 0 +1 +1 +1 +1 1 0 0 +1 -1 +1 +1 2 1 2 +1 +1 +1 +1 3 1 2 +1 -1 +1 +1 4 2 4 +1 +1 +1 +1 5 2 4 +1 -1 +1 +1 6 0 0 +1 +1 +1 -1 7 0 0 +1 -1 +1 -1 8 1 2 +1 +1 +1 -1 9 1 2 +1 -1 +1 -1 10 2 4 +1 +1 +1 -1 11 2 4 +1 -1 +1 -1 DMRS Ports Signaling DMRS port(s) for a PDSCH or a PUSCH are signaled in the corresponding scheduling DCI. In addition to the DMRS ports, the number of CDM groups that are not allocated for PDSCH or PUSCH and the number of front-loaded DMRS symbols are dynamically signaled in the DCI. In PUSCH scheduling, the number of layers is indicated separately from DMRS ports signaling in the DCI. While for PDSCH scheduling, the number of layers and DMRS ports are signaled jointly in the DCI. An “antenna port(s)” bit field in DCI is used the purpose. An example for type 1 DMRS with rank=1 and up to two maximum number of front-loaded DMRS OFDM symbols for PUSCH is shown in Tables 5 and 6, which correspond to Table 7.3.1.1.2-12 and Table 7.3.1.1.2-13 of 3GPP TS 38.212. Here, 4bits are used. Note that DMRS type and maximum number of front- loaded DMRS symbols are semi-statically configured by RRC. Table 5: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 1 (from TS38.212 of 3gpp) V_alue ^{Number of DMRS CDM group(s) without} DMRS Number of front-load d_ata port(s) symbols 0 1 0 1 1 1 1 1 2 2 0 1 3 2 1 1 4 2 2 1 5 2 3 1 6 2 0 2 7 2 1 2 8 2 2 2 9 2 3 2 10 2 4 2 11 2 5 2 12 2 6 2 13 2 7 2 14-15 Reserved Reserved Reserved

Table 6: Antenna port(s), transform precoder is disabled, dmrs-Type=1, maxLength=2, rank = 2 V_alue ^{Number of DMRS CDM group(s) without} DMRS Number of front-load d_ata port(s) symbols 0 1 0,1 1 1 2 0,1 1 2 2 2,3 1 3 2 0,2 1 4 2 0,1 2 5 2 2,3 2 6 2 4,5 2 7 2 6,7 2 8 2 0,4 2 9 2 2,6 2 10-15 Reserved Reserved Reserved Another example for type 1 DMRS with up to two maximum number of front-loaded DMRS OFDM symbols for PDSCH is shown in Table 7, which corresponds to Table 7.3.1.2.2-2 of 3GPP TS 38.212.

Table 7: Antenna port(s) (1000 + DMRS port), dmrs-Type=1, maxLength=2 (from TS38.212 of 3GPP) One Codeword: Two Codewords: Codeword 0 enabled, Codeword 0 enabled, Codeword 1 disabled Codeword 1 enabled Number Number of DMRS Number of DMRS Number Value CDM DMRS of front- Value CDM DMRS po of front- group(s) port(s) load group(s) rt(s) load without symbols without symbols data data 0 1 0 1 0 2 0-4 2 1 1 1 1 1 2 0,1,2,3,4,6 2 2 1 0,1 1 2 2 0,1,2,3,4,5,6 2 3 2 0 1 3 2 0,1,2,3,4,5,6,7 2 4 2 1 1 4-31 reserved reserved reserved 5 2 2 1 6 2 3 1 7 2 0,1 1 8 2 2,3 1 9 2 0-2 1 10 2 0-3 1 11 2 0,2 1 12 2 0 2 13 2 1 2 14 2 2 2 15 2 3 2 16 2 4 2 17 2 5 2 18 2 6 2 19 2 7 2 20 2 0,1 2 21 2 2,3 2 22 2 4,5 2 23 2 6,7 2 24 2 0,4 2 25 2 2,6 2 26 2 0,1,4 2 27 2 2,3,6 2 28 2 0,1,4,5 2 29 2 2,3,6,7 2 30 2 0,2,4,6 2 31 Reserved Reserved Reserved Channel State Information Reference Symbols (CSI-RS) In NR, a reference symbol sequence is introduced for the intent to estimate channel state information, the CSI-RS. By measuring on a CSI-RS a UE can estimate the effective channel the CSI-RS is traversing including the radio propagation channel and antenna gains. In more mathematical rigor _{this implies that if a known CSI-RS signal} x _{is transmitted, a UE can estimate the coupling} between the transmitted signal and the signal (i.e., the effective channel). Hence if no virtualization is performed in the transmission, the received signal ^y can be expressed as y ^ Hx ^ e and the UE can estimate the effective channel ^H . Up to 32 CSI-RS ports can be configured for a NR UE. That is, the UE can estimate the channel from up to thirty-two transmit antenna ports. An antenna port is equivalent to a reference signal resource that the UE shall use to measure the channel. Hence, an gNB with two antennas could define two CSI-RS ports, where each port is a set of resource elements in the time frequency grid within a subframe or slot. The base station transmits each of these two reference signals from each of the two antennas so that the UE can measure the two radio channels and report channel state information back to the base station based on these measurements. In NR, CSI-RS resources with 1,2,4,8,12,16,24 and 32 ports is supported. The sequence used for CSI-RS is ^^( ^^) and is defined by r_{(m) ^} ¹ _{^1 ^2 ^c(2m) ^ ^ j} ¹ _^ ¹ _^ ² _^c ⁽² _{m ^} ¹⁾ _^ 2 2 where the pseudo-random of 3GPP TS 38.211. The pseudo-random sequence generator shall be initialised with ^^_init = ₍2¹⁰ ₍ ^^_s ^s y^lo m^t b ^^_s ^{^^} ,_f + ^^ + 1₎(2 ^^_ID + 1) + ^^_ID)mod2³¹ at the start of each frame, ^l is the OFDM symbol number within a slot, and ^{n ID} equals the higher-layer parameter scramblingID or sequenceGenerationConfig. There are 18 different CSI-RS resource configurations in NR, where each have a specific number of ports X, as disclosed in Table 8 below. When CDM is applied, the index ^^ _^^ indicates the first subcarrier in the PRB that is used for mapping the CSI-RS sequence to resource elements, where the second subcarrier is ^^ _^^ + 1. This set ( ^^ _^^, ^^ _^^ + 1) of two subcarriers is associated with a CDM group ^^, where a CDM group covers 1, 2 or 4 OFDM symbols. The index ^^ _^^′ , or ^^ _^^′ + 1, indicates the first OFDM symbol within the slot that is associated with a CDM group. Note that ^^ _^^ and ^^ _^^′ are parameters signalled from gNB to UE by RRC signalling when configuring the CSI- RS resource. When CDM is applied, the size of a CDM group, ^^, is either 2, 4 or 8 and the total number of CDM groups is given by the number of ( ^^ _^^ , ^^ _^^′), ( ^^ _^^, ^^ _^^′ + 1) pairs given by the configuration. A CDM group can thus refer to a set of ports, where the set of 2 antenna ports occurs when only CDM in frequency-domain over two adjacent subcarriers is considered (FD- CDM2). In NR, CSI-RS ports are numbered within a CDM group first and then across CDM groups ^^, ^^ = 3000 + ^^^′, where ^^^′ = ^^ + ^^ ∙ ^^ with ^^ = 0,1, … , ^^ − 1 (Ports are sometimes numbered by excluding the value “3000”, meaning that ports are implicitly indicated by ^^^′.) For example, CSI-RS resource configuration given by row 4 in Table 1 has two CDM groups ( ^^ = 0,1) of size ^^ = 2, where the ports 3000 and 3001 maps to the CDM group indicated by ^^₀ and the ports 3002 and 3003 maps to the CDM group indicated by ^^₀ + 2. Table 8: CSI-RS Resource Configurations Row Ports Density cdm- _{^k ,l ^} CDM group ^{k ^ l ^} X ^{^} Type index ^^ 1 ^{1 3 noCDM} ( ^^₀, ^^₀), ( ^^₀ + 4, ^^₀), ( ^^₀ + 8, ^^₀) ^{0,0,0 0 0 2 1 1, 0.5 noCDM} ( ^^₀, ^^₀), ^{0 0 0 3 2 1, 0.5 fd-CDM2} ( ^^₀, ^^₀), ^{0 0, 1 0 4 4 1 fd-CDM2} ( ^^₀, ^^₀), ⁽ ^^₀ + 2, ^^₀ ^{) 0,1 0, 1 0} 5 4 1 fd-CDM2 ( ^^₀, ^^₀), ( ^^₀, ^^₀ + 1) 0,1 0, 1 0 6 8 1 fd-CDM2 ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₂, ^^₀), ( ^^₃, ^^₀) 0,1,2,3 0, 1 0 7 8 1 fd-CDM2 ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₀, ^^₀ + 1), ( ^^₁, ^^₀ + 1) 0,1,2,3 0, 1 0 8 8 1 cdm4- ( ^^₀, ^^₀), ( ^^₁, ^^₀) 0,1 0, 1 0, 1 FD2-TD2 9 ^{12 1 fd-CDM2 ( ^^} ₀ ^{, ^^} ₀ ^{) , ( ^^} ₁ ^{, ^^} ₀ ^{) , ( ^^} ₂ ^{, ^^} ₀ ^{) , ( ^^} ₃ ^{, ^^} ₀ ^{) , ( ^^} ₄ ^{, ^^} ₀ ^{) , 0,1,2,3,4, 0, 1 0} ( _{^^5, ^^0) 5} 10 12 1 cdm4- ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₂, ^^₀) 0,1,2 0, 1 0, 1 FD2-TD2 1^{1 16 1,0.5 fd-CDM2 ( ^^0, ^^0) , ( ^^1, ^^0) , ( ^^2, ^^0) , ( ^^3, ^^0) , ( ^^0, ^^0 + 0,1,2,3,4, 0, 1 0} 1_{), ( ^^1, ^^0 + 1), ( ^^2, ^^0 + 1), ( ^^3, ^^0 + 1) 5,6,7} 12 16 1, 0.5 cdm4- ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₂, ^^₀), ( ^^₃, ^^₀) ^{0,1,2,3 0, 1 0, 1} FD2-TD2 1^{3 24 1, 0.5 fd-CDM2 ( ^^0, ^^0), ( ^^1, ^^0), ( ^^2, ^^0), ( ^^0, ^^0 + 1),} 0,1,2,3, 0, 1 0 ( ^{^^} ₁ ^{, ^^} ₀ ^{+ 1) , ( ^^} ₂ ^{, ^^} ₀ ^{+ 1) , ( ^^} ₀ ^{, ^^} ₁ ^{) , ( ^^} ₁ ^{, ^^} ₁ ^{) ,} 4,5,6,7, ( _{^^ , ^^ ) , ( ^^ , ^^ + 1) , ( ^^ , ^^ + 1)} 8,9,10,11 2 _{1 0 1 1 1 , ( ^^2, ^^1 + 1)} 14 24 1, 0.5 cdm4- ^{( ^^0, ^^0) , ( ^^1, ^^ ) , ( ^^ , ^^ ) , ( ^^ , ^^ ) , ( ^^ , ^^ ) , 0,1,2,3,4, 0, 1 0, 1} FD2-TD2 ₍ ^{0 2 0 0 1 1 1} ^_{^2, ^^1) 5} 15 24 1, 0.5 cdm8- ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₂, ^^₀) ^{0,1,2 0, 1 0,} FD2-TD4 1, 2, 3 1^{6 32 1, 0.5 fd-CDM2 ( ^^0, ^^0) , ( ^^1, ^^0) , ( ^^2, ^^0) , ( ^^3, ^^0) ,( ^^0, ^^0 +} 0,1,2,3,4, 0, 1 0 1^{) , ( ^^1, ^^} 5,6,7,8, 0 ^{+ 1) , ( ^^2, ^^0 + 1) , ( ^^3, ^^ + 1) ,} ( ⁰ ^_{^ , ^^ ) , ( ^^ , ^^ ) , ( ^} 9,10,11,12, 0 _{1 1 1 ^2, ^^1) , ( ^^3, ^^1) , ( ^^0, ^^1 +} 13,14,15 1_{), ( ^^1, ^^1 + 1), ( ^^2, ^^1 + 1), ( ^^3, ^^1 + 1)} 17 32 1, 0.5 cdm4- ^{( ^^0, ^^0) , ( ^^1, ^^0) , ( ^^2, ^^0) , ( ^^ , ^^ ) , ( ^^ , ^^ ) , 0,1,2,3,4, 0, 1 0, 1} FD2-TD2 ₍ ^{3 0 0 1} ^_{^1, ^^1), ( ^^2, ^^1), ( ^^3, ^^1) 5,6,7} 18 32 1, 0.5 cdm8- ( ^^₀, ^^₀), ( ^^₁, ^^₀), ( ^^₂, ^^₀), ( ^^₃, ^^₀) ^{0,1,2,3 0,1 0,1,} FD2-TD4 2, 3 Mapping of CSI-RS ports to resource elements The 3GPP specifications for NR, TS 38.211 v16.0,0 states that for each CSI-RS configured, the UE shall assume the sequence ^^( ^^) being mapped to resources elements ( ^^, ^^) _{^^, ^^} according to ^^^{~( ^^, ^^)} ^_{^, ^^} = ^^ _{^^ ^^ ^^ ^^ ^^} ^^ _^^( ^^^′) ^^ _^^( ^^^′) ^^ _{^^, ^^, ^^}( ^^^′) ^^ = 0,1, … when the following conditions are fulfilled: - the resource element ( ^^, ^^) _{^^, ^^} is within the resource blocks occupied by the CSI-RS resource for which the UE is configured From this expression, it is possible to deduce (when CDM is applied) that for a given CSI-RS resource (row in Table 8) within a given OFDM symbol (fixed ^^), an antenna port ^^ is mapped to two adjacent subcarriers using two samples from the sequence ^^( ^^^′) where two adjacent values of ^^^′ is used since ^^^′ depends on ^^^′ = 0,1. The values of ^̅^ , ^^ and ^^ are given by RRC configuration, and the parameters ^^ _^^ ⁽ ^^^′) and ^^ _^^ ⁽ ^^^′) are given by Table 9 below, where table index is related to port number as ^^. For a CDM group of size ^^ = 2,4,8, the corresponding values on ^^^′ are ^^^′ = 0, ^^^′ = 0,1, ^^^′ = 0,1,2,3.

Table 9: OCC Parameters I_ndex [ ^^_f( ^^) ^^_f( ^^)] [ ^^_t( ^^) ^^_t( ^^) ^^_t( ^^) ^^_t( ^^)] 0 ^ ^1 ^1 ^ ^ ^1 ^1 ^1 ^1 ^ 1 ^ ^1 ^1 ^ ^ ^1 ^1 ^1 ^1 ^ 2 ^ ^1 ^1 ^ ^ ^1 ^1 ^1 ^1 ^ 3 ^ ^1 ^1 ^ ^ ^1 ^1 ^1 ^1 ^ 4 ^ ^1 ^1 ^ ^ ^1 ^1 ^1 ^1 ^ 5 _^ ^1 ^1 _{^ ^} ^1 ^1 ^1 ^1 _^ 6 _^ ^1 ^1 _{^ ^} ^1 ^1 ^1 ^1 _^ 7 _^ ^1 ^1 _{^ ^} ^1 ^1 ^1 ^1 _^ From this expression, it can also be observed that the mapping to resource elements do not depend on the CDM group. In other words, the same pseudo-random sequence is used in all the used CDM groups in OFDM symbol ^^. FIGURE 6 illustrates a Release 15 sequence mapped to CDM groups with corresponding CSI-RS antenna ports. Specifically, as illustrated in FIGURE 6, the four ports p0=3000 to p3=3003 are mapped to two CDM groups ( ^^ = 2) and where the same sequence samples ^^(0) and ^^(1) are used in both CDM groups. FIGURE 6 represents a CSI-RS resource configuration given by row 4 in Table 8, with first CDM group starting at subcarrier ^^₀ and the second starting at subcarrier ^^₀ + 2 (= ^^₁), both in the same OFDM symbol ^^₀. Phase-Tracking Reference Signals (PT-RS) for PUSCH in NR In NR, phase tracking reference signal (PT-RS) can be configured for PUSCH transmissions in order for the receiver to correct phase noise related errors. PT-RS can be configured with the higher layer parameter PTRS-UplinkConfig in DMRS-UplinkConfig for PUSCH scheduled by DCI format 0_1 or DCI format 0_2. In NR Rel.15, for CP-OFDM based waveform, either one or two PT-RS ports for PUSCH are supported. Each PT-RS port is associated with one of the DM-RS ports for the PUSCH. If more than one DM-RS port is scheduled, i.e. multi-layer MIMO transmission of PUSCH, then it is desirable from performance perspective if the PT-RS is transmitted in the layer having the highest SINR. This will maximize the phase tracking performance. The network knows which layer has best SINR, based on measurements on the multi-port SRS. Hence, the network can, when scheduling the PUSCH from the UE, indicate which layer the UE shall transmit the PT-RS on. This is signalled using PTRS-DMRS association, as defined by the table further down. The maximum number of configured PT-RS ports is given by the higher layer parameter maxNrofPorts in PTRS-UplinkConfig based on the UE reported need. If a UE has reported the capability of supporting full-coherent UL transmission, one PT-RS port is expected to be configured if needed. In the frequency domain, for CP-OFDM based waveform,, a PT-RS can be in at most one subcarrier per 2 PRBs. Also, the subcarrier used for a PT-RS port must be one of the subcarriers also used for the DM-RS port associated with the PT-RS port. For DM-RS configuration type 1, a DM-RS port is mapped to every second subcarrier. Consequently, an associated PT-RS can only be mapped to one out of 6 subcarriers. An offset can be configured to determine which subcarrier the DM-RS is mapped to (see Table 6.4.1.2.2.1-1 in 3GPP TS 38.211). In the time domain, a PT-RS can be configured with a time density of 1,2 or 4, corresponding to PT-RS in every OFDM symbol, every second OFDM symbols, or every fourth OFDM symbols in a slot, respectively. The modulated symbol used for the PT-RS is the same as the associated DM-RS at the same subcarrier. FIGURE 7 illustrates an example of PT-RS for CP-OFDM based waveform. Specifically, FIGURE 7 illustrates the PT-RS port being associated with DM-RS port 0 and having a subcarrier offset of 4 and a time density of 2. For codebook or non-codebook based UL transmission, the association between UL PT- RS port(s) and DM-RS port(s) is signalled by a “PTRS-DMRS association” field in DCI format 0_1 and DCI format 0_2. If the UE is configured with one PT-RS port, the DM-RS port associated with the PT-RS port is indicated by DCI parameter “PTRS-DMRS association” in DCI format 0_1 and DCI format 0_2 in Table 10, which provides PTRS-DMRS association for UL PTRS pot 0 and corresponds to Table 7.3.1.1.2-25 of 3GPP TS 38.212. As discussed above the purpose is to schedule the PT-RS to be transmitted on the strongest layer/DMRS port (since there is one DMRS port per layer). Table 10 Value DMRS port 0 1^st scheduled DMRS port 1 2^nd scheduled DMRS port 2 3^rd scheduled DMRS port 3 4^th scheduled DMRS port For non-codebook based UL transmission, the actual number of PT-RS port(s) to transmit is determined based on SRI(s) in DCI format 0_1 and DCI format 0_2. A UE is configured with the PT-RS port index for each configured SRS resource by the higher layer parameter ptrs- PortIndex configured by SRS-Config. If the PT-RS port index associated with different SRIs are the same, the corresponding UL DM-RS ports are associated to the one PT-RS port. For partial-coherent and non-coherent codebook-based UL transmission, the actual number of UL PT-RS port(s) is determined based on TPMI and/or number of layers which are indicated by 'Precoding information and number of layers' field in DCI format 0_1 and DCI format 0_2. If the UE is configured with 2 PT-RS ports, the actual PT-RS port(s) and the associated transmission layer(s) are derived from indicated TPMI as: - PUSCH antenna port 1000 and 1002 in indicated TPMI share PT-RS port 0, and PUSCH antenna port 1001 and 1003 in indicated TPMI share PT-RS port 1. - PT-RS port 0 is associated with a DM-RS port which are transmitted with PUSCH antenna port 1000 and PUSCH antenna port 1002 in indicated TPMI, and PT-RS port 1 is associated with another DM-RS port which are transmitted with PUSCH antenna port 1001 and PUSCH antenna port 1003 in indicated TPMI, where the two DM-RS ports are given by DCI parameter 'PTRS-DMRS association' in DCI format 0_1 and DCI format 0_2 in Table 11, which shows PTRS-DMRS association for UL PTRS ports 0 and 1 and corresponds to Table 7.3.1.1.2-26 of 3GPP TS 38.212. Table 11 Value DMRS port Value DMRS port of of LSB MSB 0 1^st DMRS port which 0 1^st DMRS port which shares PTRS port 0 shares PTRS port 1 1 2^nd DMRS port which 1 2^nd DMRS port which shares PTRS port 0 shares PTRS port 1 There currently exist certain challenge(s), however. For example, NR and LTE have one different RS design for each purpose (usage), including, for example, SRS, DMRS, CSI-RS, TRS, and PTRS. The problem with previous methods and techniques is that dedicated channel estimation algorithms are needed for each RS design. Additionally, a problem is that NR and LTE RS design may be overly dense for one usage (in either dimension), while at the same time being inadequately dense for another usage. SUMMARY Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are provided that include a scalable, dynamically extendible RS design that can be dynamically configured (or dynamically indicated) to be suitable for one purpose or multiple purposes simultaneously, when needed. According to certain embodiments, a method by a UE is provided for extending RS patterns. The method includes receiving, from a network node, information for identifying a primary RS pattern and at least one secondary RS pattern. The UE generates an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern. The UE uses the extended RS pattern to perform at least one operation associated with a RS. According to certain embodiments, a UE for extending RS patterns is configured to receive, from a network node, information for identifying a primary RS pattern and at least one secondary RS pattern. The UE is configured to generate an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern. The UE is configured to use the extended RS pattern to perform at least one operation associated with a RS. According to certain embodiments, a method by a network node is provided for extending RS patterns. The method includes transmitting, to a UE, information for generating an extended RS pattern based on a primary RS pattern and at least one secondary RS pattern. Based on the extended RS pattern, the network node receives a RS from the UE or transmitting the RS to the UE. According to certain embodiments, a network node for extending RS patterns is configured to transmit, to a UE, information for generating an extended RS pattern based on a primary RS pattern and at least one secondary RS pattern. Based on the extended RS pattern, the network node is configured to receive a RS from the UE or transmitting the RS to the UE. Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of providing an RS design that is scalable and/or dynamically extendible so as to be suitable for one or multiple purposes as needed. As another example, certain embodiments may provide a technical advantage of being dynamically configured or dynamically indicated. As still another example, certain embodiments may provide a technical advantage of providing a RS design that is based on a common framework with defining parameters so as to provide a generic and flexible design that may be adapted based on any need, purpose, usage, subcarrier spacing, more or less phase noise, etc. As another example, certain embodiments may provide a technical advantage of providing an RS design that is scalable and/or dynamically extendible so as to be suitable for one or multiple purposes as needed As yet another example, certain embodiments may provide a technical advantage of achieving excellent performance vs overhead tradeoff. As still another example, certain embodiments may provide a simplified channel estimation algorithm since the same RS framework is used irrespectively of the usage of the RS. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: FIGURE 1 illustrates an example NR time domain structure with a 14-symbol slot and 15 KHz subcarrier spacing; FIGURE 2 illustrates the basic NR physical time-frequency resource grid; FIGURE 3 illustrates an example of type 1 and type 2 front-loaded DMRS where different CDM groups are indicated by different colors and/or patterns; FIGURE 4 illustrates examples of DMRS configurations for PDSCH mapping type A; FIGURE 5 illustrates examples of DMRS configurations for PDSCH mapping type B; FIGURE 6 illustrates a Release 15 sequence mapped to CDM groups with corresponding CSI-RS antenna ports; FIGURE 7 illustrates an example of PT-RS for CP-OFDM based waveform, according to certain embodiments; FIGURE 8 illustrates an example RS pattern with a primary pattern and a secondary pattern, according to certain embodiments; FIGURE 9 illustrates a table defining RS ports used for PDSCH, PUSCH and PDCCH demodulation, for phase noise tracking, for synchronization and for CSI measurement and reporting, according to certain embodiments; FIGURE 10 illustrates an example RS pattern, according to certain embodiments; FIGURE 11 illustrates an example of DCI based selection of the primary and secondary RS, according to certain embodiments; FIGURE 12 illustrates an example of primary and secondary patterns, according to certain embodiments; FIGURE 13 illustrates another table defining RS ports used for PDSCH, PUSCH and PDCCH demodulation, for phase noise tracking, for synchronization and for CSI measurement and reporting, according to certain embodiments; FIGURE 14 illustrates another table defining RS ports used for PDSCH, PUSCH and PDCCH demodulation, for phase noise tracking, for synchronization and for CSI measurement and reporting, according to certain embodiments; FIGURE 15 illustrates a table defining CSI-RS ports used for CSI reporting, according to certain embodiments; FIGURE 16 illustrates another table defining CSI-RS ports used for CSI reporting, according to certain embodiments; FIGURE 17 illustrates a table defining SRS ports used for SRS measurements, according to certain embodiments; FIGURE 18 illustrates an example of a communication system, according to certain embodiments; FIGURE 19 illustrates an example UE, according to certain embodiments; FIGURE 20 illustrates an example network node, according to certain embodiments; FIGURE 21 illustrates a block diagram of a host, according to certain embodiments; FIGURE 22 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 23 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments; FIGURE 24 illustrates an example method by a UE for extending RS patterns, according to certain embodiments; FIGURE 25 illustrates an example method by a UE for determining a RS usage, according to certain embodiments; FIGURE 26 illustrates another example method by a UE for extending RS patterns, according to certain embodiments; FIGURE 27 illustrates an example method by a network node for extending RS patterns, according to certain embodiments; FIGURE 28 illustrates an example method by a network node for indicating a RS usage, according to certain embodiments; and FIGURE 29 illustrates another example method by a network node for extending RS patterns, according to certain embodiments. DETAILED DESCRIPTION Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g., in a gNB), Distributed Unit (e.g., in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g., Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g., E- SMLC), etc. Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc. In some embodiments, generic terminology, “radio network node” or simply “network node (NW node)”, is used. It can be any kind of network node which may comprise base station, radio base station, base transceiver station, base station controller, network controller, evolved Node B (eNB), Node B, gNodeB (gNB), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), Central Unit (e.g., in a gNB), Distributed Unit (e.g., in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), etc. The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs. According to certain embodiments, a scalable, (dynamically) extendible RS design is provided. The RS design can be dynamically configured to be suitable for one purpose, or to be configured (even dynamically indicated configuration) to be suitable for multiple purposes simultaneously. In particular, the RS design is so generic and flexible in its design that it can, with a few defining parameters, be adapted to any need/usage, purpose, subcarrier spacing, more or less phase noise, etc. For example, according to certain embodiments, methods and systems include defining one (set of) primary RS pattern and zero or more (set of) secondary RS patterns. As used herein, an RS pattern is a mapping of reference signals to the resource element grid in an OFDM system in a prescribed pattern. The resulting RS is a combination of these two patterns (primary and secondary) and each pattern is given by one or more of ^ Every k:th subcarrier in f-domain ^ Every l:th OFDM symbol in t-domain ^ An Offset in f and t domains ^ A Power boost, -inf (to create empty RE), 0 dB, or boost values (+3, +6, etc.) ^ An Antenna port identifier This can be described in text, equations, or a table. According to certain embodiments, methods and systems are provided that include a channel estimator in the receiver that is configured to use the same few parameter to re-configure the channel estimation algorithm. There is no need for specific algorithms for each RS type as in previous technology. For example, these uses of the RS can be configured to the UE for a DL transmission (and similar for UL where CSI-RS is replaced with SRS): ^ DMRS, (demodulation) ^ DMRS+TRS, (demodulation + synchronization) ^ DMRS+PTRS+TRS, (demodulation + phase noise tracking + synchronization) ^ DMRS+CSI-RS, (demodulation + CSI measurement) ^ DMRS+PTRS, (demodulation + phase noise tracking) Note that if the RS is used for only DMRS, its configuration from the generic framework of scalable and flexible configurations should be different compared to if the DMRS is also used for TRS, CSI, etc. According to certain embodiments, the PDSCH or PUSCH mapping to resource element adapts dynamically according to or to take into account (i.e. rate match around) the indicated RS pattern in the scheduled data resources. Thus, for each scheduled PDSCH, a different RS pattern from the generic pattern may apply. In a particular embodiment, with regard to DL, the UE may know the usage of the current indicated RS pattern based on one or more of: ^ If PDSCH payload is 0, and there is no CSI-RS measurement and report request indicated, then the RS is not intended for demodulation, only synchronization and there is no CSI-RS measurement ^ If PDSCH payload is 0, and there is a CSI-RS measurement and report request indicated, then the RS is not intended for demodulation, only synchronization or a CSI-RS measurement ^ If PDSCH payload is >0, the RS is used for at least demodulation, ^ If a CSI request is indicated, the RS should also be used for a CSI calculation and reporting ^ If RS structure allows for synchronization and phase noise tracking the UE can perform these functionalities as well ( this is up to the UE to decide, hence it is an implementation embodiment,) In another particular embodiment, the usage of the RS can be explicitly indicated, e.g. by a separate field in the DCI, instead of being derived from the payload size. One could also envision other DCI fields that the payload size to base the usage upon. In a particular embodiment, with regard to UL, the receiving network node(s) can decide on its/their own what to use the RS for since the network indicates to the UE what RS (which parameter combination) to use for the next transmission. For example, in a particular embodiment, if there is a need to improve sync, then a higher density RS in time and/or frequency can be triggered for the next scheduling occasion. In a particular embodiment, whenever two RS usage types overlap (there is a conflict in what to assume based on, for example, different triggering occasions of the same overlapping RS reception), a priority order is defined. In a particular embodiment, for example, the denser configuration of the overlapping RS configurations is assumed. For example, in a particular embodiment, if DMRS+CSI and DMRS+TRS is triggered, then the UE shall assume that the DMRS-TRS pattern is used for transmission/reception, since it is denser, i.e. it utilized a larger number of resources elements per defining resource group. A defining resource group can be 12 adjacent subcarriers and 14 adjacent OFDM symbols, or 12 adjacent subcarriers and the ODM symbols covered by the scheduled PDSCH duration, in a particular embodiment. This also determines the PDSCH to RE mapping. FIGURE 8 shows an example RS pattern 100 with a primary pattern and a secondary pattern, according to certain embodiments. Specifically, FIGURE 8 shows a primary pattern mapping vertically (i.e. to subcarriers within one OFDM symbol) and a secondary pattern mapping horizontally (i.e. to OFDM symbols within one subcarrier). According to certain embodiments, a primary pattern is dense in frequency + sparse in time and a secondary pattern is dense in time and sparse in frequency, similar to the RS pattern 100 illustrated in FIGURE 8. In a particular embodiment, whether a secondary pattern is present or not, can be dynamically indicated (explicitly or implicitly) in DCI (after RRC configuration): ^ For example, if QPSK is used for the scheduled PxSCH (PUSCH Or PDSCH), then secondary pattern can be disabled (implicit indication) ^ For example, if improved synchronization is needed, secondary pattern is enabled. (explicit indication in DCI) PxSCH rate matching (mapping PxSCH data to RE) takes into account the presence or no- presence of the secondary pattern. According to certain embodiments, RS patterns are universal and are subsequently used to define the antenna ports for different RS usages : — A RS is defined with the following parameters: — Frequency domain comb: k_f = {1,2,4,8,12,16,24} — Frequency domain shift: ∆_f= {0,1,2,3,4,5,6,7} — Time domain occasions: K̅_t = {k₁, k₂, k₃, k₄} symbols relative to first RS — Time domain shift: ∆_t= {0,2} symbols relative to a reference start symbol — FD-OCC w_f = {1, [_{+1 +1}], [_{+1 −1}]} — TD-OCC w_t = {1, [+1 +1], [+1 −1]} — RS Sequence seed N_seed = {N_I ⁰ D , N¹ I_D , N_I ² D , N_I ³ D , N_I ⁴ D , N_I ⁵ D , N_I ⁶ D , N_I ⁷ D , N_I ⁸ D } — Setting of additional parameters for these RS ports — Time domain shift ∆_t= 0 — Time occasions for primary RS (symbols) K̅¹ _t = {k₁, k₂, k₃, k₄} — Default {3,6,15,24} — Time periodicity for secondary RS (symbols) k² _t = {1,2,4} — Default k² _t = 2 — Enabling of secondary pattern (DCI indication). In a particular embodiment, RS ports used for PDSCH, PUSCH and PDCCH demodulation, for phase noise tracking, for synchronization and for CSI measurement and reporting are defined according to Table 200, as shown in FIGURE 9. — Note that a port may be used for one or multiple of these purposes simultaneously, depending on configuration (for DL) or network side preference (UL) — Primary RS pattern is dense in frequency and sparse in time — Both High-frequency density and low-frequency density patterns are configured (HD,LD) per OFDM symbol (i.e. time varying frequency density) — The primary RS pattern may be configured to have an unequal distribution in time, for example ^^ _^ ¹ _^ = {3,6,15,24} symbols relative to the first DMRS — Secondary RS pattern can configured and is sparse in frequency and dense in time — Secondary RS pattern may only be present for some DMRS ports in case of a rank>1 transmission (as indicated by the antenna port indication table) Secondary RS pattern for a given subcarrier repeatedly use the sequence sample of the first occasion in time of the primary pattern (before application of the FD-OCC/TD-OCC), for the scheduled PxxCH duration. FIGURE 10 illustrates an example RS pattern 300, according to certain embodiments. In a particular embodiment, for multi-layer PxSCH scheduling, when secondary pattern is enabled, only some of the transmitted layers (some of the multiple DMRS ports) have an associated secondary pattern and the remaining DMRS ports only have primary pattern. Typically, in case of a single TRP, the “first layer”, i.e..the layer with lowest DMRS port number from that TRP, uses a primary and a secondary pattern while the remaining layers from the same TRP uses the primary pattern only. For multi-TRP, the “first layer” associated with each frequency domain comb (i.e. lowest DMRS port number among ports mapped to that comb), is associated with a secondary pattern. RS patterns are universal and are subsequently used to define the antenna ports for different RS usages (as a DMRS, SRS,CSI-RS,PTRS,TRS,…. ). RS pattern follows a comb structure in time and a repetitive structure (periodic or irregular can be configured, depending on the use case) As an embodiment, an RS is defined as follows to achieve this goal, with the following parameters: ^ Frequency domain comb: ^^ _^^ = {1,2,4,8,12,16,24} ^ Frequency domain shift: ∆ _^^= {0,1,2,3,4,5,6,7} ^ Time domain ^^ { ^^₁, ^^₂, ^^₃, ^^₄} symbols relative to first RS ^ Time domain shift: relative to a reference start symbol ^ FD-OCC ^^ _^^ = {1, [_{+1 +1}], [_{+1 −1}]} ^ TD-OCC } ^ ^{RS Sequence seed} { _{^^0 ^^ ^^ , ^^1 ^^ ^^ , ^^2 ^^ ^^ , ^^3 ^^ ^^ , ^^ ^^ ^^ , ^^ ^^ ^^ , ^^ ^^ ^^ , ^^ ^^ ^^ , ^^ ^^ ^^ }} RS sequences start (virtually) at the start of the carrier bandwidth, irrespectively of where the scheduled BW is located (for MU-MIMO reasons). The UE shall assume the sequence ^^( ^^) is defined by: ^_{^( ^^) =} ¹ (^{1 − 2 ∙ ^^(2 ^^)}) ^{+ ^^ 1} (^{1 − 2 ∙ ^^(2 ^^ + 1)}) where the pseudo-random sequence ^^( ^^) is defined in clause 5.2.1 of 3GPP TS 38.211. The pseudo-random sequence generator shall be initialized in each OFDM symbol with: ^^ _{^^ ^^ ^^ ^^} = (2¹⁷( ^^ + 1)(2 ^^ _^ ^{^} ^ _^ ^{^} ^ ^{^^ ^^ ^^ ^^} + 1) + 2 ^^ _^^ ^{^} ^^{^} ^ ^{^^ ^^ ^^ ^^} + ^^ _{^^ ^^ ^^ ^^} + ∆ _^^) mod 2³¹ where ^^ is the number of the first symbol of a double symbol for MsgA and is the system symbol number otherwise, and ^ ^^ _^ ⁰ _{^ ^^} , ^^ _^ ¹ _{^ ^^} ∈ {0, 1, … , 65535} are given by the higher-layer parameters scramblingID0 and scramblingID1, respectively, if provided by RRC ^ ^^ _^ ^{^} ^ _^ ^{^} ^ ^{^^ ^^ ^^ ^^} = ^^ _^ ^{^} ^ _^ ^{^ ^} ^^{^ ^^ ^^} for MsgA (in case ^^ ^{^ ^ ^^ ^^} of selected TRP) and MsgB when preceding MsgA did ^ ^^ ^{^^} ^_{^ ^^} ^{^^ ^^ ^^ ^^} = C-RNTI for MsgB when preceding MsgA contained a C-RNTI ^ ^^ _^ ^{^} ^ _^ ^{^} ^ ^{^^ ^^ ^^ ^^} = ^^ _^ ^{^} ^ _^ ^{^ ^} ^^{^ ^^ ^^} otherwise The quantity ^^ _{^^ ^^ ^^ ^^} ∈ {0, 1} is given by the RS sequence initialization field, if the DCI associated with the PDSCH or PUSCH transmission contains the field, otherwise ^^ _{^^ ^^ ^^ ^^} = 0. For the PDCCH, ^^_init = ^^_ID mod 2³¹. Collisions Between Primary and Secondary RS Patterns In a particular embodiment, the secondary RS is mapped to resource elements which doesn’t have primary RS already. Hence, primary is mapped out first before mapping out secondary (at least conceptually). For the purpose of sequence-to-RE mapping, several possibilities exist when handling the “collision” between primary and secondary resources (e.g. the secondary sequence is punctured when collisions occur, or the colliding RE is excluded from the secondary sequence mapping). Generation of Sequences According to certain embodiments, the primary RS pattern and the secondary RS pattern use different sequences. Thus, different seeds are used for the random number generator. Alternatively, in other embodiments, the secondary RS sequence is mathematically derived from the primary RS sequence and there is, thus, no need for a separate secondary sequence generator. DCI FIGURE 11 illustrates an example 400 of DCI based selection of the primary and secondary RS, according to certain embodiments. According to certain embodiments, to indicate the RS to be used for a transmission, or reception, the scheduling DCI has a field or a codepoint that indicates an entry in a combination table. The combination table entry then points out an entry of a primary table and if secondary RS is present for an antenna port, an entry in a secondary table is addressed. The tables for primary and secondary RS may be one and the same table that each selects one RS pattern from a generic, flexible, RS pattern. Hence, each table row contains the parameter setting to configure an instance of the generic RS pattern. It is noted that the use of table here is conceptual; the information may be represented in other, alternative ways than a table. In a particular embodiment, a rule can be applied, which handles the case where both primary and secondary RS has mapping to the same RE, then the primary pattern should be assumed. This rule is important in case primary and secondary pattern has different RS sequence values in such colliding RE since otherwise there will be confusion on which modulation constellation symbol (e.g. QPSK symbol) is used for that RE and performance would degrade. FIGURE 12 illustrates an example 500 of primary and secondary patterns, according to certain embodiments. RS Port Tables RS are using the defined scalable and extendable RS framework. These port tables are used when there is a multipurpose usage of the RS e.g. simultaneous synchronization and demodulation. For example, RS ports used for PDSCH, PUSCH and PDCCH demodulation, for phase noise tracking, for synchronization and for CSI measurement and reporting are defined according to Table 600 shown in FIGURE 13 and Table 700 shown in FIGURE 14. ^ Note that a port may be used for one or multiple of these purposes simultaneously, depending on configuration (for DL) or network side preference (UL) ^ Primary RS pattern is dense in frequency and sparse in time ^ Both High-frequency density and low-frequency density patterns are configured (HD,LD) per OFDM symbol (i.e. time varying frequency density) ^ The primary RS pattern may be configured to have an unequal distribution in time, for example ^^ _^ ¹ _^ = {3,6,15,24} symbols relative to the first DMRS ^ Secondary RS pattern can configured and is sparse in frequency and dense in time ^ Secondary RS pattern may only be present for some DMRS ports in case of a rank>1 transmission (as indicated by the antenna port indication table) ^ Secondary RS pattern for a given subcarrier repeatedly use the sequence sample of the first occasion in time of the primary pattern (before application of the FD-OCC/TD-OCC), for the scheduled PxxCH duration. ^ Port 0 is used for Msg A DMRS and is double symbol RS every 8^th symbol using all subcarriers ^ Setting of additional parameters for these RS ports ^ Time domain shift ∆ _^^= 0 ^ Time occasions for primary RS (symbols) ^̅^ _^ ¹ _^ = { ^^₁, ^^₂, ^^₃, ^^₄} ^ Default {3,6,15,24} (?) ^ Time periodicity for secondary RS (symbols) ^^ _^ ² _^ = {1,2,4} ^ Default ^^ _^ ² _^ = 2 (?) ^ Enabling of secondary pattern (DCI indication) RS ports in Table 700 shown in FIGURE 14 are used for PDSCH, PUSCH and PDCCH demodulation, for possible simultaneous phase noise tracking, for synchronization and for CSI measurement and reporting ^ Note that a port may be used for one or multiple of these purposes simultaneously, depending on configuration (for DL) or network side preference (UL) ^ Port 0 is used for Msg A DMRS and is double symbol RS every 8^th symbol using all subcarriers ^ Setting of additional parameters for these RS ports ^ Time domain shift ∆ _^^= 0 ^ Time occasions for RS (symbols) ^̅^ _^ ¹ _^ = { ^^₁, ^^₂, ^^₃, ^^₄} ^ Default ^{3,6,15,24^} CSI-RS Ports for CSI Measurement Usage CSI-RS ports are using the defined scalable and extendable RS framework. These are used when the only purpose and usage of the RS is for CSI reporting. They are defined according to the Table 800 of FIGURE 15 and Table 900 of FIGURE 16. a. Time periodicity ^^ _^ ^{^} _^ ^{^} = {0, … } configured i. ^^ _^ ^{^} _^ ^{^}=0 default and implies aperiodic CSI-RS b. 1-4 ports using Port 101-104 is in 1 symbol using comb-2 c. 8 port using Port 105-112 is in 1 symbol using comb-4 d. 16 port using Port 113-128 is in 2 symbol using comb-8 and TD-OCC, no FD-OCC e. 32 port using Port 129-160 is in 4 symbols using comb-8 and TD-OCC, no FD- OCC f. 64 port using Port 161-224 is in 8 symbols using comb-8 and TD-OCC, no FD- OCC SRS Ports for SRS measurement Usage SRS ports are using the defined scalable and extendable RS framework. These are used when the only purpose and usage of the RS is for SRS measurements (and not uplink sync or demodulation). They are defined according to Table 1000 shown in FIGURE 17 as follows: a. Time periodicity ^^ _^ ^{^} _^ ^{^} = {0, … } can be configured using RRC i. Default ^^ _^ ^{^} _^ ^{^}=0 implies an aperiodic SRS b. 1-4 ports using Port 501-504 is in 1 symbol using comb-2 c. 1-8 ports using Port 505-512 is in 1 symbol using comb-4 FIGURE 18 shows an example of a communication system 1100 in accordance with some embodiments. In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1112 and/or with other network nodes or equipment in the telecommunication network 1102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1102. In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF). The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system 1100 of FIGURE 18 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. In some examples, the UEs 1112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC). In the example, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and/or 1112d) and network nodes (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. The hub 1114 may have a constant/persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and/or schedule between the hub 1114 and UEs (e.g., UE 1112c and/or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and/or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. FIGURE 19 shows a UE 1200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 19. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc. The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs). In the example, the input/output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device. In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and/or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied. The memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems. The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1210 may allow the UE 1200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium. The processing circuitry 1202 may be configured to communicate with an access network or other network using the communication interface 1212. The communication interface 1212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1222. The communication interface 1212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1218 and/or a receiver 1220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1218 and receiver 1220 may be coupled to one or more antennas (e.g., antenna 1222) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient). As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item- tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1200 shown in FIGURE 19. As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. FIGURE 20 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). The network node 1300 includes a processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308. The network node 1300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 1300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300. The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1300 components, such as the memory 1304, to provide network node 1300 functionality. In some embodiments, the processing circuitry 1302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1302 includes one or more of radio frequency (RF) transceiver circuitry 1312 and baseband processing circuitry 1314. In some embodiments, the radio frequency (RF) transceiver circuitry 1312 and the baseband processing circuitry 1314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1312 and baseband processing circuitry 1314 may be on the same chip or set of chips, boards, or units. The memory 1304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1302. The memory 1304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1302 and utilized by the network node 1300. The memory 1304 may be used to store any calculations made by the processing circuitry 1302 and/or any data received via the communication interface 1306. In some embodiments, the processing circuitry 1302 and memory 1304 is integrated. The communication interface 1306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front- end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and/or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front- end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown). The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port. The antenna 1310, communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment. The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail. Embodiments of the network node 1300 may include additional components beyond those shown in FIGURE 20 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300. FIGURE 21 is a block diagram of a host 1400, which may be an embodiment of the host 1116 of FIGURE 18, in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1400 may provide one or more services to one or more UEs. The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a network interface 1408, a power source 1410, and a memory 1412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of host 1400. The memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Embodiments of the host 1400 may utilize only a subset or all of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. FIGURE 22 is a block diagram illustrating a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. Applications 1502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1500 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Hardware 1504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508. The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, a VM 1508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502. Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units. FIGURE 23 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1112a of FIGURE 18 and/or UE 1200 of FIGURE 19), network node (such as network node 1110a of FIGURE 18 and/or network node 1300 of FIGURE 20), and host (such as host 1116 of FIGURE 18 and/or host 1400 of FIGURE 13) discussed in the preceding paragraphs will now be described with reference to FIGURE 23. Like host 1400, embodiments of host 1602 include hardware, such as a communication interface, processing circuitry, and memory. The host 1602 also includes software, which is stored in or accessible by the host 1602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and host 1602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1650. The network node 1604 includes hardware enabling it to communicate with the host 1602 and UE 1606. The connection 1660 may be direct or pass through a core network (like core network 1106 of FIGURE 18) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. The UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602. In the host 1602, an executing host application may communicate with the executing client application via the OTT connection 1650 terminating at the UE 1606 and host 1602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1650. The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606. The connection 1660 and wireless connection 1670, over which the OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices. As an example of transmitting data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data towards the UE 1606. The host 1602 may initiate the transmission responsive to a request transmitted by the UE 1606. The request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606. The transmission may pass via the network node 1604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602. In some examples, the UE 1606 executes a client application which provides user data to the host 1602. The user data may be provided in reaction or response to the data received from the host 1602. Accordingly, in step 1616, the UE 1606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1606. Regardless of the specific manner in which the user data was provided, the UE 1606 initiates, in step 1618, transmission of the user data towards the host 1602 via the network node 1604. In step 1620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1604 receives user data from the UE 1606 and initiates transmission of the received user data towards the host 1602. In step 1622, the host 1602 receives the user data carried in the transmission initiated by the UE 1606. One or more of the various embodiments improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of, for example, data rate, latency, and/or power consumption and, thereby, provide benefits such as, for example, reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime. In an example scenario, factory status information may be collected and analyzed by the host 1602. As another example, the host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1602 may store surveillance video uploaded by a UE. As another example, the host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1650 between the host 1602 and UE 1606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and/or UE 1606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1650 while monitoring propagation times, errors, etc. FIGURE 24 illustrates an example method 1700 by a UE 1112 for extending RS patterns, according to certain embodiments. In the illustrated embodiment, the method includes a receiving step at 17702, a generating step at 1704, and a using step at 1706. For example, at step 1702, the UE may receive, from a network node, information for identifying a primary RS pattern and at least one secondary RS pattern. At step 1704, for example, the UE may generate an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern. At step 1706, for example, the UE may use the extended RS pattern to perform at least one operation associated with a RS. FIGURE 25 illustrates an example method 1800 by a UE 1112 for determining a RS usage, according to certain embodiments. In the illustrated embodiment, the method includes a receiving step at 1802. For example, at step 1802, the UE may receive, from a network node, information indicating: at least one scheduled resource associated with a RS to be received or transmitted by the UE, and at least one value for at least one parameter indicating a usage of a RS pattern by the UE for receiving or transmitting the RS. FIGURE 26 illustrates a method 1900 by a UE 1112 for extending RS patterns, according to certain embodiments. The method begins at step 1902 when the UE 1112 receives, from a network node 1110, information for identifying a primary RS pattern and at least one secondary RS pattern. At step 1904, the UE 1112 generates an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern. At step 1906, the UE 1112 uses the extended RS pattern to perform at least one operation associated with a RS. In a particular embodiment, at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern include a mapping of reference signals to resource element grid in an Orthogonal Frequency Division Multiplexing system. In a particular embodiment, the information indicates an entry in a combination table. When identifying the primary RS pattern and the at least one secondary RS pattern, the UE determines an entry of a primary table and an entry of the at least one secondary table based on the entry in the combination table. In a further particular embodiment, each one of the primary table and the at least one secondary table are separate tables. In a further particular embodiment, the primary table and the at least one secondary tables are different rows in a same table. In a particular embodiment, the primary RS pattern is denser in frequency and sparser in time, and/or the at least one secondary RS pattern is sparser in frequency and denser in time. In a particular embodiment, the RS is transmitted or received by the UE on a plurality of ports, and each one of the plurality of ports are associated with the primary RS pattern. Only a subset of the plurality of ports are associated with the at least one secondary RS pattern. In a particular embodiment, the UE 1112 determines that the primary RS pattern and the at least one secondary RS pattern map to a same resource element. Based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, the UE 1112 performs at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element. In a particular embodiment, when using the extended RS pattern to perform the at least one operation associated with the RS, the UE 1112 performs at least one of: receiving the RS from the network node on a PDSCH, receiving the RS from the network node on a PDCCH, transmitting the RS to the network node on a PUSCH, performing at least one measurement associated with the RS; performing demodulation of the RS; performing synchronization; and performing phase noise tracking. In a particular embodiment, when generating the extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern, the UE 1112 combines the primary RS pattern and the at least one secondary RS pattern to generate the extended RS pattern. In a particular embodiment, the UE 1112 obtains at least one value for at least one parameter associated with the extended RS pattern. The at least one value for the at least one parameter indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS. Additionally or alternatively, the at least one value for the at least one parameter indicates and/or is associated with the at least one operation performed using the extended RS pattern. In a further particular embodiment, the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^^ _^^; a value associated with a time domain shift, ∆ _^^, relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed. In a particular embodiment, the UE 1112 obtains the at least one parameter by receiving the at least one parameter indicating the usage of the extended RS pattern from the network node 1110. The method further includes the UE 1112 receiving, from the network node 1110, information comprising at least one scheduled resource associated with a RS to be received or transmitted by the UE 1112. In a further particular embodiment, the RS is a DMRS received by the UE 1112 and/or the usage of the RS pattern is demodulation by the UE 1112. Additionally or alternatively, the UE 1112 uses the RS pattern to perform demodulation of the DMRS. In a further particular embodiment, the RS is a SRS transmitted by the UE 1112 to the network node 1110, and/or the usage of the RS pattern is at least one measurement performed by the network node 1110. The UE 1112 receives, from the network node 1110, a measurement report comprising at least one value associated with the at least one measurement performed on the SRS by the network node. In a further particular embodiment, the RS is a CSI-RS, and/or the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE 1112. The UE 1112 uses the RS pattern to perform the at least one measurement on the CSI-RS and transmits a measurement report to the network node. The measurement report includes at least one value associated with the at least one measurement performed on the CSI-RS. In a further particular embodiment, the RS is a PTRS, and/or the usage of the RS pattern is phase noise tracking performed by the UE 1112. The UE 1112 uses the RS pattern to perform phase noise tracking based on the PTRS. In a further particular embodiment, the RS is a Tracking Reference Signal, TRS, and/or the usage of the RS pattern is downlink synchronization performed by the UE based on the TRS. The UE 1112 uses the RS pattern to perform the downlink synchronization based on the TRS. In a particular embodiment, the information further indicates that the RS to be received or transmitted by the UE 1112 includes no data. The UE 1112 determines that the RS is not intended for demodulation based on the RS including no data and/or uses the RS pattern for synchronization. FIGURE 27 illustrates an example method 2000 by a network node 1110 for extending RS patterns, according to certain embodiments. In the illustrated embodiment, the method includes a transmitting step at 2002. For example, at step 2002, the network node 1110 may transmit, to a UE 1112, information for identifying a primary RS pattern and at least one secondary RS pattern. The UE 1110 is configured to generate an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern and use the extended RS pattern to perform at least one operation associated with a RS. FIGURE 28 illustrates an example method 2100 by a network node 1110 for indicating a RS usage, according to certain embodiments. In the illustrated embodiment, the method includes a determining step at 2102 and a transmitting step at 2104. For example, at step 2102, the network node 1110 may determine, for at least one scheduled resource associated with a RS, a usage of a RS and/or a RS pattern by the UE 1112. At step 2104, for example, the network node 1110 may transmit information to the UE 1112. The information includes: the at least one scheduled resource associated with the RS to be received or transmitted by the UE 1112, and at least one value for at least one parameter indicating the usage of the RS pattern by the UE 1112. FIGURE 29 illustrates a method 2200 by a network node 1110 for extending RS patterns, according to certain embodiments. The method begins at step 2202 when the UE 1112 transmits, to a UE 1112, information for generating an extended RS pattern based on a primary RS pattern and at least one secondary RS pattern. Based on the extended RS pattern, the network node 1110 receives a RS from the UE 1112 or transmits the RS to the UE 1112, at step 2204. In a particular embodiment, at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern comprise a mapping of reference signals to resource element grid in an OFDM system. In a particular embodiment, the information indicates an entry in a combination table, an entry of a primary table is identified based on the entry in the combination table, and an entry of at least one secondary table is identified based on the entry in the combination table. In a further particular embodiment, each one of the primary table and the at least one secondary table are separate tables. In a further particular embodiment, the primary table and the at least one secondary tables are different rows in a same table. In a particular embodiment, the primary RS pattern is denser in frequency and sparser in time, and the at least one secondary RS pattern is sparser in frequency and denser in time. In a particular embodiment, the RS is transmitted or received by the UE 1112 on a plurality of ports, and each one of the plurality of ports are associated with the primary RS pattern. Only a subset of the plurality of ports are associated with the at least one secondary RS pattern. In a particular embodiment, the primary RS pattern and the at least one secondary RS pattern map to a same resource element. The UE 1112 is configured, based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, to perform at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element. In a particular embodiment, the network node 1110 transmits the RS to the UE on a PDSCH and/or PDCCH. Additionally or alternatively, the network node 1110 receives the RS from the UE 1112 on a PUSCH. In a particular embodiment, the information transmitted to the UE 1112 includes at least one value for at least one parameter associated with the extended RS pattern. The at least one value for at least one parameter associated with the extended RS pattern indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS. Additionally or alternatively, the at least one value for at least one parameter associated with the extended RS pattern indicates and/or is associated with the at least one operation performed by the UE using the extended RS pattern. In a further particular embodiment, the at least one value for the at least one parameter includes at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^^ _^^; a value associated with a time domain ∆ _^^, relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed. In a particular embodiment, the network node 1110 determines, for the at least one scheduled resource associated with the RS, the usage of the RS and/or the RS pattern by the UE 1112. In a particular embodiment, the RS is a Demodulation Reference Signal, DMRS, to be received by the UE, and/or the usage of the RS pattern is demodulation by the UE. In a particular embodiment, the RS is a Sounding Reference Signal, SRS, transmitted by the UE to the network node, and/or the usage of the RS pattern is at least one measurement performed by the network node. The method includes the network node 1110 receiving the SRS from the UE 1112, performing the at least one measurement on the SRS, and transmitting a measurement report to the UE that includes at least one value associated with the at least one measurement performed on the SRS by the network node. In a particular embodiment, the RS is a CSI-RS, and/or the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE. Additionally or alternatively, the network node 1110 receives, from the UE 1112, a measurement report comprising at least one value associated with the at least one measurement performed on the CSI-RS. In a particular embodiment, the RS is a PTRS, and the usage of the RS pattern is phase noise tracking performed by the UE 1112. In a particular embodiment, the RS is a TRS, and the usage of the RS pattern is downlink synchronization performed by the UE 1112 based on the TRS. In a particular embodiment, the information further indicates that the RS to be received from the UE 1112 or transmitted to the UE 1112 includes no data. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally. EXAMPLE EMBODIMENTS Group A Example Embodiments Example Embodiment A1. A method by a user equipment for utilizing dynamic density Reference Signal (RS) patterns, the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above. Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node. Group B Example Embodiments Example Embodiment B1. A method performed by a network node for utilizing dynamic density Reference Signal (RS) patterns, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above. Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above. Example Embodiment B3. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group C Example Embodiments Example Embodiment C1. A method by a UE for extending RS patterns, the method comprising: receiving, from a network node, information for identifying a primary RS pattern and at least one secondary RS pattern; generating an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern; and using the extended RS pattern to perform at least one operation associated with a RS. Example Embodiment C2. The method of Example Embodiment C1, wherein the information is received via DCI. Example Embodiment C3. The method of any one of Example Embodiments C1 to C2, wherein at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern comprise a mapping of reference signals to resource element grid in an OFDM system. Example Embodiment C4. The method of any one of Example Embodiments C1 to C3, wherein the information indicates an entry in a combination table, and the method comprises: based on the entry in the combination table, identifying the primary RS pattern and the at least one secondary RS pattern. Example Embodiment C5. The method of Example Embodiment C4, wherein identifying the primary RS pattern and the at least one secondary RS pattern comprises: based on the entry in the combination table, determining an entry of a primary table; and based on the entry in the combination table, determining an entry of the at least one secondary table. Example Embodiment C6. The method of Example Embodiment C5, wherein each one of the primary table and the at least one secondary table are separate tables. Example Embodiment C7. The method of Example Embodiment C5, wherein the primary table and the at least one secondary tables are different rows in a same table. Example Embodiment C8. The method of any one of Example Embodiments C1 to C7, wherein: the primary RS pattern is denser in frequency and sparser in time, and the at least one secondary RS pattern is sparser in frequency and denser in time. Example Embodiment C9. The method of any one of Example Embodiments C1 to C8, wherein the RS is transmitted or received by the UE on a plurality of ports, and wherein each one of the plurality of ports are associated with the primary RS pattern and wherein only a subset of the plurality of ports are associated with the at least one secondary RS pattern. Example Embodiment C10. The method of any one of Example Embodiments C1 to C9, comprising: determining that the primary RS pattern and the at least one secondary RS pattern map to a same resource element; and based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, performing at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element. Example Embodiment C11. The method of any one of Example Embodiments C1 to C10, wherein using the extended RS pattern to perform the at least one operation associated with the RS comprises at least one of: receiving the RS from the network node on a PDSCH; receiving the RS from the network node on a PDCCH; transmitting the RS to the network node on a PUSCH; performing at least one measurement associated with the RS; performing demodulation of the RS; performing synchronization; and performing phase noise tracking. Example Emboidment C12. The method of any one of Example Embodiments C1 to C11, comprising determining at least one value for at least one parameter associated with the extended RS pattern, wherein the at least one value for the at least one parameter indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS. Example Embodiment C13. The method of any one of Example Embodiments C1 to C11, comprising determining at least one value for at least one parameter associated with the extended RS pattern, wherein the at least one value for the at least one parameter indicates and/or is associated with the at least one operation performed using the extended RS pattern. Example Embodiment C14. The method of any one of Example Embodiments C12 to C13, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^̅^ _^^ ; a value associated with a time shift, ∆ , _^^ relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed . Example Embodiment C15. The method of any one of Example Embodiments C1 to C14, wherein the RS comprises at least one of: a DMRS, a SRS, a CSI-RS, a PTRS, and a TRS. Example Embodiment C16. The method of any one of Example Embodiments C1 to C15, wherein generating the extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern comprises: combining the primary RS pattern and the at least one secondary RS pattern to generate the extended RS pattern. Example Embodiment C17. The method of Example Embodiments C1 to C16, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Example Embodiment C18. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C17. Example Embodiment C19. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C17. Example Embodiment C20. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C17. Example Embodiment C21. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C17. Example Embodiment C22. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments C1 to C17. Group D Example Embodiments Example Embodiment D1. A method by a UE for determining a RS usage, the method comprising: receiving, from a network node, information comprising: at least one scheduled resource associated with a RS to be received or transmitted by the UE, and at least one value for at least one parameter indicating a usage of a RS pattern by the UE for receiving or transmitting the RS. Example Embodiment D2. The method of Example Embodiment D1, wherein the at least one scheduled resource is for receiving the RS by the UE on a PDSCH or a PDCCH. Example Embodiment D3. The method of Example Embodiment D1, wherein the at least one scheduled resource is for transmitting the RS by the UE on a PUSCH. Example Embodiment D4. The method of any one of Example Embodiments D1 to D3, comprising: based on the at least one value for the at least one parameter, determining the usage of the RS pattern. Example Embodiment D5. The method of any one of Example Embodiments D1 to D4, comprising: based on the usage indicated by the at least one value for the at least one parameter, using the RS pattern. Example Embodiment D6. The method of any one of Example Embodiments D1 to D5, wherein at least one of: the RS is a DMRS received by the UE, and the usage of the RS pattern is demodulation by the UE. Example Embodiment D7. The method of Example Embodiment D6, further comprising: using the RS pattern to perform demodulation of the DMRS. Example Embodiment D8. The method of any one of Example Embodiments D1 to D5, wherein at least one of: the RS is a SRS transmitted by the UE to the network node, and the usage of the RS pattern is at least one measurement performed by the network node. Example Embodiment D9. The method of Example Embodiment D8, further comprising: receiving, from the network node, a measurement report comprising at least one value associated with the at least one measurement performed on the SRS by the network node. Example Embodiment D10. The method of any one of Example Embodiments D1 to D5, wherein at least one of: the RS is a CSI-RS, and the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE. Example Embodiment D11. The method of Example Embodiment D10, further comprising: using the RS pattern to perform the at least one measurement on the CSI-RS, and transmitting a measurement report to the network node, the measurement report comprising at least one value associated with the at least one measurement performed on the CSI-RS. Example Embodiment D12. The method of any one of Example Embodiments D1 to D5, wherein at least one of: the RS is a PTRS, and the usage of the RS pattern is phase noise tracking performed by the UE. Example Embodiment D13. The method of Example Embodiment D12, further comprising: using the RS pattern to perform phase noise tracking based on the PTRS. Example Embodiment D14. The method of any one of Example Embodiments D1 to D5, wherein at least one of: the RS is a TRS, and the usage of the RS pattern is downlink synchronization performed by the UE based on the TRS. Example Embodiment D15. The method of Example Embodiment D14, further comprising: using the RS pattern to perform the downlink synchronization based on the TRS. Example Embodiment D16. The method of any one of Example Embodiments D1 to D15, wherein the information further indicates that the RS to be received or transmitted by the UE includes no data (i.e., payload is zero), and the method further comprises at least one of: determining that the RS is not intended for demodulation based on the RS including no data, and using the RS pattern for synchronization. Example Embodiment D17. The method any one of Example Embodiments D1 to D16, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^̅^ _^^ ; a value associated with a time domain shift, ∆ _^^ , relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed. Example Embodiment D18. The method of any one of Example Embodiments D1 to D17, wherein the information comprises a scheduling assignment received via DCI. Example Embodiment D19. The method of Example Embodiments D1 to D18, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Example Embodiment D20. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D19. Example Embodiment D21. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D19. Example Embodiment D22. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D19. Example Embodiment D23. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D19. Example Embodiment D24. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D19. Group E Example Embodiments Example Embodiment E1. A method by a network node for extending RS patterns, the method comprising: transmitting, to a UE, information for identifying a primary RS pattern and at least one secondary RS pattern, wherein the UE is configured to generate an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern and use the extended RS pattern to perform at least one operation associated with a RS. Example Embodiment E2. The method of Example Embodiment E1, wherein the information is transmitted via DCI. Example Embodiment E3. The method of any one of Example Embodiments E1 to E2, wherein at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern comprise a mapping of reference signals to resource element grid in an OFDM system. Example Embodiment E4. The method of any one of Example Embodiments E1 to E3, wherein the information indicates an entry in a combination table, and the primary RS pattern and the at least one secondary RS pattern are identified based on the entry in the combination table. Example Embodiment E5. The method of Example Embodiment E4, wherein: an entry of the primary table is identified based on the entry in the combination table; and an entry of the at least one secondary table is identified based on the entry in the combination table. Example Embodiment E6. The method of Example Embodiment E5, wherein each one of the primary table and the at least one secondary table are separate tables. Example Embodiment E7. The method of Example Embodiment E5, wherein the primary table and the at least one secondary tables are different rows in a same table. Example Embodiment E8. The method of any one of Example Embodiments E1 to E7, wherein: the primary RS pattern is denser in frequency and sparser in time, and the at least one secondary RS pattern is sparser in frequency and denser in time. Example Embodiment E9. The method of any one of Example Embodiments E1 to E8, wherein the RS is transmitted or received by the UE on a plurality of ports, and wherein each one of the plurality of ports are associated with the primary RS pattern and wherein only a subset of the plurality of ports are associated with the at least one secondary RS pattern. Example Embodiment E10. The method of any one of Example Embodiments E1 to E9, wherein: the primary RS pattern and the at least one secondary RS pattern map to a same resource element; and the UE is configured, based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, to perform at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element. Example Embodiment E11. The method of any one of Example Embodiments E1 to E10, comprising at least one of: transmitting the RS to the UE on a PDSCH; transmitting the RS to the UE on a PDCCH; and receiving the RS from the UE on a PUSCH. Example Embodiment E12. The method of any one of Example Embodiments E1 to E11, wherein at least one value for at least one parameter associated with the extended RS pattern indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS. Example Embodiment E13. The method of any one of Example Embodiments E1 to E11, wherein at least one value for at least one parameter associated with the extended RS pattern indicates and/or is associated with the at least one operation performed by the UE using the extended RS pattern. Example Embodiment E14. The method of any one of Example Embodiments E12 to E13, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^̅^ _^^ ; a value associated with a time shift, ∆ _^^ , relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed . Example Embodiment E15. The method of any one of Example Embodiments E1 to E14, wherein the RS comprises at least one of: a DMRS, a SRS, a CSI-RS, a PTRS, and a TRS. Example Embodiment E16. The method of any one of Example Embodiments E1 to E15, wherein configuring the UE to generate the extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern comprises: configuring the UE to combine the primary RS pattern and the at least one secondary RS pattern to generate the extended RS pattern. Example Embodiment E17. The method of any one of Example Embodiments E1 to E16, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Example Embodiment E18. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments E1 to E17. Example Embodiment E19. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments E1 to E17. Example Embodiment E20. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments E1 to E17. Example Embodiment E21. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments E1 to E17. Group F Example Embodiments Example Embodiment F1. A method by a network node for indicating a RS usage, the method comprising: determining, for at least one scheduled resource associated with a RS, a usage of a RS and/or a RS pattern by a UE; and transmitting, to the UE, information comprising: the at least one scheduled resource associated with the RS to be received or transmitted by the UE; and at least one value for at least one parameter indicating the usage of the RS pattern by the UE. Example Embodiment F2. The method of Example Embodiment F1, wherein the at least one scheduled resource is for receiving the RS by the UE on a PDSCH or PDCCH. Example Embodiment F3. The method of Example Embodiment F1, wherein the at least one scheduled resource is for transmitting the RS by the UE on a PUSCH. Example Embodiment F4. The method of any one of Example Embodiments F1 to F3, wherein at least one of: the RS is a DMRS to be received by the UE, and the usage of the RS pattern is demodulation by the UE. Example Embodiment F5. The method of Example Embodiment F4, further comprising: configuring the UE to use and/or adapt the RS pattern to perform demodulation of the DMRS. Example Embodiment F6. The method of any one of Example Embodiments F1 to F3, wherein at least one of: the RS is a SRS transmitted by the UE to the network node, and the usage of the RS pattern is at least one measurement performed by the network node. Example Embodiment F7. The method of Example Embodiment F6, further comprising at least one of: receiving the SRS from the UE; performing the at least one measurement on the SRS; and transmitting, to the UE, a measurement report comprising at least one value associated with the at least one measurement performed on the SRS by the network node. Example Embodiment F8. The method of any one of Example Embodiments F1 to F3, wherein at least one of: the RS is a CSI-RS, and the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE. Example Embodiment F9. The method of Example Embodiment F8, further comprising: configuring the UE to use and/or adapt the RS pattern to perform the at least one measurement on the CSI-RS, and receiving, from the UE, a measurement report comprising at least one value associated with the at least one measurement performed on the CSI-RS. Example Embodiment F10. The method of any one of Example Embodiments F1 to F3, wherein at least one of: the RS is a PTRS, and the usage of the RS pattern is phase noise tracking performed by the UE. Example Embodiment F11. The method of Example Embodiment F10, further comprising: configuring the UE to use and/or adapt the RS pattern to perform phase noise tracking based on the PTRS. Example Embodiment F12. The method of any one of Example Embodiments F1 to F3, wherein at least one of: the RS is a TRS, and the usage of the RS pattern is downlink synchronization performed by the UE based on the TRS. Example Embodiment F13. The method of Example Embodiment F12, further comprising: configuring the UE to use and/or adapt the RS pattern to perform the downlink synchronization based on the TRS. Example Embodiment F14. The method of any one of Example Embodiments F1 to F13, wherein the information further indicates that the RS to be received or transmitted by the UE includes no data (i.e., payload is zero), and the method further comprises at least one of: configuring the UE to determine that the RS is not intended for demodulation based on the RS including no data, and configuring the UE to use and/or adapt the RS pattern for performing synchronization. Example Embodiment F15. The method any one of Example Embodiments F1 to F14, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain occasion, ^̅^ _^^ ; a value associated with a time shift, ∆ _^^ , relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed . Example Embodiment F16. The method of any one of Example Embodiments F1 to F15, wherein the information comprises a scheduling assignment transmitted via downlink control information, DCI. Example Embodiment F17. The method of any one of Example Embodiments F1 to F16, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Example Embodiment F18. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments F1 to F17. Example Embodiment F19. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments F1 to F17. Example Embodiment F20. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments F1 to F17. Example Embodiment F21. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments F1 to F17. Group G Example Embodiments Example Embodiment G1. A user equipment (UE) for extending Reference Signal (RS) for measurements for a downlink RS transmission, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group A, C, and D Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry. Example Embodiment G2. A network node for extending Reference Signal (RS) for measurements for a downlink RS transmission, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, E, and F Example Embodiments; power supply circuitry configured to supply power to the processing circuitry. Example Embodiment G3. A user equipment (UE) for extending Reference Signal (RS) for measurements for a downlink RS transmission, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE. Example Embodiment G4. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments to receive the user data from the host. Example Embodiment G5. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host. Example Embodiment G6. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. Example Embodiment G7. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A, C, and D Example Embodiments to receive the user data from the host. Example Emboidment G8. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. Example Embodiment G9. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. Example Emboidment G10. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A, C, and D Example Embodiments to transmit the user data to the host. Example Emboidment G11. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host. Example Embodiment G12. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. Example Embodiment G13. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A, C, and D Example Embodiments to transmit the user data to the host. Example Embodiment G14. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. Example Embodiment G15. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. Example Embodiment G16. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, D, and F Example Embodiments to transmit the user data from the host to the UE. Example Embodiment G17. The host of the previous Example Embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. Example Embodiment G18. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B, E, and F Example Embodiments to transmit the user data from the host to the UE. Example Embodiment G19. The method of the previous Example Embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE. Example Emboidment G20. The method of any of the previous 2 Example Embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. Example Embodiment G21. A communication system configured to provide an over-the- top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, E, and F Example Embodiments to transmit the user data from the host to the UE. Example Embodiment G22. The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment. Example Embodiment G23. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B, E, and F Example Embodiments to receive the user data from a user equipment (UE) for the host. Example Embodiment G24. The host of the previous 2 Example Embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application. Example Embodiment G25. The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data. Example Embodiment G26. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B, E, and F Example Embodiments to receive the user data from the UE for the host. Example Embodiment G27. The method of the previous Example Embodiment, further comprising at the network node, transmitting the received user data to the host.

Claims

CLAIMS 1. A method (1900) by a user equipment, UE (1112), for extending Reference Signal, RS, patterns, the method comprising: receiving (1902), from a network node (1110), information for identifying a primary RS pattern and at least one secondary RS pattern; generating (1904) an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern; and using (1906) the extended RS pattern to perform at least one operation associated with a RS.

2. The method of Claim 1, wherein at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern comprise a mapping of reference signals to resource element grid in an Orthogonal Frequency Division Multiplexing system.

3. The method of any one of Claims 1 to 2, wherein the information indicates an entry in a combination table, and wherein identifying the primary RS pattern and the at least one secondary RS pattern comprises: based on the entry in the combination table, determining an entry of a primary table; and based on the entry in the combination table, determining an entry of the at least one secondary table.

4. The method of Claim 3, wherein each one of the primary table and the at least one secondary table are separate tables.

5. The method of Claim 3, wherein the primary table and the at least one secondary tables are different rows in a same table.

6. The method of any one of Claims 1 to 5, wherein: the primary RS pattern is denser in frequency and sparser in time, and the at least one secondary RS pattern is sparser in frequency and denser in time.

7. The method of any one of Claims 1 to 6, wherein the RS is transmitted or received by the UE on a plurality of ports, and wherein each one of the plurality of ports are associated with the primary RS pattern and wherein only a subset of the plurality of ports are associated with the at least one secondary RS pattern.

8. The method of any one of Claims 1 to 7, comprising: determining that the primary RS pattern and the at least one secondary RS pattern map to a same resource element; and based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, performing at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element.

9. The method of any one of Claims 1 to 8, wherein using the extended RS pattern to perform the at least one operation associated with the RS comprises at least one of: receiving the RS from the network node on a Physical Downlink Shared Channel, PDSCH; receiving the RS from the network node on a Physical Downlink Control Channel, PDCCH; transmitting the RS to the network node on a Physical Uplink Shared Channel, PUSCH; performing at least one measurement associated with the RS; performing demodulation of the RS; performing synchronization; and performing phase noise tracking.

10. The method of any one of Claims 1 to 9, wherein generating the extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern comprises: combining the primary RS pattern and the at least one secondary RS pattern to generate the extended RS pattern.

11. The method of any one of Claims 1 to 10, comprising obtaining at least one value for at least one parameter associated with the extended RS pattern, wherein: the at least one value for the at least one parameter indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS, and/or the at least one value for the at least one parameter indicates and/or is associated with the at least one operation performed using the extended RS pattern.

12. The method of Claim 11, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain ^̅^ _^^; a value associated with a time domain shift, ∆ _^^, relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed .

13. The method of any one of Claims 11 to 12, wherein obtaining the at least one parameter comprises receiving the at least one parameter indicating the usage of the extended RS pattern from the network node, and the method further comprises receiving, from the network node, information comprising at least one scheduled resource associated with a RS to be received or transmitted by the UE.

14. The method of any one of Claims 11 to 13, wherein: at least one of: the RS is a Demodulation Reference Signal, DMRS, received by the UE, and the usage of the RS pattern is demodulation by the UE, and the method comprises using the RS pattern to perform demodulation of the DMRS.

15. The method of any one of Claims 11 to 13, wherein: at least one of: the RS is a Sounding Reference Signal, SRS, transmitted by the UE to the network node, and the usage of the RS pattern is at least one measurement performed by the network node, and the method comprises receiving, from the network node, a measurement report comprising at least one value associated with the at least one measurement performed on the SRS by the network node.

16. The method of any one of Claims 11 to 13, wherein: at least one of: the RS is a Channel State Information-Reference Signal, CSI-RS, and the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE, and the method comprises: using the RS pattern to perform the at least one measurement on the CSI-RS, and transmitting a measurement report to the network node, the measurement report comprising at least one value associated with the at least one measurement performed on the CSI- RS.

17. The method of any one of Claims 11 to 13, wherein: at least one of: the RS is a Phase Tracking Reference Signal, PTRS, and the usage of the RS pattern is phase noise tracking performed by the UE, and the method comprises using the RS pattern to perform phase noise tracking based on the PTRS.

18. The method of any one of Claims 11 to 13, wherein: at least one of: the RS is a Tracking Reference Signal, TRS, and the usage of the RS pattern is downlink synchronization performed by the UE based on the TRS, and the method comprises using the RS pattern to perform the downlink synchronization based on the TRS.

19. The method of any one of Claims 1 to 18, wherein the information further indicates that the RS to be received or transmitted by the UE includes no data, and the method further comprises at least one of: determining that the RS is not intended for demodulation based on the RS including no data, and using the RS pattern for synchronization.

20. A method (2200) by a network node (1110) for extending Reference Signal, RS patterns, the method comprising: transmitting (2202), to a user equipment, UE (1112), information for generating an extended RS pattern based on a primary RS pattern and at least one secondary RS pattern; and based on the extended RS pattern, receiving (2204) a RS from the UE or transmitting the RS to the UE.

21. The method of Claim 20, wherein at least one of the primary RS pattern, the at least one secondary RS pattern, and the extended RS pattern comprise a mapping of reference signals to resource element grid in an Orthogonal Frequency Division Multiplexing system.

22. The method of any one of Claims 20 to 21, wherein: the information indicates an entry in a combination table, an entry of a primary table is identified based on the entry in the combination table; and an entry of at least one secondary table is identified based on the entry in the combination table.

23. The method of Claim 22, wherein each one of the primary table and the at least one secondary table are separate tables.

24. The method of Claim 22, wherein the primary table and the at least one secondary tables are different rows in a same table.

25. The method of any one of Claims 20 to 24, wherein: the primary RS pattern is denser in frequency and sparser in time, and the at least one secondary RS pattern is sparser in frequency and denser in time.

26. The method of any one of Claims 20 to 25, wherein the RS is transmitted or received by the UE on a plurality of ports, and wherein each one of the plurality of ports are associated with the primary RS pattern and wherein only a subset of the plurality of ports are associated with the at least one secondary RS pattern.

27. The method of any one of Claims 20 to 26, wherein: the primary RS pattern and the at least one secondary RS pattern map to a same resource element; and the UE is configured, based on the primary RS pattern and the at least one secondary RS pattern mapping to the same resource element, to perform at least one of: puncturing a secondary sequence associated with the at least one secondary RS pattern; excluding the resource element from a secondary sequence associated with the at least one secondary RS pattern; and using a primary sequence associated the primary RS pattern for the resource element.

28. The method of any one of Claims 20 to 27, comprising at least one of: transmitting the RS to the UE on a Physical Downlink Shared Channel, PDSCH; transmitting the RS to the UE on a Physical Downlink Control Channel, PDCCH; and receiving the RS from the UE on a Physical Uplink Shared Channel, PUSCH.

29. The method of any one of Claims 20 to 28, wherein the information transmitted to the UE comprises at least one value for at least one parameter associated with the extended RS pattern, and wherein: the at least one value for at least one parameter associated with the extended RS pattern indicates a usage of the extended RS pattern by the UE for receiving or transmitting the RS, and/or the at least one value for at least one parameter associated with the extended RS pattern indicates and/or is associated with the at least one operation performed by the UE using the extended RS pattern.

30. The method of Claim 29, wherein the at least one value for the at least one parameter comprises at least one of: a value associated with a frequency domain comb, ^^ _^^; a value associated with a domain shift, ∆ _^^; a value associated with a time domain ^̅^ _^^; a value associated with a time domain ∆ _^^, relative to a reference start symbol; a value associated with FD-OCC, ^^ _^^; a value associated with TD-OCC, ^^ _^^; and a value associated with a RS sequence seed, N_seed .

31. The method of any one of Claims 29 to 30, comprising: determining, for the at least one scheduled resource associated with the RS, the usage of the RS and/or the RS pattern by the user equipment, UE.

32. The method of any one of Claims 29 to 31, wherein at least one of: the RS is a Demodulation Reference Signal, DMRS, to be received by the UE, and the usage of the RS pattern is demodulation by the UE.

33. The method of any one of Claims 29 to 31, wherein: at least one of: the RS is a Sounding Reference Signal, SRS, transmitted by the UE to the network node, and the usage of the RS pattern is at least one measurement performed by the network node, and the method comprises: receiving the SRS from the UE; performing the at least one measurement on the SRS; and transmitting, to the UE, a measurement report comprising at least one value associated with the at least one measurement performed on the SRS by the network node.

34. The method of any one of Claims 29 to 31, wherein: at least one of: the RS is a Channel State Information-Reference Signal, CSI-RS, and the usage of the RS pattern is at least one measurement performed on the CSI-RS by the UE, and the method comprises receiving, from the UE, a measurement report comprising at least one value associated with the at least one measurement performed on the CSI-RS.

35. The method of any one of Claims 29 to 31, wherein at least one of: the RS is a Phase Tracking Reference Signal, PTRS, and the usage of the RS pattern is phase noise tracking performed by the UE.

36. The method of any one of Claims 29 to 31, wherein at least one of: the RS is a Tracking Reference Signal, TRS, and the usage of the RS pattern is downlink synchronization performed by the UE based on the TRS.

37. The method of any one of Claims 20 to 36, wherein the information further indicates that the RS to be received from the UE or transmitted to the UE includes no data.

38. A user equipment, UE (1112), for extending Reference Signal, RS, patterns, the UE configured to: receive, from a network node (1110), information for identifying a primary RS pattern and at least one secondary RS pattern; generate an extended RS pattern based on the primary RS pattern and the at least one secondary RS pattern; and use the extended RS pattern to perform at least one operation associated with a RS.

39. The UE of Claim 38, adapted to perform any of the methods of Claims 2 to 19.

40. A network node (1110) for extending Reference Signal, RS patterns, the network node configured to: transmit, to a user equipment, UE (1112), information for generating an extended RS pattern based on a primary RS pattern and at least one secondary RS pattern; and based on the extended RS pattern, receive a RS from the UE or transmit the RS to the UE.

41. The network node of Claim 40, adapted to perform any of the methods of Claims 21 to 37.