Uplink positioning reference signal or UL-PRS adaptations and extensions for acquisition in shared communication and acquisition systems

Abstract

Various embodiments herein relate to the identification, by a user device (UE), of an uplink positioning reference signal (UL-PRS) resource based on a 5G-NR bearing reference signal (SRS), wherein the UL-PRS resource is associated with a capture to be performed during a capture operation, and wherein a UL-PRS resource comprises multiple UL-PRS symbols. The UE can further generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource. The UE can further transmit the cellular transmission during the execution of the capture operation. Other embodiments may be described and / or claimed.

Description

CROSS-REFERENCE TO RELATED REGISTRATION

[0001] The present application claims priority over the preliminary US patent application No. 63 / 431,169, which was filed on December 8, 2022. BACKGROUND

[0002] Various designs can generally affect the field of wireless communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The embodiments are easily understood through the following detailed description in conjunction with the accompanying drawings. To facilitate this description, identical reference numerals denote identical structural elements. The embodiments are illustrated in the figures of the accompanying drawings by way of example and without limitation. Fig. Figure 1 illustrates an exemplary data capture block structure according to different embodiments. Fig.Figure 2 illustrates an example of frequency multiplexing of one or more direction-finding reference signals from multiple users using Kamm-2 according to various embodiments. Fig. Figure 3 illustrates examples of uplink positioning reference signal (UL-PRS) resource element (RE) patterns according to different embodiments. Fig. Figure 4 illustrates examples of SRS configurations according to different embodiments. Fig. Figure 5 illustrates exemplary RE offsets for UL-PRS according to different embodiments. Fig. Figure 6 illustrates an exemplary setting of a path loss estimation for UL-PRS according to different embodiments. Fig. Figure 7 illustrates an example of transmit / receive point (TRP) muting for comb-2 according to different embodiments. Fig.Figure 8 illustrates an example of a spatial relationship and a path loss reference for UL-PRS according to different embodiments. Fig. Figure 9 schematically shows a wireless network in accordance with various embodiments. Fig. Figure 10 schematically shows the components of a wireless network in accordance with different embodiments. Fig. Figure 11 is a block diagram showing components according to some embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-volatile machine-readable storage medium) and performing one or more of the methods discussed herein. Fig. Figure 12 illustrates a network according to different embodiments. Fig. Figure 13 shows an exemplary procedure for carrying out the various embodiments discussed here. Fig. Figure 14 shows an alternative exemplary method for carrying out the various embodiments discussed here. Fig. Figure 15 shows an alternative exemplary method for carrying out the various embodiments discussed here. DETAILED DESCRIPTION

[0004] 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. For the purpose of explanation, not limitation, the following description sets out specific details, such as particular structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of the various aspects of different embodiments. However, it will be obvious to those skilled in the art who benefit from this disclosure that the various aspects of the different embodiments can be implemented in other examples that differ from these specific details.In certain cases, descriptions of well-known devices, circuits, and methods are omitted to avoid obscuring the description of the various embodiments with unnecessary details. For the purposes of this document, the expressions "A or B" and "A / B" mean (A), (B), or (A and B).

[0005] A design aspect of cellular-based joint communication and sensing (JCAS) is the activation of sensing functionality within the orthogonal frequency-division multiplexing (OFDM) framework. This functionality may involve 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 also requires efficient resource allocation that considers various design factors encompassing both communication and sensing capabilities. The current disclosure discloses aspects relating to the extension and adaptation of a new-radio uplink (UL) positioning reference signal (PRS) (which itself is based on a direction-finding reference signal - SRS) for the purpose of sensing.Such extensions aim to activate the acquisition based on the transmitted radio signal from user devices (UE) (which may correspond to different acquisition architectures, mono- / bi- / multistatic). Potential data acquisition frameworks / architectures in cellular systems

[0006] gNodeB- or gNB-based and UE-based data collection scenarios can exist within a cellular framework to enable different data collection applications and use cases. For example, the following cases may exist: • Case 1: The gNB transmits the acquisition radio signal and receives / measures / processes its reflections from objects / the environment in time, frequency, and spatial / angular domains. If the same gNB also receives / measures / processes the reflected signal, the scenario can be described as a gNB-based monostatic acquisition mode. If other gNBs are involved in receiving, measuring, and processing, it can be described as a gNB-based bistastatic (multistatic) acquisition mode through cooperative network nodes. • Case 2: gNB sends the detection radio signal and the UE receives / measures / processes its reflections (bistactic detection mode). • Case 3: the UE sends a detection radio signal and the same or another UE(s) or the gNB receives / measures its reflections (according to UE-based monostatic and UE-based bi- / multistatic or gNB-based bi- / multistatic detection modes).

[0007] Note: In cases 1 and 2, the acquisition signal can be based on the downlink (DL) positioning reference signal (PRS) (with some extensions and adjustments, as disclosed, for example, in IDF AE8858) or a newly designed acquisition signal.

[0008] Note: It is also possible to combine cases 1 and / or 2, including the case where the UE receives / measures the gNB radio signal for positioning purposes, e.g., if the gNB signal is based on a DL-PRS signal (which will be thoroughly investigated later).

[0009] Note: As can be seen from the above cases, acquisition may require transmission / reception from multiple nodes to perform coordinated environmental or neighborhood sensing by multiple gNBs and / or UEs.

[0010] Note: Some solutions may focus on reusing / extending the uplink (UL) PRS signal design to enable Case 3 above. It should be noted that UL-PRS may be referred to as a "Sensing Reference Signal (SRS) for Position Determination" in the specifications of the Third Generation Partnership Project (3GPP) or elsewhere.

[0011] To enable acquisition functionality that addresses different unified communications systems (UCS) with corresponding requirements for a key performance indicator (KPI) for acquisition, the wireless signal used for acquisition should meet certain requirements regarding time-domain and frequency-domain attributes. These attributes determine the underlying numerologies, frame structures, and physical resource allocations and patterns. IDF AE8858 fully examines these aspects and derives in detail the necessary attributes and characteristics of the air interface signal used for acquisition to meet range, velocity, and angle requirements. These characteristics can be applied to the signal transmitted by gNB and / or UE.In IDF AE8858, the corresponding necessary adjustments to DL-PRS can also be disclosed to meet the desired attributes for capture.

[0012] Embodiments herein may relate to scenarios that rely on the transmission of the UE's radio signal for the purpose of detection. Based on the derived structure and the detection signal pattern / attributes in IDF AE8858, this disclosure first establishes the reusability of the UL direction-finding reference signal structure for detection, followed by disclosed adaptations and extensions to UL-PRS (based on SRS).

[0013] Specifically, this paper first examines SRS signal attributes according to 3GPP Release 15 (Rel-15), followed by UL-PRS design based on SRS according to Release 16 (Rel-16). Then, a feasibility analysis of UL-PRS-based acquisition (similar to what was done for DL-PRS in IDF AE8858) is performed, followed by the derivation of the necessary extensions.

[0014] Embodiments described herein may relate to air interface signal design and attributes, and not to architectural, hardware, and implementation aspects. For example, aspects such as enabling full-duplex for monostatic UE acquisition or synchronization for bi- / multistatic acquisition (e.g., in gNB) based on the UE signal are not the focus of this disclosure. 1. Exemplary statistical properties / structure of the acquisition signal in time and frequency domains (as can be described in IDF AE8858)

[0015] The parameterization, frame structure, and time / frequency domain or TD / FD resource allocation / dimensioning of the signal used for acquisition (either a dedicated acquisition signal or a DL communication signal) are driven by the distance and velocity resolution requirements and their respective unique maximum detectable values, as well as the requirements for multiplexing communication and acquisition. More specifically, the dimensioning of the 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 the acquisition signal are primarily driven by these requirements. Furthermore, all OFDM system parameters (e.g., BW, SCS, number of subcarriers, CP duration, symbol duration, number of OFDM symbols) can be derived from these requirements.For example, while the time-domain repetition of the acquisition signal and the SCS define the maximum detectable velocity, the total time span duration (i.e., the integration time – acquisition block) defines the achievable velocity resolution. Conversely, the SCS and the CP duration (i.e., numerology) define the maximum detectable distance, while the bandwidth (total frequency span) defines the distance resolution. A. Time domain recording resources (attributes / patterns) and system parameters

[0016] To ensure adequate acquisition performance, a certain time span and time interval for the signal used for acquisition may be required. Possible time domain resource allocation properties for signal acquisition to enable Doppler processing exist: 1. Integration time span over which the acquisition signal extends when the Doppler profile is calculated: Capture block (or capture frame) = c0(2fcΔν), which is inversely proportional to velocity resolution and carrier frequency. In acquisition frame design, the acquisition block duration is an integer (k) multiple of SRI durations, i.e., k × T SRI . k is the size of the FFT operation performed during Doppler processing. 2. The maximum time interval between acquisition symbols within a span of the acquisition block to allow a Doppler estimation per beam direction, defined by the symbol repetition interval (SRI): TSRI≤c0(4fcνmax), which is inversely proportional to the maximum detectable velocity and carrier frequency. As mentioned previously, this can be viewed as a Nyquist sampling rate for detecting the maximum velocity. Besides this factor, there are other limits to the maximum detectable velocity. The maximum detectable velocity must satisfy the SRI Nyquist rate, the ICI condition (the maximum Doppler frequency should be ~10% of SCS), and distance migration. νmax≤Min(c04fcTSRI,c0×SCS20×fc,Δdk×TSRI).

[0017] These two properties can be considered basic requirements for a detection signal with respect to Doppler processing in order to perform a single task of detection (without additional processing enhancements) ( Fig.1) Any time repetition and / or block duration beyond the minimum required values ​​results in additional processing gains and an improvement in SNR. It is also noted that these attributes determine the basic allocation scheme in the context of single-beam acquisition. Furthermore, these concepts can then be extended to the case of multi-beam operation.

[0018] There is also another time-related system parameter that is associated with the detection distance requirements. An ideal detection requirement for a detection distance without cross-symbol interference (ISI) can be expressed as the required CP duration (T). CP) should be translated. For ideal distance detection performance, the CP duration should be on the order of 2x(maximum distance) / c0. The NR-CP in frequency range 1 (FR1) is long enough to cover distances beyond 180-350 m. Therefore, FR1 supports longer-range UCs with the same CP and OFDM symbol durations for communication and detection symbols. Furthermore, in FR1, a useful symbol duration is large compared to the CP values ​​desired for detection distance determination (low CP loss). It is noted that, generally, only CP (and therefore total symbol duration) may need to differ between the detection numerology and the communication numerology; otherwise, SCS, etc., are all aligned between the communication and detection systems.For frequency range 2 (FR2_), supporting a unified symbol / CP duration between communication and acquisition for higher SCSs may not be possible depending on the maximum UC distance requirement. Specifically, FR2 may support shorter-range UCs with the same CP and OFDM symbol duration for both acquisition and communication, and longer-range UCs with different CP and OFDM symbol durations for acquisition and communication. B. Frequency domain acquisition resources (attributes / patterns) and system parameters

[0019] In this subsection, we examine the translation of acquisition requirements into signal properties in the frequency domain. Specifically, the frequency domain resource allocation for an acquisition signal must satisfy the following condition to enable a single acquisition task: 1. The minimum required signal bandwidth is inversely proportional to the supported distance resolution: c0(2Δd). Therefore, Δd in the submeter range is achievable with a bandwidth > 150 MHz. Accordingly, FR1 may impose a potential trade-off in distance resolution, which can be remedied by enabling the use of carrier aggregation to provide an extended bandwidth for acquisition. 2. Regarding the use of subcarriers within the allocated bandwidth (BW), it should be noted that an FD comb structure reduces the maximum unique distance (since it increases the effective SCS). On the other hand, as discussed previously, distance detection performance is also limited by a CP constraint, and the CP-based distance is usually much smaller than the maximum unique distance. In a practical system, the largest integer value mKamm , for the n×c0Tcp2 smaller than 1 / m Kamm x is (the maximum unique range, i.e. n×c0Tcp2≤c0mKamm(2×SCS)), It can be derived, e.g., for some systems even 5 times the CP distance is approximately (1 / 3) x (maximum unique distance). Then the comb size can be expressed as a number less than or equal to m. Kamm be selected.

[0020] There is also another frequency-related system parameter that is connected to the acquisition speed requirements and the SCS. Specifically, the SCS has various implications and trade-offs regarding acquisition. On the one hand, the SCS is inversely proportional to the maximum unique detectable distance. This means that a larger SCS can enable the detection of higher Doppler shifts and faster-moving targets without intercarrier orthogonality (to ICI attenuation). For acceptable ICI, the SCS should be greater than ~10×Doppler frequency~20×fc×νmaxc0 On the other hand, when the SCS is increased to support certain distance requirements, CP loss increases due to inefficiency (caused by the ratio of CP time to usable OFDM symbol time). Typically, a larger SCS is available for higher carrier frequencies, which support shorter OFDM symbol and CP durations, resulting in reduced detection distances.

[0021] As discussed below, for different SCS values ​​the choice of SRI and acquisition frame duration can be determined separately, and the reachability of certain distances can also be assessed depending on CP, etc. 2. Examples of a data capture framework structure design

[0022] To create the capture frame structure design from the time and frequency domain attributes discussed in the previous section, the following high-level procedural steps were followed: • An estimate of various system parameters is derived from the KPIs. • Then, the values ​​for system parameters are fine-tuned based on the derived estimate, taking into account practical cellular frame structure and numerology parameters. • The resulting achievable KPIs and the achievable SNR (from the connection budget) can then be calculated.

[0023] This section provides examples of how a capture frame structure can fit into the cellular system frame and numerology. Accordingly, the following exemplary SRI values ​​and Doppler FFT sizes (and thus the capture frame structure and duration) were also discussed in IDF AE8858 to support the highest possible velocity estimation capabilities under varying constraints and to meet reasonably fine velocity resolutions while keeping the design as simple as possible (without compromising supported capture performance).

[0024] For example, an SRI is defined such that it operates at either half a slot rate, a full slot rate, or double a slot rate for different maximum desired speeds (depending on the use case). The resulting exact supported maximum speed and speed resolution can then also be determined based on the carrier frequency. • For all carrier frequencies in FR1, the following SRI durations (in number of OFDM symbols (OS)) and Doppler FFT sizes (k) are to be supported: • For SCS=15 kHz, {T SRI , k} = {7OS, 32}, {7OS, 64}; • For SCS=30 kHz, {T SRI , k} = {14OS, 32}, {14OS, 64}, {7OS, 64}, {7OS, 128} • For SCS=60 kHz, {T SRI , k} = {28OS, 32}, {28OS, 64}, {14OS, 64}, {14OS, 128} These result in a capture block duration = k × T SRI = 16.32 ms • For FR2, the following SRI durations and Doppler FFT sizes (k) should be supported. • For SCS=60 kHz, for all carrier frequencies in FR2, {T SRI , k} = {7OS, 64}, {7OS, 128}, which leads to a capture block duration = k × T SRI 8.16 ms leads • For frequencies <30 GHz in FR2, {T SRI , k} = {14OS, 32}, {14OS, 64}, {14OS, 128} is also supported, resulting in a capture block duration of 8, 16, 32 ms. • For frequencies > 50GHz in FR2, {T SRI , k} = {7, 256} is supported, resulting in a capture block duration of 32 ms. • For SCS=120 kHz, • For all carrier frequencies in FR2, {T SRI , k} = {14OS, 64}, {14OS, 128} is supported, resulting in a capture block duration of 8.16 ms, and {T SRI , k} = {7OS, 64}, {7OS, 128} is supported, resulting in a capture block duration of 4.8 ms. • For carrier frequencies > 50GHz in FR2, k=256 is also supported, resulting in a capture block duration of 32.16 ms for T. SRI =14 or 7OS leads to.

