WO2024123677A1 - Uplink positioning reference signal (ul-prs) adaptations and extensions for sensing in joint communication and sensing systems - Google Patents

Uplink positioning reference signal (ul-prs) adaptations and extensions for sensing in joint communication and sensing systems Download PDF

Info

Publication number
WO2024123677A1
WO2024123677A1 PCT/US2023/082297 US2023082297W WO2024123677A1 WO 2024123677 A1 WO2024123677 A1 WO 2024123677A1 US 2023082297 W US2023082297 W US 2023082297W WO 2024123677 A1 WO2024123677 A1 WO 2024123677A1
Authority
WO
WIPO (PCT)
Prior art keywords
prs
resource
sensing
srs
symbols
Prior art date
Application number
PCT/US2023/082297
Other languages
French (fr)
Inventor
Fatemeh HAMIDI-SEPEHR
Thushara Hewavithana
Mark Lehne
Qian Li
Debdeep CHATTERJEE
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2024123677A1 publication Critical patent/WO2024123677A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management

Definitions

  • Various embodiments generally may relate to the field of wireless communications.
  • Figure 1 illustrates an example sensing block structure, in accordance with various embodiments.
  • Figure 2 illustrates an example of frequency multiplexing of sounding reference signal(s) from multiple users using comb-2, in accordance with various embodiments.
  • FIG. 3 illustrates examples of uplink positioning reference signal (UL-PRS) resource element (RE) patterns, in accordance with various embodiments.
  • U-PRS uplink positioning reference signal
  • RE resource element
  • FIG. 4 illustrates examples of SRS configurations, in accordance with various embodiments.
  • Figure 5 illustrates example RE offsets for UL-PRS, in accordance with various embodiments.
  • Figure 6 illustrates an example setting of pathloss estimation for UL-PRS, in accordance with various embodiments.
  • FIG. 7 illustrates an example of transmit/reception point (TRP) muting for comb-2, in accordance with various embodiments.
  • Figure 8 illustrates an example of spatial relation and pathloss reference for UL-PRS, in accordance with various embodiments.
  • Figure 9 schematically illustrates a wireless network in accordance with various embodiments.
  • Figure 10 schematically illustrates components of a wireless network in accordance with various embodiments.
  • Figure 11 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • a machine-readable or computer-readable medium e.g., a non-transitory machine-readable storage medium
  • Figure 12 illustrates a network in accordance with various embodiments.
  • Figure 13 depicts an example procedure for practicing the various embodiments discussed herein.
  • Figure 14 depicts an alternative example procedure for practicing the various embodiments discussed herein.
  • Figure 15 depicts an alternative example procedure for practicing the various embodiments discussed herein.
  • JCAS cellular-based joint communication and sensing
  • This functionality may include the proper definition and configuration of the numerology and sensing frame structure, and should be properly aligned within the boundaries of an existing communication frame.
  • the functionality may also require efficient assignment of resources, which consider various design factors involving both communication and sensing performances.
  • aspects with respect to extension and adaptation of new radio (NR) uplink (UL) Positioning Reference Signal (PRS) (which itself is based on Sounding Reference Signal - SRS) for the purpose of sensing are disclosed.
  • NR new radio
  • UL Uplink
  • PRS Positioning Reference Signal
  • Such extensions target enablement of sensing based on User Equipment (UE)’s transmitted radio signal (which may correspond to different sensing architectures, mono/bi/multi- static).
  • gNodeB gNodeB
  • UE-based sensing scenarios can exist in a cellular framework, to enable different sensing application and use cases.
  • the following cases can exist:
  • Case 1 gNB sends the sensing radio signal and receives/measures/processes its reflections from objects/environment, in time, frequency, and spatial/angular domains. If the same gNB also receives/measures/processes the reflected signal, the scenario may be called gNB-based monostatic sensing mode, and if other gNB(s) are involved in receiving, measurement/processing, it may be called gNB-based bi-static (multi-static) sensing mode by cooperative network nodes.
  • Case 2 gNB sends the sensing radio signal and UE receives/measures/processes its reflections (bi-static sensing mode).
  • sensing may require transmission/reception from multiple nodes to perform coordinated environment or neighborhood perception by multiple gNBs and/or UEs.
  • UL-PRS uplink
  • 3GPP third generation partnership project
  • SRS sounding reference signal
  • the wireless signal used for the purpose of sensing should meet certain requirements in terms of time domain and frequency domain attributes.
  • attributes determine the underlying numerologies, frame structures, as well as the physical resource assignments and patterns.
  • IDF AE8858 these aspects are fully investigated, and the required attributes and properties of air-interface signal used for sensing to meet range, speed, and angular requirements are derived in detail. These characteristics may be applicable to the signal transmitted from gNB and/or UE.
  • the corresponding required adaptations on DL-PRS may also be disclosed in order to meet the desired attributes for sensing.
  • Embodiments herein may relate to scenarios which rely on transmission of UE’s radio signal for the purpose of sensing. Based on the derived structure and signal pattem/attributes for sensing detection in IDF AE8858, in this disclosure, first, reusability of UL sounding reference signal structure for sensing may be established, followed by disclosed adaptations and extensions to UL-PRS (based on SRS).
  • Embodiments herein may relate to air- interface signal design and attributes, and not on architectural, hardware and implementation aspects. For example, aspects such as enablement of full-duplex for monostatic UE sensing, or synchronization for bi/multi- static sensing (e.g., at gNB) based on UE’s signal, are not the focus of this disclosure.
  • Example statistical properties/structure of the sensing signal in time and frequency domains e.g., as may be described in IDF AE8858
  • the parametrization, numerology, frame structure, and time domain/frequency domain (TD/FD) resource mapping/dimensioning of the signal used for sensing is driven by the requirements concerning range and velocity resolution, and their respective unambiguous max detectable values, as well as the requirements concerning multiplexing of communication and sensing. More accurately, dimensioning of numerology (selection of SCS and symbol/CP duration), and time-frequency attributes, resource allocation, and statistical properties (which is the most important aspect in enabling the desired detection processing) of sensing signal is primarily driven by such requirements.
  • all the OFDM system parameters e.g., bandwidth (BW), SCS, number of subcarriers, CP duration, symbol duration, number of OFDM symbols
  • BW bandwidth
  • SCS number of subcarriers
  • CP duration symbol duration
  • number of OFDM symbols number of OFDM symbols
  • time span and time spacing may be needed for the signal used for sensing.
  • time domain resource assignment properties for sensing signal to enable Doppler processing are possible.
  • Sensing block or sensing frame
  • the sensing block duration is an integer number (fc) multiple of SRI duration, i.e., k X T SRI .
  • k is the size of
  • T SRI ⁇ which is inversely proportional to the maximum detectable speed and carrier frequency.
  • SRI symbol repetition interval
  • ISI inter- symbol-interference
  • TCP CP duration
  • NR CP in frequency range 1 FR1
  • FR1 supports longer range UCs, with same CP and OFDM symbol durations for communication and sensing symbols.
  • useful symbol duration is very large compared to the orders of CPs desired for sensing ranging (low CP loss).
  • FR2_ supporting a unified symbol/CP duration between communication and sensing may not be possible for higher SCSs, depending on UC’s max range requirement.
  • FR2 can support shorter range UCs, with same CP and OFDM symbol duration for sensing and communication, and longer-range UCs, with different CP and OFDM symbol duration for sensing and communication.
  • Frequency domain sensing resources attributes/pattems
  • system parameters In this subsection we take a look at translating the sensing requirements into signal properties in frequency domain. Particularly, frequency domain resource assignment for sensing signal to enable a single sensing task, needs to meet the following condition:
  • FR1 may impose potential compromise in range resolution, which may be addressed by enabling use of carrier aggregation to provide extended bandwidth for sensing.
  • FD comb structure reduces the max unambiguous range (since it increases effective SCS).
  • range detection performance is limited by CP limitation as well, and CP-based range is normally much smaller than max unambiguous range.
  • the largest integer value m comb for which, n X / 2 is less than l/nr comi) x the maximum unambiguous range, i.e., n - X SCS can b e derived, e.g., for some systems, even 5 times CP range is about (1/3) x (maximum unambiguous range).
  • the comb size can be selected as a number less than or equal to m comb .
  • SCS frequency-related system parameter
  • SCS frequency-related system parameter
  • SCS have different implications and tradeoffs in terms of sensing.
  • SCS is inversely proportional to the maximum unambiguous detectable range. Meaning that larger SCS may allow for detection of higher Doppler shifts and faster moving targets without inter carrier orthogonality (for ICI mitigation).
  • the SCS should be larger than -lOxDoppler frequency
  • CP loss due to inefficiency (caused by the ratio of CP time to usable OFDM symbol time) increases.
  • larger SCS are available for higher carrier frequencies, which support shorter OFDM symbol and CP durations, resulting in shortened sensing ranges.
  • the current section provides examples of how a sensing frame structure can fit in the cellular system frame and numerology. Accordingly, the following example SRI values and Doppler FFT sizes (and hence, sensing frame structure and durations) were also discussed in IDF AE8858 to support highest possible capabilities for velocity estimation under different limitations, and to meet reasonably fine velocity resolutions, while keeping the design as simple as possible (without compromising supported sensing performance).
  • SRI is defined to occur either at half-slot-rate, full-slot-rate, or double-slot- rate, for different maximum desired speeds (depending on the use-case).
  • the resulting exact supported max speed, and speed resolution can be determined then, also based on the carrier frequency.
  • the number of OFDM symbols in the SRI should provide a good balance between the maximum detectable speed, the sensing repetition gain (the total Doppler processing gain, for a certain sensing block is 101ogl0(Doppler FFT size) + 101ogl0(number of OFDM symbol within SRI)), the flexibility/capability to support multiplexing between sensing and communication, the field-of-view (FoV) coverage, depending on the required number of beams, and the beamwidth.
  • the Doppler FFT sizes are generally smaller is FR1, which involves fewer number of radio frames for sensing and less limitation and unavailability for communication.
  • Doppler FFT sizes may also be supported (e.g., to provide finer Doppler resolution and/or higher processing gain)
  • longer sensing frame durations resulting from large Doppler FFT sizes may result in range migration issue in the range-Doppler image. This would require proper handling to avoid performance degradation.
  • the CP durations are the same as in NR, are also adopted for OFDM symbols used for sensing.
  • the CP durations are the same as in NR, are also adopted for OFDM symbols used for sensing.
  • the CP durations are the same as in NR, are also adopted for OFDM symbols used for sensing.
  • the power range may not allow more than 100m (even 100m for some practical deployments may be too far, e.g., rooftop looking around the block), the support of longer-range UCs with FR2, may not be fully justified (especially, as the longer-range UCs can be supported with FR1 with less complications).
  • NR DL-PRS signal was anall led in IDF AE8858, and required extensions to enable sensing, were disclosed.
  • UL-PRS signal design including the frequency and time resource allocation and pattems/regularities is reviewed, followed by identifying similarities and gaps with respect to what is desired for sensing, in the subsection after.
  • NR UL-PRS was defined in NR Rel-16 based on Rel-15 SRS, for the purpose of UE localization/positioning. Accordingly, first, examples of Rel-15 SRS design is provided, followed by Rel-16 extensions for UL positioning.
  • Rel-15 SRS resource can span ⁇ 1, 2, 4 ⁇ consecutive OFDM Symbols (OSs), mapped within the last six symbols of the slot only. Multiple SRS symbols allow coverage extension and increased sounding capacity. Ideally, the whole system bandwidth would be measured in a single OFDM symbol, for all SRS ports. However, this is only possible if the UE is close to the receiving base station, as the power spectral density is low when the UE power is used in a full bandwidth transmission.
  • Rel-15 has a repetition factor R, of 1, 2, or 4 in the resource, in which case the same SRS subcarriers are used (sounded) in each repetition, i.e., same subcarriers for R symbols.
  • Rel-15 SRS is transmitted in the same part of the band for 2 or 4 OFDM symbols in SRS resource.
  • a 2- or 4-OS SRS duration is 2- or 4-times repetition of the 1-OS SRS, respectively (depending on depends on configuration of groupHopping and sequenceHopping via the groupOrSequenceHopping parameter, same sequence may be repeated within the SRS resource, or the sequence group and/or sequence-in-a- group may hop across symbols).
  • SRS repetition can also be used when the SRS is beamformed, as in FR2, to allow the gNB to perform receive beam tuning: since UE repeats SRS transmission using same transmit beam multiple times, the gNB can evaluate performance of several gNB receive beam candidates. The performance of these different gNB receive beams can be directly compared since it is known that UE keeps its transmit beam constant for each transmission.
  • Sequences applied to the set of SRS REs are partly based on Zadoff-Chu (ZC) sequences.
  • ZC sequences of prime length are preferred in order to maximize the number of available sequences
  • SRS sequences are not of prime length.
  • SRS sequences are extended ZC sequences based on the longest prime-length ZC sequence with a length M smaller or equal to the desired SRS sequence length. The sequence is then cyclically extended in the frequency domain(FD) up to the desired SRS-sequence length. As the extension is done in the FD, the extended sequence still has a constant spectrum, and thus a “perfect” cyclic autocorrelation, but the time domain amplitude will vary somewhat.
  • Extended ZC sequences are used as SRS sequences for sequence lengths of 36 or larger, corresponding to an SRS extending over 6 and 12 resource blocks in case of comb-2 and comb-4, respectively.
  • a time-dependent sequence randomization (sequence hopping) can be configured for SRS sequence.
  • the sequence used for SRS depends pseudo-randomly on both slot index and symbol index within a slot.
  • the used SRS sequence initialization is configured UE-specific by the RRC.
  • the SRS is also designed with a comb-based pattern similar to the DL-PRS.
  • SRS transmissions from different UEs can be Frequency Domain Multiplexed (FDMed), within the same frequency range by assigning different combs, corresponding to different frequency offsets ( Figure 2).
  • UEs can be multiplexed over the same transmitting symbol by assigning different comb patterns.
  • comb-2 for example, two SRS can be FDMed.
  • up to 12 SRS can be FDMed.
  • multiple SRS ports i.e., 1001 - 1003 are interleaved in the frequency domain within the same OFDM symbol.
  • An SRS resource can be configured to 1, 2, or 4 SRS ports.
  • each SRS port of the SRS resource is present in every symbol and across the whole configured SRS bandwidth of resource, i.e., all SRS ports are present in each OFDM symbol of the resource.
  • An SRS antenna port can thus be repeatedly transmitted by a UE in 2 or 4 symbols in a slot, which can be used to extend the SRS coverage.
  • Different configuration alternatives for the mapping of ports of an SRS resource to subcarriers in an OFDM symbol can use either a comb-4 or a comb-2 structure.
  • An SRS port transmission is mapped to every 2 nd to 4 th subcarrier in an OFDM symbol (i.e., a comb structure is used).
  • comb structure can be used for FDM of multiple UEs as well as FDM of multiple ports of a PRS resource.
  • a gNB can configure a 2-port UE over one comb-2 set of REs, and FDM another 1-port or 2-port UE over the other comb-2 set of REs, over the same OFDM symbol, where each UE’s multi-port transmission is separated using cyclic shift (CS), over same resource elements (REs).
  • CS resource elements
  • the port can be mapped to any of the combs and a CS can be applied (to separate SRS port from another UEs transmission by using different CS and/or different comb).
  • both ports are mapped to the same comb and separated by CS.
  • Any of the combs can be configured for this SRS resource (the other comb can be used by another (e.g., 1-port or 2-port) UE. If this is configured to a single UE, then that is the expectation from that UE).
  • the UE can be configured with a multiport SRS resource. But between different UEs, it is not necessary for the gNB to configure each UE with a multi-port resource.
  • a 4-SRS-port resource either all four ports are mapped to the same comb and separated by CS, or groups of two ports are mapped to either of two configured combs, and separated by CS within the group. It is not possible to map a 4-port SRS resource to 4 different combs, a CS must be used to separate at least two ports. For a four-port and four-comb case when two combs are configured, the two combs cannot be adjacent since that prevents multiplexing another SRS resource in the same OFDM symbol (when using groups of 2 ports, this may limit the capacity to FDM with other UEs).
  • a UE can be configured (by higher layer parameter SRS-ResourceSet, or SRS- PosResourceSet-rl 6) with more than one SRS Resource Set (that each contains one or more SRS resources), used for different purposes (“usages”).
  • these sets can be for DL and UL multi-antenna precoding, or DL and UL beam management.
  • each set is designated for a certain “usage”, such as “Antenna switching”, “Beam management”, etc., and an SRS resource transmitted in a given set cannot be used for another use than it has been configured for.
  • an SRS transmission for “antenna switching” cannot simultaneously be used for “codebook”-based usage and vice versa.
  • each SRS Resource Set can include one or more configured SRS resources.
  • a UE may be configured with K > 1 SRS resources (by higher layer parameter SRS-Resource).
  • the maximum value of K is indicated by the UE capability (supported SRS- Resources in TS 38.306).
  • SRS resources belonging to a set can be in the same slot (adjacent or nonadjacent) or can be distributed across different slots. There is no specified restriction in terms of how far the resources from the same set can be distanced (it will be up to configuration).
  • a slot can be used for transmitting more than one SRS resource, for example, the multiple SRS resources of an SRS resource set.
  • a slot can also contain resources from different sets.
  • the SRS resources of a set can be time domain multiplexed.
  • a 4-port SRS resource for Antenna Port 1001 and 1003 frequency domain multiplexing is also supported (a resource set may correspond to different comb offsets).
  • a UE can be configured with up to 16 SRS resource sets per bandwidth part (limited to 4 sets in FR1) and each set can contain maximum of 64 SRS resources.
  • FR1 the total number of SRS resources is limited to 10, as larger number of resources is needed only when SRS resources are transmitted in different UL beams.
  • an SRS resource set :
  • SRS is used for multiple functionalities
  • UE can be configured with multiple SRS resource sets simultaneously.
  • An SRS can be configured for periodic, semi-persistent (SP), or aperiodic transmission.
  • a periodic SRS is transmitted with a certain periodicity and slot offset within that periodicity and is only configured by RRC.
  • An SP SRS has a periodicity and slot offset in the same way as a periodic SRS and is also configured by RRC. However, actual UL-PRS transmission according to the periodicity and slot offset is activated/deactivated by MAC CE signaling.
  • SP SRS allows to start/stop periodic SRS transmission using MAC signaling from gNB to UE, which is faster than RRC control, and provides a means to trigger periodic SRS transmissions when needed only, to avoid interference & unnecessary transmissions from the UE.
  • An aperiodic SRS is configured by RRC but only transmitted when explicitly triggered by DCI. Activation/deactivation, and triggering for SP and aperiodic SRS, respectively, not done for a specific SRS but for an SRS resource set.
  • Rel-15 supports SRS periodicities of ⁇ 1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560 ⁇ slots.
  • Periodic, semi-persistent or aperiodic SRS transmission is a property of an SRS resource set. All SRS resources included within an SRS Resource Set are of the same type. Transmission of aperiodic SRS, or more accurately, transmission of the set of configured SRS included in an aperiodic SRS resource set, is triggered by DCI. All resources within the set also have the same periodicity.
  • UL-based positioning reference signal is based on Rel-15 SRS transmitted from the devices, with enhancements for positioning purposes.
  • UL-PRS may be referred to as “ SRS for positioning” .
  • UL-PRS can be seen as UL equivalence to DL-PRS.
  • SRS for positioning in Rel-16 resolves two aspects specific to positioning. Lirst, since positioning involves measurements from multiple receiving BSs, the signal must have enough range to reach not only the serving BS to which the UE is connected, but also the neighboring BSs involved in the positioning process. Second, the SRS is also designed to cover the full bandwidth, where REs are spread across the different symbols so as to cover all subcarriers. In other words, UL-PRS signal can support a large delay spread range, since it must be received at potentially distant neighboring BSs for position estimation.
  • SNR signal-to-noise ratio
  • configurable patterns cover each subcarrier in the configured bandwidth over the pattern duration which gives the maximum measurement range for the Time of Arrival (ToA) measurement in scenarios with large delay spreads.
  • the UL-PRS sequence is similarly based on Zadoff-Chu sequences as a base signal, also used for Rel-15 SRS, to ensure low-PAPR transmission from the UE.
  • the particular sequence used to generate an SRS symbol depends on configuration parameters.
  • UL-PRS REs are arranged in a particular time/frequency pattern.
  • the SRS structure is extended in several ways: In time domain, the length of the sequence is extended to ensure a sufficiently good signal-to-noise ratio for accurate measurements in gNB.
  • an UL- PRS resource may span 1, 2, 4, 8 or 12 consecutive OLDM symbols (which provide enough coverage to reach all TRPs involved in the positioning procedures), located anywhere in a (UL) slot.
  • the starting point is also more flexible to account for the increased duration.
  • the SRS resources for positioning are transmitted on a single antenna port (i.e., for UL positioning, each UL-PRS resource also is limited to have a single port).
  • the UL-PRS has also a comb-N pattern (N is comb size).
  • Lor Rel-15 SRS, N can take values 2 or 4, but for UL-PRS N is extended to a set of ⁇ 2, 4, 8 ⁇ to allow multiplexing of a larger number of devices. Similar to DL-PRS, a “permuted” comb is used for positioning.
  • UL-PRS Resource with 1, 2, 4, 8 or 12 consecutive OFDM symbols is transmitted in the UE’ s active UL bandwidth part.
  • the number of symbols can be larger or smaller than the comb size. For example, a comb-2 UL-PRS with one symbol, or a comb-4 with eight symbols are also supported (if comb-size is smaller than the number of symbols, then repetition within the resource can take place).
  • RE mapping is not arranged in a staircase pattern (Eigure 3), with the advantage being that the first few symbols already have a better effective comb size. For example, if only the first few symbols are considered for TOA measurement, the effect of the alias correlation peaks are better suppressed.
  • the first two symbols of the comb-4 UL-PRS provide an effective comb-2 RE pattern (after destaggering). For each pair of comb size and the number of symbols, there is one RE pattern.
  • the RE pattern of an UL-PRS resource is configured with a comb offset for the first symbol in UL- PRS. Relative RE offsets of subsequent symbols are defined relative to the comb offset of first symbol.
  • an UL-PRS resource can span 1, 2, 4, 8, or 12 adjacent OFDM symbols in one slot (i.e., number of consecutive OFDM symbols in an SRS resource is configurable with one of the values in the set ⁇ 1, 2, 4, 8, 12 ⁇ ), which can be transmitted anywhere in the slot (flexible starting point of UL SRS for positioning).
  • the UL-PRS comb size set is extended from ⁇ 2, 4 ⁇ for Rel-15 SRS, to ⁇ 2, 4, 8 ⁇ .
  • Rel-16 supports staggered comb patterns in a single SRS resource, which Rel-15 did not ( Figure 4). Rel-16 repetitions are very specific to the patterns specified by RE offsets for pairs of UL-PRS comb size and number of symbols as shown in Table 1.
  • RE pattern of an UL-PRS is configured with a comb offset for the 1 st symbol in an SRS resource, and relative RE offsets (for other symbols) are defined relative to the comb offset of the 1 st symbol in the SRS resource ( Figure 5).
  • the number of repetitions is not separately configured for SRS for positioning; rather, it is realized by the configured number of SRS symbols and the comboffset sequence as shown in Table 1.
  • SRS UL-PRS
  • a device can be configured with one or more UL-PRS Resource Sets (by higher layer parameter SRS-ResourceSet or SRS-PosResourceSet), that can be used for different purposes.
  • Each UL-PRS Resource Set can include one or more UL-PRS Resources.
  • SRS is configured with the higher layer parameter SRS-PosResourceSet-rl6
  • a UE may be configured with SRS resources (higher layer parameter SRSPosResource-rl6), where the maximum value of K is 16.
  • the SRS is identified, separately, i.e., it is a different configuration. This means that although positioning uses SRS, in the configuration itself, the purpose is distinguished by the signaling.
  • up to 16 SRS resource sets can be configured to a UE [TS 38.331],
  • an UL-PRS can be configured for periodic, semi-periodic, and aperiodic transmission.
  • periodicities of ⁇ 1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560 ⁇ slots periodicities of ⁇ 5120, 10240, 20480, 40960, 81920 ⁇ slots are supported for UL-PRS:
  • Periodicity of 20480 slots is applicable for 30, 60 and 120 kHz SCS only;
  • Periodicity of 40960 slots is applicable for 60 and 120 kHz SCS only;
  • Periodicity of 81920 slots is applicable for 120 kHz SCS only.
  • UL-PRS resource set (and hence, all its UL-PRS resources) can have a periodic pattern, with periodicity depending on the SCS.
  • Lor SP SRS for positioning configuration with MAC CE activation/deactivation is supported, with SRS to be received at the serving cell and neighbor cell.
  • Aperiodic SRS for positioning is triggered by a DCI, with no impact to Rel-15 DCI (the triggers in place in Rel-15 are reused).
  • Periodic, semi-persistent or aperiodic UL-PRS transmission is a property of an UL-PRS Resource Set, i.e., all UL-PRS Resources included within an ULPRS Resource Set are of the same type.
  • UL-PRS Resource Set Another property of UL-PRS Resource Set is the Tx power control (PC).
  • PC Tx power control
  • Lor UL-PRS, only open-loop (OL) PC is supported, including support for (fractional) pathloss compensation to serving and neighboring TRPs.
  • the UE estimates UL pathloss for serving and neighboring TRPs based on DL measurements and sets UL-PRS Tx power accordingly.
  • the UE may estimate the pathloss from a DL RS, which may be an SSB or DL-PRS not only from the serving TRP but also from neighbor TRPs ( Figure 6).
  • DL pathloss estimate based on serving TRP may result in too small of Tx power for UL- PRS to be detectable at the neighbor TRPs (UL hearability).
  • the pathloss estimate based on an RS from neighbor TRPs can be used to transmit UL-PRS with an appropriate power towards the intended TRPs. That is, a smaller pathloss estimate results in higher UL-PRS transmit power towards the intended TRP.
  • the UE can be configured with different SRS instances, each with independent power control loops. This allows an SRS pointed at neighbor cells to have better hearability and keeps the interference low in the serving cell. Assistance information is provided if SSB/DL PRS is used for pathloss estimation.
  • PC parameters are part of the SRS resource set configuration, all resources in a set, should have same PC parameters.
  • cyclic shift for generating the reference sequence e.g., Comb 2 supports 8 cyclic shifts and Comb 4 supports 12 cyclic shifts
  • Frequency Domain Shift defining frequency domain position of UL-PRS Resource (same as for Rel-15 SRS)
  • Frequency Hopping defining bandwidth of UL-PRS Resource.
  • the name is reused from Rel-15 SRS, although frequency hopping for UL-PRS is not supported. However, part of the frequency hopping parameter is BW indication, which is the only parameter applicable for UL-PRS
  • Group or Sequence Hopping defining whether group or sequence of hopping is used (same as for Rel-15 SRS). The hopping modes are used to randomize the reuse of a sequence in the system • Resource Type', defining UL-PRS Resource type (periodic, semi-pers, aperiodic) & periodicity for semi-persistent & periodic UL-PRS
  • Sequence ID defining a UE specific sequence ID used to initialize PN group and sequence hopping.
  • #diff erent sequence group hopping pattern is increased from 1024 (Rel-15 SRS) to 65536, and number of bits for sequence ID is increased to 16.
  • #UL-PRS to be received by neighboring TRPs increasing available #UL-PRS sequences can be beneficial for reducing UL-PRS collision & further mitigating UL interference
  • the reference RS can be an SSB, CSLRS (for serving cell only), DL-PRS, SRS or UL-PRS.
  • UL-PRS Resource Set Identity SRS-PosResourceSetld in the specification: defining particular UL-PRS Resource Set. It is unique in the context of the BWP in which the UL- PRS is defined.
  • Resource Type defining time domain behavior of UL-PRS resource configuration.
  • the network configures UL-PRS Resources in the same Resource Set with the same time domain behavior on periodic, aperiodic & semi-persistent. This means that the periodicity values are configured for the set, and different resources within the set cannot have different periodicities.
  • a UE is not expected to be configured with SRS resources in the same SRS resource set SRS-ResourceSet or SRS-PosResourceSet-rl6 with different slot level periodicities.
  • Alpha a value for the UL-PRS power control: defining the fractional pathloss compensation.
  • the alpha value is multiplied by the UE with the pathloss estimate.
  • alpha is equal to 1.
  • the UL-PRS Tx power determination is based on pO + alpha ⁇ PL, where PL is the pathloss estimate
  • Pathloss Reference RS defining the reference DL signal to be used for pathloss estimation.
  • the DL reference signal can be an SSB or DL-PRS from the serving or neighboring TRP
  • AoA is angle of arrival for signal transmitted by UE relative to either a global reference or geographical North pole and the zenith, or relative to a local coordinate system. In a fixed- beam system this in practice corresponds to the direction of the beam receiving the signal
  • SRS-RSRP SRS received power
  • Table 2 provides information in terms of mapping between UL PRS and gNB measurements. Positioning techniques are also indicated for information purpose only.
  • DL TDOA DL time difference of arrival
  • UL TDOA UL time difference of arrival
  • DL angle of departure This method makes use of the DL PRS-RSRP measurements made on signals received from multiple gNBs along with knowledge of the spatial information of the DL radio signals and geographical coordinates of the gNBs to determine the position of the UE.
  • UL AoA UL angle of arrival
  • Multi-round trip time With this method the UE position is estimated based on measurements made at both the UE and the gNB. These measurements are (a) UE Rx- Tx and DL PRS-RSRP of signals received at the UE from multiple gNBs and (b) gNB Rx- Tx and UL SRS-RSRP of signals received at the multiple gNBs from the UE.
  • NR Rel-16 positioning specification supports multiple interference management techniques:
  • PRSs on both UL and DL directions, are orthogonalized in code, frequency, and time domains
  • both UL and DL PRSs can be configured (among interfering nodes) using different frequency-domain comb-factors
  • Both DL-PRS and UL-PRS can also serve as spatial quasi co-location (QCL) references to establish positioning beam pairs. That is, given the knowledge of a suitable RX beam for DL- PRS, the RX knows that the same RX beam should be suitable for UL-PRS.
  • Spatial relation indication for UL-PRS Resources is supported, either to a DL RS (SSB, CSLRS (for serving cell only) or DL-PRS) or UE’s previously transmitted SRS or UL-PRS.
  • the UL-PRS beam may be derived from the spatial relation to an indicated DL RS, whereupon UE may transmit UL-PRS in the reciprocal direction to how it set its RX beam when receiving the DL RS, as illustrated.
  • An additional procedure may be used by the network, where UE transmits an UL-PRS or SRS beam sweep & gNB refers back to one of the swept beams in a previously transmitted UL-PRS or SRS resource to indicate spatial relation to UL-PRS resource.
  • UL-PRS can have a spatial relation to a neighbor TRP (Ligure 8). Lor positioning, UL-PRS generally needs to be received also by neighboring TRPs.
  • NR UEs supporting mmWave typically include multiple antenna panels pointing in different directions.
  • the spatial relation for both serving and neighboring TRPs is primarily used to indicate which UL TX beam UE may use for UL-PRS.
  • the UE may receive a RS for the UL-PRS beam from the same direction as that of UL-PRS desired direction.
  • the RS from a neighbor TRP may be an SSB or DL-PRS.
  • an SRS resource set there is flexibility for spatial allocations. Particularly, there can be different resources (beams) within a set.
  • the current SRS design enables the possibility to repeat some directions more often than others. Even though all resources of a set repeat by the same periodicity, but within a resource, (e.g., for comb-2/2-OS), 1 or 2 or 4 or 6 repetitions can take place, which provides additional flexibility.
  • multiple SRS resource sets may be configured to a UE, which may allow different beamforming across the different sets. For instance, a set of narrow beams to cover a region that is mapped to one set, and another set of wider beams to target a slightly different coverage that can be mapped to the second resource set.
  • this design aspect may also have application in realizing sub- slot- level SRI durations, as will be disclosed later.
  • this concept may be reused to define multiple sensing frames (together with their corresponding SRI settings) (e.g., to benefit from different measurements and/or different levels of dynamicity in different parts of the environment/FoV). Multiple sensing frames could be defined using SP SRS setting and the appropriate frame can be activated by MAC CE in dynamic fashion. This would be useful because the UE could dynamically be assigned different SRS settings, e.g. for different SRIs, etc.
  • Embodiment Reuse of UL-PRS signal for sensing (UL-PRS signal resource structure from the sensing point of view)
  • UL-PRS has features that are desired for sensing.
  • UL-PRS have certain regularities and attributes, and the supported patterns are in synergy with sensing signal attributes.
  • Example 1 Mapping UL-PRS attributes to sensing signal desired attributes - Analogies between UL-PRS and sensing signal attributes
  • UL-PRS resource sensing beam for UL-based positioning, single port UL-PRS resource is supported, i.e., each UL-PRS resource is dedicated for transmission in a single direction).
  • a resource corresponds to an SRS beam, and resource sets correspond to a collection of SRS resource (i.e., beams) aimed at a given TRP.
  • the number of PRS resources within a PRS resource set the number of beam directions in SRI. This is also related to the number of OLDM symbols in each SRS resource of the set and how they are located. Lor sensing, smaller comb- sizes are preferred, because compared to the larger size combs, they utilize more SC and provide more intra-SRI flexibility of assigning OLDM symbols to different directions and/or for different purposes (UL-PRS vs non-PRS), while also imposes less limitation on the maximum unambiguously detectable range.
  • each symbol within SRI can be allocated to a different beam/direction and in an SRS resource set, multiple SRS resources, each for one direction is transmitted.
  • the entire time interval which contains repetitions of resource set with its periodicity (i.e., repetitions of SRI - k*SRI) sensing block - possible durations is based on network configuration.
  • Example 2 One-direction sensing via UL-PRS
  • one UL-PRS resource i.e., one beam direction
  • repetitions of that resource for Doppler estimation is required.
  • UL-PRS-based sensing it is important to understand that with proper UL-PRS configurations, how frequent the occurrence of one direction can be for Doppler processing, and with what granularity time/frequency resources for that direction can be configured.
  • a look into slot-level supported patterns of UL-PRS resources shows that within a slot, there can exist one or multiple UL-PRS resources (of one or multiple resource sets), each with or without intra-resource-level repetition.
  • Lor example it is possible that multiple UL-PRS resources, e.g., each of length 2 OS, are Time-Domain-Multiplexed (TDMed) within one resource set of length one slot.
  • TDMed Time-Domain-Multiplexed
  • SRIs of length 70S or 14OS or 28OS would be needed (at least for certain UCs which does not require extremely high speeds).
  • SRIs durations of integer number of slots can be achieved straightforwardly, since the minimum periodicity of one slot is supported.
  • the current UL-PRS resource settings may have some limitations, as will be discussed and addressed.
  • SRI duration of integer multiples of slot (minimum of one-slot SRI duration)
  • different SRI durations can be defined.
  • Lor example with a periodicity of 1 slot, and all SRS resources of the set also packed next to each other within a slot, e.g., each UL-PRS resource is 1-12 OLDM symbols, an SRI duration of one slot can be achieved.
  • an SRI of 2 slots With a periodicity of 2 slots, and all SRS resources of the set are also packed next to each other within a slot, an SRI of 2 slots can be achieved wherein only within the first slot of the SRI, the sensing transmission takes places. The same logic applies for larger periodicities, leading to lower Doppler/speed detection.
  • In NR UL-PRS design in each slot, (at least) two symbols are not used for PRS transmission and are reserved for other communication channels.
  • sub- slot level SRI duration For sub- slot level SRI duration, one needs to properly handle the non-UL-PRS symbols and deal with such minimum gap within the UL-PRS slot. Otherwise, for sensing, in case of subslot level SRI, this can cause irregularities across SRIs, which is not desired (since inconsistencies across SRIs troubles the repetition and Doppler FFT processing).
  • the same number and allocation of OFDM symbols across all SRIs should be considered for non-UL-PRS transmissions, to realize sub- slot- level (e.g., half-slot) SRI.
  • each half slot can form an SRI over different UL-PRS resource sets.
  • the two PRS resources sets each in a half- slot should be configured with similar pattern and number of PRS resources, covering same spatial domains, to maintain the consistency across SRIs.
  • the durations are either 2, 4, 6, or 12 ‘consecutive’ symbols. It is not possible to have two symbols of a 4-OS comb-2 UL-PRS resource in the first half of the slot, and the other two symbols in the second half. These limitations need to be to take into consideration and be dealt with, properly.
  • multiple UL-PRS resources i.e., multiple beam directions, and repetitions of those resource for Doppler estimation is required.
  • repetition of each beam is mainly for processing gain within the SRI, not for Doppler estimation.
  • SRI can be defined differently.
  • SRI durations of integer multiples of slots similar to the one-directional sensing case, if multiple PRS resources of the same resource set are TDMed within one slot, and if all resources of a set fit in a slot, the minimum SRI duration of one slot would be achieved. Depending also on the periodicity set for the set, different SRI durations can be defined.
  • an SRS resource set contains resources over multiple slots, either one slot per resource, or mix of slots with single and multiple resources, SRIs over multiple slots can be also defined, effectively for lower Doppler estimations.
  • Embodiment Expansions, and adaptations to UL-PRS for reuse in sensing
  • SRS UL-PRS
  • SRS UL-PRS
  • SRS UL-PRS
  • a new sensing signal is defined in the next generation of cellular systems, likely it can be also used for positioning, especially, if the design accommodates backward compatibility. From the resource efficiency and overhead perspective, it may not be desired to have separate positioning signal and sensing signal being transmitted in the system (at least at the same time), as much as possible. Motivated by the same reason, it is also logical to adapt the positioning reference signal to accommodate the sensing needs as much as possible.
  • the JCAS system can support both UE-based monostatic sensing and gNB-based bi-static sensing (UE being the UL-PRS signal transmitter, and gNB being UL-PRS signal sensing receiver), as well as gNB-based positioning (refer to Section 2, for more background).
  • Comb-1 means use of consecutive subcarriers over the OFDM symbol (extension to allow use of consecutive subcarriers over one symbol; examples may include single symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS (SRS) resource).
  • SRS UL-PRS
  • different sets of subcarriers e.g., realized with different frequency domain RE offsets
  • the interference from the signals used for sensing from the close-by UEs.
  • there are different approaches to mitigate interference e.g., by leveraging multiplexing in time, frequency, code, and/or sequence domain.
  • a combination of different approaches may be accommodated and supported by the design, yet this is out of the scope of the current disclosure.
  • Partially staggered patterns for UL-PRS signals that may be defined by M-level comb and N symbols for a UL-PRS resource with M > N.
  • Unstaggered patterns for UL-PRS signals such that the same REs are used in consecutive symbols within an UL-PRS resource; examples may include:
  • Extending configuration to allow for a slot being fully occupied by UL-PRS resources from one or multiple sets i.e., possible to have zero resources for non-UL-PRS purposes in a slot.
  • the minimum of 2 non-PRS OFDM symbols in UL-PRS slots e.g., the maximum duration of SRS resource is 12OS
  • SRS resource is 12OS
  • Multi-port transmission may allow for sending multiple beams at different directions at the same time. For example, even currently, for channel reciprocity-based use cases with 2-port 4-port SRS resource configuration, the UE can sound simultaneously on 2 or 4 ports (i.e., in multiple directions), respectively.
  • Extending configuration to allow inconsecutive (and preferably, symmetric over the two half-slots) allocation of OFDM symbols per PRS resource within a slot For example, a comb-2 UL-PRS resource of length 4, may be realized with an equal split of the 4 symbols over two 2- symbol occurrences each in one half-slot. Especially, this enables realizing sub-slot-level SRI duration (e.g., half-slot), using one UL-PRS resource set. Inconsecutive allocation of OFDM symbols for one UL-PRS resource, may be achieved by different means, e.g., through enabling configuration of the PRS resource symbol offset by a vector, etc.
  • Extending configuration to allow configurations of periodicity at the granularity of UL- PRS resource (e.g., per UL-PRS resource) as against defining them at the set level.
  • different resources within the set are able to have different periodicities, to help better spatial adjustments to cover the field of view. This helps with realizing different SRI durations for different beam directions in the FoV. Otherwise, different sets are needed to cover the FoV, e.g., each set covering the directions (SRS resources) with the same required SRI, which may lead to excessive configuration signaling.
  • a UE is not expected to be configured with SRS resources in the same SRS resource set SRS-ResourceSet or SRS-PosResourceSet-rl6 with different slot level periodicities.
  • Extending configuration to allow the periodicity of half-slot, as well (e.g., for higher speed UCs, etc.).
  • FoV For sensing it may be desired (e.g., depending on the use-case and its requirements) to gather a full scan of FoV within a short time and then wait for a longer period of time before starting another scan. This may allow for the highest possible velocity detection without blurring.
  • the scanning can be performed at a slower rate (e.g., with larger SRIs) when no fast-moving objects are expected.
  • Extending configuration to allow for multiple levels of scan rate configurations (to allow multiple/diff erent repetition patterns and update rates), to enable a fast scan rate for rapidly gathering a number of UL-PRS resources, followed by a slower scan rate to enable a waiting period for dedicated communications before the next rapid period.
  • SRS UL-PRS
  • the current SRS resource set configurations may be limited to combs applied mainly to the small portion of the OFDM symbols within the slot (typically the latter symbols). It would be ideal for sensing to attain a burst with each slot nearly full of sensing combs, to get all of the needed sensing performed quickly.
  • the purpose of this extension is to ensure that any new UL-PRS can accommodate the need for sensing to gather the full FoV scan rapidly, allowing optimal Doppler detection, rather than slowly attaining the FoV scan as may occur in a background process.
  • Extending configuration to allow for a fully programmable rapid burst of UL-PRS transmissions/acquisitions.
  • the burst of transmissions/acquisitions may need to occur at a faster rate than DCI updates, so it may require to contain all of the necessary parameters without a need for interruption by DCI or RRC re-configuration.
  • Rate of transmission/acquisition, number of transmissions/acquisitions, as well as the normal UL-PRS parameters such as OLDM symbol position within RB, comb size, and cyclic offset need to be set independently for the burst of transmissions/acquisitions.
  • Extending configuration to allow different power control parameters for resources within a set i.e., to allow PC configuration per UL-PRS resource (beam).
  • Extending configuration to allow multiple (two or more) UL-PRS resource sets with potentially same resource settings within the sets at least for certain parameters (e.g., same time/frequency domain placement, same spatial configuration of resources, same resource pattern, etc., except for the configuration defining the starting time location of the resources), which can be TDMed even within one slot, to enable realizing different (e.g., two or more) SRIs using different (e.g., two or more) sets, and their repetitions.
  • certain parameters e.g., same time/frequency domain placement, same spatial configuration of resources, same resource pattern, etc., except for the configuration defining the starting time location of the resources
  • this extension enables realizing sub-slot-level SRI duration (e.g., half-slot), or SRIs of durations of non-integer multiple of slots (e.g., 1.5 slot, etc.), using two or more UL-PRS resource sets.
  • sub-slot-level SRI duration e.g., half-slot
  • SRIs of durations of non-integer multiple of slots e.g., 1.5 slot, etc.
  • the starting symbol offset within a slot, and (if needed) the numbers of symbols for an UL-PRS resource may be configured differently for the two/multiple resource sets that may share other parameters commonly.
  • SRI duration of integer multiples of slot minimum of one-slot SRI duration
  • SRI duration can be defined depending on the periodicity and number and durations and placements of the resources in a set. For example, with a periodicity of 1 slot, and all UL-PRS resources of the set also packed next to each other within a slot, an SRI duration of one slot can be achieved.
  • two sets may be configured, with common configuration of UL-PRS resources (e.g., except for the configuration defining the time location of the resources) and covered beam directions, and every other SRI is realized using one set, with a periodicity of 2 slots.
  • this concept may be reused to define multiple sensing frames (together with their corresponding SRI settings) (e.g., to benefit from different measurements and/or different levels of dynamicity in different parts of the environment/FoV).
  • Extending the UL-PRS configuration to also allow repeating the entire periodic occurrence of a set over certain configured duration (as per extension of Example 13), with a configurable number of slots (> 0) as a gap in between the repetitions.
  • This realizes a configurable update rate.
  • This configuration can be indicated by RRC signaling, MAC CE, or DCI (the latter for more flexibility and less latency).
  • the entire periodic occurrence of a set over certain configured duration may occur irregularly based on some indications/triggers (i.e., the intervals with the configured durations, can re-occur (start/stop) based on indications). This results in periodic/semi-periodic/aperiodic nature of the entire burst (a burst is a sensing block of Doppler FFT x SRI duration).
  • SRS is identified separately, i.e., it is a different configuration. This means that although positioning uses SRS, but in the configuration itself, the purpose is distinguished.
  • extensions of UL-PRS for the purpose of sensing may also be configured using separate parameters, which imply sensing usage.
  • a “sensing” usage may be defined, similar to “beam management”, “antenna switching”, etc.
  • different sensing usages may be defined, corresponding to different categories of UCs which require different measurements/processing. Accordingly, for each usage, different measurements may also be expected.
  • channel measurements may be performed (and may be reported) by the sensing receiver.
  • the JCAS system can support both UE-based monostatic sensing and gNB-based bi-static sensing (UE being the UL-PRS signal transmitter, and gNB being UL-PRS signal sensing receiver), as well as gNB- based positioning.
  • UE being the UL-PRS signal transmitter
  • gNB being UL-PRS signal sensing receiver
  • the methods for interference handling between signals from different UEs are also applicable for UL-PRS-based sensing scenarios.
  • the UE’s transmit power may not need to be different compared to the case of positioning/communication, since the [sensing] signal travels the same distance between the sensing TX and RX nodes, as for the case of positioning/communication. Accordingly, the existing techniques for interference handling can be adequate also for the case of sensing.
  • Embodiment Enabling speed and/or direction related measurements to allow velocity estimation in localization/positioning
  • IDF AE8858 Numerology, frame structure, and signal resource dimensioning for joint communication and sensing systems
  • FIG. 9 illustrates a network 900 in accordance with various embodiments.
  • the network 900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with a RAN 904 via an over-the-air connection.
  • the UE 902 may be communicatively coupled with the RAN 904 by a Uu interface.
  • the UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 900 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 902 may additionally communicate with an AP 906 via an over-the-air connection.
  • the AP 906 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 904.
  • the connection between the UE 902 and the AP 906 may be consistent with any IEEE 802.11 protocol, wherein the AP 906 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 902, RAN 904, and AP 906 may utilize cellular- WLAN aggregation (for example, LWA/LWIP).
  • Cellular- WLAN aggregation may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.
  • the RAN 904 may include one or more access nodes, for example, AN 908.
  • AN 908 may terminate air-interface protocols for the UE 902 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 908 may enable data/voice connectivity between CN 920 and the UE 902.
  • the AN 908 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 908 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the AN 908 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 904 may be coupled with one another via an X2 interface (if the RAN 904 is an LTE RAN) or an Xn interface (if the RAN 904 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 904 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 902 with an air interface for network access.
  • the UE 902 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 904.
  • the UE 902 and RAN 904 may use carrier aggregation to allow the UE 902 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG.
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 904 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 902 or AN 908 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 904 may be an LTE RAN 910 with eNBs, for example, eNB 912.
  • the LTE RAN 910 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc.
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE.
  • the LTE air interface may operating on sub-6 GHz bands.
  • the RAN 904 may be an NG-RAN 914 with gNBs, for example, gNB 916, or ng-eNBs, for example, ng-eNB 918.
  • the gNB 916 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 916 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 918 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface.
  • the gNB 916 and the ng-eNB 918 may connect with each other over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 914 and a UPF 948 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN914 and an AMF 944 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 914 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking.
  • the 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • the 5G-NR air interface may utilize BWPs for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 902 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 902, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 902 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 902 and in some cases at the gNB 916.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
  • the RAN 904 is communicatively coupled to CN 920 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 902).
  • the components of the CN 920 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 920 may be referred to as a network sub-slice.
  • the CN 920 may be an LTE CN 922, which may also be referred to as an EPC.
  • the LTE CN 922 may include MME 924, SGW 926, SGSN 928, HSS 930, PGW 932, and PCRF 934 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 922 may be briefly introduced as follows.
  • the MME 924 may implement mobility management functions to track a current location of the UE 902 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 926 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 922.
  • the SGW 926 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 928 may track a location of the UE 902 and perform security functions and access control. In addition, the SGSN 928 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 924; MME selection for handovers; etc.
  • the S3 reference point between the MME 924 and the SGSN 928 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 930 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 930 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 930 and the MME 924 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 920.
  • the PGW 932 may terminate an SGi interface toward a data network (DN) 936 that may include an application/content server 938.
  • the PGW 932 may route data packets between the LTE CN 922 and the data network 936.
  • the PGW 932 may be coupled with the SGW 926 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 932 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • PCEF policy enforcement and charging data collection
  • the SGi reference point between the PGW 932 and the data network 9 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services.
  • the PGW 932 may be coupled with a PCRF 934 via a Gx reference point.
  • the PCRF 934 is the policy and charging control element of the LTE CN 922.
  • the PCRF 934 may be communicatively coupled to the app/content server 938 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 932 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 920 may be a 5GC 940.
  • the 5GC 940 may include an AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, and AF 960 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 940 may be briefly introduced as follows.
  • the AUSF 942 may store data for authentication of UE 902 and handle authentication- related functionality.
  • the AUSF 942 may facilitate a common authentication framework for various access types.
  • the AUSF 942 may exhibit an Nausf service-based interface.
  • the AMF 944 may allow other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and to subscribe to notifications about mobility events with respect to the UE 902.
  • the AMF 944 may be responsible for registration management (for example, for registering UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 944 may provide transport for SM messages between the UE 902 and the SMF 946, and act as a transparent proxy for routing SM messages.
  • AMF 944 may also provide transport for SMS messages between UE 902 and an SMSF.
  • AMF 944 may interact with the AUSF 942 and the UE 902 to perform various security anchor and context management functions.
  • AMF 944 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 904 and the AMF 944; and the AMF 944 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 944 may also support NAS signaling with the UE 902 over an N3 IWF interface.
  • the SMF 946 may be responsible for SM (for example, session establishment, tunnel management between UPF 948 and AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 948 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 944 over N2 to AN 908; and determining SSC mode of a session.
  • SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 902 and the data network 936.
  • the UPF 948 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 936, and a branching point to support multi-homed PDU session.
  • the UPF 948 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 948 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 950 may select a set of network slice instances serving the UE 902.
  • the NSSF 950 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed.
  • the NSSF 950 may also determine the AMF set to be used to serve the UE 902, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 954.
  • the selection of a set of network slice instances for the UE 902 may be triggered by the AMF 944 with which the UE 902 is registered by interacting with the NSSF 950, which may lead to a change of AMF.
  • the NSSF 950 may interact with the AMF 944 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 950 may exhibit an Nnssf service-based interface.
  • the NEF 952 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 960), edge computing or fog computing systems, etc.
  • the NEF 952 may authenticate, authorize, or throttle the AFs.
  • NEF 952 may also translate information exchanged with the AF 960 and information exchanged with internal network functions. For example, the NEF 952 may translate between an AF-Service-Identifier and an internal 5GC information.
  • NEF 952 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 952 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 952 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 952 may exhibit an Nnef service-based interface.
  • the NRF 954 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 954 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 954 may exhibit the Nnrf service-based interface.
  • the PCF 956 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior.
  • the PCF 956 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 958.
  • the PCF 956 exhibit an Npcf service-based interface.
  • the UDM 958 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 902. For example, subscription data may be communicated via an N8 reference point between the UDM 958 and the AMF 944.
  • the UDM 958 may include two parts, an application front end and a UDR.
  • the UDR may store subscription data and policy data for the UDM 958 and the PCF 956, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 902) for the NEF 952.
  • the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 958, PCF 956, and NEF 952 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 958 may exhibit the Nudm service-based interface.
  • the AF 960 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 940 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 902 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 940 may select a UPF 948 close to the UE 902 and execute traffic steering from the UPF 948 to data network 936 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 960 to interact directly with relevant NFs. Additionally, the AF 960 may exhibit an Naf service-based interface.
  • the data network 936 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 938.
  • FIG 10 schematically illustrates a wireless network 1000 in accordance with various embodiments.
  • the wireless network 1000 may include a UE 1002 in wireless communication with an AN 1004.
  • the UE 1002 and AN 1004 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 1002 may be communicatively coupled with the AN 1004 via connection 1006.
  • the connection 1006 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
  • the UE 1002 may include a host platform 1008 coupled with a modem platform 1010.
  • the host platform 1008 may include application processing circuitry 1012, which may be coupled with protocol processing circuitry 1014 of the modem platform 1010.
  • the application processing circuitry 1012 may run various applications for the UE 1002 that source/sink application data.
  • the application processing circuitry 1012 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry 1014 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1006.
  • the layer operations implemented by the protocol processing circuitry 1014 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
  • the modem platform 1010 may further include digital baseband circuitry 1016 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1014 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may
  • the modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and RF front end (RFFE) 1024, which may include or connect to one or more antenna panels 1026.
  • the transmit circuitry 1018 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry 1020 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 1022 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 1024 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
  • the protocol processing circuitry 1014 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 1026, RFFE 1024, RF circuitry 1022, receive circuitry 1020, digital baseband circuitry 1016, and protocol processing circuitry 1014.
  • the antenna panels 1026 may receive a transmission from the AN 1004 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1026.
  • a UE transmission may be established by and via the protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panels 1026.
  • the transmit components of the UE 1004 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1026.
  • the AN 1004 may include a host platform 1028 coupled with a modem platform 1030.
  • the host platform 1028 may include application processing circuitry 1032 coupled with protocol processing circuitry 1034 of the modem platform 1030.
  • the modem platform may further include digital baseband circuitry 1036, transmit circuitry 1038, receive circuitry 1040, RF circuitry 1042, RFFE circuitry 1044, and antenna panels 1046.
  • the components of the AN 1004 may be similar to and substantially interchangeable with like- named components of the UE 1002.
  • the components of the AN 1008 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • Figure 11 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • Figure 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors (or processor cores) 1110, one or more memory/storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry.
  • a hypervisor 1102 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 1100.
  • the processors 1110 may include, for example, a processor 1112 and a processor 1114.
  • the processors 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
  • the memory/storage devices 1120 may include main memory, disk storage, or any suitable combination thereof.
  • the memory/storage devices 1120 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory
  • SRAM static random access memory
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • Flash memory solid-state storage, etc.
  • the communication resources 1130 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 or other network elements via a network 1108.
  • the communication resources 1130 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.
  • Instructions 1150 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1110 to perform any one or more of the methodologies discussed herein.
  • the instructions 1150 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor’s cache memory), the memory/storage devices 1120, or any suitable combination thereof. Furthermore, any portion of the instructions 1150 may be transferred to the hardware resources 1100 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of processors 1110, the memory/storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.
  • Figure 12 illustrates a network 1200 in accordance with various embodiments.
  • the network 1200 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems.
  • the network 1200 may operate concurrently with network 900.
  • the network 1200 may share one or more frequency or bandwidth resources with network 900.
  • a UE e.g., UE 1202
  • UE 1202 may be configured to operate in both network 1200 and network 900.
  • Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 900 and 1200.
  • several elements of network 1200 may share one or more characteristics with elements of network 900. For the sake of brevity and clarity, such elements may not be repeated in the description of network 1200.
  • the network 1200 may include a UE 1202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1208 via an over-the-air connection.
  • the UE 1202 may be similar to, for example, UE 902.
  • the UE 1202 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
  • the network 1200 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 1202 may be communicatively coupled with an AP such as AP 906 as described with respect to Figure 9.
  • the RAN 1208 may include one or more ANss such as AN 908 as described with respect to Figure 9.
  • the RAN 1208 and/or the AN of the RAN 1208 may be referred to as a base station (BS), a RAN node, or using some other term or name.
  • the UE 1202 and the RAN 1208 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface.
  • the 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing.
  • THz terahertz
  • sub-THz bandwidth may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing.
  • THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.
  • the RAN 1208 may allow for communication between the UE 1202 and a 6G core network (CN) 1210. Specifically, the RAN 1208 may facilitate the transmission and reception of data between the UE 1202 and the 6G CN 1210.
  • the 6G CN 1210 may include various functions such as NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, AF 960, SMF 946, and AUSF 942.
  • the 6G CN 1210 may additional include UPF 948 and DN 936 as shown in Figure 12.
  • the RAN 1208 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network.
  • Two such functions may include a Compute Control Function (Comp CF) 1224 and a Compute Service Function (Comp SF) 1236.
  • the Comp CF 1224 and the Comp SF 1236 may be parts or functions of the Computing Service Plane.
  • Comp CF 1224 may be a control plane function that provides functionalities such as management of the Comp SF 1236, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc..
  • Comp SF 1236 may be a user plane function that serves as the gateway to interface computing service users (such as UE 1202) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1236 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1236 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1224 instance may control one or more Comp SF 1236 instances.
  • Two other such functions may include a Communication Control Function (Comm CF) 1228 and a Communication Service Function (Comm SF) 1238, which may be parts of the Communication Service Plane.
  • the Comm CF 1228 may be the control plane function for managing the Comm SF 1238, communication sessions creation/configuration/releasing, and managing communication session context.
  • the Comm SF 1238 may be a user plane function for data transport.
  • Comm CF 1228 and Comm SF 1238 may be considered as upgrades of SMF 946 and UPF 948, which were described with respect to a 5G system in Figure 9.
  • the upgrades provided by the Comm CF 1228 and the Comm SF 1238 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 946 and UPF 948 may still be used.
  • Data CF 1222 may be a control plane function and provides functionalities such as Data SF 1232 management, Data service creation/configuration/releasing, Data service context management, etc.
  • Data SF 1232 may be a user plane function and serve as the gateway between data service users (such as UE 1202 and the various functions of the 6G CN 1210) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.
  • SOCF 1220 may discover, orchestrate and chain up communication/computing/data services provided by functions in the network.
  • SOCF 1220 may interact with one or more of Comp CF 1224, Comm CF 1228, and Data CF 1222 to identify Comp SF 1236, Comm SF 1238, and Data SF 1232 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1236, Comm SF 1238, and Data SF 1232 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain.
  • the SOCF 1220 may also responsible for maintaining, updating, and releasing a created service chain.
  • SRF 1214 may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 1236 and Data SF 1232 gateways and services provided by the UE 1202.
  • the SRF 1214 may be considered a counterpart of NRF 954, which may act as the registry for network functions.
  • eSCP evolved service communication proxy
  • SCP service communication proxy
  • eSCP-U 1234 service communication proxy
  • SICF 1226 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.
  • the AMF 1244 may be similar to 944, but with additional functionality. Specifically, the AMF 1244 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1244 to the RAN 1208.
  • SOEF service orchestration exposure function
  • the SOEF may be configured to expose service orchestration and chaining services to external users such as applications.
  • the UE 1202 may include an additional function that is referred to as a computing client service function (comp CSF) 1204.
  • the comp CSF 1204 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1220, Comp CF 1224, Comp SF 1236, Data CF 1222, and/or Data SF 1232 for service discovery, request/response, compute task workload exchange, etc.
  • the Comp CSF 1204 may also work with network side functions to decide on whether a computing task should be run on the UE 1202, the RAN 1208, and/or an element of the 6G CN 1210.
  • the UE 1202 and/or the Comp CSF 1204 may include a service mesh proxy 1206.
  • the service mesh proxy 1206 may act as a proxy for service-to- service communication in the user plane. Capabilities of the service mesh proxy 1206 may include one or more of addressing, security, load balancing, etc.
  • the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 9-12, or some other figure herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof.
  • One such process is depicted in Figure 13.
  • the process may relate to a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include and/or implement a base station.
  • the process may include receiving, at 1301 from a user equipment (UE), an uplink positioning reference signal (UL-PRS); and performing, at 1302, sensing based on the UL-PRS.
  • UE user equipment
  • U-PRS uplink positioning reference signal
  • the process of Figure 14 may relate to a method to be performed by a user equipment (UE), one or more elements of a UE, and/or one or more electronic devices that include or implement a UE.
  • the process may include identifying, at 1401, one or more sensing-related parameters; generating, at 1402 based on the one or more sensing-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, at 1403 to a base station, the UL-PRS, wherein the base station is to use the UL-PRS for sensing.
  • UE user equipment
  • the process may include identifying, at 1401, one or more sensing-related parameters; generating, at 1402 based on the one or more sensing-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, at 1403 to a base station, the UL-PRS, wherein the base station is to use the UL-PRS for sensing.
  • UL-PRS uplink positioning reference signal
  • the process of Figure 15 may relate to a method to be performed by an electronic device (e.g., a user equipment (UE) in a cellular network.
  • the process may include identifying, at 1501, an uplink positioning reference signal (UL-PRS) resource related to sensing to be performed during a sensing operation, wherein a UL- PRS resource includes a plurality of UL-PRS symbols.
  • UL-PRS uplink positioning reference signal
  • the UL-PRS resource may be based on a fifth generation (5G) new radio (NR) sounding reference signal (SRS); generating, at 1502, a cellular transmission that includes a symbol repetition interval (SRI) composed of or based on the UL-PRS resource; and transmitting, at 1503, the cellular transmission during performance of the sensing operation.
  • 5G fifth generation
  • NR new radio
  • SRI symbol repetition interval
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • Example 1 may include an apparatus used in a sensing entity wherein the apparatus comprises processor circuitry configured to cause the sensing entity to map and transmit the modulated symbols, according to 5G NR Uplink (UL) Positioning Reference Signal (PRS) design, wherein the following equivalences are used (marked with ⁇ ->)
  • UL Uplink
  • PRS Positioning Reference Signal
  • UL-PRS resource sensing beam for UL-based positioning, single port UL-PRS resource is supported, i.e., each UL-PRS resource is dedicated for transmission in a single direction).
  • a resource corresponds to an SRS beam, and resource sets correspond to a collection of SRS resource (i.e., beams) aimed at a given TRP.
  • the number of PRS resources within a PRS resource set the number of beam directions in SRI. This is also related to the number of OFDM symbols in each SRS resource of the set and how they are located. For sensing, smaller comb- sizes are preferred, because compared to the larger size combs, they utilize more subcarriers and provide more intra-SRI flexibility of assigning OFDM symbols to different directions and/or for different purposes (UL-PRS vs non-PRS), while also imposes less limitation on the maximum unambiguously detectable range.
  • the entire time interval which contains repetitions of resource set with its periodicity (i.e., repetitions of SRI) sensing block - possible durations is based on network configuration. Across SRIs within a sensing block, the number and pattern of sensing resources and directions is configured the same to achieve consistent configuration of SRS resources in periodic occurrences of SRS resource sets. The same number and placement of OFDM symbols across all SRIs is also considered for non-PRS transmissions. The number of repetitions of SRS resource set Doppler FFT size, K.
  • Example 2 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration also allows single-symbol and three-symbol PRS resources.
  • Example 3 may include the apparatus of example 1 or some other example herein, wherein use of consecutive subcarriers over one OFDM symbol by UL-PRS or PRS-like signal is also supported, with or without repetitions within an UL-PRS resource.
  • Comb-1 means use of consecutive subcarriers over the OFDM symbol (extension to allow use of consecutive subcarriers over one symbol; examples may include single symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS (SRS) resource).
  • SRS UL-PRS
  • Example 4 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to support a comb size from of ⁇ 1, 2, 4, 8 ⁇ , or ⁇ 1, 2, 3, 4, 8 ⁇ , where comb-3 may be applicable to UL-PRS resource duration of 1 or 3 or 12 OS.
  • Example 5 may include the apparatus of example 5 or some other example herein, wherein different sets of subcarriers (e.g., realized with different frequency domain RE offsets), are used to handle the interference from the signals used for sensing, from the close-by UEs.
  • different sets of subcarriers e.g., realized with different frequency domain RE offsets
  • Example 6 may include the apparatus of example 1 or some other example herein, wherein use of partially staggered patterns for UL-PRS or PRS-like signals that may be defined by M-level comb and N symbols for an UL-PRS resource with M > N, is also supported.
  • Example 7 may include the apparatus of example 1 or some other example herein, wherein unstaggered patterns for UL-PRS or PRS-like signals are supported such that the same resource elements (REs) are used in consecutive symbols within an UL-PRS resource; examples may include:
  • Example 8 may include the apparatus of example 1 or some other example herein, wherein combinations of fully or partially staggered and unstaggered patterns for PRS or PRS- like signals are supported.
  • Example 9 may include the apparatus of example 1 or some other example herein, wherein use of all symbols within a slot for PRS allocation is supported, i.e., the configuration is extended to allow for a slot being fully occupied by UL-PRS resources from one or multiple sets (i.e., possible to have zero resources for non-UL-PRS purposes in a slot).
  • Example 10 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows accommodation of inconsecutive OFDM symbols (minimum of two inconsecutive symbols) for non-UL-PRS transmission within the PRS slot.
  • Example 11 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows multi-port UL-PRS resource transmission, enabling sending multiple beams at different directions at the same time.
  • Example 12 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow inconsecutive (and preferably, symmetric over the two half-slots) allocation of OFDM symbols per PRS resource within a slot, to enable realizing sub- slot- level SRI duration (e.g., half-slot), using one UL-PRS resource set.
  • a comb-2 UL-PRS resource of length 4 may be realized with an equal split of the 4 symbols over two 2-symbol occurrences each in one half-slot.
  • Inconsecutive allocation of OFDM symbols for one PRS resource may be achieved by different means, e.g., through enabling configuration of the PRS resource symbol offset by a vector, etc.
  • Example 13 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows configuring periodicity at the granularity of UL-PRS resource (e.g., per UL-PRS resource) as against defining them at the resource set level. As such, different resources within the set are able to have different periodicities, to help better spatial adjustments to cover the field of view.
  • UL-PRS configuration allows configuring periodicity at the granularity of UL-PRS resource (e.g., per UL-PRS resource) as against defining them at the resource set level.
  • Example 14 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows the periodicity of half-slot (e.g., for higher speed usecases, etc.).
  • Example 15 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows for multiple levels of periodicity control (to allow multiple/different repetition patterns), so as to enable a fast periodicity (scan rate) for rapidly gathering a number of UL-PRS resources, followed by a slower periodicity to enable a waiting period for dedicated communications before the next rapid period.
  • UL-PRS configuration allows for multiple levels of periodicity control (to allow multiple/different repetition patterns), so as to enable a fast periodicity (scan rate) for rapidly gathering a number of UL-PRS resources, followed by a slower periodicity to enable a waiting period for dedicated communications before the next rapid period.
  • Example 16 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows for a fully programmable rapid burst of UL-PRS transmissions/acquisitions.
  • the burst of transmissions/acquisitions needs to occur at a faster rate than DCI updates, so it must contain all of the necessary parameters without need for interruption by DCI or RRC re-configuration.
  • Rate of transmission/acquisition (the update rate for a full doppler FFT x SRI duration), number of transmissions/acquisitions, as well as normal UE-PRS parameters such as OFDM symbol position within RB, comb size, and cyclic offset need to be set independently for the burst of transmissions/acquisitions.
  • Example 17 may include the apparatus of example 1 or some other example herein, wherein UE-PRS configuration allows for different power control parameters for resources within a set, i.e., to allow PC configuration per UL-PRS resource (beam).
  • Example 18 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for multiple (two or more) UL-PRS resource sets with potentially same resource settings within the sets (i.e., same time/frequency domain placement, same spatial configuration of resources, same resource pattern, etc., potentially except for the configuration defining the starting time location of the resources), which can be TDMed even within one slot, to enable realizing different (e.g., two or more) Symbol Repetition Intervals (SRIs) using different (e.g., two or more) sets, and their repetitions.
  • SRIs Symbol Repetition Intervals
  • this extension enables realizing sub-slot-level SRI duration (e.g., half-slot), or SRIs of durations of non-integer multiple of slots (e.g., 1.5 slot, etc.), but instead, by using two or more UL-PRS resource sets.
  • the starting symbol offset within a slot, and (if needed) the numbers of symbols for an UL-PRS resource may be configured differently for the two/multiple resource sets that may share other parameters commonly.
  • Example 19 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for separate parameters and/or usage for configuring UL-PRS for the purpose of sensing.
  • Example 20 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for different sensing usages, corresponding to different categories of use-cases which require different measurements/processing. Accordingly, for each usage, different measurements may also be expected.
  • Example 21 may include the apparatus of example 20 or some other example herein, wherein for sensing use-cases which may need inferring channel variations or resolving channel multi-path (multi-path exploitation), e.g., weather monitoring, or (Al-based) gesture recognition, etc., channel measurements may be performed (and may be reported) by the sensing receiver.
  • multi-path multi-path exploitation
  • channel measurements may be performed (and may be reported) by the sensing receiver.
  • Example 22 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to also include the overall duration (e.g., in number of slots) over which, the set (at least for semi-periodic and period sets) occurs with a certain configured periodicity.
  • UL-PRS configuration is extended to also include the overall duration (e.g., in number of slots) over which, the set (at least for semi-periodic and period sets) occurs with a certain configured periodicity.
  • Example 24 may include the apparatus of example 23 or some other example herein, wherein the configuration can be indicated by RRC signaling, MAC CE, or DCI.
  • Example 25 may include the apparatus of example 1 or some other example herein, wherein the entire periodic occurrence of a set over a certain configured duration, may occur irregularly based on some indications/triggers (i.e., the intervals with the configured durations, can re-occur (start/stop) based on indications).
  • Example 26 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to also allow multiple periodicities for an UL-PRS (SRS) resource set configuration, potentially each with an overall effective duration over which the periodic pattern with the corresponding periodicity continues (e.g., in number of slots, etc.).
  • SRS UL-PRS
  • Example 27 may include an apparatus used in a positioning entity to localize User Equipment (UE), wherein the apparatus comprises processor circuitry configured to also generate UE’s Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26).
  • UE User Equipment
  • the apparatus comprises processor circuitry configured to also generate UE’s Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26).
  • Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26).
  • Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26).
  • Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26).
  • Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples
  • Example 28 includes a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include and/or implement a base station, wherein the method comprises: receiving, from a user equipment (UE), an uplink positioning reference signal (UL-PRS); and performing sensing based on the UL-PRS.
  • UE user equipment
  • U-PRS uplink positioning reference signal
  • Example 29 includes the method of example 28, and/or some other example herein, further comprising identifying, based on a UL-PRS resource of the UL-PRS, a sensing beam for sensing.
  • Example 30 includes the method of any of examples 28-29, and/or some other example herein, further comprising identifying, based on a number of PRS resources within a PRS resource set of the UL-PRS, a number of beam directions in a symbol repetition interval (SRI).
  • SRI symbol repetition interval
  • Example 31 includes the method of any of examples 28-30, and/or some other example herein, further comprising identifying, based on a resource set of the UL-PRS, the SRI.
  • Example 32 includes the method of any of examples 28-31, and/or some other example herein, further comprising identifying, based on a time interval which contains repetitions of a resource set with its periodicity related to the UL-PRS, a sensing block.
  • Example 33 includes the method of any of examples 28-32, and/or some other example herein, further comprising identifying, based on a periodic occurrence frequency of the UL-PRS, an update rate for sensing.
  • Example 34 includes a method to be performed by a user equipment (UE), one or more elements of a UE, and/or one or more electronic devices that include or implement a UE, wherein the method comprises: identifying one or more sensing-related parameters; generating, based on the one or more sensing-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, to a base station, the UL-PRS, wherein the base station is to use the UL-PRS for sensing.
  • UE user equipment
  • UL-PRS uplink positioning reference signal
  • Example 35 includes the method of example 34, and/or some other example herein, wherein the one or more sensing-related parameters include a sensing beam for sensing, and wherein the UL-PRS includes a UL-PRS resource based on the sensing beam.
  • Example 36 includes the method of any of examples 34-35, and/or some other example herein, wherein the one or more sensing-related parameters include a number of beam directions in a symbol repetition interval (SRI), and wherein the UL-PRS includes a number of PRS resources within a PRS resource set of the UL-PRS based on the number of beam directions.
  • SRI symbol repetition interval
  • Example 37 includes the method of any of examples 34-36, and/or some other example herein, wherein the one or more sensing-related parameters include the SRI, and wherein the UL-PRS includes a resource set of the UL-PRS based on the SRI.
  • Example 38 includes the method of any of examples 34-37, and/or some other example herein, wherein the one or more sensing-related parameters include a sensing block, and wherein the UL-PRS includes a time interval which contains repetitions of a resource set with its periodicity related to the UL-PRS based on the sensing block.
  • Example 39 includes the method of any of examples 34-38, and/or some other example herein, wherein the sensing-related parameter is an update rate for sensing, and wherein the UL- PRS includes a periodic occurrence frequency of the UL-PRS based on the update rate.
  • Example 40 includes a method to be performed by an electronic device in a cellular network, wherein the method comprises: identifying an uplink positioning reference signal (UL- PRS) resource related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; generating a cellular transmission that includes a symbol repetition interval (SRI) composed of the UL-PRS resource; and transmitting the cellular transmission during performance of the sensing operation.
  • UL- PRS uplink positioning reference signal
  • SRI symbol repetition interval
  • Example 41 includes the method of example 40, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
  • Example 42 includes the method of any of examples 40-41, and/or some other example herein, further comprising: identifying a frequency domain comb size from the set ⁇ 1, 2, 3, 4, 8 ⁇ ; mapping, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and mapping, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OLDM symbol.
  • identifying a frequency domain comb size from the set ⁇ 1, 2, 3, 4, 8 ⁇ ; mapping, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and mapping, based on the identified frequency domain
  • Example 43 includes the method of example 42, and/or some other example herein, wherein the plurality of UL-PRS symbols are mapped to a subset of the OLDM symbols of the slot.
  • Example 44 includes the method of example 43, and/or some other example herein, wherein OLDM symbols that are not in the subset of OLDM symbols are inconsecutive.
  • Example 45 includes the method of example 43, and/or some other example herein, further comprising mapping UL-PRS symbols of a second UL-PRS resource of a second UL- PRS resource set to a second subset of OLDM symbols of the slot.
  • Example 46 includes the method of any of examples 40-45, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a bilevel comb over N UL-PRS symbols, wherein M is greater than N.
  • Example 47 includes the method of example 46, and/or some other example herein, wherein resource elements (REs) of consecutive UL-PRS symbols of the plurality of UL-PRS symbols are the same as one another.
  • REs resource elements
  • Example 48 includes the method of any of examples 40-47, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
  • Example 49 includes the method of any of examples 40-48, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
  • Example 50 includes the method of example 49, and/or some other example herein, wherein the UL-PRS periodicity is based on half of a length of a slot, the length of one slot, or an integer multiplication of the length of one slot.
  • Example 51 includes the method of any of examples 40-50, and/or some other example herein, wherein the UL-PRS resource is based on an indication of a UL-PRS configuration received via radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), or downlink control information (DCI).
  • RRC radio resource control
  • MAC medium access control
  • DCI downlink control information
  • Example 52 includes the method of any of examples 40-51, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
  • PC power control
  • LExample 53 includes a ⁇ A- user equipment (UE) comprising: memory to store an uplink positioning reference signal (UL-PRS) resource based on a 5G NR Sounding Reference Signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; and one or more processors configured to: generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation.
  • SRS 5G NR Sounding Reference Signal
  • Example 54 includes the subject matter of example 53, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
  • Example 55 includes the subject matter of any of examples 53-54, and/or some other example herein, wherein the one or more processors are further configured to: identify a frequency domain comb size from the set ⁇ 1, 2, 3, 4, 8 ⁇ ; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OLDM symbol.
  • the one or more processors are further configured to: identify a frequency domain comb size from the set ⁇ 1, 2, 3, 4, 8 ⁇ ; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol
  • Example 56 includes the subject matter of example 55, and/or some other example herein, wherein the plurality of UL-PRS symbols are mapped to a subset of the OLDM symbols of the slot.
  • Example 57 includes the subject matter of example 56, and/or some other example herein, wherein OLDM symbols that are not in the subset of OLDM symbols are inconsecutive.
  • Example 58 includes the subject matter of example 56, wherein the one or more processors are further configured to map UL-PRS symbols of a second UL-PRS resource of a second UL-PRS resource set to a second subset of OFDM symbols of the slot.
  • Example 59 includes the subject matter of any of examples 53-58, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
  • Example 60 includes the subject matter of example 59, and/or some other example herein, wherein resource elements (REs) of consecutive UL-PRS symbols of the plurality of UL- PRS symbols are the same as one another.
  • REs resource elements
  • Example 61 includes the subject matter of any of examples 53-60, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
  • Example 62 includes the subject matter of any of examples 53-61, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
  • Example 63 includes the subject matter of example 62, and/or some other example herein, wherein the UL-PRS periodicity is based on half of a length of a slot, the length of one slot, or an integer multiplication of the length of one slot.
  • Example 64 includes the subject matter of any of examples 53-63, and/or some other example herein, wherein the UL-PRS resource is based on an indication of a UL-PRS configuration received via radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), or downlink control information (DCI).
  • RRC radio resource control
  • MAC medium access control
  • DCI downlink control information
  • Example 65 includes the subject matter of any of examples 53-64, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL- PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
  • PC power control
  • Example 66 includes one or more non-transitory computer-readable media (NTCRM) comprising instructions that, upon execution of the instructions by one or more processors of a user equipment (UE), are to cause the UE to: identify an uplink positioning reference signal (UL-PRS) resource based on a fifth generation (5G) new radio (NR) sounding reference signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation.
  • Example 67 includes the subject matter of example 66, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
  • Example 68 includes the subject matter of any of examples 66-67, and/or some other example herein, wherein the instructions are further to cause the UE to: identify a frequency domain comb size from the set ⁇ 1, 2, 3, 4, 8 ⁇ ; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OFDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OFDM symbol.
  • OFDM orthogonal frequency division multiplexed
  • Example 69 includes the subject matter of any of examples 66-68, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
  • Example 70 includes the subject matter of any of examples 66-69, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
  • Example 71 includes the subject matter of any of examples 66-70, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
  • Example 72 includes the subject matter of any of examples 66-71, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL- PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
  • PC power control
  • Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
  • Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
  • Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
  • Example Z04 may include a method, technique, or process as described in or related to any of examples 1-72, or portions or parts thereof.
  • Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
  • Example Z06 may include a signal as described in or related to any of examples 1-72, or portions or parts thereof.
  • Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z08 may include a signal encoded with data as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
  • Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
  • PDU protocol data unit
  • Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
  • Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
  • Example Z12 may include a signal in a wireless network as shown and described herein.
  • Example Z13 may include a method of communicating in a wireless network as shown and described herein.
  • Example Z14 may include a system for providing wireless communication as shown and described herein.
  • Example Z15 may include a device for providing wireless communication as shown and described herein.
  • 5GC 5G Core Protocol Antenna Server network 45 Port, Access Point 80 BSS Business
  • Mobility Adaptation Protocol CC Component
  • AN Access 70 BER Bit Error Ratio 105 Checksum CCA Clear Channel Mandatory Network, Cloud Assessment CMAS Commercial RAN CCE Control Mobile Alert Service CRB Common Channel Element CMD Command Resource Block CCCH Common 40 CMS Cloud 75 CRC Cyclic Control Channel Management System Redundancy Check CE Coverage CO Conditional CRI Channel-State Enhancement Optional Information CDM Content CoMP Coordinated Resource Delivery Network 45 Multi-Point 80 Indicator, CSI-RS CDMA Code- CORESET Control Resource Division Multiple Resource Set Indicator Access COTS Commercial C-RNTI Cell
  • Gateway Function Premise Information CHF Charging Equipment CSI-IM CSI
  • CID Cell-ID e.g., CQI Channel CSI-RS CSI positioning method
  • CIM Common CPU CSI processing CSI-RSRP CSI Information Model unit
  • Central reference signal CIR Carrier to 65 Processing Unit
  • received power Interference Ratio C/R CSI-RSRQ CSI CK
  • Cipher Key Command/Resp reference signal CM Connection onse field bit received quality Management
  • DM-RS DMRS Element
  • Function Demodulation 70 Enhanced CCE 105
  • E-UTRAN Evolved 85 Division Duplex eNB evolved NodeB, UTRAN FDM Frequency
  • E-UTRAN Node B EV2X Enhanced V2X Division EN-DC
  • E- F1AP Fl Application Multiplex UTRA-NR Dual Protocol FDMA Frequency
  • EPRE Energy per Channel/Full feLAA further resource element 65 rate 100 enhanced Licensed EPS Evolved Packet FACCH/H Fast Assisted System Associated Control Access, further
  • GSM EDGE for Mobile Packet Access
  • GGSN Gateway GPRS GTP GPRS Packet Access Support Node Tunneling Protocol HSS Home GLONASS GTP-UGPRS Subscriber Server
  • Intermodulation 70 IR Infrared 105 KQI Key Quality Indicator LMF Location (TSG T WG3 context)
  • KSI Key Set Management Function MAC-IMAC used for Identifier LOS Line of data integrity of ksps kilo-symbols Sight signalling messages per second 40 LPLMN Local 75 (TSG T WG3 context) KVM Kernel Virtual PLMN MANO Machine LPP LTE Management
  • L2 Layer 2 (data LWA LTE-WLAN Service link layer) aggregation MBSFN L3 Layer 3 50 LWIP LTE/WLAN 85 Multimedia
  • N-PoP Network Point NR New Radio, OFDM Orthogonal of Presence Neighbour Relation Frequency Division NMIB, N-MIB 65 NRF NF Repository 100 Multiplexing Narrowband MIB Function OFDMA NPBCH NRS Narrowband Orthogonal
  • PCRF Policy Control 70 PM Performance 105 Sidelink Broadcast Channel QFI QoS Flow ID, REG Resource
  • Uplink Control number (used for RLM-RS
  • Latency 40 Network Function 75 XRES EXpected user
  • AFML application may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • AFML application or the like may be an application that contains some AI/ML models and application-level descriptions.
  • circuitry refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality.
  • FPD field-programmable device
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • CPLD complex PLD
  • HPLD high-capacity PLD
  • DSPs digital signal processors
  • the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality.
  • the term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
  • processor circuitry refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data.
  • Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information.
  • processor circuitry may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes.
  • Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like.
  • the one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators.
  • CV computer vision
  • DL deep learning
  • application circuitry and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
  • interface circuitry refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices.
  • interface circuitry may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
  • user equipment refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network.
  • the term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc.
  • the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
  • network element refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services.
  • network element may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
  • computer system refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
  • appliance refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource.
  • program code e.g., software or firmware
  • a “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
  • resource refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like.
  • a “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s).
  • a “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc.
  • network resource or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network.
  • system resources may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
  • channel refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream.
  • channel may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated.
  • link refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
  • instantiate refers to the creation of an instance.
  • An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
  • Coupled may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other.
  • directly coupled may mean that two or more elements are in direct contact with one another.
  • communicatively coupled may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
  • information element refers to a structural element containing one or more fields.
  • field refers to individual contents of an information element, or a data element that contains content.
  • SMTC refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .
  • SSB refers to an SS/PBCH block.
  • Primary Cell refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
  • Primary SCG Cell refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
  • Secondary Cell refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
  • Secondary Cell Group refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
  • Server Cell refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
  • serving cell refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
  • Special Cell refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
  • machine learning refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences.
  • ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks.
  • training data referred to as “training data,” “model training information,” or the like
  • an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.
  • machine learning model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like.
  • supervised learning e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.
  • unsupervised learning e.g., K-means clustering, principle component analysis (PCA), etc.
  • reinforcement learning e.g., Q-learning, multi-armed bandit learning,
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor.
  • the “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • ML inference host refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Various embodiments herein relate to identifying, by a user equipment (UE), an uplink positioning reference signal (UL-PRS) resource based on a 5G NR Sounding Reference Signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols. The UE may further generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource. The UE may further transmit the cellular transmission during performance of the sensing operation. Other embodiments may be described and/or claimed.

