WO2024141991A1 - Systems and methods for dynamic density reference signal patterns - Google Patents
Systems and methods for dynamic density reference signal patternsInfo
- Publication number
- WO2024141991A1 WO2024141991A1 PCT/IB2023/063349 IB2023063349W WO2024141991A1 WO 2024141991 A1 WO2024141991 A1 WO 2024141991A1 IB 2023063349 W IB2023063349 W IB 2023063349W WO 2024141991 A1 WO2024141991 A1 WO 2024141991A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- time
- network node
- density
- pattern
- occasions
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 117
- 230000005540 biological transmission Effects 0.000 claims description 43
- 238000004891 communication Methods 0.000 description 88
- 238000012545 processing Methods 0.000 description 77
- 230000006870 function Effects 0.000 description 37
- 230000015654 memory Effects 0.000 description 36
- 238000013507 mapping Methods 0.000 description 23
- 230000008901 benefit Effects 0.000 description 16
- 238000004590 computer program Methods 0.000 description 13
- 230000001413 cellular effect Effects 0.000 description 12
- 238000005259 measurement Methods 0.000 description 9
- 230000004044 response Effects 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 8
- 238000007726 management method Methods 0.000 description 7
- 238000012544 monitoring process Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 5
- 230000000977 initiatory effect Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 239000000969 carrier Substances 0.000 description 3
- 230000005611 electricity Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000003086 colorant Substances 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012806 monitoring device Methods 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 230000002085 persistent effect Effects 0.000 description 2
- 230000001953 sensory effect Effects 0.000 description 2
- 241001465754 Metazoa Species 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000004378 air conditioning Methods 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000003416 augmentation Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- QVFWZNCVPCJQOP-UHFFFAOYSA-N chloralodol Chemical compound CC(O)(C)CC(C)OC(O)C(Cl)(Cl)Cl QVFWZNCVPCJQOP-UHFFFAOYSA-N 0.000 description 1
- 230000001427 coherent effect Effects 0.000 description 1
- 239000004020 conductor Substances 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000013480 data collection Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000001976 improved effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000010248 power generation Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000004043 responsiveness Effects 0.000 description 1
- 239000000779 smoke Substances 0.000 description 1
- 230000008093 supporting effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 210000003813 thumb Anatomy 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Abstract
A method (1100) by a user equipment, UE (412, 500), is provided for utilizing dynamic density Reference Signal, RS, patterns The method includes receiving (1102), from a network node (410, 600), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. Based on the RS pattern, the UE transmits (1104) the RS to the network node on an uplink channel or receiving the RS from the network node on a downlink channel. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions.
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 1 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 colors and/or 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 DM SR CS H ^^ ^^( ^^′) ^^ ^^( ^^′) ^^(2 ^^ + ^^′)
1 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 wf ( k ^ ) wt( 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 wf ( k ^ ) wt( 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 3rd or 4th 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 wf ^k ^ ^ , wt ^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 wf ( k ^ ) wt( 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) Value Number of DMRS CDM group(s) without DMRS Number of front-load data 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 Value Number of DMRS CDM group(s) without DMRS Number of front-load data 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- t(s) load Value CDM group(s) DMRS p of front- group(s) por ort(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 There currently exist certain challenge(s), however. For example, in NR, the DMRS overhead is the same in all OFDM symbols in the scheduled PDSCH and PUSCH duration which leads to excessive RS overhead. The problem is that after initial channel estimation and possible also synchronization using the first DMRS symbol (in the beginning of the scheduled PDSCH or PUSCH duration) based on DMRS, the RS overhead is often too large, i.e. unnecessarily large for what it is used for (unless the channel is highly time selective).
It is, thus, a problem with excessive DMRS overhead for PDSCH and PUSCH. In NR, the tracking RS (TRS) may be used by the UE to perform synchronization. However, it consumes overhead. Additionally, it makes the use of dynamic point switching complicated since the UE needs to be informed about a new TRS (transmitted from the second TRP) before the UE can be switched to the second TRP. 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 indicating, in scheduled DCI, the RS frequency density for the different RS time occasions of the scheduled PxSCH duration. Thereby, the RS overhead can be adapted to the actual need. According to certain embodiments, a method by a UE is provided for utilizing dynamic density RS patterns. The method includes receiving, from a network node, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. Based on the RS pattern, the UE transmits the RS to the network node on an uplink channel or receiving the RS from the network node on a downlink channel. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. According to certain embodiments, a US for utilizing dynamic density RS patterns is configured to receive, from a network node, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. Based on the RS pattern, the UE is configured to transmits the RS to the network node on an uplink channel or receiving the RS from the network node on a downlink channel. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. According to certain embodiments, a method by a network node is provided for utilizing dynamic density RS patterns. The method includes transmitting, to a UE, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. The plurality of RS time occasions of the RS pattern are associated with an uplink or downlink transmission. Based on the RS pattern, the network node transmits the RS to the UE on an downlink channel or receiving the RS from the UE on an uplink channel. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. According to certain embodiments, a network node for utilizing dynamic density RS patterns is configured to transmit, to a UE, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. The plurality of RS time occasions of the RS pattern are associated with an uplink or downlink transmission. Based
on the RS pattern, the network node is configured to transmit the RS to the UE on an downlink channel or receive the RS from the UE on an uplink channel. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enabling RS density to be dynamically adapted in time and/or frequency within a PxSCH resource. Thus, the RS density may be dynamically adapted to the actual need and use (e.g. normal reception or normal reception+synchronization) of the RS. As another example, certain embodiments may provide a technical advantage of, if FDM between data and DMRS, a OFDM symbol containing low density (LD) DMRS would give the benefit that more RE is available for PxSCH. As still another example, certain embodiments may provide a technical advantage of, if TDM between data and DMRS, even if there is no benefit that more RE is available for PxSCH, there may be a power boosting benefit since power in empty RE can be borrowed to boost the DMRS RE. The power boosting is larger for the LD pattern (comb 4) than the HD pattern (comb- 2). 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 an example DMRS patterns, according to certain embodiments; FIGURE 7 illustrates an example RS pattern, according to certain embodiments; FIGURE 8 illustrates another example RS pattern, according to certain embodiments;
FIGURE 9 illustrates an example communication system, according to certain embodiments; FIGURE 10 illustrates an example UE, according to certain embodiments; FIGURE 11 illustrates an example network node, according to certain embodiments; FIGURE 12 illustrates a block diagram of a host, according to certain embodiments; FIGURE 13 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 14 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments; FIGURE 15 illustrates an example method by a UE for utilizing dynamic density RS patterns, according to certain embodiments; FIGURE 16 illustrates another example method by a UE for utilizing dynamic density RS patterns, according to certain embodiments; FIGURE 17 illustrates an example method by a network node for utilizing dynamic density RS patterns, according to certain embodiments; and FIGURE 18 illustrates another example method by a network node for utilizing dynamic density 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. Herein, the term PxSCH is used to represent PDSCH or PUSCH or PSSCH or any other data-carrying channel. According to certain embodiments described herein, methods and systems are provided that include using the scheduling DCI to indicate the RS frequency density for the different RS time occasions of the scheduled PxSCH duration. Thereby, the RS overhead can be adapted to the actual need. According to certain embodiments, for example, the RS occasions in time is designed so that a burst of dense RS is used in the beginning of a PDSCH duration (to allow for synchronization), while sparser RS is used towards the end of the PDSCH duration. This is useful for systems and carriers/cells without a TRS where the UE must synchronize using DMRS. In addition, the switch between bursty and equidistant DMRS is using DCI, so that an already synchronized UE doesn’t need to use the bursty DMRS and, thereby, the overhead is reduced. Typically the density refers to frequency density since an RS is only present in one OFDM symbol. However, multiple adjacent symbol RS can also be considered in which case density may also refer to time density.
In Table 8, high density (HD) or low density (LD) is indicated by two bits with states 0,1,2,3 which gives different sequences of HD and LD pattern. Each value in the sequency corresponds to a RS time occasion in the scheduled PxSCH duration. HD corresponds, for example, to comb 2, and LD corresponds to comb 4 mapping in frequency domain, in a particular embodiment. Table 8 High-density / Low-density sequence D-Value Sequence 0 HD HD HD HD 1 HD HD LD LD 2 HD LD LD LD 3 LD HD HD LD In this example, it is assumed that a DCI schedules a 14 OFDM symbol long PDSCH where RS is configured to occur in every 6th OFDM symbol. In a particular example embodiment, if the DCI indicates an RS density “2”, then the first DMRS (in the first symbol of the duration) has high density (i.e., comb 2) while the second and third DMRS symbol of the duration has low RS density (i.e., comb 4). In a particular embodiment, the position of the DMRS symbols in time in the scheduled PxSCH duration can be non-equidistant. In a particular embodiment, time occasions for the RS positions within the scheduled PxSCH ^̅^ ^^ = { ^^1, ^^2, ^^3, ^^4} are dynamically indicated (explicitly or implicitly) by DCI to allow for DMRS+TRS functionality (where TRS functionality implies that the DMRS is also used for synchronization, in which case the RS spacing in time is shorter in the beginning of the PxSCH duration, i.e. ^^1, ^^2 is smaller than ^^2, ^^3 spacing for or DMRS only functionality (in this case equally spaced ^^1, ^^2, ^^3, ^^4). A scheduled PxSCH duration may be short and not use all valued ^^1, ^^2, ^^3, ^^4 but only the first few ones, e.g., ^^1, ^^2, since the remaining ones are outside the scheduled duration. FIGURE 6 illustrates example DMRS patterns 100, according to certain embodiments. Specifically, the left side of FIGURE 6 shows a burst of high time density and high frequency density patterns in the beginning of the scheduled PxSCH duration followed by a LD DMRS symbol in the later part. The idea is that the UE synchronizes during the first three DMRS (and also uses these for demodulation of PDSCH), while using the latter DMRS symbol only for demodulation assistance.
The right side of FIGURE 6 shows example DMRS for a case when the receiver is already synchronized. Specifically, a sparse DMRS pattern in time and a HD DMRS followed by two LD DMRS is sufficient for this receiver to perform demodulation. According to certain embodiments, the scheduler (i.e., network node) can select the left or right pattern based on the need. For example, in a particular embodiment, if the UE has not been scheduled for a while and/or the synchronization needs to be fine-tuned, the left pattern is used. In the next occasions, close in time to the first one, the pattern to the right can be used, in a particular embodiment. In a particular embodiment, the values ^^1, ^^2, ^^3, ^^4 can be configured by RRC based on need. See an example of such configuration in the Table 9 below. Rows in Table 9 can be indicated by DCI. Hence, it is possible to dynamically switch between equidistant and non-equidistant spacing in time. The RRC can configure the values of such a table. Table 9 Time occasions ^̅^ ^ 1 ^ = { ^^1, ^^2, ^^3, ^^4} T-Value Sequence 0 3 6 15 24 1 3 12 21 30 2 9 18 27 36 3 - - - - In a particular embodiment, for example, in systems or carriers without the use of a dedicated TRS for synchronization, the UE is expected to perform synchronization using the DMRS only (possibly also using broadcasted synchronization signals as SSB in NR). Thus, the DMRS spacing, in time, may need special configuration. Otherwise, if a TRS is present, then the spacing of the occasions ^^1, ^^2, ^^3, ^^4 can be equidistant. In a particular embodiment, if the UE is configured to operate in parallel on multiple cells/carriers, then some cells may use a TRS while others do not and hence the configuration of ^^1, ^^2, ^^3, ^^4 need to be cell specific/carrier specific. In addition, in a particular embodiment, different set of values ^^1, ^^2, ^^3, ^^4 can be configured for different RNTI. For example, C-RNTI use one set of values, and SI-RNTI or RA- RNTI use another set of values. In a particular embodiment, the RA-RNTI may use a time dense DMRS pattern (for initial access), while the user data (based on C-RNTI) may use a sparser time pattern.
While monitoring for the RA-RNTI, the UE assumes (i.e., is configured with) a more dense RS pattern such as, for example, to compensate for less good beam alignment or unknown UE speed, while a more sparse pattern can be used for data transmission associated with C-RNTI as the beams are better aligned, and as the network may know that the UE is not moving fast, etc. In one particular embodiment, the RS pattern is the same across different RNTIs in the first few symbols. For example, in a particular embodiment, ( ^^1, ^^2) is the same for all RNTI, while it can vary for ( ^^3, ^^4). This embodiment may be utilized since the PxSCH channel estimation can start before the PDCCH is decided in this case. In a particular embodiment, the values ^^1, ^^2, ^^3, ^^4 for some transmissions (such as those related to initial access /P-RNTI/RA-RNTI/SI-RNTI) may be given by specifications and cannot be configured or changed by the network. For scheduled PxSCH with long duration, values can be extended using a mathematical expression without the need to be explicitly configured by the network and/or transmitted from the network. For example, the values may be mathematically determined at the UE for larger n, e.g. kn = kn-1 + (kn-1 - kn-2) n ≥ 5. In a particular embodiment, a scheduler adjusts MCS to compensate for the current RS overhead for PxSCH. This may be considered a network implementation embodiment. In a particular embodiment, high density (HD) and low density (LD) frequency patterns are indicated in DCI. For example, HD is comb 2, and LD is comb 4, in a particular embodiment. In one embodiment, the HD and LD frequency pattern applies per DMRS port, as shown in Table 10 where one row is provided per DMRS port. Table 10 Primary pattern High Density (HD) Low Density (LD) RS port ( ^^ ^^, ^̅^ ^ 1 ^ ) ^^ ^^ Δ f /N seed ^^ ^^ ( ^^ ^^, ^^ ^ 1 ^) Δ f /N seed 0 (1,8) 1 0 [+1 +1] - - 1 (2, ^̅^ ^ 1 ^) [+1 +1] 0 1 (4, ^^ ^ 1 ^) 0 2 (2, ^̅^ ^ 1 ^) [+1 -1] 0 1 (4, ^^ ^ 1 ^) 0 3 (2, ^̅^ ^ 1 ^) [+1 +1] 1 1 (4, ^^ ^ 1 ^) 2 4 (2, ^̅^ ^ 1 ^) [+1 -1] 1 1 (4, ^^ ^ 1 ^) 2 5 (4, ^̅^ ^ 1 ^) [+1 +1] 0 1 - - 6 (4, ^̅^ ^ 1 ^) [+1 -1] 0 1 - - 7 (4, ^̅^ ^ 1 ^) [+1 +1] 1 1 - - 8 (4, ^̅^ ^ 1 ^) [+1 -1] 1 1 - - 9 (4, ^̅^ ^ 1 ^) [+1 +1] 2 1 - - 10 (4, ^̅^ ^ 1 ^) [+1 -1] 2 1 - -
11 (4, ^̅^ ^ 1 ^) [+1 +1] 3 1 - - 12 (4, ^̅^ ^ 1 ^) [+1 -1] 3 1 - - In a particular embodiment, if a DMRs port has a HD pattern that already is comb 4 (i.e. row 5-12), then there is no LD pattern (since the “HD pattern” is already natively low density). This can be seen in Table 10 where only ports 0 to 4 have a LD pattern. Example 1: DMRS port 1 ^̅^ ^ 1 ^ = {8}, (HD+LD) FIGURE 7 illustrates an example RS pattern 200, according to certain embodiments. In a particular embodiment, the possibility to use both HD and LD patterns for one and the same scheduled PxSCH (i.e. the different DMRS symbols belonging to the PxSCH) is enabled only when PxSCH and DMRS are FDM:ed in OFDM symbols containing DMRS. This because since switching from HD to LD pattern in this case would give the benefit that more RE is available for PxSCH In a particular embodiment, whether DMRS and PxSCH are FDM or TDM can be dynamically indicated in the scheduling DCI, i.e. it can be different from one PxSCH to the next. In one alternative embodiment, the possibility to use both HD and LD patterns for one and the same scheduled PxSCH is enabled for both when PxSCH and DMRS are FDM:ed or TDM:ed in OFDM symbols containing DMRS, (i.e. no restriction when to use it). In a particular embodiment, if DFT-s-OFDM based PxSCH, then the RS sequence, e.g. ZC sequences used as the sequence must be defined per OFDM symbol since the sequence length depends on whether LD and HD…. This is not required in the case in CP-OFDM case since one could have a running sequence that maps over multiple OFDM symbols. FIGURE 8 illustrates an example RS pattern 300, according to certain embodiments. In the illustrated embodiment, the RS is defined 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 occasions: ^^ ^^ = { ^^1, ^^2, ^^3, ^^4} symbols relative to first RS Time domain shift: ∆ ^^= {0,2} symbols relative to reference start FD-OCC ^^ ^^ = {1, [+1 +1], [+1 −1]} TD-OCC ^^ ^^ = {1, [+1 +1], [+1 −1]} RS Sequence seed ^ 8 ^ ^^ }
FIGURE 9 shows an example of a communication system 400 in accordance with some embodiments. In the example, the communication system 400 includes a telecommunication network 402 that includes an access network 404, such as a radio access network (RAN), and a core network 406, which includes one or more core network nodes 408. The access network 404 includes one or more access network nodes, such as network nodes 410a and 410b (one or more of which may be generally referred to as network nodes 410), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 412a, 412b, 412c, and 412d (one or more of which may be generally referred to as UEs 412) to the core network 406 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 400 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 400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. The UEs 412 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 410 and other communication devices. Similarly, the network nodes 410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 412 and/or with other network nodes or equipment in the telecommunication network 402 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 402. In the depicted example, the core network 406 connects the network nodes 410 to one or more hosts, such as host 416. 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 406 includes one more core network nodes (e.g., core network node 408) 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 408. 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 416 may be under the ownership or control of a service provider other than an operator or provider of the access network 404 and/or the telecommunication network 402, and may be operated by the service provider or on behalf of the service provider. The host 416 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 400 of FIGURE 9 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 402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 402. For example, the telecommunications network 402 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 412 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 404 on a predetermined schedule, when triggered by an internal or external
event, or in response to requests from the access network 404. 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 414 communicates with the access network 404 to facilitate indirect communication between one or more UEs (e.g., UE 412c and/or 412d) and network nodes (e.g., network node 410b). In some examples, the hub 414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 414 may be a broadband router enabling access to the core network 406 for the UEs. As another example, the hub 414 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 410, or by executable code, script, process, or other instructions in the hub 414. As another example, the hub 414 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 414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 414 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 414 may have a constant/persistent or intermittent connection to the network node 410b. The hub 414 may also allow for a different communication scheme and/or schedule between the hub 414 and UEs (e.g., UE 412c and/or 412d), and between the hub 414 and the core network 406. In other examples, the hub 414 is connected to the core network 406 and/or one or more UEs via a wired connection. Moreover, the hub 414 may be configured to connect to an M2M service provider over the access network 404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 410 while still connected via the hub 414 via a wired or wireless connection. In some embodiments, the hub 414 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 410b. In other embodiments, the hub 414 may be a non- dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
FIGURE 10 shows a UE 500 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 500 includes processing circuitry 502 that is operatively coupled via a bus 504 to an input/output interface 506, a power source 508, a memory 510, a communication interface 512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 10. 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 502 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 510. The processing circuitry 502 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 502 may include multiple central processing units (CPUs). In the example, the input/output interface 506 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 500. 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 508 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 508 may further include power circuitry for delivering power from the power source 508 itself, and/or an external power source, to the various parts of the UE 500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 508 to make the power suitable for the respective components of the UE 500 to which power is supplied. The memory 510 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 510 includes one or more application programs 514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 516. The memory 510 may store, for use by the UE 500, any of a variety of various operating systems or combinations of operating systems. The memory 510 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 510 may allow the UE 500 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 510, which may be or comprise a device-readable storage medium. The processing circuitry 502 may be configured to communicate with an access network or other network using the communication interface 512. The communication interface 512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 522. The communication interface 512 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 518 and/or a receiver 520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 518 and receiver 520 may be coupled to one or more antennas (e.g., antenna 522) and may share circuit components, software or firmware, or alternatively be implemented separately. In the illustrated embodiment, communication functions of the communication interface 512 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 512, 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 500 shown in FIGURE 10. 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 11 shows a network node 600 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 600 includes a processing circuitry 602, a memory 604, a communication interface 606, and a power source 608. The network node 600 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 600 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 600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 604 for different RATs) and some components may be reused (e.g., a same antenna 610 may be shared by different RATs). The network node 600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 600, 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 600. The processing circuitry 602 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 600 components, such as the memory 604, to provide network node 600 functionality. In some embodiments, the processing circuitry 602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 602 includes one or more of radio frequency (RF) transceiver circuitry 612 and baseband processing circuitry 614. In some embodiments, the radio frequency (RF) transceiver circuitry 612 and the baseband processing circuitry 614 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 612 and baseband processing circuitry 614 may be on the same chip or set of chips, boards, or units. The memory 604 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 602. The memory 604 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 602 and utilized by the network node 600. The memory 604 may be used to store any calculations made by the processing circuitry 602 and/or any data received via the communication interface 606. In some embodiments, the processing circuitry 602 and memory 604 is integrated. The communication interface 606 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 606 comprises port(s)/terminal(s) 616 to send and receive data, for example to and from a network over a wired connection. The communication interface 606 also includes radio front- end circuitry 618 that may be coupled to, or in certain embodiments a part of, the antenna 610. Radio front-end circuitry 618 comprises filters 620 and amplifiers 622. The radio front-end circuitry 618 may be connected to an antenna 610 and processing circuitry 602. The radio front- end circuitry may be configured to condition signals communicated between antenna 610 and processing circuitry 602. The radio front-end circuitry 618 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 618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 620 and/or amplifiers 622. The radio signal may then be transmitted via the antenna 610. Similarly, when receiving data, the antenna 610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 618. The digital data may be passed to the processing circuitry 602. In other embodiments, the communication interface may comprise different components and/or different combinations of components. In certain alternative embodiments, the network node 600 does not include separate radio front-end circuitry 618, instead, the processing circuitry 602 includes radio front-end circuitry and is connected to the antenna 610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 612 is part of the communication interface 606. In still other embodiments, the communication interface 606 includes one or more ports or terminals 616, the radio front-end circuitry 618, and the RF transceiver circuitry 612, as part of a radio unit (not shown), and the communication interface 606 communicates with the baseband processing circuitry 614, which is part of a digital unit (not shown).
The antenna 610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 610 may be coupled to the radio front-end circuitry 618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 610 is separate from the network node 600 and connectable to the network node 600 through an interface or port. The antenna 610, communication interface 606, and/or the processing circuitry 602 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 610, the communication interface 606, and/or the processing circuitry 602 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 608 provides power to the various components of network node 600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 600 with power for performing the functionality described herein. For example, the network node 600 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 608. As a further example, the power source 608 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 600 may include additional components beyond those shown in FIGURE 11 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 600 may include user interface equipment to allow input of information into the network node 600 and to allow output of information from the network node 600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 600. FIGURE 12 is a block diagram of a host 700, which may be an embodiment of the host 416 of FIGURE 9, in accordance with various aspects described herein. As used herein, the host 700 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 700 may provide one or more services to one or more UEs. The host 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a network interface 708, a power source 710, and a memory 712. 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 5 and 6, such that the descriptions thereof are generally applicable to the corresponding components of host 700. The memory 712 may include one or more computer programs including one or more host application programs 714 and data 716, which may include user data, e.g., data generated by a UE for the host 700 or data generated by the host 700 for a UE. Embodiments of the host 700 may utilize only a subset or all of the components shown. The host application programs 714 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 714 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 700 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 714 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 13 is a block diagram illustrating a virtualization environment 800 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 800 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 802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Hardware 804 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 806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 808a and 808b (one or more of which may be generally referred to as VMs 808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 806 may present a virtual operating platform that appears like networking hardware to the VMs 808. The VMs 808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 806. Different embodiments of the instance of a virtual appliance 802 may be implemented on one or more of VMs 808, 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 808 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 808, and that part of hardware 804 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 808 on top of the hardware 804 and corresponds to the application 802. Hardware 804 may be implemented in a standalone network node with generic or specific components. Hardware 804 may implement some functions via virtualization. Alternatively, hardware 804 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 810, which, among others, oversees lifecycle management of applications 802. In some embodiments, hardware 804 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 812 which may alternatively be used for communication between hardware nodes and radio units. FIGURE 14 shows a communication diagram of a host 902 communicating via a network node 904 with a UE 906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 412a of FIGURE 9 and/or UE 500 of FIGURE 10), network node (such as network node 410a of FIGURE 9 and/or network node 600 of FIGURE 11), and host (such as host 416 of FIGURE 9 and/or host 700 of FIGURE 12) discussed in the preceding paragraphs will now be described with reference to FIGURE 14. Like host 700, embodiments of host 902 include hardware, such as a communication interface, processing circuitry, and memory. The host 902 also includes software, which is stored in or accessible by the host 902 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 906 connecting via an over-the-top (OTT) connection 950 extending between the UE 906 and host 902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 950. The network node 904 includes hardware enabling it to communicate with the host 902 and UE 906. The connection 960 may be direct or pass through a core network (like core network 406 of FIGURE 9) 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 906 includes hardware and software, which is stored in or accessible by UE 906 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 906 with the support of the host 902. In the host 902, an executing host application may communicate with the executing client application via the OTT connection 950
terminating at the UE 906 and host 902. 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 950 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 950. The OTT connection 950 may extend via a connection 960 between the host 902 and the network node 904 and via a wireless connection 970 between the network node 904 and the UE 906 to provide the connection between the host 902 and the UE 906. The connection 960 and wireless connection 970, over which the OTT connection 950 may be provided, have been drawn abstractly to illustrate the communication between the host 902 and the UE 906 via the network node 904, 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 950, in step 908, the host 902 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 906. In other embodiments, the user data is associated with a UE 906 that shares data with the host 902 without explicit human interaction. In step 910, the host 902 initiates a transmission carrying the user data towards the UE 906. The host 902 may initiate the transmission responsive to a request transmitted by the UE 906. The request may be caused by human interaction with the UE 906 or by operation of the client application executing on the UE 906. The transmission may pass via the network node 904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 912, the network node 904 transmits to the UE 906 the user data that was carried in the transmission that the host 902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 914, the UE 906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 906 associated with the host application executed by the host 902. In some examples, the UE 906 executes a client application which provides user data to the host 902. The user data may be provided in reaction or response to the data received from the host 902. Accordingly, in step 916, the UE 906 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 906. Regardless of the specific manner in which the user data was provided, the UE 906 initiates, in step 918, transmission of the user data towards the host 902 via the network node 904. In step 920, in accordance with the teachings of the embodiments described throughout this disclosure, the
network node 904 receives user data from the UE 906 and initiates transmission of the received user data towards the host 902. In step 922, the host 902 receives the user data carried in the transmission initiated by the UE 906. One or more of the various embodiments improve the performance of OTT services provided to the UE 906 using the OTT connection 950, in which the wireless connection 970 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 902. As another example, the host 902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 902 may store surveillance video uploaded by a UE. As another example, the host 902 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 902 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 950 between the host 902 and UE 906, 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 902 and/or UE 906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 950 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 950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 904. 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 902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 950 while monitoring propagation times, errors, etc. FIGURE 15 illustrates an example method 1000 by a UE 412 for utilizing dynamic density RS patterns, according to certain embodiments. In the illustrated embodiment, the method includes a receiving step at 1002. For example, at step 1002, the UE 412 may receive, from a network node 410, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. FIGURE 16 illustrates another example method 1100 by a UE 412 for utilizing dynamic density RS patterns, according to certain embodiments. The method begins at step 1102 when the UE 412 receives, from a network node 410, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. Based on the RS pattern, the UE 412 transmits the RS to the network node on an uplink channel or receives the RS from the network node on a downlink channel, at step 1104. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. In a particular embodiment, the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis and/or the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier. In a particular embodiment, the time density indicates a frequency at which the RS is transmitted or received on a symbol basis. In a particular embodiment, a spacing between RS time occasions within the plurality of RS time occasions is equidistant. In a particular embodiment, a spacing between RS time occasions within the plurality of RS time occasions is not equidistant. In a further particular embodiment, an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern. In a particular embodiment, the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions. In a particular embodiment, the information is received via DCI. In a particular embodiment, transmitting the RS to the network node on the uplink channel or receiving the RS from the network node on the downlink channel includes:
^ based on the RS pattern, transmitting the RS to the network node on a Physical Uplink Shared Channel, PUSCH; or ^ based on the RS pattern, receiving the RS from the network node on a Physical Downlink Shared Channel, PDSCH; or ^ based on the RS pattern, receiving the RS from the network node on a Physical Downlink Control Channel, PDCCH. FIGURE 17 illustrates an example method 1200 by a network node 410 for utilizing dynamic density RS patterns, according to certain embodiments. In the illustrated embodiment, the method includes a transmitting step at 1202. For example, at step 1202, the network node 410 may transmit, to a UE 412, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. FIGURE 18 illustrates another example method 1300 by a network node 410 for utilizing dynamic density RS patterns, according to certain embodiments. The method begins at step 1302 when the network node transmits, to a UE 412, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern. The plurality of RS time occasions of the RS pattern are associated with an uplink or downlink transmission. Based on the RS pattern, the network node 410 transmits the RS to the UE on an downlink channel or receives the RS from the UE on an uplink channel, at step 1304. At least one of the frequency density and/or the time density changes within the plurality of RS time occasions. In a particular embodiment, the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis, and/or the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier. In a particular embodiment, the time density indicates a frequency at which the RS is transmitted or received on a symbol basis. In a particular embodiment, a spacing between RS time occasions within the plurality of RS time occasions is equidistant. In a particular embodiment, a spacing between RS time occasions within the plurality of RS time occasions is not equidistant. In a particular embodiment, an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern.
In a particular embodiment, the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions, and the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions. In a particular embodiment, the information is transmitted via downlink control information, DCI. In a particular embodiment, transmitting the RS to the UE on the downlink channel or receiving the RS from the UE on the uplink channel comprises: ^ based on the RS pattern, transmitting the RS to the network node on a Physical Uplink Shared Channel, PUSCH; or ^ based on the RS pattern, receiving the RS from the network node on a Physical Downlink Shared Channel, PDSCH; or ^ based on the RS pattern, receiving the RS from the network node on a Physical Downlink Control Channel, PDCCH. 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 user equipment (UE) for utilizing dynamic density Reference Signal (RS) patterns, the method comprising: receiving, from a network node, information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern, wherein at least one of the frequency density and/or the time density changes within the plurality of RS time occasions. Example Embodiment C2. The method of Example Embodiment C1, wherein the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis. Example Embodiment C3. The method of any one of Example Embodiments C1 to C2, wherein the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier. Example Embodiment C4. The method of any one of Example Embodiments C1 to C3, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis. Example Embodiment C5. The method of any one of Example Embodiments C1 to C4, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant. Example Embodiment C6. The method of any one of Example Embodiments C1 to C4, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant. Example Embodiment C7. The method of Example Embodiment C6, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of a RS duration is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS duration. Example Embodiment C8. The method of any one of Example Embodiments C6 to C7, wherein the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions. Example Embodiment C9. The method of Example Embodiment C8, comprising: using the RS transmitted or received according to the higher density for demodulation and synchronization, and using the RS transmitted or received according to the lower density for demodulation but not synchronization. Example Embodiment C10. The method of any one of Example Embodiments C6 to C7, wherein the RS is transmitted or received according to a lower density during a beginning of the
plurality of RS time occasions and wherein the RS is transmitted or received according to a higher density at an end of the plurality of RS time occasions. Example Embodiment C11. The method of Example Embodiment C10, comprising: using the RS transmitted or received according to the higher density for demodulation and synchronization, and using the RS transmitted or received according to the lower density for demodulation but not synchronization. Example Embodiment C12. The method of any one of Example Embodiments C1 to C11, wherein the information is received via downlink control information (DCI). Example Embodiment C13. The method of any one of Example Embodiments C1 to C12, comprising: based on the RS pattern, transmitting the RS to the network node on a Physical Uplink Shared Channel (PUSCH); or based on the RS pattern, receiving the RS from the network node on a Physical Downlink Shared Channel (PDSCH); or based on the RS pattern, receiving the RS from the network node on a Physical Downlink Control Channel (PDCCH). Example Embodiment C14. The method of any one of Example Embodiments C1 to C13, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node. Example Embodiment C15. A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C14. Example Embodiment C16. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments C1 to C14. Example Embodiment C17. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments C1 to C14. Example Embodiment C18. 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 C14. Example Embodiment C19. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments C1 to C14. Group D Example Embodiments Example Embodiment D1. A method by a network node for utilizing dynamic density Reference Signal (RS) patterns, the method comprising: transmitting, to a user equipment (UE), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern, wherein at least one of the frequency density and/or the time
density changes within the plurality of RS time occasions. Example Embodiment D2. The method of Example Embodiment D1, wherein the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis. Example Embodiment D3. The method of any one of Example Embodiments D1 to D2, wherein the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier. Example Embodiment D4. The method of any one of Example Embodiments D1 to D3, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis. Example Embodiment D5. The method of any one of Example Embodiments D1 to D4, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant. Example Embodiment D6. The method of any one of Example Embodiments D1 to D4, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant. Example Embodiment D7. The method of Example Embodiment D6, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of a RS duration is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS duration. Example Embodiment D8. The method of any one of Example Embodiments D6 to D7, wherein the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions. Example Embodiment D9. The method of Example Embodiment D8, comprising: configuring the UE to use the RS transmitted or received according to the higher density for demodulation and synchronization, and configuring the UE to use the RS transmitted or received according to the lower density for demodulation but not synchronization. Example Embodiment D10. The method of any one of Example Embodiments D6 to D7, wherein the RS is transmitted or received according to a lower density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a higher density at an end of the plurality of RS time occasions. Example Embodiment D11. The method of Example Embodiment D10, comprising: configuring the UE to use the RS transmitted or received according to the higher density for demodulation and synchronization, and configuring the UE to use the RS transmitted or received
according to the lower density for demodulation but not synchronization. Example Embodiment D12. The method of any one of Example Embodiments D1 to D11, wherein the information is transmitted via downlink control information (DCI). Example Embodiment D13. The method of any one of Example Embodiments D1 to D12, comprising: based on the RS pattern, receiving the RS from the UE on a Physical Uplink Shared Channel (PUSCH); or based on the RS pattern, transmitting the RS to the UE on a Physical Downlink Shared Channel (PDSCH); or based on the RS pattern, transmitting the RS to the UE on a Physical Downlink Control Channel (PDCCH). Example Embodiment D14. The method of any one of Example Embodiments D1 to D13, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Example Embodiment D15. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments D1 to D14. Example Embodiment D16. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments D1 to D14. Example Embodiment D17. 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 D14. Example Embodiment D18. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments D1 to D14. Group E Example Embodiments Example Embodiment E1. A user equipment for utilizing dynamic density Reference Signal (RS) patterns, comprising: processing circuitry configured to perform any of the steps of any of the Group A and C Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry. Example Embodiment E2. A network node for utilizing dynamic density Reference Signal (RS) patterns, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B and D Example Embodiments; power supply circuitry configured to supply power to the processing circuitry. Example Embodiment E3. A user equipment (UE) for utilizing dynamic density Reference Signal (RS) patterns, 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 and C 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 E4. 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 and C Example Embodiments to receive the user data from the host. Example Embodiment E5. 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 E6. 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 E7. 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 embodiments to receive the user data from the host. Example Emboidment E8. 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 E9. 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 E10. 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 and C Example Embodiments to transmit the user data to the host. Example Emboidment E11. 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 E12. 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 E13. 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 and C Example Embodiments to transmit the user data to the host. Example Embodiment E14. 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 E15. 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 E16. 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 and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment E17. 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 E18. 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 and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment E19. 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 E20. 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 E21. 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 and D Example Embodiments to transmit the user data from the host to the UE. Example Embodiment E22. The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment. Example Embodiment E23. 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 and D Example Embodiments to receive the user data from a user equipment (UE) for the host. Example Embodiment E24. 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 E25. 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 E26. 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 and D Example Embodiments to receive the user data from the UE for the host. Example Embodiment E27. 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 (1100) by a user equipment, UE (412, 500), for utilizing dynamic density Reference Signal, RS, patterns, the method comprising: receiving (1102), from a network node (410, 600), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern; and based on the RS pattern, transmitting (1104) the RS to the network node on an uplink channel or receiving the RS from the network node on a downlink channel, and wherein at least one of the frequency density and/or the time density changes within the plurality of RS time occasions.
2. The method of Claim 1, wherein at least one of: the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis, and the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier.
3. The method of any one of Claims 1 to 2, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis.
4. The method of any one of Claims 1 to 3, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant.
5. The method of any one of Claims 1 to 3, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant.
6. The method of Claim 5, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern.
7. The method of any one of Claims 5 to 6, wherein the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions.
8. The method of any one of Claims 1 to 7, wherein the information is received via downlink control information, DCI.
9. The method of any one of Claims 1 to 8, wherein transmitting the RS to the network node on the uplink channel or receiving the RS from the network node on the downlink channel comprises:
based on the RS pattern, transmitting the RS to the network node on a Physical Uplink Shared Channel, PUSCH; or based on the RS pattern, receiving the RS from the network node on a Physical Downlink Shared Channel, PDSCH; or based on the RS pattern, receiving the RS from the network node on a Physical Downlink Control Channel, PDCCH.
10. A method (1300) by a network node (410, 600) for utilizing dynamic density Reference Signal, RS, patterns, the method comprising: transmitting (1302), to a user equipment, UE (412, 500), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern, wherein the plurality of RS time occasions of the RS pattern are associated with an uplink or downlink transmission; and based on the RS pattern, transmitting (1304) the RS to the UE on an downlink channel or receiving the RS from the UE on an uplink channel, and wherein at least one of the frequency density and/or the time density changes within the plurality of RS time occasions.
11. The method of Claim 10, wherein at least one of: the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis, and the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier.
12. The method of any one of Claims 10 to 11, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis.
13. The method of any one of Claims 10 to 12, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant.
14. The method of any one of Claims 10 to 12, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant.
15. The method of Claim 14, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern.
16. The method of any one of Claims 14 to 15, wherein:
the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions, and the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions.
17. The method of any one of Claims 10 to 16, wherein the information is transmitted via downlink control information, DCI.
18. The method of any one of Claims 10 to 17, wherein transmitting the RS to the UE on the downlink channel or receiving the RS from the UE on the uplink channel comprises: based on the RS pattern, receiving the RS from the UE on a Physical Uplink Shared Channel, PUSCH; or based on the RS pattern, transmitting the RS to the UE on a Physical Downlink Shared Channel, PDSCH; or based on the RS pattern, transmitting the RS to the UE on a Physical Downlink Control Channel, PDCCH.
19. A user equipment, UE (412, 500), for utilizing dynamic density Reference Signal, RS, patterns, the UE configured to: receive, from a network node (410, 600), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern; and based on the RS pattern, transmit the RS to the network node on an uplink channel or receive the RS from the network node on a downlink channel, and wherein at least one of the frequency density and/or the time density changes within the plurality of RS time occasions.
20. The UE of Claim 19, wherein at least one of: the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis, and the frequency density is represented as 1/X and the 1/X indicates that the RS is mapped to every Xth subcarrier.
21. The UE of any one of Claims 19 to 20, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis.
22. The UE of any one of Claims 19 to 21, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant.
23. The UE of any one of Claims 19 to 21, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant.
24. The UE of Claim 23, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern.
25. The UE of any one of Claims 23 to 24, wherein the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions and wherein the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions.
26. The UE of any one of Claims 19 to 25, wherein the information is received via downlink control information, DCI.
27. The UE of any one of Claims 19 to 26, wherein when transmitting the RS to the network node on the uplink channel or receiving the RS from the network node on the downlink channel, the UE is configured to: based on the RS pattern, transmit the RS to the network node on a Physical Uplink Shared Channel, PUSCH; or based on the RS pattern, receive the RS from the network node on a Physical Downlink Shared Channel, PDSCH; or based on the RS pattern, receive the RS from the network node on a Physical Downlink Control Channel, PDCCH.
28. A network node (410, 600) for utilizing dynamic density Reference Signal, RS, patterns, the network node configured to: transmit, to a user equipment, UE (412, 500), information indicating at least one of a frequency density or a time density for a plurality of RS time occasions of a RS pattern, wherein the plurality of RS time occasions of the RS pattern are associated with an uplink or downlink transmission; and based on the RS pattern, transmit the RS to the UE on an downlink channel or receiving the RS from the UE on an uplink channel, and wherein at least one of the frequency density and/or the time density changes within the plurality of RS time occasions.
29. The network node of Claim 28, wherein at least one of: the frequency density indicates a frequency at which a RS is mapped on a subcarrier basis, and the frequency density is represented as 1/X and wherein the 1/X indicates that the RS is mapped to every Xth subcarrier.
30. The network node of any one of Claims 28 to 29, wherein the time density indicates a frequency at which the RS is transmitted or received on a symbol basis.
31. The network node of any one of Claims 28 to 30, wherein a spacing between RS time occasions within the plurality of RS time occasions is equidistant.
32. The network node of any one of Claims 28 to 30, wherein a spacing between RS time occasions within the plurality of RS time occasions is not equidistant.
33. The network node of Claim 32, wherein an amount of time spacing between two consecutive RS time occasions that are closer to a beginning of the RS pattern is less than an amount of time between two consecutive RS time occasions that are closer to an end of the RS pattern.
34. The network node of any one of Claims 32 to 33, wherein: the RS is transmitted or received according to a higher density during a beginning of the plurality of RS time occasions, and the RS is transmitted or received according to a lower density at an end of the plurality of RS time occasions.
35. The method of any one of Claims 28 to 34, wherein the information is transmitted via downlink control information, DCI.
36. The network node of any one of Claims 28 to 35, wherein when transmitting the RS to the UE on the downlink channel or receiving the RS from the UE on the uplink channel, the network node is configured to: based on the RS pattern, receive the RS from the UE on a Physical Uplink Shared Channel, PUSCH; or based on the RS pattern, transmit the RS to the UE on a Physical Downlink Shared Channel, PDSCH; or based on the RS pattern, transmit the RS to the UE on a Physical Downlink Control Channel, PDCCH.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US63/478,118 | 2022-12-31 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024141991A1 true WO2024141991A1 (en) | 2024-07-04 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP4381884A1 (en) | Random access partitioning and random access report | |
| WO2023174858A1 (en) | Antenna port tables for physical downlink shared channel with increased number of frequency division codes | |
| WO2023209695A1 (en) | Determining channels and signals for applying a time advance | |
| WO2024141991A1 (en) | Systems and methods for dynamic density reference signal patterns | |
| WO2023174859A1 (en) | Antenna port tables for physical uplink shared channel with increased number of frequency domain codes | |
| WO2024142014A1 (en) | Systems and methods for dynamic density reference signal patterns | |
| WO2023062610A1 (en) | Multi-slot physical layer downlink control channel (pdcch) monitoring | |
| WO2024033471A1 (en) | Handling co-scheduled demodulation reference signals in a communication network | |
| WO2024033531A1 (en) | Dynamic switching between different number of additional dmrs symbols for pdsch or pusch | |
| WO2023209680A1 (en) | Dynamic switching between legacy and extended dmrs procedures | |
| EP4381672A1 (en) | Physical downlink control channel monitoring for enhanced cross carrier scheduling | |
| WO2024127320A1 (en) | Pt-rs enhancement for more dmrs ports | |
| WO2023095093A1 (en) | Mac ce signaling for supporting both joint dl/ul tci and separate dl/ul tci operations | |
| WO2023211358A1 (en) | Search space determination for single downlink control information scheduling multiple cells | |
| KR20240089682A (en) | Multi-slot physical layer downlink control channel (PDCCH) monitoring | |
| WO2023211352A1 (en) | Dynamic slot format indication | |
| WO2023152720A1 (en) | Systems and methods for configuring spatial relation for sounding reference signal for propagation delay compensation | |
| WO2024100073A1 (en) | Single dci scheduling for multiple cell carrier selection | |
| WO2023170658A1 (en) | Td-occ over nonconsecutive dm-rs symbols | |
| WO2024035312A1 (en) | Devices and methods for dynamic uplink transmission switching | |
| WO2024035327A1 (en) | Network node energy savings via flexible random access response mechanism | |
| WO2023203143A1 (en) | Carrier configuration and scheduling for subband full duplex systems | |
| WO2023211357A1 (en) | Carrier selection for single downlink control information scheduling multiple cells | |
| WO2023053088A1 (en) | Methods and apparatuses for rlm for inter-cell mtrp operation | |
| WO2023209686A1 (en) | Systems and methods for invalidation signaling |