[0025] It should be noted that the number of OFDM symbols in the SRI should provide a good balance between the maximum detectable velocity, the acquisition repetition gain (the total Doppler processing gain for a given acquisition block is 10 log10 (Doppler FFT size) + 10 log10 (number of OFDM symbols within the SRI)), the flexibility / ability to support multiplexing between acquisition and communication, the field of view (FoV) coverage, depending on the required number of beams, and the beamwidth. Furthermore, as can be seen from the values ​​discussed above, Doppler FFT sizes in FR1 are generally smaller, which implies a lower number of radio frames for acquisition and less restriction and unavailability for communication. It should also be noted that although larger Doppler FFT sizes can be supported (e.g.,(To provide finer Doppler resolution and / or higher processing gain), longer acquisition frame durations resulting from large Doppler FFT sizes can lead to a distance migration problem in the distance Doppler image. This would require proper handling to avoid performance degradation.

[0026] Note: Capturing UCs and services in a JCAS system may also support values ​​for SRI duration and / or Doppler FFT size other than those discussed previously. The discussed values ​​provide examples of how a capture frame structure can fit into the cellular system frame and numerology.

[0027] In at least some of the above cases, the CP durations are the same as in NR and are also adopted for OFDM symbols used for acquisition. In the case of using different CPs (and therefore symbol durations) between communication and acquisition (which may be primarily motivated when there is a need to support longer acquisition distances (>100 m) with higher SCSs in FR2), proper alignment between acquisition block durations and communication slot limits is required (the details are disclosed in IDF AE9196). Given that the normal CP of NR supports ISI-free distance detection up to ~90 m for 120 kHz SCS, and considering that for mmWave frequencies the power range (link budget) may not exceed 100 m (even 100 m may be too far for some practical applications, e.g.,(when looking around the block from the roof), the support of longer-distance UCs with FR2 may not be fully justified (especially when the longer-distance UCs can be supported with FR1 with fewer complications). 3. UL-PRS Signal Design and Attributes

[0028] In the preceding sections (and in more detail in IDF AE8858), the acquisition requirements, acquisition signal numerology, time and frequency attributes, and acquisition frame structure aspects were discussed and formulated. Considering such characteristics, the NR-DL-PRS signal in IDF AE8858 was analyzed, and necessary extensions to enable acquisition were disclosed. The next subsection reviews the UL-PRS signal design, including frequency and time resource allocation and patterns / regularities, followed by the identification of similarities and gaps with respect to what is desired for acquisition in the subsequent subsection.

[0029] NR UL-PRS was defined in NR Rel-16 based on Rel-15 SRS for the purpose of UE localization / positioning. Accordingly, examples of the Rel-15-SRS design are provided first, followed by Rel-16 extensions for UL positioning. A. Examples of the direction finding reference signal or SRS design according to Rel-15

[0030] To enable UL channel direction finding, a device can be configured to transmit SRS. As an UL-only signal, SRS is transmitted through the UE, originally to help gNB obtain channel status information (CSI) for each user. CSI describes how the NR signal propagates from UE to gNB and represents the combined effect of dispersion, attenuation, and power decay with distance. The system uses SRS for resource planning, link matching, massive MIMO, and beam management. SRS is specifically configured for UE. Time / frequency characteristics of SRS

[0031] In the time domain, the SRS resource according to Rel-15 {1, 2, 4} can span consecutive OFDM symbols (OSS) that are mapped only within the last six symbols of the slot. Multiple SRS symbols allow for coverage extension and increased bearing capacity. Ideally, the entire 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 spectral power 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 (coupled) in each repetition, i.e., the same subcarriers for R symbols. With repetition enabled, Rel-15 SRS is transmitted in the same portion of the band for 2 or 4 OFDM symbols in the SRS resource.For example, a 2- or 4-OS SRS duration is a 2- or 4-fold repetition of the 1-OS SRS (depending on the configuration of groupHopping and sequenceHopping via the groupOrSequenceHopping parameter, the same sequence within the SRS resource can be repeated, or the sequence group and / or the sequence-within-a-group can jump via symbols). In addition to coverage extension, SRS repetition can also be used when the SRS is beam-shaped, as in FR2, to allow the gNB to perform receive beam tuning: since the UE repeats the SRS transmission multiple times using the same transmit beam, the gNB can evaluate the performance of several gNB receive beam candidates. The performance of these different gNB receive beams can be directly compared because the UE is known to keep its transmit beam constant for each transmission.

[0032] Regarding frequency domain aspects, a nested structure is used, and the design of the SRS and its frequency hopping mechanism is the same as that used in LTE. SRS sequences

[0033] Sequences applied to the set of SRS-REs are partly based on Zadoff-Chu or ZC sequences. Although prime-length ZC sequences are preferred to maximize the number of available sequences, SRS sequences do not have prime lengths. SRS sequences are extended ZC sequences based on the ZC sequence with the longest prime length, with a length M less than or equal to the desired SRS sequence length. The sequence is then cyclically extended in the frequency domain (FD) until the desired SRS sequence length is reached. Because the extension occurs in the FD, the extended sequence still has a constant spectrum and thus "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 more, which correspond to an SRS spanning 6 or 12 resource blocks in the case of Kamm-2 and Kamm-4, respectively. Randomization between users

[0034] To randomize SRS interference between users transmitting SRS within the same bandwidth, in the same cell, and in different cells, time-dependent sequence randomization (sequence jump) can be configured for the SRS sequence. The sequence used for SRS depends pseudorandomly on both the slot index and the symbol index within a slot. Furthermore, the SRS sequence initialization used is configured by the RRC UE-specifically. UE multiplexing

[0035] The SRS is also designed with a comb-based pattern similar to the DL-PRS. SRS transmissions from different UEs can be subjected to frequency domain division multiplexing (FDM) within the same frequency range by assigning different combs corresponding to different frequency offsets ( Fig.2) Units can be multiplexed over the same transmission symbol by assigning different comb patterns. For example, comb 2 can subject two SRSs to FDM. In the case of comb 12, up to 12 SRSs can be subjected to FDM. On the other hand, multiple SRS ports (i.e., 1001 to 1003) are nested in the frequency domain within the same OFDM symbol. SRS Ports Multiplexing

[0036] An SRS resource can be configured for 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 entire configured SRS bandwidth of the resource; that is, all SRS ports are present in every OFDM symbol of the resource. An SRS antenna connection can thus be repeatedly transmitted through a UE in 2 or 4 symbols within a single slot, which can be used to extend SRS coverage. Different configuration alternatives for mapping 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 the comb structure can be used for FDM of multiple UEs as well as for FDM of multiple ports of a PRS resource.For example, a gNB can configure one 2-port UE over one comb-2 set of REs and another 1-port or 2-port UE over the other comb-2 set of REs, using the same OFDM symbol, with the multi-port transmission of each UE separated using cyclic shift (CS) across identical 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 the SRS port from another UE transmission by using a different CS and / or a different comb). For a 2-SRS port resource, both ports are mapped to the same comb and separated by CS. Each of the combs can be configured for this SRS resource (the other comb can be used by a different UE (e.g., 1-port or 2-port). If this is configured for a single UE, then this is the expectation for that UE). If a UE is capable of, for example,To transmit using 2 panels or 2 beams, the UE can be configured with a multiport SRS resource. However, between different UEs, it is not necessary for the gNB to configure each UE with a multiport resource. For a 4-port SRS resource, either all four ports are mapped to the same comb and separated by CS, or groups of two ports are mapped to one 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. In a case with four ports and four combs, if two combs are configured, the two combs cannot be adjacent, as this prevents multiplexing another SRS resource in the same OFDM symbol (if groups of 2 ports are used, this can limit the capacity for FDM with other UEs). SRS resource quantity and SRS resource

[0037] A UE can be configured (through the parameters of a higher-layer SRS-ResourceSet or SRS-PosResourceSet-r16) with more than one SRS resource set (each containing one or more SRS resources) used for different purposes ("uses"). These sets might be for, for example, DL and UL multi-antenna precoding or DL ​​and UL beam management. Specifically, each set is designated for a particular "use," such as "antenna switching," "beam management," etc., and an SRS resource transmitted in a given set cannot be used for a use other than the one for which it was configured. For example, an SRS transmission for "antenna switching" cannot be used simultaneously for "codebook"-based use, and vice versa. Because each configured SRS resource set can only have one "use," it may be necessary to configure multiple resource sets for the UE concurrently.SRS resource set applicability is configured by the higher-layer usage parameter in the SRS ResourceSet. Different usages may have certain restrictions regarding SRS resource or resource set configurations / numbers, port configurations, etc. For example, if the higher-layer usage parameter is set to "beamManagement," only one SRS resource in each of multiple SRS sets can be transmitted at any given time (which may imply TDM of beams, i.e., beam sweeping), but SRS resources in different SRS resource sets with the same time domain behavior in the same bandwidth portion can be transmitted concurrently. The specification does not limit the number of ports for the single SRS resource in each SRS set for beam management (unlike CSI-RS, which has a certain limitation of 1 / 2 ports for beam management).

[0038] On the other hand, in general, each SRS resource set can contain one or more configured SRS resources. Specifically, for each SRS resource set configured by the higher-layer parameter SRS-ResourceSet, a UE with K ≥ 1 SRS resource can be configured (by the higher-layer parameter SRS-Resource). The maximum value of K is specified 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 non-adjacent) or they can be distributed across different slots. There is no specified restriction on the distance of resources from the same set (it will be determined by the configuration). A slot can be used to transfer 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.

[0039] The SRS resources of a set can be time-domain multiplexed. For a 4-port SRS resource for antenna connections 1001 and 1003, frequency-domain multiplexing is also supported (one resource set can correspond to different comb offsets).

[0040] A UE can be configured with up to 16 SRS resource sets per bandwidth segment (limited to 4 sets in FR1), and each set can contain a maximum of 64 SRS resources. In FR1, the total number of SRS resources is limited to 10, as a larger number of resources is only needed 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), where the maximum value is UE capability; • can have multiple SRS resources in the same slot, where resources are temporally adjacent or non-adjacent; • can have SRS resources in different slots; • is configured with a single “use” (only one purpose at a time);

[0041] Since SRS is used for multiple functionalities, the UE can be configured with multiple SRS resource sets simultaneously. SRS types (TD structure of SRS)

[0042] A SRS can be configured for periodic, semi-persistent (SP), or aperiodic transmission. A periodic SRS transmits with a certain periodicity and a certain slot offset within that periodicity and is configured only by the RRC. An SP-SRS has a periodicity and slot offset in the same way as a periodic SRS and is also configured by the RRC. However, the actual UL-PRS transmission according to the periodicity and slot offset is enabled / disabled by MAC-CE signaling. SP SRS allows a periodic SRS transmission to be started / stopped using MAC signaling from the gNB to the UE, which is faster than RRC control, and provides a means to trigger periodic SRS transmissions only when needed to avoid interference and unnecessary transmissions from the UE. An aperiodic SRS is configured by the RRC but only transmits when explicitly triggered by DCI.Activation / deactivation and triggering for SP or aperiodic SRS is not performed for a specific SRS slot, but rather 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 contained within an SRS resource set are of the same type. The transmission of aperiodic SRS, or more precisely, the transmission of the set of configured SRS contained within an aperiodic SRS resource set, is triggered by DCI. All resources within the set also have the same periodicity. B. Examples of the design of the UL positioning reference signal (UL-PRS) according to Rel-16

[0043] The UL-based positioning reference signal is based on Rel-15-SRS transmitted by the devices, with enhancements for positioning purposes. In the 3GPP specification, UL-PRS can be referred to as "SRS for positioning". UL-PRS(SRS)-RESOURCE

[0044] In some aspects, UL-PRS can be considered the UL equivalent of DL-PRS. SRS for positioning in Rel-16 addresses two aspects specific to positioning. Since positioning involves measurements from multiple receiving BSs, the signal must first have sufficient range to reach not only the supplying BS to which the UE is connected, but also the neighboring BSs involved in the positioning process. Second, SRS is also designed to cover the full bandwidth, with REs distributed across the various symbols so that they cover all subcarriers. In other words, the UL-PRS signal can support a large delay spread range because it must be received by potentially distant neighboring BSs for position estimation.This is achieved by covering the entire configured bandwidth and transmitting the PRS over multiple symbols that can be aggregated to accumulate power and increase the signal-to-noise ratio (SNR). Specifically, configurable patterns cover every subcarrier within the configured bandwidth over the pattern duration, providing the maximum measurement range for time-of-arrival (ToA) measurement in scenarios with large delay spreads.

[0045] The UL-PRS sequence is based on Zadoff-Chu sequences as a base signal, which is also used for Rel-15-SRS to ensure low-PAPR transmission from the UE. The specific sequence used to generate an SRS symbol depends on configuration parameters. UL-PRS resources are arranged in a specific time / frequency pattern. To better support positioning, the SRS structure is extended in several ways: In the time domain, the sequence length is extended to ensure a sufficiently good signal-to-noise ratio for accurate measurements in gNB. Unlike Rel-15-SRS, a UL-PRS resource can span 1, 2, 4, 8, or 12 consecutive OFDM symbols (providing sufficient coverage to reach all TRPs involved in the positioning procedures) located anywhere within a (UL) slot. The starting point is also more flexible to accommodate the increased duration.Like DL-PRS, SRS positioning resources are transmitted over a single antenna port (i.e., like UL positioning, each UL-PRS resource is also limited to a single port). In the frequency domain, UL-PRS also features a comb N pattern (where N is the comb size). For Rel-15-SRS, N can take values ​​of 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.

[0046] Furthermore, frequency hopping for UL-PRS is not supported for SRS-based positioning (excluded for positioning by Rel-16) because a single UL-PRS transmission typically covers the entire configured bandwidth. A "UL-PRS resource" with 1, 2, 4, 8, or 12 consecutive OFDM symbols is transmitted in the active UL bandwidth portion of the UE. 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 is also supported (if the comb size is smaller than the number of symbols, repetition can occur within the resource). Similar to DL-PRS, the RE mapping is not arranged in a stair-step pattern ( Fig.3), with the advantage 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 alias correlation peaks is better suppressed. For example, the first two symbols of the comb-4 UL-PRS provide an effective comb-2 RE pattern (after de-staggering). For each pair of comb size and number of symbols, there is an RE pattern. The RE pattern of a 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 the first symbol.

[0047] In summary, a UL-PRS resource can span 1, 2, 4, 8, or 12 adjacent OFDM symbols in a slot (i.e., the 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 transferred 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 was not the case for Rel-15. Fig. 4) Rel-16 repetitions are highly specific to the patterns specified by RE offsets for pairs of UL-PRS comb size and number of symbols, as shown in Table 1. In particular, the RE pattern of a UL-PRS is configured with a comb offset for the first symbol in an SRS resource, and relative RE offsets (for other symbols) are defined relative to the comb offset of the first symbol in the SRS resource ( Fig. 5) Furthermore, the number of repetitions is not configured separately for SRS positioning; rather, it is realized through the configured number of SRS symbols and the comb offset sequence, as shown in Table 1. Table 1. RE offsets for pairs of UL-PRS comb size and number of symbols Number of symbols / comb size 1 2 4 8 12 2 {0} {0,1} {0, 1, 0, 1} n / a n / a 4 n / a {0,2} {0,2,1,3}, {0,2,1,3,0,2,1,3} {0,2,1,3, 0,2,1,3, 0,2,1,3} 8 n / a n / a {0,4,2,6} {0,4,2,6,1,5,3,7} {0,4,2, 6, 1, 5,3,7,0, 4,2, 6}

[0048] Furthermore, unlike the DL-PRS case, which supports two levels of repetition (within and across PRS resources), UL-PRS only supports one level of repetition (only within the resource, i.e., no repetition of SRS resources is supported). UL-PRS(SRS) resource set

[0049] Similar to Rel-15-SRS, a device can be configured with one or more UL-PRS resource sets (via higher-layer parameter SRS-ResourceSet or SRS-PosResourceSet) that can be used for different purposes. Each UL-PRS resource set can contain one or more UL-PRS resources. If the SRS is configured with the higher-layer parameter SRS-PosResourceSet-r16, a UE can be configured with SRS resources (higher-layer parameter SRSPosResource-r16), where the maximum value of K is 16.

[0050] As the parameter above also shows, the SRS is identified separately for positioning purposes; that is, it is a different configuration. This means that although positioning uses SRS, the purpose is differentiated within the configuration itself through signaling.

[0051] Finally, for the purpose of UL positioning, up to 16 SRS resource sets can be configured for one UE [TS 38.331]. UL-PRS types

[0052] Similar to Rel-15-SRS, a 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, UL-PRS supports periodicities of {5120, 10240, 20480, 40960, 81920} slots. • The periodicity of 20480 slots is only applicable for 30, 60 and 120 kHz SCS; • The periodicity of 40960 slots is only applicable to 60 and 120 kHz SCS; • The periodicity of 81920 slots is only applicable to 120 kHz SCS.

[0053] This means that the PRS resource set (and therefore all its PRS resources) can also exhibit a periodic pattern, with the periodicity depending on the SCS. For SP-SRS for positioning, a configuration with MAC-CE enable / disable is supported, where SRS is received at the serving cell and the neighboring cell. Aperiodic SRS for positioning is triggered by a DCI, without affecting the Re1-15 DCI (the existing triggers in Rel-15 are reused). UL-PRS(SRS) resource set properties

[0054] Periodic, semipersistent, or aperiodic UL-PRS transmission is a property of a UL-PRS resource set, i.e., all UL-PRS resources contained in a UL-PRS resource set are of the same type.

[0055] Another feature of the UL-PRS resource set is the Tx power control (PC). For UL-PRS, only an open-loop (OL) PC is supported, including support for (fractional) path loss compensation to supplying and neighboring TRPs. The UE estimates UL path loss for supplying and neighboring TRPs based on DL measurements and sets the UL-PRS Tx power accordingly. The UE can estimate the path loss from a DL RS, which can be an SSB or DL-PRS not only from the supplying TRP but also from neighboring TRPs. Fig.6) Since the serving TRP is likely closer to the UE than a neighboring TRP, a DL path loss estimation based on the serving TRP may result in insufficient Tx power for UL-PRS being detectable at the neighboring TRPs (UL audibility). Path loss estimation based on a RS of neighboring TRPs can be used to transmit UL-PRS to the intended TRPs at an appropriate power. That is, a smaller path loss estimate results in higher UL-PRS transmission power to 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 pointing to neighboring cells to have better audibility and keep the noise in the serving cell low. Assistance information is provided if SSB / DL-PRS is used for path loss estimation.Since PC parameters are part of the SRS resource set configuration, all resources in a set should have the same PC parameters. Parameters that describe a UL-PRS resource (similar to or extensions of Rel-15-SRS parameters) • UL-PRS resource identity (SRS-PosResourceId in the specification): Defining the specific UL-PRS resource • Transmission comb: Define • Comb size N of UL-PRS (N = 2, 4 or 8), • Comb offset of the first symbol of the UL-PRS resource (0 . . . N-1) • Cyclic shift to generate the reference sequence, e.g. Kamm-2 supports 8 cyclic shifts, and Kamm-4 supports 12 cyclic shifts • Resource allocation: Define a 1st OFDM symbol location of the UL-PRS resource in a slot (0, 1, 2, ... , 13) and the number of symbols of the UL-PRS resource (1, 2, 4, 8 or 12) • Frequency domain shift: Define the frequency domain position of the UL-PRS resource (as for Rel-15-SRS) • Frequency hopping: Defines the bandwidth of the UL-PRS resource. The name is reused from Rel-15-SRS, although frequency hopping is not supported for UL-PRS. However, part of the frequency hopping parameter is the bandwidth specification, which is the only parameter applicable to UL-PRS. • Group or sequence jumps: Define whether a group or sequence of jumps is used (as for Rel-15-SRS). The jump modes are used to randomize the reuse of a sequence within the system. • Resource type: Define UL-PRS resource type (periodic, semi-persistent, aperiodic) & periodicity for semi-persistent & periodic UL-PRS • Sequence ID, defines a UE-specific sequence ID used to initialize PN group and sequence jumps. For UL-PRS, the number of distinct sequence group jump patterns is increased from 1024 (Rel-15 SRS) to 65536, and the number of bits for the sequence ID is increased to 16. To enable UL-PRS to be received by neighboring TRPs, increasing the number of available UL-PRS sequences can be advantageous to reduce UL-PRS collisions and further attenuate UL interference. • Spatial relationship information: Defines the spatial relationship between a reference RS and the target UL-PRS. The reference RS can be an SSB, CSI-RS (serving cell only), DL-PRS, SRS, or UL-PRS. Parameters that describe a UL-PRS resource set (similar to or extensions of the Rel-15-SRS parameters) • UL-PRS resource set identity (SRS-PosResourceSetId in the specification): Defines a specific UL-PRS resource set. It is unique within the context of the BWP in which the UL-PRS is defined. • Resource Type: Defines the time domain behavior of the UL-PRS resource configuration. The network configures UL-PRS resources within the same resource set with the same time domain behavior as periodic, aperiodic, and 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 with SRS resources within the same SRS resource set (SRS-ResourceSet or SRS-PosResourceSet-r16) is not expected to be configured with different slot-level periodicities.For periodic SRS, the duration of SRS transmission with these periodicities depends on the network configuration, and periodic transmission will continue unless reconfigured (as long as the UE is in that particular state unless reconfigured by RRC, because it is inactive or connected, the UE will be able to transmit). • Alpha is a value used for UL-PRS power control: It defines fractional path loss compensation. The alpha value is multiplied by the path loss estimate using the UE (Ultimate Energy). For complete path loss compensation, alpha equals 1. • p0 is a value for 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 p0 + Alpha · PL, where PL is the path loss estimate. • Path Loss Reference RS: Defines the reference DL signal to be used for path loss estimation. The DL reference signal can be an SSB or DL-PRS signal from the supplying or adjacent TRP. • UL-PRS Resource List: Define the configuration for each resource in the set. UL-based positioning measurements.