Description

UPLINK POSITIONING REFERENCE SIGNAL (UL-PRS) ADAPTATIONS AND EXTENSIONS FOR SENSING IN JOINT COMMUNICATION AND SENSING SYSTEMS
CROSS REFERENCE TO RELATED APPLICATION
The present application claims priority to U.S. Provisional Patent Application No. 63/431,169, which was filed December 8, 2022.
BACKGROUND
Various embodiments generally may relate to the field of wireless communications.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.
Figure 1 illustrates an example sensing block structure, in accordance with various embodiments.
Figure 2 illustrates an example of frequency multiplexing of sounding reference signal(s) from multiple users using comb-2, in accordance with various embodiments.
Figure 3 illustrates examples of uplink positioning reference signal (UL-PRS) resource element (RE) patterns, in accordance with various embodiments.
Figure 4 illustrates examples of SRS configurations, in accordance with various embodiments.
Figure 5 illustrates example RE offsets for UL-PRS, in accordance with various embodiments.
Figure 6 illustrates an example setting of pathloss estimation for UL-PRS, in accordance with various embodiments.
Figure 7 illustrates an example of transmit/reception point (TRP) muting for comb-2, in accordance with various embodiments.
Figure 8 illustrates an example of spatial relation and pathloss reference for UL-PRS, in accordance with various embodiments.
Figure 9 schematically illustrates a wireless network in accordance with various embodiments.
Figure 10 schematically illustrates components of a wireless network in accordance with various embodiments.
Figure 11 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
Figure 12 illustrates a network in accordance with various embodiments.
Figure 13 depicts an example procedure for practicing the various embodiments discussed herein.
Figure 14 depicts an alternative example procedure for practicing the various embodiments discussed herein.
Figure 15 depicts an alternative example procedure for practicing the various embodiments discussed herein.
DETAILED DESCRIPTION
The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).
One design aspect of cellular-based joint communication and sensing (JCAS) is the enablement of sensing functionality within the orthogonal frequency division multiplexing (OFDM) framework. This functionality may include the proper definition and configuration of the numerology and sensing frame structure, and should be properly aligned within the boundaries of an existing communication frame. The functionality may also require efficient assignment of resources, which consider various design factors involving both communication and sensing performances. In the current disclosure, aspects with respect to extension and adaptation of new radio (NR) uplink (UL) Positioning Reference Signal (PRS) (which itself is based on Sounding Reference Signal - SRS) for the purpose of sensing are disclosed. Such extensions, target enablement of sensing based on User Equipment (UE)’s transmitted radio signal (which may correspond to different sensing architectures, mono/bi/multi- static).
Potential sensing frameworks/architectures in cellular systems gNodeB (gNB)-based and UE-based sensing scenarios can exist in a cellular framework, to enable different sensing application and use cases. For example, the following cases can exist:
• Case 1: gNB sends the sensing radio signal and receives/measures/processes its reflections from objects/environment, in time, frequency, and spatial/angular domains. If the same gNB also receives/measures/processes the reflected signal, the scenario may be called gNB-based monostatic sensing mode, and if other gNB(s) are involved in receiving, measurement/processing, it may be called gNB-based bi-static (multi-static) sensing mode by cooperative network nodes.
• Case 2: gNB sends the sensing radio signal and UE receives/measures/processes its reflections (bi-static sensing mode).
• Case 3: UE sends sensing radio signal and same or different UE(s), or gNB(s) receives/measures its reflections (corresponding to UE-based monostatic and UE-based bi/multi-static, or gNB-based bi/multi-static sensing modes, respectively).
Note: For cases 1 and 2, sensing signal can be based on the downlink (DL) positioning reference signal (PRS) (with some extensions and adaptations, as disclosed, for example, in IDF AE8858), or some newly designed sensing signal.
Note: There is also possibility of combining cases 1 and/or 2, also with the case where the UE receives/measures gNB’s radio signal for the positioning purposes, e.g., when gNB’s signal is based on DL PRS signal (which will be thoroughly investigated later).
Note: As can be seen from the above cases, sensing may require transmission/reception from multiple nodes to perform coordinated environment or neighborhood perception by multiple gNBs and/or UEs.
Note: Some solutions may focus on reusing/extending the uplink (UL)-PRS signal design in order to enable Case 3 above. It is noted, that in the third generation partnership project (3GPP) specifications or elsewhere, UL-PRS may be referred to as “sounding reference signal (SRS)for positioning” .
In order to enable sensing functionality addressing different use-cases (UCs) with corresponding sensing key performance indicator (KPI) requirements, the wireless signal used for the purpose of sensing, should meet certain requirements in terms of time domain and frequency domain attributes. Such attributes determine the underlying numerologies, frame structures, as well as the physical resource assignments and patterns. In IDF AE8858, these aspects are fully investigated, and the required attributes and properties of air-interface signal used for sensing to meet range, speed, and angular requirements are derived in detail. These characteristics may be applicable to the signal transmitted from gNB and/or UE. In IDF AE8858, the corresponding required adaptations on DL-PRS may also be disclosed in order to meet the desired attributes for sensing. Embodiments herein may relate to scenarios which rely on transmission of UE’s radio signal for the purpose of sensing. Based on the derived structure and signal pattem/attributes for sensing detection in IDF AE8858, in this disclosure, first, reusability of UL sounding reference signal structure for sensing may be established, followed by disclosed adaptations and extensions to UL-PRS (based on SRS).
Particularly, first, a closer look is taken into 3GPP release- 15 (Rel-15) SRS signal attributes, followed by release- 16 (Rel-16) UL-PRS design based on SRS. Then, feasibility analysis of UL-PRS-based sensing (similar to what was done for DL-PRS in IDF AE8858) is performed, followed by deriving the required extensions.
Embodiments herein may relate to air- interface signal design and attributes, and not on architectural, hardware and implementation aspects. For example, aspects such as enablement of full-duplex for monostatic UE sensing, or synchronization for bi/multi- static sensing (e.g., at gNB) based on UE’s signal, are not the focus of this disclosure.
1. Example statistical properties/structure of the sensing signal in time and frequency domains (e.g., as may be described in IDF AE8858)
The parametrization, numerology, frame structure, and time domain/frequency domain (TD/FD) resource mapping/dimensioning of the signal used for sensing (either a specific sensing signal or a DL communication signal), is driven by the requirements concerning range and velocity resolution, and their respective unambiguous max detectable values, as well as the requirements concerning multiplexing of communication and sensing. More accurately, dimensioning of numerology (selection of SCS and symbol/CP duration), and time-frequency attributes, resource allocation, and statistical properties (which is the most important aspect in enabling the desired detection processing) of sensing signal is primarily driven by such requirements. Further, all the OFDM system parameters (e.g., bandwidth (BW), SCS, number of subcarriers, CP duration, symbol duration, number of OFDM symbols) can be derived from these requirements. For example, while the sensing signal’s time domain repetition, as well as the SCS, define the max detectable speed, the total time span duration (i.e., the integration time - sensing block), defines the achievable speed resolution. On the other hand, the SCS and the CP duration (i.e., numerology), define the maximum detectable range, while the bandwidth (total frequency span), defines the range resolution.
A. Time domain sensing resources (attributes/pattems) and system parameters
To ensure certain sensing performance, certain time span and time spacing may be needed for the signal used for sensing. There are possible time domain resource assignment properties for sensing signal to enable Doppler processing:
1. Integration time span over which sensing signal shall extend when computing Doppler profile: Sensing block (or sensing frame) = °/ is inversely proportional to
Figure imgf000007_0001
velocity resolution and carrier frequency. In sensing frame design, the sensing block duration is an integer number (fc) multiple of SRI duration, i.e., k X TSRI. k is the size of
FFT operation performed in Doppler processing.
2. The maximum time spacing between sensing symbols within span of sensing block to enable Doppler estimation per beam direction defined by symbol repetition interval (SRI): TSRI < which is inversely proportional to the maximum detectable speed
Figure imgf000007_0002
and carrier frequency. As also mentioned earlier, this can be seen as a Nyquist sampling rate for max speed detection. Besides this factor, there are also other limits on max detectable speed. The maximum detectable speed needs to meet SRI Nyquist rate, ICI condition (Max Doppler frequency should be -10% of SCS), and range migration:
Figure imgf000007_0003
These two properties may be viewed as fundamental requirements for a sensing signal with respect to doppler processing, to perform a single task of sensing (without additional processing gains) (Figure 1). Any time repetition and/or block duration beyond the minimum required values, results in additional processing gain, and improving SNR. It is also noted that these attributes determine the basic allocation scheme in the context of sensing using a single beam. Further, these concepts can then be extended to the case of multi-beam operation.
There is also another time-related system parameter, which is related to the sensing range requirements. Ideal inter- symbol-interference (ISI) free sensing range detection requirement can be translated into the required CP duration (TCP). For ideal range detection performance, CP duration should be on the order of 2x(maximum range )/co. NR CP in frequency range 1 (FR1), is long enough to cover ranges beyond 180-350m. As such, FR1 supports longer range UCs, with same CP and OFDM symbol durations for communication and sensing symbols. Also, in FR1, useful symbol duration is very large compared to the orders of CPs desired for sensing ranging (low CP loss). It is noted that in general, between the sensing numerology and the communication numerology, only CP (hence, total symbol duration) may need to be different; other than that, SCS, etc. are all aligned between the communication and sensing systems. For frequency range 2 (FR2_, supporting a unified symbol/CP duration between communication and sensing may not be possible for higher SCSs, depending on UC’s max range requirement. Particularly, FR2 can support shorter range UCs, with same CP and OFDM symbol duration for sensing and communication, and longer-range UCs, with different CP and OFDM symbol duration for sensing and communication.
B. Frequency domain sensing resources (attributes/pattems) and system parameters In this subsection we take a look at translating the sensing requirements into signal properties in frequency domain. Particularly, frequency domain resource assignment for sensing signal to enable a single sensing task, needs to meet the following condition:
1. The minimum required signal bandwidth is inversely proportional to the supported range resolution: °/ sub-meter Ad is achievable with a bandwidth > 150MHz.
Figure imgf000008_0001
Accordingly, FR1 may impose potential compromise in range resolution, which may be addressed by enabling use of carrier aggregation to provide extended bandwidth for sensing.
In terms of the use of subcarriers within the assigned bandwidth (BW), it is noted that FD comb structure reduces the max unambiguous range (since it increases effective SCS). On the other hand, as discussed earlier, range detection performance is limited by CP limitation as well, and CP-based range is normally much smaller than max unambiguous range. For a practical system, the largest integer value mcomb for which, n X
Figure imgf000008_0002
/ 2 is less than l/nrcomi) x (the maximum unambiguous range, i.e., n
Figure imgf000008_0003
- X SCS can be derived, e.g., for some systems, even 5 times CP range is
Figure imgf000008_0004
about (1/3) x (maximum unambiguous range). Then, the comb size can be selected as a number less than or equal to mcomb.
There is also another frequency-related system parameter, which is related to the sensing speed requirements and is related to the SCS. Particularly, SCS have different implications and tradeoffs in terms of sensing. On the one hand, SCS is inversely proportional to the maximum unambiguous detectable range. Meaning that larger SCS may allow for detection of higher Doppler shifts and faster moving targets without inter carrier orthogonality (for ICI mitigation).
For acceptable ICI, the SCS should be larger than -lOxDoppler frequency
Figure imgf000008_0005
On the c0 other hand, as SCS is increased, to support certain range requirements, CP loss due to inefficiency (caused by the ratio of CP time to usable OFDM symbol time) increases. Usually, larger SCS are available for higher carrier frequencies, which support shorter OFDM symbol and CP durations, resulting in shortened sensing ranges.
As will be discussed later, for different SCS values, the choice of SRI and sensing frame duration will be determined separately, and achievability of certain ranges can also be assessed depending on CP, etc.
2. Examples of of Sensing frame structure design
In order to come up with the sensing frame structure design from the time and frequency domain attributes discussed in the previous section, the following high-level procedural steps has been followed:
• From the KPIs, a ballpark of different system parameters is derived.
• Then, the values for system parameters are fine-tuned based on the derived ballpark, considering practical cellular frame structure and numerology parameters.
• The resulting achievable KPIs, as well as achievable SNR (from link budget), can then be calculated.
The current section provides examples of how a sensing frame structure can fit in the cellular system frame and numerology. Accordingly, the following example SRI values and Doppler FFT sizes (and hence, sensing frame structure and durations) were also discussed in IDF AE8858 to support highest possible capabilities for velocity estimation under different limitations, and to meet reasonably fine velocity resolutions, while keeping the design as simple as possible (without compromising supported sensing performance).
For example, SRI is defined to occur either at half-slot-rate, full-slot-rate, or double-slot- rate, for different maximum desired speeds (depending on the use-case). The resulting exact supported max speed, and speed resolution can be determined then, also based on the carrier frequency.
• For all carrier frequencies in FR1, following SRI durations (in number of OFDM symbol (OS)) and Doppler FFT sizes (k) to be supported
• For SCS=15KHz, {TSRI, k} = {70S, 32}, {70S, 64}
• For SCS=30KHz, {TSRI, k} = { 14OS, 32}, { 14OS, 64}, {70S, 64}, {70S, 128}
• For SCS=60KHz, {TSRI, k} = {28OS, 32}, {28OS, 64}, { 14OS, 64}, { 14OS, 128}
These result in sensing block duration = k X TSR} = 16, 32msec
• For FR2, following SRI durations and Doppler FFT sizes (k) to be supported
• For SCS=60KHz, for all carrier frequencies in FR2, {TSRI, k} = {70S, 64}, {70S, 128}, which results in sensing block duration = k X TSR} = 8, 16msec
• For frequencies <30GHz in FR2, {TSRI, k} = { 14OS, 32}, { 14OS, 64}, { 1408, 128} are also supported, resulting in sensing block duration = 8,16,32msec.
• For frequencies > 50GHz in FR2, {TSR}, k} = {7, 256} is also supported, resulting in sensing block duration=32msec.
• For SCS=120KHz,
• For all carrier frequencies in FR2, {TSRI, k} = { 140S, 64}, { 140S, 128} are supported, resulting in sensing block duration=8, 16msec, and {TSR}, k} = {70S, 64}, {70S, 128} are supported, resulting in sensing block duration = 4, 8msec.
• For carrier frequencies > 50GHz in FR2, k=256 is also supported, resulting in sensing block duration=32, 16msec for TSRI=14, 70S, respectively.
It is noted that the number of OFDM symbols in the SRI, should provide a good balance between the maximum detectable speed, the sensing repetition gain (the total Doppler processing gain, for a certain sensing block is 101ogl0(Doppler FFT size) + 101ogl0(number of OFDM symbol within SRI)), the flexibility/capability to support multiplexing between sensing and communication, the field-of-view (FoV) coverage, depending on the required number of beams, and the beamwidth. Further, as can be seen from the discussed values above, the Doppler FFT sizes are generally smaller is FR1, which involves fewer number of radio frames for sensing and less limitation and unavailability for communication. It is also noted that while larger Doppler FFT sizes may also be supported (e.g., to provide finer Doppler resolution and/or higher processing gain), longer sensing frame durations resulting from large Doppler FFT sizes, may result in range migration issue in the range-Doppler image. This would require proper handling to avoid performance degradation.
Note: Sensing UCs and services in a JCAS system, may also support different values for SRI duration and/or Doppler FFT size than the above discussed values. The discussed values provide examples on how a sensing frame structure can fit in the cellular system frame and numerology.
In at least some of the above cases, the CP durations are the same as in NR, are also adopted for OFDM symbols used for sensing. In case of using different CP (and hence symbol duration) between communication and sensing (which may be mainly motivated if there is a need to support longer sensing ranges (>100m) with higher SCSs in FR2), proper alignment between sensing block durations and communication slot boundaries is required (the details are disclosed in IDF AE9196). Given that normal CP of NR supports up to ~90m IS I- free range detection, for 120kHz SCS, and considering the fact that for mmWave frequencies, the power range (link-budget) may not allow more than 100m (even 100m for some practical deployments may be too far, e.g., rooftop looking around the block), the support of longer-range UCs with FR2, may not be fully justified (especially, as the longer-range UCs can be supported with FR1 with less complications).
3. UL-PRS signal design and attributes
In the previous sections (and in more details, in IDF AE8858), the sensing requirements, sensing signal numerology, time and frequency attributes, and sensing frame structure aspects were discussed and formulated. Considering such characteristics, NR DL-PRS signal was anall led in IDF AE8858, and required extensions to enable sensing, were disclosed. In the next subsection, UL-PRS signal design, including the frequency and time resource allocation and pattems/regularities is reviewed, followed by identifying similarities and gaps with respect to what is desired for sensing, in the subsection after. NR UL-PRS was defined in NR Rel-16 based on Rel-15 SRS, for the purpose of UE localization/positioning. Accordingly, first, examples of Rel-15 SRS design is provided, followed by Rel-16 extensions for UL positioning.
A. Examples of Rel-15 Sounding Reference Signal (SRS) design
To enable UL channel sounding a device can be configured for transmission of SRS. As an UL-only signal, SRS is transmitted by UE, originally to help gNB obtain the channel state info (CSI) for each user. CSI describes how NR signal propagates from UE to gNB and represents the combined effect of scattering, fading, and power decay with distance. The system uses SRS for resource scheduling, link adaptation, Massive MIMO, and beam management. SRS is configured specific to UE.
Time/frequency characteristics of SRS
In time domain, Rel-15 SRS resource can span { 1, 2, 4} consecutive OFDM Symbols (OSs), mapped within the last six symbols of the slot only. Multiple SRS symbols allow coverage extension and increased sounding capacity. Ideally, the whole system bandwidth would be measured in a single OFDM symbol, for all SRS ports. However, this is only possible if the UE is close to the receiving base station, as the power spectral density is low when the UE power is used in a full bandwidth transmission. Rel-15 has a repetition factor R, of 1, 2, or 4 in the resource, in which case the same SRS subcarriers are used (sounded) in each repetition, i.e., same subcarriers for R symbols. With repetition enabled, Rel-15 SRS is transmitted in the same part of the band for 2 or 4 OFDM symbols in SRS resource. For example, a 2- or 4-OS SRS duration is 2- or 4-times repetition of the 1-OS SRS, respectively (depending on depends on configuration of groupHopping and sequenceHopping via the groupOrSequenceHopping parameter, same sequence may be repeated within the SRS resource, or the sequence group and/or sequence-in-a- group may hop across symbols). In addition to coverage extension, SRS repetition can also be used when the SRS is beamformed, as in FR2, to allow the gNB to perform receive beam tuning: since UE repeats SRS transmission using same transmit beam multiple times, the gNB can evaluate performance of several gNB receive beam candidates. The performance of these different gNB receive beams can be directly compared since it is known that UE keeps its transmit beam constant for each transmission.
As to the frequency domain aspects, an interleaved structure is used andthe design of the SRS and its frequency hopping mechanism is same as used in LTE.
SRS Sequences
Sequences applied to the set of SRS REs are partly based on Zadoff-Chu (ZC) sequences. Although ZC sequences of prime length are preferred in order to maximize the number of available sequences, SRS sequences are not of prime length. SRS sequences are extended ZC sequences based on the longest prime-length ZC sequence with a length M smaller or equal to the desired SRS sequence length. The sequence is then cyclically extended in the frequency domain(FD) up to the desired SRS-sequence length. As the extension is done in the FD, the extended sequence still has a constant spectrum, and thus a “perfect” cyclic autocorrelation, but the time domain amplitude will vary somewhat. Extended ZC sequences are used as SRS sequences for sequence lengths of 36 or larger, corresponding to an SRS extending over 6 and 12 resource blocks in case of comb-2 and comb-4, respectively.
Randomizing between users
To randomize SRS interference between users transmitting SRS within the same bandwidth, in the same cell and in different cells, a time-dependent sequence randomization (sequence hopping) can be configured for SRS sequence. The sequence used for SRS depends pseudo-randomly on both slot index and symbol index within a slot. In addition, the used SRS sequence initialization is configured UE-specific by the RRC.
UE multiplexing
The SRS is also designed with a comb-based pattern similar to the DL-PRS. SRS transmissions from different UEs can be Frequency Domain Multiplexed (FDMed), within the same frequency range by assigning different combs, corresponding to different frequency offsets (Figure 2). UEs can be multiplexed over the same transmitting symbol by assigning different comb patterns. For comb-2, for example, two SRS can be FDMed. In the case of comb- 12, up to 12 SRS can be FDMed. On the other hand, multiple SRS ports (i.e., 1001 - 1003) are interleaved in the frequency domain within the same OFDM symbol.
SRS ports multiplexing
An SRS resource can be configured to 1, 2, or 4 SRS ports. When an SRS resource is mapped to more than one OFDM symbol, each SRS port of the SRS resource is present in every symbol and across the whole configured SRS bandwidth of resource, i.e., all SRS ports are present in each OFDM symbol of the resource. An SRS antenna port can thus be repeatedly transmitted by a UE in 2 or 4 symbols in a slot, which can be used to extend the SRS coverage. Different configuration alternatives for the mapping of ports of an SRS resource to subcarriers in an OFDM symbol can use either a comb-4 or a comb-2 structure. An SRS port transmission is mapped to every 2nd to 4th subcarrier in an OFDM symbol (i.e., a comb structure is used). This means that comb structure can be used for FDM of multiple UEs as well as FDM of multiple ports of a PRS resource. For example, a gNB can configure a 2-port UE over one comb-2 set of REs, and FDM another 1-port or 2-port UE over the other comb-2 set of REs, over the same OFDM symbol, where each UE’s multi-port transmission is separated using cyclic shift (CS), over same resource elements (REs). For a 1-SRS-port resource, the port can be mapped to any of the combs and a CS can be applied (to separate SRS port from another UEs transmission by using different CS and/or different comb). For a 2-SRS-port resource, both ports are mapped to the same comb and separated by CS. Any of the combs can be configured for this SRS resource (the other comb can be used by another (e.g., 1-port or 2-port) UE. If this is configured to a single UE, then that is the expectation from that UE). When a UE is capable of transmitting, e.g., using 2 panels or 2 beams, the UE can be configured with a multiport SRS resource. But between different UEs, it is not necessary for the gNB to configure each UE with a multi-port resource. For a 4-SRS-port resource, either all four ports are mapped to the same comb and separated by CS, or groups of two ports are mapped to either of two configured combs, and separated by CS within the group. It is not possible to map a 4-port SRS resource to 4 different combs, a CS must be used to separate at least two ports. For a four-port and four-comb case when two combs are configured, the two combs cannot be adjacent since that prevents multiplexing another SRS resource in the same OFDM symbol (when using groups of 2 ports, this may limit the capacity to FDM with other UEs).
SRS resource set and SRS resource
A UE can be configured (by higher layer parameter SRS-ResourceSet, or SRS- PosResourceSet-rl 6) with more than one SRS Resource Set (that each contains one or more SRS resources), used for different purposes (“usages”). For example, these sets can be for DL and UL multi-antenna precoding, or DL and UL beam management. Particularly, each set is designated for a certain “usage”, such as “Antenna switching”, “Beam management”, etc., and an SRS resource transmitted in a given set cannot be used for another use than it has been configured for. For example, an SRS transmission for “antenna switching” cannot simultaneously be used for “codebook”-based usage and vice versa. Since each configured SRS resource set can only have one “usage” there may be a need for configuring several resource sets simultaneously to the UE. SRS resource set applicability is configured by the higher layer parameter usage in SRS- ResourceSet. Different usages may have certain limitations in terms of SRS resource or resource set configurations/numbers, port configurations, etc. For example, when higher layer parameter usage is set to 'beamManagement’, only one SRS resource in each of multiple SRS sets may be transmitted at a given time instant (which may imply TDM of beams i.e., beam sweeping), but SRS resources in different SRS resource sets with same time domain behavior in the same bandwidth part may be transmitted simultaneously. The specification does not limit the number of ports for the one SRS resource in each SRS set for beam management (unlike the case for CSI- RS which has some restriction for 1/2 ports for beam management).
On the other hand, generally, each SRS Resource Set can include one or more configured SRS resources. Particularly, for each SRS resource set configured by the higher layer parameter SRS-ResourceSet, a UE may be configured with K > 1 SRS resources (by higher layer parameter SRS-Resource). The maximum value of K is indicated by the UE capability (supported SRS- Resources in TS 38.306). SRS resources belonging to a set can be in the same slot (adjacent or nonadjacent) or can be distributed across different slots. There is no specified restriction in terms of how far the resources from the same set can be distanced (it will be up to configuration). A slot can be used for transmitting more than one SRS resource, for example, the multiple SRS resources of an SRS resource set. A slot can also contain resources from different sets.
The SRS resources of a set can be time domain multiplexed. For a 4-port SRS resource for Antenna Port 1001 and 1003, frequency domain multiplexing is also supported (a resource set may correspond to different comb offsets).
A UE can be configured with up to 16 SRS resource sets per bandwidth part (limited to 4 sets in FR1) and each set can contain maximum of 64 SRS resources. In FR1, the total number of SRS resources is limited to 10, as larger number of resources is needed only when SRS resources are transmitted in different UL beams. In summary, an SRS resource set:
• can have up to 64 SRS resources; Each resource set can contain K >=1 resource(s), with maximum value being UE capability;
• can have multiple SRS resources in the same slot where resources are adjacent or nonadjacent in time;
• can have SRS resources in different slots;
• is configured with a single “usage” (only one purpose at a time);
Since SRS is used for multiple functionalities, UE can be configured with multiple SRS resource sets simultaneously.
SRS types (TD structure of SRS)
An SRS can be configured for periodic, semi-persistent (SP), or aperiodic transmission. A periodic SRS is transmitted with a certain periodicity and slot offset within that periodicity and is only configured by RRC. An SP SRS has a periodicity and slot offset in the same way as a periodic SRS and is also configured by RRC. However, actual UL-PRS transmission according to the periodicity and slot offset is activated/deactivated by MAC CE signaling. SP SRS allows to start/stop periodic SRS transmission using MAC signaling from gNB to UE, which is faster than RRC control, and provides a means to trigger periodic SRS transmissions when needed only, to avoid interference & unnecessary transmissions from the UE. An aperiodic SRS is configured by RRC but only transmitted when explicitly triggered by DCI. Activation/deactivation, and triggering for SP and aperiodic SRS, respectively, not done for a specific SRS but for an SRS resource set. Rel-15 supports SRS periodicities of { 1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560} slots. Periodic, semi-persistent or aperiodic SRS transmission is a property of an SRS resource set. All SRS resources included within an SRS Resource Set are of the same type. Transmission of aperiodic SRS, or more accurately, transmission of the set of configured SRS included in an aperiodic SRS resource set, is triggered by DCI. All resources within the set also have the same periodicity.
B. Examples of Rel-16 UL Positioning Reference Signal (UL-PRS) design
UL-based positioning reference signal is based on Rel-15 SRS transmitted from the devices, with enhancements for positioning purposes. In the 3 GPP specification, UL-PRS may be referred to as “ SRS for positioning” .
UL-PRS (SRS) resource
In some respects, UL-PRS can be seen as UL equivalence to DL-PRS. SRS for positioning in Rel-16, resolves two aspects specific to positioning. Lirst, since positioning involves measurements from multiple receiving BSs, the signal must have enough range to reach not only the serving BS to which the UE is connected, but also the neighboring BSs involved in the positioning process. Second, the SRS is also designed to cover the full bandwidth, where REs are spread across the different symbols so as to cover all subcarriers. In other words, UL-PRS signal can support a large delay spread range, since it must be received at potentially distant neighboring BSs for position estimation. This is achieved by covering the whole configured bandwidth and transmitting PRS over multiple symbols that can be aggregated to accumulate power and increase the signal-to-noise ratio (SNR). Particularly, configurable patterns cover each subcarrier in the configured bandwidth over the pattern duration which gives the maximum measurement range for the Time of Arrival (ToA) measurement in scenarios with large delay spreads.
The UL-PRS sequence is similarly based on Zadoff-Chu sequences as a base signal, also used for Rel-15 SRS, to ensure low-PAPR transmission from the UE. The particular sequence used to generate an SRS symbol depends on configuration parameters. UL-PRS REs are arranged in a particular time/frequency pattern. To better support positioning, the SRS structure is extended in several ways: In time domain, the length of the sequence is extended to ensure a sufficiently good signal-to-noise ratio for accurate measurements in gNB. In contrast to Rel-15 SRS, an UL- PRS resource may span 1, 2, 4, 8 or 12 consecutive OLDM symbols (which provide enough coverage to reach all TRPs involved in the positioning procedures), located anywhere in a (UL) slot. The starting point is also more flexible to account for the increased duration. Like the DL PRS, the SRS resources for positioning are transmitted on a single antenna port (i.e., for UL positioning, each UL-PRS resource also is limited to have a single port). In frequency domain, the UL-PRS has also a comb-N pattern (N is comb size). Lor Rel-15 SRS, N can take values 2 or 4, but for UL-PRS N is extended to a set of {2, 4, 8} to allow multiplexing of a larger number of devices. Similar to DL-PRS, a “permuted” comb is used for positioning.
Lurther, frequency hopping for UL-PRS is not supported for SRS-based positioning (precluded for positioning by Rel-16), since a single transmission of UL-PRS typically covers the whole configured bandwidth. An “UL-PRS Resource” with 1, 2, 4, 8 or 12 consecutive OFDM symbols is transmitted in the UE’ s active UL bandwidth part. For UL-PRS, the number of symbols can be larger or smaller than the comb size. For example, a comb-2 UL-PRS with one symbol, or a comb-4 with eight symbols are also supported (if comb-size is smaller than the number of symbols, then repetition within the resource can take place). Similar to DL-PRS, RE mapping is not arranged in a staircase pattern (Eigure 3), with the advantage being that the first few symbols already have a better effective comb size. For example, if only the first few symbols are considered for TOA measurement, the effect of the alias correlation peaks are better suppressed. For example, the first two symbols of the comb-4 UL-PRS provide an effective comb-2 RE pattern (after destaggering). For each pair of comb size and the number of symbols, there is one RE pattern. The RE pattern of an UL-PRS resource is configured with a comb offset for the first symbol in UL- PRS. Relative RE offsets of subsequent symbols are defined relative to the comb offset of first symbol.
In summary, an UL-PRS resource can span 1, 2, 4, 8, or 12 adjacent OFDM symbols in one slot (i.e., number of consecutive OFDM symbols in an SRS resource is configurable with one of the values in the set { 1, 2, 4, 8, 12}), which can be transmitted anywhere in the slot (flexible starting point of UL SRS for positioning). The UL-PRS comb size set is extended from {2, 4} for Rel-15 SRS, to {2, 4, 8}. Rel-16 supports staggered comb patterns in a single SRS resource, which Rel-15 did not (Figure 4). Rel-16 repetitions are very specific to the patterns specified by RE offsets for pairs of UL-PRS comb size and number of symbols as shown in Table 1. Particularly, RE pattern of an UL-PRS, is configured with a comb offset for the 1st symbol in an SRS resource, and relative RE offsets (for other symbols) are defined relative to the comb offset of the 1st symbol in the SRS resource (Figure 5). Further, the number of repetitions is not separately configured for SRS for positioning; rather, it is realized by the configured number of SRS symbols and the comboffset sequence as shown in Table 1.
Table 1. RE offsets for pairs of UL-PRS comb size and number of symbols
Figure imgf000016_0001
Further, unlike the DL-PRS case where two levels of repetitions are supported (within and across PRS resources), for UL-PRS, only one level of repetition is supported (only inside the resource, i.e., no repetition of SRS resources is supported).
UL-PRS (SRS) resource set
Similar to Rel-15 SRS, a device can be configured with one or more UL-PRS Resource Sets (by higher layer parameter SRS-ResourceSet or SRS-PosResourceSet), that can be used for different purposes. Each UL-PRS Resource Set can include one or more UL-PRS Resources. When the SRS is configured with the higher layer parameter SRS-PosResourceSet-rl6, a UE may be configured with SRS resources (higher layer parameter SRSPosResource-rl6), where the maximum value of K is 16.
As the parameter above also shows, for the purpose of positioning, the SRS is identified, separately, i.e., it is a different configuration. This means that although positioning uses SRS, in the configuration itself, the purpose is distinguished by the signaling.
Lastly, for UL positioning purpose, up to 16 SRS resource sets can be configured to a UE [TS 38.331],
UL-PRS types
Similar to Rel-15 SRS, an UL-PRS can be configured for periodic, semi-periodic, and aperiodic transmission. In addition to Rel-15 SRS periodicities of { 1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560} slots, periodicities of {5120, 10240, 20480, 40960, 81920} slots are supported for UL-PRS:
• Periodicity of 20480 slots is applicable for 30, 60 and 120 kHz SCS only;
• Periodicity of 40960 slots is applicable for 60 and 120 kHz SCS only;
• Periodicity of 81920 slots is applicable for 120 kHz SCS only.
This means that UL-PRS resource set (and hence, all its UL-PRS resources) can have a periodic pattern, with periodicity depending on the SCS. Lor SP SRS for positioning, configuration with MAC CE activation/deactivation is supported, with SRS to be received at the serving cell and neighbor cell. Aperiodic SRS for positioning, is triggered by a DCI, with no impact to Rel-15 DCI (the triggers in place in Rel-15 are reused).
UL-PRS (SRS) resource set properties
Periodic, semi-persistent or aperiodic UL-PRS transmission is a property of an UL-PRS Resource Set, i.e., all UL-PRS Resources included within an ULPRS Resource Set are of the same type.
Another property of UL-PRS Resource Set is the Tx power control (PC). Lor UL-PRS, only open-loop (OL) PC is supported, including support for (fractional) pathloss compensation to serving and neighboring TRPs. The UE estimates UL pathloss for serving and neighboring TRPs based on DL measurements and sets UL-PRS Tx power accordingly. The UE may estimate the pathloss from a DL RS, which may be an SSB or DL-PRS not only from the serving TRP but also from neighbor TRPs (Figure 6). As the serving TRP is likely to be closer to UE than a neighboring TRP, DL pathloss estimate based on serving TRP may result in too small of Tx power for UL- PRS to be detectable at the neighbor TRPs (UL hearability). The pathloss estimate based on an RS from neighbor TRPs can be used to transmit UL-PRS with an appropriate power towards the intended TRPs. That is, a smaller pathloss estimate results in higher UL-PRS transmit power towards the intended TRP. To minimize interference, the UE can be configured with different SRS instances, each with independent power control loops. This allows an SRS pointed at neighbor cells to have better hearability and keeps the interference low in the serving cell. Assistance information is provided if SSB/DL PRS is used for pathloss estimation. As PC parameters are part of the SRS resource set configuration, all resources in a set, should have same PC parameters.
Parameters describing an UL-PRS resource (Similar or extensions of Rel-15 SRS parameters)
• UL-PRS Resource Identity (SRS-PosResourceld in spec): defining the particular UL-PRS Resource
• Transmission Comb', defining
• comb size N of UL-PRS (N = 2, 4 or 8),
• comb offset of the first symbol of UL-PRS Resource (0 . . . N- 1)
• cyclic shift for generating the reference sequence, e.g., Comb 2 supports 8 cyclic shifts and Comb 4 supports 12 cyclic shifts
• Resource Mapping', defining 1st OFDM symbol location of UL-PRS Resource in a slot (0,1,2, . . . ,13) and the number of symbols of UL-PRS Resource (1, 2, 4, 8 or 12)
• Frequency Domain Shift: defining frequency domain position of UL-PRS Resource (same as for Rel-15 SRS)
• Frequency Hopping: defining bandwidth of UL-PRS Resource. The name is reused from Rel-15 SRS, although frequency hopping for UL-PRS is not supported. However, part of the frequency hopping parameter is BW indication, which is the only parameter applicable for UL-PRS
• Group or Sequence Hopping: defining whether group or sequence of hopping is used (same as for Rel-15 SRS). The hopping modes are used to randomize the reuse of a sequence in the system • Resource Type', defining UL-PRS Resource type (periodic, semi-pers, aperiodic) & periodicity for semi-persistent & periodic UL-PRS
• Sequence ID, defining a UE specific sequence ID used to initialize PN group and sequence hopping. For UL-PRS, #diff erent sequence group hopping pattern is increased from 1024 (Rel-15 SRS) to 65536, and number of bits for sequence ID is increased to 16. For UL- PRS to be received by neighboring TRPs, increasing available #UL-PRS sequences can be beneficial for reducing UL-PRS collision & further mitigating UL interference
• Spatial Relation Info: defining the spatial relation between a reference RS and the target UL-PRS. The reference RS can be an SSB, CSLRS (for serving cell only), DL-PRS, SRS or UL-PRS.
Parameters describing an UL-PRS resource set (Similar or extensions of the Rel-15 SRS parameters)
• UL-PRS Resource Set Identity (SRS-PosResourceSetld in the specification): defining particular UL-PRS Resource Set. It is unique in the context of the BWP in which the UL- PRS is defined.
• Resource Type: defining time domain behavior of UL-PRS resource configuration. The network configures UL-PRS Resources in the same Resource Set with the same time domain behavior on periodic, aperiodic & semi-persistent. This means that the periodicity values are configured for the set, and different resources within the set cannot have different periodicities. A UE is not expected to be configured with SRS resources in the same SRS resource set SRS-ResourceSet or SRS-PosResourceSet-rl6 with different slot level periodicities. For periodic SRS, for how long the SRS is transmitted with those periodicities, is up to the network configuration, and the periodic transmission continues unless reconfigured (as long as UE is in that particular state unless reconfigured by RRC, being it inactive or connected, the UE will be able to transmit).
• Alpha a value for the UL-PRS power control: defining the fractional pathloss compensation. The alpha value is multiplied by the UE with the pathloss estimate. For full pathloss compensation, alpha is equal to 1.
• pO a value for the UL-PRS power control which can be described as the “desired receive power” at the TRP. That is, the UL-PRS Tx power determination is based on pO + alpha ■ PL, where PL is the pathloss estimate
• Pathloss Reference RS: defining the reference DL signal to be used for pathloss estimation. The DL reference signal can be an SSB or DL-PRS from the serving or neighboring TRP
• UL-PRS Resource list: defining the configuration for each resource in the set.
UL-based positioning - measurements For the same reasons as in DL, additional measurements are specified to support UL-based positioning. Particularly, four new gNB measurements are defined:
• Relative ToA, which measures the arrival time of SRS relative to a configurable time reference,
• Rx-Tx time difference, similar but with the subframe boundary as the reference. Hence, it reports the arrival time of an SRS relative to the nearest DL subframe boundary.
• AoA, is angle of arrival for signal transmitted by UE relative to either a global reference or geographical North pole and the zenith, or relative to a local coordinate system. In a fixed- beam system this in practice corresponds to the direction of the beam receiving the signal
• SRS RS Rx power, the SRS received power (SRS-RSRP) is similar to its DL counterpart, namely, received power of SRS. It can for example be used for fingerprinting schemes.
It is noted that in Rel-15, no SRS-based measurements were defined/specified (left up to the gNB). However, for positioning, the measurements are defined for the gNB be to provide to the LMF.
Table 2 provides information in terms of mapping between UL PRS and gNB measurements. Positioning techniques are also indicated for information purpose only.
Table 2. Mapping between UL PRS and gNB measurements
Figure imgf000020_0001
NR RAT-dependent UE positioning methods
The following RAT-dependent UE positioning methods are supported in Rel-16:
• DL time difference of arrival (DL TDOA): This method makes use of the DL RSTD, and optionally the DL-PRS-RSRP measurements, received from multiple gNBs at the UE, along with knowledge of the geographical coordinates of the gNBs and their relative DL timing, to determine the position of the UE. • UL time difference of arrival (UL TDOA): With this method, the UE’s position is estimated based on the UL TDOA and optionally on the UL SRS-RSRP measurements taken at different gNBs of UL signals from the UE along with other configuration information.
• DL angle of departure (DL AoD): This method makes use of the DL PRS-RSRP measurements made on signals received from multiple gNBs along with knowledge of the spatial information of the DL radio signals and geographical coordinates of the gNBs to determine the position of the UE.
• UL angle of arrival (UL AoA): With this method, the UE position is estimated based on the UL AoA and optionally the UL SRS-RSRP measurements taken on UL radio signals at different gNBs, along with other configuration information.
• Multi-round trip time (Multi-RTT): With this method the UE position is estimated based on measurements made at both the UE and the gNB. These measurements are (a) UE Rx- Tx and DL PRS-RSRP of signals received at the UE from multiple gNBs and (b) gNB Rx- Tx and UL SRS-RSRP of signals received at the multiple gNBs from the UE.
Interference handling for UL-PRS
To minimize interference among TRPs transmitting DL-PRS and UEs transmitting UL- PRS, NR Rel-16 positioning specification supports multiple interference management techniques:
• PRSs, on both UL and DL directions, are orthogonalized in code, frequency, and time domains
• Lor the code domain orthogonality, QPSK modulated PRS is initialized by
• standard 31 -bit Gold code sequence in DL and
• standard Zadoff-Chu sequence in UL
• To maintain frequency domain orthogonality, both UL and DL PRSs can be configured (among interfering nodes) using different frequency-domain comb-factors
• To orthogonalize PRS in time domain (Ligure 7),
• cyclic shift configurations are used for UL-PRS
• muting configurations are used for DL-PRS.
UL-PRS spatial relation (Supported spatial relations to the UL-PRS resource)
Both DL-PRS and UL-PRS can also serve as spatial quasi co-location (QCL) references to establish positioning beam pairs. That is, given the knowledge of a suitable RX beam for DL- PRS, the RX knows that the same RX beam should be suitable for UL-PRS. Spatial relation indication for UL-PRS Resources is supported, either to a DL RS (SSB, CSLRS (for serving cell only) or DL-PRS) or UE’s previously transmitted SRS or UL-PRS. The UL-PRS beam may be derived from the spatial relation to an indicated DL RS, whereupon UE may transmit UL-PRS in the reciprocal direction to how it set its RX beam when receiving the DL RS, as illustrated. An additional procedure may be used by the network, where UE transmits an UL-PRS or SRS beam sweep & gNB refers back to one of the swept beams in a previously transmitted UL-PRS or SRS resource to indicate spatial relation to UL-PRS resource.
Compared to the Rel-15 SRS, UL-PRS can have a spatial relation to a neighbor TRP (Ligure 8). Lor positioning, UL-PRS generally needs to be received also by neighboring TRPs. To provide connectivity, NR UEs supporting mmWave, typically include multiple antenna panels pointing in different directions. The spatial relation for both serving and neighboring TRPs is primarily used to indicate which UL TX beam UE may use for UL-PRS. To determine an appropriate UL-PRS spatial domain transmission filter in LR2 (i.e., beam) that points towards neighboring TRPs, the UE may receive a RS for the UL-PRS beam from the same direction as that of UL-PRS desired direction. The RS from a neighbor TRP may be an SSB or DL-PRS.
UL-PRS flexibility for beamforming and spatial allocation
Within an SRS resource set, there is flexibility for spatial allocations. Particularly, there can be different resources (beams) within a set. The current SRS design enables the possibility to repeat some directions more often than others. Even though all resources of a set repeat by the same periodicity, but within a resource, (e.g., for comb-2/2-OS), 1 or 2 or 4 or 6 repetitions can take place, which provides additional flexibility.
Further, multiple SRS resource sets may be configured to a UE, which may allow different beamforming across the different sets. For instance, a set of narrow beams to cover a region that is mapped to one set, and another set of wider beams to target a slightly different coverage that can be mapped to the second resource set. In the context of sensing, this design aspect may also have application in realizing sub- slot- level SRI durations, as will be disclosed later. Further, this concept may be reused to define multiple sensing frames (together with their corresponding SRI settings) (e.g., to benefit from different measurements and/or different levels of dynamicity in different parts of the environment/FoV). Multiple sensing frames could be defined using SP SRS setting and the appropriate frame can be activated by MAC CE in dynamic fashion. This would be useful because the UE could dynamically be assigned different SRS settings, e.g. for different SRIs, etc.
4. Embodiment: Reuse of UL-PRS signal for sensing (UL-PRS signal resource structure from the sensing point of view)
In this section, the focus is on assessing feasibility of reusing of UL-PRS signal for the sensing (even though the possibility may be limited to certain UCs/KPIs). As mentioned earlier, in terms of the frequency and time resource allocation, patterns, and regularities, similar to DL- PRS, UL-PRS has features that are desired for sensing. Particularly, UL-PRS have certain regularities and attributes, and the supported patterns are in synergy with sensing signal attributes.
In order to understand feasibility of reusing UL-PRS signal for sensing, it is important to identify the analogies and differences between the specified PRS signal and the desired resource structure for the sensing signal.
Example 1: Mapping UL-PRS attributes to sensing signal desired attributes - Analogies between UL-PRS and sensing signal attributes
1. UL-PRS resource sensing beam (for UL-based positioning, single port UL-PRS resource is supported, i.e., each UL-PRS resource is dedicated for transmission in a single direction). A resource corresponds to an SRS beam, and resource sets correspond to a collection of SRS resource (i.e., beams) aimed at a given TRP.
2. The number of PRS resources within a PRS resource set the number of beam directions in SRI. This is also related to the number of OLDM symbols in each SRS resource of the set and how they are located. Lor sensing, smaller comb- sizes are preferred, because compared to the larger size combs, they utilize more SC and provide more intra-SRI flexibility of assigning OLDM symbols to different directions and/or for different purposes (UL-PRS vs non-PRS), while also imposes less limitation on the maximum unambiguously detectable range.
3. Resource set together with periodicity/repetition parameters and the number and distancing of resources within the set, define SRI SRI (collection of one occurrence of all PRS resources within the set)
• As mentioned above, for sensing, each symbol within SRI can be allocated to a different beam/direction and in an SRS resource set, multiple SRS resources, each for one direction is transmitted.
• Lor comb-2/2-OS, there can be 1, 2, 4, or 6 repetitions within one SRS resource. This is equivalent to using multiple SRI symbols for repetition of a same direction and processing gain.
• Currently, there may be no restriction on the min/max duration of a set (one instance of the set) in time domain, and the duration and placement of the resources within a set are a matter of configuration.
4. The entire time interval which contains repetitions of resource set with its periodicity (i.e., repetitions of SRI - k*SRI) sensing block - possible durations is based on network configuration.
• Across SRIs within a sensing block, the number and pattern of sensing resources and directions should be the same (additional processing would be required for irregular resources, which may not be always justified). As such, consistent configuration of SRS resources in periodic occurrences of SRS resource sets is required, which is realized by definition of periodically occurring occasions.
• The same number and placement of OFDM symbols across all SRIs should be considered for non-PRS transmissions.
• Number of repetitions of SRS resource set Doppler FFT size, k
5. How frequent periodic occurrence (i.e., the whole sensing block consisting of k*SRI) can be (re-)configured and repeated update rate for sensing (the minimum achievable update rate may be related to the signaling limitations).
Example 2: One-direction sensing via UL-PRS
For one-direction sensing, one UL-PRS resource, i.e., one beam direction, and repetitions of that resource for Doppler estimation is required. For UL-PRS-based sensing, it is important to understand that with proper UL-PRS configurations, how frequent the occurrence of one direction can be for Doppler processing, and with what granularity time/frequency resources for that direction can be configured.
A look into slot-level supported patterns of UL-PRS resources, shows that within a slot, there can exist one or multiple UL-PRS resources (of one or multiple resource sets), each with or without intra-resource-level repetition. Lor example, it is possible that multiple UL-PRS resources, e.g., each of length 2 OS, are Time-Domain-Multiplexed (TDMed) within one resource set of length one slot.
While repetition of the UL-PRS resource sets occurs across slots, within the resource, also repetition of a beam is allowed, this may be mainly used for processing gain (not Doppler estimation). Particularly, based on the analogies built in the previous section, intra-resource repetition, can allow for repetition of a certain beam, within the SRI, for power gain, and may not help with speed detection. Lor example, at most, 6 repetition of a 2-OS/comb-2 within one slot is supported.
As discussed in prior sections, SRIs of length 70S or 14OS or 28OS would be needed (at least for certain UCs which does not require extremely high speeds). With UL-PRS-based sensing, SRIs durations of integer number of slots can be achieved straightforwardly, since the minimum periodicity of one slot is supported. However, for SRI duration of half- slot, the current UL-PRS resource settings may have some limitations, as will be discussed and addressed.
Regarding SRI duration of integer multiples of slot (minimum of one-slot SRI duration), depending on the periodicity, and the number of resources within the set, different SRI durations can be defined. Lor example, with a periodicity of 1 slot, and all SRS resources of the set also packed next to each other within a slot, e.g., each UL-PRS resource is 1-12 OLDM symbols, an SRI duration of one slot can be achieved. With a periodicity of 2 slots, and all SRS resources of the set are also packed next to each other within a slot, an SRI of 2 slots can be achieved wherein only within the first slot of the SRI, the sensing transmission takes places. The same logic applies for larger periodicities, leading to lower Doppler/speed detection. In NR UL-PRS design, in each slot, (at least) two symbols are not used for PRS transmission and are reserved for other communication channels.
For sub- slot level SRI duration, one needs to properly handle the non-UL-PRS symbols and deal with such minimum gap within the UL-PRS slot. Otherwise, for sensing, in case of subslot level SRI, this can cause irregularities across SRIs, which is not desired (since inconsistencies across SRIs troubles the repetition and Doppler FFT processing). For example, the same number and allocation of OFDM symbols across all SRIs should be considered for non-UL-PRS transmissions, to realize sub- slot- level (e.g., half-slot) SRI. For example, each half slot can form an SRI over different UL-PRS resource sets. The two PRS resources sets each in a half- slot should be configured with similar pattern and number of PRS resources, covering same spatial domains, to maintain the consistency across SRIs.
For UL-PRS resource of comb-2, the durations are either 2, 4, 6, or 12 ‘consecutive’ symbols. It is not possible to have two symbols of a 4-OS comb-2 UL-PRS resource in the first half of the slot, and the other two symbols in the second half. These limitations need to be to take into consideration and be dealt with, properly.
For more flexibility in terms of reusing UL-PRS design for sensing, some expansion and enhancements are discussed later.
Example 3: Multi-direction sensing via UL-PRS
For multi-directional sensing, multiple UL-PRS resources, i.e., multiple beam directions, and repetitions of those resource for Doppler estimation is required. Within the resource, repetition of each beam is mainly for processing gain within the SRI, not for Doppler estimation. Depending on how different resources of a single or multiple resource sets are located, SRI can be defined differently.
For SRI durations of integer multiples of slots, similar to the one-directional sensing case, if multiple PRS resources of the same resource set are TDMed within one slot, and if all resources of a set fit in a slot, the minimum SRI duration of one slot would be achieved. Depending also on the periodicity set for the set, different SRI durations can be defined.
Further, if an SRS resource set contains resources over multiple slots, either one slot per resource, or mix of slots with single and multiple resources, SRIs over multiple slots can be also defined, effectively for lower Doppler estimations.
5. Embodiment: Expansions, and adaptations to UL-PRS for reuse in sensing
Based on the above examples, SRS (UL-PRS) signal supported patterns, attributes, regularities, and characteristics, are in line with general desired attributes of sensing signal. As such, for any sensing scenario/architecture capable of leveraging an UL radio signal for sensing, UL-PRS (SRS) seems to be the best fit. Further, if a new sensing signal is defined in the next generation of cellular systems, likely it can be also used for positioning, especially, if the design accommodates backward compatibility. From the resource efficiency and overhead perspective, it may not be desired to have separate positioning signal and sensing signal being transmitted in the system (at least at the same time), as much as possible. Motivated by the same reason, it is also logical to adapt the positioning reference signal to accommodate the sensing needs as much as possible.
In summary, in the same spirit as SRS originally being defined for sounding, being re-used for UL positioning with extensions, while DL-PRS and UL-PRS are originally introduced for positioning, with certain extensions, these signals can be also used for sensing.
It is also noted that by enabling UL-PRS-based sensing, the JCAS system can support both UE-based monostatic sensing and gNB-based bi-static sensing (UE being the UL-PRS signal transmitter, and gNB being UL-PRS signal sensing receiver), as well as gNB-based positioning (refer to Section 2, for more background).
In order to enable or enhance the reuse of UL-PRS signal for the purpose of sensing, some accommodations and adaptations are disclosed in the following. It is noted that some of the extensions are in the same spirit as DL-PRS extensions disclosed in IDF AE8858.
Example 1
Extending configuration of UL-PRS comb size from {2, 4, 8}, to { 1, 2, 4, 8}, or to { 1, 2, 3, 4, 8}, where comb-3 may be applicable to UL-PRS resource duration of 1 or 3 (which can also be part of the extended configuration for UL-PRS) or 12 OS. Comb-1 means use of consecutive subcarriers over the OFDM symbol (extension to allow use of consecutive subcarriers over one symbol; examples may include single symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS (SRS) resource).
As discussed in Section 2, from the sensing point of view, for example, FD comb of size mcomb = 2 or 3 can be supported, where different sets of subcarriers (e.g., realized with different frequency domain RE offsets), can be used to handle [at least, to some extent], the interference from the signals used for sensing, from the close-by UEs. It is noted that in general, there are different approaches to mitigate interference, e.g., by leveraging multiplexing in time, frequency, code, and/or sequence domain. For effective handling of interference, a combination of different approaches may be accommodated and supported by the design, yet this is out of the scope of the current disclosure.
Example 2 Extending UL-PRS configurations to allow use of
Partially staggered patterns for UL-PRS signals that may be defined by M-level comb and N symbols for a UL-PRS resource with M > N.
• Unstaggered patterns for UL-PRS signals such that the same REs are used in consecutive symbols within an UL-PRS resource; examples may include:
• Every other subcarrier over one symbol, without staggering over multiple symbols.
• Every 3rd subcarrier within one symbol, without staggering over multiple symbols.
• Combinations of fully or partially staggered and unstaggered patterns for UL-PRS signals.
As discussed earlier, the current structure in terms of time and frequency domain resources, can impose limitations in terms of flexibility of assigning symbols within SRI duration to different beam directions, or for different purposes (communication and sensing). The above additions to the allowable PRS resource configurations, improve such flexibilities.
Example 3
Extending configuration to allow for a slot being fully occupied by UL-PRS resources from one or multiple sets (i.e., possible to have zero resources for non-UL-PRS purposes in a slot). The minimum of 2 non-PRS OFDM symbols in UL-PRS slots (e.g., the maximum duration of SRS resource is 12OS), can impose limitations in designing the SRI. It is beneficial if UL-PRS configuration allows for allocating all the symbols within a slot for UL-PRS transmission.
Example 4
Extending configuration to allow accommodation of inconsecutive symbols (minimum of two inconsecutive) for non-UL-PRS transmission (motivated by the same reasons for above examples).
Example 5
Extending configuration to allow multi-port UL-PRS resource transmission. Multi-port transmission may allow for sending multiple beams at different directions at the same time. For example, even currently, for channel reciprocity-based use cases with 2-port 4-port SRS resource configuration, the UE can sound simultaneously on 2 or 4 ports (i.e., in multiple directions), respectively.
Example 6
Extending configuration to allow inconsecutive (and preferably, symmetric over the two half-slots) allocation of OFDM symbols per PRS resource within a slot. For example, a comb-2 UL-PRS resource of length 4, may be realized with an equal split of the 4 symbols over two 2- symbol occurrences each in one half-slot. Especially, this enables realizing sub-slot-level SRI duration (e.g., half-slot), using one UL-PRS resource set. Inconsecutive allocation of OFDM symbols for one UL-PRS resource, may be achieved by different means, e.g., through enabling configuration of the PRS resource symbol offset by a vector, etc.
Example 7
Extending configuration to allow configurations of periodicity at the granularity of UL- PRS resource (e.g., per UL-PRS resource) as against defining them at the set level. As such, different resources within the set are able to have different periodicities, to help better spatial adjustments to cover the field of view. This helps with realizing different SRI durations for different beam directions in the FoV. Otherwise, different sets are needed to cover the FoV, e.g., each set covering the directions (SRS resources) with the same required SRI, which may lead to excessive configuration signaling.
(It is noted that currently, a UE is not expected to be configured with SRS resources in the same SRS resource set SRS-ResourceSet or SRS-PosResourceSet-rl6 with different slot level periodicities.)
Example 8
Extending configuration to allow the periodicity of half-slot, as well (e.g., for higher speed UCs, etc.).
Example 9
For sensing it may be desired (e.g., depending on the use-case and its requirements) to gather a full scan of FoV within a short time and then wait for a longer period of time before starting another scan. This may allow for the highest possible velocity detection without blurring. In some use-case scenarios, it is desired that once per slow [update-]rate, a full snapshot of FoV is taken at the fastest rate (e.g., with shorter SRIs to detect high speeds and potentially shorter sensing block duration), to provide optimal coverage of any fast-moving objects. At other times, the scanning can be performed at a slower rate (e.g., with larger SRIs) when no fast-moving objects are expected.
Extending configuration to allow for multiple levels of scan rate configurations (to allow multiple/diff erent repetition patterns and update rates), to enable a fast scan rate for rapidly gathering a number of UL-PRS resources, followed by a slower scan rate to enable a waiting period for dedicated communications before the next rapid period.
Also, extending configuration to allow multiple periodicities for an UL-PRS (SRS) resource set configuration, potentially each with an overall effective duration (for example, as disclosed in Example 13, e.g., in number of slots, etc.).
Together with the disclosed idea in Example 14, these provide the required flexibility to adjust the scans based on FoV characteristics.
As also mentioned in Example 3, the current SRS resource set configurations may be limited to combs applied mainly to the small portion of the OFDM symbols within the slot (typically the latter symbols). It would be ideal for sensing to attain a burst with each slot nearly full of sensing combs, to get all of the needed sensing performed quickly. The purpose of this extension is to ensure that any new UL-PRS can accommodate the need for sensing to gather the full FoV scan rapidly, allowing optimal Doppler detection, rather than slowly attaining the FoV scan as may occur in a background process.
Example 10
For UL-PRS, the flexibility of both periodic and semi-persistent occurrences are potentially useful. Yet, much of the flexibility options in UL-PRS rely on signaling form DCI or RRC updates that are slower than the time needed for a single full scan. Lor sensing, there may need to allow a quick burst of repetitions to gather a full scan, and then a slower periodic control for spacing time between scans.
Extending configuration to allow for a fully programmable rapid burst of UL-PRS transmissions/acquisitions. The burst of transmissions/acquisitions may need to occur at a faster rate than DCI updates, so it may require to contain all of the necessary parameters without a need for interruption by DCI or RRC re-configuration. Rate of transmission/acquisition, number of transmissions/acquisitions, as well as the normal UL-PRS parameters such as OLDM symbol position within RB, comb size, and cyclic offset need to be set independently for the burst of transmissions/acquisitions.
Example 11
Extending configuration to allow different power control parameters for resources within a set, i.e., to allow PC configuration per UL-PRS resource (beam).
Example 12
Extending configuration to allow multiple (two or more) UL-PRS resource sets with potentially same resource settings within the sets at least for certain parameters (e.g., same time/frequency domain placement, same spatial configuration of resources, same resource pattern, etc., except for the configuration defining the starting time location of the resources), which can be TDMed even within one slot, to enable realizing different (e.g., two or more) SRIs using different (e.g., two or more) sets, and their repetitions.
Especially, this extension enables realizing sub-slot-level SRI duration (e.g., half-slot), or SRIs of durations of non-integer multiple of slots (e.g., 1.5 slot, etc.), using two or more UL-PRS resource sets. For example, the starting symbol offset within a slot, and (if needed) the numbers of symbols for an UL-PRS resource, may be configured differently for the two/multiple resource sets that may share other parameters commonly.
Regarding SRI duration of integer multiples of slot (minimum of one-slot SRI duration), it was previously discussed that depending on the periodicity and number and durations and placements of the resources in a set, different SRI durations can be defined. For example, with a periodicity of 1 slot, and all UL-PRS resources of the set also packed next to each other within a slot, an SRI duration of one slot can be achieved. With the supported configuration in the current example, alternatively, to realize such SRI duration, two sets may be configured, with common configuration of UL-PRS resources (e.g., except for the configuration defining the time location of the resources) and covered beam directions, and every other SRI is realized using one set, with a periodicity of 2 slots.
Further, this concept may be reused to define multiple sensing frames (together with their corresponding SRI settings) (e.g., to benefit from different measurements and/or different levels of dynamicity in different parts of the environment/FoV).
Example 13
Extending the UL-PRS configuration to also include the overall duration (e.g., in number of slots) over which, the set (at least for semi-periodic and period sets) occurs with a certain configured periodicity. This allows for a configurable sensing block duration.
Example 14
For UL-PRS, how frequent the periodic occurrence (i.e., the whole sensing block consisting of k*SRI) can be (re-)configured and repeated, which determines the update rate for sensing (the minimum achievable update rate) is related to the signaling limitations.
Extending the UL-PRS configuration to also allow repeating the entire periodic occurrence of a set over certain configured duration (as per extension of Example 13), with a configurable number of slots (>=0) as a gap in between the repetitions. This realizes a configurable update rate. This configuration can be indicated by RRC signaling, MAC CE, or DCI (the latter for more flexibility and less latency). Further, the entire periodic occurrence of a set over certain configured duration, may occur irregularly based on some indications/triggers (i.e., the intervals with the configured durations, can re-occur (start/stop) based on indications). This results in periodic/semi-periodic/aperiodic nature of the entire burst (a burst is a sensing block of Doppler FFT x SRI duration).
Example 15
As mentioned before, for the purpose of positioning, SRS is identified separately, i.e., it is a different configuration. This means that although positioning uses SRS, but in the configuration itself, the purpose is distinguished. Similarly, in one example, extensions of UL-PRS for the purpose of sensing, may also be configured using separate parameters, which imply sensing usage. Alternatively, a “sensing” usage may be defined, similar to “beam management”, “antenna switching”, etc. In an extended example, different sensing usages may be defined, corresponding to different categories of UCs which require different measurements/processing. Accordingly, for each usage, different measurements may also be expected. For example, for sensing UCs which may need inferring channel variations or resolving channel multi-path (multi-path exploitation), e.g., weather monitoring, or (Al-based) gesture recognition, etc., channel measurements may be performed (and may be reported) by the sensing receiver.
Previously, it was mentioned that by enabling UL-PRS-based sensing, the JCAS system can support both UE-based monostatic sensing and gNB-based bi-static sensing (UE being the UL-PRS signal transmitter, and gNB being UL-PRS signal sensing receiver), as well as gNB- based positioning. As such, the methods for interference handling between signals from different UEs, are also applicable for UL-PRS-based sensing scenarios. Further, for the case of gNB-based bi-static sensing (UE being the UL-PRS signal transmitter, and gNB being UL-PRS signal sensing receiver), the UE’s transmit power may not need to be different compared to the case of positioning/communication, since the [sensing] signal travels the same distance between the sensing TX and RX nodes, as for the case of positioning/communication. Accordingly, the existing techniques for interference handling can be adequate also for the case of sensing.
6. Embodiment: Enabling speed and/or direction related measurements to allow velocity estimation in localization/positioning
While UE’s speed estimation by the localization management function (or gNB) is not currently precluded, but UL-PRS signal is not originally designed to support proper velocity estimation. With the discussed adaptations to the UL-PRS signal, it is also possible to perform/report [more accurate] UE’s Doppler related measurements and allow the network and/or gNB, to perform Doppler and direction of movement estimation with better accuracy. For example, currently, as part of performing positioning measurements (e.g., ToA, etc.), correlation function may be applied in delay (range) domain and the peaks in the correlation function can lead to the position estimates. The correlation function may be extended to also have a second dimension in Doppler domain, to enable Doppler processing. This can be similar to generating the 2D periodogram which is part of the baseline object detection receiver processing for sensing applications.
References
[1] IDF AE8858 Numerology, frame structure, and signal resource dimensioning for joint communication and sensing systems
[2] IDF AE9196 Multiplexing and joint design for communication and sensing
[3] Lin X, Lee N. 5G and Beyond. Springer International Publishing; 2021
[4] Hexa-X WP3 first deliverable D3.1 (Section 3.1), published at the end of 2021.
SYSTEMS AND IMPLEMENTATIONS Figures 9-12 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
Figure 9 illustrates a network 900 in accordance with various embodiments. The network 900 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
The network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with a RAN 904 via an over-the-air connection. The UE 902 may be communicatively coupled with the RAN 904 by a Uu interface. The UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
In some embodiments, the network 900 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
In some embodiments, the UE 902 may additionally communicate with an AP 906 via an over-the-air connection. The AP 906 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 904. The connection between the UE 902 and the AP 906 may be consistent with any IEEE 802.11 protocol, wherein the AP 906 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 902, RAN 904, and AP 906 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 902 being configured by the RAN 904 to utilize both cellular radio resources and WLAN resources.
The RAN 904 may include one or more access nodes, for example, AN 908. AN 908 may terminate air-interface protocols for the UE 902 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 908 may enable data/voice connectivity between CN 920 and the UE 902. In some embodiments, the AN 908 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 908 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 908 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
In embodiments in which the RAN 904 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 904 is an LTE RAN) or an Xn interface (if the RAN 904 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
The ANs of the RAN 904 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 902 with an air interface for network access. The UE 902 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 904. For example, the UE 902 and RAN 904 may use carrier aggregation to allow the UE 902 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
The RAN 904 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
In V2X scenarios the UE 902 or AN 908 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
In some embodiments, the RAN 904 may be an LTE RAN 910 with eNBs, for example, eNB 912. The LTE RAN 910 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.
In some embodiments, the RAN 904 may be an NG-RAN 914 with gNBs, for example, gNB 916, or ng-eNBs, for example, ng-eNB 918. The gNB 916 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 916 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 918 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 916 and the ng-eNB 918 may connect with each other over an Xn interface.
In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 914 and a UPF 948 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN914 and an AMF 944 (e.g., N2 interface).
The NG-RAN 914 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 902 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 902, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 902 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 902 and in some cases at the gNB 916. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.
The RAN 904 is communicatively coupled to CN 920 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 902). The components of the CN 920 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 920 may be referred to as a network slice, and a logical instantiation of a portion of the CN 920 may be referred to as a network sub-slice.
In some embodiments, the CN 920 may be an LTE CN 922, which may also be referred to as an EPC. The LTE CN 922 may include MME 924, SGW 926, SGSN 928, HSS 930, PGW 932, and PCRF 934 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 922 may be briefly introduced as follows.
The MME 924 may implement mobility management functions to track a current location of the UE 902 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
The SGW 926 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 922. The SGW 926 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
The SGSN 928 may track a location of the UE 902 and perform security functions and access control. In addition, the SGSN 928 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 924; MME selection for handovers; etc. The S3 reference point between the MME 924 and the SGSN 928 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
The HSS 930 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 930 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 930 and the MME 924 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 920. The PGW 932 may terminate an SGi interface toward a data network (DN) 936 that may include an application/content server 938. The PGW 932 may route data packets between the LTE CN 922 and the data network 936. The PGW 932 may be coupled with the SGW 926 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 932 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 932 and the data network 9 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 932 may be coupled with a PCRF 934 via a Gx reference point.
The PCRF 934 is the policy and charging control element of the LTE CN 922. The PCRF 934 may be communicatively coupled to the app/content server 938 to determine appropriate QoS and charging parameters for service flows. The PCRF 932 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.
In some embodiments, the CN 920 may be a 5GC 940. The 5GC 940 may include an AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, and AF 960 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 940 may be briefly introduced as follows.
The AUSF 942 may store data for authentication of UE 902 and handle authentication- related functionality. The AUSF 942 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 940 over reference points as shown, the AUSF 942 may exhibit an Nausf service-based interface.
The AMF 944 may allow other functions of the 5GC 940 to communicate with the UE 902 and the RAN 904 and to subscribe to notifications about mobility events with respect to the UE 902. The AMF 944 may be responsible for registration management (for example, for registering UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 944 may provide transport for SM messages between the UE 902 and the SMF 946, and act as a transparent proxy for routing SM messages. AMF 944 may also provide transport for SMS messages between UE 902 and an SMSF. AMF 944 may interact with the AUSF 942 and the UE 902 to perform various security anchor and context management functions. Furthermore, AMF 944 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 904 and the AMF 944; and the AMF 944 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 944 may also support NAS signaling with the UE 902 over an N3 IWF interface.
The SMF 946 may be responsible for SM (for example, session establishment, tunnel management between UPF 948 and AN 908); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 948 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 944 over N2 to AN 908; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 902 and the data network 936.
The UPF 948 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 936, and a branching point to support multi-homed PDU session. The UPF 948 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 948 may include an uplink classifier to support routing traffic flows to a data network.
The NSSF 950 may select a set of network slice instances serving the UE 902. The NSSF 950 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 950 may also determine the AMF set to be used to serve the UE 902, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 954. The selection of a set of network slice instances for the UE 902 may be triggered by the AMF 944 with which the UE 902 is registered by interacting with the NSSF 950, which may lead to a change of AMF. The NSSF 950 may interact with the AMF 944 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 950 may exhibit an Nnssf service-based interface.
The NEF 952 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 960), edge computing or fog computing systems, etc. In such embodiments, the NEF 952 may authenticate, authorize, or throttle the AFs. NEF 952 may also translate information exchanged with the AF 960 and information exchanged with internal network functions. For example, the NEF 952 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 952 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 952 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 952 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 952 may exhibit an Nnef service-based interface.
The NRF 954 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 954 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 954 may exhibit the Nnrf service-based interface.
The PCF 956 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 956 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 958. In addition to communicating with functions over reference points as shown, the PCF 956 exhibit an Npcf service-based interface.
The UDM 958 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 902. For example, subscription data may be communicated via an N8 reference point between the UDM 958 and the AMF 944. The UDM 958 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 958 and the PCF 956, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 902) for the NEF 952. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 958, PCF 956, and NEF 952 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 958 may exhibit the Nudm service-based interface.
The AF 960 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
In some embodiments, the 5GC 940 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 902 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 940 may select a UPF 948 close to the UE 902 and execute traffic steering from the UPF 948 to data network 936 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 960 is considered to be a trusted entity, the network operator may permit AF 960 to interact directly with relevant NFs. Additionally, the AF 960 may exhibit an Naf service-based interface.
The data network 936 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 938.
Figure 10 schematically illustrates a wireless network 1000 in accordance with various embodiments. The wireless network 1000 may include a UE 1002 in wireless communication with an AN 1004. The UE 1002 and AN 1004 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
The UE 1002 may be communicatively coupled with the AN 1004 via connection 1006. The connection 1006 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.
The UE 1002 may include a host platform 1008 coupled with a modem platform 1010.
The host platform 1008 may include application processing circuitry 1012, which may be coupled with protocol processing circuitry 1014 of the modem platform 1010. The application processing circuitry 1012 may run various applications for the UE 1002 that source/sink application data. The application processing circuitry 1012 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
The protocol processing circuitry 1014 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1006. The layer operations implemented by the protocol processing circuitry 1014 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.
The modem platform 1010 may further include digital baseband circuitry 1016 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1014 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
The modem platform 1010 may further include transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, and RF front end (RFFE) 1024, which may include or connect to one or more antenna panels 1026. Briefly, the transmit circuitry 1018 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1020 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1022 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1024 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1018, receive circuitry 1020, RF circuitry 1022, RFFE 1024, and antenna panels 1026 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.
In some embodiments, the protocol processing circuitry 1014 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
A UE reception may be established by and via the antenna panels 1026, RFFE 1024, RF circuitry 1022, receive circuitry 1020, digital baseband circuitry 1016, and protocol processing circuitry 1014. In some embodiments, the antenna panels 1026 may receive a transmission from the AN 1004 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1026.
A UE transmission may be established by and via the protocol processing circuitry 1014, digital baseband circuitry 1016, transmit circuitry 1018, RF circuitry 1022, RFFE 1024, and antenna panels 1026. In some embodiments, the transmit components of the UE 1004 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1026.
Similar to the UE 1002, the AN 1004 may include a host platform 1028 coupled with a modem platform 1030. The host platform 1028 may include application processing circuitry 1032 coupled with protocol processing circuitry 1034 of the modem platform 1030. The modem platform may further include digital baseband circuitry 1036, transmit circuitry 1038, receive circuitry 1040, RF circuitry 1042, RFFE circuitry 1044, and antenna panels 1046. The components of the AN 1004 may be similar to and substantially interchangeable with like- named components of the UE 1002. In addition to performing data transmission/reception as described above, the components of the AN 1008 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
Figure 11 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 11 shows a diagrammatic representation of hardware resources 1100 including one or more processors (or processor cores) 1110, one or more memory/storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled via a bus 1140 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 1100.
The processors 1110 may include, for example, a processor 1112 and a processor 1114. The processors 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.
The memory/storage devices 1120 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1120 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.
The communication resources 1130 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 or other network elements via a network 1108. For example, the communication resources 1130 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 1150 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1110 to perform any one or more of the methodologies discussed herein. The instructions 1150 may reside, completely or partially, within at least one of the processors 1110 (e.g., within the processor’s cache memory), the memory/storage devices 1120, or any suitable combination thereof. Furthermore, any portion of the instructions 1150 may be transferred to the hardware resources 1100 from any combination of the peripheral devices 1104 or the databases 1106. Accordingly, the memory of processors 1110, the memory/storage devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.
Figure 12 illustrates a network 1200 in accordance with various embodiments. The network 1200 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1200 may operate concurrently with network 900. For example, in some embodiments, the network 1200 may share one or more frequency or bandwidth resources with network 900. As one specific example, a UE (e.g., UE 1202) may be configured to operate in both network 1200 and network 900. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 900 and 1200. In general, several elements of network 1200 may share one or more characteristics with elements of network 900. For the sake of brevity and clarity, such elements may not be repeated in the description of network 1200.
The network 1200 may include a UE 1202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1208 via an over-the-air connection. The UE 1202 may be similar to, for example, UE 902. The UE 1202 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.
Although not specifically shown in Figure 12, in some embodiments the network 1200 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 12, the UE 1202 may be communicatively coupled with an AP such as AP 906 as described with respect to Figure 9. Additionally, although not specifically shown in Figure 12, in some embodiments the RAN 1208 may include one or more ANss such as AN 908 as described with respect to Figure 9. The RAN 1208 and/or the AN of the RAN 1208 may be referred to as a base station (BS), a RAN node, or using some other term or name.
The UE 1202 and the RAN 1208 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.
The RAN 1208 may allow for communication between the UE 1202 and a 6G core network (CN) 1210. Specifically, the RAN 1208 may facilitate the transmission and reception of data between the UE 1202 and the 6G CN 1210. The 6G CN 1210 may include various functions such as NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, AF 960, SMF 946, and AUSF 942. The 6G CN 1210 may additional include UPF 948 and DN 936 as shown in Figure 12.
Additionally, the RAN 1208 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1224 and a Compute Service Function (Comp SF) 1236. The Comp CF 1224 and the Comp SF 1236 may be parts or functions of the Computing Service Plane. Comp CF 1224 may be a control plane function that provides functionalities such as management of the Comp SF 1236, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc.. Comp SF 1236 may be a user plane function that serves as the gateway to interface computing service users (such as UE 1202) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1236 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1236 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1224 instance may control one or more Comp SF 1236 instances.
Two other such functions may include a Communication Control Function (Comm CF) 1228 and a Communication Service Function (Comm SF) 1238, which may be parts of the Communication Service Plane. The Comm CF 1228 may be the control plane function for managing the Comm SF 1238, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 1238 may be a user plane function for data transport. Comm CF 1228 and Comm SF 1238 may be considered as upgrades of SMF 946 and UPF 948, which were described with respect to a 5G system in Figure 9. The upgrades provided by the Comm CF 1228 and the Comm SF 1238 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 946 and UPF 948 may still be used.
Two other such functions may include a Data Control Function (Data CF) 1222 and Data Service Function (Data SF) 1232 may be parts of the Data Service Plane. Data CF 1222 may be a control plane function and provides functionalities such as Data SF 1232 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 1232 may be a user plane function and serve as the gateway between data service users (such as UE 1202 and the various functions of the 6G CN 1210) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.
Another such function may be the Service Orchestration and Chaining Function (SOCF) 1220, which may discover, orchestrate and chain up communication/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 1220 may interact with one or more of Comp CF 1224, Comm CF 1228, and Data CF 1222 to identify Comp SF 1236, Comm SF 1238, and Data SF 1232 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1236, Comm SF 1238, and Data SF 1232 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 1220 may also responsible for maintaining, updating, and releasing a created service chain.
Another such function may be the service registration function (SRF) 1214, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 1236 and Data SF 1232 gateways and services provided by the UE 1202. The SRF 1214 may be considered a counterpart of NRF 954, which may act as the registry for network functions.
Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 1226, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 1212 and eSCP- U 1234, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 1226 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.
Another such function is the AMF 1244. The AMF 1244 may be similar to 944, but with additional functionality. Specifically, the AMF 1244 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1244 to the RAN 1208.
Another such function is the service orchestration exposure function (SOEF) 1218. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.
The UE 1202 may include an additional function that is referred to as a computing client service function (comp CSF) 1204. The comp CSF 1204 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1220, Comp CF 1224, Comp SF 1236, Data CF 1222, and/or Data SF 1232 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 1204 may also work with network side functions to decide on whether a computing task should be run on the UE 1202, the RAN 1208, and/or an element of the 6G CN 1210.
The UE 1202 and/or the Comp CSF 1204 may include a service mesh proxy 1206. The service mesh proxy 1206 may act as a proxy for service-to- service communication in the user plane. Capabilities of the service mesh proxy 1206 may include one or more of addressing, security, load balancing, etc.
EX MPLE PROCEDURES
In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 9-12, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 13. The process may relate to a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include and/or implement a base station. The process may include receiving, at 1301 from a user equipment (UE), an uplink positioning reference signal (UL-PRS); and performing, at 1302, sensing based on the UL-PRS.
Another such process is depicted in Figure 14. The process of Figure 14 may relate to a method to be performed by a user equipment (UE), one or more elements of a UE, and/or one or more electronic devices that include or implement a UE. The process may include identifying, at 1401, one or more sensing-related parameters; generating, at 1402 based on the one or more sensing-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, at 1403 to a base station, the UL-PRS, wherein the base station is to use the UL-PRS for sensing.
Another such process is depicted in Figure 15. The process of Figure 15 may relate to a method to be performed by an electronic device (e.g., a user equipment (UE) in a cellular network. The process may include identifying, at 1501, an uplink positioning reference signal (UL-PRS) resource related to sensing to be performed during a sensing operation, wherein a UL- PRS resource includes a plurality of UL-PRS symbols. In some embodiments, the UL-PRS resource may be based on a fifth generation (5G) new radio (NR) sounding reference signal (SRS); generating, at 1502, a cellular transmission that includes a symbol repetition interval (SRI) composed of or based on the UL-PRS resource; and transmitting, at 1503, the cellular transmission during performance of the sensing operation.
For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
EXAMPLES
Example 1 may include an apparatus used in a sensing entity wherein the apparatus comprises processor circuitry configured to cause the sensing entity to map and transmit the modulated symbols, according to 5G NR Uplink (UL) Positioning Reference Signal (PRS) design, wherein the following equivalences are used (marked with <->)
• UL-PRS resource sensing beam (for UL-based positioning, single port UL-PRS resource is supported, i.e., each UL-PRS resource is dedicated for transmission in a single direction). A resource corresponds to an SRS beam, and resource sets correspond to a collection of SRS resource (i.e., beams) aimed at a given TRP.
• The number of PRS resources within a PRS resource set the number of beam directions in SRI. This is also related to the number of OFDM symbols in each SRS resource of the set and how they are located. For sensing, smaller comb- sizes are preferred, because compared to the larger size combs, they utilize more subcarriers and provide more intra-SRI flexibility of assigning OFDM symbols to different directions and/or for different purposes (UL-PRS vs non-PRS), while also imposes less limitation on the maximum unambiguously detectable range.
• Resource set together with periodicity/repetition parameters and the number and distancing of resources within the set SRI (collection of one occurrence of all PRS resources within the set). In an SRS resource set, multiple SRS resources, each for one direction is transmitted. For comb-2/2-OS, there can be 1, 2, 4, or 6 repetitions within one SRS resource. This is equivalent to using multiple SRI symbols for repetition of a same direction and processing gain.
• The entire time interval which contains repetitions of resource set with its periodicity (i.e., repetitions of SRI) sensing block - possible durations is based on network configuration. Across SRIs within a sensing block, the number and pattern of sensing resources and directions is configured the same to achieve consistent configuration of SRS resources in periodic occurrences of SRS resource sets. The same number and placement of OFDM symbols across all SRIs is also considered for non-PRS transmissions. The number of repetitions of SRS resource set Doppler FFT size, K.
• How frequent periodic occurrence can be (re-)configured update rate for sensing (the minimum achievable update rate may be related to the signaling limitations).
Example 2 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration also allows single-symbol and three-symbol PRS resources.
Example 3 may include the apparatus of example 1 or some other example herein, wherein use of consecutive subcarriers over one OFDM symbol by UL-PRS or PRS-like signal is also supported, with or without repetitions within an UL-PRS resource. Comb-1 means use of consecutive subcarriers over the OFDM symbol (extension to allow use of consecutive subcarriers over one symbol; examples may include single symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS (SRS) resource).
Example 4 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to support a comb size from of { 1, 2, 4, 8}, or { 1, 2, 3, 4, 8}, where comb-3 may be applicable to UL-PRS resource duration of 1 or 3 or 12 OS.
Example 5 may include the apparatus of example 5 or some other example herein, wherein different sets of subcarriers (e.g., realized with different frequency domain RE offsets), are used to handle the interference from the signals used for sensing, from the close-by UEs.
Example 6 may include the apparatus of example 1 or some other example herein, wherein use of partially staggered patterns for UL-PRS or PRS-like signals that may be defined by M-level comb and N symbols for an UL-PRS resource with M > N, is also supported.
Example 7 may include the apparatus of example 1 or some other example herein, wherein unstaggered patterns for UL-PRS or PRS-like signals are supported such that the same resource elements (REs) are used in consecutive symbols within an UL-PRS resource; examples may include:
• Every other subcarrier over one symbol, without staggering over multiple symbols. • Every 3rd subcarrier within one symbol, without staggering over multiple symbols.
Example 8 may include the apparatus of example 1 or some other example herein, wherein combinations of fully or partially staggered and unstaggered patterns for PRS or PRS- like signals are supported.
Example 9 may include the apparatus of example 1 or some other example herein, wherein use of all symbols within a slot for PRS allocation is supported, i.e., the configuration is extended to allow for a slot being fully occupied by UL-PRS resources from one or multiple sets (i.e., possible to have zero resources for non-UL-PRS purposes in a slot).
Example 10 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows accommodation of inconsecutive OFDM symbols (minimum of two inconsecutive symbols) for non-UL-PRS transmission within the PRS slot.
Example 11 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows multi-port UL-PRS resource transmission, enabling sending multiple beams at different directions at the same time.
Example 12 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow inconsecutive (and preferably, symmetric over the two half-slots) allocation of OFDM symbols per PRS resource within a slot, to enable realizing sub- slot- level SRI duration (e.g., half-slot), using one UL-PRS resource set. For example, a comb-2 UL-PRS resource of length 4, may be realized with an equal split of the 4 symbols over two 2-symbol occurrences each in one half-slot. Inconsecutive allocation of OFDM symbols for one PRS resource, may be achieved by different means, e.g., through enabling configuration of the PRS resource symbol offset by a vector, etc.
Example 13 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows configuring periodicity at the granularity of UL-PRS resource (e.g., per UL-PRS resource) as against defining them at the resource set level. As such, different resources within the set are able to have different periodicities, to help better spatial adjustments to cover the field of view.
Example 14 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows the periodicity of half-slot (e.g., for higher speed usecases, etc.).
Example 15 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows for multiple levels of periodicity control (to allow multiple/different repetition patterns), so as to enable a fast periodicity (scan rate) for rapidly gathering a number of UL-PRS resources, followed by a slower periodicity to enable a waiting period for dedicated communications before the next rapid period.
Example 16 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration allows for a fully programmable rapid burst of UL-PRS transmissions/acquisitions. The burst of transmissions/acquisitions needs to occur at a faster rate than DCI updates, so it must contain all of the necessary parameters without need for interruption by DCI or RRC re-configuration. Rate of transmission/acquisition (the update rate for a full doppler FFT x SRI duration), number of transmissions/acquisitions, as well as normal UE-PRS parameters such as OFDM symbol position within RB, comb size, and cyclic offset need to be set independently for the burst of transmissions/acquisitions.
Example 17 may include the apparatus of example 1 or some other example herein, wherein UE-PRS configuration allows for different power control parameters for resources within a set, i.e., to allow PC configuration per UL-PRS resource (beam).
Example 18 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for multiple (two or more) UL-PRS resource sets with potentially same resource settings within the sets (i.e., same time/frequency domain placement, same spatial configuration of resources, same resource pattern, etc., potentially except for the configuration defining the starting time location of the resources), which can be TDMed even within one slot, to enable realizing different (e.g., two or more) Symbol Repetition Intervals (SRIs) using different (e.g., two or more) sets, and their repetitions. Similar to the apparatus of example 12, this extension enables realizing sub-slot-level SRI duration (e.g., half-slot), or SRIs of durations of non-integer multiple of slots (e.g., 1.5 slot, etc.), but instead, by using two or more UL-PRS resource sets. For example, the starting symbol offset within a slot, and (if needed) the numbers of symbols for an UL-PRS resource, may be configured differently for the two/multiple resource sets that may share other parameters commonly.
Example 19 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for separate parameters and/or usage for configuring UL-PRS for the purpose of sensing.
Example 20 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to allow for different sensing usages, corresponding to different categories of use-cases which require different measurements/processing. Accordingly, for each usage, different measurements may also be expected.
Example 21 may include the apparatus of example 20 or some other example herein, wherein for sensing use-cases which may need inferring channel variations or resolving channel multi-path (multi-path exploitation), e.g., weather monitoring, or (Al-based) gesture recognition, etc., channel measurements may be performed (and may be reported) by the sensing receiver.
Example 22 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to also include the overall duration (e.g., in number of slots) over which, the set (at least for semi-periodic and period sets) occurs with a certain configured periodicity.
Example 23 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to also allow repeating the entire periodic occurrence of a set over certain configured duration (as per extension of example 22), with a configurable number of slots (>=0) as a gap in between the repetitions.
Example 24 may include the apparatus of example 23 or some other example herein, wherein the configuration can be indicated by RRC signaling, MAC CE, or DCI.
Example 25 may include the apparatus of example 1 or some other example herein, wherein the entire periodic occurrence of a set over a certain configured duration, may occur irregularly based on some indications/triggers (i.e., the intervals with the configured durations, can re-occur (start/stop) based on indications).
Example 26 may include the apparatus of example 1 or some other example herein, wherein UL-PRS configuration is extended to also allow multiple periodicities for an UL-PRS (SRS) resource set configuration, potentially each with an overall effective duration over which the periodic pattern with the corresponding periodicity continues (e.g., in number of slots, etc.).
Example 27 may include an apparatus used in a positioning entity to localize User Equipment (UE), wherein the apparatus comprises processor circuitry configured to also generate UE’s Doppler-related measurements based on transmitted UL-PRS signal (or an extended version of PRS signal according to examples 1-26). For example, currently, as part of performing positioning measurements (e.g., ToA, etc.), correlation function may be applied in delay (range) domain and the peaks in the correlation function can lead to the position estimates. The correlation function may be extended to also have a second dimension in Doppler domain, to enable Doppler processing. This can be similar to generating the 2D periodogram which is part of the baseline object detection receiver processing for sensing applications.
Example 28 includes a method to be performed by a base station, one or more elements of a base station, and/or one or more electronic devices that include and/or implement a base station, wherein the method comprises: receiving, from a user equipment (UE), an uplink positioning reference signal (UL-PRS); and performing sensing based on the UL-PRS.
Example 29 includes the method of example 28, and/or some other example herein, further comprising identifying, based on a UL-PRS resource of the UL-PRS, a sensing beam for sensing. Example 30 includes the method of any of examples 28-29, and/or some other example herein, further comprising identifying, based on a number of PRS resources within a PRS resource set of the UL-PRS, a number of beam directions in a symbol repetition interval (SRI).
Example 31 includes the method of any of examples 28-30, and/or some other example herein, further comprising identifying, based on a resource set of the UL-PRS, the SRI.
Example 32 includes the method of any of examples 28-31, and/or some other example herein, further comprising identifying, based on a time interval which contains repetitions of a resource set with its periodicity related to the UL-PRS, a sensing block.
Example 33 includes the method of any of examples 28-32, and/or some other example herein, further comprising identifying, based on a periodic occurrence frequency of the UL-PRS, an update rate for sensing.
Example 34 includes a method to be performed by a user equipment (UE), one or more elements of a UE, and/or one or more electronic devices that include or implement a UE, wherein the method comprises: identifying one or more sensing-related parameters; generating, based on the one or more sensing-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, to a base station, the UL-PRS, wherein the base station is to use the UL-PRS for sensing.
Example 35 includes the method of example 34, and/or some other example herein, wherein the one or more sensing-related parameters include a sensing beam for sensing, and wherein the UL-PRS includes a UL-PRS resource based on the sensing beam.
Example 36 includes the method of any of examples 34-35, and/or some other example herein, wherein the one or more sensing-related parameters include a number of beam directions in a symbol repetition interval (SRI), and wherein the UL-PRS includes a number of PRS resources within a PRS resource set of the UL-PRS based on the number of beam directions.
Example 37 includes the method of any of examples 34-36, and/or some other example herein, wherein the one or more sensing-related parameters include the SRI, and wherein the UL-PRS includes a resource set of the UL-PRS based on the SRI.
Example 38 includes the method of any of examples 34-37, and/or some other example herein, wherein the one or more sensing-related parameters include a sensing block, and wherein the UL-PRS includes a time interval which contains repetitions of a resource set with its periodicity related to the UL-PRS based on the sensing block.
Example 39 includes the method of any of examples 34-38, and/or some other example herein, wherein the sensing-related parameter is an update rate for sensing, and wherein the UL- PRS includes a periodic occurrence frequency of the UL-PRS based on the update rate. Example 40 includes a method to be performed by an electronic device in a cellular network, wherein the method comprises: identifying an uplink positioning reference signal (UL- PRS) resource related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; generating a cellular transmission that includes a symbol repetition interval (SRI) composed of the UL-PRS resource; and transmitting the cellular transmission during performance of the sensing operation.
Example 41 includes the method of example 40, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
Example 42 includes the method of any of examples 40-41, and/or some other example herein, further comprising: identifying a frequency domain comb size from the set { 1, 2, 3, 4, 8 } ; mapping, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and mapping, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OLDM symbol.
Example 43 includes the method of example 42, and/or some other example herein, wherein the plurality of UL-PRS symbols are mapped to a subset of the OLDM symbols of the slot.
Example 44 includes the method of example 43, and/or some other example herein, wherein OLDM symbols that are not in the subset of OLDM symbols are inconsecutive.
Example 45 includes the method of example 43, and/or some other example herein, further comprising mapping UL-PRS symbols of a second UL-PRS resource of a second UL- PRS resource set to a second subset of OLDM symbols of the slot.
Example 46 includes the method of any of examples 40-45, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a bilevel comb over N UL-PRS symbols, wherein M is greater than N.
Example 47 includes the method of example 46, and/or some other example herein, wherein resource elements (REs) of consecutive UL-PRS symbols of the plurality of UL-PRS symbols are the same as one another.
Example 48 includes the method of any of examples 40-47, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
Example 49 includes the method of any of examples 40-48, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level. Example 50 includes the method of example 49, and/or some other example herein, wherein the UL-PRS periodicity is based on half of a length of a slot, the length of one slot, or an integer multiplication of the length of one slot.
Example 51 includes the method of any of examples 40-50, and/or some other example herein, wherein the UL-PRS resource is based on an indication of a UL-PRS configuration received via radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), or downlink control information (DCI).
Example 52 includes the method of any of examples 40-51, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
LExample 53 includes a^A- user equipment (UE) comprising: memory to store an uplink positioning reference signal (UL-PRS) resource based on a 5G NR Sounding Reference Signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; and one or more processors configured to: generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation.
Example 54 includes the subject matter of example 53, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
Example 55 includes the subject matter of any of examples 53-54, and/or some other example herein, wherein the one or more processors are further configured to: identify a frequency domain comb size from the set { 1, 2, 3, 4, 8}; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OLDM symbol.
Example 56 includes the subject matter of example 55, and/or some other example herein, wherein the plurality of UL-PRS symbols are mapped to a subset of the OLDM symbols of the slot.
Example 57 includes the subject matter of example 56, and/or some other example herein, wherein OLDM symbols that are not in the subset of OLDM symbols are inconsecutive. Example 58 includes the subject matter of example 56, wherein the one or more processors are further configured to map UL-PRS symbols of a second UL-PRS resource of a second UL-PRS resource set to a second subset of OFDM symbols of the slot.
Example 59 includes the subject matter of any of examples 53-58, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
Example 60 includes the subject matter of example 59, and/or some other example herein, wherein resource elements (REs) of consecutive UL-PRS symbols of the plurality of UL- PRS symbols are the same as one another.
Example 61 includes the subject matter of any of examples 53-60, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
Example 62 includes the subject matter of any of examples 53-61, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
Example 63 includes the subject matter of example 62, and/or some other example herein, wherein the UL-PRS periodicity is based on half of a length of a slot, the length of one slot, or an integer multiplication of the length of one slot.
Example 64 includes the subject matter of any of examples 53-63, and/or some other example herein, wherein the UL-PRS resource is based on an indication of a UL-PRS configuration received via radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), or downlink control information (DCI).
Example 65 includes the subject matter of any of examples 53-64, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL- PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
Example 66 includes one or more non-transitory computer-readable media (NTCRM) comprising instructions that, upon execution of the instructions by one or more processors of a user equipment (UE), are to cause the UE to: identify an uplink positioning reference signal (UL-PRS) resource based on a fifth generation (5G) new radio (NR) sounding reference signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation. Example 67 includes the subject matter of example 66, and/or some other example herein, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
Example 68 includes the subject matter of any of examples 66-67, and/or some other example herein, wherein the instructions are further to cause the UE to: identify a frequency domain comb size from the set { 1, 2, 3, 4, 8}; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OFDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OFDM symbol.
Example 69 includes the subject matter of any of examples 66-68, and/or some other example herein, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
Example 70 includes the subject matter of any of examples 66-69, and/or some other example herein, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
Example 71 includes the subject matter of any of examples 66-70, and/or some other example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
Example 72 includes the subject matter of any of examples 66-71, and/or some other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL- PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-72, or any other method or process described herein.
Example Z04 may include a method, technique, or process as described in or related to any of examples 1-72, or portions or parts thereof.
Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
Example Z06 may include a signal as described in or related to any of examples 1-72, or portions or parts thereof.
Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z08 may include a signal encoded with data as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-72, or portions or parts thereof, or otherwise described in the present disclosure.
Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-72, or portions thereof.
Example Z12 may include a signal in a wireless network as shown and described herein.
Example Z13 may include a method of communicating in a wireless network as shown and described herein.
Example Z14 may include a system for providing wireless communication as shown and described herein.
Example Z15 may include a device for providing wireless communication as shown and described herein.
Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. Abbreviations
Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.
3GPP Third Network BFD Beam
Generation AnLF Analytics Failure Detection
Partnership Logical Function BLER Block Error
Project ANR Automatic Rate
4G Fourth 40 Neighbour Relation 75 BPSK Binary Phase
Generation AOA Angle of Shift Keying
5G Fifth Arrival BRAS Broadband
Generation AP Application Remote Access
5GC 5G Core Protocol, Antenna Server network 45 Port, Access Point 80 BSS Business
AC API Application Support System
Application Programming Interface BS Base Station
Client APN Access Point BSR Buffer Status
ACR Application Name Report
Context Relocation 50 ARP Allocation and 85 BW Bandwidth
ACK Retention Priority BWP Bandwidth Part
Acknowledgem ARQ Automatic C-RNTI Cell ent Repeat Request Radio Network
ACID AS Access Stratum Temporary
Application 55 ASP 90 Identity
Client Identification Application Service CA Carrier
ADRF Analytics Data Provider Aggregation,
Repository Certification
Function ASN.1 Abstract Syntax Authority
AF Application 60 Notation One 95 CAPEX CAPital
Function AUSF Authentication Expenditure
AM Acknowledged Server Function CBD Candidate
Mode AWGN Additive Beam Detection
AMBR Aggregate White Gaussian CBRA Contention
Maximum Bit Rate 65 Noise 100 Based Random
AMF Access and BAP Backhaul Access
Mobility Adaptation Protocol CC Component
Management BCH Broadcast Carrier, Country
Function Channel Code, Cryptographic
AN Access 70 BER Bit Error Ratio 105 Checksum CCA Clear Channel Mandatory Network, Cloud Assessment CMAS Commercial RAN CCE Control Mobile Alert Service CRB Common Channel Element CMD Command Resource Block CCCH Common 40 CMS Cloud 75 CRC Cyclic Control Channel Management System Redundancy Check CE Coverage CO Conditional CRI Channel-State Enhancement Optional Information CDM Content CoMP Coordinated Resource Delivery Network 45 Multi-Point 80 Indicator, CSI-RS CDMA Code- CORESET Control Resource Division Multiple Resource Set Indicator Access COTS Commercial C-RNTI Cell
CDR Charging Data Off-The-Shelf RNTI Request 50 CP Control Plane, 85 CS Circuit
CDR Charging Data Cyclic Prefix, Switched Response Connection CSCF call
CFRA Contention Free Point session control function Random Access CPD Connection CSAR Cloud Service CG Cell Group 55 Point Descriptor 90 Archive CGF Charging CPE Customer CSI Channel-State
Gateway Function Premise Information CHF Charging Equipment CSI-IM CSI
Function CPICH Common Pilot Interference
CI Cell Identity 60 Channel 95 Measurement CID Cell-ID (e.g., CQI Channel CSI-RS CSI positioning method) Quality Indicator Reference Signal CIM Common CPU CSI processing CSI-RSRP CSI Information Model unit, Central reference signal CIR Carrier to 65 Processing Unit 100 received power Interference Ratio C/R CSI-RSRQ CSI CK Cipher Key Command/Resp reference signal CM Connection onse field bit received quality Management, CRAN Cloud Radio CSI-SINR CSI
Conditional 70 Access 105 signal-to-noise and interference Reference Signal ED Energy ratio DN Data network Detection
CSMA Carrier Sense DNN Data Network EDGE Enhanced
Multiple Access Name Datarates for GSM
CSMA/CA CSMA 40 DNAI Data Network 75 Evolution with collision Access Identifier (GSM Evolution) avoidance EAS Edge
CSS Common DRB Data Radio Application Server
Search Space, CellBearer EASID Edge specific Search 45 DRS Discovery 80 Application Server
Space Reference Signal Identification
CTF Charging DRX Discontinuous ECS Edge
Trigger Function Reception Configuration Server
CTS Clear-to-Send DSL Domain ECSP Edge
CW Codeword 50 Specific Language. 85 Computing Service
CWS Contention Digital Provider
Window Size Subscriber Line EDN Edge
D2D Device-to- DSLAM DSL Data Network
Device Access Multiplexer EEC Edge
DC Dual 55 DwPTS 90 Enabler Client
Connectivity, Direct Downlink Pilot EECID Edge Current Time Slot Enabler Client
DCI Downlink E-LAN Ethernet Identification
Control Local Area Network EES Edge
Information 60 E2E End-to-End 95 Enabler Server
DF Deployment EAS Edge EESID Edge
Flavour Application Server Enabler Server
DL Downlink ECCA extended clear Identification
DMTF Distributed channel EHE Edge
Management Task 65 assessment, 100 Hosting Environment
Force extended CCA EGMF Exposure
DPDK Data Plane ECCE Enhanced Governance
Development Kit Control Channel Management
DM-RS, DMRS Element, Function Demodulation 70 Enhanced CCE 105 EGPRS Enhanced ETSI European Channel
GPRS Telecommunica FAUSCH Fast
EIR Equipment tions Standards Uplink Signalling Identity Register Institute Channel eLAA enhanced 40 ETWS Earthquake and 75 FB Functional Licensed Assisted Tsunami Warning Block
Access, System FBI Feedback enhanced LAA eUICC embedded Information EM Element UICC, embedded FCC Federal Manager 45 Universal 80 Communications eMBB Enhanced Integrated Circuit Commission Mobile Card FCCH Frequency
Broadband E-UTRA Evolved Correction CHannel
EMS Element UTRA FDD Frequency
Management System 50 E-UTRAN Evolved 85 Division Duplex eNB evolved NodeB, UTRAN FDM Frequency E-UTRAN Node B EV2X Enhanced V2X Division EN-DC E- F1AP Fl Application Multiplex UTRA-NR Dual Protocol FDMA Frequency
Connectivity 55 Fl-C Fl Control 90 Division Multiple EPC Evolved Packet plane interface Access Core Fl-U Fl User plane FE Front End EPDCCH interface FEC Forward Error enhanced FACCH Fast Correction PDCCH, enhanced 60 Associated Control 95 FFS For Further
Physical CHannel Study
Downlink Control FACCH/F Fast FFT Fast Fourier Cannel Associated Control Transformation
EPRE Energy per Channel/Full feLAA further resource element 65 rate 100 enhanced Licensed EPS Evolved Packet FACCH/H Fast Assisted System Associated Control Access, further
EREG enhanced REG, Channel/Half enhanced LAA enhanced resource rate FN Frame Number element groups 70 FACH Forward Access 105 FPGA Field- Programmable Gate Generation HFN HyperFrame
Array NodeB Number FR Frequency distributed unit HHO Hard Handover Range GNSS Global HLR Home Location FQDN Fully 40 Navigation Satellite 75 Register Qualified Domain System HN Home Network Name GPRS General Packet HO Handover
G-RNTI GERAN Radio Service HPLMN Home
Radio Network GPS I Generic Public Land Mobile
Temporary 45 Public Subscription 80 Network
Identity Identifier HSDPA High
GERAN GSM Global System Speed Downlink
GSM EDGE for Mobile Packet Access
RAN, GSM EDGE Communication HSN Hopping
Radio Access 50 s, Groupe Special 85 Sequence Number
Network Mobile HSPA High Speed
GGSN Gateway GPRS GTP GPRS Packet Access Support Node Tunneling Protocol HSS Home GLONASS GTP-UGPRS Subscriber Server
GLObal'naya 55 Tunnelling Protocol 90 HSUPA High
NAvigatsionnay for User Plane Speed Uplink Packet a Sputnikovaya GTS Go To Sleep Access Sistema (Engl.: Signal (related HTTP Hyper Text Global Navigation to WUS) Transfer Protocol
Satellite 60 GUMMEI Globally 95 HTTPS Hyper
System) Unique MME Text Transfer Protocol gNB Next Identifier Secure (https is Generation NodeB GUTI Globally http/ 1.1 over gNB-CU gNB- Unique Temporary SSL, i.e. port 443) centralized unit, Next 65 UE Identity 100 I-Block
Generation HARQ Hybrid ARQ, Information
NodeB Hybrid Block centralized unit Automatic ICCID Integrated gNB-DU gNB- Repeat Request Circuit Card distributed unit, Next 70 HANDO Handover 105 Identification IAB Integrated , IP Multimedia IS In Sync
Access and IMC IMS IRP Integration
Backhaul Credentials Reference Point
ICIC Inter-Cell IMEI International ISDN Integrated
Interference 40 Mobile 75 Services Digital
Coordination Equipment Network
ID Identity, Identity ISIM IM Services identifier IMGI International Identity Module
IDFT Inverse Discrete mobile group identity ISO International
Fourier 45 IMPI IP Multimedia 80 Organisation for
Transform Private Identity Standardisation
IE Information IMPU IP Multimedia ISP Internet Service element PUblic identity Provider
IBE In-Band IMS IP Multimedia IWF Interworking-
Emission 50 Subsystem 85 Function
IEEE Institute of IMSI International I-WLAN
Electrical and Mobile Interworking
Electronics Subscriber WLAN
Engineers Identity Constraint
IEI Information 55 loT Internet of 90 length of the
Element Things convolutional
Identifier IP Internet code, USIM
IEIDL Information Protocol Individual key
Element Ipsec IP Security, kB Kilobyte (1000
Identifier Data 60 Internet Protocol 95 bytes)
Length Security kbps kilo-bits per
IETF Internet IP-CAN IP- second
Engineering Task Connectivity Access Kc Ciphering key
Force Network Ki Individual
IF Infrastructure 65 IP-M IP Multicast 100 subscriber
IIOT Industrial IPv4 Internet authentication
Internet of Things Protocol Version 4 key
IM Interference IPv6 Internet KPI Key
Measurement, Protocol Version 6 Performance Indicator
Intermodulation 70 IR Infrared 105 KQI Key Quality Indicator LMF Location (TSG T WG3 context)
KSI Key Set Management Function MAC-IMAC used for Identifier LOS Line of data integrity of ksps kilo-symbols Sight signalling messages per second 40 LPLMN Local 75 (TSG T WG3 context) KVM Kernel Virtual PLMN MANO Machine LPP LTE Management
LI Layer 1 Positioning Protocol and Orchestration (physical layer) LSB Least MBMS Ll-RSRP Layer 1 45 Significant Bit 80 Multimedia reference signal LTE Long Term Broadcast and received power Evolution Multicast
L2 Layer 2 (data LWA LTE-WLAN Service link layer) aggregation MBSFN L3 Layer 3 50 LWIP LTE/WLAN 85 Multimedia
(network layer) Radio Level Broadcast LAA Licensed Integration with multicast Assisted Access IPsec Tunnel service Single LAN Local Area LTE Long Term Frequency Network 55 Evolution 90 Network
LADN Local M2M Machine-to- MCC Mobile Country Area Data Network Machine Code LBT Listen Before MAC Medium Access MCG Master Cell Talk Control Group
LCM LifeCycle 60 (protocol 95 MCOT Maximum Management layering context) Channel
LCR Low Chip Rate MAC Message Occupancy LCS Location authentication code Time Services (security/encryption MCS Modulation and
LCID Logical 65 context) 100 coding scheme Channel ID MAC-A MAC MD AF Management
LI Layer Indicator used for Data Analytics LLC Logical Link authentication Function Control, Low Layer and key MDAS Management Compatibility 70 agreement 105 Data Analytics Service Physical Downlink Terminated, Mobile
MDT Minimization of Control Termination
Drive Tests CHannel MTC Machine-Type
ME Mobile MPDSCH MTC Communication
Equipment 40 Physical Downlink 75 s
MeNB master eNB Shared MTLF Model Training
MER Message Error CHannel Logical
Ratio MPRACH MTC Functions
MGL Measurement Physical Random mMTCmassive MTC,
Gap Length 45 Access 80 massive
MGRP Measurement CHannel Machine-Type
Gap Repetition MPUSCH MTC Communication
Period Physical Uplink Shared s
MIB Master Channel MU-MIMO Multi
Information Block, 50 MPLS MultiProtocol 85 User MIMO
Management Label Switching MWUS MTC
Information Base MS Mobile Station wake-up signal, MTC
MIMO Multiple Input MSB Most WUS
Multiple Output Significant Bit NACK Negative
MLC Mobile 55 MSC Mobile 90 Acknowledgement
Location Centre Switching Centre NAI Network
MM Mobility MSI Minimum Access Identifier
Management System NAS Non-Access
MME Mobility Information, Stratum, Non- Access
Management Entity 60 MCH Scheduling 95 Stratum layer MN Master Node Information NCT Network
MNO Mobile MSID Mobile Station Connectivity
Network Operator Identifier Topology
MO Measurement MSIN Mobile Station NC-JT Non¬
Object, Mobile 65 Identification 100 coherent Joint
Originated Number Transmission
MPBCH MTC MSISDN Mobile NEC Network
Physical Broadcast Subscriber ISDN Capability
CHannel Number Exposure
MPDCCH MTC 70 MT Mobile 105 NE-DC NR-E- UTRA Dual CHannel NSA Non-Standalone
Connectivity NPDCCH operation mode
NEF Network Narrowband NSD Network
Exposure Function Physical Service Descriptor
NF Network 40 Downlink 75 NSR Network
Function Control CHannel Service Record
NFP Network NPDSCH NSS Al Network Slice
Forwarding Path Narrowband Selection
NFPD Network Physical Assistance
Forwarding Path 45 Downlink 80 Information
Descriptor Shared CHannel S-NNSAI Single-
NFV Network NPRACH NSSAI
Functions Narrowband NSSF Network Slice
Virtualization Physical Random Selection Function
NFVI NFV 50 Access CHannel 85 NW Network
Infrastructure NPUSCH NWDAF Network
NFVO NFV Narrowband Data Analytics
Orchestrator Physical Uplink Function
NG Next Shared CHannel NWUS Narrowband
Generation, Next Gen 55 NPSS Narrowband 90 wake-up signal,
NGEN-DC NG- Primary Narrowband WUS
RAN E-UTRA-NR Synchronization NZP Non-Zero
Dual Connectivity Signal Power
NM Network NSSS Narrowband O&M Operation and
Manager 60 Secondary 95 Maintenance
NMS Network Synchronization ODU2 Optical channel
Management System Signal Data Unit - type 2
N-PoP Network Point NR New Radio, OFDM Orthogonal of Presence Neighbour Relation Frequency Division NMIB, N-MIB 65 NRF NF Repository 100 Multiplexing Narrowband MIB Function OFDMA NPBCH NRS Narrowband Orthogonal
Narrowband Reference Signal Frequency Division
Physical NS Network Multiple Access
Broadcast 70 Service 105 OOB Out-of-band OOS Out of and Charging Rules Measurement
Sync Function PMI Precoding
OPEX OPerating PDCP Packet Data Matrix Indicator
EXpense Convergence PNF Physical
OSI Other System 40 Protocol, Packet 75 Network Function Information Data Convergence PNFD Physical
OSS Operations Protocol layer Network Function Support System PDCCH Physical Descriptor OTA over-the-air Downlink Control PNFR Physical
PAPR Peak-to- 45 Channel 80 Network Function
Average Power PDCP Packet Data Record
Ratio Convergence Protocol POC PTT over
PAR Peak to PDN Packet Data Cellular
Average Ratio Network, Public PP, PTP Point-to-
PBCH Physical 50 Data Network 85 Point
Broadcast Channel PDSCH Physical PPP Point-to-Point
PC Power Control, Downlink Shared Protocol
Personal Channel PRACH Physical
Computer PDU Protocol Data RACH
PCC Primary 55 Unit 90 PRB Physical
Component Carrier, PEI Permanent resource block Primary CC Equipment PRG Physical
P-CSCF Proxy Identifiers resource block
CSCF PFD Packet Flow group
PCell Primary Cell 60 Description 95 ProSe Proximity
PCI Physical Cell P-GW PDN Gateway Services, ID, Physical Cell PHICH Physical Proximity- Identity hybrid-ARQ indicator Based Service
PCEF Policy and channel PRS Positioning
Charging 65 PHY Physical layer 100 Reference Signal
Enforcement PEMN Public Eand PRR Packet
Function Mobile Network Reception Radio
PCF Policy Control PIN Personal PS Packet Services Function Identification Number PSBCH Physical
PCRF Policy Control 70 PM Performance 105 Sidelink Broadcast Channel QFI QoS Flow ID, REG Resource
PSDCH Physical QoS Flow Element Group
Sidelink Downlink Identifier Rel Release
Channel QoS Quality of REQ REQuest
PSCCH Physical 40 Service 75 RF Radio
Sidelink Control QPSK Quadrature Frequency
Channel (Quaternary) Phase RI Rank Indicator
PSSCH Physical Shift Keying RIV Resource
Sidelink Shared QZSS Quasi-Zenith indicator value
Channel 45 Satellite System 80 RL Radio Link
PSFCH physical RA-RNTI Random RLC Radio Link sidelink feedback Access RNTI Control, Radio channel RAB Radio Access Link Control
PSCell Primary SCell Bearer, Random layer
PSS Primary 50 Access Burst 85 RLC AM RLC
Synchronization RACH Random Access Acknowledged Mode
Signal Channel RLC UM RLC
PSTN Public Switched RADIUS Remote Unacknowledged
Telephone Network Authentication Dial Mode
PT-RS Phase-tracking 55 In User Service 90 RLF Radio Link reference signal RAN Radio Access Failure
PTT Push-to-Talk Network RLM Radio Link
PUCCH Physical RAND RANDom Monitoring
Uplink Control number (used for RLM-RS
Channel 60 authentication) 95 Reference
PUSCH Physical RAR Random Access Signal for RLM
Uplink Shared Response RM Registration
Channel RAT Radio Access Management
QAM Quadrature Technology RMC Reference
Amplitude 65 RAU Routing Area 100 Measurement Channel
Modulation Update RMSI Remaining
QCI QoS class of RB Resource block, MSI, Remaining identifier Radio Bearer Minimum
QCL Quasi coRBG Resource block System location 70 group 105 Information RN Relay Node Time SCell Secondary Cell
RNC Radio Network Rx Reception, SCEF Service
Controller Receiving, Receiver Capability Exposure
RNL Radio Network S1AP SI Application Function
Layer 40 Protocol 75 SC-FDMA Single
RNTI Radio Network SI -MME SI for Carrier Frequency
Temporary the control plane Division
Identifier Sl-U SI for the user Multiple Access
ROHC RObust Header plane SCG Secondary Cell
Compression 45 S-CSCF serving 80 Group
RRC Radio Resource CSCF SCM Security
Control, Radio S-GW Serving Context
Resource Control Gateway Management layer S-RNTI SRNC SCS Subcarrier
RRM Radio Resource 50 Radio Network 85 Spacing
Management Temporary SCTP Stream Control
RS Reference Identity Transmission
Signal S-TMSI SAE Protocol
RSRP Reference Temporary Mobile SDAP Service Data
Signal Received 55 Station 90 Adaptation
Power Identifier Protocol,
RSRQ Reference SA Standalone Service Data
Signal Received operation mode Adaptation
Quality SAE System Protocol layer
RSSI Received Signal 60 Architecture 95 SDE Supplementary
Strength Evolution Downlink
Indicator SAP Service Access SDNF Structured Data
RSU Road Side Unit Point Storage Network
RSTD Reference SAPD Service Access Function
Signal Time 65 Point Descriptor 100 SDP Session difference SAPI Service Access Description Protocol
RTP Real Time Point Identifier SDSF Structured Data
Protocol SCC Secondary Storage Function
RTS Ready-To-Send Component Carrier, SDT Small Data
RTT Round Trip 70 Secondary CC 105 Transmission SDU Service Data Agreement Identifier
Unit SM Session SS/PBCH Block
SEAF Security Management SSBRI SS/PBCH Anchor Function SMF Session Block Resource
SeNB secondary eNB 40 Management Function 75 Indicator, SEPP Security Edge SMS Short Message Synchronization Protection Proxy Service Signal Block SFI Slot format SMSF SMS Function Resource indication SMTC SSB-based Indicator
SFTD Space- 45 Measurement Timing 80 SSC Session and
Frequency Time Configuration Service
Diversity, SFN SN Secondary Continuity and frame timing Node, Sequence SS-RSRP difference Number Synchronization
SFN System Frame 50 SoC System on Chip 85 Signal based
Number SON Self-Organizing Reference
SgNB Secondary gNB Network Signal Received
SGSN Serving GPRS SpCell Special Cell Power
Support Node SP-CSI-RNTISemi- SS-RSRQ
S-GW Serving 55 Persistent CSI RNTI 90 Synchronization
Gateway SPS Semi-Persistent Signal based
SI System Scheduling Reference
Information SQN Sequence Signal Received
SI-RNTI System number Quality
Information RNTI 60 SR Scheduling 95 SS-SINR
SIB System Request Synchronization
Information Block SRB Signalling Signal based Signal
SIM Subscriber Radio Bearer to Noise and
Identity Module SRS Sounding Interference Ratio
SIP Session 65 Reference Signal 100 SSS Secondary
Initiated Protocol SS Synchronization Synchronization
SiP System in Signal Signal
Package SSB Synchronization SSSG Search Space SL Sidelink Signal Block Set Group
SLA Service Level 70 SSID Sendee Set 105 SSSIF Search Space Set Indicator TE Terminal Radio Network
SST Slice/Service Equipment Temporary
Types TEID Tunnel End Identity
SU-MIMO Single Point Identifier UART Universal
User MIMO 40 TFT Traffic Flow 75 Asynchronous
SUL Supplementary Template Receiver and
Uplink TMSI Temporary Transmitter
TA Timing Mobile UCI Uplink Control
Advance, Tracking Subscriber Information
Area 45 Identity 80 UE User Equipment
TAC Tracking Area TNL Transport UDM Unified Data
Code Network Layer Management
TAG Timing TPC Transmit Power UDP User Datagram
Advance Group Control Protocol
TAI 50 TPMI Transmitted 85 UDSF Unstructured
Tracking Area Precoding Matrix Data Storage Network
Identity Indicator Function
TAU Tracking Area TR Technical UICC Universal
Update Report Integrated Circuit
TB Transport Block 55 TRP, TRxP 90 Card
TBS Transport Block Transmission UL Uplink
Size Reception Point UM
TBD To Be Defined TRS Tracking Unacknowledge
TCI Transmission Reference Signal d Mode
Configuration 60 TRx Transceiver 95 UML Unified
Indicator TS Technical Modelling Language
TCP Transmission Specifications, UMTS Universal
Communication Technical Mobile
Protocol Standard Telecommunica
TDD Time Division 65 TTI Transmission 100 tions System
Duplex Time Interval UP User Plane
TDM Time Division Tx Transmission, UPF User Plane
Multiplexing Transmitting, Function
TDMATime Division Transmitter URI Uniform
Multiple Access 70 U-RNTI UTRAN 105 Resource Identifier URL Uniform Network X2-U X2-User plane
Resource Locator VM Virtual XML extensible
URLLC UltraMachine Markup
Reliable and Low VNF Virtualized Language
Latency 40 Network Function 75 XRES EXpected user
USB Universal Serial VNFFG VNF RESponse
Bus Forwarding Graph XOR exclusive OR
USIM Universal VNFFGD VNF ZC Zadoff-Chu
Subscriber Identity Forwarding Graph ZP Zero Power
Module 45 Descriptor 80
USS UE- specific VNFMVNF Manager search space VoIP Voice-over- IP,
UTRA UMTS Voice-over- Internet
Terrestrial Radio Protocol
Access 50 VPEMN Visited
UTRAN Public Eand Mobile
Universal Network
Terrestrial Radio VPN Virtual Private
Access Network
Network 55 VRB Virtual
UwPTS Uplink Resource Block
Pilot Time Slot WiMAX
V2I Vehicle-to- Worldwide
Infrastruction Interoperability
V2P Vehicle-to- 60 for Microwave
Pedestrian Access
V2V Vehicle-to- WEANWireless Focal
Vehicle Area Network
V2X Vehicle-to- WMAN Wireless everything 65 Metropolitan Area
VIM Virtualized Network
Infrastructure Manager WPANWireless
VL Virtual Link, Personal Area Network
VLAN Virtual LAN, X2-C X2-Control Virtual Local Area 70 plane Terminology
For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.
The term “application” may refer to a complete and deployable package, environment to achieve a certain function in an operational environment. The term “AFML application” or the like may be an application that contains some AI/ML models and application-level descriptions.
The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.
The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”
The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.
The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.
The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.
The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.
The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.
The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.
The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.
The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.
The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.
The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.
The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .
The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.
The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.
The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.
The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.
The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.
The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.
The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.
The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), descision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K-means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML-host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