[0056] For the same reasons as with DL, additional measurements are specified to support UL-based positioning. In particular, 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 using the subframe boundary as a reference. Therefore, this reports the arrival time of an SRS relative to the nearest DL subframe boundary. • AoA is the angle of arrival for a signal transmitted by the UE relative to either a global reference or geographic north and the zenith, or relative to a local coordinate system. In a fixed-beam system, this corresponds in practice to the direction in which the beam receives the signal. • SRS-Rx power is the SRS receive power (SRS-RSRP), similar to its DL counterpart, which is the received power of SRS. It can be used, for example, for fingerprint schemes.

[0057] It is noted that no SRS-based measurements were defined / specified in Rel-15 (left for the gNB). However, for positioning purposes, the measurements are defined for the gNB-BU to provide for the LMF.

[0058] Table 2 provides information regarding the mapping between UL-PRS and gNB measurements. Positioning techniques are also given for informational purposes only. Table 2. Comparison between UL-PRS and gNB measurements UL-PRS gNB measurements To enable support for the following positioning techniques Rel-16-SRS for positioning UL-RTOA UL-TDOA Rel-16-SRS for positioning UL-SRS-RSRP UL-TDOA, UL-AoA, Multi-RTT Rel-16-SRS for positioning gNB Rx-Tx time difference Multi-RTT Rel-16-SRS for positioning AoA and ZoA UL-AoA, Multi-RTT NR RAT-dependent UE positioning procedures

[0059] The following RAT-dependent UE positioning methods are supported in Rel-16: • DL Time Difference of Arrival (DL TDOA): This method uses the DL-RSTD and optionally the DL-PRS-RSRP measurements received by multiple gNBs at the UE, together with knowledge of the geographic coordinates of the gNBs and their relative DL timing, to determine the position of the UE. • UL Time Difference of Arrival (UL TDOA): In this procedure, the position of the UE 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 exit angle (DL AOD): This method uses the DL PRS-RSRP measurements taken on signals received by multiple gNBs, together with knowledge of the spatial information of the DL radio signals and geographic coordinates of the gNBs to determine the position of the UE. • UL Angle of Arrival (UL-AoA): This method is used to estimate the UE position based on the UL-AoA and optionally the UL-SRS-RSRP measurements performed on UL radio signals at different gNBs, along with other configuration information. • Multi-round-time (Multi-RTT): In this method, the UE position is estimated based on measurements taken 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 by the UE. Interference handling for UL-PRS

[0060] To minimize interference between TRPs transmitting DL-PRS and UEs transmitting UL-PRS, the NR-Rel-16 positioning specification supports several interference management techniques: • PRSs are orthogonalized in code, frequency, and time domains in both the UL and DL directions. • For 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 (under interfering nodes) can be configured using different frequency domain comb factors. • Orthogonalizing PRS in the time domain ( Fig. 7) • Cyclic displacement configurations are used for UL-PRS • Mute configurations are used for DL-PRS. Spatial UL-PRS relationship (supported spatial relationships to the UL-PRS resource)

[0061] Both DL-PRS and UL-PRS can also serve as spatial quasi-co-location (QCL) references for establishing positioning beam pairs. That is, given knowledge of a suitable RX beam for DL-PRS, the RX knows that the same RX beam should be suitable for UL-PRS. A spatial relationship specification for UL-PRS resources is supported either to a DL-RS (SSB, CSI-RS (serving cell only), or DL-PRS) or to previously transmitted UE-SRS or UL-PRS. The UL-PRS beam can be derived from the spatial relationship to a specified DL-RS, with the UE being able to transmit UL-PRS in the reciprocal direction of how it sets up its RX beam upon receiving the DL-RS, as illustrated.An additional procedure can be used by the network, whereby the UE transmits a UL-PRS or SRS beam sweep and gNB refers back to one of the overlapped beams in a previously transmitted UL-PRS or SRS resource to indicate a spatial relationship to the UL-PRS resource.

[0062] In comparison to the Rel-15-SRS, UL-PRS can exhibit a spatial relationship to a neighboring TRP ( Fig.8) For positioning, UL-PRS generally also need to be received by neighboring TRPs. To provide connectivity, NR-UEs supporting mmWave typically include multiple antenna arrays pointing in different directions. The spatial relationship for both providing and neighboring TRPs is primarily used to indicate which UL-TX beam the UE can use for UL-PRS. To determine a suitable spatial UL-PRS domain transmission filter in FR2 (i.e., beam) pointing toward neighboring TRPs, the UE can receive an RS for the UL-PRS beam from the same direction as those of the desired UL-PRS direction. The RS from a neighboring TRP can be an SSB or DL-PRS. UL-PRS flexibility for beam shaping and spatial allocation

[0063] Within an SRS resource set, there is flexibility for spatial allocations. In particular, there can be different resources (rays) within a set. The current SRS design allows for some directions to be repeated more frequently than others. Although all resources in a set repeat with the same periodicity, within a single resource (e.g., for Kamm-2 / 2-OS) there can be 1, 2, 4, or 6 repetitions, providing additional flexibility.

[0064] Furthermore, multiple SRS resource sets can be configured for a single UE, enabling different beamforming across the different sets. For example, one set of narrow beams to cover an area assigned to one set, and another set of wider beams to target a slightly different coverage assigned to the second resource set. In the context of acquisition, this design aspect can also be applied to implementing SRI durations at the sub-slot level, as will be revealed later. This concept can also be reused to define multiple acquisition frames (along with their corresponding SRI settings) (e.g., to take advantage of different measurements and / or different dynamic levels in different parts of the environment / FoV).Multiple capture frames could be defined using an SP-SRS setting, and the appropriate frame could be dynamically activated by MAC CE. This would be useful because different SRS settings could be dynamically assigned to the UE, e.g., for different SRIs, etc. 4. Implementation: Reusing the UL-PRS signal for detection (UL-PRS signal resource structure from the detection point of view)

[0065] This section focuses on assessing the feasibility of reusing a UL-PRS signal for acquisition (although the possibility may be limited to certain UCs / KPIs). As previously mentioned, UL-PRS exhibits characteristics similar to DL-PRS regarding frequency and time resource allocation, patterns, and regularity, which are desirable for acquisition. In particular, UL-PRS has certain regularities and attributes, and the supported patterns show synergy with acquisition signal attributes.

[0066] To understand the feasibility of reusing a UL-PRS signal for acquisition, it is important to identify the analogies and differences between the specified PRS signal and the desired resource structure for the acquisition signal.

[0067] Example 1: Mapping UL-PRS attributes to desired detection signal attributes - Analogies between UL-PRS and detection signal attributes 1. UL-PRS resource ↔ acquisition beam (for UL-based positioning, UL-PRS resources are supported with one port, i.e., each UL-PRS resource is dedicated to transmission in a single direction). One resource corresponds to one SRS beam, and resource sets correspond to a collection of SRS resources (i.e., beams) aligned to a given TRP. 2. The number of PRS resources within a PRS resource set ↔ the number of beam directions in SRI. This also relates to the number of OFDM symbols in each SRS resource of the set and how they are located. Smaller comb sizes are preferred for detection because, compared to larger combs, they utilize more SC and provide more intra-SRI flexibility in assigning OFDM symbols to different directions and / or for different purposes (UL-PRS versus non-PRS), while also imposing less of a limitation on the maximum uniquely detectable distance. 3. Resource set together with periodicity / repetition parameters and the number and distance of resources within the set, defining SRI ↔ SRI (collection of an occurrence of all PRS resources within the set) • As mentioned above, for the purpose of capturing each symbol within the SRI, a different beam / direction can be assigned, and in an SRS resource set, multiple SRS resources are transmitted, each for one direction. • For Kamm-2 / 2-OS, there can be 1, 2, 4, or 6 repetitions within an SRS resource. This is equivalent to using multiple SRI symbols to repeat the same direction and processing gain. • Currently, there may be no limit to the min / max duration of a sentence (an instance of the sentence) in the time domain, and the duration and placement of resources within a sentence are a matter of configuration. 4. The total time interval containing repetitions of the resource set with its periodicity (i.e., repetitions of SRI - k*SRI) ↔ capture block - possible duration, based on the network configuration. • Across SRIs within a capture block, the number and pattern of capture resources and directions should be the same (additional processing would be required for irregular resources, which may not always be justified). Therefore, a consistent configuration of SRS resources is required for periodic occurrences of SRS resource sets, which is achieved by defining periodically occurring opportunities. • The same number and placement of OFDM symbols across all SRIs should be considered for non-PRS transmissions. • Number of repetitions of the SRS resource set ↔ Doppler FFT size, k 5. How frequently periodic occurrence (i.e., the entire acquisition block consisting of k*SRI) can be (re-)configured and repeated ↔ update rate for acquisition (the minimum achievable update rate may be related to signaling limitations). Example 2: One-way detection via UL-PRS

[0068] For single-direction acquisition, a UL-PRS resource (i.e., a beam direction) and repetitions of this resource are required for Doppler estimation. For UL-PRS-based acquisition, it is important to understand, with proper UL-PRS configurations, how frequently a direction can occur for Doppler processing and at what granularity time / frequency resources can be configured for that direction.

[0069] A look at supported slot-level patterns of UL-PRS resources shows that one or more UL-PRS resources (from one or more resource sets) can exist within a slot, each with or without repetition at the intra-resource level. For example, it is possible for multiple UL-PRS resources, such as each with a length of 2 OS, to be subjected to time domain multiplexing (TDM) within a resource set the length of a slot.

[0070] Although UL-PRS resource sets are repeated across slots, repetition of a single beam within the resource is also permitted; this can be used primarily for processing gain (not Doppler estimation). Specifically, based on the analogies built into the previous section, intra-resource repetition can allow repetition of a certain beam within the SRI for power gain and may not aid in velocity detection. For example, a maximum of 6 repetitions of a 2-OS / Kamm-2 within a slot are supported.

[0071] As discussed in previous sections, SRIs with a length of 7 OS, 14 OS, or 28 OS would be required (at least for certain UCs that do not require extremely high speeds). With UL-PRS-based acquisition, SRI durations of an integer number of slots can be easily achieved because the minimum periodicity of a slot is supported. However, for half-slot SRI durations, current UL-PRS resource settings may have some limitations, as discussed and addressed.

[0072] Regarding the SRI duration as an integer multiple of the slot (minimum SRI duration with one slot), different SRI durations can be defined depending on the periodicity and the number of resources within the set. For example, with a periodicity of 1 slot and all SRS resources of the set packed contiguously within a single slot (e.g., each UL-PRS resource is 1-12 OFDM symbols), an SRI duration of one slot can be achieved. With a periodicity of 2 slots and all SRS resources of the set packed contiguously within a single slot, an SRI of 2 slots can be achieved, with the capture transmission occurring only within the first slot of the SRI. The same logic applies to larger periodicities, resulting in lower Doppler / velocity detection. In the NR-UL-PRS design, at least two symbols in each slot are not used for PRS transmission and are reserved for other communication channels.

[0073] For a sub-slot SRI duration, non-UL-PRS symbols must be handled properly, taking into account the minimal gap within the UL-PRS slot. Otherwise, this can cause inconsistencies across SRIs for capture, which is undesirable (since inconsistencies across SRIs complicate replay 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 implement a sub-slot SRI (e.g., half-slot). For instance, each half-slot can form an SRI across different UL-PRS resource sets. The two PRS resource sets, each in half a slot, should be configured with a similar pattern and a similar number of PRS resources, covering the same spatial domains to maintain consistency across SRIs.

[0074] For the Kamm-2 UL-PRS resource, the duration is either 2, 4, 6, or 12 consecutive symbols. It is not possible to have two symbols of a 4-OS Kamm-2 UL-PRS resource in the first half of the slot and the other two symbols in the second half. These restrictions should be taken into account and handled appropriately.

[0075] To provide more flexibility regarding the reuse of the UL-PRS design for detection, some extensions and improvements will be discussed later. Example 3: Multi-directional detection via UL-PRS

[0076] Multidirectional acquisition requires multiple UL-PRS resources, i.e., multiple beam directions, and repetitions of this resource for Doppler estimation. Within the resource, a repetition of each beam primarily serves to increase processing gains within the SRI, not for Doppler estimation. Depending on how different resources of a single or multiple resource sets are localized, SRI can be defined differently.

[0077] For SRI durations of integer multiples of slots, similar to the unidirectional acquisition case, if multiple PRS resources of the same resource quantity within a slot are subjected to TDM, and if all resources of a quantity fit into one slot, the minimum SRI duration of a slot would be achieved. Depending on the periodicity defined for the quantity, different SRI durations can be defined.

[0078] Furthermore, if an SRS resource set contains resources across multiple slots, either one slot per resource or a mixture of slots with a single and multiple resources, SRIs across multiple slots can also be defined, effectively for lower Doppler estimates. 5. Implementation: Extensions and adaptations to UL-PRS for reuse in detection

[0079] Based on the examples above, SRS(UL-PRS) signal-supported patterns, attributes, regularities, and characteristics align with generally desired attributes of the acquisition signal. Therefore, UL-PRS (SRS) appears to be the most suitable for any acquisition scenario / architecture capable of utilizing a UL radio signal for acquisition. Furthermore, if a new acquisition signal is defined in the next generation of cellular systems, it can likely also be used for positioning, especially if the design incorporates backward compatibility. From a resource efficiency and overhead perspective, it may not be desirable to transmit the positioning and acquisition signals separately in the system (at least simultaneously) whenever possible.For the same reasons, it is also logical to adjust the positioning reference signal so that the detection requirements are taken into account as much as possible.

[0080] In summary, in the same sense that SRS, which was originally defined for bearing, is reused for UL positioning with extensions, while DL-PRS and UL-PRS were originally introduced for positioning, these signals can also be used for detection with certain extensions.

[0081] It is also noted that by enabling UL-PRS-based acquisition, the JCAS system can support both UE-based monostatic acquisition and gNB-based bistatic acquisition (UE is the UL-PRS signal transmitter and gNB is the UL-PRS signal acquisition receiver), as well as gNB-based positioning (see Section 2 for more background).

[0082] To enable or improve the reuse of the UL-PRS signal for acquisition purposes, some modifications and adaptations are disclosed below. It is noted that some of the extensions are similar to DL-PRS extensions disclosed in IDF AE8858. Example 1

[0083] Extending the UL-PRS comb size configuration from {2, 4, 8} to {1, 2, 4, 8} or to {1, 2, 3, 4, 8}, where comb-3 can be applied to the 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 the use of consecutive subcarriers over the OFDM symbol (extension to allow the use of consecutive subcarriers over a symbol; examples may include a single-symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS(SRS) resource).

[0084] As discussed in section 2, from the perspective of the detection point, for example, an FD comb of size m Kamm = 2 or 3 are supported, whereby different sets of subcarriers (implemented, for example, with different frequency domain RE offsets) can be used to manage interference from the signals used for detection by the nearby UEs [at least to some extent]. It should be noted that there are generally different approaches to mitigating interference, such as exploiting multiplexing in the time, frequency, code, and / or sequence domains. A combination of different approaches can be considered and supported by the design for effective interference management, but this is outside the scope of protection of the current disclosure. Example 2

[0085] Extending UL-PRS configurations to enable the use of the following

[0086] Partially staggered patterns for UL-PRS signals, which can be defined by M-level comb symbols and N symbols for a UL-PRS resource with M > N • Unstaggered patterns for UL-PRS signals, so that the same REs are used in successive symbols within a UL-PRS resource; examples may include: • Every second subcarrier above a symbol, without staggering across multiple symbols. • Every third subcarrier within a symbol, without staggering across multiple symbols. • Combinations of fully or partially staggered and non-staggered patterns for UL-PRS signals.

[0087] As discussed previously, the current structure regarding time and frequency domain resources can impose limitations on the flexibility of assigning symbols within the SRI duration to different beam directions or for different purposes (communication and acquisition). The above additions to the permissible PRS resource configurations improve such flexibility. Example 3

[0088] Extend the configuration to allow a slot to be fully occupied by UL-PRS resources from one or more sets (i.e., it is possible to have zero resources for non-UL-PRS purposes in a slot). The minimum of two non-PRS OFDM symbols in UL-PRS slots (e.g., the maximum duration of the SRS resource is 12 OS) can impose restrictions on SRI design. It is advantageous if the UL-PRS configuration allows all symbols within a slot to be allocated for UL-PRS transmission. Example 4

[0089] Extending the configuration to allow for the adaptation of non-consecutive symbols (at least two non-consecutive) for non-UL-PRS transmission (motivated by the same reasons for the examples above). Example 5

[0090] Extend the configuration to enable multi-port UL-PRS resource transfer. Multi-port transfer allows the simultaneous transmission of multiple beams in different directions. For example, the UE itself can currently aim on 2 or 4 ports simultaneously (i.e., in multiple directions) for channel reciprocity-based use cases with a 2-port / 4-port SRS resource configuration. Example 6

[0091] Extend the configuration to allow non-consecutive (and preferably symmetrical across 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 can be implemented with an equal distribution of the 4 symbols across two 2-symbol occurrences, each in a half-slot. In particular, this allows the implementation of SRI duration at the sub-slot level (e.g., half-slot) using a UL PRS resource set. Non-consecutive allocation of OFDM symbols for a UL PRS resource can be achieved by various means, such as enabling a configuration of the PRS resource symbol that is offset by a vector, etc. Example 7

[0092] Extending the configuration to allow for periodicity configurations at the granularity of the UL-PRS resource (e.g., per UL-PRS resource), as opposed to their definition at the fixed level. Therefore, different resources within the set can have different periodicities to support better spatial adaptations to cover the field of view. This helps to implement different SRI durations for different beam directions in the FoV. Otherwise, different sets are required to cover the FoV, with, for example, each set covering the directions (SRS resources) with the same required SRI, which can lead to excessive configuration signaling.

[0093] (It should be noted that currently it is not expected that a UE with SRS resources in the same SRS resource set SRS-ResourceSet or SRS-PosResourceSet-r16 will be configured with different periodicities at the slot level.) Example 8

[0094] Extending the configuration to also allow for the periodicity of the half-slot (e.g., for higher-speed UCs, etc.). Example 9

[0095] For acquisition purposes, it may be desirable (e.g., depending on the use case and its requirements) to collect a complete FoV scan within a short time and then wait for a longer period before initiating another scan. This can enable the highest possible velocity detection without blurring. In some use case scenarios, it is desirable to capture a complete snapshot of the FoV at the fastest rate (e.g., with shorter SRIs to detect high velocities and potentially shorter capture block durations) once per slower update rate to provide optimal coverage of any fast-moving objects. At other times, scanning can be performed at a slower rate (e.g., with larger SRIs) when no fast-moving objects are expected.

[0096] Extending the configuration to allow multiple levels of sampling rate configurations (to allow multiple / different repetition patterns and update rates) to enable a fast sampling rate for quickly collecting a number of UL-PRS resources, followed by a slower sampling rate to allow a wait time for dedicated communications before the next fast period.

[0097] Furthermore, extending the configuration to allow multiple periodicities for a UL-PRS(SRS) resource set configuration, potentially each with a total effective duration (as revealed, for example, in Example 13, e.g., in a number of slots, etc.).

[0098] Together with the idea revealed in Example 14, these provide the necessary flexibility to adapt the sampling based on FoV characteristics.

[0099] As mentioned in Example 3, current SRS resource set configurations can be limited to combs applied primarily to the small portion of OFDM symbols within the slot (typically the latter symbols). Ideally, for acquisition, it would be best to achieve a burst with each slot nearly full of acquisition combs to quickly perform all necessary acquisitions. The purpose of this extension is to ensure that any new UL-PRS can accommodate the need for a single acquisition to quickly gather the full field of view (FoV) sample, thus enabling optimal Doppler detection, rather than slowly achieving the FoV sample, as can occur in a background process. Example 10

[0100] For UL-PRS, the flexibility of handling both periodic and semi-persistent occurrences is potentially useful. However, many of the flexibility options in UL-PRS rely on signaling modes of DCI or RRC updates, which are slower than the time required for a single complete sample. Acquisition may require enabling a rapid burst of repetitions to gather a complete sample, followed by slower periodic control of the interval between samples.

[0101] Extend the configuration to enable a fully programmable, high-speed burst of UL-PRS transmits / captures. The transmit / capture burst may need to occur at a faster rate than DCI updates, so it may require including all necessary parameters without interruption by DCI or RRC reconfiguration. Transmit rate / capture, number of transmits / captures, and the normal UL-PRS parameters, such as OFDM symbol position within RB, comb size, and cyclic offset, must be set independently for the transmit / capture burst. Example 11

[0102] Extending the configuration to allow different power control parameters for resources within a set, i.e., to allow one PC configuration per UL-PRS resource (beam). Example 12

[0103] Extending the configuration to allow multiple (two or more) UL-PRS resource sets with potentially identical 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 that defines the resource start location), which may even be subject to TDM within a single slot, to enable the realization of different (e.g., two or more) SRIs using different (e.g., two or more) sets and their repetitions.

[0104] In particular, this extension enables the implementation of SRI durations at the sub-slot level (e.g., half-slot) or SRIs with durations of non-integer multiples of slots (e.g., 1.5 slots, etc.) using two or more UL-PRS resource sets. For example, the start symbol offset within a slot and (if required) the number of symbols for a UL-PRS resource can be configured differently for the two or more resource sets, which can typically share other parameters.

[0105] Regarding the SRI duration as an integer multiple of the slot (minimum SRI duration with one slot), it was previously discussed that different SRI durations can be defined depending on the periodicity, number, duration, and placement of the resources in a set. With a periodicity of 1 slot and all PRS resources of the set packed side-by-side within a single slot, an SRI duration of one slot can be achieved. Alternatively, with the supported configuration in the current example, to realize such an SRI duration, two sets can be configured with a common configuration of UL-PRS resources (e.g., excluding the configuration that defines the temporal location of the resources) and covered beam directions, and any other SRI is realized using a set with a periodicity of 2 slots.

[0106] Furthermore, this concept can be reused to define multiple acquisition frames (along with their corresponding SRI settings) (e.g., to benefit from different measurements and / or different dynamic levels in different parts of the environment / FoV). Example 13

[0107] Extending the UL-PRS configuration to also include the total duration (e.g., across a number of slots) over which the set (at least for semi-periodic and periodic sets) occurs with a specific configured periodicity. This enables a configurable capture block duration. Example 14

[0108] For UL-PRS, the frequency of periodic occurrence (i.e., the entire capture block consisting of k*SRI) can be (re-)configured and repeated, which determines that the capture update rate (the minimum achievable update rate) is related to the signaling constraints.

[0109] Extending the UL-PRS configuration to allow repetition of the entire periodic occurrence of a set over a specified configured duration (as extended in Example 13), with a configurable number of slots (>=0) as the gap between repetitions, implements a configurable update rate. This configuration can be specified via RRC signaling, MAC CE, or DCI (the latter for greater flexibility and lower latency). Furthermore, the entire periodic occurrence of a set over a specified configured duration can be made irregular based on certain specifications / triggers (i.e., the intervals with the configured durations can recur based on specifications (start / stop)). This results in a periodic / semi-periodic / aperiodic nature for the entire burst (a burst being a capture block of the Doppler FFT x SRI duration). Example 15

[0110] As mentioned previously, SRS is identified separately for positioning purposes; that is, it is a different configuration. This means that although positioning uses SRS, the purpose is differentiated within the configuration itself. Similarly, in one example, extensions of UL-PRS for acquisition purposes can also be configured using separate parameters that imply an acquisition use. Alternatively, an "acquisition" use can be defined, similar to "beam management," "antenna switching," etc. In a more advanced example, different acquisition uses can be defined, corresponding to different categories of UCs that require different measurements / processing. Accordingly, different measurements can be expected for each use.For example, channel measurements to detect UCs, which may involve inference channel variations or resolving channel multipath utilization (multipath utilization), e.g., weather monitoring or (AI-based) gesture recognition, etc., can be performed (and potentially reported) by the detection receiver.

[0111] It has already been mentioned that by enabling UL-PRS-based acquisition, the JCAS system can support both UE-based monostatic acquisition and gNB-based bistatic acquisition (UE being the UL-PRS signal transmitter and gNB being the UL-PRS signal acquisition receiver), as well as gNB-based positioning. Therefore, the methods for handling interference between signals from different UEs are also applicable to UL-PRS-based acquisition scenarios. Furthermore, in the case of gNB-based bistatic acquisition (UE being the UL-PRS signal transmitter and gNB being a UL-PRS signal acquisition receiver), the transmit power of the UE may not need to differ compared to the positioning / communication case, since the acquisition signal travels the same distance between the acquisition TX and RX nodes as in the positioning / communication case.Accordingly, existing interference treatment techniques may also be appropriate in the case of detection.

[0112] 6. Embodiment: Enabling speed and / or direction-related measurements to enable speed estimation during localization / positioning.

[0113] Although velocity estimation of an UE by the localization management function (or the gNB) is not currently precluded, the UL-PRS signal was not originally designed to support proper velocity estimation. With the discussed modifications to the UL-PRS signal, it is also possible to perform / report more accurate Doppler-related measurements of the UE and to enable the network and / or the gNB to perform Doppler and motion direction estimation with greater accuracy. For example, currently, as part of performing positioning measurements (e.g., ToA, etc.), a correlation function can be applied in the delay (distance) domain, and the peaks in the correlation function can contribute to the position estimates. The correlation function can be extended to also include a second dimension in the Doppler domain to enable Doppler processing.This may be similar to generating the 2D periodogram, which is part of the baseline object detection receiver processing for acquisition applications. literature [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 (Chapter 3.1), released at the end of 2021. SYSTEMS AND IMPLEMENTATIONS

[0114] In the Fig. Figures 9-12 show various systems, devices and components with which aspects of the disclosed embodiments can be implemented.

[0115] Fig.Figure 9 illustrates a Network 900 according to various embodiments. The Network 900 can be operated in a manner that complies with the 3GPP technical specifications for LTE or 5G / NR systems. However, the exemplary embodiments are not limited in this respect, and the described embodiments may also apply to other networks that benefit from the principles described herein, e.g., future 3GPP systems or the like.

[0116] The Network 900 can include a UE 902, which can contain any mobile or non-mobile data processing device designed to communicate with the RAN 904 via an over-the-air connection. The UE 902 can be communicatively coupled to the RAN 904 through a Uu interface.The UE 902 can be, among other things, a smartphone, a tablet computer, a wearable computer device, a desktop computer, a laptop computer, in-vehicle infotainment, an in-vehicle entertainment device, a combination instrument, a head-up display device, an on-board diagnostic device, a mobile dashboard equipment, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked device, a machine-type communication device, an M2M or D2D device, an IoT device, etc.

[0117] In some embodiments, the Network 900 can include multiple UEs that are directly coupled to each other via a sidelink interface. The UEs can be M2M / D2D devices that communicate using physical sidelink channels, such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0118] In some embodiments, the UE 902 can additionally communicate with an AP 906 via an over-the-air connection. The AP 906 can manage a WLAN connection, which can be used to offload some or all of the network traffic from the RAN 904. The connection between the UE 902 and the AP 906 can be compliant with any IEEE 802.11 protocol, with the AP 906 potentially being a Wireless Fidelity (Wi-Fi®) router. In some embodiments, the UE 902, the RAN 904, and the AP 906 can use cellular WLAN aggregation (for example, LWA / LWIP). Cellular WLAN aggregation can involve the UE 902 being configured by the RAN 904 to use both cellular radio resources and WLAN resources.

[0119] The RAN 904 can include one or more access nodes, for example, the AN 908. The AN 908 can terminate air interface protocols for the UE 902 by providing access stratum protocols, including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, the AN 908 can enable data / voice connectivity between the CN 920 and the UE 902. In some embodiments, the AN 908 can be implemented in a discrete device or as one or more software entities running on server computers, for example, as part of a virtual network that can be called a CRAN or virtual baseband unit pool. The AN 908 can be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.The AN 908 can be a macrocell base station or a low-power base station for providing femtocells, picocells or other similar cells with smaller coverage areas, smaller user capacity or higher bandwidth compared to macrocells.

[0120] In embodiments where the RAN 904 includes multiple ANs, they can be interconnected 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 in some embodiments may be separated into control / user layer interfaces, allow the ANs to communicate information related to handoffs, data / context transfers, mobility, load management, interference coordination, and so on.

[0121] The ANs of the RAN 904 can 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 can be connected to multiple cells simultaneously, provided by the same or different ANs of the RAN 904. For example, the UE 902 and the RAN 904 can use carrier aggregation to allow the UE 902 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN can be a master node providing an MCG, and a second AN can be a secondary node providing an SCG. The first / second AN can be any combination of eNB, gNB, ng-eNB, etc.

[0122] The RAN 904 can provide the air interface over either licensed or unlicensed spectrum. For operation over unlicensed spectrum, nodes can use LAA, eLAA, and / or feLAA mechanisms based on CA technology with Pcells / Scells. Before accessing the unlicensed spectrum, nodes can perform media / carrier detection, for example, based on an LBT (listen-before-talk) protocol.

[0123] In V2X scenarios, the UE 902 or the AN 908 can be, or function as, an RSU, which can refer to any transport infrastructure entity used for V2X communications. An RSU can be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE can be referred to as a "UE-type RSU"; an eNB can be referred to as an "eNB-type RSU"; a gNB can be referred to as a "gNB-type RSU"; and so on. In one example, an RSU is a computing device coupled to a roadside radio frequency circuitry arrangement that supports connectivity for passing vehicle UEs.The RSU can also include an internal data storage circuitry to store intersection geometry, traffic statistics, media, and applications / software for capturing and controlling ongoing vehicle and pedestrian traffic. The RSU can enable very low-latency communication, which is necessary for high-speed events such as collision avoidance, traffic alerts, and the like. Additionally or alternatively, the RSU can also provide other cellular / WLAN communication services. The RSU components can be housed in a weatherproof enclosure suitable for outdoor installation, and they can include a network interface controller that provides a wired connection (e.g., Ethernet) to a traffic signal controller or backhaul network.

[0124] In some embodiments, the RAN 904 can be an LTE-RAN 910 with eNBs, for example, the eNB 912. The LTE-RAN 910 can provide an LTE air interface with the following characteristics: 15 kHz SCS; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface can 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 can operate on sub-6 GHz bands.

[0125] In some embodiments, the RAN 904 can be an NG-RAN 914 with gNBs, for example the gNB 916, or ng-eNBs, for example the ng-eNB 918. The gNB 916 can connect to 5G-enabled UEs using a 5G NR interface. The gNB 916 can connect to a 5G core via an NG interface, which may include an N2 or N3 interface. The ng-eNB 918 can also connect to the 5G core via an NG interface, but can also connect to a UE via an LTE air interface. The gNB 916 and the ng-eNB 918 can connect to each other via an Xn interface.

[0126] In some embodiments, the NG interface can be divided into two parts: an NG user level (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 level (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 914 and an AMF 944 (e.g., N2 interface).

[0127] The NG-RAN 914 can provide a 5G-NR air interface with the following features: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repeat, simplex, and Reed-Muller codes for control, and LDPC for data. The 5G-NR air interface can rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE air interface. The 5G-NR air interface may not use CRS, but instead uses PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and a reference signal for timing tracking. The 5G-NR air interface can operate in FR1 bands, which include sub-6 GHz bands, or in FR2 bands, which include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface can contain an SSB, which is an area of ​​a downlink resource grid containing PSS / SSS / PBCH.

[0128] In some embodiments, the SG-NR air interface can utilize BWPs for various purposes. For example, BWP can be used for dynamic adjustment of the SCS. For instance, the UE 902 can be configured with multiple BWPs, each with a different SCS. When a BWP change is communicated to the UE 902, the transmission's SCS is also modified. Another application of BWP is power saving. Specifically, multiple BWPs for the UE 902 can be configured with varying amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing fewer PRBs can be used for data transmission under low traffic load conditions, while allowing power savings on the UE 902 and, in some cases, on the gNB 916.A BWP with a larger number of PRBs can be used for scenarios with higher traffic volumes.

[0129] The RAN 904 is communicatively coupled to the CN 920, which contains network elements to provide various functions for supporting data and telecommunications services for customers / subscribers (for example, users of the UE 902). The components of the CN 920 can be implemented in a single physical node or in separate physical nodes. In some embodiments, NFV can be used to virtualize any or all of the functions provided by the network elements of the CN 920 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of the CN 920 can be referred to as a network slice, and a logical instantiation of a section of the CN 920 can be referred to as a network sub-slice.

[0130] In some embodiments, the CN 920 can be an LTE-CN 922, which can also be referred to as an EPC. The LTE-CN 922 can include the MME 924, the SGW 926, the SGSN 928, the HSS 930, the PGW 932, and the PCRF 934, which are coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of the LTE-CN 922 can be briefly introduced below.

[0131] The MME 924 can implement mobility management functions to track the current location of the UE 902, enabling paging, carrier activation / deactivation, handovers, gateway selection, authentication, etc.

[0132] The SGW 926 can establish an S1 interface to the RAN and route data packets between the RAN and the LTE-CN 922. The SGW 926 can serve as a local mobility anchor point for RAN-cross node handoffs and also provide an anchor for 3GPP-cross mobility. Other tasks may include regulatory monitoring, billing, and enforcement of certain policies.

[0133] The SGSN 928 can track the location of a UE 902 and perform security functions and access control. Additionally, the SGSN 928 can perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by the MME 924; MME selection for handovers; and so on. The S3 reference point between the MME 924 and the SGSN 928 enables user and carrier information exchange for inter-3GPP access network mobility in idle / active states.

[0134] The HSS 930 can include a database for network users, including participation-related information to support the handling of communication sessions by the network units. The HSS 930 can provide support for routing / roaming, authentication, authorization, name / address resolution, location dependencies, and more. An S6a reference point between the HSS 930 and the MME 924 can enable the transfer of subscription and authentication data to authenticate / authorize user access to the LTE-CN 920.

[0135] The PGW 932 can establish an SGi interface to data network (DN) 936, which may include application / content server 938. The PGW 932 can route data packets between LTE CN 922 and data network 936. The PGW 932 can be coupled to SGW 926 via an S5 reference point to enable user-level tunneling and tunnel management. The PGW 932 can also include a node for policy enforcement and charge collection data (e.g., PCEF). Additionally, the SGi reference point between PGW 932 and data network 936 can be an external public PDN, a private PDN, or an internal PDN, for example, for providing IMS services. The PGW 932 can be coupled to PCRF 934 via a Gx reference point.

[0136] The PCRF 934 is the policy and charge calculation control element of the LTE-CN 922. The PCRF 934 can be communicatively coupled with the 938 application / content server to determine appropriate QoS and charge calculation parameters for service flows. The PCRF 932 can provide associated rules to a PCEF (via a Gx reference point) with a suitable TFT and QCI.

[0137] In some embodiments, the CN 920 can be the 5GC 940. The 5GC 940 can be the AUSF 942, AMF 944, SMF 946, UPF 948, NSSF 950, NEF 952, NRF 954, PCF 956, UDM 958, and AF 960, which, as shown, are coupled to each other via interfaces (or "reference points"). The functions of the elements of the 5GC 940 can be briefly described below.

[0138] The AUSF 942 can store data for UE 902 authentication and handle authentication-related functionality. The AUSF 942 can provide a common authentication framework for different access types. In addition to communicating with other 5GC 940 elements via reference points, as shown, the AUSF 942 can have a service-based NausF interface.

[0139] The AMF 944 can 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 related to the UE 902. The AMF 944 can also handle registration management (for example, registering the UE 902), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 944 can provide transport for SM messages between the UE 902 and the SMF 946 and act as a transparent proxy for routing SM messages. The AMF 944 can also provide transport for SMS messages between the UE 902 and an SMSF. The AMF 944 can interact with the AUSF 942 and the UE 902 to perform various security anchor and context management functions.Furthermore, the AMF 944 can be an endpoint 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 can be a termination point of NAS (N1) signaling, and perform NAS encryption and integrity protection. The AMF 944 can also support NAS signaling with the UE 902 via an N3-IWF interface.

[0140] The SMF 946 can be responsible for SM (for example, session setup, tunnel management between the UPF 948 and an AN 908); UE IP address assignment and management (including optional authorization); selection and control of a UP function; configuration of traffic routing at the UPF 948 to direct traffic to a suitable destination; completion of interfaces to policy control functions; control of part of policy enforcement, charge billing, and QoS; lawful monitoring (for SM events and interface to the LI system); completion of SM portions of NAS messages; downlink data notification; initiation of specific SM information sent via AMF 944 over N2 to the AN 908; and determination of a session's SSC mode.SM can refer to the management of a PDU session, and a PDU session or "session" can refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 902 and the 936 data network.

[0141] The UPF 948 can act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for the interconnect to the 936 data network, and a branch point to support a multi-homed PDU session. The UPF 948 can also perform packet routing and forwarding, packet inspection, enforcement of the user-level portion of policy rules, lawful packet monitoring (UP collection), traffic usage reporting, user-level QoS handling (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic auditing (e.g., SDF-to-QoS flow mapping), transport-level packet marking in the uplink and downlink, and downlink packet buffering and downlink data notification triggering. The UPF 948 can include an uplink classifier to support routing traffic flows to a data network.

[0142] The NSSF 950 can select a set of network slice instances to serve the UE 902. The NSSF 950 can also determine permissible NSSAIs and the mapping to the subscribed S-NSSAIs, if necessary. The NSSF 950 can also determine an AMF set to use 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 network slice instance set for the UE 902 can be triggered by the AMF 944, with which the UE 902 is registered, by interacting with the NSSF 950, which may result in a change to the AMF. The NSSF 950 can interact with the AMF 944 via an N22 reference point. and can communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 950 can have a service-based NSSF interface.

[0143] The NEF 952 can securely discover services and capabilities provided by 3GPP third-party network functions, internal discovery / re-discovery, AFs (e.g., AF 960), edge computing or fog computing systems, and so on. In such configurations, the NEF 952 can authenticate, authorize, or throttle the AFs. The NEF 952 can also translate information exchanged with the AF 960 and information exchanged with internal network functions. For example, the NEF 952 can translate between an AF service identifier and internal 5GC information. The NEF 952 can also receive information from other network functions based on the disclosed capabilities of other network functions. This information can be stored as structured data in the NEF 952 or in a data storage network function using standardized interfaces.The stored information can then be disclosed by the NEF 952 to other NFs and AFs or used for other purposes, such as analytics. Additionally, the NEF 952 can have a service-based Nnef interface.

[0144] The NRF 954 can support service discovery functions, receive NF discovery requests from NF instances, and provide information about discovered NF instances to the NF instances. The NRF 954 also manages information about available NF instances and their supported services. As used herein, the terms "instantiate," "instantiation," and the like can refer to the creation of an instance, and an "instance" can refer to a specific occurrence of an object, such as that which might occur during the execution of program code. Additionally, the NRF 954 can have a service-based Nnrf interface.

[0145] The PCF 956 can provide policy rules to control plane functions for enforcement and can also support a unified policy framework to govern network behavior. The PCF 956 can also implement a front end to access subscription information relevant to policy decisions in a UDR of the UDM 958. In addition to communicating with functions via reference points, as shown, the PCF 956 features a service-based Npcf interface.

[0146] The UDM 958 can handle subscription-related information to support the handling of communication sessions by network entities and can store subscription data from the UE 902. For example, subscription data can be communicated between the UDM 958 and the AMF 944 via an N8 reference point. The UDM 958 can comprise two parts: an application front end and a UDR. The UDR can store subscription and policy data for the UDM 958 and the PCF 956, and / or structured exposure and application data (including application detection PFDs and application requirement information for multiple UE 902s) for the NEF 952. The service-based Nudr interface can be used by the UDR 958 to grant the UDM 958, PCF 956, and NEF 952 access to a specific set of stored data, as well as the ability to read and update it (e.g., by changing the stored data).To enable adding, modifying, deleting, and subscribing to notifications about relevant data changes in the UDR. The UDM can include a UDM frontend responsible for credential processing, site management, subscription management, and so on. Multiple different frontends can serve the same user in different transactions. The UDM frontend accesses the subscription information stored in the UDR and performs credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other network interfaces via reference points, as shown, the UDM 958 can feature the service-based Nudm interface.

[0147] The AF 960 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0148] In some embodiments, the 5GC 940 can enable edge computing by selecting operator / third-party services that are geographically close to a point where the UE 902 connects to the network. This can reduce latency and network load. To provide edge computing implementations, the 5GC 940 can select a UPF 948 near the UE 902 and perform traffic routing from the UPF 948 to the Data Network 936 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by the AF 960. In this way, the AF 960 can influence UPF (re)selection and traffic routing. Based on the operator's deployment, if the AF 960 is considered a trusted entity, the network operator can allow the AF 960 to interact directly with relevant network functions. Additionally, the AF 960 can feature a service-based Naf interface.

[0149] The data network 936 can represent various network operator services, internet access, or third-party services, which may be provided by one or more servers, including, for example, the application / content server 938.

[0150] Fig. Figure 10 schematically illustrates a wireless network 1000 according to various embodiments. The wireless network 1000 can include a UE 1002 in wireless communication with an AN 1004. The UE 1002 and the AN 1004 can be similar to and essentially interchangeable with the identically named components described elsewhere herein.

[0151] The UE 1002 can be communicatively coupled with the AN 1004 via connection 1006. Connection 1006 is illustrated as an air interface to enable communicative coupling and can be compatible with cellular communication protocols, such as an LTE protocol or an SG-NR protocol operating at millimeter wave or sub-6 GHz frequencies.

[0152] The UE 1002 can include a host platform 1008 coupled to a modem platform 1010. The host platform 1008 can include an application processing circuit arrangement 1012, which can be coupled to the protocol processing circuit arrangement 1014 of the modem platform 1010. The application processing circuit arrangement 1012 can run various applications for the UE 1002 that send / receive application data. Furthermore, the application processing circuit arrangement 1012 can implement one or more layer operations to send / receive application data to / from a data network. These layer operations can include transport (e.g., UDP) and internet (e.g., IP) operations.

[0153] The protocol processing circuit arrangement 1014 can implement one or more of the layer operations to enable the transmission or reception of data over the link 1006. The layer operations implemented by the protocol processing circuit arrangement 1014 can include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0154] The 1010 modem platform can further include a 1016 digital baseband circuitry arrangement that can implement one or more layer operations that are “below” layer operations performed by the 1014 protocol processing circuitry arrangement in a network protocol stack. These operations can include, for example, PHY operations, including one or more HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding, which can include one or more space-time, space-frequency, or spatial encodings, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel blind decoding, and other related functions.

[0155] The modem platform 1010 can further include a transmit circuit assembly 1018, a receive circuit assembly 1020, an RF circuit assembly 1022, and an RF front end (RFFE) 1024, which may include or be connected to one or more antenna panels 1026. In short, the transmit circuit assembly 1018 can include a digital-to-analog converter, a mixer, intermediate frequency (IF) components, etc.; the receive circuit assembly 1020 can include an analog-to-digital converter, a mixer, IF components, etc.; the RF circuit assembly 1022 can include a low-noise amplifier, a power amplifier, power tracking components, etc. The RFFE 1024 can include filters (for example, acoustic surface / volume wave filters), switches, antenna tuners, beamforming components (for example, phase array antenna components), etc.The selection and arrangement of the components of the transmit circuit arrangement 1018, the receive circuit arrangement 1020, the RF circuit arrangement 1022, the RFFE 1024, and the antenna panels 1026 (generally referred to as "transmit / receive components") may be specific to details of a particular implementation, such as whether the communication is TDM or FDM, takes place 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 located in the same or different chips / modules, etc.

[0156] In some embodiments, the protocol processing circuit arrangement 1014 may include one or more instances of a control circuit arrangement (not shown) for providing control functions for the transmit / receive components.

[0157] UE reception can be established through and via the antenna panels 1026, the RFFE 1024, the RF circuit 1022, the receiving circuit 1020, the digital baseband circuit 1016, and the protocol processing circuit 1014. In some embodiments, the antenna panels 1026 can receive a transmission from the AN 1004 by receiving beamforming signals, which are received by several antennas / antenna elements of the one or more antenna panels 1026.

[0158] A UE transmission can be established through and via the protocol processing circuit 1014, the digital baseband circuit 1016, the transmit circuit 1018, the RF circuit 1022, the RFFE 1024, and the antenna panels 1026. In some embodiments, the transmitting components of the UE 1004 can apply a spatial filter to the data to be transmitted in order to form a transmit beam that is emitted by the antenna elements of the antenna panels 1026.

[0159] Similar to the UE 1002, the AN 1004 can include a host platform 1028 coupled to a modem platform 1030. The host platform 1028 can include an application processing circuit arrangement 1032 coupled to the protocol processing circuit arrangement 1034 of the modem platform 1030. The modem platform can also include a digital baseband circuit arrangement 1036, a transmit circuit arrangement 1038, a receive circuit arrangement 1040, an RF circuit arrangement 1042, an RFFE circuit arrangement 1044, and antenna arrays 1046. The components of the AN 1004 can resemble and be essentially interchangeable with the corresponding components of the UE 1002. In addition to the data transmission / reception described above, the components of the AN 1004 can perform various logical functions, such as...RNC functions include radio carrier management, dynamic management of uplink and downlink radio resources, and data packet scheduling.

[0160] Fig. Figure 11 is a block diagram illustrating components according to some exemplary embodiments that are capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-volatile machine-readable storage medium) and executing one or more of any of the methodologies discussed herein. In particular, Figure 11 shows Fig.11 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 circuit arrangement. In embodiments in which node virtualization (e.g., NFV) is used, a hypervisor 1102 may be run to provide an execution environment for one or more network slices / sub-slices that utilize the hardware resources 1100.

[0161] The 1110 processors can include, for example, the 1112 and 1114 processors. The 1110 processors can 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 Radio-Frequency Integrated Circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0162] The memory / storage devices 1120 can include main memory, disk storage, or any suitable combination thereof. The memory / storage devices 1120 can include, among other things, any type of volatile or non-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 memory, etc.