Claims

1. A user equipment (UE) comprising: memory to store an uplink positioning reference signal (UL-PRS) resource based on a fifth generation (5G) new radio (NR) Sounding Reference Signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; and one or more processors configured to: generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation.
2. The UE of claim 1, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
3. The UE of claim 1, wherein the one or more processors are further configured to: identify a frequency domain comb size from the set { 1, 2, 3, 4, 8}; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OLDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OLDM symbol.
4. The UE of claim 3, wherein the plurality of UL-PRS symbols are mapped to a subset of the OLDM symbols of the slot.
5. The UE of claim 4, wherein OLDM symbols that are not in the subset of OLDM symbols are inconsecutive.
6. The UE of claim 4, wherein the one or more processors are further configured to map UL-PRS symbols of a second UL-PRS resource of a second UL-PRS resource set to a second subset of OLDM symbols of the slot.
7. The UE of any of claims 1-6, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
8. The UE of claim 7, wherein resource elements (REs) of consecutive UL-PRS symbols of the plurality of UL-PRS symbols are the same as one another.
9. The UE of any of claims 1-6, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
10. The UE of any of claims 1-6, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
11. The UE of claim 10, wherein the UL-PRS periodicity is based on half of a length of a slot, the length of one slot, or an integer multiplication of the length of one slot.
12. The UE of any of claims 1-6, wherein the UL-PRS resource is based on an indication of a UL-PRS configuration received via radio resource control (RRC) signaling, a medium access control (MAC) control element (CE), or downlink control information (DCI).
13. The UE of any of claims 1-6, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL- PRS resource of the UL-PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
14. One or more non-transitory computer-readable media (NTCRM) comprising instructions that, upon execution of the instructions by one or more processors of a user equipment (UE), are to cause the UE to: identify an uplink positioning reference signal (UL-PRS) resource based on a fifth generation (5G) new radio (NR) sounding reference signal (SRS), wherein the UL-PRS resource is related to sensing to be performed during a sensing operation, wherein a UL-PRS resource includes a plurality of UL-PRS symbols; generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during performance of the sensing operation.
15. The one or more NTCRM of claim 14, wherein the plurality of UL-PRS symbols includes three UL-PRS symbols.
16. The one or more NTCRM of claim 14, wherein the instructions are further to cause the UE to: identify a frequency domain comb size from the set { 1, 2, 3, 4, 8}; map, based on the identified frequency domain comb size, a first UL-PRS symbol of the plurality of UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplexed (OFDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the plurality of UL-PRS symbols to a second subcarrier of the OFDM symbol.
17. The one or more NTCRM of any of claims 14-16, wherein a pattern of a UL-PRS resource for the cellular transmission is based on a M-level comb over N UL-PRS symbols, wherein M is greater than N.
18. The one or more NTCRM of any of claims 14-16, wherein the cellular transmission is a multi-port UL-PRS resource transmission.
19. The one or more NTCRM of any of claims 14-16, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.
20. The one or more NTCRM of any of claims 14-16, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set that includes a plurality of UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control (PC) parameter that is different than a PC parameter of a second UL-PRS resource of the UL-PRS resource set.
PCT/US2023/082297 2022-12-08 2023-12-04 Uplink positioning reference signal (ul-prs) adaptations and extensions for sensing in joint communication and sensing systems WO2024123677A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263431169P 2022-12-08 2022-12-08
US63/431,169 2022-12-08

Publications (1)

Publication Number Publication Date
WO2024123677A1 true WO2024123677A1 (en) 2024-06-13

Family

ID=91380066

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/082297 WO2024123677A1 (en) 2022-12-08 2023-12-04 Uplink positioning reference signal (ul-prs) adaptations and extensions for sensing in joint communication and sensing systems

Country Status (1)

Country Link
WO (1) WO2024123677A1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090067990A (en) * 2007-12-21 2009-06-25 재단법인대구경북과학기술원 Ultra wide band vehicle radar system driving method and ultra wide band vehicle radar system
US20110124347A1 (en) * 2009-09-15 2011-05-26 Byron Hua Chen Method And Apparatus for UE Positioning in LTE Networks

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090067990A (en) * 2007-12-21 2009-06-25 재단법인대구경북과학기술원 Ultra wide band vehicle radar system driving method and ultra wide band vehicle radar system
US20110124347A1 (en) * 2009-09-15 2011-05-26 Byron Hua Chen Method And Apparatus for UE Positioning in LTE Networks

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NTT DOCOMO, INC.: "Discussion on improved accuracy based on NR carrier phase measurement", 3GPP DRAFT; R1-2204387, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 28 April 2022 (2022-04-28), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052153515 *
OPPO: "Discussion on UL Reference Signals for NR Positioning", 3GPP DRAFT; R1-1910122, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Chongqing, China; 20191014 - 20191020, 4 October 2019 (2019-10-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 6, XP051788929 *
YAN CHENG, HUAWEI, HISILICON: "SRS enhancement for TDD CJT and UL 8Tx operation in Rel-18", 3GPP DRAFT; R1-2210915; TYPE DISCUSSION; NR_MIMO_EVO_DL_UL-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 1, no. Toulouse, FR; 20221114 - 20221118, 7 November 2022 (2022-11-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052221479 *

Similar Documents

Publication Publication Date Title
US20240154883A1 (en) Sixth generation (6g) system architecture and functions
CN117581501A (en) Enhanced Sounding Reference Signal (SRS) Operation for Fifth Generation (5G) Systems
WO2023014910A1 (en) Collision handling for sounding reference signal (srs) transmission
JP2024512511A (en) Techniques for Channel State Information Reference Signal (CSI-RS) Transmission
WO2022197678A1 (en) Sounding reference signal configuration for antenna switching and carrier switching
US20230156509A1 (en) Listen-before-talk (lbt) in radio resource management (rrm) for new radio systems
WO2022031692A1 (en) Discovery reference signal beamforming randomization
US20240014976A1 (en) Multiplexing and joint design for communication and sensing
US20240235775A1 (en) Configuration and collision handling for simultaneous uplink transmission using multiple antenna panels
US20240204931A1 (en) Multi-cell communication with multi-pdsch/pusch scheduling via a single dci
WO2023173075A9 (en) Training updates for network data analytics functions (nwdafs)
WO2023141298A1 (en) Valid pdschs or puschs with multiple pdsch or pusch scheduling
WO2023069653A1 (en) User equipment (ue) switching between networks using measurement gaps
WO2023055900A1 (en) Rate-matching for transport block processing over multiple slots for physical uplink shared channel
US20240235797A1 (en) Transmission configuration indicator (tci) chain enhancements for new radio systems
EP4246853A1 (en) Configuration and identification for advanced duplex system
US20240236957A1 (en) Techniques to avoid inter-symbol interference during tci state switching in high-speed train deployments
US20240178945A1 (en) Time domain bundling of hybrid automatic repeat request-acknowledgement (harq-ack) feedback
US20240251274A1 (en) Pre-configured measurement gap status indication to a user equipment (ue)
US20240146454A1 (en) Enhanced mapping for control channel transmission based on polar code
WO2024123677A1 (en) Uplink positioning reference signal (ul-prs) adaptations and extensions for sensing in joint communication and sensing systems
WO2024211513A1 (en) Scheduling restriction for multi-rx chain simultaneous reception
WO2023205691A1 (en) Pre-configured measurement gap (mg) testing procedure
WO2024172913A1 (en) Sidelink positioning measurements, reports, and assistance information
WO2024173075A1 (en) Dual transmission configuration indicator (tci) activation in multi-receiver (rx) chain

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23901394

Country of ref document: EP

Kind code of ref document: A1