[0163] The communication resources 1130 can include interlink or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1104, one or more databases 1106, or other network elements over a network 1108. The communication resources 1130 can include, for example, 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.

[0164] The instructions 1150 may consist of software, a program, an application, an applet, an app, or other executable code to cause at least one of the processors 1110 to perform one or more of the methods described herein. The instructions 1150 may reside wholly or partially in at least one of the processors 1110 (e.g., in the processor's cache memory), in the memory / storage devices 1120, or in a suitable combination thereof. Furthermore, any portion of the instructions 1150 may be transferred from any combination of the peripheral devices 1104 or the databases 1106 to the hardware resources 1100. Accordingly, the memory of the processors 1110, the memory devices 1120, the peripheral devices 1104, and the databases 1106 are examples of computer-readable and machine-readable media.

[0165] Fig.Figure 12 illustrates a Network 1200 according to various embodiments. The Network 1200 can operate in a manner that complies with the 3GPP technical specifications for 6G systems. In some embodiments, the Network 1200 can operate concurrently with the Network 900. For example, in some embodiments, the Network 1200 can share one or more frequency or bandwidth resources with the Network 900. As a specific example, a UE (e.g., UE 1202) can be configured to operate in both the Network 1200 and the Network 900. Such a configuration can be based on a UE that includes a circuit arrangement designed to communicate with frequency and bandwidth resources of both the Network 900 and the Network 1200. In general, several elements of the Network 1200 can share one or more characteristics with elements of the Network 900.For the sake of brevity and clarity, such elements may not be repeated in the description of Network 1200.

[0166] The Network 1200 can include a UE 1202, which can be any mobile or non-mobile computing device capable of wireless communication with a RAN 1208. The UE 1202 can be similar to the UE 902, for example. The UE 1202 can be, among other things, a smartphone, tablet computer, wearable computing device, desktop computer, laptop computer, in-vehicle infotainment system, in-vehicle entertainment device, instrument cluster, head-up display (HUD), on-board diagnostic device, mobile dashboard device, mobile data terminal, electronic engine management system, electronic / power machine control unit, electronic / power machine control module, embedded system, sensor, microcontroller, control module, power machine management system, networked device, machine-type communication device, M2M or D2D device, IoT device, etc.

[0167] Although in Fig. Not specifically shown in Figure 12, the Network 1200 in some embodiments can include a variety of UEs directly coupled to each other via a sidelink interface. The UEs can be M2M / D2D devices that communicate using physical sidelink channels, such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Likewise, although this is shown in Figure 12, the network can also include a variety of UEs that are directly coupled to each other via a sidelink interface. Fig. 12 not specifically shown, the UE 1202 may be communicatively coupled with an AP, such as the AP 906, as with reference to Fig. 9 described. Although this in Fig. Unless specifically shown in Figure 12, RAN 1208 may additionally include one or more ANs, such as AN 908, in some embodiments, as described in reference to Fig. 9 described. The RAN 1208 and / or the AN of the RAN 1208 may be referred to as a base station (BS), a RAN node, or by any other term or name.

[0168] The UE 1202 and the RAN 1208 can be configured to communicate over 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 shared communication and acquisition. As used herein, the term "shared communication and acquisition" may refer to a system that enables wireless communication as well as radar-based acquisition over various types of multiplexes. As used herein, THz or sub-THz bandwidths may refer to communication in the frequency ranges of 80 GHz and above. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mmWave" frequency ranges.

[0169] The RAN 1208 enables communication between the UE 1202 and a 6G core network (CN) 1210. Specifically, the RAN 1208 allows the transmission and reception of data between the UE 1202 and the 6G-CN 1210. The 6G-CN 1210 can 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 can additionally include UPF 948 and DN 936, as described in [reference missing]. Fig. 12 shown.

[0170] Additionally, the RAN 1208 can include various supplementary functions that are in addition to, or alternative to, the functions of a legacy cellular network, such as a 4G or 5G network. Two such functions can 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 can be parts or functions of the Compute Service Layer. The Comp-CF 1224 can be a control layer function that provides functionalities such as managing the Comp-SF 1236, generating and managing compute task contexts (e.g., creating, reading, modifying, deleting), interacting with the underlying compute infrastructure for compute resource management, and so on. The Comp-SF 1236 can be a user layer function that acts as the gateway to interface compute service users (such as the UE 1202) and compute nodes behind a Comp-SF instance.Some functionalities of the Comp-SF 1236 can include: parsing compute service data received from users to calculate tasks executable by compute nodes; maintaining a service mesh entry gateway or service API gateway; enforcing service and charge policies; performance monitoring and telemetry collection, etc. In some implementations, a single instance of the Comp-SF 1236 can serve as the user-level gateway for a cluster of compute nodes. A single instance of the Comp-CF 1224 can control one or more instances of the Comp-SF 1236.

[0171] Two other such functions can include a Communication Control Function (Comm-CF) 1228 and a Communication Service Function (Comm-SF) 1238, which can be parts of the Communication Service Layer. The Comm-CF 1228 can be the control layer function for managing the Comm-SF 1238, creating / configuring / releasing communication sessions, and managing the communication session context. The Comm-SF 1238 can be a user layer function for data transport. The Comm-CF 1228 and the Comm-SF 1238 can be considered upgrades of the SMF 946 and the UPF 948, respectively, with respect to a 5G system in Fig. 9. The upgrades provided by the Comm-CF 1228 and the Comm-SF 1238 can enable service-conscious transport. For legacy data transport (e.g., 4G or 5G), the SMF 946 and the UPF 948 can still be used.

[0172] Two other such functions can include a Data Control Function (Data-CF) 1222 and a Data Service Function (Data-SF) 1232, which can be parts of the data service layer. The Data-CF 1222 can be a control layer function and provides functionalities such as managing the Data-SF 1232, creating, configuring, and releasing data services, managing the context of data services, and so on. The Data-SF 1232 can be a user layer function and act as the gateway between data service users (such as the UE 1202 and the various functions of the 6G-CN 1210) and data service endpoints behind the gateway. Specific functionalities can include parsing data service user data and forwarding it to appropriate data service endpoints, generating charge data, and reporting the data service status.

[0173] Another such function is the Service Orchestration and Chaining Function (SOCF) 1220, which can discover, orchestrate, and chain communication / computing / data services provided by functions on the network. Upon receiving service requests from users, the SOCF 1220 can interact with one or more of the Comp-CF 1224, the Comm-CF 1228, and the Data-CF 1222 to identify instances of the Comp-SF 1236, the Comm-SF 1238, and the Data-SF 1232, configure service resources, and create the service chain. This chain could contain multiple instances of the Comp-SF 1236, the Comm-SF 1238, and the Data-SF 1232 and their associated compute endpoints. Workload processing and data movement can then be performed within the created service chain. SOCF 1220 can also be responsible for maintaining, updating, and releasing a created service chain.Another such function can be the Service Registry Function (SRF) 1214, which can act as a registry for system services provided at the user level, such as services provided by service endpoints behind gateways of Comp-SF 1236 and Data-SF 1232, and services provided by UE 1202. SRF 1214 can be considered a counterpart to NRF 954, which can act as the registry for network functions.

[0174] Other such functions may include an Evolved Service Communications Proxy (eSCP) and a Service Infrastructure Control Function (SICF) 1226, which can provide a service communications infrastructure for control-plane and user-plane services. The eSCP can be related to the 5G Service Communications Proxy (SCP), adding user-plane service communications proxy capabilities. The eSCP is therefore expressed in two parts: eCSP-C 1212 and eSCP-U 1234 for control-plane and user-plane service communications proxy, respectively. The SICF 1226 can control and configure eCSP instances with respect to service traffic routing policies, access rules, load balancing configurations, performance monitoring, and so on.

[0175] Another such function is AMF 1244. AMF 1244 can be similar to 944, but with additional functionality. In particular, AMF 1244 can involve a potential functional repartitioning, such as moving the message forwarding functionality from AMF 1244 to RAN 1208.

[0176] Another such function is the Service Orchestration Discovery Function (SOEF) 1218. The SOEF can be designed to disclose service orchestration and chaining services to external users, such as applications.

[0177] The UE 1202 can include an additional function called the Compute Client Service Function (Comp-CSF) 1204. The Comp-CSF 1204 can have both control-plane and user-plane functionalities and can 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 job workload exchange, etc. The Comp-CSF 1204 can also work with network-side functions to decide whether a compute job should be executed on the UE 1202, the RAN 1208, and / or an element of the 6G-CN 1210.

[0178] The UE 1202 and / or the Comp-CSF 1204 can include a Service Mesh Proxy 1206. The Service Mesh Proxy 1206 can act as a proxy for service-to-service communication at the user level. Capabilities of the Service Mesh Proxy 1206 can include addressing, security, load balancing, etc. EXEMPLARY PROCEDURES

[0179] In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or parts or implementations thereof, may be the Fig. 9-12 or any other figure herein be designed to carry out one or more processes, techniques, or procedures as described herein, or parts thereof. Such a process is in Fig.Figure 13 illustrates the process. The process may refer to a procedure 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 involve, as described in Figure 1301, receiving an uplink positioning reference signal (UL-PRS) at a user device (UE); and performing, as described in Figure 1302, a capture based on the UL-PRS.

[0180] Another such process is in Fig. 14 shown. The process from Fig.14 may refer to a process to be carried out by a user device (UE), one or more elements of a UE, and / or one or more electronic devices that include or implement a UE. The process may, in 1401, include: identifying one or more acquisition-related parameters; generating, in 1402, based on the one or more acquisition-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting, in 1403, the UL-PRS to a base station, the base station being to use the UL-PRS for acquisition.

[0181] Another such process is in Fig. 15 shown. The process from Fig.15 may refer to a process to be performed by an electronic device (e.g., a user device (UE)) in a cellular network. The process may involve, at 1501, identifying an uplink positioning reference signal or UL-PRS resource with respect to a capture to be performed during a capture operation, wherein a UL-PRS resource comprises multiple UL-PRS symbols. In some embodiments, the UL-PRS resource may be based on a fifth-generation (5G) new-radio or NR bearing reference signal (SRS); generating, at 1502, a cellular transmission comprising a symbol repetition interval (SRI) that consists of or is based on the UL-PRS resource; and transmitting, at 1503, the cellular transmission during the performance of the capture operation.

[0182] In one or more embodiments, at least one of the components shown in one or more of the preceding figures may be designed to perform one or more operations, techniques, processes, and / or procedures as set forth in the following example section. For example, the baseband circuit arrangement, as described above in conjunction with one or more of the preceding figures, may be designed to operate according to one or more of the examples below. As another example, circuit arrangements connected to a UE, base station, network element, etc., as described above in conjunction with one or more of the preceding figures, may be designed to operate in accordance with one or more of the examples listed below in the example section. EXAMPLES

[0183] Example 1 may include a device used in a capture entity, wherein the device comprises a processor circuit arrangement designed to cause the capture entity to map and transmit the modulated symbols according to the 5G-NR Uplink (UL) Positioning Reference Signal (PRS) design, using the following equivalences (marked with ↔). • UL-PRS resource ↔ acquisition beam (for UL-based positioning, UL-PRS resources are supported with one port, meaning each UL-PRS resource is dedicated to transmission in a single direction). One resource corresponds to one SRS beam, and resource sets correspond to a collection of SRS resources (i.e., beams) aligned to a given TRP. • The number of PRS resources within a PRS resource set ↔ the number of beam directions in SRI. This also relates to the number of OFDM symbols in each SRS resource of the set and how they are located. Smaller comb sizes are preferred for detection because, compared to larger combs, they utilize more subcarriers and provide more intra-SRI flexibility in assigning OFDM symbols to different directions and / or for different purposes (UL-PRS versus non-PRS), while also imposing less of a constraint on the maximum uniquely detectable distance. • Resource set, together with periodicity / repetition parameters and the number and distance 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 are transferred, each for one direction. For Kamm-2 / 2-OS, there can be 1, 2, 4, or 6 repetitions within an SRS resource. This is equivalent to using multiple SRI symbols to repeat the same direction and the same processing gain. • The entire time interval containing repetitions of the resource set with its periodicity (i.e., repetitions of SRI) ↔ capture block – possible durations, is based on the network configuration. Across SRIs within a capture block, the number and pattern of capture resources and directions are configured identically to achieve a consistent configuration of SRS resources for periodic occurrences of SRS resource sets. The same number and placement of OFDM symbols across all SRIs is also maintained for non-PRS transmissions. The number of repetitions of the SRS resource set ↔ Doppler FFT size, K. • How frequently periodic occurrence can be (re)configured ↔ update rate for detection (the minimum achievable update rate may be related to signaling limitations).

[0184] Example 2 can include the setup from Example 1 or any other example herein, with the UL-PRS configuration also allowing one-symbol and three-symbol PRS resources.

[0185] Example 3 may include the setup from Example 1 or any other example herein, supporting the use of consecutive subcarriers over an OFDM symbol by a UL-PRS or PRS-like signal, with or without repetitions within a UL-PRS resource. Comb-1 signifies the use of consecutive subcarriers over the OFDM symbol (an extension to allow the use of consecutive subcarriers over a symbol; examples may include a single-symbol UL-PRS signal, potentially with or without repetitions within a UL-PRS(SRS) resource).

[0186] Example 4 may include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to support a comb size of {1, 2, 4, 8} or {1, 2, 3, 4, 8}, where comb-3 may be applicable to a UL-PRS resource duration of 1 or 3 or 12 OS.

[0187] Example 5 may include the setup from Example 5 or any other example herein, using different sets of subcarriers (e.g., implemented with different frequency domain RE offsets) to handle interference from the signals used to capture from nearby UEs.

[0188] Example 6 may include the setup from Example 1 or any other example herein, and also supports the use of partially staggered patterns for UL-PRS or PRS-like signals, which may be defined by M-level comb symbols and N symbols for a UL-PRS resource with M > N.

[0189] Example 7 may include the setup from Example 1 or any other example herein, supporting non-staggered patterns for UL-PRS or PRS-like signals, so that the same resource elements (REs) are used in successive symbols within a UL-PRS resource; examples may include: • Every second subcarrier above a symbol, without staggering across multiple symbols. • Every third subcarrier within a symbol, without staggering across multiple symbols.

[0190] Example 8 may include the setup from Example 1 or any other example herein, supporting combinations of fully or partially staggered and non-staggered patterns for PRS or PRS-like signals.

[0191] Example 9 can include the setup from Example 1 or any other example herein, supporting the use of all symbols within a slot for PRS allocation, i.e., the configuration is extended to allow a slot to be fully occupied by UL-PRS resources from one or more sets (i.e., it is possible to have zero resources for non-UL-PRS purposes in a slot).

[0192] Example 10 may include the setup from Example 1 or any other example herein, wherein a UL-PRS configuration allows for the adaptation of non-consecutive OFDM symbols (at least two non-consecutive symbols) for a non-UL-PRS transmission within the PRS slot.

[0193] Example 11 may include the setup from Example 1 or any other example herein, wherein a UL-PRS configuration enables multi-port UL-PRS resource transfer, thereby allowing multiple beams to be sent in different directions simultaneously.

[0194] Example 12 can include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to allow non-consecutive (and preferably symmetrical across the two half-slots) allocation of OFDM symbols per PRS resource within a slot, enabling the realization of an SRI duration at the sub-slot level (e.g., half-slot) using a UL-PRS resource set. For example, a comb-2 UL-PRS resource of length 4 can be realized with an equal distribution of the 4 symbols across two 2-symbol occurrences, each in a half-slot. Non-consecutive allocation of OFDM symbols for a PRS resource can be achieved by various means, such as allowing the configuration of the PRS resource symbol to be offset by a vector, etc.

[0195] Example 13 can include the setup from Example 1 or any other example herein, where a UL-PRS configuration allows configuring a periodicity with the granularity of the UL-PRS resource (e.g., per UL-PRS resource) as opposed to defining it at the resource quantity level. Therefore, different resources within the set can have different periodicities to support better spatial adjustments to cover the field of view.

[0196] Example 14 may include the setup from Example 1 or any other example herein, where a UL-PRS configuration allows for half-slot periodicity (e.g., for higher-speed use cases, etc.).

[0197] Example 15 may include the setup from Example 1 or any other example herein, where a UL-PRS configuration allows multiple levels of periodicity control (to allow multiple / different repetition patterns) to enable a fast periodicity (sampling rate) for quickly collecting a number of UL-PRS resources, followed by a slower periodicity to allow a waiting period for dedicated communications before the next fast period.

[0198] Example 16 can incorporate the setup from Example 1 or any other example herein, where a UL-PRS configuration enables a fully programmable fast burst of UL-PRS transmits / captures. The transmit / capture burst must occur at a faster rate than DCI updates, so it must include all necessary parameters without requiring interruption by DCI or RRC reconfiguration. The transmit / capture rate (the update rate for a full Doppler FFT x SRI duration), the number of transmits / captures, and normal UL-PRS parameters, such as OFDM symbol position within RB, comb size, and cyclic offset, must be set independently for the transmit / capture burst.

[0199] Example 17 may include the setup from Example 1 or any other example herein, where the UL-PRS configuration allows different power control parameters for resources within a set, i.e., to allow one PC configuration per UL-PRS resource (beam).

[0200] Example 18 can include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to allow multiple (two or more) UL-PRS resource sets with potentially identical 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 resource start location). These sets can even be subjected to TDM within a single slot to allow the realization of different (e.g., two or more) symbol repetition intervals (SRIs) using different (e.g., two or more) sets and their repetitions. Similar to the setup from Example 12, this extension allows the realization of a sub-slot SRI duration (e.g., half-slot) or SRIs with durations of non-integer multiples of slots (e.g., 1.5 slots, etc.).), but instead by using two or more UL-PRS resource sets. For example, the start symbol offset within a slot and (if required) the number of symbols for a UL-PRS resource can be configured differently for the two or more resource sets, which can typically share other parameters.

[0201] Example 19 may include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to allow separate parameters and / or use for configuring UL-PRS for the purpose of acquisition.

[0202] Example 20 can include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to allow for different acquisition uses corresponding to different categories of use cases that require different measurements / processing. Accordingly, different measurements can be expected for each use.

[0203] Example 21 may include the setup from Example 20 or any other example herein, wherein, for the purpose of capturing use cases, inferring channel variations or resolving channel multipath utilization (multipath utilization), e.g. weather monitoring or (AI-based) gesture recognition, etc., channel measurements can be performed (and reported) by the capture receiver.

[0204] Example 22 may include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to also include the total duration (e.g., in a number of slots) over which the set (at least for semi-periodic sets and periodic sets) occurs with a certain configured periodicity.

[0205] Example 23 may include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to also allow the repetition of the entire periodic occurrence of a set over a specified configured duration (as extended from Example 22) with a configurable number of slots (>=0) as a gap between the repetitions.

[0206] Example 24 may include the setup from Example 23 or any other example herein, where the configuration may be specified by RRC signaling, MAC CE or DCI.

[0207] Example 25 may include the setup from Example 1 or any other example herein, where the entire periodic occurrence of a set over a certain configured duration may occur irregularly based on some specifications / triggers (i.e., the intervals with the configured duration may reoccur based on specifications (start / stop)).

[0208] Example 26 may include the setup from Example 1 or any other example herein, extending the UL-PRS configuration to also allow multiple periodicities for a UL-PRS(SRS) resource set configuration, potentially each with a total effective duration over which the periodic pattern continues with the corresponding periodicity (e.g., in a number of slots, etc.).

[0209] Example 27 can include a device used in a positioning entity to locate user devices (UEs), wherein the device comprises a processor circuit arrangement designed to also generate Doppler-related measurements of the UE based on a transmitted UL-PRS signal (or an extended version of the PRS signal as described in Examples 1-26). For example, currently, as part of performing positioning measurements (e.g., ToA, etc.), a correlation function can be applied in the delay (distance) domain, and the peaks in the correlation function can lead to position estimates. The correlation function can be extended to also have a second dimension in the Doppler domain to enable Doppler processing. This can be similar to generating the 2D periodogram that is part of the baseline object detection receiver processing for sensing applications.

[0210] 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 device (UE), an uplink positioning reference signal (UL-PRS); and performing a detection based on the UL-PRS.

[0211] Example 29 includes the procedure from Example 28 and / or another example herein, further comprising identifying, based on a UL-PRS resource of the UL-PRS, a detection beam for detection.

[0212] Example 30 includes the procedure from one of Examples 28-29 and / or another 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).

[0213] Example 31 includes the procedure from one of Examples 28-30 and / or another example herein, furthermore comprehensively identifying, based on a resource set of the UL-PRS, the SRI.

[0214] Example 32 includes the procedure from one of Examples 28-31 and / or another example herein, further comprising identifying, based on a time interval containing repetitions of a resource set with its periodicity with respect to the UL-PRS, a capture block.

[0215] Example 33 includes the procedure from one of Examples 28-32 and / or another example herein, further comprising identifying based on a periodic frequency of occurrence of the UL-PRS and an update rate for recording.

[0216] Example 34 includes a method to be performed by a user device (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 acquisition-related parameters; generating, based on the one or more acquisition-related parameters, an uplink positioning reference signal (UL-PRS); and transmitting the UL-PRS to a base station, wherein the base station is to use the UL-PRS for acquisition.

[0217] Example 35 includes the procedure from Example 34 and / or another example herein, wherein one or more acquisition-related parameters include an acquisition beam for acquisition and wherein the UL-PRS includes a UL-PRS resource based on the acquisition beam.

[0218] Example 36 includes the method from one of Examples 34-35 and / or another example herein, wherein the one or more detection-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.

[0219] Example 37 includes the procedure from one of Examples 34-36 and / or another example herein, wherein one or more acquisition-related parameters include the SRI and wherein the UL-PRS includes a resource set of the UL-PRS based on the SRI.

[0220] Example 38 includes the procedure from one of Examples 34-37 and / or another example herein, wherein the one or more acquisition-related parameters include an acquisition block and wherein the UL-PRS includes a time interval containing repetitions of a resource set with its periodicity with respect to the UL-PRS based on the acquisition block.

[0221] Example 39 includes the procedure from one of Examples 34-38 and / or another example herein, wherein the capture-related parameter is a capture update rate and wherein the UL-PRS includes a periodic frequency of occurrence of the UL-PRS based on the update rate.

[0222] Example 40 includes a method to be performed by an electronic device in a cellular network, the method comprising: identifying an uplink positioning reference signal (UL-PRS) resource with respect to a capture to be performed during a capture operation, wherein a UL-PRS resource includes multiple UL-PRS symbols; generating a cellular transmission that includes a symbol repetition interval (SRI) consisting of the UL-PRS resource; and transmitting the cellular transmission during the performance of the cellular transmission.

[0223] Example 41 includes the procedure from Example 40 and / or another example herein, wherein the multiple UL-PRS symbols include three UL-PRS symbols.

[0224] Example 42 includes the procedure from one of Examples 40-41 and / or another 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 multiple UL-PRS symbols to a first subcarrier of an orthogonal frequency-division multiplex (OFDM) symbol of a slot; and mapping, based on the identified frequency domain comb size, a second UL-PRS symbol of the multiple UL-PRS symbols to a second subcarrier of the OFDM symbol.

[0225] Example 43 includes the procedure from Example 42 and / or another example herein, where the multiple UL-PRS symbols are mapped to a subset of the OFDM symbols of the slot.

[0226] Example 44 includes the procedure from Example 43 and / or another example herein, wherein OFDM symbols that are not in the subset of OFDM symbols are not consecutive.

[0227] Example 45 includes the procedure from Example 43 and / or another 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 OFDM symbols of the slot.

[0228] Example 46 incorporates the method from one of Examples 40-45 and / or another example herein, wherein a pattern of a UL-PRS resource for cellular transmission is based on an M-level comb over N UL-PRS symbols, where M is greater than N.

[0229] Example 47 includes the procedure from Example 46 and / or another example herein, wherein resource elements (REs) of successive UL-PRS symbols of the multiple UL-PRS symbols are the same.

[0230] Example 48 includes the procedure from one of Examples 40-47 and / or another example herein, wherein the cellular transfer is a multi-port UL-PRS resource transfer.

[0231] Example 49 includes the procedure from Examples 40-48 and / or another example herein, wherein a UL-PRS transmission periodicity is configured at a UL-PRS resource level.

[0232] Example 50 includes the procedure from Example 49 and / or another example herein, wherein the UL-PRS periodicity is based on half the length of a slot, the length of a slot, or an integer multiplication of the length of a slot.

[0233] Example 51 includes the procedure from one of Examples 40-50 and / or another example herein, wherein the UL-PRS resource is based on a specification of a UL-PRS configuration received via radio resource control or RRC signaling, a media access control (MAC CE) control, or downlink control (DCI) information.

[0234] Example 52 includes the method from one of Examples 40-51 and / or another example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set which contains multiple UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control or PC parameter that is different from a PC parameter of a second UL-PRS resource of the UL-PRS resource set.

[0235] Example 53 includes a user device (UE) comprising: memory for storing an uplink positioning reference signal (UL-PRS) resource based on a 5G-NR bearing reference signal (SRS), wherein the UL-PRS resource is associated with a capture to be performed during a capture operation, wherein a UL-PRS resource includes multiple UL-PRS symbols; and one or more processors designed to: generate a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during the performance of the capture operation.

[0236] Example 54 includes the item from Example 53 and / or any other example herein, wherein the multiple UL-PRS symbols include three UL-PRS symbols.

[0237] Example 55 includes the subject matter from one of Examples 53-54 and / or another 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 multiple UL-PRS symbols to a first subcarrier of an orthogonal frequency-division multiplex (OFDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the multiple UL-PRS symbols to a second subcarrier of the OFDM symbol.

[0238] Example 56 includes the item from Example 55 and / or another example herein, wherein the multiple UL-PRS symbols are mapped to a subset of the OFDM symbols of the slot.

[0239] Example 57 includes the item from Example 56 and / or any other example herein, where OFDM symbols that are not in the subset of OFDM symbols are not consecutive.

[0240] Example 58 includes the subject from 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.

[0241] Example 59 includes the subject matter from one of Examples 53-58 and / or another example herein, wherein a pattern of a UL-PRS resource for cellular transmission is based on an M-level comb over N UL-PRS symbols, where M is greater than N.

[0242] Example 60 includes the item from Example 59 and / or any other example herein, wherein resource elements (REs) of successive UL-PRS symbols of the multiple UL-PRS symbols are the same.

[0243] Example 61 includes the subject from one of Examples 53-60 and / or another example herein, wherein the cellular transfer is a multi-port UL-PRS resource transfer.

[0244] Example 62 includes the item from one of Examples 53-61 and / or another example herein, with a UL-PRS transmission periodicity configured at a UL-PRS resource level.

[0245] Example 63 includes the subject matter from Example 62 and / or any other example herein, wherein the UL-PRS periodicity is based on half the length of a slot, the length of a slot, or an integer multiplication of the length of a slot.

[0246] Example 64 includes the item from one of Examples 53-63 and / or another example herein, wherein the UL-PRS resource is based on a specification of a UL-PRS configuration received via radio resource control or RRC signaling, a media access control (MAC CE) control, or downlink control (DCI) information.

[0247] Example 65 includes the subject matter from one of Examples 53-64 and / or another example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set which contains multiple UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control or PC parameter that is different from a PC parameter of a second UL-PRS resource of the UL-PRS resource set.

[0248] Example 66 includes one or more non-volatile computer-readable media (NTCRM) containing instructions that, when executed by one or more processors of a user device (UE), are intended to cause the UE to: identify an uplink positioning reference signal (UL-PRS) resource based on a fifth-generation (5G) new radio or NR bearing reference signal (SRS), wherein the UL-PRS resource is associated with a capture to be performed during a capture operation, and wherein a UL-PRS contains multiple UL-PRS symbols; generate a cellular transmission containing a symbol repetition interval (SRI) based on the UL-PRS resource; and transmit the cellular transmission during the performance of the capture operation.

[0249] Example 67 includes the item from Example 66 and / or any other example herein, wherein the multiple UL-PRS symbols include three UL-PRS symbols.

[0250] Example 68 includes the subject from one of Examples 66-67 and / or another example herein, the instructions further serving 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 multiple UL-PRS symbols to a first subcarrier of an orthogonal frequency-division multiplex (OFDM) symbol of a slot; and map, based on the identified frequency domain comb size, a second UL-PRS symbol of the multiple UL-PRS symbols to a second subcarrier of the OFDM symbol.

[0251] Example 69 includes the subject matter from one of Examples 66-68 and / or another example herein, wherein a pattern of a UL-PRS resource for cellular transmission is based on an M-level comb over N UL-PRS symbols, where M is greater than N.

[0252] Example 70 includes the subject from one of Examples 66-69 and / or another example herein, wherein the cellular transfer is a multi-port UL-PRS resource transfer.

[0253] Example 71 includes the item from one of Examples 66-70 and / or another example herein, with a UL-PRS transmission periodicity configured at a UL-PRS resource level.

[0254] Example 72 includes the subject matter from any of Examples 66-71 and / or any other example herein, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set which contains multiple UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control or PC parameter that is different from a PC parameter of a second UL-PRS resource of the UL-PRS resource set.

[0255] Example Z01 may include a facility comprising means to carry out one or more elements of a procedure or related procedure described in any of Examples 1-72, or any other procedure or process described herein.

[0256] Example Z02 may include one or more non-volatile, computer-readable media containing 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.

[0257] Example Z03 may include a device comprising logic, modules or circuitry for performing one or more elements of a procedure described in or related to any of Examples 1-72, or of any other procedure or process described herein.

[0258] Example Z04 may include a method, technique or process as described in or related to any of Examples 1-72, or sections or parts thereof.

[0259] Example Z05 may include a device comprising: one or more processors and one or more computer-readable media comprising instructions which, when executed by the one or more processors, cause the one or more processors to perform the procedure, techniques or process as described in or related to any of Examples 1-72 or sections thereof.

[0260] Example Z06 may include a signal as described in or related to any of Examples 1 - 72, or sections or parts thereof.

[0261] 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 sections or parts thereof, or as otherwise described in the present disclosure.

[0262] Example Z08 may include a signal encoded with data as described in or related to any of Examples 1-72, or sections or parts thereof, or as otherwise described in the present disclosure.

[0263] 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 sections or parts thereof, or as otherwise described in the present disclosure.

[0264] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein the execution of the computer-readable instructions by one or more processors is intended 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 parts thereof.

[0265] Example Z11 may include a computer program comprising instructions, wherein the execution of the program by a processing element is intended to cause the processing element to execute the procedure, techniques or process as described in or related to any of Examples 1-72, or parts thereof.

[0266] Example Z12 can contain a signal in a wireless network, as shown and described herein.

[0267] Example Z13 can include a method for communication in a wireless network, as shown and described here.

[0268] Example Z14 can include a system for providing wireless communication, as shown and described here.

[0269] Example Z15 can include a wireless communication device, as shown and described here.

[0270] Each of the examples described above can be combined with any other example (or combination of examples) unless expressly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not to be considered exhaustive or as limiting the scope of protection of embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or can be acquired by practicing different embodiments. Abbreviations

[0271] Unless otherwise stated herein, the terms, definitions, and abbreviations may correspond to those defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein. 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G core network AC Application Client ACR Application Context Implementation ACK confirmation ACID Application Client Identification ADRF Analytics Data Repository Function AF Application Function AM Confirmed Mode AMBR Aggregated Maximum Bitrate AMF Access and Mobility Management Function AN access network AnLF Logical Analysis Function ANR Automatic Neighborhood Relationship AOA arrival angle AP Application Protocol, antenna connector, access point API Application Programming Interface APN Access Point Name ARP allocation and storage priority ARQ Automatic Re-Request AS access layer ASP Application Service Provider ASN.1 Abstract Syntax Notation One AUSF authentication server function AWGN Additives White Gaussian Noise BAP backhaul adjustment protocol BCH Broadcast Channel BER (Bit Error Ratio) BFD beam failure detection BLER block error rate BPSK Binary Phase Shift Keying BRAS Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW bandwidth BWP bandwidth portion C-RNTI Temporary Cell Network Identifier CA Carrier Aggregation, Certification Authority CAPEX investment expenditure CBD candidate beam detection CBRA access conflict-based direct access CC component carrier, country code, cryptographic checksum CCA Clear Channel Rating CCE control channel element CCCH common control channel CE Coverage Improvement CDM Content Delivery Network CDMA code multiplex access CDR Billing Data Request CDR Billing Data Response CFRA Non-Competition Random Access CG cell group CCF Billing Gateway Function CHF clearing function CI Cell Identity CID Cell ID (e.g., positioning method) CIM Common Information Model CIR Carrier-to-Noise Ratio CK encryption key CM Connection Management, conditionally mandatory CMAS Commercial Mobile Warning Service CMD command CMS Cloud Management System CO Conditionally optional CoMP (Coordinated Multipoint) CORESET control resource quantity COTS Commercial serial product CP control plane, cyclic prefix, connection point CPD connection point descriptor CPE equipment at the customer site CPICH Joint Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit, central processing unit C / R Command / Response Field Bit CRAN Cloud radio access network, Cloud RAN CRB Shared Resource Block CRC Cyclic Redundancy Check CRI channel health information resource indicator, CSI-RS resource indicator C-RNTI Cell-RNTI CS Line-switched CSCF Call Session Control Function CSAR Cloud Service Archive CSI channel state information CSI-IM CSI Interference Measurement CSI-RS CSI reference signal CSI-RSRP CSI Reference Signal Reception Power CSI-RSRQ CSI Reference Signal Reception Quality CSI-SINR CSI signal-to-noise ratio CSMA carrier detection - multiple access CSMA / CA CSMA with collision avoidance CSS shared search space, cell-specific search space CTF settlement trigger function CTS Readiness to Transmit CW Codeword CWS competitor window size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Einsatz-Flavor DL Downlink DMTF Distributed Management Working Group DPDK Data Layer Development Kit DM-RS, DMRS demodulation reference signal DN Data Network DNN Data Network Name DNAI Data Network Access Identifier DRB data radio carrier DRS Discovery Reference Signal DRX Discontinuous Reception DSL Domain-Specific Language Digital Subscriber Line DSLAM DSL access multiplexer DwPTS Downlink Pilot Time Slot E-LANE thernet local network E2E End-to-End EAS Edge application server ECCA Extended Clear Channel Rating, CCA Extended ECCE Improved Control Channel Element, Improved CCE ED Energy Detection EDGE Improved Data Rates for GSM Evolution (GSM Evolution) EAS Edge application server EASID Edge application server identification ECS Edge configuration server ECSP Edge Computing Service Provider EDN Edge Data Network EEC Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server EESID Edge enabler server identification EHE Edge Hosting Environment EGMF Exposure Control Management Function EGPRS Enhanced GPRS EIR Equipment Identity Register eLAA Extended Licensed Supported Access, Extended LAA EM Element Manager eMBB extended mobile broadband EMS Element Management System eNB Evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR dual connectivity EPC Developed Package Core EPDCCH extended PDCCH, extended physical downlink control channel EPRE Energy per Resource Element EPS-developed packaging system EREG Extended REG, Extended Resource Element Groups ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC, embedded universal integrated circuit board E-UTRA Developed UTRA E-UTRAN Developed UTRAN EV2X Enhanced V2X F1AP F1 Application Protocol F1-C F1 control plane interface F1-U F1 user-level interface FACCH Fast Associated Control Channel FACCH / F Fast Associated Control Channel / Full Rate FACCH / H Faster Associated Control Channel / Half Rate TECHNICAL Forward Access Channel FAUSCH Fast Uplink Signaling Channel FB Function Block FBI feedback information FCC Federal Communications Commission FCCH frequency correction channel FDD Frequency Duplex FDM Frequency Division Multiplexing FDMA Frequency Division Multiple Access FE Frontend FEC Forward Error Correction FFS for further investigation FFT Fast Fourier Transform feLAA further expanded licensed supported access, further expanded LAA FN Frame number FPGA field programmable gate array FR frequency range FQDN fully qualified domain name G-RNTI Temporary GERAN radio network identity GERAN GSM-EDGE-RAN, GSM-EDGE radio access network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Global Satellite Navigation System) gNB NodeB next generation gNB-CU gNB central unit, next generation NodeB central unit gNB-DU distributed gNB unit, next generation distributed NodeB unit GNSS Global Navigation Satellite System GPRS General Packet-Oriented Radio Service GPSI Generic Public Subscriber Identifier GSM Global System for Mobile Communications, Groupe Special Mobile GTP GPRS Tunnel Protocol GTP-UGPRS user-level tunnel protocol GTS Go To Sleep Signal (related to WUS) GUMMEI Global unique MME identifier GUTI Global unique temporary EU identity HARQ Hybrid-ARQ, hybrid automatic re-request HANDO Handover HFN HyperFrame Number HO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Public Terrestrial Mobile Network HSDPA High-Speed ​​Downlink Packet Access HSN Jump Sequence Number HSPA High-Speed ​​Packet Access HSS Home Participant Server HSUPA High-Speed ​​Uplink Packet Access HTTP Hypertext Transfer Protocol HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-Cell Disruption Coordination ID identity, identifier IDFT Inverse Discrete Fourier Transform IE Information Element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI information element identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IIOT Industrial Internet of Things IM interference measurement, intermodulation, IP multimedia IMC IMS authorization certificates IMEI International Mobile Device Identity IMGI International Mobile Group Identity IMPI Private IP Multimedia Identity IMPU Public IP Multimedia Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT (Internet of Things) IP Internet Protocol IPsec IP security, Internet Protocol security IP-CAN IP Connectivity Access Network IP-M IP-Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS Synchron IRP Integration Reference Point ISDN Digital Network for Integrated Services ISIM IM Service Identity Module ISO International Organization for Standardization ISP Internet Service Provider IWF Interworking Function I-WLAN Interworking-WLAN Limited length of the folding code, individual USIM key kB Kilobyte (1000 bytes) kbps kilobits per second Kc encryption key AI Individual Participant Authentication Key KPI Key Performance Indicator KQI Key Quality Indicator KSI key set identifier ksps Kilo symbols per second KVM Virtual Kernel Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 Reference Signal Receive Power L2 Layer 2 (Data Link Layer) L3 Layer 3 (Network Layer) LAA Licensed Supported Access LAN local network LADN Local Area Data Network LBT Listen Before Talk LCM Lifecycle Management LCR Low Chip Rate LCS Site Services LCID Logic Channel ID LI layer indicator LLC logic link control, low layer compatibility LMF site management function LOS line of sight LPLMN Local PLMN LPP LTE Positioning Protocol LSB Least Significant Bit LTE Long Term Evolution LWA LTE-WLAN Aggregation LWIP LTE / WLAN radio plane integration with IPsec tunnel LTE Long Term Evolution M2M machine-to-machine MAC Media Access Control (Protocol Layer Context) MAC message authentication code (security / encryption context) MAC-A MAC for authentication and key agreement (context TSG T WG3) MAC-IMAC for data integrity of signaling messages (context TSG T WG3) MANO Management and Orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MCC mobile network country code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and Coding Scheme MDAF Management Data Analysis Function MDAS Management Data Analysis Service MDT Minimization of Drive Tests ME mobile device MeNB Master-eNB MER message error ratio MGL measurement gap length MRP measurement gap repetition period MIB master information block, management information base MIMO Multiple Input / Multiple Output MLC Mobile Location Center MM Mobility Management MME Mobility Management Unit MN Master Node MNO mobile network operator MO measuring object, mobile origin MPBCH Physical MTC Broadcast Channel MPDCCH Physical MTC Downlink Control Channel MPDSCH Physical Shared MTC Downlink Channel MPRACH Physical MTC Direct Access Channel MPUSCH Physical Shared MTC Uplink Channel MPLS MultiProtocol Label Switching MS Mobile Station MSB Highest Significant Bit MSC Mobile Interchange MSI minimum system information, MCH planning information MSID Mobile Station Identifier MSIN mobile station identification number MSISDN Mobile Subscriber ISDN Number MT Mobil contract completed, mobile contract MTC Machine Type Communication MTLF Model Training Logical Functions mMTC Massive MTC, Massive Machine Type Communication MU-MIMO Multi-user MIMO MWUS MTC wake-up signal, MTC-WUS NACK Negative Confirmation NAI Network Access Identifier NAS Non-Access Stratum, Non-Access Stratum Layer NCT Network Connectivity Topology NC-JT Non-coherent joint transmission NEC Network Capabilities Discovery NE-DC NR-E-UTRA dual connectivity NEF Network Discovery Function NF network function NFP network forwarding path NFPD Network Forwarding Path Descriptor NFV Network Function Virtualization NFVI NFV infrastructure NFVO NFV Orchestrator NG Next Generation, Next-Gen NGEN-DC NG-RAN-E-UTRA-NR dual connectivity NM Network Manager NMS Network Management System N-PoP Network Presence Point NMIB, N-MIB Narrowband MIB NPBCH Physical Narrowband Broadcast Channel NPDCCH Physical Narrowband Downlink Control Channel NPDSCH Shared Physical Narrowband Downlink Channel NPRACH Physical Narrowband Direct Access Channel NPUSCH Shared Physical Narrowband Uplink Channel NPSS narrowband primary synchronization signal NSSS Narrowband Secondary Synchronization Signal NR New-Radio, Neighborhood Relationship NRF NF repository function NRS narrowband reference signal NS Network Service NSA Non-standalone operating mode NSD Network Service Descriptor NSR Network Service Recording NSSAI Network Slice Selection Assistant Information S-NNSAI Single NSSAI NSSF Network Slice Selection Function NW Network NWDAF Network Data Analysis Function NWUS narrowband wake-up signal, narrowband WUS NZP Non-Zero Power O&M Operations and Maintenance ODU2 Optical Channel Data Unit - Type 2 OFDM Orthogonal frequency division multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out-of-Band OOS Out-of-Sync OPEX operating costs OSI Other System Information OSS Operational Support System OTA Over-the-Air / Air PAPR Peak-to-Average Power Ratio PAR (Peak-to-Average Ratio) PBCH Physical Broadcast Channel PC performance control, personal computer PCC primary component carrier, primary CC P-CSCF Proxy-CSCF PCell primary cell PCI Physical Cell ID, Physical Cell Identity PCEF Policy and Fee Enforcement Function PCF policy control function PCRF Policy Control and Fee Regulation Function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Network, Public Data Network PDSCH Shared Physical Downlink Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PDF package flow description P-GW PDN Gateway PHICH Physical Hybrid ARQ Indicator Channel PHY Physical Layer PLMN Public Terrestrial Mobile Network PIN Personal Identification Number PM Performance Measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Recording POC PTT-over-Cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH PRB Physical Resource Block PRG Physical Resource Block Group ProSe proximity services, proximity-based service PRS positioning reference signal PRR packet receiving radio PS Parcel services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink-Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Shared Physical Sidelink Channel PSFCH Physical Sidelink Feedback Channel PScell ​​Primary Scell PSS Primary Synchronization Signal PSTN Public Telephone Exchange Network PT-RS phase tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Shared physical uplink channel QAM quadrature amplitude modulation QCI QoS class of the identifier QCL quasi-colocalization QFI QoS flow ID, QoS flow identifier QoS Service Quality QPSK Quadrature (quaternary) phase shift keying QZSS Quasi-Zenith Satellite System RA-RNTI Direct Access-RNTI RAB radio access carrier, direct access burst RACH Direct Access Channel RADIUS Remote Authentication Dial In User Service RAN wireless access network RAND random number (used for authentication) RAR Direct Access Response RAT wireless access technology RAU Routing Area Update RB Resource Block, Radio Carrier RBG Resource Block Group REG Resource Element Group Release REQ requirement RF high frequency RI rank indicator RIV Resource Indicator Value RL radio connection RLC radio link control, radio link control layer RLC AM RLC Confirmed Mode RLC UM RLC Unconfirmed Mode RLF radio communication failure RLM radio link monitoring RLM-RS reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Minimum System Information RN Relay Node RNC wireless network control RNL radio network layer RNTI Temporary Radio Network Identifier ROHC Robust Header Compression RRC Radio Resource Control, Radio Resource Control Layer RRM Radio Resource Management RS reference signal RSRP Reference Signal Reception Power RSRQ Reference Signal Reception Quality RSSI signal strength indicator RSU Roadside Unit RSTD reference signal time difference RTP Real-Time Protocol RTS broadcast readiness RTT cycle time Rx reception, receiving, receiver S1AP S1 application protocol S1-MME S1 for the control level S1-U S1 for the user level S-CSCF Serving CSCF S-GW Supplying Gateway S-RNTI Temporary SRNC radio network identity S-TMSI Temporary SAE Mobile Station Identifier SA Standalone operating mode SAE System Architecture Development SAP Service Access Point SAPD service access point descriptor SAPI Service Access Point Identifier SCC secondary component carrier, secondary CC SCell secondary cell SCEF Fitness for Duty Detection Function SC-FDMA Single Carrier Frequency Division Multiple Access SCG secondary cell group SCM Security Context Management SCS subbeam spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer SDL Additional Downlink SDNF network function with structured data storage SDP Session Description Protocol SDSF function for structured data storage SDT Small Data Transmission SDU Service Data Unit SEAF safety anchor function SeNB Secondary eNB SEPP Safety Edge Protection Proxy SFI Slot Format Specification SFTD Spatial Frequency-Time Diversity, SFN and Frame Timing Difference SFN System Frame Number SgNB Secondary gNB SGSN Providing GPRS Support Node S-GW Supplying Gateway SI System Information SI-RNTI System information RNTI SIB System Information Block SIM subscriber identity module SIP Session-Initiated Protocol SIP System-in-Package SL Sidelink SLA Service Level Agreement SM Meeting Management SMF meeting management function SMS short messaging service SMSF SMS function SMTC SSB-based measurement timing configuration SN Secondary node, sequence number SOC System-on-Chip SON Self-Organizing Network SpCell special cell SP-CSI-RNTI Semi-persistent CSI-RNTI PLC Semi-persistent Planning SQN sequence number SR Planning Requirements SRB signaling radio carrier SRS bearing reference signal SS synchronization signal SSB synchronization signal block SSID Service Identifier SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator, Synchronization Signal Block Resource Indicator SSC Meeting and Service Continuity SS-RSRP Synchronization Signal-Based Reference Signal Reception Power SS-RSRQ Synchronization signal-based reference signal reception quality SS-SINR Synchronization signal-based signal-to-noise ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF search space set indicator SST Slice / Service Types SU-MIMO Single-user MIMO SUL Additional Uplink TA Timing Advance, Tracking Area TAC tracking area code TAG Timing-Advance Group TAI tracking area identity TAU tracking area update TB Transport Block TBS Transport Block Size TBD Still to be defined TCI transmission configuration indicator TCP (Transmission Communication Protocol) TDD Time Duplex TDM Time Division Multiplex TDMA time-division multiple access TE terminal TEID tunnel endpoint identifier TFT traffic flow template TMSI Temporary Mobile Subscriber Identity TNL network transport layer TPC transmit power control TPMI Transmitted Precoding Matrix Indicator TR Technical Report TRP, TRxP transmission receiving point TRS tracking reference signal TRX transceiver TS Technical Specifications, Technical Standard TTI transmission time interval Tx transmission, transmit, sender U-RNTI Temporary UTRAN radio network identity UART Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Device UDM Unified Data Management UDP User Datagram Protocol UDSF network function for unstructured data storage UICC Universal Integrated Circuit Board UL Uplink UM Unconfirmed Mode UML Unified Modeling Language UMTS Universal Mobile Telecommunications System UP user level UPF user level function URI (Uniform Resource Identifier) URL Unified Resource Locator URLLC Ultra-reliable and low latency USB Universal Serial Bus USIM Universal Participant Identity Module USS UE-specific search space UTRA UTRA terrestrial radio access UTRAN Universal Terrestrial Wireless Access Network UwPTS Uplink pilot time slot V2I Vehicle-to-Infrastructure V2P (Vehicle-to-Pedestrian) V2V vehicle-to-vehicle V2X Vehicle-to-Everything VIM Virtualized Infrastructure Manager VL Virtual Link VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Function VNFFG VNF forwarding graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNFM Manager VoIP Voice over IP, Voice over Internet Protocol VPLMN Visited Public Terrestrial Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX Worldwide Interoperability for Microwave Access WLAND wireless local area network WMAN Wireless Urban Network WPAND wireless personal network X2-C X2 control plane X2-U X2 user level XML Extensible Markup Language XRES Expected User Response XOR Exclusive OR ZC Zadoff-Chu ZP Zero power terminology

[0272] For the purposes of this document, the following terms and definitions apply to the examples and embodiments discussed herein.

[0273] The term "application" can refer to a complete and usable package, an environment for achieving a specific function within an operational environment. The term "AI / ML application" or similar can refer to an application that includes some AI / ML models and application-level descriptions.

[0274] The term “circuit arrangement,” as used herein, refers to hardware components, such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), 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., designed to provide the described functionality, is part of, or includes, the described functionality. In some embodiments, the circuit arrangement may execute one or more software or firmware programs to provide at least some of the described functionality.The term "circuit arrangement" can 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 execute the functionality of that program code. In these embodiments, the combination of hardware elements and program code can be described as a particular type of circuit arrangement.

[0275] The term "processor circuit arrangement," as used here, refers to a circuit arrangement capable of sequentially and automatically executing a series of arithmetic or logical operations, or of recording, storing, and / or transmitting digital data. The processing circuit arrangement may include one or more processor cores for executing instructions and one or more memory structures for storing program and data information.The term "processor circuit arrangement" can 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 computer-executable instructions, such as program code, software modules, and / or functional processes. A processing circuit arrangement may include multiple hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may, for example, include accelerators for computer vision (CV) and / or deep learning (DL).The terms “application circuit arrangement” and / or “baseband circuit arrangement” can be considered synonymous with “processor circuit arrangement” and can be referred to as such.

[0276] The term "interface circuit arrangement," as used herein, refers to, is part of, or includes a circuit arrangement that enables the exchange of information between two or more components or devices. The term "interface circuit arrangement" may refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, and / or the like.

[0277] The term "user device" or "UE" as used here refers to a device with wireless communication capabilities and can describe a remote user of network resources in a communications network. The term "user device" or "UE" can be considered synonymous with client, handset, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio, reconfigurable radio, reconfigurable mobile device, etc. Furthermore, the term "user device" or "UE" can include any type of wireless / wired device or any computing device with a wireless communication interface.

[0278] The term "network element," as used herein, refers to a physical or virtualized device and / or physical or virtualized infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered and / or referred to as synonymous with a networked computer, network hardware, network equipment, network node, router, switch, hub, bridge, wireless network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and / or the like.

[0279] The term "computer system," as used here, refers to any type of interconnected electronic devices, computer equipment, or their components. Additionally, the term "computer system" and / or "system" can refer to various components of a computer that are communicatively coupled. Furthermore, the term "computer system" and / or "system" can refer to multiple computer devices and / or multiple data processing systems that are communicatively coupled and designed to share data processing and / or network resources.

[0280] The terms “device”, “computer device”, or similar, as used here, refer to a computer device or computer system with program code (e.g., software or firmware) specifically designed to provide a particular computer resource. A “virtual device” is an image of a virtual machine implemented by a device equipped with a hypervisor that virtualizes or emulates a computer device or is otherwise intended to provide a particular computer resource.

[0281] As used herein, the term “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, storage space, processor / CPU time, processor / CPU utilization, processor and accelerator loads, hardware time or utilization, electrical power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and applications, workload units, and / or the like. A “hardware resource” may refer to computing, storage, and / or networking resources provided by one or more physical hardware elements.A "virtualized resource" can 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" can refer to resources that computer devices / systems can access via a communication network. The term "system resources" can refer to any type of shared entity used to provide services and may include compute and / or network resources. System resources can be viewed as a set of coherent functions, network data objects, or services accessible by a server, where such system resources reside on a single host or multiple hosts and are uniquely identifiable.

[0282] The term "channel," as used herein, refers to any tangible or intangible transmission medium used to communicate data or a data stream. The term "channel" may be synonymous with and / or interchangeable with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data connection," "carrier," "radio frequency carrier," and / or any other similar term denoting a path or medium over which data is transmitted. Furthermore, the term "link / connection," as used herein, refers to a connection between two devices via a RAT for the purpose of transmitting and receiving information.

[0283] The terms "instantiate," "instantiation," and the like, as used herein, refer to the creation of an instance. An "instance" also refers to a concrete occurrence of an object, which can occur, for example, during the execution of program code.

[0284] The terms "coupled," "communicatively coupled," and their derivatives are used here. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other; it can mean that two or more elements are indirectly touching but still interacting or working together; and / or it can mean that one or more other elements are coupled or connected between the elements described as coupled. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" can mean that two or more elements can be in contact with each other via a means of communication, such as a cable or other connection, a wireless communication channel, ink, and / or the like.

[0285] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to individual pieces of content within an information element or to a data element that contains content.

[0286] The term "SMTC" refers to an SSB-based measurement timing configuration, which is configured by SSB-MeasurementTimingConfiguration.

[0287] The term "SSB" refers to an SS / PBCH block.

[0288] The term “a primary cell” refers to the MCG cell operating at a primary frequency in which a UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0289] The term "primary SCG cell" refers to the SCG cell that the UE randomly accesses when it performs the reconfiguration using the sync procedure for DC operation.

[0290] The term "secondary cell" refers to a cell that provides additional radio resources on a dedicated cell for a UE configured with CA.

[0291] The term "secondary cell group" refers to a subset of supplying cells that includes the PSCell and zero or more secondary cells for a UE configured with DC.

[0292] The term "providing cell" refers to the primary cell for a UE in RRC_CONNECTED that is not configured with CA / DC, where there is only one providing cell that encompasses the primary cell.

[0293] The term "secondary cell" or "secondary cell group" refers to a set of cells that includes the special cell(s) and all secondary cells for a UE in RRC_CONNECTED that is configured with CA.

[0294] The term "special cell" refers to the PCell of MCG or the PSCell of SCG for DC operation; otherwise, the term "special cell" refers to the PCell.

[0295] The term "machine learning" or "ML" refers to the use of computer systems that implement algorithms and / or statistical models to perform one or more specific tasks without using explicit instructions, instead relying on patterns and inferences. ML algorithms create or estimate one or more mathematical models (referred to as "ML models" or similar) based on sample data (referred to as "training data," "model training information," or similar) to make predictions or decisions without being explicitly programmed to perform such tasks.In general, a machine learning (ML) algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model can be any object or data structure that is created after an ML algorithm has been trained on one or more training datasets. After training, an ML model can be used to make predictions about new datasets. Although the term "ML algorithm" refers to different concepts than the term "ML model," these terms may be used interchangeably for the purposes of this disclosure, as discussed herein.

[0296] The term "machine learning model," "ML model," or similar can also refer to ML methods and concepts used by an ML-supported solution. An "ML-supported solution" is a solution that handles a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep learning, etc.), neural networks, and the like. Depending on the implementation, a given ML model can have many sub-models as components, and the ML model can train all of these sub-models together.Separately trained machine learning (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 to an ML-powered solution; an ML pipeline can include one or more data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The "actor" is an entity that delivers an ML-powered solution using the results of the ML model inference. The term "ML training host" refers to an entity, such as a network function, that hosts the model training. The term "ML inference host" refers to an entity, such as a network function, that hosts the model during inference mode (which includes both model execution and, if applicable, online learning).The ML host informs the actor about the output of the ML algorithm, and the actor makes a decision on an action (an "action" is performed by an actor as a result of the output of an ML-supported solution). The term "model inference information" refers to information used as input to the ML model for deriving inferences; the data used to train an ML model and the data used to derive inferences can overlap, but "training data" and "inference data" refer to distinct concepts. QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] US 63 / 431,169

[0001] Cited non-patent literature

[0000] IDF AE8858 Numerology, frame structure, and signal resource dimensioning for joint communication and sensing systems

[0113] IDF AE9196 Multiplexing and joint design for communication and sensing

[0113] Lin X, Lee N. 5G and Beyond. Springer International Publishing; 2021

[0113] Hexa-X WP3 first deliverable D3.1 (Chapter 3.1), released end of 2021

[0113]

Claims

[1] User device (UE) comprising: Memory for storing an uplink positioning reference signal (UL-PRS) resource based on a fifth-generation (5G) new radio or NR bearing reference signal (SRS), wherein the UL-PRS resource is associated with a capture to be performed during a capture operation, and wherein a UL-PRS resource contains multiple UL-PRS symbols; and one or more processors designed for: Generating a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and Transmission of cellular transmission during the performance of the acquisition operation. [2] UE according to claim 1, wherein the multiple UL-PRS symbols include three UL-PRS symbols. [3] UE according to claim 1, wherein the one or more processors are further configured to: Identifying a frequency domain comb size from the set {1, 2, 3, 4, 8}; Mapping, based on the identified frequency domain comb size, of a first UL-PRS symbol of the multiple UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplex (OFDM) symbol of a slot; and Mapping, based on the identified frequency domain comb size, of a second UL-PRS symbol of the multiple UL-PRS symbols to a second subcarrier of the OFDM symbol. [4] UE according to claim 3, wherein the multiple UL-PRS symbols are mapped to a subset of the OFDM symbols of the slot. [5] UE according to claim 4, wherein OFDM symbols that are not in the subset of OFDM symbols are not consecutive. [6] UE according to 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 OFDM symbols of the slot. [7] UE according to any one of claims 1-6, wherein a pattern of a UL-PRS resource for cellular transmission is based on an M-level comb over N UL-PRS symbols, wherein M is greater than N [8] UE according to claim 7, wherein resource elements (REs) of successive UL-PRS symbols of the multiple UL-PRS symbols are the same. [9] UE according to any one of claims 1-6, wherein the cellular transfer is a multi-port UL-PRS resource transfer. [10] UE according to any one of claims 1-6, wherein a UL-PRS transmission periodicity is configured on a UL-PRS resource level. [11] UE according to claim 10, wherein the UL-PRS periodicity is based on half the length of a slot, the length of a slot or an integer multiplication of the length of a slot. [12] UE according to any one of claims 1-6, wherein the UL-PRS resource is based on a specification of a UL-PRS configuration received via radio resource control or RRC signaling, a media access control (MAC CE) or downlink control (DCI) information. [13] UE according to any one of claims 1-6, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set which includes multiple UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control or PC parameter which differs from a PC parameter of a second UL-PRS resource of the UL-PRS resource set. [14] One or more non-volatile computer-readable media (NTCRM) comprising instructions which, when executed by one or more processors of a user device (UE), are intended to cause the UE to: Identifying an uplink positioning reference signal (UL-PRS) resource based on a fifth generation (5G) new radio or NR bearing reference signal (SRS), wherein the UL-PRS resource is associated with a capture to be performed during a capture operation, and wherein a UL-PRS resource includes multiple UL-PRS symbols; Generating a cellular transmission that includes a symbol repetition interval (SRI) based on the UL-PRS resource; and Transmission of cellular transmission during the performance of the acquisition operation. [15] One or more NTCRMs according to claim 14, wherein the multiple UL-PRS symbols include three UL-PRS symbols. [16] One or more NTCRMs according to claim 14, wherein the instructions are further intended to cause the UE to: Identifying a frequency domain comb size from the set {1, 2, 3, 4, 8}; Mapping, based on the identified frequency domain comb size, of a first UL-PRS symbol of the multiple UL-PRS symbols to a first subcarrier of an orthogonal frequency division multiplex (OFDM) symbol of a slot; and Mapping, based on the identified frequency domain comb size, of a second UL-PRS symbol of the multiple UL-PRS symbols to a second subcarrier of the OFDM symbol. [17] One or more NTCRMs according to any one of claims 14-16, wherein a pattern of a UL-PRS resource for cellular transmission is based on an M-level comb over N UL-PRS symbols, wherein M is greater than N [18] One or more NTCRMs according to any one of claims 14-16, wherein the cellular transfer is a multi-port UL-PRS resource transfer. [19] One or more NTCRMs according to any one of claims 14-16, wherein a UL-PRS transmission periodicity is configured on a UL-PRS resource level. [20] One or more NTCRMs according to any one of claims 14-16, wherein the UL-PRS resource is a UL-PRS resource of a UL-PRS resource set which includes multiple UL-PRS resources, and wherein a first UL-PRS resource of the UL-PRS resource set has a power control or PC parameter which differs from a PC parameter of a second UL-PRS resource of the UL-PRS resource set.

Images